systemd-cron 1.5.13-1 MIGRATED to testing

2018-04-02 Thread Debian testing watch 
FYI: The status of the systemd-cron source package
in Debian's testing distribution has changed.

  Previous version: 1.5.12-2
  Current version:  1.5.13-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
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#867368: systemd-udevd: delays boot for 2+ minutes when LVM PV is inside a LV

2018-04-02 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 lvm2
Bug #867368 [udev] systemd-udevd: delays boot for 2+ minutes when LVM PV is 
inside a LV
Bug reassigned from package 'udev' to 'lvm2'.
No longer marked as found in versions systemd/232-25.
Ignoring request to alter fixed versions of bug #867368 to the same values 
previously set

-- 
867368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867368
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#894605: systemd: System fails to suspend.

2018-04-02 Thread Michael Biebl 
Am 02.04.2018 um 10:20 schrieb Hubert Golembiowski:
> Package: systemd
> Version: 238-3
> Severity: normal
> 
> Dear Maintainer,
> 
> Following issue observed:
> - Select "Suspend" from UI or close laptop lid (closing lid is set to trigger
> suspend)
> - System doesn't suspend but instead:
> - screen goes blank
> - keyboard stops to take input
> - pc is still running (fans, leds are on, etc.)
> - The only way to get out if that state is hard reset
> - This used to work without any problem, issue appeared 4-5 days ago

What happens if you run (as root)
echo "mem" > /sys/power/state

Did you upgrade other packages the last couple of days, like say the
kernel? Does the failure to suspend correlate with a certain package update?
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature
___
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#883877: marked as done (systemd segfaults in manager_unref_uid_internal)

2018-04-02 Thread Debian Bug Tracking System 
Your message dated Mon, 2 Apr 2018 23:16:27 +0200
with message-id 
and subject line Re: Bug#883877: rsyslog: fails to configure, dpkg --configure 
exits with error
has caused the Debian Bug report #883877,
regarding systemd segfaults in manager_unref_uid_internal
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
883877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rsyslog
Version: 8.31.0-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

$ sudo LC_ALL=C dpkg --configure --pending
Setting up rsyslog (8.31.0-1) ...
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
Failed to retrieve unit: Connection timed out
Failed to restart rsyslog.service: Connection timed out
See system logs and 'systemctl status rsyslog.service' for details.
invoke-rc.d: initscript rsyslog, action "restart" failed.
Failed to get properties: Connection timed out
dpkg: error processing package rsyslog (--configure):
 installed rsyslog package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 rsyslog

$ sudo LC_ALL=C systemctl status rsyslog.service
Failed to get properties: Connection timed out

Dec  8 18:55:47 geode rsyslogd: action '*' treated as ':omusrmsg:*' - please 
use ':omusrmsg:*' syntax instead, '*' will not be supported in the future 
[v8.31.0 try http://www.rsyslog.com/e/2184 ]
Dec  8 18:55:47 geode rsyslogd: error during parsing file 
/etc/rsyslog.d/50-default.conf, on or before line 46: warnings occured in file 
'/etc/rsyslog.d/50-default.conf' around line 46 [v8.31.0 try 
http://www.rsyslog.com/e/2207 ]
Dec  8 18:55:47 geode rsyslogd:  [origin software="rsyslogd" swVersion="8.31.0" 
x-pid="368" x-info="http://www.rsyslog.com;] start
Dec  8 18:55:47 geode rsyslogd: action '*' treated as ':omusrmsg:*' - please 
use ':omusrmsg:*' syntax instead, '*' will not be supported in the future 
[v8.31.0 try http://www.rsyslog.com/e/2184 ]
Dec  8 18:55:47 geode rsyslogd: error during parsing file 
/etc/rsyslog.d/50-default.conf, on or before line 46: warnings occured in file 
'/etc/rsyslog.d/50-default.conf' around line 46 [v8.31.0 try 
http://www.rsyslog.com/e/2207 ]
Dec  8 18:55:47 geode rsyslogd:  [origin software="rsyslogd" swVersion="8.31.0" 
x-pid="368" x-info="http://www.rsyslog.com;] start
Dec  8 18:55:47 geode rsyslogd: Could not open output pipe '/dev/xconsole':: No 
such file or directory [v8.31.0 try http://www.rsyslog.com/e/2039 ]
Dec  8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 
'builtin:ompipe'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.31.0 try http://www.rsyslog.com/e/2007 ]
Dec  8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 
'builtin:ompipe'), next retry is Fri Dec  8 18:56:17 2017, retry nbr 0. There 
should be messages before this one giving the reason for suspension. [v8.31.0 
try http://www.rsyslog.com/e/2007 ]
Dec  8 18:55:47 geode rsyslogd: Could not open output pipe '/dev/xconsole':: No 
such file or directory [v8.31.0 try http://www.rsyslog.com/e/2039 ]
Dec  8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 
'builtin:ompipe'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.31.0 try http://www.rsyslog.com/e/2007 ]
Dec  8 18:55:47 geode rsyslogd: action 'action 9' suspended (module 
'builtin:ompipe'), next retry is Fri Dec  8 18:56:17 2017, retry nbr 0. There 
should be messages before this one giving the reason for suspension. [v8.31.0 
try http://www.rsyslog.com/e/2007 ]

Please see also ( 
https://q-funk.blogspot.fi/2017/12/dbus-rsyslogd-systemd-which-one-is.html )

Thanks!
Martin-Éric

- -- System Information: Debian Release: buster/sid
  APT prefers testing
  APT policy: (, 'testing'), (1101, 'stable'), (1011, 'oldstable'), (1001, 
'oldoldstable'), (500, 'testing-debug')
Architecture: i386 (i586)

Kernel: Linux 4.13.0-1-686 (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rsyslog depends on:
ii  init-system-helpers  1.51
ii  libc62.25-3
ii  libestr0 0.1.10-2.1
ii