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 424485 - crash in Tasks: i was just exiting Evolu...
crash in Tasks: i was just exiting Evolu...
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 13:49 UTC by goan
Modified: 2007-03-30 21:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description goan 2007-03-30 13:49:21 UTC 
What were you doing when the application crashed?
i was just exiting Evolution


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

System: Linux 2.6.20-1.3025.fc7 #1 SMP Wed Mar 28 20:33:47 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 132255744 vsize: 132255744 resident: 27467776 share: 17981440 rss: 27467776 rss_rlim: 4294967295
CPU usage: start_time: 1175262296 rtime: 261 utime: 228 stime: 33 cutime:1 cstime: 2 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 -1209076000 (LWP 3776)]
[New Thread -1247585392 (LWP 3848)]
(no debugging symbols found)
0x00dd3402 in __kernel_vsyscall ()

+ Trace 123514

Thread 1 (Thread -1209076000 (LWP 3776))

  • #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
  • #12 ??
  • #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 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #18 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #19 ??
    from /lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #21 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #22 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
BottomRight
Sending reload event...
CalDAV Eplugin starting up ...
** (evolution:3776): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3776): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:3776): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(gaim:3110): Bonobo-WARNING **: Leaked a total of 1 refs to 1 bonobo object(s)
CalDAV Eplugin starting up ...
(evolution:3776): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
process 3776: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection.
  D-Bus not built with -rdynamic so unable to print a backtrace
--------------------------------------------------
Comment 1 Susana 2007-03-30 21:04:31 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 ***