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 424412 - crash in Tasks: Shuting down Evolution w...
crash in Tasks: Shuting down Evolution w...
Status: RESOLVED DUPLICATE of bug 419885
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-30 09:07 UTC by jernestpaschal
Modified: 2007-03-30 21:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jernestpaschal 2007-03-30 09:07:40 UTC 
What were you doing when the application crashed?
Shuting down Evolution while the systems was also doing an initial update of 99 applications!


Distribution: Fedora release 6.92 (Rawhide)
Gnome Release: 2.18.0 2007-03-20 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3023.fc7 #1 SMP Sun Mar 25 22:12:02 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 141807616 vsize: 141807616 resident: 31424512 share: 19107840 rss: 31424512 rss_rlim: 4294967295
CPU usage: start_time: 1175245204 rtime: 645 utime: 542 stime: 103 cutime:43 cstime: 29 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208375584 (LWP 9063)]
[New Thread -1236812912 (LWP 9289)]
(no debugging symbols found)
0x00c95402 in __kernel_vsyscall ()

+ Trace 123461

Thread 1 (Thread -1208375584 (LWP 9063))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 ??
    from /lib/libdbus-1.so.3
  • #8 ??
    from /lib/libdbus-1.so.3
  • #9 dbus_connection_unref
    from /lib/libdbus-1.so.3
  • #10 ??
    from /usr/lib/libnm_glib.so.0
  • #11 e_shell_nm_glib_dispose
    from /usr/bin/evolution
  • #12 ??
    from /usr/bin/evolution
  • #13 g_object_run_dispose
    from /lib/libgobject-2.0.so.0
  • #14 gtk_object_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /usr/bin/evolution
  • #17 ??
  • #18 ??
  • #19 g_source_remove
    from /lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 


----------- .xsession-errors (7 sec old) ---------------------
warning: .dynamic section for "/usr/lib/evolution/2.10/libevolution-widgets-a11y.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/evolution/2.10/libevolution-a11y.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/evolution/2.10/libeutil.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/evolution/2.10/components/libevolution-calendar.so" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/evolution/2.10/components/libevolution-mail.so" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/evolution/2.10/libmenus.so.0" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Susana 2007-03-30 21:03:42 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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