GNOME Bugzilla – Bug 369603
crash in GnoTime Tracking Tool: Clicked Reports -> Daily
Last modified: 2006-11-02 23:06:17 UTC
What were you doing when the application crashed? Clicked Reports -> Daily 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.18-1.2798.fc6 #1 SMP Mon Oct 16 14:39:22 EDT 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- Resource id: 0x4a0001c QColor::setRgb: RGB parameter(s) out of range QColor::setRgb: RGB parameter(s) out of range QColor::setRgb: RGB parameter(s) out of range QColor::setRgb: RGB parameter(s) out of range QColor::setRgb: RGB parameter(s) out of range QColor::setRgb: RGB parameter(s) out of range X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4206bcc (gnotime:9617): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed ** (bug-buddy:10872): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 308510720 vsize: 308510720 resident: 23228416 share: 12849152 rss: 23228416 rss_rlim: -1 CPU usage: start_time: 1162488217 rtime: 269 utime: 219 stime: 50 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 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 46912499244128 (LWP 9617)] (no debugging symbols found) 0x00000031c160d935 in waitpid () from /lib64/libpthread.so.0
+ Trace 82024
Thread 1 (Thread 46912499244128 (LWP 9617))
Thanks for the bug report. However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors at http://sourceforge.net/tracker/?group_id=55463&atid=477103 . Please 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. *** This bug has been marked as a duplicate of 356732 ***