GNOME Bugzilla – Bug 480301
crash in Tasks: double clicked an enclos...
Last modified: 2007-09-29 01:39:13 UTC
Version: 2.10 What were you doing when the application crashed? double clicked an enclosed jpeg to view 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.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 121536512 vsize: 121536512 resident: 47751168 share: 34988032 rss: 47751168 rss_rlim: 4294967295 CPU usage: start_time: 1190737247 rtime: 682 utime: 596 stime: 86 cutime:41 cstime: 15 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 -1208845584 (LWP 3075)] [New Thread -1268003952 (LWP 3793)] [New Thread -1278493808 (LWP 3122)] [New Thread -1217598576 (LWP 3097)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 165419
Thread 1 (Thread -1208845584 (LWP 3075))
----------- .xsession-errors (71 sec old) --------------------- RosegardenSequencerApp::quit() AudioInstrumentMixer::destroyAllPlugins done AudioInstrumentMixer::~AudioInstrumentMixer AudioInstrumentMixer::removeAllPlugins AudioInstrumentMixer::~AudioInstrumentMixer exiting DataBlockRepository::clear() SoundDriver::~SoundDriver (exiting) AudioPlayQueue::~AudioPlayQueue() Toodle-pip. ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave OggS-SEEK: at 60352 want 520 got 0 (diff-requested -59832) OggS-SEEK: at 78400 want 520 got 0 (diff-requested -77880) ICE default IO error handler doing an exit(), pid = 3775, errno = 0 --------------------------------------------------
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 467763 ***