Bug 757832

Summary:	[abrt] pitivi-0.15.0-1.fc16: track.py:467:setObjectStart:TypeError: could not convert argument to correct param type
Product:	[Fedora] Fedora	Reporter:	Richard W.M. Jones <rjones>
Component:	pitivi	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gwync, hicham.haouari, otte
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:	abrt_hash:687f1385d6b1d6a462a9a371f3794671b375f9ad
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 15:59:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	747988
Bug Blocks:

Description Richard W.M. Jones 2011-11-28 19:45:16 UTC

libreport version: 2.0.7
abrt_version:   2.0.6
cmdline:        python /usr/bin/pitivi
executable:     /usr/bin/pitivi
kernel:         3.1.0-0.rc6.git0.0.fc16.x86_64
reason:         track.py:467:setObjectStart:TypeError: could not convert argument to correct param type
time:           Mon 28 Nov 2011 19:40:46 GMT
uid:            500
username:       rjones

backtrace:
:track.py:467:setObjectStart:TypeError: could not convert argument to correct param type
:
:Traceback (most recent call last):
:  File "/usr/share/pitivi/python/pitivi/ui/timeline.py", line 792, in split
:    self.timeline.split(self._position)
:  File "/usr/share/pitivi/python/pitivi/timeline/timeline.py", line 2010, in split
:    obj.split(time)
:  File "/usr/share/pitivi/python/pitivi/timeline/timeline.py", line 366, in split
:    other_track_object = track_object.splitObject(position)
:  File "/usr/share/pitivi/python/pitivi/timeline/track.py", line 637, in splitObject
:    other.trimObjectStart(position)
:  File "/usr/share/pitivi/python/pitivi/timeline/track.py", line 594, in trimObjectStart
:    self.setObjectStart(position)
:  File "/usr/share/pitivi/python/pitivi/timeline/track.py", line 467, in setObjectStart
:    self.gnl_object.props.start = position
:TypeError: could not convert argument to correct param type
:
:Local variables in innermost frame:
:position: 690000000000.0
:self: <pitivi.timeline.track.SourceTrackObject object at 0x3b88f50>

comment:
:Just using Pitivi.
:
:Static typing FTW ...

Comment 1 Gwyn Ciesla 2012-03-27 18:04:48 UTC

Does this crash with the 0.15.0-3 in updates-testing?

Comment 2 Fedora End Of Life 2013-01-16 14:44:21 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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

Comment 3 Fedora End Of Life 2013-02-13 15:59:51 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.