Bug 1405167 - vinagre: No apparent way to exit full screen mode
Summary: vinagre: No apparent way to exit full screen mode
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: vinagre
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David King
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-15 18:33 UTC by Florian Weimer
Modified: 2022-12-13 15:11 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:11:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Restore fullscreen drawer functionality. (1.32 KB, patch)
2018-02-09 19:06 UTC, Philippe Troin
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 770484 0 Normal RESOLVED popup menu in full screen mode not visible 2020-11-30 08:02:48 UTC
GNOME Gitlab GNOME vinagre issues 9 0 None None None 2020-11-30 08:02:58 UTC

Description Florian Weimer 2016-12-15 18:33:18 UTC
Description of problem:

The manual says “While in fullscreen mode, move the mouse to the top-center of the screen to display a hidden toolbar, which has Leave Fullscreen, Disconnect and other buttons.”, but this does not happen, neither for the top of the remote screen, nor the top of the display.

Version-Release number of selected component (if applicable):

vinagre-3.22.0-1.fc25.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. Start vinagre with a host on the command line.
2. Activate full screen mode.
3. Move the pointer around.

Actual results:

No toolbar displayed.

Expected results:

Toolbar displayed.

Additional info:

I'm using a GNOME desktop with Wayland.

Comment 1 Fedora End Of Life 2017-02-28 10:47:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 2 redhat 2017-11-03 15:55:03 UTC
Still present in FC26.

Comment 3 Chris Schanzle 2018-02-03 23:31:48 UTC
Still a problem in Fedora 27 under Xorg and Wayland with up-to-date system as of this writing:
vinagre-3.22.0-6.fc27.x86_64

The icons seem to be just invisible...you can escape with some care.

If you move the cursor to top-center where the pull-down should appear, then move down about 10-15 pixels and "hover" (do not move for a few seconds) the cursor, you should see tooltips.  Carefully move horizontally left until you see "Leave fullscreen".  Then left-click.

Hope that helps someone and maybe even give clues to debug the issue.

Comment 4 Philippe Troin 2018-02-09 19:06:22 UTC
Created attachment 1393953 [details]
Restore fullscreen drawer functionality.

This bug is only two years old! Time to fix it.
The vinagre maintainers seem to be MIA, this patch has been sitting https://bugzilla.gnome.org/show_bug.cgi?id=770484 for several months.

I am not the author of the patch, see the Gnome Bug #770484 for attribution.

Adding this patch makes vinagre works for me.

Comment 5 Fedora End Of Life 2018-05-03 08:14:28 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora  'version'
of '26'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 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  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

Comment 6 Philippe Troin 2018-05-07 20:28:40 UTC
Still present in F27 and F28.

Comment 7 Ben Cotton 2019-05-02 21:45:40 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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
EOL if it remains open with a Fedora 'version' of '28'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 8 Chris Schanzle 2019-05-06 04:30:00 UTC
Present in F29.  [haven't tried F30 yet.]

Comment 9 Ben Cotton 2019-05-28 19:22:39 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 10 Alexander Korsunsky 2020-03-23 12:32:46 UTC
Still present in Fedora 31 and Fedora 32. Please reopen this bug.

Comment 11 Jaroslav Škarvada 2020-07-03 19:26:32 UTC
The bug is still present, it's very annoying. Even killing the vinagre doesn't help, I need to wipe it's configuration in order to start in normal mode.

Comment 12 Stan King 2020-09-03 15:53:12 UTC
Just a "by the way": vinagre is the only Fedora VNC viewer that can successfully connect to Intel AMT VNC with a color mode of more than 8 bits per pixel, so it's likely that any Intel AMT users out there would appreciate a more graceful way to exit from vinagre full-screen.

Comment 13 Ben Cotton 2020-11-03 14:58:11 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 EOL if it remains open with a
Fedora 'version' of '31'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 14 Stan King 2020-11-07 20:18:19 UTC
It's still happening with Fedora 32.

Comment 15 Ben Cotton 2020-11-24 15:15:33 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 16 Stan King 2020-11-29 22:16:24 UTC
It's still a problem in Fedora 32.

However, the workaround from comment 3, to attempt to navigate the invisible icon panel, seems to work for me.

Of course, given that the icons are invisible, the chance of clicking on the wrong one is quite high.

What's the right course of action from here?  Re-open this problem report?  Enter a new report?

How does one persuade the upstream maintainers to look at this?  It's issue #9 there, encountered in the Fedora 29 environment, link https://gitlab.gnome.org/GNOME/vinagre/-/issues/9

Comment 17 Fedora Program Management 2021-04-29 15:52:57 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 EOL if it remains open with a
Fedora 'version' of '32'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 18 Jaroslav Škarvada 2021-04-30 15:25:09 UTC
Moving to f33.

Comment 19 Ben Cotton 2021-11-04 14:05:13 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 EOL if it remains open with a
Fedora 'version' of '33'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 20 Ben Cotton 2021-11-04 14:34:14 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 EOL if it remains open with a
Fedora 'version' of '33'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 21 Ben Cotton 2021-11-04 15:32:04 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 EOL if it remains open with a
Fedora 'version' of '33'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 22 Jaroslav Škarvada 2021-11-05 09:42:48 UTC
Moving to f34.

Comment 23 Felipe Borges 2021-11-09 10:19:04 UTC
We recommend that Vinagre users migrate to gnome-connections. Vinagre is getting discontinued.

GNOME Connections uses the same gtk-vnc backend for VNC connections as Vinagre, so you should expect similar behavior.

Comment 24 Ben Cotton 2022-05-12 14:55:12 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
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 EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 25 Stan King 2022-05-16 23:40:45 UTC
Vinagre was the only VNC client on Fedora that worked correctly with Intel AMT's VNC server with regard to supporting a decent color map.  I just verified that gnome-connections does just as well.  Its "fit to window" mode doesn't constratin to the original aspect ratio, which is a little weird, but you can't have everything, I suppose.

Comment 26 Felipe Borges 2022-05-18 12:00:21 UTC
(In reply to Stan King from comment #25)
> Vinagre was the only VNC client on Fedora that worked correctly with Intel
> AMT's VNC server with regard to supporting a decent color map.  I just
> verified that gnome-connections does just as well.  Its "fit to window" mode
> doesn't constratin to the original aspect ratio, which is a little weird,
> but you can't have everything, I suppose.

thanks! I will take a look at fixing this issue with wrong aspect ratio.

Comment 27 Ben Cotton 2022-11-29 16:44:57 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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 EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 28 Ben Cotton 2022-12-13 15:11:58 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.