emerald-theme-manager crashed with SIGSEGV in g_main_context_dispatch()

Bug #156618 reported by Savvas Radevic
28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
emerald (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: emerald

I was just opening/running the themer, it closed by itself. I'm using nvidia-glx with nvidia NX7300GT graphics card if it means anything
No apport showing up, but I saw this in /var/crash

ProblemType: Crash
Architecture: amd64
Date: Thu Oct 18 16:04:55 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/emerald-theme-manager
NonfreeKernelModules: vmnet vmmon nvidia
Package: emerald 0.3~git20070717-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: emerald-theme-manager
ProcCwd: /home/forger
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: emerald
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
 ?? () from /usr/lib/libgnomevfs-2.so.0
 g_main_context_dispatch ()
 ?? () from /usr/lib/libglib-2.0.so.0
Title: emerald-theme-manager crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux ubuntu 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Savvas Radevic (medigeek) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:get_file_info_callback (vfs_handle=<value optimized out>, results=<value optimized out>, data=0xfa8e10) at gtkfilesystemgnomevfs.c:1473
dispatch_job_callback (data=<value optimized out>) at gnome-vfs-job.c:247
IA__g_main_context_dispatch (context=0x646110) at /build/buildd/glib2.0-2.14.1/glib/gmain.c:2061
g_main_context_iterate (context=0x646110, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.14.1/glib/gmain.c:2694
IA__g_main_loop_run (loop=0x8d9940) at /build/buildd/glib2.0-2.14.1/glib/gmain.c:2898

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in emerald:
importance: Undecided → Medium
Changed in emerald:
status: New → Invalid
Revision history for this message
Bernhard (b.a.koenig) wrote :

Why is this invalid? Emerald-theme-manager is currently very unstable for me (uses 50% CPU in dual core), especially when reloading or editing themes. I would set this to confirmed.

Changed in emerald:
status: Invalid → Confirmed
Revision history for this message
Bernhard (b.a.koenig) wrote :

Sorry, just realized that this is from October 2007! Anyway, emerald-theme-manager is very unstable for me at the moment. Maybe I should file a new bug...

Revision history for this message
Savvas Radevic (medigeek) wrote : Re: [Bug 156618] Re: emerald-theme-manager crashed with SIGSEGV in g_main_context_dispatch()

> Sorry, just realized that this is from October 2007! Anyway, emerald-
> theme-manager is very unstable for me at the moment. Maybe I should file
> a new bug...

Right, I switched it because I cannot verify it anymore, however if
you think you have the same error since 2007, mark as confirmed,
otherwise mark it as "Invalid" or "Incomplete" (which would mark it as
invalid after 3 months or so of inactivity) :)

Revision history for this message
Bernhard (b.a.koenig) wrote :

Actually, it's probably not the same error: I don't get a SIGSEGV, just a 50% CPU load. But that's bad enough. Maybe I should file again.

Changed in emerald:
status: Confirmed → 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.