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 355492 - crash in Evolution: inline viewing photos
crash in Evolution: inline viewing photos
Status: RESOLVED DUPLICATE of bug 355028
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-11 20:52 UTC by Bengt Thuree
Modified: 2006-09-11 21:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Bengt Thuree 2006-09-11 20:52:44 UTC 
What were you doing when the application crashed?
inline viewing photos


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 140763136 vsize: 0 resident: 140763136 share: 0 rss: 36474880 rss_rlim: 0
CPU usage: start_time: 1157962620 rtime: 0 utime: 5689 stime: 0 cutime:5340 cstime: 0 timeout: 349 it_real_value: 0 frequency: 3

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232144720 (LWP 26502)]
[New Thread -1315329120 (LWP 30026)]
[New Thread -1306526816 (LWP 30024)]
[New Thread -1296516192 (LWP 26539)]
[New Thread -1288123488 (LWP 26514)]
[New Thread -1266926688 (LWP 26512)]
[New Thread -1258108000 (LWP 26510)]
[New Thread -1249678432 (LWP 26508)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72149







Comment 1


André Klapper





          2006-09-11 21:52:28 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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