Bug 19090 - ksmserver crashes, causing issues loading KWin and Plasma
Summary: ksmserver crashes, causing issues loading KWin and Plasma
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker critical
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
Whiteboard: NEEDINFO
Depends on:
Blocks: 17523
  Show dependency treegraph
Reported: 2016-07-29 16:31 CEST by David Walser
Modified: 2016-10-29 17:07 CEST (History)
3 users (show)

See Also:
Source RPM: plasma-workspace-5.7.2-3.mga6.src.rpm
Status comment: Needs testing with latest plasma updates that reached cauldron

backtrace (5.18 KB, text/plain)
2016-07-29 16:32 CEST, David Walser
some errors messages during startup MGA6-4.7.2 (118.45 KB, image/jpeg)
2016-08-25 19:53 CEST, j pierre LAJOIE
second pict with error (136.81 KB, image/jpeg)
2016-08-25 19:54 CEST, j pierre LAJOIE
bad authent. window (65.71 KB, image/jpeg)
2016-08-25 19:56 CEST, j pierre LAJOIE

Description David Walser 2016-07-29 16:31:10 CEST
ksmserver crashes when logging into Plasma
Comment 1 David Walser 2016-07-29 16:32:32 CEST
Created attachment 8285 [details]
David Walser 2016-07-29 16:32:39 CEST

Assignee: bugsquad => mageia

Comment 2 David Walser 2016-07-29 16:33:41 CEST
I also had some trouble with KCrash, because I clicked the button to save the backtrace and when it opened the file save dialog, it couldn't list any directory contents or save anything.  There was an error message about not connecting to D-Bus.
David Walser 2016-07-30 03:21:29 CEST

Blocks: (none) => 17523

Comment 3 j pierre LAJOIE 2016-08-05 19:33:04 CEST
for me it's impossible to pass the identification platform  .
i have the following message :
ksmserver PID 6898 segmentation fault (11) 
temps 05/08/2016 19:02;58
this is just after the last update of mageia6  yesterday .
 how can i do to start again ?

CC: (none) => arbedall

Comment 4 j pierre LAJOIE 2016-08-06 16:57:56 CEST
after today update it's ok again .....
Comment 5 j pierre LAJOIE 2016-08-06 17:25:01 CEST
but i still have two   minors  quirks :
-1 : when starting the following message:
kaslr disabled : not on cmd line (hibernation selected) 
i don't know what it's means ?
-2 : the US flag on identification platform (before it was the french flag)
Comment 6 j pierre LAJOIE 2016-08-07 12:01:37 CEST
i have again ksmserver error !!

1-i start my computer
2-i choose last mageia6 kernel 4.7.0 desktop-2.mga6
3-i enter my password in identify window
4- i have a black screen and a window message : could not start ksmserver, Check your installation. OK ?

5 after a click on ok  , 2 cases possible :
 a) mageia start 
 b) mageia stop with  error : no system tray detected on this system 
unable to start , exiting
OK ?
Comment 7 Nicolas Lécureuil 2016-08-07 12:35:57 CEST
can you install debuginfo packages and report this bug upstream please ?
Morgan Leijström 2016-08-10 18:08:13 CEST

CC: (none) => fri

Comment 8 David Walser 2016-08-12 18:30:23 CEST
It looks like there's maybe a race condition too when logging in to Plasma.

Sometimes I immediately see a "xmessage" dialog saying it couldn't start ksmserver, sometimes I see that after the splash, sometimes I don't see that but after the splash fades I get a black screen with no desktop, sometimes I get a KDE crash dialog for ksmserver, and sometimes everything works fine.
Comment 9 j pierre LAJOIE 2016-08-13 19:48:29 CEST
since the last updates of plasma , for me everything works correctly and i also start with  the new mageia screen ;=)
Samuel Verschelde 2016-08-25 16:25:19 CEST

Assignee: mageia => kde

Comment 10 j pierre LAJOIE 2016-08-25 19:10:06 CEST
actually i have with grub2 asus card UEFI
il i chose windows 10 =in all c
mga6  4.6.3 ok
mga6  4.7.2 => crash
mga6  4.7.0 => crash

sometimes i have a  screen with tree ???
sometimes a black screen 
sometimes a message asking video parameters but anyone works
sometimes i have the autentification window   with US flag on down right corner  but i cannot enter nothing!
but  if i chose 4.6.3 or 4.7.0 i have the good auth windows and MGA6 start .
Comment 11 j pierre LAJOIE 2016-08-25 19:11:37 CEST
i was saying that in all cases if i select win10 in grub i have a black screen .
Comment 12 j pierre LAJOIE 2016-08-25 19:46:55 CEST
(In reply to Nicolas Lécureuil from comment #7)
> can you install debuginfo packages and report this bug upstream please ?

please what's name and where are thoses packages ?
Comment 13 j pierre LAJOIE 2016-08-25 19:53:05 CEST
Created attachment 8367 [details]
some errors messages during startup MGA6-4.7.2
Comment 14 j pierre LAJOIE 2016-08-25 19:54:00 CEST
Created attachment 8368 [details]
second pict with error
Comment 15 j pierre LAJOIE 2016-08-25 19:56:23 CEST
Created attachment 8369 [details]
bad authent. window

from this time :no keybord, no mouse, nothing is possible.
Comment 16 David Walser 2016-09-07 16:29:25 CEST
There are some comments on this bug that aren't relevant to what this actual bug is about (ksmserver crashing or otherwise not starting correctly).

This may be related to, or even the cause of, Bug 19294.

We'll have to see if it persists with the latest Plasma updates pushed to Cauldron.

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

Samuel Verschelde 2016-09-12 16:20:16 CEST

Summary: ksmserver crashes => ksmserver crashes, causing issues loading KWin and Plasma

Samuel Verschelde 2016-09-12 16:20:59 CEST

Status comment: (none) => Needs testing with latest plasma updates that reached cauldron

Comment 17 Rémi Verschelde 2016-10-18 10:29:44 CEST
Is this bug still valid? I'm using plasma daily and haven't had segfaults recently.

Whiteboard: (none) => NEEDINFO

Comment 18 David Walser 2016-10-18 12:17:15 CEST
Hard to say.  I've only definitively seen the issue on a physical machine that I no longer have access to.
Comment 19 Samuel Verschelde 2016-10-18 12:19:15 CEST
(In reply to David Walser from comment #18)
> Hard to say.  I've only definitively seen the issue on a physical machine
> that I no longer have access to.

Then I think we can close it and consider that if it's going to be a blocking bug we'll see new bug reports when Stabilization Snapshot 2 is released. Since we can't debug it I think it's the most sensible approach.
Comment 20 Nicolas Lécureuil 2016-10-29 17:07:24 CEST
closnig for now.

CC: (none) => mageia
Resolution: (none) => FIXED

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