On Wed, Jul 04, 2018 at 07:47:15AM -0000, Sebastien Bacher wrote:
> > Ok, but we still need to know how to inhibit the screen locking in compiz,
> > since the previous standard method is ineffective.
>
> The command that Julian pointed out as the one used by u-r-u is correct
> and works from our testing
>
>
> > unless you are running a GNOME session.
>
> > https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-release-
> upgrader/trunk/view/head:/DistUpgrade/DistUpgradeQuirks.py#L444
>
> It looks like Unity sessions are in a similar situation so maybe the
> code should be change to keep the inhibitor for those as well (maybe
> poping up a dialog explaining that screen lock is not going to work
> until reboot if that's less confusing to users?). That's a different
> case than the one reported here though
Right, I'll open a new bug (or look for an existing one) regarding the
Unity session locking after upgrade issue on Thursday.
On Wed, Jul 04, 2018 at 07:47:15AM -0000, Sebastien Bacher wrote: /bazaar. launchpad. net/~ubuntu- core-dev/ ubuntu- release- trunk/view/ head:/DistUpgra de/DistUpgradeQ uirks.py# L444
> > Ok, but we still need to know how to inhibit the screen locking in compiz,
> > since the previous standard method is ineffective.
>
> The command that Julian pointed out as the one used by u-r-u is correct
> and works from our testing
>
>
> > unless you are running a GNOME session.
>
> > https:/
> upgrader/
>
> It looks like Unity sessions are in a similar situation so maybe the
> code should be change to keep the inhibitor for those as well (maybe
> poping up a dialog explaining that screen lock is not going to work
> until reboot if that's less confusing to users?). That's a different
> case than the one reported here though
Right, I'll open a new bug (or look for an existing one) regarding the
Unity session locking after upgrade issue on Thursday.
--
Brian Murray