Karmic boot scripts starting kdm twice during bootup

Bug #485033 reported by doctordruidphd
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

kUbuntu-9.10 64-bit, current updates

What I expect to happen: On bootup, seeing text and then greeting screen.

What is actually happening: During bootup, either from cold or restart, it appears that kdm is being started twice. It starts once before the video driver is loaded, producing an error screen saying the fonts aren't loaded, and the "low resolution" mode screen. Escaping out of these screens returns to the text, and then the regular greeter screen appears normally.
There is another related problem, in that the "rescue mode" is unusuable. Booting into rescue mode produces the menu. which is immediately overwritten with bootup text. Pressing Enter repeatedly produces an alternation between the "root@machine" prompt and the "Machine Login:" prompt, making it impossible to use the console.
I have disabled all kernel options such as vga= and splash, this does not help.
I have also discovered that after a "normal" boot, the usual bootup text and login prompt appears on CTRL-ALT-F1, F2 thru F6 are normal (login prompt only), on CTRL-ALT-F7 there is a second set of boot text, and the graphical screen is on CTRL-ALT-F8.
The problem does not appear to be with kdm, X or the NVIDIA drivers themselves, but with a script that is starting them twice.
This might also be a security problem, if two separate graphical logins are being started.

Tags: kdm startup
Dave Stirton (dwstirton)
affects: ubuntu → kdebase-workspace (Ubuntu)
Revision history for this message
doctordruidphd (doctordruidphd) wrote :

As an experiment I switched from kdm to gdm using dpkg-reconfigure gdm. The problem goes away when using gdm. Text behavior on tty1 and tty7 are normal; graphics comes up on tty7 as normal.

Revision history for this message
Pedro Rebelo de Andrade (pedrorandrade) wrote :

I had the same problem.

I solved it renaming '/etc/init/failsafe-x.conf' to '/etc/init/failsafe-x.conf-disable'
('sudo mv /etc/init/failsafe-x.conf /etc/init/failsafe-x.conf-disable')

Apparently there is some issues with the new 'start' scripts which, in my case surfaced after the upgrade from 9.04 to 9.10.

I don't know which package was the culprit for leaving the failsafe mode in init because the upgrade had issues with the proprietary nvidia driver and i had to reconfigure X for the nv driver, so I cannot tell when this specific issue started.

Changed in kdebase-workspace (Ubuntu):
status: New → Confirmed
Revision history for this message
doctordruidphd (doctordruidphd) wrote :

('sudo mv /etc/init/failsafe-x.conf /etc/init/failsafe-x.conf-disable')
This worked for my system. Thank You!

Revision history for this message
Joel Oliver (joelol75) wrote :

Another me-too, this one drove me nuts. I was getting the low-graphics menu with a failure to open /dev/fb0 which is odd since I'm using the radeon driver. Clicking anything in the low-graphics menu would result in kdm starting properly. I threw a sleep 15 into /etc/X11/Xsession to no avail but then I read this and it worked! Thanks Pedro. Also a Jaunty install (x86) upgraded to karmic.

Changed in kdebase-workspace (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.