Bug 423558

Summary: System tray has no items after update to 5.19.1
Product: [Plasma] plasmashell Reporter: Jeroen <jrforum>
Component: System Tray widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: materka, nate
Priority: NOR    
Version First Reported In: 5.19.2   
Target Milestone: 1.0   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Contains files for debugging: plasmashell replace nohup, screenshot of system tray, plasmoidviewer systemtray, plasma-org.kde.plasma.desktop-appletsrc
plasmoidviewer org.kde.plasma.systemtray
nohub QT_LOGGING_RULES

Description Jeroen 2020-06-26 19:49:51 UTC
Created attachment 129707 [details]
Contains files for debugging: plasmashell replace nohup, screenshot of system tray, plasmoidviewer systemtray, plasma-org.kde.plasma.desktop-appletsrc

SUMMARY
My systray is completely broken, no items are available at all. Also those pop-ups I usually get for media controls (for example when I connect my bluetooth speakers you get a pop-up) are completely gone. I have attempted various manual changes to the plasma-org.kde.plasma.desktop-appletsrc and while I was able to remove some widgets that even after removing were still present by deleting the configurations from this file, it had no effect on my systray at all. After a desparate attempt to fix this by deleting the whole .config and .cache folders, I still have no systay but I cannot change my background anymore either. When I right-click on the desktop and select "Configure Desktop...". It throws an error saying "Layout changes must be applied before ...". The menu is empty and apply now does nothing. Everythis is grayed out. Also my keyboard shortcuts are no longer working.

Creating a new user via the system settings only copies over files from /etc/skel to the new user, it does not setup plasma (another bug?). Logging in anyway gives me an empty desktop with a default background and no panel / widgets / icons whatsoever. Creating the systray widget on the desktop gives me and empty box with no systray items. Creating a new user seems to be broken as well it seems, but that's a different issue.

I didn't install any additional plasmoids, my . I do have latte-dock. Removing it has no effect.

Updating to 5.19.2 doesn't solve my issue.

I was advised to no longer use bug 423107 but to create a new one.


STEPS TO REPRODUCE
1. Update to 5.19.1
2. Reboot
2. All plasma systray items are gone, my own like transgui and keepass are still there
3. Reboot
4. All systray items are gone

OBSERVED RESULT
No Items in system tray

