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 469505 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-23 07:08 UTC by phillip
Modified: 2007-08-23 11:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description phillip 2007-08-23 07:08:48 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.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 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: 586514432 vsize: 586514432 resident: 40894464 share: 28839936 rss: 40894464 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187852917 rtime: 108 utime: 100 stime: 8 cutime:1 cstime: 6 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 46912496369808 (LWP 21709)]
[New Thread 1157658960 (LWP 21737)]
[New Thread 1136679248 (LWP 21735)]
(no debugging symbols found)
0x000000374320d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496369808 (LWP 21709))

  • #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 ---------------------
(npviewer.bin:21622): Gtk-CRITICAL **: gtk_window_resize: assertion `width > 0' failed
Window manager warning: last_user_time (32) is greater than comparison timestamp (2441452833).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE
Window manager warning: 0x1000003 (Top Panel) appears to be one of the offending windows with a timestamp of 32.  Working around...
Window manager warning: last_user_time (32) is greater than comparison timestamp (2441453593).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE
Window manager warning: 0x1000003 (Top Panel) appears to be one of the offending windows with a timestamp of 32.  Working around...
Window manager warning: last_user_time (32) is greater than comparison timestamp (2441457666).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE
Window manager warning: 0x1000003 (Top Panel) appears to be one of the offending windows with a timestamp of 32.  Working around...
Window manager warning: last_user_time (32) is greater than comparison timestamp (2441468332).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE
Window manager warning: 0x1000003 (Top Panel) appears to be one of the offending windows with a timestamp of 32.  Working around...
Window manager warning: last_user_time (32) is greater than comparison timestamp (2441478774).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE
Window manager warning: 0x1000003 (Top Panel) appears to be one of the offending windows with a timestamp of 32.  Working around...
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:21709): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:21709): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Mart Raudsepp 2007-08-23 11:42:33 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 431459 ***