GNOME Bugzilla – Bug 464448
crash in Evolution: Anwendung geschlossen
Last modified: 2007-08-17 08:48:41 UTC
What were you doing when the application crashed? Anwendung geschlossen Distribution: openSUSE 10.2 (X86-64) Gnome Release: 2.18.1 2007-07-19 (SUSE) BugBuddy Version: 2.18.1 System: Linux 2.6.18.2-34-default #1 SMP Mon Nov 27 11:46:27 UTC 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70199902 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Industrial Memory status: size: 711168000 vsize: 711168000 resident: 15831040 share: 21970944 rss: 37801984 rss_rlim: 1793285120 CPU usage: start_time: 1186510705 rtime: 271 utime: 234 stime: 37 cutime:12 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46976564406528 (LWP 5352)] [New Thread 1174718784 (LWP 5390)] [New Thread 1174452544 (LWP 5387)] [New Thread 1166059840 (LWP 5386)] [New Thread 1157667136 (LWP 5385)] [New Thread 1149274432 (LWP 5367)] [New Thread 1107310912 (LWP 5361)] [New Thread 1098918208 (LWP 5360)] [New Thread 1090525504 (LWP 5359)] [New Thread 1082132800 (LWP 5358)] 0x00002ab992a14c5f in waitpid () from /lib64/libpthread.so.0
+ Trace 153542
Thread 1 (Thread 46976564406528 (LWP 5352))
----------- .xsession-errors (673 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 Checking mime type application/pdf Error: Bad named destination value Error: Bad named destination value Error: Bad named destination value Error: Bad named destination value --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 334966 ***