Bug 508308 – crash in Tasks: nothing special doing so...

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 508308 - crash in Tasks: nothing special doing so...


Summary:	crash in Tasks: nothing special doing so...


Status:	RESOLVED DUPLICATE of bug 447591

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:	2008-01-09 14:45 UTC by yasir
Modified:	2008-02-25 06:24 UTC

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

Description yasir 2008-01-09 14:45:00 UTC

Version: 2.10

What were you doing when the application crashed?
nothing special doing some programmin gin another application


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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 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: 149573632 vsize: 149573632 resident: 54595584 share: 40505344 rss: 54595584 rss_rlim: 4294967295
CPU usage: start_time: 1199889799 rtime: 660 utime: 583 stime: 77 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208445216 (LWP 16809)]
[New Thread -1249498224 (LWP 16957)]
[New Thread -1321804912 (LWP 16954)]
[New Thread -1270887536 (LWP 16829)]
[New Thread -1238615152 (LWP 16813)]
(no debugging symbols found)
0x0046e402 in __kernel_vsyscall ()

+ Trace 184678

Thread 3 (Thread -1321804912 (LWP 16954))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/i686/nosegneg/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/i686/nosegneg/libpthread.so.0
#3 pthread_mutex_lock
from /lib/i686/nosegneg/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 ??
from /lib/libglib-2.0.so.0
#9 __nptl_deallocate_tsd
from /lib/i686/nosegneg/libpthread.so.0
#10 start_thread
from /lib/i686/nosegneg/libpthread.so.0
#11 clone
from /lib/i686/nosegneg/libc.so.6



----------- .xsession-errors (130 sec old) ---------------------
  Resource id:  0x3e00b4c
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x3e00cd9
(evolution:16809): Gtk-CRITICAL **: gtk_file_system_unix_get_parent: assertion `g_path_is_absolute (filename)' failed
(evolution:16809): 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:16809): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x897a010'
(evolution:16809): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x897a130'
QClipboard: Unknown SelectionClear event received.
--------------------------------------------------

Comment 1 Tobias Mueller 2008-02-25 06:24:03 UTC

Dear Reporter,

thanks for you bugreport :)
This particular bug is very likely to
be the fedora specific bug 447591 where 
   GLib-GObject-WARNING **: gsignal.c:1669: signal
   `source_selected' is invalid for instance
indicates some memory corruption. Hence marking this as dup of bug 447591.

Feel free to report more bugs ;-)

*** This bug has been marked as a duplicate of 447591 ***