There are two workarounds mentioned: swap to lightdm and manipulate gdm3
start. I think you refer to the gdm3 startup changes when you say it causes
problems with suspend/resume (which I didn't try).
The other workaround is changing display manager to lightdm (or sddm, the
KDE display manager).
swapping to lightdm has not caused any suspend/resume problems for me on
the two Optimus laptops I used, so I think the lightdm workaround is ok.
It was the default display manager of ubuntu for a long time and is still
the default for xubuntu.
On Thu, 21 Feb 2019 at 08:45, Stefano <email address hidden> wrote:
There are two workarounds mentioned: swap to lightdm and manipulate gdm3
start. I think you refer to the gdm3 startup changes when you say it causes
problems with suspend/resume (which I didn't try).
The other workaround is changing display manager to lightdm (or sddm, the
KDE display manager).
swapping to lightdm has not caused any suspend/resume problems for me on
the two Optimus laptops I used, so I think the lightdm workaround is ok.
It was the default display manager of ubuntu for a long time and is still
the default for xubuntu.
On Thu, 21 Feb 2019 at 08:45, Stefano <email address hidden> wrote:
> Yes but this workaround is going to create others issue for suspend and /bugs.launchpad .net/bugs/ 1716857 /bugs.launchpad .net/ubuntu/ +source/ gdm3/+bug/ 1716857/ +subscriptions
> resume.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> gdm3, hybrid nvidia with modeset=1, no external monitors detected
>
> To manage notifications about this bug go to:
> https:/
>
--
Tim Richardson