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 426590 - crash in Theme: Installing a theme.
crash in Theme: Installing a theme.
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: Thomas Wood
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-05 13:20 UTC by tyjob
Modified: 2007-04-05 16:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description tyjob 2007-04-05 13:20:54 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Installing a theme.


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 259809280 vsize: 259809280 resident: 6184960 share: 14512128 rss: 20697088 rss_rlim: 894074880
CPU usage: start_time: 1175779141 rtime: 2829 utime: 2173 stime: 656 cutime:3 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46929773687824 (LWP 8931)]
[New Thread 1098918208 (LWP 8978)]
(no debugging symbols found)
0x00002aaeaf39fc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 125228

Thread 1 (Thread 46929773687824 (LWP 8931))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 __libc_message
    from /lib64/libc.so.6
  • #6 malloc_printerr
    from /lib64/libc.so.6
  • #7 gnome_theme_installer_run_cb
  • #8 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #9 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #12 file_transfer_dialog_wrap_async_xfer
  • #13 gnome_vfs_job_get_count
    from /opt/gnome/lib64/libgnomevfs-2.so.0
  • #14 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #15 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #17 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #18 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Jens Granseuer





          2007-04-05 16:16:24 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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