GNOME Bugzilla – Bug 432619
crash in Panel: i have openbox reinstall...
Last modified: 2007-04-24 02:42:46 UTC
Version: 2.18.0 What were you doing when the application crashed? i have openbox reinstalled, but I'm using beryl as WM Distribution: Unknown Gnome Release: 2.18.0 2007-03-19 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.20-ARCH #1 SMP PREEMPT Fri Apr 20 22:54:27 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaCandy Icon Theme: Tango Memory status: size: 27799552 vsize: 27799552 resident: 14872576 share: 10182656 rss: 14872576 rss_rlim: 4294967295 CPU usage: start_time: 1177340479 rtime: 68 utime: 57 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome/bin/gnome-panel' (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 -1225623872 (LWP 7172)] (no debugging symbols found) 0xb7f4f410 in __kernel_vsyscall ()
+ Trace 130016
Thread 1 (Thread -1225623872 (LWP 7172))
----------- .xsession-errors (200 sec old) --------------------- beryl: Couldn't bind redirected window 0x2a07338 to texture beryl: pixmap 0x2200813 can't be bound to texture beryl: Couldn't bind redirected window 0x2a07338 to texture beryl: pixmap 0x2200813 can't be bound to texture beryl: Couldn't bind redirected window 0x2a07338 to texture beryl: pixmap 0x2200813 can't be bound to texture beryl: Couldn't bind redirected window 0x2a07338 to texture beryl: pixmap 0x2200813 can't be bound to texture beryl: Couldn't bind redirected window 0x2a07338 to texture beryl: pixmap 0x2200813 can't be bound to texture beryl: Couldn't bind redirected window 0x2a07338 to texture beryl: pixmap 0x2200813 can't be bound to texture beryl: Couldn't bind redirected window 0x2a07338 to texture (gnome-terminal:7081): Vte-WARNING **: No handler for control sequence `device-control-string' defined. --------------------------------------------------
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 422966 ***