Red Hat Bugzilla – Bug 823795
systemd-logind first start fails which causes plasma-desktop to crash if logging immediately after system starts up
Last modified: 2012-06-11 08:33:06 EDT
Created attachment 585948 [details]
plasma-desktop stack trace
Description of problem:
If I log in to KDE desktop immediately after system starts up, plasma-desktop crashes. Subsequent log ins don't cause the crash. Furthemore, if I wait some time after system start, then log to KDE desktop, the crash also does not occur.
Based on stack trace and /var/log/messages I suspect a problem with an interaction with NetworkManager. I am not sure which component is the cause of the crash: KDE or NetworkManager.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Log in to KDE desktop immediately after system starts up (the faster the better chance to reproduce the problem)
plasma-desktop doesn't crash
I am attaching plasma-desktop stack-trace and relevant information from /var/log/messages
Created attachment 585956 [details]
NetworkManager crash info from /var/log/messages
I attach relevant info from /var/log/messages about NetworkManager crash which occured at the same time as plasma-desktop crash.
I tried to install debug symbols for NetworkManager, but after that the crashes for NetworkManager weren't logged to /var/log/messages. plasma-desktop crashed as before, as explained in the report.
Both the crashes are inside D-Bus code, I wonder whether there's something wrong with D-Bus.
Is it possible that systemd doesn't start D-Bus fast enough or that systemd doesn't wait for D-Bus to be fully started before displaying login screen?
I have found out, that crash occurs when systemd-logind.service is in a failed state. The service always fails when it starts for the first time. Therefore I changed the description and component of the bug. I will attach systemd log files shortly.
Created attachment 586776 [details]
A copy of /var/log/messages
A full copy of /var/log/message from one boot
Created attachment 586777 [details]
dmesg with systemd debug logging
Created attachment 586778 [details]
Created attachment 586779 [details]
output of /bin/systemd --test --system --log-level=debug
This is an unusual error:
[ 22.913291] systemd: RequestName() failed: Access denied
Do you have the pristine file /etc/dbus-1/system.d/org.freedesktop.systemd1.conf or are there any modifications or a possible corruption?
I have the pristine file /etc/dbus-1/system.d/org.freedesktop.systemd1.conf. I have compared my file with the one from downloaded RPM package (systemd-37-19.fc16.x86_64.rpm) and the files are identical.
My guess is that some package installed a bogus D-Bus policy file which corrupts the whole boot.
Let's see what policy D-Bus files are there. Could you attach a tarball of everything in /etc/dbus-1/ ?
I have upgraded my Fedora installation in the meantime and the problem doesn't appear in Fedora 17. Therefore I think I should close the bug and mark it as next release.