Running Firefox (Version 50.0+build2-0ubuntu0.16.04.2) with xrdp -> result: wrong colors, also for the interface

[Gabi Slonto]

Setup:

Ubuntu 16.04 LTS with all patches installed +
xrdp 0.6.1-2
vnc4server 4.1.1+xorg4.3.0-37.3ubuntu2

Firefox Version (49.0.2+build2-0ubuntu0.16.04.2) with xrdp -> all colours ok also in the normal login-console

Error:

Ubuntu 16.04 LTS with all patches installed +
Firefox Version (Version 50.0+build2-0ubuntu0.16.04.2)

with xrdp -> all colours are wrong !!!! (colours are blue, where colours have to be red!!)

with normal login-console -> all colours are ok

I am able to reproduce this error if i install the previous version of Firefox.

Thanks a lot.

Gabi

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Anders Eriksson (aen-launchpad)]

The same thing happens for me when I run firefox on a vnc-server and display it in a vnc client. Worked fine in previous package version. Running Ubuntu 16.10 and this started after restarting firefox after apt-get update; apt-get upgrade.

firefox package version 50.0+build2-0ubuntu0.16.10.2

[Anders Eriksson (aen-launchpad)]

Just updated to firefox 50.0.2+build1-0ubuntu0.16.10.1, but it is still showing the wrong colors when run in vnc server

[Anders Eriksson (aen-launchpad)]

Updated to firefox 50.1.0+build2-0ubuntu0.16.10.1 on ubuntu 16.10. Restarted firefox in vnc-server, but the colors are still not right.

[Alexander Zeitler (alexander-zeitler)]

Happens on 14.04 as well.

[Jonathan Thomas (magothy)]

I was having this issue as well against 16.04.

But changing the colors down to 16-bit instead of the 32-bit full color in the rdp client 'fixed' it.

[Anders Eriksson (aen-launchpad)]

Upgraded my ubuntu 16.10 to firefox 51.0.1+build2-0ubuntu0.16.10.1 (with vncs4erver 4.1.1+xorg4.3.0-3) and now it works again for me.

Thank you!

[Alexander Zeitler (alexander-zeitler)]

Updated to Firefox 54 on Ubuntu 14.04 LTS and everything now is fine again.
Thanks for fixing.

[Paul White (paulw2u)]

Comments #6,7 and 8 confirm issue was fixed by changing a setting in 3rd party software or by updating Firefox to a later release. No further comments for over two years so closing as fixed.