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 385333 - crash in Configuration Editor:
crash in Configuration Editor:
Status: RESOLVED DUPLICATE of bug 325759
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: 2006-12-13 04:37 UTC by btdonovan
Modified: 2006-12-14 12:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description btdonovan 2006-12-13 04:37:14 UTC 
Version: 2.16.0

What were you doing when the application crashed?



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

Memory status: size: 209698816 vsize: 0 resident: 209698816 share: 0 rss: 153853952 rss_rlim: 0
CPU usage: start_time: 1165982774 rtime: 0 utime: 4048 stime: 0 cutime:2981 cstime: 0 timeout: 1067 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 -1225247056 (LWP 12681)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 93740

Thread 1 (Thread -1225247056 (LWP 12681))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 gail_tree_view_new
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #11 g_source_is_destroyed
    from /usr/lib/libglib-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


palfrey





          2006-12-13 17:41:04 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


btdonovan





          2006-12-14 01:37:15 UTC
        



I was browsing through the keys in the gconf-editor tool when it started getting sluggish and unresponsive when expanding keys before finally crashing.  This crash was an isolated incident and I have not been able to replicate it so I have not been able to obtain the requested stack trace.

Sorry.






Comment 3


André Klapper





          2006-12-14 12:24:24 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 325759 ***