Bug 551868

Summary: SIGSEGV in "gtk_range_set_value" in /usr/bin/miro.real
Product: [Fedora] Fedora Reporter: Juergen Kaiserling <jkaiserling>
Component: MiroAssignee: Alex Lancaster <alex>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: alex, dmalcolm, ivazqueznet, james.antill, jonathansteffan, michel, will.guaraldi
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:bbc8979ecbb5f5c87d8eaee7a8f25d73b62caca5
Fixed In Version: Miro-3.0.2-1.fc12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-10 19:11:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Juergen Kaiserling 2010-01-02 18:09:16 UTC
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

Comment 1 Juergen Kaiserling 2010-01-02 18:09:22 UTC
Created attachment 381305 [details]
File: backtrace

Comment 2 Dave Malcolm 2010-01-04 20:28:40 UTC
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"

Comment 3 Alex Lancaster 2010-01-05 22:30:22 UTC
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).

Comment 4 Juergen Kaiserling 2010-01-06 17:27:43 UTC
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.

Comment 5 Michel Lind 2010-06-03 19:03:14 UTC
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!

Comment 6 Michel Lind 2010-06-03 19:05:55 UTC
Actually, since this is likely to be xulrunner-related, 3.0.2 should fix it

Comment 7 Fedora Update System 2010-06-03 19:32:08 UTC
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

Comment 8 Fedora Update System 2010-06-03 19:32:28 UTC
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

Comment 9 Juergen Kaiserling 2010-06-04 12:00:16 UTC
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!

Comment 10 Fedora Update System 2010-06-04 18:55:47 UTC
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

Comment 11 Fedora Update System 2010-06-04 18:56:43 UTC
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

Comment 12 Michel Lind 2010-06-05 15:32:43 UTC
(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!

Comment 13 Fedora Update System 2010-06-10 19:10:44 UTC
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.

Comment 14 Fedora Update System 2010-06-10 19:23:19 UTC
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.