gnome-panel crashed with SIGSEGV

[penalvch]

1) lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04

2) apt-cache policy gnome-panel
gnome-panel:
  Installed: 1:3.8.0-1ubuntu12
  Candidate: 1:3.8.0-1ubuntu12
  Version table:
 *** 1:3.8.0-1ubuntu12 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     1:3.8.0-1ubuntu11 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

3) While on battery with a Lenovo IdeaPad S415 Touch, what is expected to happen is gnome-panel doesn't crash.

4) What happened is it did. This would appear to be collatoral damage from https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1333225 , and https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1333248 .

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-panel 1:3.8.0-1ubuntu12
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 23 06:42:53 2014
ExecutablePath: /usr/bin/gnome-panel
ExecutableTimestamp: 1398723296
GsettingsChanges:

InstallationDate: Installed on 2014-06-21 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: gnome-panel
ProcCwd: /home/moniker
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1c042d999a: movzbl 0x3(%rdx),%eax
 PC (0x7f1c042d999a) ok
 source "0x3(%rdx)" (0x00000003) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL 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/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gnome-panel crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 _gtk_widget_set_shadowed (widget=widget@entry=0x1148bf0, shadowed=shadowed@entry=1) at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkwidget.c:15230
 gtk_grab_notify_foreach (child=0x1148bf0, data=0x7fffa71c9760) at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkmain.c:1954
 gtk_grab_notify_foreach (child=0x143b150, data=0x7fffa71c9760) at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkmain.c:1941
 gtk_menu_shell_forall (container=<optimized out>, include_internals=<optimized out>, callback=0x7f1c041a2630 <gtk_grab_notify_foreach>, callback_data=0x7fffa71c9760) at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkmenushell.c:1170
 gtk_grab_notify_foreach (child=0x12b3240, data=0x7fffa71c9760) at /build/buildd/gtk+3.0-3.10.8/./gtk/gtkmain.c:1941

[Dmitry Shachnev (mitya57)]

I don't understand why you marked this bug as triaged. The stack trace does not have any references to gnome-panel source code, thus it is likely a crash in Gtk internals. Given the other two bug reports you got, it can be also a problem with your system rather than Ubuntu packages.

Do you have a reliable way to reproduce this crash?

[penalvch (penalvch)]

Dmitry Schachnev, as per https://wiki.ubuntu.com/Bugs/Status it fits the definition of Triaged, where it's ready for a GNOME developer to look at and fix. If you can't fix it, or won't ultimately be fixing it, please don't adjust the Status further.

Whether or not it's a gnome-panel issue, that's up to a GNOME developer to determine. However, the package was automatically choosen by Apport Retracing Service. As well, this is not a system (local) issue.

Regarding reproducibility, it happens intermittently when connecting to an nfs4 share.As per another report, an issue was found with file-roller and this would probably be addressed when that's resolved.

[penalvch (penalvch)]

Not reproducible in Wily, not using Unity, and not using Trusty anymore.

[Dmitry Shachnev (mitya57)]

According to errors.ubuntu.com, this is the most frequently occuring gnome-panel crash on 14.04 LTS with 8414 occurences at the moment of writing. So it would be nice to get it fixed for Trusty.