GNOME Bugzilla – Bug 427120
crash in Theme Installer: While Romoving Icon them
Last modified: 2007-04-08 11:59:20 UTC
Version: 2.18.0 What were you doing when the application crashed? While Romoving Icon them Distribution: Unknown Gnome Release: 2.18.0 2007-03-19 (Archlinux) BugBuddy Version: 2.18.0 System: Linux 2.6.20-ARCH #1 SMP PREEMPT Fri Apr 6 15:04:25 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Candido-solidLINE Icon Theme: gnome Memory status: size: 31240192 vsize: 31240192 resident: 15884288 share: 10403840 rss: 15884288 rss_rlim: 4294967295 CPU usage: start_time: 1175905821 rtime: 223 utime: 130 stime: 93 cutime:0 cstime: 0 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225967936 (LWP 7174)] (no debugging symbols found) 0xb7f33410 in __kernel_vsyscall ()
+ Trace 125648
Thread 1 (Thread -1225967936 (LWP 7174))
----------- .xsession-errors (66 sec old) --------------------- beryl: Couldn't bind redirected window 0x1000bfc to texture beryl: pixmap 0x2200312 can't be bound to texture beryl: Couldn't bind redirected window 0x1000c2d to texture beryl: pixmap 0x2200314 can't be bound to texture beryl: Couldn't bind redirected window 0x1000bfc to texture beryl: pixmap 0x2200312 can't be bound to texture beryl: Couldn't bind redirected window 0x1000c2d to texture beryl: pixmap 0x2200314 can't be bound to texture beryl: Couldn't bind redirected window 0x1000bfc to texture beryl: pixmap 0x2200312 can't be bound to texture beryl: Couldn't bind redirected window 0x1000c2d to texture beryl: pixmap 0x2200314 can't be bound to texture beryl: Couldn't bind redirected window 0x1000bfc to texture ...Too much output, ignoring rest... --------------------------------------------------
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 349471 ***