Bug 496066 – crash in Tasks: typing

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 496066 - crash in Tasks: typing


Summary:	crash in Tasks: typing


Status:	RESOLVED DUPLICATE of bug 501900

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-11-12 06:53 UTC by campaign5
Modified:	2007-12-10 06:22 UTC

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

Description campaign5 2007-11-12 06:53:23 UTC

Version: 2.10

What were you doing when the application crashed?
typing


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.18-8.1.15.el5xen #1 SMP Mon Oct 22 09:01:12 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 60900000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 765911040 vsize: 765911040 resident: 85516288 share: 49049600 rss: 85516288 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194821020 rtime: 2337 utime: 1977 stime: 360 cutime:0 cstime: 5 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 46912496390288 (LWP 21131)]
[New Thread 1084229968 (LWP 21363)]
[New Thread 1105475920 (LWP 21140)]
(no debugging symbols found)
0x0000003e39a0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 177149

Thread 1 (Thread 46912496390288 (LWP 21131))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_utf8_offset_to_pointer
from /lib64/libglib-2.0.so.0
#4 ??
from /usr/lib64/libedataserverui-1.2.so.8
#5 ??
from /usr/lib64/libedataserverui-1.2.so.8
#6 ??
from /usr/lib64/libedataserverui-1.2.so.8
#7 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#8 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#9 ??
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit
from /lib64/libgobject-2.0.so.0
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#17 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#18 ??
from /lib64/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#20 g_signal_emit
from /lib64/libgobject-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#24 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#25 ??
from /lib64/libglib-2.0.so.0
#26 g_main_loop_run
from /lib64/libglib-2.0.so.0
#27 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#28 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (5513 sec old) ---------------------
  Minor opcode:  0
  Resource id:  0x1a0ba33
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x24183c3
index:0
in emp_apps_open_in
DEBUG: Inbox/scruitneer training (mbox:/home/campaign5/.evolution/mail/local#Inbox/scruitneer%20training)
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x24195b2
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2007-12-10 06:22:23 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 501900 ***