Arch Linux BBS - Applications & Desktop Environments

Hi @seth,Ok I ran;strace -o /tmp/nv-settings.strace nvidia-settings -a "[gpu:0]/GPUFanControlState=1" -a "[fan:0]/GPUTargetFanSpeed=40"After I ran the cmd, I got this output at the term;ERROR: The current user does not have permission for operation ERROR: Error assigning value 1 to attribute 'GPUFanControlState' (arch:0[gpu:0]) as specified in assignment '[gpu:0]/GPUFanControlState=1' (Operation not permitted for the current user). ERROR: The current user does not have permission for operation ERROR: Error assigning value 40 to attribute 'GPUTargetFanSpeed' (arch:0[fan:0]) as specified in assignment '[fan:0]/GPUTargetFanSpeed=40' (Operation not permitted for the current user).Here's the output;https://0x0.st/KtE4.txtTHANKS

Also can confirm. Import to PNG or use graphicsmagick - command 'gm import ...'

OK, will test.

correctmost wrote:Are you referring to the "shade" (up arrow) button?No, they are seeking a button toggle for, right-click the titlebar > toggle between "Always on Top" and "Same as Other Windows".I use Xfce for the last 10 years and I don't recall such button in xfwm4, but Xfce does not necessarily require using xfwm4, it is possible to use Xfce with some other window managers.Alternatively, KDE's kwin window manager settings has option for "Keep above" button.

Is that from a cosmic session?So why does timeshift try to open :1?DISPLAY=:0 timeshift-gtk

Only FYI, finally I bought a NVIDIA RTX 5060 Ti 16 Gb and this is another world.glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 16311 MB Total available memory: 16311 MB Currently available dedicated video memory: 15385 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 580.105.08 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6.0 NVIDIA 580.105.08 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 580.105.08 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20eglinfo -B GBM platform: EGL API version: 1.5 EGL vendor string: NVIDIA EGL version string: 1.5 EGL client APIs: OpenGL_ES OpenGL OpenGL core profile vendor: NVIDIA Corporation OpenGL core profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL core profile version: 4.6.0 NVIDIA 580.105.08 OpenGL core profile shading language version: 4.60 NVIDIA OpenGL compatibility profile vendor: NVIDIA Corporation OpenGL compatibility profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL compatibility profile version: 4.6.0 NVIDIA 580.105.08 OpenGL compatibility profile shading language version: 4.60 NVIDIA OpenGL ES profile vendor: NVIDIA Corporation OpenGL ES profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.105.08 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20 Wayland platform: EGL API version: 1.5 EGL vendor string: NVIDIA EGL version string: 1.5 EGL client APIs: OpenGL_ES OpenGL OpenGL core profile vendor: NVIDIA Corporation OpenGL core profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL core profile version: 4.6.0 NVIDIA 580.105.08 OpenGL core profile shading language version: 4.60 NVIDIA OpenGL compatibility profile vendor: NVIDIA Corporation OpenGL compatibility profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL compatibility profile version: 4.6.0 NVIDIA 580.105.08 OpenGL compatibility profile shading language version: 4.60 NVIDIA OpenGL ES profile vendor: NVIDIA Corporation OpenGL ES profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.105.08 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20 X11 platform: EGL API version: 1.5 EGL vendor string: NVIDIA EGL version string: 1.5 EGL client APIs: OpenGL_ES OpenGL OpenGL core profile vendor: NVIDIA Corporation OpenGL core profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL core profile version: 4.6.0 NVIDIA 580.105.08 OpenGL core profile shading language version: 4.60 NVIDIA OpenGL compatibility profile vendor: NVIDIA Corporation OpenGL compatibility profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL compatibility profile version: 4.6.0 NVIDIA 580.105.08 OpenGL compatibility profile shading language version: 4.60 NVIDIA OpenGL ES profile vendor: NVIDIA Corporation OpenGL ES profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.105.08 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20 Surfaceless platform: EGL API version: 1.5 EGL vendor string: NVIDIA EGL version string: 1.5 EGL client APIs: OpenGL_ES OpenGL OpenGL core profile vendor: NVIDIA Corporation OpenGL core profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL core profile version: 4.6.0 NVIDIA 580.105.08 OpenGL core profile shading language version: 4.60 NVIDIA OpenGL compatibility profile vendor: NVIDIA Corporation OpenGL compatibility profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL compatibility profile version: 4.6.0 NVIDIA 580.105.08 OpenGL compatibility profile shading language version: 4.60 NVIDIA OpenGL ES profile vendor: NVIDIA Corporation OpenGL ES profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.105.08 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20 Device platform: Device #0: Platform Device platform: EGL API version: 1.5 EGL vendor string: NVIDIA EGL version string: 1.5 EGL client APIs: OpenGL_ES OpenGL OpenGL core profile vendor: NVIDIA Corporation OpenGL core profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL core profile version: 4.6.0 NVIDIA 580.105.08 OpenGL core profile shading language version: 4.60 NVIDIA OpenGL compatibility profile vendor: NVIDIA Corporation OpenGL compatibility profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL compatibility profile version: 4.6.0 NVIDIA 580.105.08 OpenGL compatibility profile shading language version: 4.60 NVIDIA OpenGL ES profile vendor: NVIDIA Corporation OpenGL ES profile renderer: NVIDIA GeForce RTX 5060 Ti/PCIe/SSE2 OpenGL ES profile version: OpenGL ES 3.2 NVIDIA 580.105.08 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20 Device #1: Platform Device platform: libEGL warning: pci id for fd 26: 10de:2d04, driver (null) pci id for fd 30: 10de:2d04, driver (null) pci id for fd 31: 10de:2d04, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 26: 10de:2d04, driver (null) pci id for fd 30: 10de:2d04, driver (null) pci id for fd 31: 10de:2d04, driver (null) libEGL warning: egl: failed to create dri2 screen libEGL warning: pci id for fd 26: 10de:2d04, driver (null) eglinfo: eglInitialize failed Device #2: Platform Device platform: EGL API version: 1.5 EGL vendor string: Mesa Project EGL version string: 1.5 EGL client APIs: OpenGL OpenGL_ES OpenGL core profile vendor: Mesa OpenGL core profile renderer: llvmpipe (LLVM 21.1.5, 256 bits) OpenGL core profile version: 4.5 (Core Profile) Mesa 25.2.7-arch1.1 OpenGL core profile shading language version: 4.50 OpenGL compatibility profile vendor: Mesa OpenGL compatibility profile renderer: llvmpipe (LLVM 21.1.5, 256 bits) OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 25.2.7-arch1.1 OpenGL compatibility profile shading language version: 4.50 OpenGL ES profile vendor: Mesa OpenGL ES profile renderer: llvmpipe (LLVM 21.1.5, 256 bits) OpenGL ES profile version: OpenGL ES 3.2 Mesa 25.2.7-arch1.1 OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Only w/ gtk or also w/ Qt or lp (the latter had never been affected by the discussed bug)?Does downgrading cups to the previously working version restore function?The symptom suggest you're sending the PDF as raw data what's usually a misconfigured printer and/or broken filter.=> https://wiki.archlinux.org/title/CUPS/Troubleshooting enable debugging, restart cups, try to print something and post the logs.Probably open a new thread for that as it doesn't fit the general symptom/problem ITT.

