GNOME Bugzilla – Bug 457722
crash in Panel: downloading a file in fi...
Last modified: 2007-07-18 00:18:13 UTC
Version: 2.18.1 What were you doing when the application crashed? downloading a file in firefox Distribution: Frugalware 0.7pre1 (Sayshell) Gnome Release: 2.18.1 2007-04-11 (Frugalware) BugBuddy Version: 2.18.1 System: Linux 2.6.22-fw1 #1 SMP PREEMPT Tue Jul 10 12:45:20 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 34234368 vsize: 34234368 resident: 18239488 share: 12705792 rss: 18239488 rss_rlim: 4294967295 CPU usage: start_time: 1184686904 rtime: 338 utime: 297 stime: 41 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/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 -1226717504 (LWP 2868)] (no debugging symbols found) 0xb7f15410 in __kernel_vsyscall ()
+ Trace 148643
Thread 1 (Thread -1226717504 (LWP 2868))
----------- .xsession-errors (203 sec old) --------------------- Creating GQview dir:/home/fred/.gqview/collections Creating GQview dir:/home/fred/.gqview/thumbnails Creating GQview dir:/home/fred/.gqview/metadata ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (gnome-cups-icon:2880): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 422966 ***