EXPECTED RESULT
Items in system tray

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon 5.19
(available in About System)
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
Comment 1 Konrad Materka 2020-06-29 17:37:32 UTC
(In reply to Jeroen from comment #0)
> Creating a new user via the system settings only copies over files from
> /etc/skel to the new user, it does not setup plasma (another bug?). Logging
> in anyway gives me an empty desktop with a default background and no panel /
> widgets / icons whatsoever. Creating the systray widget on the desktop gives
> me and empty box with no systray items. Creating a new user seems to be
> broken as well it seems, but that's a different issue.

Something is really, really bad with your system. I just checked, creating new user works as expected, a logged in, then new/default Plasma config was created with default panel and wallpaper. I'm using the same distribution (KDE Neon 5.19).

Maybe something is not correctly updated? Please run:
sudo apt update
sudo apt full-upgrade

I have no idea what can be wrong.
Comment 2 Jeroen 2020-06-30 11:53:20 UTC
Hi Konrad,

Thanks for the reply. My system is fully updated with no broken packages. I did try a reïnstall of all KDE package with the following commands:

find /var/cache/apt/archives/ -name "*5.19.2*" | xargs sudo dpkg -i --force-overwrite --refuse-downgrade
find /var/cache/apt/archives/ -name "*5.71.0*" | xargs sudo dpkg -i --force-overwrite --refuse-downgrade
find /var/cache/apt/archives/ -name "*5.14.2*" | xargs sudo dpkg -i --force-overwrite --refuse-downgrade

This made no difference, unfortunately. Deleting ~/.cache and ~/.config completely make no difference either. Do you have any clue whatsoever where I should be looking for the problem?

Jeroen
Comment 3 Konrad Materka 2020-06-30 12:15:12 UTC
I found some errors in plasmoidviewer_systemtray, like:
QIODevice::read (KCompressionDevice): device not open
and series of 
"Cannot read property 'xxxx' of null" - that should not happen.

I need more detialed logs, can you run this?
QT_LOGGING_RULES="*=true" nohup plasmoidviewer --applet org.kde.plasma.systemtray
Comment 4 Jeroen 2020-06-30 12:18:47 UTC
Created attachment 129791 [details]
plasmoidviewer org.kde.plasma.systemtray

Here's the output.
Comment 5 Konrad Materka 2020-07-07 15:17:34 UTC
(In reply to Jeroen from comment #4)
> Created attachment 129791 [details]
> plasmoidviewer org.kde.plasma.systemtray
> 
> Here's the output.

Did you run it with: QT_LOGGING_RULES="*=true"
You can firstly run:
export QT_LOGGING_RULES="*=true"
then:
nohup plasmoidviewer --applet org.kde.plasma.systemtray

Output should be in nohup.out file
Comment 6 Jeroen 2020-07-07 19:09:27 UTC
Created attachment 129964 [details]
nohub QT_LOGGING_RULES

(In reply to Konrad Materka from comment #5)
> (In reply to Jeroen from comment #4)
> > Created attachment 129791 [details]
> > plasmoidviewer org.kde.plasma.systemtray
> > 
> > Here's the output.
> 
> Did you run it with: QT_LOGGING_RULES="*=true"
> You can firstly run:
> export QT_LOGGING_RULES="*=true"
> then:
> nohup plasmoidviewer --applet org.kde.plasma.systemtray
> 
> Output should be in nohup.out file

I did run it with that QT rule, but with the export the output is different. Please see attachment. The file was to big (8,8Mb) so I compressed it.
Comment 7 Konrad Materka 2020-07-08 11:11:49 UTC
I found suspicious file:
/usr/share/plasma/plasmoids/kpluginindex.json

Remove or move it somewhere else and check again.

Did you run Plasma as root?

Probably this is duplicate of Bug 389297
Comment 8 Jeroen 2020-07-08 11:46:56 UTC
(In reply to Konrad Materka from comment #7)
> I found suspicious file:
> /usr/share/plasma/plasmoids/kpluginindex.json
> 
> Remove or move it somewhere else and check again.
> 
> Did you run Plasma as root?
> 
> Probably this is duplicate of Bug 389297

After moving this file to .bak, my systray is back again.

I have never run plasma as root, this happened after the update from 5.19.0 to 5.19.1. Maybe an issue with the .deb packages?

I cannot thank you enough for helping me, you really saved me! Thank you!
Comment 9 Konrad Materka 2020-07-08 14:36:29 UTC
Good to know it helped.

Unfortunately I don't know what caused it - was it broken package or something else. I have the same distribution and it works correctly.

If you want you can investigate further:
* This will show if file belongs to any installed deb package (probably not):
dpkg -S /usr/share/plasma/plasmoids/kpluginindex.json
* Was the file created recently or long time ago?
* Is it in compressed format or plain JSON text? Probably a text, which suggests it is a very old, not it is compressed.
* What are the privileges to the file. Is it root:root 644 (-rw-r--r--)?

Probably we won't know but it is worth to check, maybe someone else will stumble on this bug with an idea.
Comment 10 Jeroen 2020-07-08 14:55:27 UTC
(In reply to Konrad Materka from comment #9)
> Good to know it helped.
> 
> Unfortunately I don't know what caused it - was it broken package or
> something else. I have the same distribution and it works correctly.
> 
> If you want you can investigate further:
> * This will show if file belongs to any installed deb package (probably not):
> dpkg -S /usr/share/plasma/plasmoids/kpluginindex.json
> * Was the file created recently or long time ago?
> * Is it in compressed format or plain JSON text? Probably a text, which
> suggests it is a very old, not it is compressed.
> * What are the privileges to the file. Is it root:root 644 (-rw-r--r--)?
> 
> Probably we won't know but it is worth to check, maybe someone else will
> stumble on this bug with an idea.

After moving the file to .bak fixed the issue, I removed it. I do remember the file command saying it was a bzip2 compressed file and owned by root. But that's all I have for you.