Bug 483638 – 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 483638 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 455180

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-10-05 09:19 UTC by xsilliga
Modified:	2007-10-05 14:06 UTC

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

Description xsilliga 2007-10-05 09:19:17 UTC

Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 132100096 vsize: 132100096 resident: 52187136 share: 35745792 rss: 52187136 rss_rlim: 4294967295
CPU usage: start_time: 1191566192 rtime: 1636 utime: 1523 stime: 113 cutime:1 cstime: 1 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 -1208277280 (LWP 3183)]
[New Thread -1248695408 (LWP 4259)]
[New Thread -1308619888 (LWP 4256)]
[New Thread -1266070640 (LWP 3243)]
[New Thread -1216820336 (LWP 3205)]
(no debugging symbols found)
0x00b32402 in __kernel_vsyscall ()

+ Trace 167920

Thread 1 (Thread -1208277280 (LWP 3183))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free1
from /lib/libglib-2.0.so.0
#9 g_slist_free_1
from /lib/libglib-2.0.so.0
#10 g_slist_remove
from /lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#12 ??
from /lib/libglib-2.0.so.0
#13 g_main_loop_run
from /lib/libglib-2.0.so.0
#14 bonobo_main
from /usr/lib/libbonobo-2.so.0
#15 main
#0 __kernel_vsyscall



----------- .xsession-errors (37 sec old) ---------------------
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
--------------------------------------------------

Comment 1 palfrey 2007-10-05 14:06:15 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 455180 ***