Another section of the log when this happened:
Aug 15 18:00:48 arch kwin_wayland[3328]: This plugin does not support raise()
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_VALUE in glTexStorage2D(width, height or depth < 1)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_OPERATION in glBindFramebuffer(non-gen name)
Aug 15 18:00:48 arch kwin_wayland[3328]: kwin_scene_opengl: 0x2: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer)
I realized it works in most programs, however it doesn’t in xwayland
And it’s precisely those xwayland programs (IntelliJ and Android Studio) that I would use this key most times
Used to be messing with kernel arguments and installing/tweaking boot parameters. That was until Grub broke, I learned systemd-boot and chrooting into the system via live USB
Now if I break anything it’s just a matter of “sigh, let me get the USB and type a few commands”
Depends on config, ArchWiki recommends optmizing some sysctl values to take advantage of it
it generally starts kicking in after >60% RAM usage even with this config
That’d be over 1TB with zram on
Happened once around two years ago, s botched update from mainstream or something like that. Made me learn systemd boot which is simple and never EVER use grub again
deleted by creator
deleted by creator
3rd gen i7 is outdated
Even a 8th gen i7 struggles to keep cool and quiet compared to Ryzens from 2019 onwards running the same stack
deleted by creator
I finally switched to AMD after 3 years in Linux, and man I didn’t even know I was suffering until I booted with AMD and didn’t have to take care of several env variables and separate modules for hw acc
It just works
ctrl isn’t stuck because entering and subsequently exiting plasma edit mode makes the default left click behavior work again, at least for some time
I managed to use Waypipe to open a GUI programa unde another user in the same Wayland display (actually someone else did a script for it, it’s in my profile history), so I guess it is possible to forward it with Waypipe remotely
Heya could you share how you do this trick to screen share ? Would it work on MS Teams?
It actually runs and feels smoother for me in a 144hz display and 2016 NVDIA card. Of course it still has its glitches and strange things happening from time to time, while with Xorg it “just works”. I’d say it’s still in alpha stage for Nvidia users, which require some tweaking and extra env variables to properly work; and in beta stage for everyone else
Most things would be solved if mainteners EVER updated their app’s electron version or stopped doing custom things with it and just let electron read $XDG_CONFIG_HOME/electron-flags.conf
I had a chuckle with his description because “Redondo” translates to “round” in Spanish
It’s not exempt from happening; however, it rarely ever updates and has less complexity/functionality than grub, which makes it less prone to error happening (be it from the developers, or from the user like me trying to theme it :))
tyvm