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 226260 - Crash: While importing other mailers
Crash: While importing other mailers
Status: RESOLVED DUPLICATE of bug 221604
Product: evolution
Classification: Applications
Component: Importers
unspecified
Other All
: Normal blocker
: ---
Assigned To: Iain
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-06-14 09:55 UTC by sboharon
Modified: 2002-10-04 18:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description sboharon 2002-06-14 09:55:14 UTC
Package: Evolution
Priority: Normal
Version: 1.0.2
Synopsis: While importing other mailers
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Done nothing but waiting for it to complete.
First time started evo.



Debugging Information:

(no debugging symbols found)...[New Thread 1024 (LWP 2614)]
[New Thread 2049 (LWP 2638)]
[New Thread 1026 (LWP 2639)]
[New Thread 2051 (LWP 2640)]
[New Thread 3076 (LWP 2641)]
[New Thread 6149 (LWP 2711)]
0x40fb9ca9 in __wait4 ()
   from /lib/i686/libc.so.6

Thread 3 (Thread 1026 (LWP 2639))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 __pthread_alt_lock
    at restart.h line 34
  • #3 __pthread_mutex_lock
    at mutex.c line 120
  • #4 message_browser_get_type
  • #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
  • #9 mail_msg_wait_all
  • #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 284


Unknown reporter: sboharon@cisco.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Gerardo Marin 2002-10-04 18:07:31 UTC

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