Bug 445755 – crash in Evolution: ничего особенного Ошибка...

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 445755 - crash in Evolution: ничего особенного Ошибка...


Summary:	crash in Evolution: ничего особенного Ошибка...


Status:	RESOLVED DUPLICATE of bug 425129

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-09 13:08 UTC by sgs
Modified:	2007-06-10 19:47 UTC

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

Description sgs 2007-06-09 13:08:57 UTC

What were you doing when the application crashed?
ничего особенного
Ошибка при запуске Evolution появлялась в любом случае


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 78626816 vsize: 78626816 resident: 24031232 share: 15523840 rss: 24031232 rss_rlim: 4294967295
CPU usage: start_time: 1181394548 rtime: 145 utime: 132 stime: 13 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/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237240096 (LWP 14399)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 139572

Thread 1 (Thread -1237240096 (LWP 14399))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/libpthread.so.0
#2 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/i686/libc.so.6
#5 icaltimezone_get_builtin_timezone_from_offset
from /usr/lib/libecal-1.2.so.7
#6 e_timezone_dialog_set_timezone
from /usr/lib/evolution/2.10/libetimezonedialog.so.0
#7 startup_wizard_timezone_page
from /usr/lib/evolution/2.10/plugins/liborg-gnome-evolution-startup-wizard.so
#8 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/evolution/2.10/libeutil.so.0
#9 e_plugin_invoke
from /usr/lib/evolution/2.10/libeutil.so.0
#10 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/evolution/2.10/libeutil.so.0
#11 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/evolution/2.10/libeutil.so.0
#12 e_config_create_widget
from /usr/lib/evolution/2.10/libeutil.so.0
#13 e_config_create_window
from /usr/lib/evolution/2.10/libeutil.so.0
#14 em_account_editor_new
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 startup_wizard
from /usr/lib/evolution/2.10/plugins/liborg-gnome-evolution-startup-wizard.so
#16 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/evolution/2.10/libeutil.so.0
#17 e_plugin_invoke
from /usr/lib/evolution/2.10/libeutil.so.0
#18 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/evolution/2.10/libeutil.so.0
#19 e_event_emit
from /usr/lib/evolution/2.10/libeutil.so.0
#20 e_shell_attempt_upgrade
#21 e_shell_construct
#22 e_shell_new
#23 ??
#24 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 bonobo_main
from /usr/lib/libbonobo-2.so.0
#29 main
#0 __kernel_vsyscall

Comment 1 Pascal Terjan 2007-06-10 19:47:20 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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