Bug 474149 – crash in Tasks: b??d zapisu spotkania po...

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 474149 - crash in Tasks: b??d zapisu spotkania po...


Summary:	crash in Tasks: b??d zapisu spotkania po...


Status:	RESOLVED DUPLICATE of bug 470928

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-06 08:10 UTC by biuro
Modified:	2007-09-06 12:07 UTC

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

Description biuro 2007-09-06 08:10:51 UTC

Version: 2.10

What were you doing when the application crashed?
błąd zapisu spotkania
podawany komunikat
niezgodność formatu daty


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 116269056 vsize: 116269056 resident: 49041408 share: 30617600 rss: 49041408 rss_rlim: 4294967295
CPU usage: start_time: 1189065207 rtime: 1706 utime: 1581 stime: 125 cutime:3 cstime: 13 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 -1208174880 (LWP 5528)]
[New Thread -1290208368 (LWP 5602)]
[New Thread -1235952752 (LWP 5588)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 160815

Thread 1 (Thread -1208174880 (LWP 5528))

#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_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libbonoboui-2.so.0
#11 ??
from /lib/libglib-2.0.so.0
#12 bonobo_ui_engine_dispose
from /usr/lib/libbonoboui-2.so.0
#13 ??
from /usr/lib/libbonoboui-2.so.0
#14 ??
#15 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#16 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#18 e_shell_close_all_windows
#19 ??
#20 ??
from /lib/libglib-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /lib/libglib-2.0.so.0
#24 bonobo_main
from /usr/lib/libbonobo-2.so.0
#25 main
#0 __kernel_vsyscall



----------- .xsession-errors (211 sec old) ---------------------
(evolution:5528): e-dateedit.c-WARNING **: time_text:10:01
(evolution:5528): e-dateedit.c-WARNING **: time_text:11:01
(evolution:5528): e-dateedit.c-WARNING **: time_text:10:01
(evolution:5528): e-dateedit.c-WARNING **: time_text:11:01
(evolution:5528): 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?)
(evolution:5528): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x906a000'
(evolution:5528): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x906ab40'
(evolution:5528): evolution-mail-WARNING **: unable to open /home/kasa/.evolution/mail/config/gtkrc-mail-fonts
--------------------------------------------------

Comment 1 palfrey 2007-09-06 12:07:13 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 470928 ***