Bug 372622 – crash in Evolution: deleting an attachment f...

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 372622 - crash in Evolution: deleting an attachment f...


Summary:	crash in Evolution: deleting an attachment f...


Status:	RESOLVED DUPLICATE of bug 357492

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-08 19:54 UTC by jd
Modified:	2006-11-08 21:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description jd 2006-11-08 19:54:23 UTC

What were you doing when the application crashed?
deleting an attachment from the attachment list of a compose window


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 512458752 vsize: 512458752 resident: 102035456 share: 25677824 rss: 102035456 rss_rlim: -1
CPU usage: start_time: 1163013736 rtime: 6079 utime: 5516 stime: 563 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

(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 47961949240640 (LWP 26350)]
[New Thread 1132755280 (LWP 26790)]
[New Thread 1141147984 (LWP 26789)]
[New Thread 1124362576 (LWP 26512)]
[New Thread 1107577168 (LWP 26391)]
[New Thread 1115969872 (LWP 26386)]
[New Thread 1090525520 (LWP 26373)]
[New Thread 1099184464 (LWP 26371)]
[New Thread 1090791760 (LWP 26364)]
[New Thread 1082132816 (LWP 26358)]
(no debugging symbols found)
0x00002b9efea695cf in waitpid () from /lib/libc.so.6

+ Trace 84479

Thread 10 (Thread 1082132816 (LWP 26358))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Thread 8 (Thread 1099184464 (LWP 26371))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Thread 7 (Thread 1090525520 (LWP 26373))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Thread 6 (Thread 1115969872 (LWP 26386))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Thread 5 (Thread 1107577168 (LWP 26391))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Thread 3 (Thread 1141147984 (LWP 26789))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Thread 2 (Thread 1132755280 (LWP 26790))

#0 select
from /lib/libc.so.6
#1 e_msgport_wait
from /usr/lib64/libedataserver-1.2.so.7
#2 e_msgport_reply
from /usr/lib64/libedataserver-1.2.so.7
#3 start_thread
from /lib/libpthread.so.0
#4 clone
from /lib/libc.so.6
#5 ??

Comment 1 Karsten Bräckelmann 2006-11-08 21:42:00 UTC

Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue.

However, according to the description this is the same issue as bug 357492.


Just in case you can reproduce this crash later, please consider installing
debugging packages [1], which help a lot in tracking down the crash.  Thanks!

Also, please feel free to report any further bugs you find.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions


*** This bug has been marked as a duplicate of 357492 ***