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 446893 - crash in Tasks: Just opening Evolution a...
crash in Tasks: Just opening Evolution a...
Status: RESOLVED DUPLICATE of bug 334966
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-12 21:15 UTC by pablo.portero
Modified: 2007-06-13 11:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description pablo.portero 2007-06-12 21:15:12 UTC 
What were you doing when the application crashed?
Just opening Evolution and quickily closing it again.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

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

Memory status: size: 539959296 vsize: 539959296 resident: 38727680 share: 29863936 rss: 38727680 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181682842 rtime: 109 utime: 97 stime: 12 cutime:40 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496414304 (LWP 3433)]
[New Thread 1126455632 (LWP 3460)]
(no debugging symbols found)
0x00000033c460d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 140464

Thread 1 (Thread 46912496414304 (LWP 3433))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib64/libc.so.6
  • #4 e_shell_window_set_title
  • #5 ??
  • #6 GNOME_Evolution_ShellView_setTitle
    from /usr/lib64/evolution/2.10/libeshell.so.0
  • #7 e_component_view_set_title
    from /usr/lib64/evolution/2.10/libeshell.so.0
  • #8 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /lib64/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #11 ??
    from /lib64/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #13 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #14 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (6 sec old) ---------------------
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
CalDAV Eplugin starting up ...
** (evolution:3259): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3259): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:3259): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3259): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
CalDAV Eplugin starting up ...
** (evolution:3433): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3433): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:3433): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 André Klapper 2007-06-13 11:46:26 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 334966 ***