abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 18780 bytes cmdline: grip comment: Just closed grip.. component: grip Attached file: coredump, 69824512 bytes crash_function: GripUpdate executable: /usr/bin/grip kernel: 2.6.35.11-83.fc14.x86_64 package: grip-1:3.2.0-29.fc13 rating: 4 reason: Process /usr/bin/grip was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1299058888 uid: 500 How to reproduce ----- 1. Close Grip
Created attachment 481821 [details] File: backtrace
Package: grip-1:3.2.0-29.fc13 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Quit grip 2. Crash
Package: grip-1:3.2.0-29.fc13 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start GRip from menu 2. Rip 3 CDs 3. Click on window "X" close button Comment ----- I tried to reproduce this and couldn't; I've no idea how to do so. Here's some more detail: I started GRip, and put a disk in the drive. This resulted in three dialog boxes: * The usual Gnome "Audio Disk" requester * One I've never seen before titled "Removable medium in inserted". This one wanted the same info as the first, but gave me a list, rather than the pop-up menu that the Gnome requester uses. * An untitled error box that read Unable to mount Audio Disc DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered I closed/canceled all three, and continued with GRip. Everything seemed to work; GRip found the disk info on the 'net and displayed it, so it could read the CD. The Rip+Encode operation appeared to proceed normally. It's only when I tried to exit GRip that things went wrong. The only thing that I did differently this time that I haven't done before is encode the tracks as FLAC, rather than OggVorbis.
Arrgh. Fumble fingers strike again. The second box title should be "Removable medium is inserted". Also, I just tried inserting a CD without GRip running, and I got the same three dialog boxes. I have no idea what that's about; I've never seen them before now.
Backtrace analysis found this bug to be similar to bug #728254, closing as duplicate. Bugs which were found to be similar to this bug: bug #602622, bug #628344, bug #728254 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 728254 ***