Activity log for bug #792999

Date Who What changed Old value New value Message
2011-06-05 03:22:18 Eliah Kagan bug added bug
2011-06-05 03:22:57 Eliah Kagan visibility private public
2011-06-05 03:26:34 Eliah Kagan description 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). 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: 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). 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:
2011-06-05 03:28:21 Eliah Kagan description 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). 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: 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. 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:
2011-06-05 03:28:35 Eliah Kagan description 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. 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: 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). 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:
2011-06-10 08:04:31 Jean-Baptiste Lallement metacity (Ubuntu): importance Undecided Medium
2011-06-10 08:04:31 Jean-Baptiste Lallement metacity (Ubuntu): status New Confirmed
2011-06-16 10:09:16 Apport retracing service bug added subscriber Crash bug triagers for Ubuntu packages
2011-06-16 10:09:18 Apport retracing service attachment removed CoreDump.gz https://bugs.launchpad.net/bugs/792999/+attachment/2155315/+files/CoreDump.gz
2011-06-16 10:09:19 Apport retracing service attachment removed Dependencies.txt https://bugs.launchpad.net/bugs/792999/+attachment/2155316/+files/Dependencies.txt
2011-06-16 10:09:19 Apport retracing service attachment removed Disassembly.txt https://bugs.launchpad.net/bugs/792999/+attachment/2155317/+files/Disassembly.txt
2011-06-16 10:09:20 Apport retracing service attachment removed ProcMaps.txt https://bugs.launchpad.net/bugs/792999/+attachment/2155318/+files/ProcMaps.txt
2011-06-16 10:09:21 Apport retracing service attachment removed ProcStatus.txt https://bugs.launchpad.net/bugs/792999/+attachment/2155319/+files/ProcStatus.txt
2011-06-16 10:09:22 Apport retracing service attachment removed Registers.txt https://bugs.launchpad.net/bugs/792999/+attachment/2155320/+files/Registers.txt
2011-06-16 10:09:23 Apport retracing service attachment removed Stacktrace.txt https://bugs.launchpad.net/bugs/792999/+attachment/2155321/+files/Stacktrace.txt
2011-06-16 10:09:23 Apport retracing service attachment removed ThreadStacktrace.txt https://bugs.launchpad.net/bugs/792999/+attachment/2155322/+files/ThreadStacktrace.txt
2011-06-16 10:09:25 Apport retracing service marked as duplicate 793981
2011-06-16 10:09:28 Apport retracing service tags apport-crash i386 need-i386-retrace oneiric unity-2d apport-crash i386 oneiric unity-2d
2011-06-20 07:31:09 Eliah Kagan changed duplicate marker 793981 797078