Bug 1222216 - VMware Player fixed resolution with wayland
Summary: VMware Player fixed resolution with wayland
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wayland
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-16 13:17 UTC by Jimmy Jones
Modified: 2016-07-19 14:07 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 14:07:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jimmy Jones 2015-05-16 13:17:05 UTC
With F22 beta on VMware player 6, gdm uses a fixed resolution (possibly 640x480, very small) and if choose the wayland session you are stuck in this resolution even if you maximise or fullscreen the VMware window. In contrast, going into an X11 session the desktop will fill the window.

Comment 1 Thomas Hellström 2015-06-01 08:26:39 UTC
I'm not sure why GDM and Wayland choose 640x480 as the default resolution, as the vmwgfx KMS systems typically sets 800x600 a the preferred mode.

However, open-vm-tools that is responsible for display resolution change under X
does currently not work with gnome/Wayland. You'd have to manually install the gnome display tool and use that to change resolution within gnome/Wayland.

/Thomas

Comment 2 Fedora End Of Life 2016-07-19 14:07:14 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.


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