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 631130 - Regression: Cannot skip forward or backward while watching video full screen
Regression: Cannot skip forward or backward while watching video full screen
Status: RESOLVED DUPLICATE of bug 556984
Product: banshee
Classification: Other
Component: User Interface
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-10-01 18:44 UTC by lnxme1
Modified: 2011-06-10 19:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description lnxme1 2010-10-01 18:44:33 UTC
Hello,

While watching a video full screen, keyboard shortcut to skip forward (right direction key) and skip backward (left direction key) doesn't work anymore.

Was working fine in 1.7.6.

To reproduce.

- In Banshee, select video in the left pane. 
- Choose a video in the video list -> a list of video appear on the right pane.
- Double clik on a video to start playing it -> the video starts playing in the right pane
- Go full screen by pressing the "f" key -> the video goes full screen
- press right direction key; the video should skip forward a few min -> nothing happens
- press left direction key the video should skip backward a few min -> nothing happens

The only to navigate inside the video is now to exit full screen, using time slider with mouse, then going back full screen.
Comment 1 lnxme1 2010-11-21 14:36:32 UTC
Same issue in banshee 1.9.0

How to make this bug status "CONFIRMED" ?
Comment 2 Michael Martin-Smucker 2010-11-22 23:26:53 UTC
I can confirm this with Banshee from git -- I don't know whether it's a regression or not because i haven't used Banshee much for video, but I'll take your word for it.  :)
Comment 3 lnxme1 2011-06-10 19:45:50 UTC

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