#fbdev #vconsole #unimap #fbcon #keymaps #codepages … 3 hours of unproductive time wasted on research why one machine uses code page 437 (the Linux default code page for #tty) and the other machine doesn’t.

It is mentioned on several pages, that the default is #CP437, and how I can change this default, but it seems like a mystery or forbidden knowledge WHY it is changed, without me actively changing it.

It might have to do with the screen resolutions of those two devices, or that one is an #Intel #GPU and the other is #Nvidia. But i was not able to find anything of value.

Oh #fuck this shit.

#ModernLinuxProblems #MagicBullshit

Can the system please let ME be in control and not doing seemingly undocumented random shit that is not represented in any configuration and feels like it’s hidden in a blackbox?

That would be great, thanks.

When using GIMP, “downgrading” to X11 by using Xwayland does not only fix the splash screen having window decoration (on Wayland it weirdly has), it also makes it possible to store window positions in multi-window mode (which on Wayland does not work).

#Wayland #ModernLinuxProblems #X11 #GIMP3 #GIMP #Xwayland

After lots and lots of waiting and trying out multiple different things regarding single window recording in #OBS  on #Wayland  running #labwc  there is now a solution in place I can work with.

I wrote a wrapper script (see here) that does the following things when added as #pipemenu in labwc and I click the menu entry to create the output.

I can now start #OBS and can add a #PipeWire screen recording and select the output (I have to do it blindly by just moving the cursor outside my actual display, because there is no menu, but that’s fine).

For what I’m doing the performance of the OBS preview is fast enough so I simply move the cursor over to the virtual output and use it “inside OBS”.

When I’m done, I invoke the script again, by clicking the remove entry which is dynamically shown if the output is active.

Until individual-window recording will be possible this is a good workaround.

#JustLinuxThings #ModernLinuxProblems #SharingIsCaring #scripting #Luanti #MinetestGame

//cc @whynothugo (thanks) @LXQt (thanks, too)

I wish #FreeCAD  would consistently work on #Wayland  … For a few releases it does, with the 1.0 release it stopped. (No, using #Xwayland is not a solution but a disgusting workaround that introduces a lot of issues).

#ModernLinuxProblems

Great. Another thing I need to work around. 😠

The #evolution of modern Linux feels more like a #devolution for me sometimes.

Latest entry in my personal list is @neovim which now uses the ancient #Vim leftover highlight configurations guifg and guibg by default, messing up modern colorschemes in Lua-only setups.

#ModernLinuxProblems

Modern Linux reminds me of when I started using Linux ca. 2 decades ago.

The graphics server randomly crashing without any usable error message, all applications have different font scaling and style. Screen recording not working (let alone individual windows recording), having to re-login for gaming, desktop menu has no proper icons support etc.

My last thing is starting log-running terminal tasks in a #tmux session because I know that at some point the GUI just stops working and drops me to the login prompt.

#ModernLinuxProblems #Nvidia #labwc #Wayland

Unfortunately #FreeCAD  does not run on #Wayland  (maybe it’s an #Nvidia issue?). By using #Xwayland this issue can be circumvented.

It of course comes with all the downsides of Xwayland, like lower performance, running less stable, etc.

With this custom startup script at least the scaling on my 4K 28" screen is fixed (you might want to tinker with the QT_FONT_DPI value). Just place as file with 755 permissions in /usr/local/bin/freecad.

I just wish it would work with Wayland on #labwc  instead of just showing a blue area where the 3D model would be.

//cc: @FreeCAD

#JustLinuxThings #ModernLinuxProblems