Bug 512712 – crash in Tasks:

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 512712 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 364700

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-29 04:52 UTC by manu
Modified:	2008-01-29 18:19 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description manu 2008-01-29 04:52:05 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 126242816 vsize: 126242816 resident: 38146048 share: 31588352 rss: 38146048 rss_rlim: 4294967295
CPU usage: start_time: 1201581953 rtime: 33 utime: 29 stime: 4 cutime:0 cstime: 0 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 -1208256800 (LWP 3146)]
[New Thread -1268790384 (LWP 3172)]
[New Thread -1225340016 (LWP 3167)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 187150

Thread 1 (Thread -1208256800 (LWP 3146))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 g_main_context_check
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 g_main_context_iteration
from /lib/libglib-2.0.so.0
#8 link_main_iteration
from /usr/lib/libORBit-2.so.0
#9 giop_recv_buffer_get
from /usr/lib/libORBit-2.so.0
#10 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#11 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#12 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#13 ConfigDatabase2_all_entries_with_schema_name
from /usr/lib/libgconf-2.so.4
#14 gconf_engine_all_entries
from /usr/lib/libgconf-2.so.4
#15 ??
from /usr/lib/libgconf-2.so.4
#16 gconf_client_add_dir
from /usr/lib/libgconf-2.so.4
#17 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#18 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#19 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#20 ??
from /lib/libglib-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /lib/libglib-2.0.so.0
#24 bonobo_main
from /usr/lib/libbonobo-2.so.0
#25 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
localuser:admin being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2963
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
CalDAV Eplugin starting up ...
** (evolution:3146): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3146): 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
--------------------------------------------------

Comment 1 Tobias Mueller 2008-01-29 18:19:48 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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