Bug 479304 – crash in Tasks: Selected Polish language...

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 479304 - crash in Tasks: Selected Polish language...


Summary:	crash in Tasks: Selected Polish language...


Status:	RESOLVED DUPLICATE of bug 434653

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-09-22 16:19 UTC by theant
Modified:	2007-10-29 06:58 UTC

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

Description theant 2007-09-22 16:19:23 UTC

Version: 2.10

What were you doing when the application crashed?
Selected Polish language in spellcheck configuration.


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.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 129798144 vsize: 129798144 resident: 53653504 share: 39034880 rss: 53653504 rss_rlim: 4294967295
CPU usage: start_time: 1190477718 rtime: 733 utime: 679 stime: 54 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 -1208674592 (LWP 6324)]
[New Thread -1311450224 (LWP 6341)]
[New Thread -1271936112 (LWP 6336)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 164672

Thread 1 (Thread -1208674592 (LWP 6324))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free1
from /lib/libglib-2.0.so.0
#9 g_slist_free_1
from /lib/libglib-2.0.so.0
#10 g_slist_remove_all
from /lib/libglib-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_object_unref
from /lib/libgobject-2.0.so.0
#13 gtk_rc_style_unref
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_hash_table_foreach
from /lib/libglib-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_rc_reparse_all_for_settings
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_rc_reparse_all
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#20 ??
from /usr/lib/libgconf-2.so.4
#21 gconf_listeners_notify
from /usr/lib/libgconf-2.so.4
#22 ??
from /usr/lib/libgconf-2.so.4
#23 ??
from /usr/lib/libgconf-2.so.4
#24 ??
from /lib/libglib-2.0.so.0
#25 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#26 ??
from /lib/libglib-2.0.so.0
#27 g_main_loop_run
from /lib/libglib-2.0.so.0
#28 bonobo_main
from /usr/lib/libbonobo-2.so.0
#29 main
#0 __kernel_vsyscall



----------- .xsession-errors (520 sec old) ---------------------
  Resource id:  0x2c01387
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x2c01387
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x2c01387
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x2c01387
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-29 06:58:17 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
the maintainers need more information to fix the bug. Could you please answer
the questions in the other report in order to help the developers?

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