Ubuntu 16.04 is supported, but we have a rather confusing policy of
marking all bugs as fixed as soon as any release exists with the fix.
To get a fix into 16.04 we would still use this bug, but would need to
find out *what* fixed it in 18.10 etc first.
--
You received this bug notification
Do you mean that Gnome environment in Ubuntu 16.04 LTS is not (longer)
supported?
On Mon, 3 Sep 2018 at 04:30, Daniel van Vugt
wrote:
>
> Using GNOME 3.29 on Ubuntu 18.10 it appears this bug is fixed.
>
> I'm not sure about Ubuntu 18.04 but do recommend you upgrade to 18.04
> ASAP anyway since it
Using GNOME 3.29 on Ubuntu 18.10 it appears this bug is fixed.
I'm not sure about Ubuntu 18.04 but do recommend you upgrade to 18.04
ASAP anyway since it is our latest long term release that will be
getting the most GNOME fixes.
** Changed in: colord (Ubuntu)
Status: Incomplete => New
**
The problem is specific to Gnome 3 environment and not present on
Unity Desktop. I think, this excludes Unity and Nvidia driver from
suspicion.
On Thu, 30 Aug 2018 at 08:56, Daniel van Vugt
wrote:
>
> Please try logging into Unity and see if the problem persists there.
>
> If the problem remains
I've just tested this on 16.04 with Intel graphics on Unity, and the
colour profile is maintained correctly after the screensaver and unlock.
So that makes me think the problem is specific to GNOME or Nvidia.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Please try logging into Unity and see if the problem persists there.
If the problem remains then maybe also consider uninstalling the Nvidia
driver (which appears to be an unofficial unsupported version) and see
if it continues using the default nouveau driver.
** Changed in: colord (Ubuntu)
** Package changed: xorg (Ubuntu) => colord (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
