Bug#803468: systemd: /etc/locale.conf locale variables are not set into the user locale

2015-10-30 Thread nfb
Package: systemd Version: 227-2 Severity: normal Dear Maintainer, after installing locales package, generating my localization, editing /etc/locale.conf and finally rebooting the system, all the locales variable now default to "POSIX", as stated from the output of "locale". "localectl status",

Bug#803468: systemd: /etc/locale.conf locale variables are not set into the user locale

2015-10-30 Thread nfb
> > There is no /etc/locale.conf in Debian, the correct file is > > /etc/default/locale > > Btw, did you manually create /etc/locale.conf? This file is not shipped > by systemd There is no /etc/locale.conf but there is a man page for it. The file itself is not shipped with systemd but its man

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-23 Thread nfb
Hm, if the Chromium kernel/LSM forbids this, I don't see how this can be fixed in systemd? Do you? Obviously the answer is no... i reported here since the commands in the service file were working fine when executed by hand, so i thought it couldn't be a kernel issue, but how systemd handled

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-22 Thread nfb
Are you suspecting the arm architecture or the custom kernel to be the culprit? Can you test the stock Debian kernel on arm? Your custom kernel, does it have every option enabled as specified in /usr/share/doc/systemd/README.gz Yes i suspect about the kernel, also because among the error logs

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread nfb
Including the complete .service file would be helpful. Oh yes i didn't specify i installed the tor package in the debian testing repos, so the unit file is the one included in the package: --- [Unit] Description=Anonymizing overlay network for TCP After=network.target nss-lookup.target

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread nfb
Once you file the bug upstream, reply to *this* bug report with the upstream bug report number. This way I can link the two bug reports and we can track the upstream process automatically. here it is: https://github.com/systemd/systemd/issues/567 @Intrigeri So you cannot confirm... maybe

Bug#792187: systemd: systemctl start not working when ReadWriteDirectories is a symlink

2015-07-12 Thread nfb
Package: systemd Version: 221-1 Severity: normal Dear Maintainer, I installed tor (The onion router) the other day and when i started it (either via /usr/sbin/service or systemctl) i went through this: $ sudo systemctl start tor.service Job for tor.service failed because the control process