Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#33426 - Xserver fails to start in some boots

Attached to Project: Arch Linux
Opened by Amitav (amitavmohanty01) - Thursday, 17 January 2013, 13:57 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 06 May 2013, 17:38 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After some boots, the X server fails to start. I get the following messages shown as errors in journalctl -b

kdm[347]: X server startup timeout, terminating
kdm[347]: X server for display :0 cannot be started, session disabled
.
.
pam_ck_connector(login:session): process already registered with ConsoleKit

Additional info:
* package version(s)
kdebase-workspace 4.9.5-2
systemd 197-4

* config and/or log files etc.
please find attached
   boot.log (90.5 KiB)
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Monday, 06 May 2013, 17:38 GMT
Reason for closing:  No response
Comment by Jan de Groot (JGC) - Friday, 18 January 2013, 11:26 GMT
Without Xorg logs we can't see anything here.

Also note you're using the binary nvidia driver, so we probably can't fix it anyways in case it's a crash in the nvidia driver itself.
Comment by Amitav (amitavmohanty01) - Friday, 18 January 2013, 12:52 GMT
I was thinking there might not be any logs written to Xorg.0.log because it said X server start-up timed out. I thought Xorg.0.log would just be older logs. Will check it next time and append a sample.

About the binary nvidia driver issue, well I am aware that we can't fix it; but lets first root the issue to it. :)
Comment by Amitav (amitavmohanty01) - Sunday, 20 January 2013, 07:51 GMT
Please find attached the Xorg.0.log after X server failed to start. I hope this confirms the issue.
   xorg.log (23.6 KiB)
Comment by Daniel Wallace (gtmanfred) - Sunday, 20 January 2013, 07:54 GMT
That logs says it started perfectly fine and closed because it had nothing else to start

[ 117.785] Server terminated successfully (0). Closing log file.
Comment by Amitav (amitavmohanty01) - Sunday, 20 January 2013, 08:02 GMT
There are messages about unloadable modules. I don't understand why the modules turn out to be unloadable in some boots but work fine in other boots.
Comment by Amitav (amitavmohanty01) - Wednesday, 23 January 2013, 07:50 GMT
If I restart kdm using the following command, it starts fine.

systemctl restart kdm

I think it might be so happening that kdm starts before X server when it fails.

Loading...