gnome-panel crashed with SIGSEGV in gtk_container_forall()

Bug #1033819 reported by dino99
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

crash after opening the gnome-classic session on Quantal i386

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-panel 1:3.5.4-0ubuntu2
Uname: Linux 3.6.0-999-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
Date: Mon Aug 6 18:45:59 2012
ExecutablePath: /usr/bin/gnome-panel
ProcCmdline: gnome-panel
SegvAnalysis:
 Segfault happened at: 0xb754d2eb: mov %edx,0x50(%eax)
 PC (0xb754d2eb) ok
 source "%edx" ok
 destination "0x50(%eax)" (0xaaaaaafa) in non-writable VMA region: 0xa7d9a000-0xac000000 r--p /usr/share/icons/gnome/icon-theme.cache
SegvReason: writing VMA /usr/share/icons/gnome/icon-theme.cache
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 gtk_container_forall () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: gnome-panel crashed with SIGSEGV in gtk_container_forall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin avahi-autoipd cdrom couchdb dialout dip disk fax fuse haldaemon lpadmin netdev plugdev polkituser proxy root rtkit sambashare ssh tape tty users video whoopsie www-data

Revision history for this message
dino99 (9d9) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0xb754d2eb in gtk_viewport_size_allocate (widget=0x88cb280, allocation=0x88cb1f8) at /build/buildd/gtk+3.0-3.5.8/./gtk/gtkviewport.c:849
   [Error: /build/buildd/gtk+3.0-3.5.8/./gtk/gtkviewport.c was not found in source tree]
 #1 0xb7757000 in ?? () from /tmp/tmpZur0UU/usr/lib/i386-linux-gnu/libgtk-3.so.0
StacktraceTop:
 gtk_viewport_size_allocate (widget=0x88cb280, allocation=0x88cb1f8) at /build/buildd/gtk+3.0-3.5.8/./gtk/gtkviewport.c:849
 ?? () from /tmp/tmpZur0UU/usr/lib/i386-linux-gnu/libgtk-3.so.0

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 gnome-panel (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:

libgdk-pixbuf2.0-common version 2.26.1-1ubuntu1 required, but 2.26.2-0ubuntu1 is available
libgtk-3-common version 3.5.9~git20120804.10676271-0ubuntu1~12.10~ricotz0 required, but 3.5.8-0ubuntu2 is available
libatspi2.0-0 version 2.5.4-0ubuntu1 required, but 2.5.5-0ubuntu1 is available
libgdk-pixbuf2.0-0 version 2.26.1-1ubuntu1 required, but 2.26.2-0ubuntu1 is available
libecal-1.2-15 version 3.5.4-0ubuntu2 required, but 3.5.5-0ubuntu1 is available
libglib2.0-0 version 2.33.7~git20120804.f1a13b89-0ubuntu1~12.10~ricotz0 required, but 2.33.6-1 is available
libedataserver-1.2-17 version 3.5.4-0ubuntu2 required, but 3.5.5-0ubuntu1 is available
libgtk-3-bin version 3.5.9~git20120804.10676271-0ubuntu1~12.10~ricotz0 required, but 3.5.8-0ubuntu2 is available
libgtk-3-0 version 3.5.9~git20120804.10676271-0ubuntu1~12.10~ricotz0 required, but 3.5.8-0ubuntu2 is available
libcamel-1.2-39 version 3.5.4-0ubuntu2 required, but 3.5.5-0ubuntu1 is available
libatk-bridge2.0-0 version 2.5.4-0ubuntu1 required, but 2.5.5-0ubuntu1 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-i386-retrace
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.