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 426386 - crash in Configuration Editor: I was searching for the ...
crash in Configuration Editor: I was searching for the ...
Status: RESOLVED DUPLICATE of bug 361137
Product: gconf-editor
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Gconf Editor Maintainers
Gconf Editor Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-04 21:42 UTC by rodrigorivascosta
Modified: 2007-04-06 13:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rodrigorivascosta 2007-04-04 21:42:52 UTC 
Version: 2.16.0

What were you doing when the application crashed?
I was searching for the "asf" string using the 'Find' utility. I checked both the 'keys' and 'values'. It gave the result of the search, and then crashed


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:38:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 50532352 vsize: 0 resident: 50532352 share: 0 rss: 12750848 rss_rlim: 0
CPU usage: start_time: 1175463581 rtime: 0 utime: 237 stime: 0 cutime:207 cstime: 0 timeout: 30 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209075488 (LWP 4891)]
(no debugging symbols found)
0x0073b402 in __kernel_vsyscall ()

+ Trace 125061

Thread 1 (Thread -1209075488 (LWP 4891))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/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 /lib/libgobject-2.0.so.0
  • #6 g_datalist_id_set_data_full
    from /lib/libglib-2.0.so.0
  • #7 g_object_get_qdata
    from /lib/libgobject-2.0.so.0
  • #8 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #9 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #10 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #11 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /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/libc.so.6
  • #18 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (106358 sec old) ---------------------
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
[mpeg4 @ 0x86db6e0]marker does not match f_code
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-04-05 16:39:44 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 Kjartan Maraas 2007-04-06 13:38:31 UTC 

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