Processed: [bts-link] source package systemd
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #791897 (http://bugs.debian.org/791897) # Bug title: systemd: incorrect x bit for group on .journal log files after setting Storage=persistent # * https://github.com/systemd/systemd/issues/534 # * remote status changed: open - closed # * closed upstream tags 791897 + fixed-upstream Bug #791897 [systemd] systemd: incorrect x bit for group on .journal log files after setting Storage=persistent Added tag(s) fixed-upstream. usertags 791897 - status-open Usertags were: status-open. Usertags are now: . usertags 791897 + status-closed There were no usertags set. Usertags are now: status-closed. # remote status report for #792090 (http://bugs.debian.org/792090) # Bug title: journalctl: Error was encountered while opening journal files: Invalid argument # * https://github.com/systemd/systemd/issues/487 # * remote status changed: open - closed # * closed upstream tags 792090 + fixed-upstream Bug #792090 [systemd] journalctl: Error was encountered while opening journal files: Invalid argument Added tag(s) fixed-upstream. usertags 792090 - status-open Usertags were: status-open. Usertags are now: . usertags 792090 + status-closed There were no usertags set. Usertags are now: status-closed. # remote status report for #792761 (http://bugs.debian.org/792761) # Bug title: UX issue, handling of endless shutdown loops # * https://github.com/systemd/systemd/issues/633 # * remote status changed: (?) - open usertags 792761 + status-open There were no usertags set. Usertags are now: status-open. thanks Stopping processing here. Please contact me if you need assistance. -- 791897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791897 792090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792090 792761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#792761: UX issue, handling of endless shutdown loops
On Mon, 20 Jul 2015 10:13:25 -0300 Felipe Sateler fsate...@debian.org wrote: I'm afraid 2 is really an upstream issue and not an integration issue. Could you please file that bug upstream? Maybe... I will give it a try tonight. However I am sceptical regarding productive communication with upstream. Great, let us know when you have filed a bug upstream. https://github.com/systemd/systemd/issues/633^ Says that it cannot find an id. Checked: $ sudo journalctl --list-boots -1 39f59f8ebdd644f39aeb46b67eef9bff Sa 2015-07-18 09:12:05 CESTâMo 2015-07-20 08 0 39f59f8ebdd644f39aeb46b67eef9bff Mo 2015-07-20 08:39:43 CESTâMo 2015-07-20 08 No idea what happened to the logs. Do you have persistent logging enabled? I think you do not. Please follow the instructions of the README.Debian if you want to enable it. Done, waiting for repro situation... Regards, Eduard. -- xTs rpm? Waren das nicht verwunschene debs? ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
[bts-link] source package systemd
# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #791897 (http://bugs.debian.org/791897) # Bug title: systemd: incorrect x bit for group on .journal log files after setting Storage=persistent # * https://github.com/systemd/systemd/issues/534 # * remote status changed: open - closed # * closed upstream tags 791897 + fixed-upstream usertags 791897 - status-open usertags 791897 + status-closed # remote status report for #792090 (http://bugs.debian.org/792090) # Bug title: journalctl: Error was encountered while opening journal files: Invalid argument # * https://github.com/systemd/systemd/issues/487 # * remote status changed: open - closed # * closed upstream tags 792090 + fixed-upstream usertags 792090 - status-open usertags 792090 + status-closed # remote status report for #792761 (http://bugs.debian.org/792761) # Bug title: UX issue, handling of endless shutdown loops # * https://github.com/systemd/systemd/issues/633 # * remote status changed: (?) - open usertags 792761 + status-open thanks ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#793814: systemd-logind: Logins via ssh and su are delayed by 25 seconds
Processing control commands: forcemerge 770135 793814 Bug #770135 [systemd] systemd: ssh logins considerably delayed (until PAM timeout) when systemd is upgraded but the system not rebooted Bug #793814 [systemd] systemd-logind: Logins via ssh and su are delayed by 25 seconds Severity set to 'normal' from 'important' Marked as found in versions systemd/215-6. Bug #770135 [systemd] systemd: ssh logins considerably delayed (until PAM timeout) when systemd is upgraded but the system not rebooted Marked as found in versions systemd/215-17+deb8u1. Merged 770135 793814 found 770135 222-2 Bug #770135 [systemd] systemd: ssh logins considerably delayed (until PAM timeout) when systemd is upgraded but the system not rebooted Bug #793814 [systemd] systemd-logind: Logins via ssh and su are delayed by 25 seconds Marked as found in versions systemd/222-2. Marked as found in versions systemd/222-2. -- 770135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770135 793814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793814 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#770135: Bug#793814: systemd-logind: Logins via ssh and su are delayed by 25 seconds
Control: forcemerge 770135 793814 Control: found 770135 222-2 Hi Steven, On 27 July 2015 at 15:05, Steven Monai smo...@sd57.bc.ca wrote: Dear Maintainer, There is an issue with the systemd-logind daemon that appears to be triggered whenever the dbus daemon is restarted. Specifically, after a recent 'apt-get upgrade' to install a security update (of libexpat1, if that matters), I restarted the 'dbus' daemon, since 'needrestart' had flagged it as one of the daemons requiring a restart. After that, I noticed that logins via ssh and 'su -' were being delayed by about 25 seconds. Here is what I see in /var/log/syslog after every login attempt: Jul 27 09:27:59 ldb dbus[27174]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' Jul 27 09:28:24 ldb dbus[27174]: [system] Failed to activate service 'org.freedesktop.login1': timed out Notice the 25-second timespan between log entries. The problem goes away after I restart the systemd-logind daemon. To reliably trigger the problem on my system (it is a headless server, no Xorg installed), I merely need to do this: systemctl restart dbus All subsequent logins or su's then experience a 25 second delay before proceeding successfully. The following command then returns login processing to normal, without the delay: systemctl restart systemd-logind This was already reported as #770135 , but the dbus connection was not mentioned before. I can confirm the same behavior on systemd 222-2 (inside an nspawn container). -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: timedatectl Should Not be Enabled by Default: Privacy/Anonymity risks
Hi, bancfc wrote (26 Jul 2015 18:19:59 GMT) : The research comes from WhonixOS a privacy centric distro like TAILS. For the record, this does not imply any position from Tails regarding this topic: the Tails threat model generally does not apply as-is to Debian. Also, it would be good to describe what exact threat model you see timedatectl as a security/privacy problem, so Debian has the data to evaluate if/how its default installation settings behave in that context: looking at one single potential issue in isolation does not make much sense to me, if there are potentially dozens of other ways for an attacker to do what they want. Thanks in advance! To end with, I'm wondering whether this email is really about timesyncd. Cheers, -- intrigeri ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#792418: Wrong illegal-runtime-test-name for comma separated Tests: in debian/tests/control
Hey Niels, sorry for the delay, I was on holiday. Niels Thykier [2015-07-15 7:20 +0200]: If you are planning on using comma as the canonical separator, please consider also updating the examples in your documentation. E.g. your [1] still says: The source package provides a test metadata file debian/tests/control. This is a file containing zero or more RFC822-style stanzas, along these lines: Tests: fred bill bongo Restrictions: needs-root breaks-testbed Thanks for pointing out! Fixed in git now: http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=5521c On a related note, do you want us to recommend users to use comma instead of whitespace (by warning about a pure whitespace separator)? Using whitespace only is still legitimate syntax and I don't want to break that for the time being due to backwards compat. Likewise I wouldn't want to introduce potentially hundreds of lintian warnings just for that yet. So a lintian warning seems to be too strong to me, at least for the time being. Thanks! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
