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 368248 - crash in Theme: Changed theme. It seems ...
crash in Theme: Changed theme. It seems ...
Status: RESOLVED DUPLICATE of bug 352265
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-31 12:05 UTC by jops87
Modified: 2006-10-31 16:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jops87 2006-10-31 12:05:20 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Changed theme. It seems that if I select another theme than the default one, all applications start crashing immediately even after I restart computer. I have to start gnome-theme-manager in KDE in order to fix it back to default theme.

X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode:  146
  Minor opcode:  3
  Resource id:  0x0
Failed to open device



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

Memory status: size: 30744576 vsize: 0 resident: 30744576 share: 0 rss: 13070336 rss_rlim: 0
CPU usage: start_time: 1162296061 rtime: 0 utime: 71 stime: 0 cutime:68 cstime: 0 timeout: 3 it_real_value: 0 frequency: 8

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 -1225554256 (LWP 7717)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 80931

Thread 1 (Thread -1225554256 (LWP 7717))

  • #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 ??
  • #5 gdk_x11_drawable_get_xdisplay
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #8 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 main
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-10-31 16:51:56 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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