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 487118 - crash in Tasks:
crash in Tasks:
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-16 11:09 UTC by rsvcakaiser
Modified: 2007-11-14 13:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description rsvcakaiser 2007-10-16 11:09:34 UTC
Version: 2.10

What were you doing when the application crashed?



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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 183259136 vsize: 183259136 resident: 104427520 share: 34320384 rss: 104427520 rss_rlim: 4294967295
CPU usage: start_time: 1192529904 rtime: 79624 utime: 78956 stime: 668 cutime:0 cstime: 0 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 -1208936736 (LWP 7763)]
[New Thread -1294734448 (LWP 7800)]
[New Thread -1225786480 (LWP 7772)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208936736 (LWP 7763))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 e_iterator_is_valid
    from /usr/lib/libedataserver-1.2.so.9
  • #6 mail_config_get_account_by_source_url
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #7 em_uri_from_camel
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #8 mail_vfolder_add_uri
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #10 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #11 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(evolution:7763): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `EListIterator'
(evolution:7763): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `EListIterator'
(evolution:7763): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `EListIterator'
(evolution:7763): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `EListIterator'
(evolution:7763): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `EListIterator'
(evolution:7763): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(evolution:7763): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(evolution:7763): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2007-10-17 05:19:15 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Comment 2 Akhil Laddha 2007-11-14 13:21:40 UTC
Unfortunately the stacktrace does not have any hints about the real cause of
the crash and does not help in debugging this issue.

For some yet unknown reason, such stacktraces are pretty common currently on
certain distros. However, almost all of them do turn out to be filed already,
once we managed to gather a useful stacktrace. To do so, simply install the
corresponding debugging packages and reproduce the issue, if possible. The
resulting stacktrace (see bug-buddy details) will help us to identify and fix
the issue.

Just in case you ever can reproduce this crash later, please consider
installing debugging packages [1] and either reopen this bug report or simply
file a new one with the resulting stacktrace.  Thanks!

Closing this bug report as no further information has been provided.
Also, please feel free to report any further bugs you find.  Thanks!

thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.4 or later), please reopen. thanks in advance.