closing the window of an incoming mail (e.g. via ESC-Button) leads to a crash of the application in 1 of 3 occasions

Bug #692958 reported by Holger Sickmann
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: evolution

Excerpt from /var/log/messages:
Dec 21 13:01:06 saturn kernel: [ 484.240931] show_signal_msg: 18 callbacks suppressed
Dec 21 13:01:06 saturn kernel: [ 484.240943] evolution[2130]: segfault at 14 ip 02bbfb46 sp bf92aa30 error 4 in libetable.so.0.0.0[2b51000+7d000]
Dec 21 13:01:53 saturn kernel: [ 530.859427] evolution[2231]: segfault at 83e58962 ip 00a540d0 sp bf98f8e0 error 4 in libgobject-2.0.so.0.2600.0[a2b000+40000]
Dec 21 13:02:09 saturn kernel: [ 546.809876] evolution[2285]: segfault at 2 ip 00fa0b46 sp bfe01470 error 4 in libetable.so.0.0.0[f32000+7d000]
Dec 21 13:02:24 saturn kernel: [ 562.129665] evolution[2321]: segfault at 79726170 ip 0415e957 sp bfc9fde0 error 4 in libetable.so.0.0.0[4141000+7d000]

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu7.1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Dec 21 13:16:13 2010
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: evolution

Revision history for this message
Holger Sickmann (holger-sickmann) wrote :
Revision history for this message
Victor Vargas (kamus) wrote :

I cannot reproduce that issue here with 2.30.3-1ubuntu7.2 release, Please could you upgrade to the latest version included in Ubuntu Maverick and check if this behaviour is still occurring? Thanks.

Changed in evolution (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Holger Sickmann (holger-sickmann) wrote :
Download full text (7.5 KiB)

The error still persists:
Here I have the gdb-output:
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/evolution...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/evolution
[Thread debugging using libthread_db enabled]
[New Thread 0xb7bbfb70 (LWP 7970)]
[New Thread 0xb7324b70 (LWP 7971)]
[New Thread 0xb6b23b70 (LWP 7972)]
[New Thread 0xb3503b70 (LWP 7973)]
[New Thread 0xb2d02b70 (LWP 7974)]
[New Thread 0xb2369b70 (LWP 7975)]
[New Thread 0xb1b68b70 (LWP 7976)]
[New Thread 0xb1367b70 (LWP 7977)]
[Thread 0xb2369b70 (LWP 7975) exited]
[Thread 0xb1b68b70 (LWP 7976) exited]
[Thread 0xb1367b70 (LWP 7977) exited]
[New Thread 0xb1367b70 (LWP 7978)]
[Thread 0xb1367b70 (LWP 7978) exited]
[New Thread 0xb1367b70 (LWP 7979)]
[New Thread 0xb1b68b70 (LWP 7980)]
[New Thread 0xb2369b70 (LWP 7981)]
[New Thread 0xb0b66b70 (LWP 7982)]
[New Thread 0xb0365b70 (LWP 7983)]
[New Thread 0xafb64b70 (LWP 7984)]
[New Thread 0xaf363b70 (LWP 7985)]
[New Thread 0xaeb62b70 (LWP 7986)]
[New Thread 0xae361b70 (LWP 7987)]
[New Thread 0xadb00b70 (LWP 7988)]
[New Thread 0xad2ffb70 (LWP 7989)]
[Thread 0xb0365b70 (LWP 7983) exited]
[Thread 0xae361b70 (LWP 7987) exited]
[Thread 0xadb00b70 (LWP 7988) exited]
[New Thread 0xadb00b70 (LWP 7990)]
[Thread 0xb2369b70 (LWP 7981) exited]
[Thread 0xb0b66b70 (LWP 7982) exited]
[Thread 0xadb00b70 (LWP 7990) exited]
[Thread 0xad2ffb70 (LWP 7989) exited]
[Thread 0xaf363b70 (LWP 7985) exited]
[Thread 0xaeb62b70 (LWP 7986) exited]
[New Thread 0xaeb62b70 (LWP 7991)]
[Thread 0xaeb62b70 (LWP 7991) exited]
[New Thread 0xaeb62b70 (LWP 7992)]
[Thread 0xaeb62b70 (LWP 7992) exited]
[Thread 0xafb64b70 (LWP 7984) exited]
[Thread 0xb3503b70 (LWP 7973) exited]
[New Thread 0xb3503b70 (LWP 7993)]
[New Thread 0xafb64b70 (LWP 7994)]
[Thread 0xafb64b70 (LWP 7994) exited]
[Thread 0xb2d02b70 (LWP 7974) exited]
[New Thread 0xb2d02b70 (LWP 7999)]
[Thread 0xb2d02b70 (LWP 7999) exited]
[New Thread 0xb2d02b70 (LWP 8000)]
[New Thread 0xafb64b70 (LWP 8001)]
[Thread 0xafb64b70 (LWP 8001) exited]
[New Thread 0xafb64b70 (LWP 8002)]
[Thread 0xafb64b70 (LWP 8002) exited]
[New Thread 0xafb64b70 (LWP 8003)]
[Thread 0xb2d02b70 (LWP 8000) exited]
[Thread 0xafb64b70 (LWP 8003) exited]
[New Thread 0xafb64b70 (LWP 8005)]
[New Thread 0xb2d02b70 (LWP 8007)]
[Thread 0xb3503b70 (LWP 7993) exited]
[Thread 0xafb64b70 (LWP 8005) exited]
[New Thread 0xafb64b70 (LWP 8008)]
[Thread 0xafb64b70 (LWP 8008) exited]
[New Thread 0xafb64b70 (LWP 8009)]
[New Thread 0xb3503b70 (LWP 8010)]
[Thread 0xb3503b70 (LWP 8010) exited]
[New Thread 0xb3503b70 (LWP 8011)]
[Thread 0xb3503b70 (LWP 8011) exited]
[New Thread 0xb3503b70 (LWP 8012)]
[Thread 0xafb64b70 (LWP 8009) exited]
[Thread 0xb3503b70 (LWP 8012) exited]
[New Thread 0xb3503b70 (LWP 8013)]
[New ...

Read more...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Theres no symbols there, may you please install evolution-dbgsym, libgtk and libglib dbgsyms and try again? thanks.

Revision history for this message
Holger Sickmann (holger-sickmann) wrote :

I installed the debug-symbols. Attached you can find the gdb-output.
Hopefully it helps.

Revision history for this message
Holger Sickmann (holger-sickmann) wrote :

It seems, that
- only unread mails cause this problem
- the problem arises when such an unread mail is marked as read.

I tried to mark a mail as read, of which i knew, that i have read it.
I didn't know, why it was marked as unread.
When i marked it as read by context-menu the program crashed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for evolution (Ubuntu) because there has been no activity for 60 days.]

Changed in evolution (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.