Bug 9240

Summary:	Selecting "kscreen" rather than kded-randrmonitor caused long boot and shutdown delays
Product:	Mageia	Reporter:	Greg McGee <gjmcgee>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kscreen	CVE:
Status comment:

Description Greg McGee 2013-03-02 18:25:45 CET

Post MGA3b1 install, you must choose between kscreen and kded-randrmonitor.

If kscreen is selected, KDE startup & shutdown are VERY slow:

shutdown select shutdown>10 second, then a huge sync write ~10 more seconds after selecting reboot or whatever.

This behavior is only seen if kscreen is selected, did a new clean install to verify.

If kded-randrmonitor is selected (old default) it runs smooth as silk startup and shutdown are both ~20 seconds faster on same hardware/OS.

Comment 1 Greg McGee 2013-03-02 18:29:18 CET

for clarity--- the kscreen or kded-randrmonitor choice is presented on initial updates through the gui.

I strongly suggest "kded-randrmonitor", which is the default IIRC
(only tried kscreen to test it)

Greg McGee 2013-03-02 18:29:38 CET

Source RPM: (none) => kscreen

Comment 2 Manuel Hiebel 2013-03-16 16:14:59 CET

same with kde4.10.1 ?

Comment 3 Greg McGee 2013-03-16 20:31:24 CET

Have not tried it again with b3.

I suppose it's just simply a matter of removing kded-randrmonitor --nodeps and installing kscreen, but there may be a herd of dependancy issues, have not tried that yet.

Comment 4 Greg McGee 2013-03-16 22:13:35 CET

It was easier than I thought, simply urpmi kscreen and it removes the kded-randmonitor and deps and replaces it.

Issue appears to have resolved itself, no long pauses on boot or shutdown anymore.
Does seem to corrupt the kde bootsplash screen.

Comment 5 Nicolas Lécureuil 2013-03-16 22:59:47 CET

so we can close this bugreport ?

CC: (none) => nicolas.lecureuil

Comment 6 Greg McGee 2013-03-17 00:10:25 CET

Just tested it on a second machine, works now, so unless someone else has issues, I'd say it was fixed with latest KDE updates.

Comment 7 Nicolas Lécureuil 2013-03-17 00:13:26 CET

thank you so closing ( it works OK here )

Status: NEW => RESOLVED
Resolution: (none) => FIXED