gnome-panel crashed with SIGSEGV in g_signal_emit_valist()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-panel (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This afternoon, apt-get upgrade installed some gnome related packages, according to /var/log/
gnome-search-tool: 3.3.1-1
gnome-system-log: 3.3.1-2ubuntu1
gnome-settings-
gnome-screenshot: 3.3.91-1ubuntu1
gnome-utils: 3.2.1-0ubuntu5
gnome-utils-common: 3.2.1-0ubuntu5
gnome-dictionary: 3.2.1-0ubuntu5
gnome-online-
gnome-font-viewer: 3.2.1-0ubuntu5
After the upgrade, a window popped up, saying an internal error happened.
Reboot the machine, we can see the files on Desktop, but gnome-panel did not start.
After about 1 or 2 minutes, the internal error pop up window jumped out again.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-panel 1:3.3.91-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Wed Mar 14 16:47:00 2012
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: gnome-panel
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fe84064fe85: mov 0x78(%rax),%edx
PC (0x7fe84064fe85) ok
source "0x78(%rax)" (0xaaaaaaaaaaaa
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
Title: gnome-panel crashed with SIGSEGV in g_signal_
UpgradeStatus: Upgraded to precise on 2012-01-12 (62 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare
visibility: | public → private |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #948667, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.