GNOME Bugzilla – Bug 494517
crash in Tasks: In settings I set time t...
Last modified: 2007-12-10 00:36:23 UTC
Version: 2.10 What were you doing when the application crashed? In settings I set time to mark a message as read to 0,0 s and clicked OK Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 143073280 vsize: 143073280 resident: 69197824 share: 33415168 rss: 69197824 rss_rlim: 4294967295 CPU usage: start_time: 1194425072 rtime: 15813 utime: 10763 stime: 5050 cutime:105 cstime: 160 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208633632 (LWP 2956)] [New Thread -1238369392 (LWP 2988)] [New Thread -1259349104 (LWP 2980)] 0x00110402 in __kernel_vsyscall ()
+ Trace 175987
Thread 1 (Thread -1208633632 (LWP 2956))
----------- .xsession-errors (7 sec old) --------------------- (evolution:2956): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97e7010' (evolution:2956): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97e7130' X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x140228b X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x140228b X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 157 Minor opcode: 6 Resource id: 0x1a5 --------------------------------------------------
Thanks for taking the time to report this bug. It's most likely that this particular bug is the fedora specific bug 447591: GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance 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. As GLib debug symbols are missing, it's just a guess anyway since we can't determine the issue without debug information. Feel free to install debug information and open a new bug. See http://live.gnome.org/GettingTraces for details *** This bug has been marked as a duplicate of 447591 ***