GNOME Bugzilla – Bug 476666
crash in PalmOS Devices: Getting pilot settings f...
Last modified: 2007-09-14 07:32:10 UTC
What were you doing when the application crashed? Getting pilot settings from the pilot Distribution: Red Hat Enterprise Linux Client release 5 (Tikanga) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 Memory status: size: 51134464 vsize: 0 resident: 51134464 share: 0 rss: 12357632 rss_rlim: 0 CPU usage: start_time: 1189709013 rtime: 0 utime: 58 stime: 0 cutime:52 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gpilotd-control-applet' (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 -1208723232 (LWP 18854)] (no debugging symbols found) 0x0088a410 in __kernel_vsyscall ()
+ Trace 162703
Thread 1 (Thread -1208723232 (LWP 18854))
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 365181 ***