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 507035 - crash in Tasks: I Enabled the "Group by ...
crash in Tasks: I Enabled the "Group by ...
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-03 14:44 UTC by paglia
Modified: 2008-02-25 06:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description paglia 2008-01-03 14:44:22 UTC 
Version: 2.10

What were you doing when the application crashed?
I Enabled the "Group by threads button"


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.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: 684548096 vsize: 684548096 resident: 62939136 share: 39460864 rss: 62939136 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199363793 rtime: 1526 utime: 1374 stime: 152 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 46912496410768 (LWP 10421)]
[New Thread 1105209680 (LWP 11052)]
[New Thread 1105475920 (LWP 10433)]
[New Thread 1094719824 (LWP 10431)]
(no debugging symbols found)
0x00000032b880d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 183920

Thread 2 (Thread 1105209680 (LWP 11052))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 <signal handler called>
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 ??
    from /lib64/libglib-2.0.so.0
  • #7 __nptl_deallocate_tsd
    from /lib64/libpthread.so.0
  • #8 start_thread
    from /lib64/libpthread.so.0
  • #9 clone
    from /lib64/libc.so.6 


----------- .xsession-errors (123 sec old) ---------------------
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
** (nautilus:4261): WARNING **: Hit unhandled case 31 (Operation cancelled) in fm_report_error_loading_directory
(evolution:10421): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:10421): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:10421): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x86b4b0'
(evolution:10421): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x86b0b0'
--------------------------------------------------
Comment 1 Tobias Mueller 2008-02-25 06:22:30 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 ***