unity-panel-service crashed with SIGSEGV in g_dbus_proxy_call_internal()

Bug #1035156 reported by Steve Langasek
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I don't know what triggered this crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity-services 6.0.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CrashCounter: 1
Date: Thu Aug 9 17:09:58 2012
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: /usr/lib/unity/unity-panel-service
SegvAnalysis:
 Segfault happened at: 0x7fd14c33a766 <g_dbus_proxy_call_internal+54>: mov (%rbx),%rdx
 PC (0x7fd14c33a766) ok
 source "(%rbx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_dbus_proxy_call_internal (proxy=0xaaaaaaaaaaaaaaaa, method_name=0x7fd1410f9a9a "AboutToShowGroup", parameters=0x7fd13f99f160, flags=G_DBUS_CALL_FLAGS_NONE, timeout_msec=-1, fd_list=fd_list@entry=0x0, cancellable=0x0, callback=callback@entry=0, user_data=user_data@entry=0x0) at /build/buildd/glib2.0-2.33.6/./gio/gdbusproxy.c:2705
 g_dbus_proxy_call (proxy=<optimized out>, method_name=<optimized out>, parameters=<optimized out>, flags=<optimized out>, timeout_msec=<optimized out>, cancellable=<optimized out>, callback=0, user_data=0x0) at /build/buildd/glib2.0-2.33.6/./gio/gdbusproxy.c:3017
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
 g_main_dispatch (context=0x1343040) at /build/buildd/glib2.0-2.33.6/./glib/gmain.c:2691
 g_main_context_dispatch (context=context@entry=0x1343040) at /build/buildd/glib2.0-2.33.6/./glib/gmain.c:3195
Title: unity-panel-service crashed with SIGSEGV in g_dbus_proxy_call_internal()
UpgradeStatus: Upgraded to quantal on 2012-06-11 (59 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src sudo

Revision history for this message
Steve Langasek (vorlon) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 _g_dbus_proxy_set_object (interface=0xaaaaaaaaaaaaaaaa, object=0x7fd1410f9a9a) at /build/buildd/glib2.0-2.33.8/./gio/gdbusproxy.c:3237
   [Error: /build/buildd/glib2.0-2.33.8/./gio/gdbusproxy.c was not found in source tree]
 #1 0x0000000002874b63 in ?? ()
 #2 0x0000000000000000 in ?? ()
StacktraceTop:
 _g_dbus_proxy_set_object (interface=0xaaaaaaaaaaaaaaaa, object=0x7fd1410f9a9a) at /build/buildd/glib2.0-2.33.8/./gio/gdbusproxy.c:3237
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libglib2.0-0 version 2.33.6-1 required, but 2.33.8-1 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1033267, so it 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. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.