After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 508504 - crash in Tasks: Coonect to a Exchange se...
crash in Tasks: Coonect to a Exchange se...
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-10 12:45 UTC by ccarl
Modified: 2008-02-25 06:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description ccarl 2008-01-10 12:45:05 UTC 
Version: 2.10

What were you doing when the application crashed?
Coonect to a Exchange server using IMAP


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 114855936 vsize: 114855936 resident: 45887488 share: 31838208 rss: 45887488 rss_rlim: 4294967295
CPU usage: start_time: 1199968764 rtime: 510 utime: 344 stime: 166 cutime:0 cstime: 0 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 -1209047328 (LWP 2990)]
[New Thread -1294382192 (LWP 3108)]
[New Thread -1230271600 (LWP 2999)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 184787

Thread 2 (Thread -1294382192 (LWP 3108))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 __nptl_deallocate_tsd
    from /lib/libpthread.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6 


----------- .xsession-errors ---------------------
(evolution:2990): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8b5f000'
(evolution:2990): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8b5f120'
Window manager warning: last_user_time (1673099301) is greater than comparison timestamp (1673098412).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x32014da (Evolution ) appears to be one of the offending windows with a timestamp of 1673099301.  Working around...
(evolution:2990): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:2990): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8b5f240'
(evolution:2990): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8b5f360'
(evolution:2990): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Could not connect to securemail.edmc.edu: Connection refused
--------------------------------------------------
Comment 1 Tobias Mueller 2008-02-25 06:42:48 UTC 
Dear Reporter,

thanks for you bugreport :)
This particular bug is very likely to
be the fedora specific bug 447591 where 
   GLib-GObject-WARNING **: gsignal.c:1669: signal
   `source_selected' is invalid for instance
indicates some memory corruption. Hence marking this as dup of bug 447591.

Feel free to report more bugs ;-)

*** This bug has been marked as a duplicate of 447591 ***