Arch Linux BBS - Applications & Desktop Environments

I can open Steam Parameters or launch recent game withour problemSo it's only the steam web client?Do you have similar issues w/ other chromium/electron-based clients?Does steam log any error to stdout?

I unfortunately had to forcefully shut down my system due to a crash/freeze and the problem started again, but this time I found the REAL solution. Once I got the "Software Renderer in use" notification from Plasma Renderer, I clicked the system tray and set the Rendering Backend (which must've been changed due to the crash) to "Automatic" and everything works perfectly.

I figured it out, it was not a ghost keyboard, but a ghost display.  There was a usb-c hub with an HDMI output on it that had falsely thought it was connected to a display.  So when I 'threw' the window, it went to the dummy display, which explains why the windows on my laptop monitor went inactive, and the scratch space was then opening on the dummy display as well.

doesn't react to anythingHow do you close it then?(All default mechanisms will use SIGTERM that the process needs to handle)I'm on wayland, (although im assuming firefox runs under xwayland) using hyprlandCheck and flip this aroundhttps://wiki.archlinux.org/title/Waylan … plicationshttps://wiki.archlinux.org/title/Firefox#XwaylandAlso test the behavior on not-hyprland (eg. weston will do - or openbox on actual X11)Right clicking will open a (modal) context menu - chances are that this blocks input to firefox but you can't see it for bugs specific to your compositor or even more likely: your configuration of it.Did you maybe copy+paste someone elses dotfiles?

nbqr wrote:Are there other WMs/compositors that use this style? Or can any WM/compositor (niri for example)  be made to use it?xmonad can do that, they call it "submapping".Here's how I use it to control window tabbing:... , ((mod, xK_t ), submap $ myTabbingSubmap) ... myTabbingSubmap = M.fromList $ [ ((0, xK_h), sendMessage $ pullGroup L) , ((0, xK_j), sendMessage $ pullGroup D) , ((0, xK_k), sendMessage $ pullGroup U) , ((0, xK_l), sendMessage $ pullGroup R) , ((0, xK_t), withFocused (sendMessage . UnMerge)) ]

Whenever I use my "adjust keyboard backlight brightness" command on my Lenovo ThinkPad (Fn + Space) it works, but in KDE Plasma I don't get any brightness popup that I usually do and the Brightness & Color applet shows NO changes (it does show changes for my "change screen brightness keys", UNTIL I restart upower.service THEN it works as normal and if I stop upower.service after starting it, then it replicates my problem exactly but the problem is is that whenever my laptop boots up it shows no error with upower.service and that it was started successfully. I've already tried enabling upower.service but to no avail. I'm not familiar with keyboard backlights in systems administration so all help is appreciated.Video: https://imgur.com/a/FGlIwoG

Update in (later) 2026, since this thread still shows up for me on google when searching for "GLEW Wayland" errors.Since 2.2.0, GLEW added 'glewContextInit()' (to be used instead of glewInit()) which removes the mandatory GLX display check and works on wayland just fine using the version provided by the default repository.

Thanks for the tip, anyway I didn't have any checked option for the Close behavior setting. The issue was solved in a way I cannot explain: I did several wipes and restores from backup without success, created and deleted new wallets which worked while the restore from backup didn't. I was about to give up when at a certain point I closed the restored wallet and re-opened it, and magically this fixed the problem. I'm not 100% sure I did it exactly as described since I was shooting in the dark at that time, but anyway it works again now.

Issue caused by the window compositor. Disabling the compositor can solve it immediately.

Recently, I've started noticing my Framework 13 Laptop will lock up/freeze after a bit of use (a few hours) having any Zathura window open for said duration of time.  The journal keeps name dropping Zathura, but I'm not so skilled to really understand what is actually going on.- Arch Linux x86_64- Framework 13- AMD Ryzen 5 7040U @ 4.97 GHz- AMD Radeon 760M Graphics- Linux Kernel 7.2.4-arch1-2- wlroots/sway 1.12Here is the pastebin (as to not clutter) of one of the segments from $ journalctl -eb -1 https://pastebin.com/uqSnVBEjPlease let me know if you need any more information.

I think the issue is happening because of latest Hyprland version . I should wait till next update

Also related to that part when I wrote that the screen was capped at 60Hz on the monitor controls, even with a powerful DP connection. The sway monitor mode was incorrect, I had to add to sway config "output DP-x mode 1920x1080@143.93Hz" which was not the mode selected by default by sway

karnage42 wrote:`ddcutil` 3.0.1 seems to have patched this: https://github.com/rockowitz/ddcutil/bl … ANGELOG.md, it's now available...Looking back at my boot history, pacman logs and ddctuil package infos, I downloaded the 3.0.1 version  during the same boot for when I downgraded my kernel which might explain why it worked. But I don't recall updating any packages during that time and the version was released before my issues happened so it doesn't make complete sense.

Apologies for how long it took to get back to you, but downgrading to 2.17.0 does not fix the issue, and I don't have 48-guessfamily.conf where it'd normally be.Is there a way I can change the font GPU Screen Recorder UI uses, just for that specific program?Update: Yes there is, and all I had to do was add the following to my user fontconfig file: <match target="pattern"> <test name="prgname" compare="eq"> <string>gsr-ui</string> </test> <edit name="family" mode="assign" binding="strong"> <string>Microsoft Sans Serif</string> </edit> </match> <match target="pattern"> <test name="prgname" compare="eq"> <string>gsr-notify</string> </test> <edit name="family" mode="assign" binding="strong"> <string>Microsoft Sans Serif</string> </edit> </match>Seems like any bitmap font doesn't work for GSR-UI for the time being, so I'll go ahead and mark this as worked around.EDIT: Additional block of code for the notifs too, since those are on a separate program.

Okay I think I solved it. My laptop is quite old and I used to start my plasma session via .xinitrc, so I still had the following there.export DESKTOP_SESSION=plasma exec startplasma-x11This was run when I started my plasma session via sddm, so it started the x11 session. After removing these lines the wayland session would not start, but I have now switched to Plasma Login Manager and everything seems to work now.