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 213169 - Crash: Fatal Evolution!
Crash: Fatal Evolution!
Status: RESOLVED DUPLICATE of bug 243160
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2001-10-22 14:33 UTC by nagajuna
Modified: 2003-05-16 17:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description nagajuna 2001-10-22 06:33:37 UTC
Package: Evolution
Priority: Critical
Version: 0.15
Synopsis: Fatal Evolution!
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:

Evolution mail crashed during powerup of evo itself.

Thanks



Debugging Information:

[New Thread 1024 (LWP 2536)]
[New Thread 2049 (LWP 2569)]
[New Thread 1026 (LWP 2570)]
0x40b62519 in __wait4 () from /lib/i686/libc.so.6

Thread 1 (Thread 1024 (LWP 2536))

  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 gnome_segv_handle
    at gnome-init.c line 659
  • #4 segv_redirect
    at main.c line 67
  • #5 pthread_sighandler
    at signals.c line 97
  • #6 <signal handler called>
  • #7 read
    at eval.c line 41
  • #8 __curbrk
    at eval.c line 41
  • #9 _dl_map_object
    at eval.c line 41
  • #10 dl_open_worker
    at dl-open.c line 230
  • #11 _dl_catch_error
    at eval.c line 41
  • #12 _dl_open
    at dl-open.c line 362
  • #13 dlopen_doit
    at dlopen.c line 39
  • #14 _dl_catch_error
    at eval.c line 41
  • #15 _dlerror_run
    at dlerror.c line 130
  • #16 __dlopen_check
    at dlopen.c line 53
  • #17 _g_module_open
    at gmodule-dl.c line 93
  • #18 g_module_open
    at gmodule.c line 231
  • #19 mail_importer_init
    at mail-importer.c line 217
  • #20 owner_set_cb
    at component-factory.c line 684
  • #21 gtk_marshal_NONE__POINTER_POINTER
    at gtkmarshal.c line 340
  • #22 gtk_handlers_run
    at gtksignal.c line 1917
  • #23 gtk_signal_real_emit
    at gtksignal.c line 1477
  • #24 gtk_signal_emit
    at gtksignal.c line 552
  • #25 impl_setOwner
    at evolution-shell-component.c line 317
  • #26 _ORBIT_skel_GNOME_Evolution_ShellComponent_setOwner
    at Evolution-skels.c line 1224
  • #27 ORBit_POA_handle_request
    at orbit_poa.c line 507
  • #28 ORBit_handle_incoming_request
    at server.c line 90
  • #29 ORBit_handle_incoming_message
    at server.c line 160
  • #30 giop_main_handle_connection
    at connection.c line 1211
  • #31 orb_handle_connection
    at oaf-mainloop.c line 69
  • #32 g_io_unix_dispatch
    at giounix.c line 137
  • #33 g_main_dispatch
    at gmain.c line 656
  • #34 g_main_iterate
    at gmain.c line 877
  • #35 g_main_run
    at gmain.c line 935
  • #36 gtk_main
    at gtkmain.c line 524
  • #37 bonobo_main
    at bonobo-main.c line 283
  • #38 main
    at main.c line 141
  • #39 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 gnome_segv_handle
    at gnome-init.c line 659
  • #4 segv_redirect
    at main.c line 67
  • #5 pthread_sighandler
    at signals.c line 97
  • #6 <signal handler called>
  • #7 read
    at eval.c line 41


Unknown reporter: nagajuna@optushome.com.au, changed to bugbuddy-import@ximian.com.

Comment 1 Luis Villa 2001-10-22 17:23:28 UTC
What distribution are you using?
Comment 2 Jeffrey Stedfast 2002-04-23 04:47:41 UTC
Mass close of stale bugs >= 4 months old. Odds are that the reason that the
user's have not responded are because the issues have been fixed in more recent
releases of Evolution. If your issue is still not resolved in Evolution 1.0.4,
please reopen and try to provide any additional information that was requested.

Thank you.
Comment 3 Dan Winship 2003-05-16 17:33:45 UTC

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