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 463341 - crash in Tasks: I gave a send receive co...
crash in Tasks: I gave a send receive co...
Status: RESOLVED DUPLICATE of bug 441638
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-04 05:05 UTC by systemadmin
Modified: 2007-08-10 15:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description systemadmin 2007-08-04 05:05:42 UTC 
What were you doing when the application crashed?
I gave a send receive command, application crashed.		


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 134434816 vsize: 134434816 resident: 34340864 share: 20365312 rss: 34340864 rss_rlim: 4294967295
CPU usage: start_time: 1186203363 rtime: 841 utime: 731 stime: 110 cutime:65 cstime: 35 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 -1208453408 (LWP 10610)]
[New Thread -1281561712 (LWP 10884)]
[New Thread -1303188592 (LWP 10818)]
[New Thread -1249547376 (LWP 10665)]
[New Thread -1229653104 (LWP 10632)]
(no debugging symbols found)
0x009e1402 in __kernel_vsyscall ()

+ Trace 152705

Thread 2 (Thread -1281561712 (LWP 10884))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 g_slice_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #10 g_slist_free
    from /lib/libglib-2.0.so.0
  • #11 g_strsplit
    from /lib/libglib-2.0.so.0
  • #12 camel_uid_cache_new
    from /usr/lib/libcamel-provider-1.2.so.10
  • #13 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 start_thread
    from /lib/libpthread.so.0
  • #18 clone
    from /lib/libc.so.6 


----------- .xsession-errors (1264 sec old) ---------------------
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
/usr/bin/beryl: water: GL_ARB_fragment_program is missing
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2007-08-10 15:41:02 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 441638 ***