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 386368 - crash in Theme: instalando un tema de es...
crash in Theme: instalando un tema de es...
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: 2006-12-16 00:35 UTC by aoshidan
Modified: 2006-12-16 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description aoshidan 2006-12-16 00:35:47 UTC 
Version: 2.16.1

What were you doing when the application crashed?
instalando un tema de escritorio


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

Memory status: size: 70402048 vsize: 0 resident: 70402048 share: 0 rss: 17158144 rss_rlim: 0
CPU usage: start_time: 1166229515 rtime: 0 utime: 176 stime: 0 cutime:166 cstime: 0 timeout: 10 it_real_value: 0 frequency: 3

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

(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 -1225083216 (LWP 4765)]
[New Thread -1272833120 (LWP 4819)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 94516

Thread 1 (Thread -1225083216 (LWP 4765))

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






Comment 1


Susana





          2006-12-16 10:03:54 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 issue is fixed in version 2.16.2 .

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