Hardy 64bit freeze after "Running local boot scripts"

[shaikailash]

Hi, Yesterday I've installed Kubuntu Hardy 64bit on my Dell XPS M1530, using the RC version, live cd. I've done the updates released in these days, and everything works perfectly. But today I have a problem booting.

Kubuntu starts, I see the Kubuntu loading bar, but then appears the black screen with some :
Starting K display manager KDM [OK]
...
...
..
..
until this:
Running local boot scripts (/etc/rc.local) [OK]

Then nothing, everything remains the same.

At this point, if I press ctrl+alt+F1, F2 until F6, I can do a shell login, then write "startx" and the desktop loads well. But, obviously, this is a very bad problem and need to be fixed.

uname -a
Linux xxx-xxx 2.6.24-16-generic #1 x86_64 GNU/Linux

Ask me if you need other infos.
Thank you

[shaikailash (steve-doc-brown)]

any idea?? :( quite boring

[PJSingh5000 (pjsingh5000)]

I am experiencing the same problem with the 8.04 Release version of Hardy (KDE 3, x64). I do not experience this problem at initial boot up, but rather when I have logged out and am attempting log back in.

I am also using the fglrx driver for the ATI Radeon X1650 Pro.

I think this is a side-effect of bug Bug #198220, which is preventing people from logging out. In the rare cases that I am able to actually log out, I experience the problem described above when try to login again. The "XDM_AUTH_MASK" solution proposed in Bug #198220 did not help.

$ uname -a
Linux Computer-0070 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

I would be happy to provide any further information.

Thanks

[PJSingh5000 (pjsingh5000)]

Would someone suggest a way to capture debug output or log info. for a problem like this?

[Harald Sitter (apachelogger)]

This bug seriously needed half a year to end up here? I guess it is true what they say about bugs getting lost when not reported against a package directly ;-)

Is this still an issue with Kubuntu Intrepid?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!