Bug 904865 - Distorted window size/colours with mutter under xrdp
Summary: Distorted window size/colours with mutter under xrdp
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 19
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-27 23:51 UTC by Bojan Smojver
Modified: 2013-07-29 00:37 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-29 00:37:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screen shot of the remote session (running under xrdp) (39.65 KB, image/png)
2013-01-29 22:30 UTC, Bojan Smojver
no flags Details
New behaviour - tilted windows (43.07 KB, image/png)
2013-06-02 06:12 UTC, Bojan Smojver
no flags Details
Slanted menu (12.01 KB, image/png)
2013-06-14 04:37 UTC, Bojan Smojver
no flags Details

Description Bojan Smojver 2013-01-27 23:51:57 UTC
Description of problem:
Just tried switching from fallback mode into regular Gnome Shell mode on my VM that runs xrdp (16-bit colour depth). When I logged in, all windows were half the width with distorted colours (showing lots of pink and green). Fallback session works fine. The computer I'm coming from uses 24-bit colour (16-bits setup in xrdp, because it is a bit faster that way across continents).

Version-Release number of selected component (if applicable):
gnome-shell-3.6.2-6.fc18.i686

How reproducible:
Always.

Steps to Reproduce:
1. Setup and VMware VM, with xrdp (16-bit colour depth).
2. Connect to it using Windows RDP client from a 24-bit colour machine.
3. See distorted Windows.
  
Actual results:
Distorted window size/colour.

Expected results:
Works in fallback.

Additional info:

Comment 1 Bojan Smojver 2013-01-27 23:57:20 UTC
Also happens in fallback when mutter is WM. Reassigning.

Comment 2 Bojan Smojver 2013-01-28 22:17:32 UTC
BTW, this is mutter-3.6.2-1.fc18.i686.

Comment 3 Peter Robinson 2013-01-28 22:39:40 UTC
It's unlikely to be mutter it's more likely to be the driver which is likely to be the llvm soft driver if it's running on vSphere

Comment 4 Bojan Smojver 2013-01-28 22:44:04 UTC
The VM is VMware, BTW. I do not control the infra, so I have no idea what version.

It is definitely soft driver (it says llvmpipe 0.4). Essentially, Xvnc is driving this, because xrdp runs Xvnc behind the scenes.

Comment 5 Adam Jackson 2013-01-29 19:16:29 UTC
Can I get a screenshot please?  I think I know what this might be but I'd like to see the corruption to get a better idea.

Comment 6 Bojan Smojver 2013-01-29 22:30:25 UTC
Created attachment 690066 [details]
Screen shot of the remote session (running under xrdp)

Note: the background is really set to black - this is not a bug.

The dialog to unlock the keyring appeared distorted as well. Gedit is distorted in the screen shot, gnome-terminal is not. Evolution also appeared distorted, although I purposely did not include it. System setting was distorted too. Overview looked OK (icons were the right size etc.).

It is interesting that in the windows that were distorted, the clicking distances were actually correct. That is to say, when I wanted to go back to fallback in system settings, I had to click the button at twice the distance that it appeared at from the left edge of the window, in order to flick it to on.

So, something is not quite right, although not totally broken.

Comment 7 Bojan Smojver 2013-03-13 03:58:39 UTC
Still the case, BTW.

Comment 8 Bojan Smojver 2013-03-13 23:51:27 UTC
The reason I'm pestering about this is the fact that Gnome fallback is going away with F-19, so this will kinda have to work under xrdp/VNC etc.

Comment 9 Bojan Smojver 2013-03-19 21:50:43 UTC
Still the case with latest mesa (9.1-1).

Comment 10 Bojan Smojver 2013-03-25 23:49:06 UTC
Still the case with mesa 9.1-3. Is there some scratch build or something like that that I can try for this?

Comment 11 Bojan Smojver 2013-03-26 02:06:42 UTC
Same bug?

https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1044436

I run my xrdp session in 16-bit mode to reduce bandwidth requirements.

Comment 12 Bojan Smojver 2013-03-26 02:20:38 UTC
When I switch the RDP client to use 24-bit mode, there is no such problem. So, 16-bits only, just like the Ubuntu bug.

Comment 13 Bojan Smojver 2013-06-02 06:12:34 UTC
Created attachment 755753 [details]
New behaviour - tilted windows

Interesting behaviour with latest mesa and llvmpipe. Some windows are tilted, as in the screenshot. This still applies to 16-bit mode. The window in the screenshot is Pidgin buddy list.

Comment 14 Bojan Smojver 2013-06-03 00:45:34 UTC
BTW, many (if not most) of the previously distorted windows are no longer distorted. Evo and gedit are just some examples. Also, the previous distortion (half width and green/purple windows) is no longer there. Only the new behaviour (i.e. see Pidgin example) now exists.

Comment 15 Bojan Smojver 2013-06-14 04:36:36 UTC
Moving to F-19, as it is still a problem there. It is actually slightly worse than what F-18 was with the latest updates. Pretty much all windows are slanted, including terminal, for instance.

Comment 16 Bojan Smojver 2013-06-14 04:37:06 UTC
Created attachment 761066 [details]
Slanted menu

Comment 17 Bojan Smojver 2013-07-29 00:37:19 UTC
Whether it was today's tigervnc 1.3.0 push or the new mesa snapshot - I don't know - but it seems fixed. So, as of this:
-------------
mesa-dri-drivers-9.2-0.14.20130723.fc19.i686
mesa-filesystem-9.2-0.14.20130723.fc19.i686
mesa-libEGL-9.2-0.14.20130723.fc19.i686
mesa-libgbm-9.2-0.14.20130723.fc19.i686
mesa-libGL-9.2-0.14.20130723.fc19.i686
mesa-libglapi-9.2-0.14.20130723.fc19.i686
mesa-libGLU-9.0.0-2.fc19.i686
mesa-libwayland-egl-9.2-0.14.20130723.fc19.i686
mesa-libxatracker-9.2-0.14.20130723.fc19.i686
tigervnc-1.3.0-3.fc19.i686
tigervnc-icons-1.3.0-3.fc19.noarch
tigervnc-license-1.3.0-3.fc19.noarch
tigervnc-server-1.3.0-3.fc19.i686
tigervnc-server-minimal-1.3.0-3.fc19.i686
-------------

It works!


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