[Bug 172935] apport-checkreports crashed with SIGSEGV while booting the Gutsy LiveCD
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:999:286643:2007-11-29 23:06:00.696566316 +:2007-11-29 23:05:52.69211 +:/var/crash/_usr_share_apport_apport-checkreports.999.crash Date: Thu Nov 29 23:05:48 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/share/apport/apport-checkreports InterpreterPath: /usr/bin/python2.5 NonfreeKernelModules: cdrom Package: apport 0.98 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/apport/apport-checkreports ProcCwd: /home/ubuntu ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: apport StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: apport-checkreports crashed with SIGSEGV Uname: Linux ubuntu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash -- apport-checkreports crashed with SIGSEGV while booting the Gutsy LiveCD https://bugs.launchpad.net/bugs/172935 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172935] Re: apport-checkreports crashed with SIGSEGV while booting the Gutsy LiveCD
** 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 added: "Disassembly.txt" http://launchpadlibrarian.net/10661311/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/10661312/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/10661313/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/10661314/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/10661315/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/10661316/ThreadStacktrace.txt -- apport-checkreports crashed with SIGSEGV while booting the Gutsy LiveCD https://bugs.launchpad.net/bugs/172935 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67487] Re: Install 6:10 Failure: Black screen at Live Desktop Stage
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 installing and switching to 'fglrx' works fine. As far as I can see this points pretty strongly to the 'ati' driver currently not working with a bunch of Radeon cards out in the wild. -- Install 6:10 Failure: Black screen at Live Desktop Stage https://launchpad.net/bugs/67487 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84718] Re: gdm session may fail if loging in immediately after a boot
*** 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, although avahi-deamon appears not to be running before the dbus restart, in case thats relevant. I'm running feisty x64 which showing the problem duel booted with edgy x32 which doesn't. Am I describing a separate problem? any logs / information I can provide that would be useful? -- gdm session may fail if loging in immediately after a boot https://launchpad.net/bugs/84718 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81670] Re: failed to initialize HAL : gdm init script priority should be at least equal to dbus one
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 /etc/init.d/dbus restart Dunno if it helps any, but when doing that I notice that avahi-daemon appears not to be running before the dbus restart but happily starts when restarting dbus. -- failed to initialize HAL : gdm init script priority should be at least equal to dbus one https://launchpad.net/bugs/81670 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 81670] Re: failed to initialize HAL : gdm init script priority should be at least equal to dbus one
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 /etc/init.d/dbus restart Dunno if it helps any, but when doing that I notice that avahi-daemon appears not to be running before the dbus restart but happily starts when restarting dbus. -- failed to initialize HAL : gdm init script priority should be at least equal to dbus one https://launchpad.net/bugs/81670 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
