** Description changed: Binary package hint: gnome-settings-daemon This crash with what appears to be a corrupt stack trace occurs most of - the time shortly after starting unity-2d sessions on Oneiric daily- - lives. This particular instance of the crash occurred on a custom CD I - created from the 20110620 daily-live for the purpose of investigating a - different (probably unrelated) bug, with all packages brought up to date - (therefore, this CD is probably quite similar to the forthcoming - 20110621 daily-live). I suspect this will turn out the same as two - previous occurrences (invalid bug 796465 and invalid bug 798722). If so, - then I'll try to obtain a backtrace manually and/or attempt to produce - it on a custom daily-live with debug symbols installed. + the time shortly after starting initial unity-2d sessions after booting + Oneiric daily-lives. This particular instance of the crash occurred on a + custom CD I created from the 20110620 daily-live for the purpose of + investigating a different (probably unrelated) bug, with all packages + brought up to date (therefore, this CD is probably quite similar to the + forthcoming 20110621 daily-live). I suspect this will turn out the same + as two previous occurrences (invalid bug 796465 and invalid bug 798722). + If so, then I'll try to obtain a backtrace manually and/or attempt to + produce it on a custom daily-live with debug symbols installed. - This might be bug 788710. The crash in bug 788710 occurs on the same - machine if I log out and back in (and this crash does not). I'm not sure - what would cause the stack to be corrupt only for the first login, - though. + UPDATE: While I had previously believed this might be bug 788710, I no + longer believe that's likely. I had thought that bug 788710 occurred on + the same machine when logging back in (after logging out of the original + session in which this bug occurred). But I have since determined (on the + 20110621 daily-live) that bug 788710 occurs on logout, not login. Since + this bug occurs at or soon after login without any logouts having + occurred since boot, and it's only major similarity to bug 788710 is + that they are both SIGSEGV's in gnome-settings-daemon, there's no reason + to think they are the same bug. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-settings-daemon 3.0.2-1ubuntu3 ProcVersionSignature: Ubuntu 3.0-1.2-generic 3.0.0-rc3 Uname: Linux 3.0-1-generic i686 Architecture: i386 Date: Tue Jun 21 07:50:04 2011 Disassembly: => 0x7cc5a70: Cannot access memory at address 0x7cc5a70 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110620) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANGUAGE= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7cc5a70: Cannot access memory at address 0x7cc5a70 PC (0x07cc5a70) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon Stacktrace: #0 0x07cc5a70 in ?? () No symbol table info available. Cannot access memory at address 0xbfd2797c StacktraceTop: ?? () Title: gnome-settings-daemon crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/800065 Title: gnome-settings-daemon crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/800065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
