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

Bug #953479 reported by Sascha
196
This bug affects 34 people
Affects Status Importance Assigned to Milestone
Application Menu Indicator
Fix Released
High
Charles Kerr
indicator-appmenu (Ubuntu)
Fix Released
High
Unassigned

Bug Description

1) Ubuntu 12.04 LTS Beta 1 (nightly build)

2) indicator-appmenu: Installiert: 0.3.92-0ubuntu1

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-appmenu 0.3.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Mon Mar 12 23:05:56 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: /usr/lib/unity/unity-panel-service
SegvAnalysis:
 Segfault happened at: 0xbfbd54: testb $0x4,0x10(%eax)
 PC (0x00bfbd54) ok
 source "$0x4" ok
 destination "0x10(%eax)" (0x00000010) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_variant_new_tuple () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/indicators3/7/libappmenu.so
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_variant_new_tuple()
UpgradeStatus: Upgraded to precise on 2012-03-10 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

Related branches

Revision history for this message
Sascha (skbierm-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_variant_is_trusted (value=0x0) at /build/buildd/glib2.0-2.31.20/./glib/gvariant-core.c:604
 g_variant_new_tuple (children=0xbfd0113c, n_children=1) at /build/buildd/glib2.0-2.31.20/./glib/gvariant.c:878
 ?? () from /tmp/tmpNPJYg3/usr/lib/indicators3/7/libappmenu.so
 call_in_idle_cb (user_data=0x95392f0) at /build/buildd/glib2.0-2.31.20/./gio/gdbusconnection.c:4698
 g_idle_dispatch (source=0xb6004118, callback=0x7ee680 <call_in_idle_cb>, user_data=0x95392f0) at /build/buildd/glib2.0-2.31.20/./glib/gmain.c:4629

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 indicator-appmenu (Ubuntu):
importance: Undecided → Medium
summary: - unity-panel-service crashed with SIGSEGV in g_variant_new_tuple()
+ unity-panel-service crashed with SIGSEGV in g_variant_is_trusted()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-appmenu (Ubuntu):
status: New → Confirmed
visibility: private → public
Changed in indicator-appmenu (Ubuntu):
importance: Medium → High
Revision history for this message
Doug McMahon (mc3man) wrote :

I think those affected should mention if they've disabled the global menus, either directly or thru a 3rd party app
This bug is 100% repeatable by removing the appmenu* packages but not removing indicator-appmenu

It's also repeatable thru the use of that Usettings package that has come around, maybe other 3rd party apps also?

Not saying this is the only cause for this crash but either of the above is guaranteed to cause this

Revision history for this message
Sascha (skbierm-deactivatedaccount) wrote :

No, I haven't disabled the global menus.

Revision history for this message
Charles Kerr (charlesk) wrote :

It's unfortunate that https://launchpadlibrarian.net/96566586/ThreadStacktrace.txt doesn't have more debugging information about libappmenu, the backtrace looks like it has unity & glib's debugging symbols, but not libappmenu's.

On the other hand, it crashed in a call to g_variant_new_tuple() from appmenu, and libappmenu only calls g_variant_new_tuple() in one place, at the end of indicator-appmenu.c's get_menus() function.... :)

Changed in indicator-appmenu:
assignee: nobody → Charles Kerr (charlesk)
importance: Undecided → High
Charles Kerr (charlesk)
Changed in indicator-appmenu:
status: New → In Progress
Revision history for this message
André Lopes (zipatei) wrote :

Here: "unity-panel-service crashed with SIGSEGV in g_variant_new_tuple()"

Revision history for this message
Robin Sheat (eythian) wrote :

I had disabled the global menu by setting 'UBUNTU_MENUPROXY=0'. When I removed this, it stopped crashing.

Charles Kerr (charlesk)
Changed in indicator-appmenu:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-appmenu - 0.3.94-0ubuntu3

---------------
indicator-appmenu (0.3.94-0ubuntu3) precise; urgency=low

  * Backport r180 to fix unity-panel-service segfaults when unsetting
    the menuproxy variable to disable menus export (lp: #953479, #958048)
 -- Sebastien Bacher <email address hidden> Mon, 19 Mar 2012 11:36:10 +0100

Changed in indicator-appmenu (Ubuntu):
status: Confirmed → Fix Released
Ted Gould (ted)
Changed in indicator-appmenu:
milestone: none → 0.3.95
Ted Gould (ted)
Changed in indicator-appmenu:
status: Fix Committed → Fix Released
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.