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 476588 - crash in Tasks: Just trying to check whe...
crash in Tasks: Just trying to check whe...
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-09-13 15:05 UTC by michael
Modified: 2007-09-27 13:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description michael 2007-09-13 15:05:05 UTC 
Version: 2.10

What were you doing when the application crashed?
Just trying to check whether I have new email (Send & Receive Mail dialog).		


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 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 344801280 vsize: 344801280 resident: 113229824 share: 83165184 rss: 113229824 rss_rlim: 4294967295
CPU usage: start_time: 1189562496 rtime: 17456 utime: 15996 stime: 1460 cutime:399 cstime: 87 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 -1208222992 (LWP 20441)]
[New Thread -1299186800 (LWP 17897)]
[New Thread -1408836720 (LWP 17895)]
[New Thread -1309676656 (LWP 17893)]
[New Thread -1397699696 (LWP 20529)]
[New Thread -1397433456 (LWP 20472)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 162640

Thread 3 (Thread -1408836720 (LWP 17895))

  • #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 (702245 sec old) ---------------------
fixme:process:IsWow64Process (0xffffffff 0x34da74) stub!
fixme:process:IsWow64Process (0xffffffff 0x34dd24) stub!
fixme:process:IsWow64Process (0xffffffff 0x34da70) stub!
fixme:process:IsWow64Process (0xffffffff 0x34da74) stub!
fixme:process:IsWow64Process (0xffffffff 0x34dd24) stub!
fixme:process:IsWow64Process (0xffffffff 0x34da70) stub!
fixme:process:IsWow64Process (0xffffffff 0x34da74) stub!
fixme:process:IsWow64Process (0xffffffff 0x34dd24) stub!
fixme:process:IsWow64Process (0xffffffff 0x34da70) stub!
fixme:process:IsWow64Process (0xffffffff 0x34da74) stub!
fixme:process:IsWow64Process (0xffffffff 0x34dd24) stub!
fixme:process:IsWow64Process (0xffffffff 0x34da70) stub!
fixme:process:IsWow64Process (0xffffffff 0x34da74) stub!
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Kjartan Maraas 2007-09-19 20:58:20 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-27 13:31:59 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 ***