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 483052 - crash in Tasks: Send and Receive message...
crash in Tasks: Send and Receive message...
Status: RESOLVED DUPLICATE of bug 364700
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-03 18:52 UTC by altafin
Modified: 2007-10-05 10:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description altafin 2007-10-03 18:52:19 UTC
Version: 2.10

What were you doing when the application crashed?
Send and Receive messages. Just open Evolution


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 208863232 vsize: 208863232 resident: 35278848 share: 27283456 rss: 35278848 rss_rlim: 4294967295
CPU usage: start_time: 1191437476 rtime: 112 utime: 101 stime: 11 cutime:0 cstime: 1 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 -1208514848 (LWP 5565)]
[New Thread -1407784048 (LWP 5625)]
[New Thread -1397294192 (LWP 5620)]
[New Thread -1386804336 (LWP 5618)]
[New Thread -1376314480 (LWP 5616)]
[New Thread -1365824624 (LWP 5614)]
[New Thread -1344844912 (LWP 5612)]
[New Thread -1323865200 (LWP 5610)]
[New Thread -1302885488 (LWP 5608)]
[New Thread -1229587568 (LWP 5606)]
[New Thread -1252004976 (LWP 5603)]
[New Thread -1241515120 (LWP 5602)]
[New Thread -1218483312 (LWP 5583)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208514848 (LWP 5565))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (17 sec old) ---------------------
(evolution:5180): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9642120'
CalDAV Eplugin starting up ...
** (evolution:5247): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:5247): 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:5247): e-data-server-DEBUG: Loading categories from "/home/altafin/.evolution/categories.xml"
(evolution:5247): e-data-server-DEBUG: Loaded 29 categories
BBDB spinning up...
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:62: error: unexpected identifier `animation', expected character `}'
CalDAV Eplugin starting up ...
** (evolution:5565): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:5565): 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
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-05 10:05:44 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 364700 ***