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 365492 - crash in Theme: trying to install DarkX-...
crash in Theme: trying to install DarkX-...
Status: RESOLVED DUPLICATE of bug 352490
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-26 23:09 UTC by roelle
Modified: 2006-10-27 01:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description roelle 2006-10-26 23:09:43 UTC 
Version: 2.16.0

What were you doing when the application crashed?
trying to install DarkX-2s in FC6


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 61861888 vsize: 0 resident: 61861888 share: 0 rss: 14942208 rss_rlim: 0
CPU usage: start_time: 1161904150 rtime: 0 utime: 40 stime: 0 cutime:34 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-theme-manager'

(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 -1208342832 (LWP 5475)]
[New Thread -1234461808 (LWP 5871)]
(no debugging symbols found)
0x00ae3402 in __kernel_vsyscall ()

+ Trace 78605

Thread 1 (Thread -1208342832 (LWP 5475))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 __libc_message
    from /lib/libc.so.6
  • #8 free
    from /lib/libc.so.6
  • #9 g_free
    from /lib/libglib-2.0.so.0
  • #10 gnome_theme_installer_run_cb
  • #11 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 file_transfer_dialog_wrap_async_xfer
  • #17 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #18 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #19 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #21 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 main
  • #0 __kernel_vsyscall 






Comment 1


Karsten Bräckelmann





          2006-10-27 01:44:31 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 352490 ***