Update: I have managed to find a consistent pattern, and I'm able to reproduce the problem at will, have managed to find a workaround, but I have been unable to figure out the cause.The problem has nothing to do with time, so it isn't that "sddm is awaiting on some service". It happens only if my Desktop is initially turned off, and then started. Upon starting the system, regardless of whether the display manager service is enabled, when the display manager starts (either by systemd or I call it in a TTY session), I will face a blank screen.At this point, all I need to do is get on a TTY session and reboot the system. Here's the kicker: whenever I explicitly reboot the system (rather than shut down and then start it again), the greeter pops up on the monitor without any issue.To summarize:1. System initially shut down -> Start system -> greeter does not appear2. System already running -> Reboot (systemctl reboot, reboot now, or whatever other method is considered 'rebooting') -> Greeter will appear after booting.I am quite surprised seeing it behave this way. I still don't know how to make it display the greeter for the first scenario. I'll try doing some more tests and see what sticks on the fence.

Strangely on my other computer with Ubuntu 24.04 it works without any problem. I think if I could identify all components in connecting chain, I'll be able to make it work on Arch as well.

https://wiki.archlinux.org/title/Reprod … lds/Status 1.3 [extra] suggests this may be due to Profile Guided Optimization .

Thank you! This is very helpful.I'm marking this one solved.

No, I had not tried to edit the PKGBUILD. It's done now, and it works! (without xdg-desktop-portal-gtk)Thanks a lot!

V1del wrote:Ah that could be possible... if we/you/the KDE devs are unlucky, the relevant wheather station assumed API abuse and either blocked your IP range specifically, blocked a potential KDE/Arch API Key or similar, but then it's a bit weird that the overview works out, but just the icon for "current" being affected. Maybe report to KDE?Tried the none system tray widget... same problem.  Its weird, that a different station from the same provider works just fine.  Looking at this it seems that one station has a human observer, and the other does not.  My suspicion is that at some point, the widget got "updated" and the method for displaying icons got changed.  This change must not, some how, account for the source of the weather icon observation...  just my guess.  Another bug report to KDE.

StarWolf3000 wrote:Fixed by discord 1:0.0.117-1 which eliminates the window manager/compositor title bar.Yeah I just updated and everything is normal

gkatev wrote:Appears to be due to xkeyboard-config: https://github.com/jordansissel/xdotool/issues/491Then I solved it with this script:#!/bin/bash while true; do xdotool key XF86Reload sleep 4 done