abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: gpilotd-control-applet --druid component: gnome-pilot crash_function: vasprintf executable: /usr/bin/gpilotd-control-applet kernel: 2.6.35.9-64.fc14.x86_64 package: gnome-pilot-2.32.0-1.fc14 rating: 4 reason: Process /usr/bin/gpilotd-control-applet was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1292922446 uid: 500 How to reproduce ----- 1. Dobavlyal applety v novyu systemu 2. 3.
Created attachment 469937 [details] File: backtrace
Package: gnome-pilot-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. soso 2. 3.
Package: gnome-pilot-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. To be honest, I'm not sure what caused this. It hasn't happened before. 2. Sytem was showing very high IO wait for a significant amount of time (70%+ CPU for 30+ seconds) 3. Restarted Gnome Pilot Applet which was 'red' , showing it was not ready. A carsh resulted and the gnome pilot applet showed normal "ready to synchronise" status
Package: gnome-pilot-2.32.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. ho connesso il mio zire31 2. ho avviato la sincronizzazione che è partita ma si è inceppata 3. ho riavviato il gnome-pilot 4. è avvenuto il crash
Backtrace analysis found this bug to be similar to bug #701139, closing as duplicate. Bugs which were found to be similar to this bug: gnome-pilot: bug #654510, bug #695099, bug #701139 menu-cache: bug #556296, bug #558303 rygel: bug #667231 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 701139 ***