Bug 21082 - Plasma shell occasionally fails to start on Live DVD
Summary: Plasma shell occasionally fails to start on Live DVD
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: High major
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
Keywords: FOR_ERRATA6
Depends on:
Reported: 2017-06-13 23:03 CEST by Martin Whitaker
Modified: 2017-06-20 21:48 CEST (History)
2 users (show)

See Also:
Source RPM:
Status comment:

System log from failing session (27.73 KB, application/gzip)
2017-06-13 23:03 CEST, Martin Whitaker

Description Martin Whitaker 2017-06-13 23:03:50 CEST
Created attachment 9407 [details]
System log from failing session

On booting from the Plasma Live DVD, after the initial Plasma startup splash sequence is displayed, the screen goes black and the Plasma desktop does not appear. MageiaWelcome is displayed, and is fully functional. Ctrl-Alt-L will bring up the lock screen, and from there a new session can be started that gives a working desktop. Unlocking the original session just returns you to the black screen.

This is fairly intermittent - maybe one time in ten.

Looking in the system log (attached), the failure looks to be here:

Jun 10 17:11:03 localhost ksmserver[2821]: ksmserver: Autostart 2 done
Jun 10 17:11:03 localhost ksmserver[2821]: ksmserver: IO error opening ICE Connection!
Jun 10 17:11:03 localhost ksmserver[2821]: ksmserver: autostart service ("/bin/plasmashell", "--shut-up") finished with exit code  13

I have only observed this in VirtualBox, but have no reason to believe it won't occur on real hardware too.
Comment 1 William Kenney 2017-06-13 23:34:45 CEST
I have resolved/moved: https://bugs.mageia.org/show_bug.cgi?id=20874
to this bug

CC: (none) => wilcal.int

Marja Van Waes 2017-06-14 00:51:05 CEST

Assignee: bugsquad => kde
CC: (none) => marja11

William Kenney 2017-06-20 19:48:15 CEST

Severity: normal => major
Priority: Normal => release_blocker

Comment 2 Marja Van Waes 2017-06-20 21:48:19 CEST
During council meeting tonight it was agreed to change this from a release blocker bug to a "for errata" bug and to suggest rebooting when someone hits it.

Keywords: (none) => FOR_ERRATA6
Priority: release_blocker => High

Note You need to log in before you can comment on or make changes to this bug.