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 327331 - Evolution crashed while launching after force kill
Evolution crashed while launching after force kill
Status: RESOLVED DUPLICATE of bug 333603
Product: evolution
Classification: Applications
Component: Calendar
2.6.x
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-01-17 11:57 UTC by Poornima
Modified: 2013-09-13 00:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Poornima 2006-01-17 11:57:05 UTC 
Evolution with exchange acount configured was hanging for some reason. so did pkill evolution.
Then launched evolution, evolution crashed.
Pasting stack traces, based on traces assigning to 'Calendar'.

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1235413312 (LWP 14359)]
[New Thread -1329624160 (LWP 14362)]
[New Thread -1319982176 (LWP 14361)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 65286

Thread 1 (Thread -1235413312 (LWP 14359))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_init_with_popt_table
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_type_check_instance_cast
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #5 reopen_with_auth
    at e-cal.c line 964
  • #6 g_list_copy
    from /opt/gnome/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /opt/gnome/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #10 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #11 main
    at main.c line 606
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-05-12 19:10:20 UTC
        



stacktrace is the same as bug 333603

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