GNOME Bugzilla – Bug 406545
crash in Terminal: Configuring Beryl, using...
Last modified: 2007-02-11 00:34:40 UTC
Version: 2.16.0 What were you doing when the application crashed? Configuring Beryl, using Beryl Manager Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 95227904 vsize: 0 resident: 95227904 share: 0 rss: 10395648 rss_rlim: 0 CPU usage: start_time: 1171109691 rtime: 0 utime: 816 stime: 0 cutime:641 cstime: 0 timeout: 175 it_real_value: 0 frequency: 1934 Backtrace was generated from '/usr/bin/gnome-terminal' (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 -1208895792 (LWP 3106)] [New Thread -1216156784 (LWP 3167)] (no debugging symbols found) 0x007a3402 in __kernel_vsyscall ()
+ Trace 109655
Thread 1 (Thread -1208895792 (LWP 3106))
----------- .xsession-errors (16 sec old) --------------------- ' TeX output 2007.02.10:1937' -> newfile1.ps <tex.pro><texps.pro>. <cmr7.pfb><cmmi7.pfb><cmmi10.pfb>[1] beryl: core: Received winTypeAtom but unable to find the window for the event No framebuffer_object support! (only simple Blur aviable). No fragment_program support! (only simple Blur aviable). No framebuffer_object support! (only simple Blur aviable). No fragment_program support! (only simple Blur aviable). beryl: water: GL_ARB_fragment_program is missing No framebuffer_object support! (only simple Blur aviable). No fragment_program support! (only simple Blur aviable). beryl: water: GL_ARB_fragment_program is missing beryl: water: GL_ARB_fragment_program is missing beryl: water: GL_ARB_fragment_program is missing ** (bug-buddy:9435): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 359005 ***