Bug 424945

Summary:	Activities disappear
Product:	[Plasma] plasmashell	Reporter:	Peterson Silva <peterson.235>
Component:	Activities in general	Assignee:	Ivan Čukić <ivan.cukic>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	daniel.pflager, inglessi, ivan.cukic, jonzn4suse, nate, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.27.0
Target Milestone:	1.0
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	After reboot, widgets are dead Cannot input data for Memory Usage I can add another Memory Usage widget.

Description Peterson Silva 2020-08-02 21:20:39 UTC

I had 4 activities, with specific widgets in each. They all disappeared after a reboot. I logged in to a blank desktop with a default wallpaper and no widgets. Switching activities did nothing; the activity bar displayed no activities. They were still "there" if I went to activity settings, but I couldn't switch to any of them (if I created a new one, I could switch to it alone). I checked some config files and I also saw the 4 were still there, as described.

Logged out and logged in again, I could see the activities in the switcher now, but they were all the same: blank, with default wallpapers. I saved what I had written in each note plasmoid so that I could at least retain it but otherwise deleted everything and stopped using activities altogether, as I'm weary it might eat my notes up.  

I do not know how to reproduce it. I just rebooted the system and it all went to hell. Glad to help with any debugging if there is some sort of log I could paste here.

Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-42-generic
OS Type: 64-bit
Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor
Memory: 15,6 GiB

Comment 1 Daniel P Pflager 2021-09-25 17:59:59 UTC

I have experienced a similar behavior.

After a display mode resolution change, and a reboot, my Activity Manager contained no activities.  It was still as long as it would have been if the activities had been visible, which suggested they were still there somewhere.

I have NO virtual desktops configured.

I rely on having different desktop icons on each activity (each activity uses a different custom folder).


Running Plasma on Wayland
Operating System: openSUSE Leap 15.2
KDE Plasma Version: 5.18.6
KDE Frameworks Version: 5.71.0
Qt Version: 5.12.7
Kernel Version: 5.3.18-lp152.87-preempt
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz
Memory: 62.4 GiB of RAM

I am using both custom locations and the desktop in my activities.

Comment 2 jonzn4SUSE 2022-09-20 08:50:46 UTC

Created attachment 152249 [details]
After reboot, widgets are dead

I can put the data back in other widgets, but Memory Usage will not allow me to input anything.  I also cannot add the widget again.


Operating System: openSUSE Tumbleweed 20220918
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.5
Kernel Version: 5.19.8-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz
Memory: 125.2 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Product Name: HP ZBook 17 G6

Comment 3 jonzn4SUSE 2022-09-20 08:51:29 UTC

Created attachment 152250 [details]
Cannot input data for Memory Usage

Comment 4 jonzn4SUSE 2022-09-20 09:06:40 UTC

Created attachment 152251 [details]
I can add another Memory Usage widget.

Comment 5 jonzn4SUSE 2024-12-19 09:16:15 UTC

All has been well for me in Tumbleweed and Leap 15.6.  ;-))

Comment 6 Nate Graham 2025-05-07 19:03:02 UTC

Given the severity of the issue, I'm really sorry we were not able to get to this yet! Peterson, has this ever happened again since the first time? Thanks a lot!

Comment 7 Peterson Silva 2025-05-07 20:40:42 UTC

(In reply to Nate Graham from comment #6)
> Given the severity of the issue, I'm really sorry we were not able to get to
> this yet! Peterson, has this ever happened again since the first time?
> Thanks a lot!

Hi Nate. Unfortunately I stopped using Activities altogether after this, so I wouldn't know. I'm guessing that based on the most recent comment (by a previously affected user, no less), this could be closed.

Comment 8 Nate Graham 2025-05-07 20:44:51 UTC

Thanks for following up!