** Visibility changed to: Public ** Description changed:
Binary package hint: metacity On an Oneiric i386 system in a unity-2d session, metacity 1:2.34.0-0ubuntu1 crashed with SIGABRT in __kernel_vsyscall(). This appeared to occur immediately after running a command with sudo 1.7.4p6-1ubuntu1 for the first time since rebooting. The crash occurred while I was being prompted for my password, so I don't believe it's caused by the specific command I ran with sudo. I have not been able to reproduce this crash. I have tried running a command with sudo again shortly thereafter, then again after running "sudo -k", and then again after running "sudo -K", then again in a separate Terminal window, but the crash did not recur. It's quite possible that the crash occurring right after I used sudo was a coincidence, and that there is no causal relationship between sudo and this metacity crash. About twenty seconds after this crash occurred, the recurring crash documented in bug 788714 happened. I have no particular reason to think that crash is related either, though it's notable that they're both SIGABRT's. Finally, it is worth noting that this crash looks a lot like the old, unresolved crash from Lucid Beta 1 described in bug 543193. Perhaps this should be marked as a duplicate of that bug (or that bug marked a - duplicate of this one). + duplicate of this one). Or perhaps not--the backtraces don't look + particularly similar (though it will be easier to tell if and when an + automatic retrace takes place for this bug). ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: metacity 1:2.34.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic i686 Architecture: i386 Date: Sat Jun 4 22:57:23 2011 ExecutablePath: /usr/bin/metacity InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110604) ProcCmdline: metacity ProcEnviron: - LANG=en_US.UTF-8 - SHELL=/bin/false - PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/false + PATH=(custom, no user) Signal: 6 SourcePackage: metacity StacktraceTop: - __kernel_vsyscall () - raise () from /lib/i386-linux-gnu/libc.so.6 - abort () from /lib/i386-linux-gnu/libc.so.6 - ?? () - ?? () + __kernel_vsyscall () + raise () from /lib/i386-linux-gnu/libc.so.6 + abort () from /lib/i386-linux-gnu/libc.so.6 + ?? () + ?? () Title: metacity crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Description changed: Binary package hint: metacity On an Oneiric i386 system in a unity-2d session, metacity 1:2.34.0-0ubuntu1 crashed with SIGABRT in __kernel_vsyscall(). This appeared to occur immediately after running a command with sudo 1.7.4p6-1ubuntu1 for the first time since rebooting. The crash occurred while I was being prompted for my password, so I don't believe it's caused by the specific command I ran with sudo. I have not been able to reproduce this crash. I have tried running a command with sudo again shortly thereafter, then again after running "sudo -k", and then again after running "sudo -K", then again in a separate Terminal window, but the crash did not recur. It's quite possible that the crash occurring right after I used sudo was a coincidence, and that there is no causal relationship between sudo and this metacity crash. About twenty seconds after this crash occurred, the recurring crash documented in bug 788714 happened. I have no particular reason to think that crash is related either, though it's notable that they're both - SIGABRT's. + SIGABRT's in the same function. Finally, it is worth noting that this crash looks a lot like the old, unresolved crash from Lucid Beta 1 described in bug 543193. Perhaps this should be marked as a duplicate of that bug (or that bug marked a duplicate of this one). Or perhaps not--the backtraces don't look particularly similar (though it will be easier to tell if and when an automatic retrace takes place for this bug). ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: metacity 1:2.34.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic i686 Architecture: i386 Date: Sat Jun 4 22:57:23 2011 ExecutablePath: /usr/bin/metacity InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110604) ProcCmdline: metacity ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/false PATH=(custom, no user) Signal: 6 SourcePackage: metacity StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () ?? () Title: metacity crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Description changed: Binary package hint: metacity On an Oneiric i386 system in a unity-2d session, metacity 1:2.34.0-0ubuntu1 crashed with SIGABRT in __kernel_vsyscall(). This appeared to occur immediately after running a command with sudo 1.7.4p6-1ubuntu1 for the first time since rebooting. The crash occurred while I was being prompted for my password, so I don't believe it's caused by the specific command I ran with sudo. I have not been able to reproduce this crash. I have tried running a command with sudo again shortly thereafter, then again after running "sudo -k", and then again after running "sudo -K", then again in a separate Terminal window, but the crash did not recur. It's quite possible that the crash occurring right after I used sudo was a coincidence, and that there is no causal relationship between sudo and this metacity crash. About twenty seconds after this crash occurred, the recurring crash documented in bug 788714 happened. I have no particular reason to think that crash is related either, though it's notable that they're both - SIGABRT's in the same function. + SIGABRT's. Finally, it is worth noting that this crash looks a lot like the old, unresolved crash from Lucid Beta 1 described in bug 543193. Perhaps this should be marked as a duplicate of that bug (or that bug marked a duplicate of this one). Or perhaps not--the backtraces don't look particularly similar (though it will be easier to tell if and when an automatic retrace takes place for this bug). ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: metacity 1:2.34.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39 Uname: Linux 2.6.39-3-generic i686 Architecture: i386 Date: Sat Jun 4 22:57:23 2011 ExecutablePath: /usr/bin/metacity InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110604) ProcCmdline: metacity ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/false PATH=(custom, no user) Signal: 6 SourcePackage: metacity StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () ?? () Title: metacity crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792999 Title: metacity crashed with SIGABRT in __kernel_vsyscall() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
