Ubuntu

gnome-panel crashed with SIGSEGV in gtk_widget_pop_verify_invariants()

Reported by Kolargol00 on 2012-03-07
This bug affects 137 people
Affects Status Importance Assigned to Milestone
GNOME Panel
New
Critical
gnome-panel (Ubuntu)
High
Unassigned

Bug Description

Crash happened while changing power settings but power settings window was still responsive.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-panel 1:3.3.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu2
Architecture: amd64
Date: Wed Mar 7 11:41:47 2012
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: gnome-panel
ProcEnviron:
 LANGUAGE=en_SG:en
 LANG=en_SG.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc89adc0e85: mov 0x78(%rax),%edx
 PC (0x7fc89adc0e85) ok
 source "0x78(%rax)" (0xaaaaaaaaaaaaab22) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-panel crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Kolargol00 (kolargol00) wrote :

StacktraceTop:
 gtk_widget_pop_verify_invariants (widget=0x1033130) at /build/buildd/gtk+3.0-3.3.18/./gtk/gtkwidget.c:8713
 gtk_widget_real_unrealize (widget=0xf2c7e0) at /build/buildd/gtk+3.0-3.3.18/./gtk/gtkwidget.c:10512
 _g_closure_invoke_va (closure=0xef6470, return_value=0x0, instance=0xf2c7e0, args=0x7fff67cc9a78, n_params=0, param_types=<optimized out>) at /build/buildd/glib2.0-2.31.20/./gobject/gclosure.c:840
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=0, var_args=<optimized out>) at /build/buildd/glib2.0-2.31.20/./gobject/gsignal.c:3206
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.31.20/./gobject/gsignal.c:3352

Changed in gnome-panel (Ubuntu):
importance: Undecided → Medium
summary: - gnome-panel crashed with SIGSEGV in g_signal_emit_valist()
+ gnome-panel crashed with SIGSEGV in gtk_widget_pop_verify_invariants()
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-panel (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
visibility: private → public
Changed in gnome-panel (Ubuntu):
importance: Medium → High
tags: added: quantal
tags: added: running-unity
Pit(er) Ralon (pitralon) wrote :

happens to me after enable compiz - then logged out and logged in

Karma Dorje (taaroa) wrote :

this after yesterday's update. as you can see there is gnome-panel.

Robert Bruce Park (robru) wrote :

Happened to me just now, after rebooting from a system update. 1:3.5.4-0ubuntu2

Bryce Harrington (bryce) on 2012-08-22
Changed in gnome-panel (Ubuntu):
status: Confirmed → Triaged
tags: added: raring
Sasa Paporovic (melchiaros) wrote :

Reported upstream.

Alistair Buxton (a-j-buxton) wrote :

My bug https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1106547 was just marked duplicate of this one, but doesn't match with the description posted on the upstream bug.

- I can't reproduce the crash in 12.04 or 12.10, only in raring.
- I can reproduce it every time by a simple procedure: add an applet to the panel (ie fish), and then remove it.
- It is definitely not a duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1076830 - while similar, the steps to reproduce are not identical, and the workaround I discovered for that bug don't affect this one.

So, is my bug really a duplicate?

Changed in gnome-panel:
importance: Unknown → Critical
status: Unknown → New
Bob Bib (bobbib) wrote :

Alistair Buxton:
> My bug was just marked duplicate of this one, but doesn't match with the description posted on the upstream bug.
> So, is my bug really a duplicate?

If I understand it correctly, automatic duplicate bug marking is done based not on the bug description, but on the crash backtrace results (i. e., the program internals leading to crash).
The same code bug may be triggered by different conditions.

Your bug #1076830 doesn't contain a coredump retrace, and therefore is not very informative.
If you can reproduce it -- report it properly, with a coredump attached.
(If apport doesn't allow you to report the crash to Launchpad, please look at the bug 994921).

Alistair Buxton (a-j-buxton) wrote :

Apport deletes the coredump if it identifies a dupe. #994921 does not address this issue. I can reattach it if you want.

Bob Bib (bobbib) wrote :

Alistair Buxton:
> Apport deletes the coredump if it identifies a dupe.
> I can reattach it if you want.

Did I understand correctly, that bug #1076830 is an attempt to report a crash which has been already identified by apport as a duplicate?
If so, then you should probably mark it as a duplicate; after that, you can add a comment to the original bug discussion with a reference to your duplicate bug.

Alistair Buxton (a-j-buxton) wrote :

no you've misunderstood. the bug in question is bug #1106547 which i believe apport has misidentified as a dupe of this bug. #1076830 is irrelevant, and i shouldn't have mentioned it. it's similar but also not a dupe.

Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/948667

tags: added: iso-testing
tags: added: saucy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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