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 166438 - gconf-editor crash when closing one of multiple windows.
gconf-editor crash when closing one of multiple windows.
Status: RESOLVED FIXED
Product: gconf-editor
Classification: Applications
Component: general
2.9.x
Other other
: Normal normal
: ---
Assigned To: Gconf Editor Maintainers
Gconf Editor Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-02-06 12:40 UTC by John Ellis
Modified: 2005-02-10 11:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
Patch forcing gtk_object_destroy on delete window event. (1.31 KB, patch)
2005-02-06 20:31 UTC, Fernando Herrera
none Details | Review
Attaching a patch that removes notify handler upon list model finalize. (638 bytes, patch)
2005-02-06 22:47 UTC, John Ellis
none Details | Review

Description John Ellis 2005-02-06 12:40:31 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: gconf-editor
Severity: normal
Version: GNOME2.9.90 2.9.x
Gnome-Distributor: GARNOME
Synopsis: gconf-editor crash when closing one of multiple windows.
Bugzilla-Product: gconf-editor
Bugzilla-Component: general
Bugzilla-Version: 2.9.x
BugBuddy-GnomeVersion: 2.0 (2.9.1)
Description:
This backtrace is from a crash that is the result of changing a key
outside of gconf-editor when it has multiple windows open.

Multiple windows were open in gconf-editor at the time of the crash, in
fact the order of operations was:

1. open gconf-editor
2. open a new window in gconf-editor (now 2 windows)
3. open a new window (now 3)
4. close a window (now 2 gconf-editor windows open)
5. change key = crash.

I suspect that the close window internals are not properly cleaning up.



Debugging Information:

Backtrace was generated from '/opt/garnome/bin/gconf-editor'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1216878912 (LWP 29989)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1216878912 (LWP 29989))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 741
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/libc.so.6
  • #5 gconf_list_model_notify_func
    at gconf-list-model.c line 50
  • #6 notify_listeners_callback
    at gconf-client.c line 2368
  • #7 notify_listener_list
    at gconf-listeners.c line 588
  • #8 ltable_notify
    at gconf-listeners.c line 654
  • #9 notify_one_entry
    at gconf-client.c line 2393
  • #10 gconf_client_flush_notifies
    at gconf-client.c line 2433
  • #11 notify_idle_callback
    at gconf-client.c line 2327
  • #12 g_idle_dispatch
    at gmain.c line 3821
  • #13 g_main_dispatch
    at gmain.c line 1947
  • #14 IA__g_main_context_dispatch
    at gmain.c line 2497
  • #15 g_main_context_iterate
    at gmain.c line 2578
  • #16 IA__g_main_loop_run
    at gmain.c line 2782
  • #17 IA__gtk_main
    at gtkmain.c line 963
  • #18 main
    at main.c line 97




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-06 07:40 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gconf-editor".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Fernando Herrera 2005-02-06 16:22:40 UTC
Cannot reproduce it here, but maybe it is a gconf problem... dunno
Comment 2 John Ellis 2005-02-06 17:51:16 UTC
You need to do more with a window before closing it, here is how I can reliably
crash every time:

This example uses a key in /apps/metacity/general/

1) open gnome-sound-properties and display the system bell tab.
2) enable visual feedback so that we can change the flash type.

3) open gconf-editor
4) make /apps/metacity/general the displayed set of keys
  (visual_bell_type resides here and should now be visible)

5) open a new window with File->New Settings Window
6) close the first gconf window (the one displaying our key)

7) In the sound preferences, change the visual feedback flash type, the crash
usually happens immediately, but once I had to toggle between fullscreen and
flash_frame a couple times.
Comment 3 Fernando Herrera 2005-02-06 20:31:21 UTC
Perfect instructions. Now I can reproduce, and yes, the problem seems to be that
closing the window does not do the destroy correcly. Does attached patch fix the
problem for you?
Comment 4 Fernando Herrera 2005-02-06 20:31:55 UTC
Created attachment 37067 [details] [review]
Patch forcing gtk_object_destroy on delete window event.
Comment 5 John Ellis 2005-02-06 22:47:06 UTC
Created attachment 37080 [details] [review]
Attaching a patch that removes notify handler upon list model finalize.

Sorry it still crashes with the patch from comment #4. I am attaching a patch
that works for me. It removes the notify handler when the list model is
finalized.
Comment 6 Fernando Herrera 2005-02-10 11:19:30 UTC
Thank you very much. I've committed your patch.