abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: rhythmbox component: rhythmbox crash_function: IA__gdk_draw_pixbuf executable: /usr/bin/rhythmbox kernel: 2.6.34.6-47.fc13.x86_64 package: rhythmbox-0.12.8-4.fc13 rating: 4 reason: Process /usr/bin/rhythmbox was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1284100040 uid: 500
Created an attachment (id=446443) File: backtrace
Package: rhythmbox-0.12.8-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. After the selected song was finished, programm terminated 2. 3.
Package: rhythmbox-0.12.8-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Rhythmbox crashed presumably when switching to the next song (unknown which, and unknown which format that next song was in, as it was playing random)
Package: rhythmbox-0.12.8-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Didn't do anything. 2. Music was playing and then it stopped. 3. I had noticed that earlier the icon on the panel disappeared, but by hitting the empty space where the icon used to be would still bring up the application. About an hour later the app failed. BTW - I've been reporting these types of failures over the last 2 weeks and should also note that this box is cold booted every morning, thus bringing up a fresh O/S.
Package: rhythmbox-0.12.8-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Play music 2. Edit tags 3. Player plays the song where I just edited the tag and crashed Comment ----- After editing a tag, Rhytmbow switched to this track and crashed immediatly.
Package: rhythmbox-0.12.8-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. No Idea 2. 3.
Package: rhythmbox-0.12.8-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Listening a song
Package: rhythmbox-0.12.8-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Rhythmbox was running on another face of the Compiz cube. 2. The face I was on had VMWare running on it. 3. Suddenly, the music stopped! Comment ----- It's hard to say what you could do to reproduce this. I only know that Rhythmbox crashed! Sorry.
*** Bug 597731 has been marked as a duplicate of this bug. ***
*** Bug 602242 has been marked as a duplicate of this bug. ***
*** Bug 602849 has been marked as a duplicate of this bug. ***
*** Bug 611293 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.