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 491405 - crash in Tasks: Reading mail.
crash in Tasks: Reading mail.
Status: RESOLVED DUPLICATE of bug 427105
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-29 15:05 UTC by Braden
Modified: 2007-10-30 11:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Braden 2007-10-29 15:05:03 UTC
Version: 2.10

What were you doing when the application crashed?
Reading mail.


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 20:47:39 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: 1111453696 vsize: 1111453696 resident: 473288704 share: 43139072 rss: 473288704 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193562232 rtime: 29289 utime: 21005 stime: 8284 cutime:760 cstime: 978 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496406672 (LWP 8652)]
[New Thread 1157925200 (LWP 30320)]
[New Thread 1147435344 (LWP 30037)]
[New Thread 1094719824 (LWP 8844)]
[New Thread 1126455632 (LWP 8843)]
[New Thread 1084229968 (LWP 8699)]
0x000000379f40d97f in __libc_waitpid (pid=30321, stat_loc=0x7fff101a92ac, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 2 (Thread 1157925200 (LWP 30320))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 81
  • #3 <signal handler called>
  • #4 slab_allocator_free_chunk
    at gslice.c line 1020
  • #5 magazine_cache_push_magazine
    at gslice.c line 567
  • #6 private_thread_memory_cleanup
    at gslice.c line 665
  • #7 __nptl_deallocate_tsd
    at pthread_create.c line 153
  • #8 start_thread
    at pthread_create.c line 303
  • #9 clone
    from /lib64/libc.so.6


----------- .xsession-errors (76453 sec old) ---------------------
17948] 13:50:27: Checking support for MIT-SHM...
17948] 13:50:27: NOTICE: MIT-SHM available (version 1.1)!
17948] 13:50:27: Your X server expects RGB24 pixmap data for standard mode.
17948] 13:50:27: Created XEmbedded window
17948] 13:50:27: DEBUG: bool gnash::Network::connectSocket(const char*) enter
17948] 13:50:27: ERROR: The connect() socket for fd 5 never was available for writing
17948] 13:50:27: LIRC daemon not running
17948] 13:50:27: X server pixel format is (R16:8, G8:8, B0:8, 32 bpp)
17948] 13:50:27: X server is using BGRA32 pixel format
17948] 13:50:27: framebuffer pixel format is BGRA32 (little-endian host)
17948] 13:50:27: DEBUG: Base url set to: http://view.atdmt.com/MON/iview/rlmddmec0290000075mon/direct/01/7967364?click=http://ad.doubleclick.net/click%3Bh=v8/35f9/3/0/%2a/h%3B140523654%3B0-0%3B0%3B126
17948] 13:50:27: GTK-AGG: Using shared memory image
17948] 13:50:27: initialized AGG buffer <0x2aaab1101000>, 384000 bytes, 160x600, rowsize is 640 bytes
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2007-10-30 04:42:29 UTC
Could be dup of bug 300539
Comment 2 palfrey 2007-10-30 11:22:15 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 427105 ***