And it made multiple buildds hang for days :-(. I just only noticed it
now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1801338
Title:
apt fails to properly handle
So, to conclude, I'm not sure what it is you would write in that bug
report.
Just as a heads up: Restoring session still does not work in lightdm.
And, as for all arguments that speak for accounts-service-daemon, the
fact remains that switching from .dmrc to a-s-d broke session save and
restore
Well, the thing is: This change broke session management and therefore I
think it's fair to comment on this right here.
Serious question: Are you actually using lightdm yourself? I mean, it's
obviously completely broken. It doesn't even restore the settings on the
same machine these days anymore.
Please let the user decide if using a /tmp noexec mount point is more
secure or not.
That doesn't even make sense. It's a fact that mounting /tmp with
noexec doesn't give you any extra security simply because you can
simply circumvent it by invoking the executable with the help of the
dynamic
Addendum:
From /var/log/lightdm/x-0-greeter.log:
*** Error in `/usr/sbin/lightdm-gtk-greeter': double free or corruption
(fasttop): 0x7f22865207c0 ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
Ok, this seem to have fixed the double or free corruption issue,
however, lightdm still doesn't start for me:
[+0.26s] DEBUG: Session pid=1890: Greeter connected version=1.10.2
[+0.53s] DEBUG: Session pid=1890: Greeter closed communication channel
[+0.53s] DEBUG: Session pid=1890: Exited with
6 matches
Mail list logo
