GNOME Bugzilla – Bug 431396
crash in 3x?? / g_s/g_s / g_slist_remove / ?? / g_cclosure_marshal_VOID__VOID
Last modified: 2008-02-27 20:49:45 UTC
What were you doing when the application crashed? Viewing the inbox of an IMAP mail box with 2061 new messages, and then clicking the "Date" header to sort by Date. Distribution: Fedora release 6.92 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3084.fc7 #1 SMP Tue Apr 17 17:18:51 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 186425344 vsize: 186425344 resident: 48541696 share: 22052864 rss: 48541696 rss_rlim: 4294967295 CPU usage: start_time: 1176999947 rtime: 914 utime: 645 stime: 269 cutime:40 cstime: 113 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208776992 (LWP 7900)] [New Thread -1344275568 (LWP 7990)] [New Thread -1280316528 (LWP 7984)] [New Thread -1210877040 (LWP 7934)] [New Thread -1269826672 (LWP 7922)] (no debugging symbols found) 0x00f08402 in __kernel_vsyscall ()
+ Trace 129052
Thread 1 (Thread -1208776992 (LWP 7900))
----------- .xsession-errors (96 sec old) --------------------- (evolution:7900): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x905c138' (evolution:7900): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 ** (evolution:7900): WARNING **: Unexpected kerberos error -1765328230 (evolution:7900): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:7900): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:7900): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__uwe@https:__mail.datek.no_exchange_' (evolution:7900): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:7900): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:7900): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:7900): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:7900): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:7900): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 437482 has been marked as a duplicate of this bug. ***
*** Bug 446734 has been marked as a duplicate of this bug. ***
*** Bug 452201 has been marked as a duplicate of this bug. ***
*** Bug 452299 has been marked as a duplicate of this bug. ***
Hy Tom Thanks for your help! I'm using Evolution (on Fedora 7) on different machines (desktop and laptop). on desktop without evolution-connector plugin (exchange-connections) i havent seen any troubles so far. this crash reported here, i havent discovered also on my laptop on which it happened...there i use the evolution-connector "plugin" to connect to a exchange server. what i've seen there is, that the complention of a typed email-address (when writing a mail) cannot be done with TAB ...completing email-addresses with TAB doesn't work so stable....when i'm using RETURN instead it works fine. I'll let you know if I discover the crash again...(hopefully with your requested information). best regards, rolf linder
*** Bug 443625 has been marked as a duplicate of this bug. ***
*** Bug 470527 has been marked as a duplicate of this bug. ***
*** Bug 473637 has been marked as a duplicate of this bug. ***
*** Bug 457874 has been marked as a duplicate of this bug. ***
*** Bug 473443 has been marked as a duplicate of this bug. ***
*** Bug 471968 has been marked as a duplicate of this bug. ***
*** Bug 470121 has been marked as a duplicate of this bug. ***
*** Bug 467913 has been marked as a duplicate of this bug. ***
*** Bug 466619 has been marked as a duplicate of this bug. ***
*** Bug 466501 has been marked as a duplicate of this bug. ***
*** Bug 462552 has been marked as a duplicate of this bug. ***
*** Bug 479014 has been marked as a duplicate of this bug. ***
*** Bug 480073 has been marked as a duplicate of this bug. ***
*** Bug 475741 has been marked as a duplicate of this bug. ***
*** Bug 475320 has been marked as a duplicate of this bug. ***
*** Bug 481487 has been marked as a duplicate of this bug. ***
*** Bug 487115 has been marked as a duplicate of this bug. ***
*** Bug 483890 has been marked as a duplicate of this bug. ***
*** Bug 488216 has been marked as a duplicate of this bug. ***
*** Bug 489588 has been marked as a duplicate of this bug. ***
*** Bug 490580 has been marked as a duplicate of this bug. ***
*** Bug 490744 has been marked as a duplicate of this bug. ***
*** Bug 491136 has been marked as a duplicate of this bug. ***
*** Bug 491140 has been marked as a duplicate of this bug. ***
*** Bug 490138 has been marked as a duplicate of this bug. ***
*** Bug 490127 has been marked as a duplicate of this bug. ***
*** Bug 489101 has been marked as a duplicate of this bug. ***
*** Bug 487571 has been marked as a duplicate of this bug. ***
*** Bug 478593 has been marked as a duplicate of this bug. ***
*** Bug 491416 has been marked as a duplicate of this bug. ***
Are there any usable backtraces for this bug? Perhaps in one of the dupes?
Matthew: No duplicate has a usable stacktrace. But round about 75% carry this warning: > (evolution:7900): GLib-GObject-WARNING **: gsignal.c:1669: signal > `source_selected' is invalid for instance `0x905c138' Isn't that the fedora specific issue?
Yep, that's the tell tale sign for bug #447591. However that bug didn't cause an immediate crash. It was more like memory corruption and then a crash sometime later. So stacktraces that include that warning will vary. Makes it hard to tell whether a bug is really of dupe of bug #447591 or not, but I'm inclined to just write 'em all off as dupes. The ones that lack any useful debugging info, anyway.
*** Bug 492516 has been marked as a duplicate of this bug. ***
*** Bug 498612 has been marked as a duplicate of this bug. ***
Once look into https://bugzilla.gnome.org/show_bug.cgi?id=494517 ( doubt it is duplicate but just for information )
*** Bug 498870 has been marked as a duplicate of this bug. ***
*** Bug 491732 has been marked as a duplicate of this bug. ***
*** Bug 493876 has been marked as a duplicate of this bug. ***
*** Bug 495506 has been marked as a duplicate of this bug. ***
*** Bug 503116 has been marked as a duplicate of this bug. ***
*** Bug 510404 has been marked as a duplicate of this bug. ***
*** Bug 506764 has been marked as a duplicate of this bug. ***
*** Bug 507160 has been marked as a duplicate of this bug. ***
*** Bug 507168 has been marked as a duplicate of this bug. ***
*** Bug 513916 has been marked as a duplicate of this bug. ***
*** Bug 514155 has been marked as a duplicate of this bug. ***
*** Bug 511494 has been marked as a duplicate of this bug. ***
*** Bug 505893 has been marked as a duplicate of this bug. ***
*** Bug 509344 has been marked as a duplicate of this bug. ***
*** Bug 507640 has been marked as a duplicate of this bug. ***
*** Bug 512017 has been marked as a duplicate of this bug. ***
*** Bug 517466 has been marked as a duplicate of this bug. ***
Closing as per comment #39 *** This bug has been marked as a duplicate of 447591 ***