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

Bug #804230 reported by Michael Terry
236
This bug affects 54 people
Affects Status Importance Assigned to Milestone
Indicator Display Objects
Confirmed
High
Robert Carr
Unity
Confirmed
Critical
Unassigned
unity (Ubuntu)
Triaged
Critical
Canonical Desktop Experience Team
Oneiric
Triaged
Critical
Canonical Desktop Experience Team

Bug Description

I clicked on an indicator. I don't remember which one.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-services 4.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic i686
Architecture: i386
CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
CrashCounter: 1
Date: Fri Jul 1 10:57:43 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110422)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x78907a <g_signal_emit_valist+10>: call 0x768be7 <__i686.get_pc_thunk.bx>
 PC (0x0078907a) ok
 source "0x768be7" (0x00768be7) ok
 destination "(%esp)" (0xbf7a4fb0) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_signal_emit_valist (instance=0x82df000, signal_id=33, detail=0, var_args=0xbf7a50fc "") at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:2913
 g_signal_emit (instance=0x82df000, signal_id=33, detail=0) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3044
 _gtk_widget_grab_notify (widget=0x82df000, was_grabbed=0) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkwidget.c:6360
 gtk_grab_notify_foreach (child=0x82df000, data=0xbf7a5424) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkmain.c:2132
 gtk_box_forall (container=0x81cc8c8, include_internals=1, callback=0x278860 <gtk_grab_notify_foreach>, callback_data=0xbf7a5424) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkbox.c:1838
Title: unity-panel-service crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Michael Terry (mterry) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_signal_emit_valist (instance=0x82df000, signal_id=33, detail=0, var_args=0xbf7a50fc "") at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:2913
 g_signal_emit (instance=0x82df000, signal_id=33, detail=0) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3044
 _gtk_widget_grab_notify (widget=0x82df000, was_grabbed=0) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkwidget.c:6360
 gtk_grab_notify_foreach (child=0x82df000, data=0xbf7a5424) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkmain.c:2132
 gtk_box_forall (container=0x81cc8c8, include_internals=1, callback=0x278860 <gtk_grab_notify_foreach>, callback_data=0xbf7a5424) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkbox.c:1838

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):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Changed in unity (Ubuntu):
importance: Medium → Critical
visibility: private → public
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Since this just affected me, and 4 other people, marking Confirmed.

Changed in unity (Ubuntu):
status: New → Confirmed
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

To provide a little extra info, this happened to me when I clicked on the indicators on my secondary monitor. For about 60 seconds, mouse was responsive in moving, but no clicks or keypresses registered until the "unity panel service has crashed" dialog appeared.

Changed in unity:
status: New → Confirmed
Revision history for this message
Daryl Sweat (curnel-d) wrote :

My experience is similar to clint's. Except I wasn't clicking on indicators, but instead clicking on a menu option in libreoffice on the integrated global menu, on my primary monitor.

Same experience after that thought. About 45-60 seconds of free mouse but unresponsive computer and then unit panel crash.

Revision history for this message
Daryl Sweat (curnel-d) wrote :

^^^ Correction to above post. Firefox, not libre. Was just working in libre, so my mind wrote that instead of the intended. :P

Revision history for this message
juan (juanjo836) wrote :

I click on the volume indicator, and it goes to max, i click it again and it goes to min, then the cursor wont move and the the crash

Revision history for this message
vulfgar (vulfgar) wrote :

I clicked on the volume indicator, which didn't work, and then the crash.

Revision history for this message
Onlyodin (ubuntu-xsnet) wrote :

I too clicked on the volume, which behaved erratically, followed the mouse pointer around, then subsequently crashed.

Changed in unity (Ubuntu):
assignee: nobody → Canonical Desktop Experience Team (canonical-dx-team)
Revision history for this message
mario catena (mcblackmar02) wrote :

me too on clock panel app.

tags: added: iso-testing
Revision history for this message
Ted Gould (ted) wrote :

This looks like a bug with the slider grabs just by how it's going through the various GTK items. Robert? What do you think, associated with what you're looking at?

Changed in ido:
importance: Undecided → High
status: New → Confirmed
assignee: nobody → Robert Carr (robertcarr)
Revision history for this message
Paul Kenyon (rixoff) wrote :

Just adding a "me too" - I can trigger this with the volume slider.

The interesting thing is that I can only do full or min volumes - if I try to drag, or click somewhere in between, it just works its way to the other side. For volume control, I revert to the hardware volume buttons, which luckily aren't linked to the pulseaudio controls in any way.

Revision history for this message
Claudio Moretti (flyingstar16) wrote :

It affects me randomly, meaning that no matter what I'm doing (though most of the times I'm surfing the web), at some point I have, like Daryl, 45-60 seconds of non responsive computer and then unity crashes.

Changed in unity (Ubuntu Oneiric):
status: Confirmed → Triaged
tags: added: rls-mgr-o-tracking
Neil J. Patel (njpatel)
Changed in unity:
importance: Undecided → Critical
milestone: none → 4.16.0
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.