[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
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 server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 823718] Re: Replace ~/.dmrc with AccountsService
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. I have filed another bug report (#1069494) on this and I don't understand why you ask me to discuss this on an ubuntu mailing list. This is an upstream *bug* and therefore this belongs to the upstream bug tracker. We have the same problem in Debian as well, so it's not an issue of what distribution is used. Adrian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/823718 Title: Replace ~/.dmrc with AccountsService Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Oneiric: Fix Released Bug description: While gdm has switched to AccountsService for storing the session type, lightdm stores that piece of info in ~/.dmrc. I suppose it would be a good idea that also lightdm makes use of AccountsService for the purpose, and drops ~/.dmrc entirely. That way would always the same option appear on the greeter if a user moves from gdm to lightdm or vice versa. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/823718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 823718] Re: Replace ~/.dmrc with AccountsService
> 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 for many corporate users. It's super easy to reproduce if you have two computers on a network with a shared home directory: - user A logs in to machine "host001", chooses MATE and en_US.UTF-8 as their defaults - user A logs out - user A logs into machine "host002" and neither MATE or en_US.UTF-8 are restored as settings but some random settings which depend on who previously logged into the machine and what user A's settings were last time logging in to "host002" All of this worked fine previously when using ~/.dmrc and is still broken after switching to a-s-d. This really needs to be fixed and if the concept of a-s-d is supposed to be kept, then a-s-d should be able to store it's database settings across different host with the same shared home directory. Adrian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/823718 Title: Replace ~/.dmrc with AccountsService Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Oneiric: Fix Released Bug description: While gdm has switched to AccountsService for storing the session type, lightdm stores that piece of info in ~/.dmrc. I suppose it would be a good idea that also lightdm makes use of AccountsService for the purpose, and drops ~/.dmrc entirely. That way would always the same option appear on the greeter if a user moves from gdm to lightdm or vice versa. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/823718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 90085] Re: When /tmp is mounted noexec, preconfigure fails
> 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 Linux loader. Anyone who wants to run an exploit can just run "lib64/ld- linux-x86-64.so.2 /tmp/bla" instead of just "/tmp/bla" and it will just work. For scripts, you just invoke them through their interpreter. Adrian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/90085 Title: When /tmp is mounted noexec, preconfigure fails Status in debconf package in Ubuntu: Triaged Status in debconf package in Debian: Confirmed Bug description: Binary package hint: mysql-server /tmp mounted noexec, this ensues: Preconfiguring packages ... Can't exec "/tmp/mysql-server-5.0.config.89611": Permission denied at /usr/share/perl/5.8/IPC/Open3.pm line 168. open2: exec of /tmp/mysql-server-5.0.config.89611 configure failed at /usr/share/perl5/Debconf/ConfModule.pm line 57 mysql-server-5.0 failed to preconfigure, with exit status 2 ace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/90085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377373] Re: Variables defined twice in config files lead to crash
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 return value 6 [+0.53s] DEBUG: Seat: Session stopped [+0.53s] DEBUG: Seat: Stopping; failed to start a greeter [+0.53s] DEBUG: Seat: Stopping [+0.53s] DEBUG: Seat: Stopping display server Seems like lightdm-gtk-greeter needs to be updated as well. Adrian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1377373 Title: Variables defined twice in config files lead to crash Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in “lightdm” package in Ubuntu: In Progress Status in “lightdm” source package in Trusty: In Progress Status in “lightdm” source package in Utopic: In Progress Status in “lightdm” package in Debian: Fix Released Bug description: Lightdm crashes on startup for me, on Ubuntu 14.10. This is the offending error: *** Error in `lightdm': double free or corruption (fasttop): 0x02535ca0 *** Aborted To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1377373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377373] Re: Variables defined twice in config files lead to crash
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. https://bugs.launchpad.net/bugs/1377373 Title: Variables defined twice in config files lead to crash Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in “lightdm” package in Ubuntu: In Progress Status in “lightdm” source package in Trusty: In Progress Status in “lightdm” source package in Utopic: In Progress Status in “lightdm” package in Debian: Fix Released Bug description: Lightdm crashes on startup for me, on Ubuntu 14.10. This is the offending error: *** Error in `lightdm': double free or corruption (fasttop): 0x02535ca0 *** Aborted To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1377373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
