gnome-panel crashed with SIGSEGV in g_type_check_instance_cast()

Bug #255461 reported by Chad Waters
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

gnome-panel 2.23.6 crash and restarted an hour or so into session.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.23.6-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: gnome-panel
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
StacktraceTop:
 g_type_check_instance_cast ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_widget_queue_resize () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_image_set_from_pixbuf ()
Title: gnome-panel crashed with SIGSEGV in g_type_check_instance_cast()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Chad Waters (chad) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Darius Regnier (darius-regnier) wrote :

This happened to me too. The panel dissapeared, the login sound played, and then the panel reappeared. There is 100% reproducability (at least for me) because this happens EVERY time I switch NVIDIA accelerated graphics drivers (between 173 and 177)

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you get the issue when using the nv open source drivers?

Revision history for this message
Darius Regnier (darius-regnier) wrote :

Do you mean package "nvidia-glx-envy"? I didn't try to install it because when I do, it says one of the packages it wants me to remove is "ubuntu-desktop" which I'm pretty sure I kinda need.

Revision history for this message
Sebastien Bacher (seb128) wrote :

no, I meant to edit the xorg configuration to use the opensource driver, you should be able to use jockey-gtk to disable the nivdia one

Revision history for this message
Chad Waters (chad) wrote :

hi, original reporter here: my X is pulling the intel driver via auto config (no xorg.conf).

The crash happened once and I haven't seen it again in a days use. The only thing I was doing at the time was browsing with firefox 3.0. I can't narrow down any particular action beyond that.

If it happens again, I'll try to pinpoint it and and reproduce it for a dump.

Revision history for this message
Darius Regnier (darius-regnier) wrote :

Sorry SB, how would a person go about editing xorg.conf to use the opensource driver? (I know what and where it is, I just don't know what to change)
As for Hardware Drivers (jockey-gtk), the only options I see are the 173 and 177 NVIDIA (nonfree) drivers (see screenshot)

Revision history for this message
Sebastien Bacher (seb128) wrote :

don't bother, the bug is not likely to be nvidia specific, do you get it every time after login?

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue seems to be bug #255644 and has been fixed today in intrepid, you just need to update

Changed in gnome-panel:
status: Incomplete → Fix Released
Revision history for this message
Darius Regnier (darius-regnier) wrote :

Hey, I don't know if this fixed this for everyone else but it didn't for me, so assuming it was a different issue I started bug #255883.

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.