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 464491 - Switching visualisation screen in fullscreen mode doesnt work correctly
Switching visualisation screen in fullscreen mode doesnt work correctly
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: Plugins (other)
0.11.x
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-07 21:15 UTC by Sebastien Bacher
Modified: 2018-05-24 12:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2007-08-07 21:15:30 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/126057

"Binary package hint: rhythmbox

I have a two screen setup. When using the visualtion plugin, there is a little combo box for picking which screen to appear on (i dont know whether this exists or not on a single screen setup). Having the visualisation running in fullscreen, and then switching the option to change screens doesnt work correctly. There are at least 2 ways it fails, on switch on my setup will cause the window to move to the correct screen, but it wont be fullscreen, and the visualistaion becomes invisible. Switching the other way just causes nothing to happen.

However it is possible to workaround by switching to embedded mode and back to fullscreen.

ProblemType: Bug
Architecture: i386
Date: Sat Jul 14 23:10:30 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.1-0ubuntu2
..."
Comment 1 GNOME Infrastructure Team 2018-05-24 12:45:44 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/417.