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 455668 - crash in Tasks: Nothing
crash in Tasks: Nothing
Status: RESOLVED DUPLICATE of bug 431459
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-07-10 19:58 UTC by adam.chiarotto
Modified: 2007-10-14 13:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description adam.chiarotto 2007-07-10 19:58:49 UTC
Version: 2.10

What were you doing when the application crashed?
Nothing		


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.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 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: 613056512 vsize: 613056512 resident: 41848832 share: 30806016 rss: 41848832 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184097514 rtime: 129 utime: 111 stime: 18 cutime:1 cstime: 3 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 46912743885600 (LWP 3018)]
[New Thread 1136679248 (LWP 3072)]
[New Thread 1094719824 (LWP 3041)]
(no debugging symbols found)
0x00002aaaad8a789f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912743885600 (LWP 3018))

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


----------- .xsession-errors (13 sec old) ---------------------
error: The metadata does not have a thumbnail property
** (gsf-office-thumbnailer:2993): CRITICAL **: msole_prop_read: assertion `size >= props[i].offset + 4' failed
error: The metadata does not have a thumbnail property
calling convert '/tmp/.gnome_thumbnail.V84CVT.FTWCVT' +matte -thumbnail 128x128 png:'/tmp/.gnome_thumbnail.V84CVT'
** (gsf-office-thumbnailer:2998): CRITICAL **: msole_prop_read: assertion `size >= props[i].offset + 4' failed
error: The metadata does not have a thumbnail property
CalDAV Eplugin starting up ...
** (evolution:3018): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3018): 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:3018): camel-WARNING **: camel_exception_get_id called with NULL parameter.
--------------------------------------------------
Comment 1 palfrey 2007-07-11 12:43:26 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-10-14 13:20:43 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 431459 ***