GNOME Bugzilla – Bug 457948
crash in Tasks: viewing attached jpgs
Last modified: 2007-08-17 13:08:55 UTC
Version: 2.10 What were you doing when the application crashed? viewing attached jpgs 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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 149716992 vsize: 149716992 resident: 61612032 share: 34418688 rss: 61612032 rss_rlim: 4294967295 CPU usage: start_time: 1184763785 rtime: 1792 utime: 1653 stime: 139 cutime:51 cstime: 41 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208441120 (LWP 2890)] [New Thread -1271338096 (LWP 3593)] [New Thread -1301267568 (LWP 2919)] [New Thread -1249965168 (LWP 2914)] (no debugging symbols found) 0x00988402 in __kernel_vsyscall ()
+ Trace 148830
Thread 1 (Thread -1208441120 (LWP 2890))
----------- .xsession-errors (360 sec old) --------------------- localuser:akonstam being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2548 Initializing nautilus-open-terminal extension ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name error getting update info: Cannot open/read repomd.xml file for repository: livna ** Message: <info> You are now connected to the wireless network '2WIRE833'. CalDAV Eplugin starting up ... ** (evolution:2890): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:2890): DEBUG: mailto URL program: evolution camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- --------------------------------------------------
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 457305 ***