driconf crashed with SIGSEGV in g_closure_invoke()

Bug #196587 reported by mabovo
4
Affects Status Importance Assigned to Milestone
driconf (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: driconf

mabovo@macbook:~$ driconf

** (driconf:9383): WARNING **: Invalid borders specified for theme pixmap:
        /home/mabovo/.themes/Mac4Lin_GTK_Graphite_v0.4/gtk-2.0/Buttons/button-default.png,
borders don't fit within the image
/var/lib/python-support/python2.5/driconf.py:163: Warning: g_object_notify: assertion `G_IS_OBJECT (object)' failed
  gtk.main()
Segmentation fault (core dumped)

Message from Kern.log/Syslog:
Feb 28 11:21:43 macbook kernel: [ 267.745273] driconf[9383] general protection rip:7fecfd5b794c rsp:7fff0873a370 error:0

ProblemType: Crash
Architecture: amd64
Date: Thu Feb 28 11:21:43 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/driconf
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: cdrom
Package: driconf 0.9.1-2ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/driconf
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_BR.UTF-8
Signal: 11
SourcePackage: driconf
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: driconf crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.24-10-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
mabovo (mabovo) wrote :
mabovo (mabovo)
description: updated
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

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

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 or 9.04?

Changed in driconf:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in driconf:
status: Incomplete → Invalid
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.