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 468347 - crash in Evolution: Just tried to close evol...
crash in Evolution: Just tried to close evol...
Status: RESOLVED DUPLICATE of bug 364700
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-19 23:42 UTC by lesley.walker
Modified: 2007-09-24 18:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description lesley.walker 2007-08-19 23:42:57 UTC 
What were you doing when the application crashed?
Just tried to close evolution


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 128286720 vsize: 0 resident: 128286720 share: 0 rss: 28618752 rss_rlim: 0
CPU usage: start_time: 1187559101 rtime: 0 utime: 217 stime: 0 cutime:200 cstime: 0 timeout: 17 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232714064 (LWP 4891)]
[New Thread -1304855648 (LWP 4962)]
[New Thread -1282409568 (LWP 4956)]
[New Thread -1272218720 (LWP 4954)]
[New Thread -1263813728 (LWP 4953)]
[New Thread -1254798432 (LWP 4952)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 156449

Thread 1 (Thread -1232714064 (LWP 4891))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
    at main.c line 615
  • #0 __kernel_vsyscall 






Comment 1


lesley.walker





          2007-08-19 23:56:35 UTC
        



I imagine the first things anyone will say in response to this are "check for updates" and "please install XXX debug library".  I'm doing updates now, but if there are other debug packages that will help pin it down, let me know. Evolution goes all stupid on me any time I try to shut it down, and it's rather annoying.






Comment 2


lesley.walker





          2007-08-27 05:32:45 UTC
        



Had another Evolution "stopped responding" incident after doing the latest updates. It only seems to happen after it's been running for a while (most recently, over the weekend). No crash report this time, though.






Comment 3


Tobias Mueller





          2007-09-24 18:57:56 UTC
        



You could attach a gdb to the running evolution and get a backtrace then :)

To check whether you have sufficient debug information, check for the question marks as in here:
No symbol table info available.




+
Trace
    165159






    

  • 
#3
??

    • 

  • 
#28
camel_session_get_service_connected

    
                from
                /usr/lib/libcamel-provider-1.2.so.8

    

    • 

  • 
#29
thread_dispatch

    
                at e-msgport.c
                  line
                  987

    

    • 








Anyway, this particular bug is a dup, so marking it as such.

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