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 216941 - Evo-1.0 crash while running in background
Evo-1.0 crash while running in background
Status: RESOLVED DUPLICATE of bug 216453
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2001-12-08 11:05 UTC by tevessen
Modified: 2001-12-11 18:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tevessen 2001-12-08 11:05:55 UTC
Package: Evolution
Priority: P3
Version: 1.0
Synopsis: Evo-1.0 crash while running in background
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Sorry, no further error reproduction description possible. :-(
I had: Killed evo with "killevo", then restarted it, removed an
IMAP server from the server list, changed into my remaining
INBOX and went to Mozilla, browsing the Ximian Bugzilla DB
with having Evolution running in the background. Suddenly,
while browsing, Evolution-Mail crashed. I have Evo set to
fetch my mail every 10 Minutes, so maybe it was just fetching
and crashed.



Debugging Information:

(no debugging symbols found)...[New Thread 1024 (LWP 28971)]
[New Thread 2049 (LWP 28980)]
[New Thread 1026 (LWP 28981)]
[New Thread 3075 (LWP 28983)]
[New Thread 4100 (LWP 28986)]
[New Thread 7173 (LWP 29005)]
0x40b82ee9 in __wait4 ()
   from /lib/i686/libc.so.6

Thread 3 (Thread 1026 (LWP 28981))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 967
  • #2 __pthread_alt_lock
    at restart.h line 34
  • #3 __pthread_mutex_lock
    at mutex.c line 120
  • #4 message_browser_get_type
    at eval.c line 41
  • #5 pthread_sighandler
    at signals.c line 97
  • #6 <signal handler called>
  • #7 timeout_cb
    at camel-remote-store.c line 219
  • #8 mail_receive_uri
    at eval.c line 41
  • #9 mail_msg_wait_all
    at eval.c line 41
  • #10 thread_received_msg
    at e-msgport.c line 469
  • #11 thread_dispatch
    at e-msgport.c line 550
  • #12 pthread_start_thread
    at manager.c line 274


Unknown priority P3. Setting to default priority "Normal".
Unknown reporter: tevessen@pop-koeln.de, changed to bugbuddy-import@ximian.com.

Comment 1 Luis Villa 2001-12-11 16:45:39 UTC
Were you using pop or imap with your autocheck? [bug 216453]
Comment 2 tevessen 2001-12-11 17:54:31 UTC
I've got only a single IMAP folder configured on this
installation (remote is Cyrus IMAPd).
Comment 3 Luis Villa 2001-12-11 18:48:51 UTC

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