abrt 1.0.0 detected a crash. How to reproduce ----- 1. Launch Firefox 2. 3. Comment: This alert came up with the launching of Firefox. There was no significant plugin used that I know of. I was checking the tracking of a FedEx delivery and used a link from an email from them. The alert appeared shortly thereafter. Attached file: backtrace cmdline: /usr/bin/python /usr/bin/miro.real component: python executable: /usr/bin/python kernel: 2.6.31.9-174.fc12.x86_64 package: python-2.6.2-2.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 381305 [details] File: backtrace
Thank you for reporting this bug. The program that's crashing is miro (which I'm not familiar with). How reproducible is this problem? If you run the program from a terminal, is an error message printed? What version of Miro do you have installed? Looking at the backtrace, it looks like the problem occurred in thread #1 in gtk_range_set_value Reassigning component from "python" to "Miro"
Perhaps this is related to bug #551680? Will: any ideas? I've not seen any crashes with miro 2.5.4 myself (although I don't use it nearly as much as I used to).
Hi Mark, Sorry for the slow comeback. The Miro version I have installed is 2.5.4. As for running Miro from the terminal, I haven't had the chance to try that yet. I will get back to you later today or tomorrow morning with my results.
Could you try to see if this problem still recur in Miro-3.0.1 (updates) or Miro-3.0.2? (should be available tomorrow by yum --enablerepo=updates-testing install Miro) Thanks!
Actually, since this is likely to be xulrunner-related, 3.0.2 should fix it
Miro-3.0.2-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/Miro-3.0.2-1.fc13
Miro-3.0.2-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/Miro-3.0.2-1.fc12
Hey Michel, I am not geographically near the machine for the next 3 weeks. This was an issue from January 6. I do not know of any more issues since the updates and all seems fine since 3.0.2+. I will be back to the unit in about three weeks if you want to pursue it then. Cheers!
Miro-3.0.2-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update Miro'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/Miro-3.0.2-1.fc12
Miro-3.0.2-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update Miro'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/Miro-3.0.2-1.fc13
(In reply to comment #9) > Hey Michel, I am not geographically near the machine for the next 3 weeks. > This was an issue from January 6. I do not know of any more issues since the > updates and all seems fine since 3.0.2+. I will be back to the unit in about > three weeks if you want to pursue it then. > > Cheers! Hi Juergen, I suspect this bug is xulrunner (Gecko)-related, so since 3.0.2 switches to using WebKit, I'm currently setting the 3.0.2 update to close this bug when it reaches the stable repository. Please feel free to reopen it if your problem still persists. Thanks!
Miro-3.0.2-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
Miro-3.0.2-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.