Bug 387265 – crash in Configuration Editor: I think gconf-editor was...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 387265 - crash in Configuration Editor: I think gconf-editor was...


Summary:	crash in Configuration Editor: I think gconf-editor was...


Status:	RESOLVED DUPLICATE of bug 361137

Product:	gconf-editor
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gconf Editor Maintainers
QA Contact:	Gconf Editor Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-18 19:34 UTC by math.16k
Modified:	2006-12-19 17:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description math.16k 2006-12-18 19:34:02 UTC

Version: 2.16.0

What were you doing when the application crashed?
I think gconf-editor was probably still busy, and I might have pressed too early on the 'close-button' [X] After that gconf-editor crashed.

Other programs that were running on the same time:
- gnome-screensaver-preferences
- XChat
- gnome-terminal
- firefox 2.0

Greetz, Math.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 34136064 vsize: 0 resident: 34136064 share: 0 rss: 13340672 rss_rlim: 0
CPU usage: start_time: 1166469139 rtime: 0 utime: 602 stime: 0 cutime:574 cstime: 0 timeout: 28 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gconf-editor'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225230144 (LWP 5744)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 95202

Thread 1 (Thread -1225230144 (LWP 5744))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 g_object_add_weak_pointer
from /usr/lib/libgobject-2.0.so.0
#6 g_datalist_id_set_data_full
from /usr/lib/libglib-2.0.so.0
#7 g_object_get_qdata
from /usr/lib/libgobject-2.0.so.0
#8 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#9 gdk_events_pending
from /usr/lib/libgdk-x11-2.0.so.0
#10 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#11 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#12 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#13 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#14 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#15 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#16 gconf_value_type_to_string
#17 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#18 ??
#0 __kernel_vsyscall

Comment 1 Damien Durand 2006-12-19 17:18:35 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 361137 ***