Processed: severity of 783509 is important

2015-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 783509 important Bug #783509 [systemd] tmp.mount activated accidentally via bind mount Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 783509: http://bugs.debian.

Processed: tagging 783509

2015-06-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 783509 + pending Bug #783509 [systemd] tmp.mount activated accidentally via bind mount Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 783509: http://bugs.debian.org/cgi-bin/bugreport.cg

Processing of systemd_220-6_amd64.changes

2015-06-11 Thread Debian FTP Masters
systemd_220-6_amd64.changes uploaded successfully to localhost along with the files: systemd_220-6.dsc systemd_220-6.debian.tar.xz libnss-myhostname_220-6_amd64.deb libnss-mymachines_220-6_amd64.deb libpam-systemd_220-6_amd64.deb libsystemd-daemon-dev_220-6_amd64.deb libsystemd-dev_22

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Michael Biebl
Control: tags -1 moreinfo Am 11.06.2015 um 02:13 schrieb jessie: > And the output of the systemd-logind.service, as you can see it fires > `suspend` on the first lid close but never on any after the very first lid > close, it is very odd, it clearly sees the event: > > ``` > -- Logs begin at W

Processed: Re: Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Debian Bug Tracking System
Processing control commands: > tags -1 moreinfo Bug #788400 [systemd] systemd-logind only fires suspend on lid close once even though it sees the event Added tag(s) moreinfo. -- 788400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788400 Debian Bug Tracking System Contact ow...@bugs.debian.

systemd_220-6_amd64.changes ACCEPTED into unstable

2015-06-11 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jun 2015 09:25:49 +0200 Source: systemd Binary: systemd systemd-sysv libpam-systemd libnss-myhostname libnss-mymachines libsystemd0 libsystemd-dev libsystemd-login-dev libsystemd-daemon-dev libsystemd-journal-

Bug#783509: marked as done (tmp.mount activated accidentally via bind mount)

2015-06-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jun 2015 10:25:59 + with message-id and subject line Bug#783509: fixed in systemd 220-6 has caused the Debian Bug report #783509, regarding tmp.mount activated accidentally via bind mount to be marked as done. This means that you claim that the problem has been deal

Bug#787542: marked as done (libudev1-udeb depends on missing libcap2)

2015-06-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Jun 2015 10:25:59 + with message-id and subject line Bug#787542: fixed in systemd 220-6 has caused the Debian Bug report #787542, regarding libudev1-udeb depends on missing libcap2 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#770135: systemd: ssh logins considerably delayed (until PAM timeout) when systemd is upgraded but the system not rebooted

2015-06-11 Thread W Forum W
After upgrade to Jessie 8.1 problem still exist ii systemd215-17+deb8u1 systemctl restart systemd-logind.service still have to manually restart the services ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintaine

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
systemd-inhibit Who: NetworkManager (UID 0/root, PID 693/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay 1 inhibitors listed. On Thu, Jun 11, 2015 at 3:16 AM, Michael Biebl wrote: > Control: tags -1 moreinfo > > Am 11.06.2015 um 02:13 sch

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
Here are the NetworkManager.service logs, it sees the first suspend and sleeps but it is not even getting the others -- Logs begin at Thu 2015-06-11 09:30:01 PDT, end at Thu 2015-06-11 09:47:32 PDT. -- Jun 11 09:30:02 debian systemd[1]: Starting Network Manager... -- Subject: Unit NetworkManager.

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Michael Biebl
Am 11.06.2015 um 18:44 schrieb Jessica Frazelle: > systemd-inhibit > Who: NetworkManager (UID 0/root, PID 693/NetworkManager) > What: sleep > Why: NetworkManager needs to turn off networks > Mode: delay > > 1 inhibitors listed. Ok, that looks fine. Do you have an external mo

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
No I don't have an external monitor, I also reproduced this on a ubuntu 15.04 machine and a machine with a commpletely fresh install of debian stretch with gnome. Also I see the same behavior when I change HandleLidSwitchDocked=suspend and run systemctl restart systemd-logind On Thu, Jun 11, 2015

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Michael Biebl
Am 11.06.2015 um 19:06 schrieb Jessica Frazelle: > No I don't have an external monitor, I also reproduced this on a > ubuntu 15.04 machine and a machine with a commpletely fresh install of > debian stretch with gnome. I guess we need a more verbose debug log then. Please boot with systemd.log_leve

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
will do! On Thu, Jun 11, 2015 at 10:29 AM, Michael Biebl wrote: > Am 11.06.2015 um 19:06 schrieb Jessica Frazelle: >> No I don't have an external monitor, I also reproduced this on a >> ubuntu 15.04 machine and a machine with a commpletely fresh install of >> debian stretch with gnome. > > I gues

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
ok confirmed, it was HandleLidSwitchDocked=suspend, it just needed a system reboot to register the change i guess restarting logind doesnt do that On Thu, Jun 11, 2015 at 10:43 AM, Jessica Frazelle wrote: > so weird it is working now... and the debug is the only line I changed... > > > > On T

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Michael Biebl
Am 11.06.2015 um 19:49 schrieb Jessica Frazelle: > ok confirmed, it was HandleLidSwitchDocked=suspend, it just needed a > system reboot to register the change i guess restarting logind doesnt > do that So logind believes your system is docked, probably because it detected a second graphics device.

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Michael Biebl
Am 11.06.2015 um 20:04 schrieb Jessica Frazelle: > attached here Ok, two things: If you suspend/resume/suspend within 90secs, systemd will ignore the 2n suspend request. That's this line: > Jun 11 10:42:17 debian systemd-logind[706]: Ignoring lid switch request, system startup or resume too clos

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

2015-06-11 Thread Jessica Frazelle
jessie at debian in ~ $ ls -la /sys/class/drm total 0 drwxr-xr-x 2 root root0 Jun 11 11:39 . drwxr-xr-x 51 root root0 Jun 11 11:39 .. lrwxrwxrwx 1 root root0 Jun 11 11:39 card0 -> ../../devices/pci:00/:00:02.0/drm/card0 lrwxrwxrwx 1 root root0 Jun 11 11:39 card0-DP-1 -> .

[bts-link] source package systemd

2015-06-11 Thread bts-link-upstream
# # 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 #746151 (http://bugs.debian.org/746151) # Bug title: systemd: daemon-reload+reload kil

Processed: [bts-link] source package systemd

2015-06-11 Thread Debian Bug Tracking System
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.o

Bug#787731: adds google nameserver without being asked to

2015-06-11 Thread Michael Biebl
Am 10.06.2015 um 11:37 schrieb Michael Biebl: > Am 09.06.2015 um 13:14 schrieb Marc Haber: >> On Sat, Jun 06, 2015 at 09:42:37PM +0200, Michael Biebl wrote: >>> This change is imho too invasive for being backported to the stable v215 >>> in jessie. The first Debian version carrying that fix is 217-