Bug 62907

Created attachment 77212 [details]
Ubuntu 12.04.3 - 7.5 - with 1920.

Created attachment 77213 [details]
Ubuntu 12.10 - 7.7 - without 1920.

Created attachment 77214 [details]
openSUSE 12.3 - 7.7 - without 1920.

We're trying to provide some default resolutions out of the box but tou can get any resolution you want by simply setting autosize->autofit guest (or by forcing it in the xorg.conf file but obviously just selecting that option is easier).

(In reply to comment #4)
> We're trying to provide some default resolutions out of the box but tou can
> get any resolution you want by simply setting autosize->autofit guest (or by
> forcing it in the xorg.conf file but obviously just selecting that option is
> easier).

Xorg.conf does not work, it gets ignored. Only works in Ubuntu. Doesn't work with XFCE or LXDE or KDE.

Autosize causes the panel/DE to misbehave, certainly not suitable for mainstream desktop use. (Like every day work on the guest.)

(In reply to comment #4)
> We're trying to provide some default resolutions out of the box but tou can
> get any resolution you want by simply setting autosize->autofit guest (or by
> forcing it in the xorg.conf file but obviously just selecting that option is
> easier).

Please see the attached xorg.conf at the Launchpad report by "dts-dreamer".
(That one works for Ubuntu/Unity but doesn't work with anything else.)

(In reply to comment #5)
> (In reply to comment #4)
> > We're trying to provide some default resolutions out of the box but tou can
> > get any resolution you want by simply setting autosize->autofit guest (or by
> > forcing it in the xorg.conf file but obviously just selecting that option is
> > easier).
> 
> Xorg.conf does not work, it gets ignored. Only works in Ubuntu. Doesn't work
> with XFCE or LXDE or KDE.

You'll have to go through normal vmware support channels if you need support with setting up your Xserver, here we just deal with bugs.

> Autosize causes the panel/DE to misbehave, certainly not suitable for
> mainstream desktop use. (Like every day work on the guest.)

Well, there's nothing we can do about that. We just set the resolution. If your software/distro has problems with the given resolution you should report it to them. So if the requested resolution is set then we can close the bug.
For whatever it's worth, I'm guessing that whatever desktop environment you're using doesn't deal very well with resolution changes while it's running. Set fit-to-guest and go fullscreen before logging into your desktop environment, that will make sure that it doesn't deal with resolution changes and just uses whatever resolution you wanted from the start.

> You'll have to go through normal vmware support channels if you need support
> with setting up your Xserver, here we just deal with bugs.

Every, I mean EVERY distribution with EVERY xorg repack works below and with 7.5. Perfectly. VMWare loads the guest, and you have one of the most popular resolutions right in the list. You can select it, the DE , WM or whatever you use will also load it perfectly. The thing you use also remember it, and there are no problems with it.

Bit of a rant: 
Here comes 7.6. It's not in the list. Well, too bad you bought a display with the most popular resolution in the world, you won't be able to use the native resolution in full-screen.

So now you are on Google now, after paying for a full license for VMWare Workstation, because the guest is unusable for real work. You try xorg.conf files, different methods, barely any of them work.

Then you come across the cvs method. It kinda works. Kinda does not. But it sometimes works, you may have a cursor (not all the time). It's alright, it's just a paid software after all.

But you get free updates with leenugz, right? Hell yeah. Try updating that Xorg to 7.7, it won't get any better.


Real answer:
Seriously?
How could I report this bug anywhere else, if THIS is the source of the problem, if THIS driver is in charge of detecting resolutions (badly)? I don't try to mock anyone's work. But VMWare Workstation is a full product with a nice price tag. You expect it to work at least this much. I just want VMWare to acknowledge the problem, and MAYBE fix it sometime later.

Telling me to report it to _every single distribution_ that ever packaged Xorg 7.6+ won't help. They are not VMware employees, they just deploy the code. (Compile, package, distribute.) I tried contacting Canonical, but they have no resource to fix this bug. The person in charge even asked around, but they are too busy with Raring and the Mir server. And well, they are not the one to blame here.

Ps.: Submitting reports to the wrong place would just waste time of the triagers and basically they would send me back here to report it upstream because it's an upstream bug. If it would work in Gentoo, Arch, SUSE or something like this, then there would be a patch that gets applied and messes up the display. But that's not the case here. Here the upstream is bugged, and the downstream gets the bug. If upstream could provide a fix, we could patch the packages.
(Even a quick n' dirty "include 1920" fix would be awesome. Just force xorg to put it in the default displays. Hell, even 1920x1200 is there, which is deprecated, so to say. Not to talk about the other even more alien resolutions.)

Alright, I got mad. Twice. Sorry.
I still believe this is a bug (regression) and it belongs to the VMWare Xorg driver. Please fix it. Thank you.

Changing to the default assignee.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org'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.freedesktop.org/xorg/driver/xf86-video-vmware/issues/6.