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 490734 - crash in Tasks: Just launched evolution....
crash in Tasks: Just launched evolution....
Status: RESOLVED DUPLICATE of bug 364700
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-10-27 06:39 UTC by berrymansj
Modified: 2007-10-28 17:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description berrymansj 2007-10-27 06:39:04 UTC 
Version: 2.10

What were you doing when the application crashed?
Just launched evolution. Not run on this machine for some time.


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

Memory status: size: 157011968 vsize: 157011968 resident: 53223424 share: 44093440 rss: 53223424 rss_rlim: 4294967295
CPU usage: start_time: 1193466896 rtime: 129 utime: 115 stime: 14 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 -1208961312 (LWP 4453)]
[New Thread -1240601712 (LWP 4457)]
[New Thread -1230095472 (LWP 4456)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 173185

Thread 1 (Thread -1208961312 (LWP 4453))

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


----------- .xsession-errors (1363043 sec old) ---------------------
  Resource id:  0x1e00003
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
X connection to :0.0 broken (explicit kill or server shutdown).
kwin: Fatal IO error: client killed
kicker: sighandler called
ICE default IO error handler doing an exit(), pid = 14613, errno = 0
*** kdesktop got signal 1 (Exiting)
klauncher: Exiting on signal 1
konsole: Fatal IO error: client killed
kdeinit: sending SIGTERM to children.
kdeinit: Exit.
QPaintDevice: Cannot destroy paint device that is being painted
klauncher: Fatal IO error: client killed
X connection to :0.0 broken (explicit kill or server shutdown).
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-28 17:20:24 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 364700 ***