Bug 437232 - Activities and desktop configuration lost after rebooting
Summary: Activities and desktop configuration lost after rebooting
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 5.18.5
Platform: Kubuntu Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-17 06:32 UTC by Pascal Niklaus
Modified: 2021-07-04 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Niklaus 2021-05-17 06:32:45 UTC
SUMMARY

This is a problem that started to occur only recently. After rebooting, the activities I have defined (three of them) no longer appear (at least the activity pager widget is not there). Also, the desktop is plain black and no desktop widgets are present anymore. 

Logging out and in again at least helped for the pager to re-appear, but the desktop settings (e.g. background) were not restored. I needed to re-configure these.

STEPS TO REPRODUCE

This is difficult to tell, but the problem occurs with a certain regularity (but not always).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 20.04.2
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2021-05-17 13:02:33 UTC
Sounds like Plasma is crashing on login. Can you please get a backtrace of the crash? If DrKonqi didn't do so automatically, you may be able to find it using the command-line `coredumpctl` utility. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 2 Pascal Niklaus 2021-05-19 16:10:54 UTC
Ok, now it happened again, but I doubt that I see the crashes that caused the problem. In the morning, all was fine despite these dumps. Upon booting in the afternoon, all activities and desktop settings disappeared again. I wonder whether this is related to restoring open applications.

$ coredumpctl 
TIME                            PID   UID   GID SIG COREFILE  EXE
Wed 2021-05-19 08:03:48 CEST   1154   124   133  31 error     /lib/systemd/systemd-timesyncd
Wed 2021-05-19 08:03:48 CEST   1190   124   133  31 error     /lib/systemd/systemd-timesyncd
Wed 2021-05-19 08:03:48 CEST   1199   124   133  31 error     /lib/systemd/systemd-timesyncd
Wed 2021-05-19 08:03:48 CEST   1208   124   133  31 error     /lib/systemd/systemd-timesyncd
Wed 2021-05-19 08:03:48 CEST   1217   124   133  31 error     /lib/systemd/systemd-timesyncd
Wed 2021-05-19 17:44:30 CEST   1158   124   133  31 error     /lib/systemd/systemd-timesyncd
Wed 2021-05-19 17:44:30 CEST   1190   124   133  31 error     /lib/systemd/systemd-timesyncd
Wed 2021-05-19 17:44:30 CEST   1201   124   133  31 error     /lib/systemd/systemd-timesyncd
Wed 2021-05-19 17:44:30 CEST   1210   124   133  31 error     /lib/systemd/systemd-timesyncd
Wed 2021-05-19 17:44:30 CEST   1219   124   133  31 error     /lib/systemd/systemd-timesyncd

$ sudo coredumpctl gdb 1219
           PID: 1219 (systemd-timesyn)
           UID: 124 (systemd-timesync)
           GID: 133 (systemd-timesync)
        Signal: 31 (SYS)
     Timestamp: Wed 2021-05-19 17:44:30 CEST (17min ago)
  Command Line: /lib/systemd/systemd-timesyncd
    Executable: /lib/systemd/systemd-timesyncd
 Control Group: /system.slice/systemd-timesyncd.service
          Unit: systemd-timesyncd.service
         Slice: system.slice
       Boot ID: bb2da3ff86ca4d0e8e4e5ab4e4a7433a
    Machine ID: ee39478c6fbf4a679a3f0795d320f25c
      Hostname: xxxxxxxx
       Storage: /var/lib/systemd/coredump/core.systemd-timesyn.124.bb2da3ff86ca4d0e8e4e5ab4e4a7433a.1219.1621439070000000000000.lz4
       Message: Process 1219 (systemd-timesyn) of user 124 dumped core.
                
                Stack trace of thread 1219:
                #0  0x00000000f7f29e3b n/a (/lib/i386-linux-gnu/ld-2.31.so + 0x1be3b)
                #1  0x00000000f7f28855 n/a (/lib/i386-linux-gnu/ld-2.31.so + 0x1a855)
                #2  0x00000000f7f0ffc5 n/a (/lib/i386-linux-gnu/ld-2.31.so + 0x1fc5)
                #3  0x00000000f7f0f12b n/a (/lib/i386-linux-gnu/ld-2.31.so + 0x112b)

GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /lib/systemd/systemd-timesyncd...
(No debugging symbols found in /lib/systemd/systemd-timesyncd)
[New LWP 1219]
Core was generated by `/lib/systemd/systemd-timesyncd'.
Program terminated with signal SIGSYS, Bad system call.
#0  0xf7f29e3b in ?? ()
(gdb) bt
#0  0xf7f29e3b in ?? ()
#1  0x56627a10 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)
Comment 3 Bug Janitor Service 2021-06-03 04:33:34 UTC
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!
Comment 4 Pascal Niklaus 2021-06-04 05:37:23 UTC
The problem did not occur in the past 2 weeks so that I can't provide additional info. I will do so when I encounter this situation again.
Comment 5 Bug Janitor Service 2021-06-19 04:33:36 UTC
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!
Comment 6 Bug Janitor Service 2021-07-04 04:33:48 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!