On 01/07/2017 10:06 AM, Yves-Alexis Perez wrote:
> On Fri, 2017-01-06 at 22:09 -0500, Gedalya wrote:
>> I've confirmed the problem appeared with systemd 232-1.
>> Downgrading to systemd 231-10 fixes everything.
>>
>> This no doubt has to do with me refusing to use systemd as my init, using
>>
On Fri, 2017-01-06 at 22:09 -0500, Gedalya wrote:
> I've confirmed the problem appeared with systemd 232-1.
> Downgrading to systemd 231-10 fixes everything.
>
> This no doubt has to do with me refusing to use systemd as my init, using
> sysvinit instead.
Can you try with systemd as init system
On 12/07/2016 03:22 AM, Yves-Alexis Perez wrote:
> It's unlikely to be in light-locker/lightDM, try to check what's upgraded in
> the Xorg stack (xserver, driver etc.).
>
>
I've confirmed the problem appeared with systemd 232-1.
Downgrading to systemd 231-10 fixes everything.
This no doubt has
On Sat, 2016-12-03 at 00:46 -0500, Gedalya wrote:
> Reverting lightdm back to 1.18.2-2 didn't help.
> Also I wasn't able to unlock per #846278 using 'loginctl unlock-session
> {X}', however my init is sysvinit, so maybe that's an issue.
It's unlikely to be in light-locker/lightDM, try to check
4 matches
Mail list logo
