Bug 499708 – crash in Tasks: Startup

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


Summary:	crash in Tasks: Startup


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:	2007-11-26 10:59 UTC by marcos.igutti
Modified:	2007-11-26 21:53 UTC

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

Description marcos.igutti 2007-11-26 10:59:28 UTC

Version: 2.10

What were you doing when the application crashed?
Startup



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.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: HighContrastInverse
Icon Theme: HighContrastInverse

Memory status: size: 144101376 vsize: 144101376 resident: 45826048 share: 36978688 rss: 45826048 rss_rlim: 4294967295
CPU usage: start_time: 1196074649 rtime: 167 utime: 141 stime: 26 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 -1208650016 (LWP 8999)]
[New Thread -1274029168 (LWP 9212)]
[New Thread -1241048176 (LWP 9209)]
[New Thread -1253049456 (LWP 9029)]
[New Thread -1263539312 (LWP 9017)]
[New Thread -1211966576 (LWP 9014)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 179672

Thread 1 (Thread -1208650016 (LWP 8999))

#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 (241220 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
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
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Tobias Mueller 2007-11-26 21:53:54 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 ***