Bug 287264

Summary:	KDE splash screen fails
Product:	[I don't know] kde	Reporter:	CS Wagner <cs>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DOWNSTREAM
Severity:	crash	CC:	cfeck
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description CS Wagner 2011-11-22 14:35:28 UTC

Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

After logging in, the splash screen loads the first three icons - ending with the globe. It fails to continue. There is no drive activity. There is no message in the logs. Eventually it shows a crash alert, but it cannot be filed because it requires a user/pass and the keyboard is unresponsive. I tried to copy/paste letters from the help text with the mouse, but there is no @ in the help text.

This happens in both KDE and KDE failsafe. It happens on all accounts (including root) and with a new account that has not .kde folder. So, it is not a simple plasma config error.

Reproducible: Always

Steps to Reproduce:
Attempt to login to KDE

Actual Results:  
KDE fails to load after showing the globe.

Expected Results:  
KDE should load.

This appears to be the result of one of the latest KDE library updates. It started after the latest yum update.

Comment 1 CS Wagner 2011-11-22 21:41:31 UTC

I have found an error in messages. I replaced the data that varies with a note about what is there, but left the same stuff indicated in each error intact:
 (date) localhost kernel: (a number) kded4[(an integer)]: segfault at c(a hex number) ip (a hex number) sp (a hex number) error 7 in ld-2.14.90.so[(a hex number)+21000]

So, I'm now searching to see if anyone else in the world has ever seen an error 7 in ld.

Comment 2 CS Wagner 2011-11-22 21:49:06 UTC

Preceding the kded4 segfault, I've found another segfault that always happens (and may cause the kded4 segfault):

 kernel: ... ksmserver[...]: segfault at c... op ... sp ... error 7 in ld-2.14.90.so[...+21000]

This tells me that this SHOULD be a plasma user configuration problem, but I get this with a new user with no .kde directory at all and I get it with root. So, it can't be a bad plasma config and it can't be a permission problem.

Comment 3 CS Wagner 2011-11-22 21:51:23 UTC

Finally - if this helps - the only odd thing I can find in the repeated attempts to start KDE is this:
 org.kde.powerdevil.backlightbelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.

Comment 4 Christoph Feck 2011-11-24 12:27:00 UTC

Do you use the NVIDIA binary drivers?

Comment 5 CS Wagner 2011-11-24 13:58:37 UTC

I do use nvidia drivers. However, this bug was not fixed with an update to those. It was fixed in the latest Fedora yum update, which included a lot of KDE packages.

Comment 6 Christoph Feck 2011-11-24 19:06:23 UTC

Thanks for the update.