After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 597704 - Traceback when undoing 'split' operation
Traceback when undoing 'split' operation
Status: RESOLVED FIXED
Product: pitivi
Classification: Other
Component: Timeline
Git
Other Linux
: Normal blocker
: 0.13.4
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on: 610444
Blocks:
 
 
Reported: 2009-10-07 16:01 UTC by Tim Waugh
Modified: 2010-02-22 00:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace (1.12 KB, text/plain)
2009-10-07 16:01 UTC, Tim Waugh
Details

Description Tim Waugh 2009-10-07 16:01:09 UTC
Created attachment 144970 [details]
backtrace

See rhbz#527683:
  https://bugzilla.redhat.com/show_bug.cgi?id=527683

This only happened once and I haven't been able to reproduce it since.
Comment 1 Edward Hervey 2009-11-27 07:39:33 UTC
Gah, bug has changed.

Scenario:
* blank timeline

* add file to timeline
  [---------------A----------------]

* seek to middle of file

* cut
  => all good, we have two clips cut at current position
  [----A1-----][--------A2---------]

* undo
  => ERROR : only second clip is kept, first one is removed and stays at the trimmed position
               [--------A2---------]

* redo
  => ok I guess, two clips are back in place
  [----A1-----][--------A2---------]
  => BUT we get the following warning:
pitivi/timeline/track.py:211: Warning: g_sequence_search: assertion `seq != NULL' failed
  self._controller.unset(self._property.name, keyframe.time)

* undo again
  => ERROR : same bug as initial UNDO

* redo again
  => ERROR : same as initial REDO + segfault
Comment 2 Jean-François Fortin Tam 2010-02-10 05:07:33 UTC
Setting the milestone so we don't forget about it... seems like a pretty important regression.
Comment 3 Jean-François Fortin Tam 2010-02-16 23:31:43 UTC
Setting as blocker as suggested by twi.
Comment 4 Sebastian Dröge (slomo) 2010-02-19 12:12:36 UTC
This is a gstreamer core bug, see bug #610444.

Nonetheless something should be done on the pitivi side too.
  self._controller.unset(self._property.name, keyframe.time)

This is deprecated API. Instead of setting/unsetting control points on the controller directly a new abstraction was added in 0.10.14. the control point stuff is inside the GstInterpolationControlSource now. No idea if that API is exposed in python already
Comment 5 Alessandro Decina 2010-02-22 00:18:05 UTC
commit 75e05d2679314ada4551623dd049fbab30efe87c
Author: Alessandro Decina <alessandro.d@gmail.com>
Date:   Mon Feb 22 01:16:55 2010 +0100

    Fix a regression undoing splitting of clips. Fixes #597704.