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 476440 - 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
aklapper[fc7]
Depends on:
Blocks:
 
 
Reported: 2007-09-13 05:33 UTC by Are Gravbrøt
Modified: 2007-09-20 16:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Are Gravbrøt 2007-09-13 05:33:13 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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 548937728 vsize: 548937728 resident: 39784448 share: 30597120 rss: 39784448 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189661557 rtime: 101 utime: 84 stime: 17 cutime:2 cstime: 8 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 46912496382096 (LWP 32458)]
[New Thread 1115699536 (LWP 32538)]
[New Thread 1094719824 (LWP 32500)]
(no debugging symbols found)
0x00000033b240d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496382096 (LWP 32458))

  • #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 (23 sec old) ---------------------
xscreensaver: 18:21:47: 0: for window 0x340307b (gnome-terminal / Gnome-terminal)
xscreensaver: 18:29:49: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 18:29:49: 0: for window 0x3400020 (gnome-terminal / Gnome-terminal)
gnome-screensaver-command: activating and locking.
flurry: warning: blocked event processing for 18.3 secs!
flurry: warning: only 9% idle over the last 23 secs (at 9.2 FPS)
flurry: warning: blocked event processing for 18.3 secs!
flurry: warning: only 9% idle over the last 23 secs (at 9.1 FPS)
XIO:  fatal IO error 10 (No child processes) on X server ":0.0"
      after 183001 requests (183000 known processed) with 0 events remaining.
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:32458): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:32458): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Kjartan Maraas 2007-09-19 18:18:46 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-09-20 16:55:28 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 ***