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 457607 - crash in Tasks:
crash in Tasks:
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-17 10:50 UTC by torbjorn.lindahl
Modified: 2007-09-29 00:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description torbjorn.lindahl 2007-07-17 10:50:51 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.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: 577093632 vsize: 577093632 resident: 44482560 share: 34238464 rss: 44482560 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184669439 rtime: 58 utime: 51 stime: 7 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496465600 (LWP 13333)]
[New Thread 1115699536 (LWP 13357)]
[New Thread 1136679248 (LWP 13347)]
[New Thread 1105209680 (LWP 13344)]
(no debugging symbols found)
0x0000003a0e00d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496465600 (LWP 13333))

  • #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 (7 sec old) ---------------------
(eog:13056): GLib-GObject-WARNING **: cannot register existing type `GdkPixbufNonAnimIter'
(eog:13056): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
Multiple segmentation faults occurred; can't display error dialog
ptrace: No such process.
/home/torbjorn/13056: No such file or directory.
No stack.
CalDAV Eplugin starting up ...
(evolution:13333): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one
(evolution:13333): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'
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 André Klapper 2007-08-01 16:33:10 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. Could you please install some debugging packages [1], start the application as normal, 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 in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 Tobias Mueller 2007-09-29 00:06:06 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 ***