Bug 450940 – crash in Tasks: Ordenando a caixa mensag...

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 450940 - crash in Tasks: Ordenando a caixa mensag...


Summary:	crash in Tasks: Ordenando a caixa mensag...


Status:	RESOLVED DUPLICATE of bug 431342

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-06-25 15:43 UTC by marcosvfarias
Modified:	2007-07-10 14:04 UTC

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

Description marcosvfarias 2007-06-25 15:43:03 UTC

What were you doing when the application crashed?
Ordenando a caixa mensagens enviadas pelo campo "para"


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 137506816 vsize: 137506816 resident: 23621632 share: 16683008 rss: 23621632 rss_rlim: 4294967295
CPU usage: start_time: 1182786148 rtime: 69 utime: 63 stime: 6 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 -1208776992 (LWP 26424)]
[New Thread -1236423792 (LWP 26430)]
(no debugging symbols found)
0x00f51402 in __kernel_vsyscall ()

+ Trace 143601

Thread 1 (Thread -1208776992 (LWP 26424))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 camel_message_info_ptr
from /usr/lib/libcamel-provider-1.2.so.10
#6 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#7 ??
from /usr/lib/evolution/2.10/libetable.so.0
#8 e_tree_model_value_at
from /usr/lib/evolution/2.10/libetable.so.0
#9 e_table_sorting_utils_tree_sort
from /usr/lib/evolution/2.10/libetable.so.0
#10 ??
from /usr/lib/evolution/2.10/libetable.so.0
#11 ??
from /usr/lib/evolution/2.10/libetable.so.0
#12 ??
from /usr/lib/evolution/2.10/libetable.so.0
#13 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 e_tree_model_node_changed
from /usr/lib/evolution/2.10/libetable.so.0
#19 e_tree_memory_thaw
from /usr/lib/evolution/2.10/libetable.so.0
#20 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#21 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 ??
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /lib/libglib-2.0.so.0
#26 bonobo_main
from /usr/lib/libbonobo-2.so.0
#27 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1408ea0
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x1408ea0
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1408ea1
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x1408ea1
--------------------------------------------------

Comment 1 André Klapper 2007-07-10 14:04:13 UTC

Thanks for taking the time to report this bug.
We are happy to tell you that this bug has been fixed already and that updated Fedora 7 packages are available. For future reference, please make sure that you have installed the latest updates before filing a bug report. Thanks a lot!


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