[natty] unity-panel-service crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-appmenu (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: indicator-appmenu
Running updated natty--daily, alt install, amd64.
I was watching a movie in fullscreen, and found apport window there when done.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-appmenu 0.1.97-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat Apr 2 19:02:17 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110402)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fb32e95ed81: mov 0x18(%rbx),%rdi
PC (0x7fb32e95ed81) ok
source "0x18(%rbx)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
g_main_
?? () from /lib/x86_
g_main_loop_run () from /lib/x86_
Title: unity-panel-service crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio avahi cdrom dialout dip fax floppy fuse games gdm gnats irc lpadmin netdev plugdev root sambashare shadow ssh sudo syslog tape video voice www-data
XsessionErrors:
(nautilus:1351): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
(nautilus:1351): GdkPixbuf-CRITICAL **: gdk_pixbuf_
(<unknown>:1342): dee-WARNING **: Transaction from com.canonical.
(<unknown>:1342): dee-WARNING **: Transaction from com.canonical.
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #741488, 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.