Bug 396997 - Plasma Crash after/during unattended 'sleep' period mostly also Syslog 22.2mb
Summary: Plasma Crash after/during unattended 'sleep' period mostly also Syslog 22.2mb
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.12.6
Platform: Kubuntu Linux
: NOR crash
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-07-30 22:10 UTC by pmb
Modified: 2018-10-28 03:14 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 pmb 2018-07-30 22:10:27 UTC
Loaded Kubuntu 18.04.1 3 times from 2 downloads - same outcome - crash when asleep(mostly).

Specifically:
When I leave the machine, the screensaver starts, the screensaver times out, the display goes dark - I move the mouse - the pointer appears but the plasma desktop does not activate. I tried it minus xscreensaver and the same results occurred. It has occurred when the xscreensaver is functioning. When I logout and return the plasma desktop reappears.

During this time the ssd light is flashing at a feverish pitch.

I Ctrl-Alt-Del and the machine restarts but the next bootup stops for 1 minute and 30 seconds with the message, "A start job is running for dev-disk by..." - again the ssd disk's light is flashing quickly.

The syslog is 22.2 mb in size with the following repeated with different components,
"Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:sys: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:devices: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:pci0000:00: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:0000:00:15.2: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:0000:0b:00.0: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:usb10: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:sys: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:devices: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:pci0000:00: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:0000:00:15.2: Ignored relative path
Jul 30 14:56:04 ????machine ureadahead[355]: ureadahead:0000:0b:00.0: Ignored relative path"

also

"Jul 30 17:25:32 ????machine lircd[887]: lircd-0.10.0[887]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
Jul 30 17:25:32 ????machine lircd-0.10.0[887]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
Jul 30 17:25:33 ????machine lircd[887]: lircd-0.10.0[887]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
Jul 30 17:25:33 ????machine lircd-0.10.0[887]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*
Jul 30 17:25:34 ????machine lircd[887]: lircd-0.10.0[887]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]*"

To confuse this issue for me I loaded Kubuntu as UEFI. I followed some rules and I created a directory as /boot/efi as Faty32. I think I did everything right.

I know nothing about uefi so please tell me what you need.

The 18.04.1 is totally unusable. I am using my old 16.04.3 on another ssd.

Hope this helps.
Comment 1 Nate Graham 2018-08-09 20:02:46 UTC
I;m sorry to hear about this issue. We need a crash log with a backtrace in order to figure out what might be going on. See https://community.kde.org/Get_Involved/Bug_Reporting#Crash_reports_must_include_backtraces

Please provide one if you can.
Comment 2 Andrew Crouthamel 2018-09-28 03:08:02 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 set the bug status 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 3 Andrew Crouthamel 2018-10-28 03:14:21 UTC
Dear Bug Submitter,

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!