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 446762 - crash in Email: nothing, just run fedora...
crash in Email: nothing, just run fedora...
Status: RESOLVED DUPLICATE of bug 425129
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-12 14:41 UTC by avstor
Modified: 2007-06-12 16:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description avstor 2007-06-12 14:41:21 UTC 
What were you doing when the application crashed?
nothing, just run fedora under the vmware workstation


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 94826496 vsize: 94826496 resident: 23453696 share: 15028224 rss: 23453696 rss_rlim: 4294967295
CPU usage: start_time: 1181659237 rtime: 110 utime: 47 stime: 63 cutime:0 cstime: 9 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 -1208322336 (LWP 3021)]
(no debugging symbols found)
0x00431402 in __kernel_vsyscall ()

+ Trace 140365

Thread 1 (Thread -1208322336 (LWP 3021))

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


----------- .xsession-errors (7 sec old) ---------------------
localuser:avstor being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2810
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the ne
CalDAV Eplugin starting up ...
(evolution:3021): e-data-server-DEBUG: Loaded default categories
--------------------------------------------------
Comment 1 palfrey 2007-06-12 16:18:20 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 ***