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 421685 - crash in Evolution: started it
crash in Evolution: started it
Status: RESOLVED DUPLICATE of bug 425129
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-22 22:43 UTC by kfirufk
Modified: 2007-04-03 10:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description kfirufk 2007-03-22 22:43:03 UTC
What were you doing when the application crashed?
started it


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.0 2007-03-22 (Gentoo)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-ck1 #4 SMP Fri Mar 23 07:07:48 IST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 410607616 vsize: 410607616 resident: 27488256 share: 16801792 rss: 27488256 rss_rlim: 18446744073709551615
CPU usage: start_time: 1174668132 rtime: 95 utime: 87 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.10'

(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 48004446790896 (LWP 19699)]
0x00002ba8e6b4c52e in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 48004446790896 (LWP 19699))

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


----------- .xsession-errors ---------------------
Bonobo-Activation-Message: About to register 'OAFIID:GNOME_Evolution_Shell:2.10': 0x619f00
Bonobo-Activation-Message: registration of 'OAFIID:GNOME_Evolution_Shell:2.10' returns (success)
Bonobo-Activation-Message: Successfully registered `OAFIID:GNOME_Evolution_Shell:2.10'
(evolution-2.10:19699): Gtk-WARNING **: Theme directory  of theme crystalsvg has no size field
util: Writing file blist.xml to directory /home/ufk/.gaim
(evolution-2.10:19699): e-data-server-DEBUG: Loaded default categories
(evolution-2.10:19699): Gtk-WARNING **: Theme directory  of theme crystalsvg has no size field
msn: S: SB 014: MSG shlomovanunu@hotmail.com Shlomo 97
(bug-buddy:19734): Gtk-WARNING **: Theme directory  of theme crystalsvg has no size field
--------------------------------------------------
Comment 1 palfrey 2007-04-03 10:49:01 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 425129 ***