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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 426807

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-09-06 02:30 UTC by asadhasnain
Modified:	2007-09-06 12:05 UTC

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

Description asadhasnain 2007-09-06 02:30:36 UTC

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 112996352 vsize: 112996352 resident: 35553280 share: 20246528 rss: 35553280 rss_rlim: 4294967295
CPU usage: start_time: 1189102850 rtime: 802 utime: 734 stime: 68 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 -1208477984 (LWP 2954)]
[New Thread -1332122736 (LWP 3141)]
[New Thread -1266431088 (LWP 3140)]
[New Thread -1310729328 (LWP 3061)]
(no debugging symbols found)
0x00cd9402 in __kernel_vsyscall ()

+ Trace 160776

Thread 1 (Thread -1208477984 (LWP 2954))

#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_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 pango_layout_line_unref
from /usr/lib/libpango-1.0.so.0
#11 ??
from /usr/lib/libpango-1.0.so.0
#12 pango_layout_set_text
from /usr/lib/libpango-1.0.so.0
#13 ??
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#14 e_clipped_label_set_text
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#15 e_info_label_set_info
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#16 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#17 ??
from /lib/libglib-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 (25 sec old) ---------------------
(evolution:2954): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
Loading "installonlyn" plugin
(evolution:2954): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:2954): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8d5c020'
(evolution:2954): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8d5c140'
(evolution:2954): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2954): camel-pop3-provider-WARNING **: Bad server response: vmysql: sql error[3]: Table 'vpopmail.users' doesn't exist
(evolution:2954): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:2954): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------

Comment 1 palfrey 2007-09-06 12:05:41 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 426807 ***