Bug 446379 – crash in Tasks: Trying to open a new mes...

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 446379 - crash in Tasks: Trying to open a new mes...


Summary:	crash in Tasks: Trying to open a new mes...


Status:	RESOLVED DUPLICATE of bug 431459

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-11 14:10 UTC by m3freak
Modified:	2007-06-17 22:07 UTC

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

Description m3freak 2007-06-11 14:10:09 UTC

What were you doing when the application crashed?
Trying to open a new message


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 119365632 vsize: 119365632 resident: 37740544 share: 30412800 rss: 37740544 rss_rlim: 4294967295
CPU usage: start_time: 1181570932 rtime: 154 utime: 137 stime: 17 cutime:0 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 -1208244512 (LWP 3684)]
[New Thread -1296663664 (LWP 3731)]
[New Thread -1241986160 (LWP 3706)]
[New Thread -1231103088 (LWP 3705)]
(no debugging symbols found)
0x00da0402 in __kernel_vsyscall ()

+ Trace 140068

Thread 1 (Thread -1208244512 (LWP 3684))

#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_loop_run
from /lib/libglib-2.0.so.0
#8 bonobo_main
from /usr/lib/libbonobo-2.so.0
#9 main
#0 __kernel_vsyscall



----------- .xsession-errors (76 sec old) ---------------------
alarm-queue.c:585 (load_alarms_for_today) - From Mon Jun 11 10:06:03 2007
 to Mon Jun 11 10:06:03 2007
alarm-queue.c:522 (load_alarms) 
alarm-queue.c:551 (load_alarms) - Setting Call backs 
alarm-notify.c:316 (cal_opened_cb) file:///home/ksandhu/.evolution/tasks/local/system - Calendar Status 0
alarm-queue.c:1998 (alarm_queue_add_async) - 0x86edcc0
alarm-queue.c:585 (load_alarms_for_today) - From MCalDAV Eplugin starting up ...
(evolution:3684): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
** (evolution:3684): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3684): 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:3684): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3684): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1
--------------------------------------------------

Comment 1 André Klapper 2007-06-17 22:07:59 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 431459 ***