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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 438756

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-08-24 11:16 UTC by sxg6
Modified:	2007-09-21 18:51 UTC

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

Description sxg6 2007-08-24 11:16:59 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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 480714752 vsize: 480714752 resident: 24453120 share: 16232448 rss: 24453120 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187953827 rtime: 75 utime: 62 stime: 13 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496492128 (LWP 3362)]
[New Thread 1084229968 (LWP 3375)]
(no debugging symbols found)
0x00000036f5e0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 157574

Thread 1 (Thread 46912496492128 (LWP 3362))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
#4 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#5 e_table_sorting_utils_tree_sort
from /usr/lib64/evolution/2.10/libetable.so.0
#6 ??
from /usr/lib64/evolution/2.10/libetable.so.0
#7 ??
from /usr/lib64/evolution/2.10/libetable.so.0
#8 ??
from /usr/lib64/evolution/2.10/libetable.so.0
#9 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#10 ??
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#12 g_signal_emit
from /lib64/libgobject-2.0.so.0
#13 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#14 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#15 ??
from /lib64/libglib-2.0.so.0
#16 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#17 ??
from /lib64/libglib-2.0.so.0
#18 g_main_loop_run
from /lib64/libglib-2.0.so.0
#19 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#20 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
startkde: Starting up...
kbuildsycoca running...
CalDAV Eplugin starting up ...
** (evolution:3362): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3362): 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
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x65
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x65
--------------------------------------------------

Comment 1 Suman Manjunath 2007-08-26 18:41:11 UTC

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here.  Thanks!

[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions

Comment 2 Suman Manjunath 2007-09-04 03:24:03 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 438756 ***