[Bug 172935] apport-checkreports crashed with SIGSEGV while booting the Gutsy LiveCD

2007-11-29 Thread Rob Oxspring
Public bug reported: Binary package hint: apport All I did was boot the Gutsy i386 Live CD ProblemType: Crash Architecture: i386 CrashReports: 600:999:999:1196313:2007-11-29 23:05:38.684869000 +:2007-11-29 23:05:39.684869000 +:/var/crash/_usr_bin_gnome-power-manager.999.crash 0:999:99

[Bug 172935] Re: apport-checkreports crashed with SIGSEGV while booting the Gutsy LiveCD

2007-11-29 Thread Rob Oxspring
** Attachment added: "ApportLog.txt" http://launchpadlibrarian.net/10661308/ApportLog.txt ** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/10661309/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/10661310/Dependencies.txt ** Attachment

[Bug 67487] Re: Install 6:10 Failure: Black screen at Live Desktop Stage

2006-11-01 Thread Rob Oxspring
I found exactly the same problem with the live CD (ATI Radeon 9200, Athlon64, Edgy x86_64) but decided I'd try installing via the alternate CD's text mode anyway and saw exactly the same again. I've managed to get in to recovery mode via grub and changing the graphics driver to use 'vesa', or inst

[Bug 84718] Re: gdm session may fail if loging in immediately after a boot

2007-02-18 Thread Rob Oxspring
*** This bug is a duplicate of bug 81670 *** How long should I have to wait after the login prompt before logging in? I've tried waiting 60s but still get "Failed to initialize hal" dialog. For what its worth, I find that doing "sudo /etc/init.d/dbus restart" gets things working again for me, alth

[Bug 81670] Re: failed to initialize HAL : gdm init script priority should be at least equal to dbus one

2007-02-21 Thread Rob Oxspring
I have a duel boot setup between a 32bit edgy and a 64bit edgy > feisty upgrade. The feisty installation shows this issue repeatedly, I think this is only since the upgrade but I'm not certain of that. For what its worth I've found running the following gets things working again for me: sudo /et

[Bug 81670] Re: failed to initialize HAL : gdm init script priority should be at least equal to dbus one

2007-02-21 Thread Rob Oxspring
I have a duel boot setup between a 32bit edgy and a 64bit edgy > feisty upgrade. The feisty installation shows this issue repeatedly, I think this is only since the upgrade but I'm not certain of that. For what its worth I've found running the following gets things working again for me: sudo /et