abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/python /usr/bin/miro.real '/mnt/a2/Caprica S1/Caprica.S01E14.PDTV.XviD-YooX.avi' comment: Seems like a one off occurrence. component: Miro executable: /usr/bin/python kernel: 2.6.34.7-61.fc13.x86_64 package: Miro-3.5-2.fc13 reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1294436992 uid: 500 How to reproduce ----- 1. I had just watched: Caprica.S01E14.PDTV.XviD-YooX.avi and the trailing credits were rolling. 2. I double clicked the window to disable fullscreen, then right clicked on Caprica.S01E15.The.DirtEaters.PDTV.SpaceTV.Nash.avi and said "Open in Miro". 3. The file played for a few seconds, glitched, and Miro died. 4. Immediately after the ABRT popped up, I opened Caprica.S01E15.The.DirtEaters.PDTV.SpaceTV.Nash again, and it played normally.
Created attachment 472326 [details] File: backtrace
Package: Miro-3.5-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- after latest updates in the system Miro segfaults at start. Comment ----- very repeatable. REinstalling Miro rpm does not help.
Package: Miro-3.5-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- does not start after installing latest system updates (Miro was not updated)
Package: Miro-3.5-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- miro segfaults at start after latest update
Package: Miro-3.5-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Miro segfaults at start after recent update, this is under freshly created user
so I don't see much activity here, therefore I've rolled back to Miro-3.0.1-1.fc13.1.x86_64 ================================================================================ Package Arch Version Repository Size ================================================================================ Downgrading: Miro x86_64 3.0.1-1.fc13.1 russianfedora-fixes-updates 2.0 M Installing for dependencies: avahi-glib i686 0.6.25-7.fc13 updates 19 k bzip2-libs i686 1.0.6-1.fc13 updates 36 k gnome-vfs2 i686 2.24.3-1.fc13 fedora 794 k hal-libs i686 0.5.14-3.fc13 fedora 66 k hunspell i686 1.2.8-18.fc13 updates 181 k libacl i686 2.2.49-6.fc13 updates 24 k libnotify i686 0.5.0-1.fc13 updates 35 k nspr i686 4.8.6-1.fc13 updates 112 k nss i686 3.12.8-2.fc13 updates 756 k nss-softokn i686 3.12.8-1.fc13 updates 171 k nss-util i686 3.12.8-1.fc13 updates 45 k startup-notification i686 0.10-4.fc13 fedora 37 k xcb-util i686 0.3.6-1.fc12 fedora 37 k xulrunner i686 1.9.2.4-0.3.build4.fc13 russianfedora-fixes-updates 9.2 M Transaction Summary ================================================================================ Install 14 Package(s) Downgrade 1 Package(s) now Miro works, but can't read the old the database format obviously, therefore I had to backup my all stuff (till better times) and re-signup for channels (if there was a way to automate it).
Package: Miro-3.5-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Opening Miro TV 2. 3.
Package: Miro-3.5-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Started Miro TV 2. 3. Comment ----- Immediately faults.
Package: Miro-3.5-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Start Miro TV 2. 3. Comment ----- This has ocrurred with in the last month
Package: Miro-3.5-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Started Miro 2.System immediately faults 3.
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.