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 320736 - crash connecting to groupwise7
crash connecting to groupwise7
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other other
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-11-05 03:13 UTC by rodc
Modified: 2005-11-07 09:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description rodc 2005-11-05 03:13:38 UTC
Distribution: Opensuse 10.0
Package: Evolution
Severity: normal
Version: GNOME2.12.0 unspecified
Gnome-Distributor: SUSE
Synopsis: imap4 crash connecting to groupwise7
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
Evolution crashes when it refreshes summary header information on
groupwise 7 imap account

Steps to reproduce the crash:
1. setup evolution as groupwise accnt with soap and imap (not using
ssl)
2. initial download of mail headers appears to work fine
3. continue to browse imap folders or close and re-open evolution and it
will crash upon initiating imap connection

Expected Results:
Should syncronize imap mail headers with server, removing deleted and
grabbing new ones for listing.


How often does this happen?
all the time after initial setup and imap mail download. tested with multiple 
users on same machine


Additional Information:
opensuse 10.0 and evolution 2.4.0-0.3.2 from YOU, also happens in both
gnome and KDE




Debugging Information:

Backtrace was generated from '/opt/gnome/bin/evolution-2.4'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread 1096986336 (LWP 15096)]
[New Thread 1249823664 (LWP 15110)]
[Thread debugging using libthread_db enabled]
[New Thread 1096986336 (LWP 15096)]
[New Thread 1249823664 (LWP 15110)]
[Thread debugging using libthread_db enabled]
[New Thread 1096986336 (LWP 15096)]
[New Thread 1249823664 (LWP 15110)]
[New Thread 1160317872 (LWP 15109)]
[New Thread 1158216624 (LWP 15108)]
[New Thread 1155722160 (LWP 15107)]
[New Thread 1153620912 (LWP 15105)]
[New Thread 1151019952 (LWP 15099)]
[New Thread 1148525488 (LWP 15098)]
0xffffe410 in __kernel_vsyscall ()

Thread 5 (Thread 1155722160 (LWP 15107))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/libc.so.6
  • #6 abort
    from /lib/tls/libc.so.6
  • #7 g_logv
    from /opt/gnome/lib/libglib-2.0.so.0
  • #8 g_log
    from /opt/gnome/lib/libglib-2.0.so.0
  • #9 groupwise_folder_item_to_msg
    at camel-groupwise-folder.c line 1394
  • #10 groupwise_refresh_folder
    at camel-groupwise-folder.c line 1125
  • #11 groupwise_refresh_info
    at camel-groupwise-folder.c line 799
  • #12 camel_folder_refresh_info
    from /opt/gnome/lib/libcamel-provider-1.2.so.6
  • #13 mail_check_service
    from /opt/gnome/lib/evolution/2.4/components/libevolution-mail.so
  • #14 mail_enable_stop
    from /opt/gnome/lib/evolution/2.4/components/libevolution-mail.so
  • #15 thread_dispatch
    at e-msgport.c line 826
  • #16 start_thread
    from /lib/tls/libpthread.so.0
  • #17 clone
    from /lib/tls/libc.so.6
  • #18 ??




------- Bug moved to this database by unknown@gnome.bugs 2005-11-05 03:13 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was rodc@ravenet.ca.

Comment 1 André Klapper 2005-11-05 11:10:06 UTC
hi rodc,
thanks for reporting.
adding version number.
Comment 2 Jeffrey Stedfast 2005-11-05 15:30:31 UTC
this has nothing to do with imap4, the groupwise protocol != imap
Comment 3 Subodh Soni 2005-11-07 08:49:22 UTC
Confirming the bug as I didn't find any stack traces similar to the one present
in this bug report.
Comment 4 parthasarathi susarla 2005-11-07 09:17:56 UTC
Fix committed to head.