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 721974 - Undo button is a fake
Undo button is a fake
Status: RESOLVED DUPLICATE of bug 709471
Product: pitivi
Classification: Other
Component: Timeline
0.92
Other Linux
: Normal normal
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2014-01-11 03:03 UTC by antistress
Modified: 2014-01-11 04:42 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Undo button (21.31 KB, image/png)
2014-01-11 03:54 UTC, antistress 		Details

Description antistress 2014-01-11 03:03:54 UTC 
Hi,

I tried two things to test the 'cancel' button :

In the media library : import a clip onto the timeline using the dedicated button. The 'cancel' button is now highlighted. Press the 'cancel button' : no effect.

On the timeline : cut the clip in two parts using the dedicated button. The 'cancel' button is now highlighted. Press the 'cancel button' : no effect.

What's wrong ?

I'm running Debian GNU/Linux :
- Linux debian 3.12-1-amd64 #1 SMP Debian 3.12.6-2 (2013-12-29) x86_64 GNU/Linux
- libc6 2.17-97

Thanks
Comment 1 Jean-François Fortin Tam 2014-01-11 03:47:36 UTC 
What's the "cancel" button? (annotated screenshot might help). Are you talking about the button to remove clips from the timeline?

If it doesn't actually remove a selected clip from the timeline, see if there are errors in the terminal?

See http://wiki.pitivi.org/wiki/Bug_reporting for some tips & tricks to get debug logs to have a better idea of what's going on.
Comment 2 antistress 2014-01-11 03:52:31 UTC 
Sorry, I meant the 'Undo' button
Comment 3 antistress 2014-01-11 03:54:48 UTC 
Created attachment 265986 [details]
Undo button
Comment 4 Jean-François Fortin Tam 2014-01-11 04:42:11 UTC 
Oh, SNAFU

*** This bug has been marked as a duplicate of bug 709471 ***