Bug#737825: another hang of systemd-tty-ask-password-agent

2015-02-10 Thread Ralf Schlatterbeck
Hmm, looking closer: Is there a process "systemd" supposed to run? I don't have one on that machine: # ps auxwww | grep systemd root 147 0.0 0.1 32956 4512 ?Ss Feb10 0:47 /lib/systemd/systemd-journald root 166 0.0 0.0 41472 3636 ?Ss Feb10 0:00 /lib/sys

Bug#737825: another hang of systemd-tty-ask-password-agent

2015-02-10 Thread Ralf Schlatterbeck
On Tue, Feb 10, 2015 at 07:56:12PM +0100, Michael Biebl wrote: > Can you provide instructions how we can reproduce the problem? > Ideally starting from a pristine, minimal debian jessie installation. Not really, it happened when I tried to apt-get update apt-get upgrade from a system installed abo

Re: Bug#776799: unblock: systemd/215-11

2015-02-10 Thread Niels Thykier
On 2015-02-10 13:12, Cyril Brulebois wrote: > Control: tag -1 confirmed > > Niels Thykier (2015-02-06): >> [...] >> >> Hi, >> >> Thanks, looks good to me. >> >> As a formality, it still needs a d-i ack for this. :) > > No objections, thanks. > > Mraw, > KiBi. > Unblocked, thanks. ~Niels

Bug#737825: another hang of systemd-tty-ask-password-agent

2015-02-10 Thread Michael Biebl
Am 10.02.2015 um 19:10 schrieb Ralf Schlatterbeck: > If you suggest any further tries / experiments, this > machine isn't production so I can try all sort of stuff. Can you provide instructions how we can reproduce the problem? Ideally starting from a pristine, minimal debian jessie installation.

Bug#737825: another hang of systemd-tty-ask-password-agent

2015-02-10 Thread Ralf Schlatterbeck
I've recently tried to upgrade a running debian testing system. It hung on upgrade of network-manager. Now if I manually start dpkg --pending --configure network manager fails to start and the process hanges. To confirm it is waiting on systemd-tty-ask-password-agent see the following output of ps

Bug#777613: systemctl enable/disable does not handle .service symlinks

2015-02-10 Thread Martin Pitt
Package: systemd Version: 218-1 Severity: serious Michael spotted that with the experimental systemd, "systemd enable/disable ssh" does not create/remove the /etc/systemd/system/sshd.service symlink any more, it just calls update-rc.d. This worked up to 217-n, but not with 218-1 any more. git bis

Bug#765870: marked as done (systemd-logind brings system to knees with RAM consumption)

2015-02-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Feb 2015 14:24:08 +0100 with message-id <20150210132408.gc3...@piware.de> and subject line Re: Bug#765870: systemd-logind brings system to knees with RAM consumption  has caused the Debian Bug report #765870, regarding systemd-logind brings system to knees with RAM cons

Re: Bug#776799: unblock: systemd/215-11

2015-02-10 Thread Cyril Brulebois
Control: tag -1 confirmed Niels Thykier (2015-02-06): > Control: tags -1 d-i > > On 2015-02-01 21:16, Martin Pitt wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: unblock > > > > systemd 215-11 hit unstable three days ago

Bug#755722: systemd must sync systemclock to RTC on shutdown

2015-02-10 Thread Martin Pitt
Control: severity -1 normal Stefan Fritsch [2015-01-31 10:19 +0100]: > severity 755722 serious > retitle 755722 systemd must sync systemclock to RTC on shutdown This is severity inflation according to https://www.debian.org/Bugs/Developer#severities ; adjusting back to original severity. I also

Processed: Re: Bug#755722: systemd must sync systemclock to RTC on shutdown

2015-02-10 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #755722 [systemd-sysv] systemd must sync systemclock to RTC on shutdown Severity set to 'normal' from 'serious' -- 755722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755722 Debian Bug Tracking System Contact ow...@bugs.debian.org with p