GNOME Bugzilla – Bug 406411
crash in GnoTime Tracking Tool: Viewing an invoice
Last modified: 2007-02-10 15:40:10 UTC
What were you doing when the application crashed? Viewing an invoice 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 18:37:28 EST 2007 ppc64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled Memory status: size: 21598208 vsize: 0 resident: 77701120 share: 0 rss: 77701120 rss_rlim: 0 CPU usage: start_time: 252103044 rtime: 0 utime: 1171120938 stime: 0 cutime:594 cstime: 0 timeout: 526 it_real_value: 0 frequency: 68 Backtrace was generated from '/usr/bin/gnotime' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 4159266816 (LWP 4983)] (no debugging symbols found) 0x0fd00104 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 109544
Thread 1 (Thread 4159266816 (LWP 4983))
----------- .xsession-errors --------------------- Minor opcode: 0 Resource id: 0x260baf5 OggS-SEEK: at 16192 want 520 got 0 (diff-requested -15672) X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1801d7c X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 156 Minor opcode: 6 Resource id: 0x4d OggS-SEEK: at 0 want 64504 got 50752 (diff-requested 64504) OggS-SEEK: at 64064 want 520 got 0 (diff-requested -63544) ** (bug-buddy:4993): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
Thanks for taking the time to report this bug. However, this GnoTime does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome. If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other. Thanks in advance! *** This bug has been marked as a duplicate of 356732 ***