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 518090 - crash in Theme Installer: I just started appearenc...
crash in Theme Installer: I just started appearenc...
Status: RESOLVED DUPLICATE of bug 364396
Product: gnome-control-center
Classification: Core
Component: [obsolete] Appearance
2.21.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-22 16:15 UTC by Jonh Wendell
Modified: 2008-02-23 15:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Jonh Wendell 2008-02-22 16:15:29 UTC 
Version: 2.21.90

What were you doing when the application crashed?
I just started appearences capplet


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.21.91 2008-02-13 (Ubuntu)
BugBuddy Version: 2.21.90

System: Linux 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 36720640 vsize: 36720640 resident: 11304960 share: 7585792 rss: 11304960 rss_rlim: 4294967295
CPU usage: start_time: 1203696837 rtime: 36 utime: 34 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-appearance-properties'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c5e720 (LWP 22054)]
0xb7f17410 in __kernel_vsyscall ()

+ Trace 190110

Thread 1 (Thread 0xb6c5e720 (LWP 22054))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.15.5/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.15.5/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 gdk_event_apply_filters
    at /build/buildd/gtk+2.0-2.12.8/gdk/x11/gdkevents-x11.c line 345
  • #8 gdk_event_translate
    at /build/buildd/gtk+2.0-2.12.8/gdk/x11/gdkevents-x11.c line 896
  • #9 _gdk_events_queue
    at /build/buildd/gtk+2.0-2.12.8/gdk/x11/gdkevents-x11.c line 2285
  • #10 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.12.8/gdk/x11/gdkevents-x11.c line 2345
  • #11 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.15.5/glib/gmain.c line 2064
  • #12 g_main_context_iterate
    at /build/buildd/glib2.0-2.15.5/glib/gmain.c line 2697
  • #13 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.15.5/glib/gmain.c line 2905
  • #14 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.8/gtk/gtkmain.c line 1163
  • #15 theme_thumbnail_factory_init
    at theme-thumbnail.c line 1146
  • #16 main
    at appearance-main.c line 50
  • #0 __kernel_vsyscall 


----------- .xsession-errors (6049 sec old) ---------------------
(update-notifier:5498): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:5498): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:5498): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:5498): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:5498): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:5498): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
(update-notifier:5498): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jens Granseuer 2008-02-23 15:41: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 364396 ***