Created attachment 136904 [details] Working widgets SUMMARY Widgets are blank after reboot, but when I add the same widgets, they are working with the same setting. STEPS TO REPRODUCE 1. I have 4 widgets setup on the right side of my external screen 2. After rebooting they are all blank 3. When adding the same widgets back, they are working with the same settings as the ones that are blank and I don't have to configure anything. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Created attachment 136905 [details] Widgets not working Widgets not working... notice the date.
Operating System: openSUSE Tumbleweed 20210319 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.6-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600
Created attachment 136906 [details] Widgets not working again Another day widgets not working
https://youtu.be/3QOdc7H_ZaM Video shows adding the same widgets and they are already working with same settings as the blank widgets.
Is `ksystemstats` running? If not, do the widgets start working if you run it manually?
I run ksystemstats to get the Network widget to work, but the other widgets I have to add again.
Created attachment 136923 [details] had to add the widgets again...
My bad... I didn't check if ksystemstats was running before I ran it. I'll check if it's running after rebooting.
Created attachment 136924 [details] Widgets are working after reboot except Network Yes, ksystemstats is running after rebooting, but the widget is not working until I run it manually. jonzn4s+ 2004 1660 0 13:29 ? 00:00:00 /usr/bin/ksystemstats jonzn4s+ 2242 1760 0 13:29 ? 00:00:00 file.so [kdeinit5] file local:/run/user/1000/klauncheraMzpjZ.1.slave-socket local:/run/user/1000/ksystemstatstHyyrd.1.slave-socket jonzn4s+ 2243 1760 0 13:29 ? 00:00:00 file.so [kdeinit5] file local:/run/user/1000/klauncheraMzpjZ.1.slave-socket local:/run/user/1000/ksystemstatsHSbGeN.2.slave-socket After this reboot the other widgets are working this time. The blank widget issue does not happen every reboot, but it happens enough for me top open this bug.
After running the cmd, this is the output I get... Could not retrieve information for NVidia GPU 0 Found unsupported GPU: /sys/devices/pci0000:00/0000:00:02.0 "Session bus not found\nTo circumvent this problem try the following command (with Linux and bash)\nexport $(dbus-launch)" [1] Exit 1 ksystemstats --replace
Got it. Looks like there's something wrong with the interaction of the ksystemststs daemon and the applet on boot, until it's restarted manually.
Created attachment 136926 [details] Widgets dead again This time i just logged out because the desktop lag has returned. I logged back in and the widgets are dead again. Notice the date and time at the bottom of the pic.
Created attachment 136957 [details] DEAD Any idea why this issue never affects the root user? This blank widget thing is...
>"Session bus not found\nTo circumvent this problem try the following command (with Linux and bash)\nexport That looks very weird
Created attachment 137010 [details] dead again after reboot Last one... ;-))
>"Session bus not found\nTo circumvent this problem try the following command (with Linux and bash)\nexport $(dbus-launch)" Please include the output of "qdbus" and "ps aux | grep dbus"
Did you want this ran after a reboot? I haven't reboot in a few days to avoid the issue. Here it is before rebooting. jonzn4suse@ZBook-17-G2-Tumbleweed:(pts/3) [1:56am]> qdbus CORRECT>gdbus (y|n|e|a)? no qdbus: Command not found. [/home/jonzn4suse] jonzn4suse@ZBook-17-G2-Tumbleweed:(pts/3) [1:56am]> ps aux | grep dbus message+ 791 0.0 0.0 9644 6284 ? Ss Mar23 0:12 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only jonzn4s+ 1685 0.0 0.0 9528 5512 ? Ss Mar23 0:08 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only jonzn4s+ 1862 0.0 0.0 228512 24612 ? Sl Mar23 0:01 /usr/bin/X11/gmenudbusmenuproxy root 11895 0.0 0.0 8072 1720 ? S Mar24 0:00 dbus-launch --autolaunch 1da9c9315b504f5dbd19403aa6edd7ef --binary-syntax --close-stderr root 11896 0.0 0.0 7984 1876 ? Ss Mar24 0:00 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session root 14875 0.0 0.0 6220 784 pts/3 S+ 01:57 0:00 grep dbus
Just rebooted after 1300+ updates and the widgets are working minus Network speed. jonzn4suse@ZBook-17-G2-Tumbleweed:(pts/4) [2:37am]> ps aux | grep dbus message+ 802 0.2 0.0 10436 6408 ? Ss 02:34 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only jonzn4s+ 2763 0.1 0.0 9040 5376 ? Ss 02:34 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only jonzn4s+ 2937 0.0 0.0 228348 24216 ? Sl 02:34 0:00 /usr/bin/X11/gmenudbusmenuproxy root 6843 0.0 0.0 6220 712 pts/4 S+ 02:37 0:00 grep dbus
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
*** This bug has been marked as a duplicate of bug 434286 ***