Estudio de viabilidad

[Cristina]

 Llamada pendiente @media only screen { html { min-height: 100%; background:
#f3f3f3; } } @media only screen and (max-width: 596px) { .small-float-center
{ margin: 0 auto !important; float: none !important; text-align: center
!important; } .small-text-center { text-align: center !important; }
.small-text-left { text-align: left !important; } .small-text-right {
text-align: right !important; } } @media only screen and (max-width: 596px)
{ .hide-for-large { display: block !important; width: auto !important;
overflow: visible !important; max-height: none !important; font-size:
inherit !important; line-height: inherit !important; } } @media only screen
and (max-width: 596px) { table.body table.container .hide-for-large,
table.body table.container .row.hide-for-large { display: table !important;
width: 100% !important; } } @media only screen and (max-width: 596px) {
table.body table.container .callout-inner.hide-for-large { display:
table-cell !important; width: 100% !important; } } @media only screen and
(max-width: 596px) { table.body table.container .show-for-large { display:
none !important; width: 0; mso-hide: all; overflow: hidden; } } @media only
screen and (max-width: 596px) { table.body img { width: auto; height: auto;
} table.body center { min-width: 0 !important; } table.body .container {
width: 95% !important; } table.body .columns, table.body .column { height:
auto !important; -moz-box-sizing: border-box; -webkit-box-sizing:
border-box; box-sizing: border-box; padding-left: 16px !important;
padding-right: 16px !important; } table.body .columns .column, table.body
.columns .columns, table.body .column .column, table.body .column .columns {
padding-left: 0 !important; padding-right: 0 !important; } table.body
.collapse .columns, table.body .collapse .column { padding-left: 0
!important; padding-right: 0 !important; } td.small-1, th.small-1 { display:
inline-block !important; width: 8.3% !important; } td.small-2,
th.small-2 { display: inline-block !important; width: 16.7% !important;
} td.small-3, th.small-3 { display: inline-block !important; width: 25%
!important; } td.small-4, th.small-4 { display: inline-block !important;
width: 33.3% !important; } td.small-5, th.small-5 { display:
inline-block !important; width: 41.7% !important; } td.small-6,
th.small-6 { display: inline-block !important; width: 50% !important; }
td.small-7, th.small-7 { display: inline-block !important; width: 58.3%
!important; } td.small-8, th.small-8 { display: inline-block !important;
width: 66.7% !important; } td.small-9, th.small-9 { display:
inline-block !important; width: 75% !important; } td.small-10, th.small-10 {
display: inline-block !important; width: 83.3% !important; }
td.small-11, th.small-11 { display: inline-block !important; width:
91.7% !important; } td.small-12, th.small-12 { display: inline-block
!important; width: 100% !important; } .columns td.small-12, .column
td.small-12, .columns th.small-12, .column th.small-12 { display: block
!important; width: 100% !important; } table.body td.small-offset-1,
table.body th.small-offset-1 { margin-left: 8.3% !important;
Margin-left: 8.3% !important; } table.body td.small-offset-2, table.body
th.small-offset-2 { margin-left: 16.7% !important; Margin-left:
16.7% !important; } table.body td.small-offset-3, table.body
th.small-offset-3 { margin-left: 25% !important; Margin-left: 25%
!important; } table.body td.small-offset-4, table.body th.small-offset-4 {
margin-left: 33.3% !important; Margin-left: 33.3% !important; }
table.body td.small-offset-5, table.body th.small-offset-5 { margin-left:
41.7% !important; Margin-left: 41.7% !important; } table.body
td.small-offset-6, table.body th.small-offset-6 { margin-left: 50%
!important; Margin-left: 50% !important; } table.body td.small-offset-7,
table.body th.small-offset-7 { margin-left: 58.3% !important;
Margin-left: 58.3% !important; } table.body td.small-offset-8,
table.body th.small-offset-8 { margin-left: 66.7% !important;
Margin-left: 66.7% !important; } table.body td.small-offset-9,
table.body th.small-offset-9 { margin-left: 75% !important; Margin-left: 75%
!important; } table.body td.small-offset-10, table.body th.small-offset-10 {
margin-left: 83.3% !important; Margin-left: 83.3% !important; }
table.body td.small-offset-11, table.body th.small-offset-11 { margin-left:
91.7% !important; Margin-left: 91.7% !important; } table.body
table.columns td.expander, table.body table.columns th.expander { display:
none !important; } table.body .right-text-pad, table.body .text-pad-right {
padding-left: 10px !important; } table.body .left-text-pad, table.body
.text-pad-left { padding-right: 10px !important; } table.menu { width: 100%
!important; } table.menu td, table.menu th { width: auto !important;
display: inline-block !important; } table.menu.vertical td,
table.menu.vertical th, table.menu.small-vertical td,

Bug#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

[Vincent Lefevre]

On 2018-04-10 12:45:51 +0200, Michael Biebl wrote:
> Do you use hidepid for /proc?

No, I don't.

> > Apr  9 15:33:25 ypig dbus-daemon[2930]: [system] Successfully activated 
> > service 'org.freedesktop.ConsoleKit'
> 
> Please uninstall/purge consolekit. It's not only useless when logind is
> used, but actively harmful:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92

Done. But this doesn't solve the problem.

I get in /var/log/syslog:

[...]
Apr 10 15:06:46 ypig dbus-daemon[2968]: [system] Activating service 
name='org.freedesktop.login1' requested by ':1.4' (uid=0 pid=3014 
comm="/usr/sbin/lightdm ") (using servicehelper)
Apr 10 15:06:47 ypig dbus-daemon[2968]: [system] Activating service 
name='org.freedesktop.systemd1' requested by ':1.5' (uid=0 pid=3160 
comm="/lib/systemd/systemd-logind ") (using servicehelper)
Apr 10 15:06:47 ypig dbus-daemon[2968]: [system] Successfully activated service 
'org.freedesktop.login1'
Apr 10 15:06:47 ypig dbus-daemon[2968]: [system] Successfully activated service 
'org.freedesktop.systemd1'
Apr 10 15:06:59 ypig dbus-daemon[3338]: [session uid=124 pid=3336] Activating 
service name='org.a11y.Bus' requested by ':1.0' (uid=124 pid=3324 
comm="/usr/sbin/lightdm-gtk-greeter ")
Apr 10 15:06:59 ypig dbus-daemon[3338]: [session uid=124 pid=3336] Successfully 
activated service 'org.a11y.Bus'
Apr 10 15:07:08 ypig dbus-daemon[2968]: [system] Activating service 
name='org.freedesktop.PolicyKit1' requested by ':1.5' (uid=0 pid=3160 
comm="/lib/systemd/systemd-logind ") (using servicehelper)
Apr 10 15:07:08 ypig polkitd[3361]: started daemon version 0.105 using 
authority implementation `local' version `0.105'
Apr 10 15:07:08 ypig dbus-daemon[2968]: [system] Successfully activated service 
'org.freedesktop.PolicyKit1'

The lightdm.log diff:

ypig:~> logdiff -u lightdm.log-237 lightdm.log-238
[... identical lines except pid's ...]
 DEBUG: Activating VT 7
-DEBUG: Activating login1 session c1
-DEBUG: Seat seat0 changes active session to c1
-DEBUG: Session c1 is already active
 DEBUG: Greeter connected version=1.18.3 resettable=false
[... identical lines except pid's ...]

In seat0-greeter.log for systemd 237, I have:

** Message: 15:24:55.160: Starting lightdm-gtk-greeter 2.0.4 (Feb 21 2018, 
10:34:28)
** Message: 15:24:55.247: [Configuration] Reading file: 
/usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_debian.conf
** Message: 15:24:55.255: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf

** (lightdm-gtk-greeter:3321): WARNING **: 15:24:57.408: [PIDs] Failed to 
execute command: upstart
[...]

In seat0-greeter.log for systemd 238, I have:

** (process:3321): WARNING **: 15:06:56.930: Failed to open CK session: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.ConsoleKit was not provided by any .service files
** Message: 15:06:58.135: Starting lightdm-gtk-greeter 2.0.4 (Feb 21 2018, 
10:34:28)
** Message: 15:06:58.206: [Configuration] Reading file: 
/usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_debian.conf
** Message: 15:06:58.214: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: nouveau

** (lightdm-gtk-greeter:3324): WARNING **: 15:07:00.342: [PIDs] Failed to 
execute command: upstart
[...]

So, it seems that with systemd 238, the login1 session is not
activated (and as a consequence, it tries to open a CK session,
which does not work, but this is not the issue here).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
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#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

[Michael Biebl]

Am 10.04.2018 um 02:15 schrieb Vincent Lefevre:
> On 2018-04-09 20:41:55 +0200, Michael Biebl wrote:
>> Not reproducible with a default GNOME / systemd as init installation.
>>
>> Please investigate, if this issue is specific to sysvinit, xfce or some
>> other custom modification (like special kernel parameters)
> 
> I'd say that it is specific to sysvinit. I have two other machines
> with similar configuration but with systemd as the init system instead
> of sysvinit, and I haven't seen any such problem on them.
> 
> The only other major difference between my machines is that the one
> with sysvinit uses the nouveau driver instead of the nvidia one for
> the two other machines, but I doubt very much that this has an
> influence.

Do you use hidepid for /proc?


> Apr  9 15:33:25 ypig dbus-daemon[2930]: [system] Successfully activated 
> service 'org.freedesktop.ConsoleKit'

Please uninstall/purge consolekit. It's not only useless when logind is
used, but actively harmful:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=92



-- 
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#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

[Vincent Lefevre]

On 2018-04-09 20:41:55 +0200, Michael Biebl wrote:
> Not reproducible with a default GNOME / systemd as init installation.
> 
> Please investigate, if this issue is specific to sysvinit, xfce or some
> other custom modification (like special kernel parameters)

I'd say that it is specific to sysvinit. I have two other machines
with similar configuration but with systemd as the init system instead
of sysvinit, and I haven't seen any such problem on them.

The only other major difference between my machines is that the one
with sysvinit uses the nouveau driver instead of the nvidia one for
the two other machines, but I doubt very much that this has an
influence.

I've also checked the logs at startup. With systemd 238 (for which the
problem occurs):

[...]
Apr  9 15:33:17 ypig dbus-daemon[2930]: [system] Activating service 
name='org.freedesktop.login1' requested by ':1.4' (uid=0 pid=2987 
comm="/usr/sbin/lightdm ") (using servicehelper)
Apr  9 15:33:17 ypig dbus-daemon[2930]: [system] Activating service 
name='org.freedesktop.systemd1' requested by ':1.6' (uid=0 pid=3115 
comm="/lib/systemd/systemd-logind ") (using servicehelper)
Apr  9 15:33:17 ypig dbus-daemon[2930]: [system] Successfully activated service 
'org.freedesktop.login1'
Apr  9 15:33:18 ypig dbus-daemon[2930]: [system] Successfully activated service 
'org.freedesktop.systemd1'
Apr  9 15:33:25 ypig dbus-daemon[2930]: [system] Activating service 
name='org.freedesktop.ConsoleKit' requested by ':1.9' (uid=0 pid=3287 
comm="lightdm --session-child 17 20 ") (using servicehelper)
Apr  9 15:33:25 ypig dbus-daemon[2930]: [system] Activating service 
name='org.freedesktop.PolicyKit1' requested by ':1.12' (uid=0 pid=3291 
comm="/usr/sbin/console-kit-daemon --no-daemon ") (using servicehelper)
Apr  9 15:33:25 ypig polkitd[3358]: started daemon version 0.105 using 
authority implementation `local' version `0.105'
Apr  9 15:33:25 ypig dbus-daemon[2930]: [system] Successfully activated service 
'org.freedesktop.PolicyKit1'
Apr  9 15:33:25 ypig dbus-daemon[2930]: [system] Successfully activated service 
'org.freedesktop.ConsoleKit'
Apr  9 15:33:27 ypig dbus-daemon[3376]: [session uid=124 pid=3374] Activating 
service name='org.a11y.Bus' requested by ':1.0' (uid=124 pid=3369 
comm="/usr/sbin/lightdm-gtk-greeter ")
Apr  9 15:33:28 ypig dbus-daemon[3376]: [session uid=124 pid=3374] Successfully 
activated service 'org.a11y.Bus'
[...]

After downgrading to systemd 237:

[...]
Apr  9 15:45:28 ypig dbus-daemon[3024]: [system] Activating service 
name='org.freedesktop.login1' requested by ':1.2' (uid=0 pid=3059 
comm="/usr/sbin/lightdm ") (using servicehelper)
Apr  9 15:45:28 ypig dbus-daemon[3024]: [system] Activating service 
name='org.freedesktop.systemd1' requested by ':1.4' (uid=0 pid=3131 
comm="/lib/systemd/systemd-logind ") (using servicehelper)
Apr  9 15:45:28 ypig dbus-daemon[3024]: [system] Successfully activated service 
'org.freedesktop.login1'
Apr  9 15:45:29 ypig dbus-daemon[3024]: [system] Successfully activated service 
'org.freedesktop.systemd1'
Apr  9 15:45:40 ypig dbus-daemon[3315]: [session uid=124 pid=3313] Activating 
service name='org.a11y.Bus' requested by ':1.0' (uid=124 pid=3308 
comm="/usr/sbin/lightdm-gtk-greeter ")
Apr  9 15:45:40 ypig dbus-daemon[3315]: [session uid=124 pid=3313] Successfully 
activated service 'org.a11y.Bus'
[...]

I assume that the ConsoleKit one can see with systemd 238 is a
fallback due to some issue with login1.

I could try again with systemd 238 and look at the lightdm debug
logs (I no longer have them right now since I rebooted twice) to
see if there's any error.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
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#895239: marked as done ([systemd] suspend works 1st time)

[Debian Bug Tracking System]

Your message dated Mon, 9 Apr 2018 23:43:33 +0200
with message-id <79f72234-8c6f-83d8-4e5d-9af265969...@debian.org>
and subject line Re: Bug#895239: [systemd] suspend works 1st time
has caused the Debian Bug report #895239,
regarding [systemd] suspend works 1st time
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.)


-- 
895239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 232-25+deb9u3
Severity: important

--- Please enter the report below this line. ---

Suspend only works first time.  It worked fine on an ancient Acer Aspire
One.  Now on an Acer S7 392, suspend works on its first try but
afterwards fails.  Currently running the backports kernel but didn't
work with stable either.

$ sudo journalctl -u suspend.target
[sudo] password for tct:
-- Logs begin at Sun 2018-04-08 12:17:50 EDT, end at Sun 2018-04-08
13:49:23 EDT. --
Apr 08 12:48:07 okeeffe systemd[1]: Reached target Suspend.
Apr 08 12:48:07 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 12:48:07 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 12:48:09 okeeffe systemd[1]: Reached target Suspend.
Apr 08 12:48:09 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 12:48:09 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 13:02:36 okeeffe systemd[1]: Reached target Suspend.
Apr 08 13:02:36 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 13:02:36 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 13:28:28 okeeffe systemd[1]: Reached target Suspend.
Apr 08 13:28:28 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 13:28:28 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 13:29:24 okeeffe systemd[1]: Reached target Suspend.
Apr 08 13:29:24 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 13:29:24 okeeffe systemd[1]: Stopped target Suspend.

and relevant portions of syslog:

Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4718]
manager: sleep requested (sleeping: no  enabled: yes)
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4719]
manager: sleeping...
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4720]
manager: NetworkManager state is now ASLEEP
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4724]
device (wlp1s0): state change: activated -> deactivating (reason
'sleeping') [100 110 37]
Apr  8 13:50:09 debian dbus[521]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4770]
device (wlp1s0): state change: deactivating -> disconnected (reason
'sleeping') [110 30 37]
Apr  8 13:50:09 debian systemd[1]: Starting Network Manager Script
Dispatcher Service...
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fd21:9228:e650::b2e on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
2601:14d:4101:380b::b2e on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fd21:9228:e650:0:889d:b57e:e0cc:c4b2 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fd21:9228:e650:0:5e51:4fff:fef2:d5b9 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address fd21:9228:e650:0:5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:889d:b57e:e0cc:c4b2.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
2601:14d:4101:380b:889d:b57e:e0cc:c4b2 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:889d:b57e:e0cc:c4b2.
Apr  8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
2601:14d:4101:380b:5e51:4fff:fef2:d5b9 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group
on interface wlp1s0.IPv6 with address fe80::5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian 

Bug#894605: systemd: System fails to suspend.

[hub...@golembiowski.pl]

> On April 2, 2018 at 11:37 PM Michael Biebl  wrote:
>
>
> 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?

echo "mem" > /sys/power/state suspends system correctly with possibility to wake
up as expected.
 
I run dist-upgrade regularly so I expect a number of packages upgrade recently.
Unfortunately can't correlate as I was not noting down packages being updated.
Found what seem to be related in #892321 mailto:892...@bugs.debian.org but can't
tell if both cases are the same.
 
 
 
 
 
 
 ___
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#895292: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

[Michael Biebl]

Control: severity -1 normal
Control: tags -1 moreinfo unreproducible

Am 09.04.2018 um 16:22 schrieb Vincent Lefevre:
> Control: reassign -1 systemd 238-4
> Control: retitle -1 Restart, Suspend, Hibernate, Shut Down all greyed out in 
> lightdm
> 
> On 2018-04-09 15:10:47 +0200, Vincent Lefevre wrote:
>> After the upgrade to policykit-1 0.105-20, the Restart, Suspend,
>> Hibernate, Shut Down menu entries are all greyed out.
>>
>> Note: lightdm and lightdm-gtk-greeter have not changed.
> 
> This is actually an issue due to the upgrade of systemd from 237-4
> to 238-4, from a previous upgrade (I thought that 238-4 was OK, but
> I now remember that I didn't test after the previous upgrade due to
> a freeze of the X server in lightdm).

Not reproducible with a default GNOME / systemd as init installation.

Please investigate, if this issue is specific to sysvinit, xfce or some
other custom modification (like special kernel parameters)


-- 
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

Processed: Re: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #895292 [systemd] Restart, Suspend, Hibernate, Shut Down all greyed out in 
lightdm
Severity set to 'normal' from 'important'
> tags -1 moreinfo unreproducible
Bug #895292 [systemd] Restart, Suspend, Hibernate, Shut Down all greyed out in 
lightdm
Added tag(s) moreinfo and unreproducible.

-- 
895292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292
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

Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

[Vincent Lefevre]

Control: reassign -1 systemd 238-4
Control: retitle -1 Restart, Suspend, Hibernate, Shut Down all greyed out in 
lightdm

On 2018-04-09 15:10:47 +0200, Vincent Lefevre wrote:
> After the upgrade to policykit-1 0.105-20, the Restart, Suspend,
> Hibernate, Shut Down menu entries are all greyed out.
> 
> Note: lightdm and lightdm-gtk-greeter have not changed.

This is actually an issue due to the upgrade of systemd from 237-4
to 238-4, from a previous upgrade (I thought that 238-4 was OK, but
I now remember that I didn't test after the previous upgrade due to
a freeze of the X server in lightdm).

Downgrading to 237-4 makes these menu entries work again (and
policykit-1 0.105-20 is OK with this).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
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: Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd 238-4
Bug #895292 [policykit-1] policykit-1: Restart, Suspend, Hibernate, Shut Down 
all greyed out in lightdm
Bug reassigned from package 'policykit-1' to 'systemd'.
No longer marked as found in versions policykit-1/0.105-20.
Ignoring request to alter fixed versions of bug #895292 to the same values 
previously set
Bug #895292 [systemd] policykit-1: Restart, Suspend, Hibernate, Shut Down all 
greyed out in lightdm
Marked as found in versions systemd/238-4.
> retitle -1 Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm
Bug #895292 [systemd] policykit-1: Restart, Suspend, Hibernate, Shut Down all 
greyed out in lightdm
Changed Bug title to 'Restart, Suspend, Hibernate, Shut Down all greyed out in 
lightdm' from 'policykit-1: Restart, Suspend, Hibernate, Shut Down all greyed 
out in lightdm'.

-- 
895292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292
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#895239: [systemd] suspend works 1st time

[Ted To]

That doesn't seem to work either.

It's curious as I've corresponded with someone with the exact same model
who asked on the Debian mailing list in 2015.  They now have everything
working great with Linux Mint 18.2.  But even booting off the 18.2 live
ISO, suspend only works the first time so it doesn't seem like it is the
kernel.  Also, as far as they recall, they did not have any special boot
parameter customizations.

In that regard I've even tried a live ISO of Antergos with a very recent
kernel and still only suspends on the first attempt.

On 04/08/2018 04:49 PM, Michael Biebl wrote:
> 
> Am 08.04.2018 um 19:56 schrieb Ted To:
>> Package: systemd
>> Version: 232-25+deb9u3
>> Severity: important
>>
>> --- Please enter the report below this line. ---
>>
>> Suspend only works first time.  It worked fine on an ancient Acer Aspire
>> One.  Now on an Acer S7 392, suspend works on its first try but
>> afterwards fails.  Currently running the backports kernel but didn't
>> work with stable either.
> 
> If you simply run (as root)
> echo mem > /sys/power/state
> 
> can you suspend/resume multiple times?
> 
> If not, it's most likely a kernel problem and not a systemd problem.
> 
> 
> 

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Business relationship!

[Steve M.]

Hello,

Good day to you and your family, I got your email contact during my random 
internet search while looking for a reliable and trustworthy foreigner for 
assistance.  I apologize if the content here is contrary to your moral ethics, 
but please treat with absolute secrecy and personal as the decision you make 
will go a long way to determine our future business relationship.

My name is Steve Mayerhofer. I served in Iraq but now I am serving with the 
82nd Airborne Division Peace keeping force in Afghanistan, I am the officer in 
charge of medics. I was a married man with two lovely daughters, but lost my 
wife through strange illness.

Objective:

I have $18,900,000.00 to my name. It is an oil business money i did with Iraq 
citizens' that worth of $100,000,000.00. but the $18,900,000.00 is my share of 
the business and it's legal. I have successfully moved the funds out of Iraq as 
family valuables with help of a Finance Company through their branch.

i need a foreign partner to enable me receive the fund from the agents since i 
am not currently there now due to the nature of my job. Honestly, i wish you 
and i will discuss more and get along. I'm interested in buying properties such 
as: houses, Building real estate etc. I wait for your contact details, thus 
enabling us move into action. In less than 7 working days, the money ought to 
be in your possession. I shall offer you 20% of the sum for your help and 10% 
will be given to the Charitable Organization and 70% is for my investment 
interest, as you will agree with me that nothing goes for nothing.

I will appreciate your idea and knowledge regarding this or any other 
profitable investment you may suggest. On my next email i will explain to you 
the full details of this investment Proposal. I shall tell you more about 
myself and my family on my next email, upon your respond; you may as well tell 
me little more about yourself.

But the most important thing is ''TRUST'' Can I Trust You? Once the funds get 
to you that you will not betray me and do away with my money. I am very honest 
man and i stand in every of my word and that is my bond. If you are interested 
I will furnish you with more details. This is just a brief of the deal. But the 
whole process is simple and we must keep a low profile at all times.

Kind regards,
Steve Mayerhofer.

___
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.

[Michael Biebl]

Control: tags -1 + moreinfo

Am 02.04.2018 um 23:37 schrieb 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?

Ping




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

Processed: Re: Bug#894605: systemd: System fails to suspend.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #894605 [systemd] systemd: System fails to suspend.
Added tag(s) moreinfo.

-- 
894605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894605
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#895239: [systemd] suspend works 1st time

[Michael Biebl]

Am 08.04.2018 um 19:56 schrieb Ted To:
> Package: systemd
> Version: 232-25+deb9u3
> Severity: important
> 
> --- Please enter the report below this line. ---
> 
> Suspend only works first time.  It worked fine on an ancient Acer Aspire
> One.  Now on an Acer S7 392, suspend works on its first try but
> afterwards fails.  Currently running the backports kernel but didn't
> work with stable either.

If you simply run (as root)
echo mem > /sys/power/state

can you suspend/resume multiple times?

If not, it's most likely a kernel problem and not a systemd problem.





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#895239: [systemd] suspend works 1st time

[Ted To]

Package: systemd
Version: 232-25+deb9u3
Severity: important

--- Please enter the report below this line. ---

Suspend only works first time.  It worked fine on an ancient Acer Aspire
One.  Now on an Acer S7 392, suspend works on its first try but
afterwards fails.  Currently running the backports kernel but didn't
work with stable either.

$ sudo journalctl -u suspend.target
[sudo] password for tct:
-- Logs begin at Sun 2018-04-08 12:17:50 EDT, end at Sun 2018-04-08
13:49:23 EDT. --
Apr 08 12:48:07 okeeffe systemd[1]: Reached target Suspend.
Apr 08 12:48:07 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 12:48:07 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 12:48:09 okeeffe systemd[1]: Reached target Suspend.
Apr 08 12:48:09 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 12:48:09 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 13:02:36 okeeffe systemd[1]: Reached target Suspend.
Apr 08 13:02:36 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 13:02:36 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 13:28:28 okeeffe systemd[1]: Reached target Suspend.
Apr 08 13:28:28 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 13:28:28 okeeffe systemd[1]: Stopped target Suspend.
Apr 08 13:29:24 okeeffe systemd[1]: Reached target Suspend.
Apr 08 13:29:24 okeeffe systemd[1]: suspend.target: Unit is bound to
inactive unit systemd-suspend.service
Apr 08 13:29:24 okeeffe systemd[1]: Stopped target Suspend.

and relevant portions of syslog:

Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4718]
manager: sleep requested (sleeping: no  enabled: yes)
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4719]
manager: sleeping...
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4720]
manager: NetworkManager state is now ASLEEP
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4724]
device (wlp1s0): state change: activated -> deactivating (reason
'sleeping') [100 110 37]
Apr  8 13:50:09 debian dbus[521]: [system] Activating via systemd:
service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr  8 13:50:09 debian NetworkManager[533]:   [1523209809.4770]
device (wlp1s0): state change: deactivating -> disconnected (reason
'sleeping') [110 30 37]
Apr  8 13:50:09 debian systemd[1]: Starting Network Manager Script
Dispatcher Service...
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fd21:9228:e650::b2e on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
2601:14d:4101:380b::b2e on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fd21:9228:e650:0:889d:b57e:e0cc:c4b2 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fd21:9228:e650:0:5e51:4fff:fef2:d5b9 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address fd21:9228:e650:0:5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:889d:b57e:e0cc:c4b2.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
2601:14d:4101:380b:889d:b57e:e0cc:c4b2 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:889d:b57e:e0cc:c4b2.
Apr  8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
2601:14d:4101:380b:5e51:4fff:fef2:d5b9 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address
2601:14d:4101:380b:5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Joining mDNS multicast group
on interface wlp1s0.IPv6 with address fe80::5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Registering new address record
for fe80::5e51:4fff:fef2:d5b9 on wlp1s0.*.
Apr  8 13:50:09 debian avahi-daemon[519]: Withdrawing address record for
fe80::5e51:4fff:fef2:d5b9 on wlp1s0.
Apr  8 13:50:09 debian avahi-daemon[519]: Leaving mDNS multicast group
on interface wlp1s0.IPv6 with address fe80::5e51:4fff:fef2:d5b9.
Apr  8 13:50:09 debian avahi-daemon[519]: Interface wlp1s0.IPv6 no
longer relevant for mDNS.
Apr  8 13:50:09 debian dbus[521]: [system] Successfully activated
service 'org.freedesktop.nm_dispatcher'
Apr  8 13:50:09 debian systemd[1]: Started Network Manager Script
Dispatcher Service.
Apr  8 13:50:09 debian nm-dispatcher: req:1 'connectivity-change': new
request (2 scripts)
Apr  8 13:50:09 debian nm-dispatcher: req:1 'connectivity-change': start
running ordered scripts...
Apr  8 13:50:09 debian NetworkManager[533]:   

Processed: bug 810247 is forwarded to https://github.com/systemd/systemd/issues/8652

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 810247 https://github.com/systemd/systemd/issues/8652
Bug #810247 [udev] Hyper-V network adapters are mapped to a different interface 
(ethN) on every boot
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/8652'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
810247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810247
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#830230: systemd disable wake-on-lan

[Norbert Schulz]

Michael Biebl schrieb:
> On Tue, 19 Jul 2016 17:39:40 +0200 Norbert Schulz
>  wrote:
>>
>> Christian Hofstaedtler schrieb:
>>> * Norbert Schulz  [160718 09:24]:
 Here are the required and some more information.
>>> Thanks for following up on this. Unfortunately, I have no idea
>>> either on what is happening here.
>>>
>> Is there any possibility to get some output if I send a wake-on-lan packet 
>> (with
>> etherwake) to the ethernet card when the system is running?
>>
> 
> Is this still reproducible with an up-to-date stretch or sid system?
> 
Sorry, until today I did not upgrade to stretch.


Norbert Schulz

___
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#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[Michael Biebl]

Am 05.04.2018 um 14:29 schrieb johnw:
> Hi Michael,
> 
> I found out, what cause the problem,
> I have this line in fstab
> "proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2,gid=4   
> 0   0"
> 
> I changed it to
> "proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2    0   0"
> (without gid=4), then the problem is gone.

https://github.com/systemd/systemd/issues/2941#issuecomment-213931080
might be relevant



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

Miners in my community

[Joseph Elibe]

Dear Sir,In a meeting held with the local miners in my  community, we have reached an understanding for me to source for a genuine gold buyer. They have always suffered forceful and intimidating kind of trading by the government and its refineries. Thus it was agreed that direct contact should be made.If you are truly serious to buy gold. I have been mandated to negotiate and make you comfortable so that you can come and buy. They will be interested in a long term contract after the first trench. Please get back to me if you are interested.Yours truly,Mr.Elibe Joseph.

___
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]

#
# 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 #845186 (http://bugs.debian.org/845186)
# Bug title: systemd: does not respect ctrl-c running into timeout when 
starting or stopping services
#  * https://github.com/systemd/systemd/issues/838
#  * remote status changed: (?) -> open
usertags 845186 + 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

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[johnw]

Hi Michael,

I found out, what cause the problem,
I have this line in fstab
"proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2,gid=4   
0   0"

I changed it to
"proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2    0   0"
(without gid=4), then the problem is gone.

Thank you.

-- 
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC




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#810247: RE: Bug#810247: Hyper-V network adapters are mapped to a different interface (ethN) on every boot

[Fernando Soto]

Thanks Michael.
I have reported it upstream:
https://github.com/systemd/systemd/issues/8652

Fernando

-Original Message-
From: Michael Biebl [mailto:bi...@debian.org] 
Sent: Saturday, March 24, 2018 5:25 PM
To: 810...@bugs.debian.org; Martin Pitt ; Fernando Soto 

Subject: Re: RE: Bug#810247: Hyper-V network adapters are mapped to a different 
interface (ethN) on every boot

On Sat, 9 Jan 2016 17:20:26 + Fernando Soto  
wrote:
> Hi Martin,
> 
> Udevadm output is attached.
> 
> Thank you,
> Fernando
> 
> > -Original Message-
> > From: Martin Pitt [mailto:mp...@debian.org]
> > Sent: Saturday, January 09, 2016 10:45 AM
> > To: Fernando Soto; 810...@bugs.debian.org
> > Subject: Re: Bug#810247: Hyper-V network adapters are mapped to a 
> > different interface (ethN) on every boot
> > 
> > Control: tag -1 moreinfo
> > 
> > Fernando Soto [2016-01-08 15:22 +]:
> > > The persistent-net udev rules are not created in virtual 
> > > environments to avoid
> > issues with cloning/migrating VMs.
> > 
> > This was true with the old persistent names in Jessie and before, 
> > but not true any more with current testing and unstable versions. 
> > See /usr/share/doc/udev/README.Debian.gz.
> > 
> > Maybe the current ifnames system cannot figure out an appropriate 
> > name for Hyper-V interfaces?


P:
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_0_16/net/eth0
E:
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_0_16/net/eth0
E: ID_NET_DRIVER=hv_netvsc
E: ID_NET_NAME_MAC=enx00155d0ae2ad
E: ID_OUI_FROM_DATABASE=Microsoft Corporation
E: ID_PATH=acpi-VMBUS:01
E: ID_PATH_TAG=acpi-VMBUS_01
E: IFINDEX=2
E: INTERFACE=eth0
E: MATCHDEVID=0x0
E: MATCHIFTYPE=1
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0
E: TAGS=:systemd:
E: USEC_INITIALIZED=39002

Looks like this is the case.
I notice that there is

Author: Hannes Reinecke 
Date:   Fri Nov 23 14:12:39 2012 +0100

udev: path_id - handle Hyper-V devices

Hyper-V has an abstract bus, which gets renumbered on guest
startup. So instead of the bus numbers we should be using
the device GUIDs, which can be retrieved from the 'device_id'
sysfs attribute.


That doesn't seem to handle network interfaces though.

That said, this doesn't look like a Debian specific problem. So it's probably 
best if you raise this upstream at https://github.com/systemd/systemd

--
Why is it that all of the instruments seeking intelligent life in the universe 
are pointed away from Earth?

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Subvenciones a fondo perdido para pymes

[Elsa]

 Lnea Directa Innovacin Subvenciones Subvenciones a fondo
perdido para pymes. Saber msSubvenciones
europeas, nacionales y de las comunidades autnomas.  Buscador
de subvenciones de toda clase para todo el territorio nacional. 
Alertas programables.  Gestin includa.  
 Quiero saber ms  Si lo prefieres puedes llamarnos al
981 90 49 49(de lunes a viernes de 9 a 16 horas) 
 
 
 
Deseamos que esta comunicación haya resultado de su 
agrado. 
No obstante, si prefiere no recibir más comunicaciones 
de este tipo,
siga este enlace. 
Tenga en cuenta que esta comunicación está dirigida a:
pkg-systemd-maintainers@lists.alioth.debian.org. 
De conformidad con lo establecido en la Ley 34/2002 
Lssice le comunicamos
que este escrito procede de Search Task, s.l.u con cif B70296009 y domicilio
en Calle Benito Blanco Rajoy 7-9, 1º, 15006, A Coruña, con finalidad
publicitaria. Search Task cumple estrictamente la normativa vigente en el
ámbito de protección de sus datos en Internet. Según dispone la Ley
Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter
Personal, le recordamos que tiene derecho legal de acceso, rectificación,
cancelación u oposición escribiendo a searchtaskm...@gmail.com. De
conformidad con lo dispuesto en dicha jurisprudencia, Search Task le
comunica que los datos que nos proporcione formarán parte de un fichero
automatizado de datos de carácter personal, responsabilidad de dicha
entidad, con la finalidad de gestionar las comunicaciones con la misma. Sus
datos han sido obtenidos de una fuente pública. El contenido del presente
comunicado es confidencial y únicamente está dirigida y autorizada su
lectura al consignatario original, quedando prohibidos cualquier
comunicación, o difusión, tanto del comunicado como de su contenido. 
 
 


___
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#878162: fixed in systemd 232-25+deb9u2

[Johan Wassberg]

Seems like it has been fixed in #892794 - great!

-- 
jocar

> On 13 Mar 2018, at 09:42, Johan Wassberg  wrote:
> 
> On Sat, 10 Mar 2018 23:13:21 -0800 Rob Leslie  wrote:
>> The fix for this bug broke the IPv6 networking on one of my systems.
>> 
>> When the RA does not include any MTU information, this patch causes no IPv6 
>> default route to be added at all, leaving the system without IPv6 
>> connectivity. The journal in this case shows:
>> 
>>  systemd-networkd[397]: eno1: Failed to get default router MTU from RA: No 
>> data available
>> 
>> A workaround is to add MTU information to the RA from the router, but I 
>> don’t think this should be necessary.
> 
> We can confirm that the change broke IPv6 on all our updated Stretch
> machines:
> 
> 2018-03-13T08:25:24.671634+01:00 machine.example.com systemd-networkd[286]: 
> ens192: Failed to get default router MTU from RA: No data available
> 
> ```
> $ sysctl -a |grep "accept_ra = "
> net.ipv6.conf.all.accept_ra = 1
> net.ipv6.conf.default.accept_ra = 1
> net.ipv6.conf.ens192.accept_ra = 0
> net.ipv6.conf.lo.accept_ra = 1
> ```
> 
> The sysctl output shows that "accept_ra" is enabled for all entries except
> for the first physical interface.
> 
> Manually setting "accept_ra" to "1" allows us to get a default route,
> but restarting systemd-networkd changes it back to 0.
> 
> -- 
> jocar

___
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: Processed (with 1 error): Re: [Pkg-samba-maint] Bug#886897: Acknowledgement (samba: samba cannot export LUKs encrypted disks mounted manually after systemd boot)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 885325
Bug #885325 {Done: Michael Biebl } [systemd] systemd: Daemon 
start with systemctl start daemon can not find mount point not mounted by boot
Bug #886811 {Done: Michael Biebl } [systemd] Can't do 
system-wide mounts/unmounts in a ssh sessions
Bug #886908 {Done: Michael Biebl } [systemd] systemd enabled 
services unable to access shares
Unarchived Bug 885325
Unarchived Bug 886811
Unarchived Bug 886908
> forcemerge 885325 886897
Bug #885325 {Done: Michael Biebl } [systemd] systemd: Daemon 
start with systemctl start daemon can not find mount point not mounted by boot
Bug #886811 {Done: Michael Biebl } [systemd] Can't do 
system-wide mounts/unmounts in a ssh sessions
Bug #886908 {Done: Michael Biebl } [systemd] systemd enabled 
services unable to access shares
Bug #886897 [systemd] samba: samba cannot export LUKs encrypted disks mounted 
manually after systemd boot
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/7761'.
Marked Bug as done
Marked as fixed in versions systemd/236-3.
Marked as found in versions systemd/236-2.
Added tag(s) fixed-upstream.
Bug #886811 {Done: Michael Biebl } [systemd] Can't do 
system-wide mounts/unmounts in a ssh sessions
Bug #886908 {Done: Michael Biebl } [systemd] systemd enabled 
services unable to access shares
Merged 885325 886811 886897 886908
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
885325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885325
886811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886811
886897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886897
886908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886908
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

Processed (with 1 error): Re: [Pkg-samba-maint] Bug#886897: Acknowledgement (samba: samba cannot export LUKs encrypted disks mounted manually after systemd boot)

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd 236-1
Bug #886897 [samba] samba: samba cannot export LUKs encrypted disks mounted 
manually after systemd boot
Bug reassigned from package 'samba' to 'systemd'.
No longer marked as found in versions samba/2:4.7.3+dfsg-1.
Ignoring request to alter fixed versions of bug #886897 to the same values 
previously set
Bug #886897 [systemd] samba: samba cannot export LUKs encrypted disks mounted 
manually after systemd boot
Marked as found in versions systemd/236-1.
> forcemerge 885325 -1
Failed to forcibly merge 885325: Not altering archived bugs; see unarchive.


-- 
886897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886897
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

Subvención europea a fondo perdido para innovación

[Jorge]

 Soluciones para el iva Horizonte 2020 Subvencin europea a fondo
perdido para innovacinEntre 500mil y 2.5
millones de euros.  Son subvencionables todas las partes del proyecto
(desde su concepcin inicial hasta su comercializacin)..
 Es necesario que tenga alcance europeo.Quiero
saber ms 
 
 
 
Deseamos que esta comunicación haya resultado de su 
agrado. 
No obstante, si prefiere no recibir más comunicaciones 
de este tipo,
siga este enlace. 
Tenga en cuenta que esta comunicación está dirigida a:
pkg-systemd-maintainers@lists.alioth.debian.org. 
De conformidad con lo establecido en la Ley 34/2002 
Lssice le comunicamos
que este escrito procede de Search Task, s.l.u con cif B70296009 y domicilio
en Calle Benito Blanco Rajoy 7-9, 1º, 15006, A Coruña, con finalidad
publicitaria. Search Task cumple estrictamente la normativa vigente en el
ámbito de protección de sus datos en Internet. Según dispone la Ley
Orgánica 15/1999, de 13 de diciembre, de Protección de Datos de Carácter
Personal, le recordamos que tiene derecho legal de acceso, rectificación,
cancelación u oposición escribiendo a searchtaskm...@gmail.com. De
conformidad con lo dispuesto en dicha jurisprudencia, Search Task le
comunica que los datos que nos proporcione formarán parte de un fichero
automatizado de datos de carácter personal, responsabilidad de dicha
entidad, con la finalidad de gestionar las comunicaciones con la misma. Sus
datos han sido obtenidos de una fuente pública. El contenido del presente
comunicado es confidencial y únicamente está dirigida y autorizada su
lectura al consignatario original, quedando prohibidos cualquier
comunicación, o difusión, tanto del comunicado como de su contenido. 
 
 


___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

systemd-cron 1.5.13-1 MIGRATED to testing

[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

[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.

[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)

[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  

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

[Martin-Éric Racine]

This seems to have resolved itself over the past few days.

I have a strong suspicion that a dangling symbolic link in
/etc/alternatives to /etc/ld.so.conf.d/i386-linux-gnu_GL.conf was the
culprit. Doing 'sudo update-alternatives --all' removed it and that
solved a bunch of issues on that particular host.

That systemd would be sensitive to that dangling link however bothers
me. It doesn't bode too well for the distribution's stability, given
how systemd is meant to replace sysvinit and a growing list of other
essential components.

2018-04-02 1:24 GMT+03:00 Michael Biebl :
> On Wed, 17 Jan 2018 05:20:49 +0200 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?=
>  wrote:
>> 2018-01-17 4:24 GMT+02:00 Michael Biebl :
>> > On Tue, 19 Dec 2017 06:55:34 +0100 Michael Biebl  wrote:
>> >> Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine:
>> >> > 2017-12-19 2:02 GMT+02:00 Michael Biebl :
>> >> >> Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine:
>> >> >>> 2017-12-18 2:08 GMT+02:00 Michael Biebl :
>> >>  Hi,
>> >> 
>> >>  I just uploaded v236 today. Before we try to debug this further, it
>> >>  would be great if you can give this version a try. Maybe your issue 
>> >>  is
>> >>  already fixed.
>> >>  If not, we'll have to involve upstream at some point by filing an
>> >>  upstream bug report. But let's first wait for your results with 236-1
>> >> >>>
>> >> >>> The issue is not fixed. Something fails at communicating with dbus,
>> >> >>> and it messes up everything else.
>> >> >>
>> >> >> Just to be sure, have you rebooted your system after upgrading to 
>> >> >> 236-1?
>> >> >
>> >> > Yes I have, but this required issuing "exec reboot -f" to bypass init
>> >> > entirely, otherwise it fails due to the lack of dbus connection.
>> >>
>> >> Sure, if PID 1 has crashed, it will freeze itself and no longer respond
>> >> to any (D-Bus) requests.
>> >>
>> >> When exactly does systemd crash? Is it immediately during boot or after
>> >> you've been using the system for a while?
>> >> I assume it works at least for a while, otherwise no other services
>> >> would be started and you would not be able to log in.
>> >> When systemd crashes, you should get an entry in the kernel log (dmesg)
>> >> respectively the journal.
>> >>
>> >> It would be great if you can follow the instructions at [1] to boot with
>> >> debug logging enabled and then provide a journal log which shows such a
>> >> crash.
>> >>
>> >
>> > Any updates on this?
>>
>> Not yet.  I just spent the last month or so giving interviews to the
>> media.  Will get back to this ASAP.
>>
>
> Ping
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>

___
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#830230: systemd disable wake-on-lan

[Michael Biebl]

On Tue, 19 Jul 2016 17:39:40 +0200 Norbert Schulz
 wrote:
> 
> 
> Christian Hofstaedtler schrieb:
> > * Norbert Schulz  [160718 09:24]:
> >> Here are the required and some more information.
> > 
> > Thanks for following up on this. Unfortunately, I have no idea
> > either on what is happening here.
> > 
> Is there any possibility to get some output if I send a wake-on-lan packet 
> (with
> etherwake) to the ethernet card when the system is running?
> 

Is this still reproducible with an up-to-date stretch or sid system?

-- 
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

Processed: forcibly merging 858211 845186

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 858211 845186
Bug #858211 [systemd] please allow console operator to abort waiting for 
TimeoutStart/Stop
Bug #858211 [systemd] please allow console operator to abort waiting for 
TimeoutStart/Stop
Marked as found in versions systemd/232-5.
Bug #845186 [systemd] systemd: does not respect ctrl-c running into timeout 
when starting or stopping services
Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/838'.
Severity set to 'wishlist' from 'normal'
Marked as found in versions systemd/232-19.
Merged 845186 858211
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
845186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845186
858211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858211
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#793116: marked as done (systemd: journald randomly exits with USR1, leaving /dev/log unusable)

[Debian Bug Tracking System]

Your message dated Mon, 2 Apr 2018 00:36:31 +0200
with message-id <8482a91c-cb35-7c96-9d87-f92649a0c...@debian.org>
and subject line Re: systemd: journald randomly exits with USR1, leaving 
/dev/log unusable
has caused the Debian Bug report #793116,
regarding systemd: journald randomly exits with USR1, leaving /dev/log unusable
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.)


-- 
793116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-17+deb8u1
Severity: normal

Dear Maintainer,

systemd-journald randomly exits sometimes, about once every 2-3 weeks. I cannot
say what leads to the situation, and I'm not sufficiently familiar with systemd
to do the neccesary digging on my own. I forgot to make a
systemd-analyze dump before restarting the service, so I won't be able
to attach it here until this happens again. Let me
know what else I can do to help solve this. The highly critical
side-effect from this bug is that
/dev/log becomes unusable,

# logger -u /dev/log FOO
logger: socket /dev/log: Connection refused

which, among others, makes postfix-policyd-spf-perl crash upon
startup, which results
in Postfix (temporarily) rejecting _all_ incoming mails.

systemctl reports

<<>>snap>>>

- Phillip Berndt


-- Package-specific info:

-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.41-042stab106.6 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-17+deb8u1
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17+deb8u1
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.18-0+deb8u1
ii  libpam-systemd  215-17+deb8u1

Versions of packages systemd suggests:
pn  systemd-ui  

-- no debconf information
--- End Message ---
--- Begin Message ---
We never heard back from Philipp after the bug was tagged moreinfo and
more information has been requested. I'm thus closing this bug report,
also keeping in mind, that a lot has changed in journald, so the
original crash is most likely no longer an issue.

If the issue still persists though, please reopen or file a new bug report.
-- 
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
--- End Message ---
___
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#883569: marked as done (libpam-systemd: Prefer systemd-sysv over systemd-shim)

[Debian Bug Tracking System]

Your message dated Mon, 2 Apr 2018 00:23:51 +0200
with message-id <9300ceda-2d7c-174c-b092-ac5f73f9f...@debian.org>
and subject line Re: Bug#883569: libpam-systemd: Prefer systemd-sysv over 
systemd-shim
has caused the Debian Bug report #883569,
regarding libpam-systemd: Prefer systemd-sysv over systemd-shim
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.)


-- 
883569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-systemd
Version: 235-3
Severity: important

libpam-systemd depending on systemd-shim first causes severe trouble with
resolving dependencies, as APT picks systemd-shim but then later sees a
package which needs systemd-sysv and fails.

I understand the order was necessary for preventing upgrades to stretch
from migrating to systemd, but with the packages now widely installed,
this should not be a problem anymore, as the dependencies are satisfied
already, so APT won't switch them.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'unstable-debug'), 
(500, 'testing-debug'), (100, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-systemd depends on:
ii  dbus1.12.2-1
ii  libc6   2.25-2
ii  libpam-runtime  1.1.8-3.6
ii  libpam0g1.1.8-3.6
ii  libselinux1 2.7-2
ii  systemd 235-3
ii  systemd-sysv235-3

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

-- no debconf information

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
--- End Message ---
--- Begin Message ---
On Fri, 23 Mar 2018 09:03:06 +0100 Martin Pitt  wrote:
> Hello Michael,
> 
> Michael Biebl [2018-03-19  6:44 +0100]:
> > So, what are we going to do now then?
> 
> "Nothing" I supppose. I don't think it's actually broken right now, it just
> feels a little odd to prefer SysV in the dependencies. But with systemd being
> installed by default, I suppose it's okay.

I guess it doesn't make sense then to keep this bug report open. So I'll
close it.
Julian, if you want to get confirmation from the CTTE that actually
switching the dependencies is ok, then I'm fine to comply accordingly.
The decision in #883573 is actually not that helpful to decide this
particular bug report.

Regards,
Michael

-- 
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
--- End Message ---
___
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: rsyslog: fails to configure, dpkg --configure exits with error

[Michael Biebl]

On Wed, 17 Jan 2018 05:20:49 +0200 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?=
 wrote:
> 2018-01-17 4:24 GMT+02:00 Michael Biebl :
> > On Tue, 19 Dec 2017 06:55:34 +0100 Michael Biebl  wrote:
> >> Am 19.12.2017 um 02:18 schrieb Martin-Éric Racine:
> >> > 2017-12-19 2:02 GMT+02:00 Michael Biebl :
> >> >> Am 18.12.2017 um 20:07 schrieb Martin-Éric Racine:
> >> >>> 2017-12-18 2:08 GMT+02:00 Michael Biebl :
> >>  Hi,
> >> 
> >>  I just uploaded v236 today. Before we try to debug this further, it
> >>  would be great if you can give this version a try. Maybe your issue is
> >>  already fixed.
> >>  If not, we'll have to involve upstream at some point by filing an
> >>  upstream bug report. But let's first wait for your results with 236-1
> >> >>>
> >> >>> The issue is not fixed. Something fails at communicating with dbus,
> >> >>> and it messes up everything else.
> >> >>
> >> >> Just to be sure, have you rebooted your system after upgrading to 236-1?
> >> >
> >> > Yes I have, but this required issuing "exec reboot -f" to bypass init
> >> > entirely, otherwise it fails due to the lack of dbus connection.
> >>
> >> Sure, if PID 1 has crashed, it will freeze itself and no longer respond
> >> to any (D-Bus) requests.
> >>
> >> When exactly does systemd crash? Is it immediately during boot or after
> >> you've been using the system for a while?
> >> I assume it works at least for a while, otherwise no other services
> >> would be started and you would not be able to log in.
> >> When systemd crashes, you should get an entry in the kernel log (dmesg)
> >> respectively the journal.
> >>
> >> It would be great if you can follow the instructions at [1] to boot with
> >> debug logging enabled and then provide a journal log which shows such a
> >> crash.
> >>
> >
> > Any updates on this?
> 
> Not yet.  I just spent the last month or so giving interviews to the
> media.  Will get back to this ASAP.
> 

Ping

-- 
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

Processed: tagging 768178, closing 768178

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 768178 + wontfix
Bug #768178 [systemd] LSB/SysV service incorrectly marked as active under 
certain conditions
Bug #763401 [systemd] LSB/SysV service incorrectly marked as active under 
certain conditions
Bug #817892 [systemd] systemd: sysv wrapper breaks LSB exit codes
Added tag(s) wontfix.
Added tag(s) wontfix.
Added tag(s) wontfix.
> close 768178
Bug #768178 [systemd] LSB/SysV service incorrectly marked as active under 
certain conditions
Bug #763401 [systemd] LSB/SysV service incorrectly marked as active under 
certain conditions
Bug #817892 [systemd] systemd: sysv wrapper breaks LSB exit codes
Marked Bug as done
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
763401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763401
768178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768178
817892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817892
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

systemd_238-4_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 01 Apr 2018 13:02:57 +0200
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 238-4
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Changes:
 systemd (238-4) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * udev/net-id: Fix check for address to keep interface names stable
   * debian/copyright: Move global wildcard section to the top
 .
   [ Martin Pitt ]
   * Fix daemon reload failures
 .
   [ Laurent Bigonville ]
   * Fix /sys/fs/cgroup mount when using SELinux.
 Since v236, all cgroups except /sys/fs/cgroup/systemd and
 /sys/fs/cgroup/unified are not mounted when SELinux is enabled (even in
 permissive mode). Disabling SELinux completely restores these cgroups.
 This patch fixes that issue by no longer making the assumption that those
 cgroups are mounted by initrd/dracut before systemd is started.
Checksums-Sha1:
 6358c18af5a705135ae2877bfcf37a6b7f09de66 4846 systemd_238-4.dsc
 2630234e544b0654f6304485c9941c4cf4bb2e26 139840 systemd_238-4.debian.tar.xz
 f6fee1a397fc488200ee342827d73fc98c88341f 9421 systemd_238-4_source.buildinfo
Checksums-Sha256:
 ce4d11ac2f1a1d4c0e06f031420bea2338eb39182a6cec78d90e53a6f599e792 4846 
systemd_238-4.dsc
 fd0353528020e4739b68fd7f68aca88df9fcd78cc78cd10e3d187b745a514846 139840 
systemd_238-4.debian.tar.xz
 954b1eb0652f833dbcd6957729a227ab814be57281f2df1438873bc0352b292e 9421 
systemd_238-4_source.buildinfo
Files:
 55f80c901de554d8b526b209a8053ada 4846 admin optional systemd_238-4.dsc
 94c745a6194a32b57233f9f72812197d 139840 admin optional 
systemd_238-4.debian.tar.xz
 3233bde4bf4c439e295cfcdc0e5b5d7c 9421 admin optional 
systemd_238-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlrAvdcACgkQauHfDWCP
ItxR9RAAlNVSgm7XOUQ/D0AioTXwMySu2FJr+x3hTUsU62VyWLpRDX7xGLFO7gfK
U/j3MBwkvZD0WjkFWh6u9gf/emeQIskQaocUhVNB59iMoymrxdmcud1QzLp4sP2r
wT3R7YPY3N+1Z1zvkgX5Bb9iHszzJAN9dCsVUWXNcYX9FCnILGMYjfRGKGOwsAIh
SjSkKUQHdJ4RJG9wrqL7fGyzWq/k1ZBagLbNuv+PDi/QmX+qTwc/R7/KuqdZsv6e
aZEWgGEzHNVvCb7l8xUAkhWGvJMW5aibsOMIVGORE+nXyQxTNvPB8Ms4m39drm44
4BLOYhWx84W13gPAfOyXtB9BYJouSxfYPXfqV+IyjnUapEHDIv8YLYmNr+FZoj9B
cM2CoqF/pZgUrpww+s3crhrWwLYRRf/wST6cS5Lsp2/gTuffXNV5EhbwmuCAre3F
RqLrjtn2TqCSTyShfaqcfb1FeMCphTcOcMJOkUkpAXsMhSXPyRtAjpMYmUSH942S
QyT7GZN+HJcLe30JWs7wCo4cox0/ZN/WUmtpDb5Y+uIKPn+EENeNhB0+CP5uZycv
EjYWKRLq9xLM1z77JcRXcWIeBRa+vB0YuvtQRhUlEIQncuLSw/qjPZU76TK1CkGY
mhnK99RB/XMeTPPBnzcSkBIm7GFPv6WgHXOXZ4jhBv3Jcs6uz5I=
=h/XJ
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 238-4 (source) into unstable

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 01 Apr 2018 13:02:57 +0200
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump systemd-tests libpam-systemd libnss-myhostname 
libnss-mymachines libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev 
libudev1 libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 238-4
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 systemd-tests - tests for systemd
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Changes:
 systemd (238-4) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * udev/net-id: Fix check for address to keep interface names stable
   * debian/copyright: Move global wildcard section to the top
 .
   [ Martin Pitt ]
   * Fix daemon reload failures
 .
   [ Laurent Bigonville ]
   * Fix /sys/fs/cgroup mount when using SELinux.
 Since v236, all cgroups except /sys/fs/cgroup/systemd and
 /sys/fs/cgroup/unified are not mounted when SELinux is enabled (even in
 permissive mode). Disabling SELinux completely restores these cgroups.
 This patch fixes that issue by no longer making the assumption that those
 cgroups are mounted by initrd/dracut before systemd is started.
Checksums-Sha1:
 6358c18af5a705135ae2877bfcf37a6b7f09de66 4846 systemd_238-4.dsc
 2630234e544b0654f6304485c9941c4cf4bb2e26 139840 systemd_238-4.debian.tar.xz
 f6fee1a397fc488200ee342827d73fc98c88341f 9421 systemd_238-4_source.buildinfo
Checksums-Sha256:
 ce4d11ac2f1a1d4c0e06f031420bea2338eb39182a6cec78d90e53a6f599e792 4846 
systemd_238-4.dsc
 fd0353528020e4739b68fd7f68aca88df9fcd78cc78cd10e3d187b745a514846 139840 
systemd_238-4.debian.tar.xz
 954b1eb0652f833dbcd6957729a227ab814be57281f2df1438873bc0352b292e 9421 
systemd_238-4_source.buildinfo
Files:
 55f80c901de554d8b526b209a8053ada 4846 admin optional systemd_238-4.dsc
 94c745a6194a32b57233f9f72812197d 139840 admin optional 
systemd_238-4.debian.tar.xz
 3233bde4bf4c439e295cfcdc0e5b5d7c 9421 admin optional 
systemd_238-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlrAvdcACgkQauHfDWCP
ItxR9RAAlNVSgm7XOUQ/D0AioTXwMySu2FJr+x3hTUsU62VyWLpRDX7xGLFO7gfK
U/j3MBwkvZD0WjkFWh6u9gf/emeQIskQaocUhVNB59iMoymrxdmcud1QzLp4sP2r
wT3R7YPY3N+1Z1zvkgX5Bb9iHszzJAN9dCsVUWXNcYX9FCnILGMYjfRGKGOwsAIh
SjSkKUQHdJ4RJG9wrqL7fGyzWq/k1ZBagLbNuv+PDi/QmX+qTwc/R7/KuqdZsv6e
aZEWgGEzHNVvCb7l8xUAkhWGvJMW5aibsOMIVGORE+nXyQxTNvPB8Ms4m39drm44
4BLOYhWx84W13gPAfOyXtB9BYJouSxfYPXfqV+IyjnUapEHDIv8YLYmNr+FZoj9B
cM2CoqF/pZgUrpww+s3crhrWwLYRRf/wST6cS5Lsp2/gTuffXNV5EhbwmuCAre3F
RqLrjtn2TqCSTyShfaqcfb1FeMCphTcOcMJOkUkpAXsMhSXPyRtAjpMYmUSH942S
QyT7GZN+HJcLe30JWs7wCo4cox0/ZN/WUmtpDb5Y+uIKPn+EENeNhB0+CP5uZycv
EjYWKRLq9xLM1z77JcRXcWIeBRa+vB0YuvtQRhUlEIQncuLSw/qjPZU76TK1CkGY
mhnK99RB/XMeTPPBnzcSkBIm7GFPv6WgHXOXZ4jhBv3Jcs6uz5I=
=h/XJ
-END PGP 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

Processing of systemd_238-4_source.changes

[Debian FTP Masters]

systemd_238-4_source.changes uploaded successfully to localhost
along with the files:
  systemd_238-4.dsc
  systemd_238-4.debian.tar.xz
  systemd_238-4_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.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

systemd-bootchart 233-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the systemd-bootchart source package
in Debian's testing distribution has changed.

  Previous version: 233-1
  Current version:  233-2

-- 
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

python-systemd 234-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the python-systemd source package
in Debian's testing distribution has changed.

  Previous version: 234-1
  Current version:  234-2

-- 
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

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[ಚಿರಾಗ್ ನಟರಾಜ್]

> No, I tried lightdm lxdm, they have same problem,
> I tried gdm3, but can not login, do not why, the screen just become to 
> blank/black.

> Any idea, how to debug?

Can you try creating a new user and trying to log in as that user? There might 
be something going on with your specific user configuration (do you have any 
user units in ~/.config/systemd/user?).

- Chiraag
-- 
ಚಿರಾಗ್ ನಟರಾಜ್
Graduate Student at Brown University
Email: chiraag.nata...@gmail.com
Phone: 610-350-6329
Website: http://chiraag.nataraj.us


signature.asc
Description: PGP 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

[bts-link] source package systemd

[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 #868159 (http://bugs.debian.org/868159)
# Bug title: systemd-setup-tmpfiles startup error when /srv is on read-only fs
#  * https://github.com/systemd/systemd/issues/8566
#  * remote status changed: (?) -> closed
#  * closed upstream
tags 868159 + fixed-upstream
usertags 868159 + status-closed

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: [bts-link] source package systemd

[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.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #868159 (http://bugs.debian.org/868159)
> # Bug title: systemd-setup-tmpfiles startup error when /srv is on read-only fs
> #  * https://github.com/systemd/systemd/issues/8566
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 868159 + fixed-upstream
Bug #868159 [systemd] systemd-setup-tmpfiles startup error when /srv is on 
read-only fs
Added tag(s) fixed-upstream.
> usertags 868159 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
868159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868159
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#809069: logind sometimes blocks input to X after VT switch

[Ben Hutchings]

On Wed, 2018-03-28 at 12:47 +0200, Michael Biebl wrote:
> Control: tags -1 + moreinfo
> 
> Am 09.03.2017 um 06:40 schrieb Michael Biebl:
> > Hi Ben
> > 
> > On Sat, 26 Dec 2015 22:44:45 + Ben Hutchings 
> > wrote:
> > > Package: systemd
> > > Version: 228-2
> > > Severity: important
> > > 
> > > After switching between a text console (VT 1) and X (VT 7) a few
> > > times, I found that keyboard and mouse input no longer worked in X.
> > > The system log showed this:
[...]
> > Sorry for not replying earlier. This bug is rather old, do you still
> > experience on an up-to-date stretch system?
> 
> This went unanswered, so probably fell through the cracks.
> Ben, do you still run into this issue with stretch and/or buster?

I don't remember seeing this again.

Ben.

-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.



signature.asc
Description: This is a digitally signed message part
___
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#887847: marked as done (Extra quoting needed for the job description)

[Debian Bug Tracking System]

Your message dated Wed, 28 Mar 2018 21:40:37 +
with message-id 
and subject line Bug#887847: fixed in systemd-cron 1.5.13-1
has caused the Debian Bug report #887847,
regarding Extra quoting needed for the job description
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.)


-- 
887847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: systemd-cron
Version: 1.5.12-2
Severity: normal

Found this in the wild: zfsutils-linux package has the following cron.d entry:


# Scrub the second Sunday of every month.
24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] && 
/usr/lib/zfs-linux/scrub


generating this timer unit:


[Unit]
Description=[Timer] "24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x 
/usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-linux/scrub"


which yields:

/run/systemd/generator/cron-zfsutils-linux-root-0.timer:2: Failed to resolve unit specifiers on [Timer] 
"24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] && 
/usr/lib/zfs-linux/scrub", ignoring: Invalid slot

The % should be escaped in Description as well using %%.

-- Package-specific info:
-- output of systemd-delta

-- System Information:
Debian Release: buster/sid
 APT prefers unstable
 APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-cron depends on:
ii  libc6 2.26-4
ii  python3   3.6.4-1
ii  systemd-sysv  236-3

Versions of packages systemd-cron recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.90-3

systemd-cron suggests no packages.
--- End Message ---
--- Begin Message ---
Source: systemd-cron
Source-Version: 1.5.13-1

We believe that the bug you reported is fixed in the latest version of
systemd-cron, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 887...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated 
systemd-cron package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 28 Mar 2018 22:58:07 +0200
Source: systemd-cron
Binary: systemd-cron
Architecture: source amd64
Version: 1.5.13-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Systemd Maintainers 

Changed-By: Alexandre Detiste 
Description:
 systemd-cron - systemd units to provide cron daemon & anacron functionality
Closes: 887847
Changes:
 systemd-cron (1.5.13-1) unstable; urgency=medium
 .
   * remove obsolete hack of $$(bindir) in Makefile
   * escape '%' in unit description (Closes: #887847)
Checksums-Sha1:
 8a47982b7bed9892bb2757a9c0a599af4e08a131 2077 systemd-cron_1.5.13-1.dsc
 66f6f4f5b8e2e328a63c7a4f46c24908b9f4975e 31533 systemd-cron_1.5.13.orig.tar.gz
 b7cf25c6e600b473032b0e77931f83c9543fa99e 6500 
systemd-cron_1.5.13-1.debian.tar.xz
 1a19efe3f8fe22b067c17d934fd6d0bb207fbcc0 6472 
systemd-cron-dbgsym_1.5.13-1_amd64.deb
 fd7af454c35a3e4c78a8c418220aec8443379218 6572 
systemd-cron_1.5.13-1_amd64.buildinfo
 d57cc6cebcfafa32a02c0f60417ac5cc6612c755 34332 systemd-cron_1.5.13-1_amd64.deb
Checksums-Sha256:
 c3989fb40d91f469fd6830dc84aa79c8c7957a579e7f7250c1a16f4898b16d6a 2077 
systemd-cron_1.5.13-1.dsc
 e14143bff01a1c74ee0f8776bc142310f1e165a6ebbee37ed670ff9a24c1cb26 31533 
systemd-cron_1.5.13.orig.tar.gz
 9a89b8ce53e5fe4fe7b81eb741bd2dd2fafb6a4782bab594ab519a6188b31fc8 6500 
systemd-cron_1.5.13-1.debian.tar.xz
 d55613e65d343c7581deda1cfc21d9d92ccd6a1e6e43e22c75151c7be902c067 6472 
systemd-cron-dbgsym_1.5.13-1_amd64.deb
 3d65c2f3a5a8cf9d24adbfff9d5f83a5aeea00677cd6af08928111375940ab88 6572 
systemd-cron_1.5.13-1_amd64.buildinfo
 489e2d6143f2ebfd256391bd517a801566ba73164f855ba4e6680f2e135b3c19 34332 
systemd-cron_1.5.13-1_amd64.deb
Files:
 

Accepted systemd-cron 1.5.13-1 (source amd64) into unstable

[Alexandre Detiste]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 28 Mar 2018 22:58:07 +0200
Source: systemd-cron
Binary: systemd-cron
Architecture: source amd64
Version: 1.5.13-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Systemd Maintainers 

Changed-By: Alexandre Detiste 
Description:
 systemd-cron - systemd units to provide cron daemon & anacron functionality
Closes: 887847
Changes:
 systemd-cron (1.5.13-1) unstable; urgency=medium
 .
   * remove obsolete hack of $$(bindir) in Makefile
   * escape '%' in unit description (Closes: #887847)
Checksums-Sha1:
 8a47982b7bed9892bb2757a9c0a599af4e08a131 2077 systemd-cron_1.5.13-1.dsc
 66f6f4f5b8e2e328a63c7a4f46c24908b9f4975e 31533 systemd-cron_1.5.13.orig.tar.gz
 b7cf25c6e600b473032b0e77931f83c9543fa99e 6500 
systemd-cron_1.5.13-1.debian.tar.xz
 1a19efe3f8fe22b067c17d934fd6d0bb207fbcc0 6472 
systemd-cron-dbgsym_1.5.13-1_amd64.deb
 fd7af454c35a3e4c78a8c418220aec8443379218 6572 
systemd-cron_1.5.13-1_amd64.buildinfo
 d57cc6cebcfafa32a02c0f60417ac5cc6612c755 34332 systemd-cron_1.5.13-1_amd64.deb
Checksums-Sha256:
 c3989fb40d91f469fd6830dc84aa79c8c7957a579e7f7250c1a16f4898b16d6a 2077 
systemd-cron_1.5.13-1.dsc
 e14143bff01a1c74ee0f8776bc142310f1e165a6ebbee37ed670ff9a24c1cb26 31533 
systemd-cron_1.5.13.orig.tar.gz
 9a89b8ce53e5fe4fe7b81eb741bd2dd2fafb6a4782bab594ab519a6188b31fc8 6500 
systemd-cron_1.5.13-1.debian.tar.xz
 d55613e65d343c7581deda1cfc21d9d92ccd6a1e6e43e22c75151c7be902c067 6472 
systemd-cron-dbgsym_1.5.13-1_amd64.deb
 3d65c2f3a5a8cf9d24adbfff9d5f83a5aeea00677cd6af08928111375940ab88 6572 
systemd-cron_1.5.13-1_amd64.buildinfo
 489e2d6143f2ebfd256391bd517a801566ba73164f855ba4e6680f2e135b3c19 34332 
systemd-cron_1.5.13-1_amd64.deb
Files:
 3bdfb209e697a4fac9aaa698c4df6287 2077 admin optional systemd-cron_1.5.13-1.dsc
 eab6eb6c6e94d175965b7c13fa101cf4 31533 admin optional 
systemd-cron_1.5.13.orig.tar.gz
 3ce4f2eb15dcf49486858ecba6112e85 6500 admin optional 
systemd-cron_1.5.13-1.debian.tar.xz
 c73640367a082f85c7c5a7a2ebca1fb7 6472 debug optional 
systemd-cron-dbgsym_1.5.13-1_amd64.deb
 06bdd8478806ebca31cdd6ffd1bd9d00 6572 admin optional 
systemd-cron_1.5.13-1_amd64.buildinfo
 6e46ad3ccd7f0193c285b8574964e3d5 34332 admin optional 
systemd-cron_1.5.13-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAlq8AjMACgkQMfMURUSh
dBoRbxAAhe1KCcjw+IxZ/KN3NicPc1DMsNyJCmMg9zfMdmdIjVhgX0Te6LqA5NoJ
TQUK9OmuYlMHtwger6yuOh3MwXsfJ6cFFaeTfGQsRR0DDq0HrUxd4Nj9urj0WhbH
RKTIeosq8Tj0wIN/AVcSwxuugqU+gJJOrr68zkOJKZb90o92XmutvbSSEm9yud+v
OA3mHGkpRz0Q1ipjJ8vyRAIiFjG/SlJD2m6touPtkhqhe5m1wORpZ6PQCrhzGWOO
WpxtrfL9aFSwPlFVMHhsMCB4RM1iwMOo78+vgQ+tnuOu1Edfii2ghsm9eFVb2LPY
38pbSKn+6RTGZnq2pX1+8KHYUrr3YcIltcgisb2guakdwcYoaBzL4u0W8JS/QCFr
ApJS1veIswYo5tu/SGfi64ux8qV4CPytr7IZpD57lhngK0Da/Ak5gGJ7dVrbPtBx
QQCZkVSEDBik/vRBas+ZN2ZTd2BPMHqmWp4vi0G/3ZaxwjeRBdXDmcvzo9PWruZr
VrE54Iz/nKbp1J47o/6tdh6Ux4DTIjyPAPzvil9+ZBYKs22FZpnrbkSIIInzcgVr
5/aWzOip0exw5FGl8UtdJgjstjVZ9ayrDrfLJpu1VTuaaz98k/o9t+ZxR+2dh+/d
ngfHiG1mhTrROZkVM0xhLPuGnCmxxkqQE8fTZ37BHcxIo4s9Nv0=
=voI9
-END PGP 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

systemd-cron_1.5.13-1_amd64.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 28 Mar 2018 22:58:07 +0200
Source: systemd-cron
Binary: systemd-cron
Architecture: source amd64
Version: 1.5.13-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Systemd Maintainers 

Changed-By: Alexandre Detiste 
Description:
 systemd-cron - systemd units to provide cron daemon & anacron functionality
Closes: 887847
Changes:
 systemd-cron (1.5.13-1) unstable; urgency=medium
 .
   * remove obsolete hack of $$(bindir) in Makefile
   * escape '%' in unit description (Closes: #887847)
Checksums-Sha1:
 8a47982b7bed9892bb2757a9c0a599af4e08a131 2077 systemd-cron_1.5.13-1.dsc
 66f6f4f5b8e2e328a63c7a4f46c24908b9f4975e 31533 systemd-cron_1.5.13.orig.tar.gz
 b7cf25c6e600b473032b0e77931f83c9543fa99e 6500 
systemd-cron_1.5.13-1.debian.tar.xz
 1a19efe3f8fe22b067c17d934fd6d0bb207fbcc0 6472 
systemd-cron-dbgsym_1.5.13-1_amd64.deb
 fd7af454c35a3e4c78a8c418220aec8443379218 6572 
systemd-cron_1.5.13-1_amd64.buildinfo
 d57cc6cebcfafa32a02c0f60417ac5cc6612c755 34332 systemd-cron_1.5.13-1_amd64.deb
Checksums-Sha256:
 c3989fb40d91f469fd6830dc84aa79c8c7957a579e7f7250c1a16f4898b16d6a 2077 
systemd-cron_1.5.13-1.dsc
 e14143bff01a1c74ee0f8776bc142310f1e165a6ebbee37ed670ff9a24c1cb26 31533 
systemd-cron_1.5.13.orig.tar.gz
 9a89b8ce53e5fe4fe7b81eb741bd2dd2fafb6a4782bab594ab519a6188b31fc8 6500 
systemd-cron_1.5.13-1.debian.tar.xz
 d55613e65d343c7581deda1cfc21d9d92ccd6a1e6e43e22c75151c7be902c067 6472 
systemd-cron-dbgsym_1.5.13-1_amd64.deb
 3d65c2f3a5a8cf9d24adbfff9d5f83a5aeea00677cd6af08928111375940ab88 6572 
systemd-cron_1.5.13-1_amd64.buildinfo
 489e2d6143f2ebfd256391bd517a801566ba73164f855ba4e6680f2e135b3c19 34332 
systemd-cron_1.5.13-1_amd64.deb
Files:
 3bdfb209e697a4fac9aaa698c4df6287 2077 admin optional systemd-cron_1.5.13-1.dsc
 eab6eb6c6e94d175965b7c13fa101cf4 31533 admin optional 
systemd-cron_1.5.13.orig.tar.gz
 3ce4f2eb15dcf49486858ecba6112e85 6500 admin optional 
systemd-cron_1.5.13-1.debian.tar.xz
 c73640367a082f85c7c5a7a2ebca1fb7 6472 debug optional 
systemd-cron-dbgsym_1.5.13-1_amd64.deb
 06bdd8478806ebca31cdd6ffd1bd9d00 6572 admin optional 
systemd-cron_1.5.13-1_amd64.buildinfo
 6e46ad3ccd7f0193c285b8574964e3d5 34332 admin optional 
systemd-cron_1.5.13-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAlq8AjMACgkQMfMURUSh
dBoRbxAAhe1KCcjw+IxZ/KN3NicPc1DMsNyJCmMg9zfMdmdIjVhgX0Te6LqA5NoJ
TQUK9OmuYlMHtwger6yuOh3MwXsfJ6cFFaeTfGQsRR0DDq0HrUxd4Nj9urj0WhbH
RKTIeosq8Tj0wIN/AVcSwxuugqU+gJJOrr68zkOJKZb90o92XmutvbSSEm9yud+v
OA3mHGkpRz0Q1ipjJ8vyRAIiFjG/SlJD2m6touPtkhqhe5m1wORpZ6PQCrhzGWOO
WpxtrfL9aFSwPlFVMHhsMCB4RM1iwMOo78+vgQ+tnuOu1Edfii2ghsm9eFVb2LPY
38pbSKn+6RTGZnq2pX1+8KHYUrr3YcIltcgisb2guakdwcYoaBzL4u0W8JS/QCFr
ApJS1veIswYo5tu/SGfi64ux8qV4CPytr7IZpD57lhngK0Da/Ak5gGJ7dVrbPtBx
QQCZkVSEDBik/vRBas+ZN2ZTd2BPMHqmWp4vi0G/3ZaxwjeRBdXDmcvzo9PWruZr
VrE54Iz/nKbp1J47o/6tdh6Ux4DTIjyPAPzvil9+ZBYKs22FZpnrbkSIIInzcgVr
5/aWzOip0exw5FGl8UtdJgjstjVZ9ayrDrfLJpu1VTuaaz98k/o9t+ZxR+2dh+/d
ngfHiG1mhTrROZkVM0xhLPuGnCmxxkqQE8fTZ37BHcxIo4s9Nv0=
=voI9
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processing of systemd-cron_1.5.13-1_amd64.changes

[Debian FTP Masters]

systemd-cron_1.5.13-1_amd64.changes uploaded successfully to localhost
along with the files:
  systemd-cron_1.5.13-1.dsc
  systemd-cron_1.5.13.orig.tar.gz
  systemd-cron_1.5.13-1.debian.tar.xz
  systemd-cron-dbgsym_1.5.13-1_amd64.deb
  systemd-cron_1.5.13-1_amd64.buildinfo
  systemd-cron_1.5.13-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.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

Processed: tagging 792045

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 792045 + wontfix
Bug #792045 [systemd] SHould handle failed stop action in lsb initscript
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
792045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792045
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#809069: logind sometimes blocks input to X after VT switch

[Michael Biebl]

Control: tags -1 + moreinfo

Am 09.03.2017 um 06:40 schrieb Michael Biebl:
> Hi Ben
> 
> On Sat, 26 Dec 2015 22:44:45 + Ben Hutchings 
> wrote:
>> Package: systemd
>> Version: 228-2
>> Severity: important
>>
>> After switching between a text console (VT 1) and X (VT 7) a few
>> times, I found that keyboard and mouse input no longer worked in X.
>> The system log showed this:
>>
>> [switching to VT 1]
>>
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) AIGLX: 
>> Suspending AIGLX clients for VT switch
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 226:0
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:69
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:64
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:66
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:72
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:65
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:68
>> Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:71
>>
>> [switching to VT 7]
>>
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 226:0
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) AIGLX: 
>> Resuming AIGLX clients after VT switch
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) intel(0): 
>> switch to mode 1600x900@60.0 on LVDS1 using pipe 0, position (0, 0), 
>> rotation normal, reflection none
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:69
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:64
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:66
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: The XKEYBOARD 
>> keymap compiler (xkbcomp) reports:
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Meta_R added to symbol map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Meta_L added to symbol map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Key  added to map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: Errors from 
>> xkbcomp are not fatal to the X server
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:72
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: The XKEYBOARD 
>> keymap compiler (xkbcomp) reports:
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Meta_R added to symbol map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Meta_L added to symbol map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error:  
>>   Key  added to map for multiple modifiers
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > 
>>   Using Mod4, ignoring Mod1.
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: Errors from 
>> xkbcomp are not fatal to the X server
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:65
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (--) synaptics: 
>> SynPS/2 Synaptics TouchPad: touchpad found
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:68
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got resume for 13:71
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 226:0
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:69
>> Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) 
>> systemd-logind: got pause for 13:64
>> Dec 26 

Processed: Re: logind sometimes blocks input to X after VT switch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #809069 [systemd] logind sometimes blocks input to X after VT switch
Added tag(s) moreinfo.

-- 
809069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809069
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

Processed: bug 792045 is forwarded to https://github.com/systemd/systemd/issues/8601

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 792045 https://github.com/systemd/systemd/issues/8601
Bug #792045 [systemd] SHould handle failed stop action in lsb initscript
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/8601'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
792045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792045
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

systemd_232-25+deb9u3_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Mar 2018 13:55:43 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-25+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 892794
Changes:
 systemd (232-25+deb9u3) stretch; urgency=medium
 .
   [ Cyril Brulebois ]
   * networkd-ndisc: Handle missing mtu gracefully.
 The previous upload made networkd respect the MTU field in IPv6 RA but
 unfortunately broke setups where there's no such field. (Closes: #892794)
Checksums-Sha1:
 e4226027323eca04a2e365a1b01c2334bdc67406 4797 systemd_232-25+deb9u3.dsc
 4bc17efc2f7190c93ef29ff691f409858a96a90c 208460 
systemd_232-25+deb9u3.debian.tar.xz
 09118a902f720e9e094e51cd23aa67ea32e63bc4 9789 
systemd_232-25+deb9u3_source.buildinfo
Checksums-Sha256:
 0e93ad29a9625e1ed964e949fc6deaa0a94c041a297311cd0c53ece9c00105f1 4797 
systemd_232-25+deb9u3.dsc
 534028b7bbe42ad1b02d2ca5a5ad5e9da4f5dcbf7cdd950cb31af57e6ff80809 208460 
systemd_232-25+deb9u3.debian.tar.xz
 b6f3ef51b3c946abe3b5865fbaa06638865a430868130de14652c6ee3706c4b6 9789 
systemd_232-25+deb9u3_source.buildinfo
Files:
 c772ab338389f4fafb0460f6ba606375 4797 admin optional systemd_232-25+deb9u3.dsc
 2b5ba81a6114e320df2746359b2c727c 208460 admin optional 
systemd_232-25+deb9u3.debian.tar.xz
 99c0c3a568abd0fcdcd1be1124f77dd1 9789 admin optional 
systemd_232-25+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlq5JwkACgkQauHfDWCP
ItxFUBAAmxduN7TZpFk1Bx9o14p9cattKbpfwp7HtPFFqKmwWQnsKK6HXHtte6FI
ZbNoF3r09rGkSLZPgjbdc+T+ld0+Wf7CfwaLDZfm+5Wjma7U/Mw99b6EeSmPmbjk
3vyG754FECIR85Ks+WDwNPHrK1liKgvt0Exql9uviDXbBYKlQ0akri1FUEEy5+ZP
/8evogkjO2VdKU2OG+Gx50KbRro6VnJkFXCdT0GIadPwyLxLuvnX46zTGJFgZerY
o8uaW44GbWaAllbVR6NyDWYUqq+oLiuwd2q53K+gESMwXGL41f91IQSzE0ped2wW
E0rBgTGWei73Gf81FD8a2Obe0/R9CF/g5ZwmTvT3kQ2w1i7TY+1ETEpS/E6pYvsx
wwNGuGU1UbY8nZIQUPAybP2nnvJuVREsNmNCS7hFM20Iq8mSSpk4tz/iBil788h6
oX5PpLrqs2ZZg/6nHSRDeo3tovB87HFo6L2TlNwtIGGtKK3p6ZTT2JFxcLcij9t/
mVwd5r3+XHq23vBflayf0MnG4kv4LD6gGcre8Cs+9HaUm1eFTE1G9s1wR0LWi1ge
x01CEWJtWVHcxGySgHkFw46EBpt6Y3NslwCb2NA/owXge2efNzaTVF6vsqaFbb8f
cEdcOyDV5gLnIv+nN9s9OMoWM/ouph1EMQV4TkgGnEVIZatFNCk=
=n6qy
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Accepted systemd 232-25+deb9u3 (source) into proposed-updates->stable-new, proposed-updates

[Michael Biebl]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Mar 2018 13:55:43 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-25+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 892794
Changes:
 systemd (232-25+deb9u3) stretch; urgency=medium
 .
   [ Cyril Brulebois ]
   * networkd-ndisc: Handle missing mtu gracefully.
 The previous upload made networkd respect the MTU field in IPv6 RA but
 unfortunately broke setups where there's no such field. (Closes: #892794)
Checksums-Sha1:
 e4226027323eca04a2e365a1b01c2334bdc67406 4797 systemd_232-25+deb9u3.dsc
 4bc17efc2f7190c93ef29ff691f409858a96a90c 208460 
systemd_232-25+deb9u3.debian.tar.xz
 09118a902f720e9e094e51cd23aa67ea32e63bc4 9789 
systemd_232-25+deb9u3_source.buildinfo
Checksums-Sha256:
 0e93ad29a9625e1ed964e949fc6deaa0a94c041a297311cd0c53ece9c00105f1 4797 
systemd_232-25+deb9u3.dsc
 534028b7bbe42ad1b02d2ca5a5ad5e9da4f5dcbf7cdd950cb31af57e6ff80809 208460 
systemd_232-25+deb9u3.debian.tar.xz
 b6f3ef51b3c946abe3b5865fbaa06638865a430868130de14652c6ee3706c4b6 9789 
systemd_232-25+deb9u3_source.buildinfo
Files:
 c772ab338389f4fafb0460f6ba606375 4797 admin optional systemd_232-25+deb9u3.dsc
 2b5ba81a6114e320df2746359b2c727c 208460 admin optional 
systemd_232-25+deb9u3.debian.tar.xz
 99c0c3a568abd0fcdcd1be1124f77dd1 9789 admin optional 
systemd_232-25+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlq5JwkACgkQauHfDWCP
ItxFUBAAmxduN7TZpFk1Bx9o14p9cattKbpfwp7HtPFFqKmwWQnsKK6HXHtte6FI
ZbNoF3r09rGkSLZPgjbdc+T+ld0+Wf7CfwaLDZfm+5Wjma7U/Mw99b6EeSmPmbjk
3vyG754FECIR85Ks+WDwNPHrK1liKgvt0Exql9uviDXbBYKlQ0akri1FUEEy5+ZP
/8evogkjO2VdKU2OG+Gx50KbRro6VnJkFXCdT0GIadPwyLxLuvnX46zTGJFgZerY
o8uaW44GbWaAllbVR6NyDWYUqq+oLiuwd2q53K+gESMwXGL41f91IQSzE0ped2wW
E0rBgTGWei73Gf81FD8a2Obe0/R9CF/g5ZwmTvT3kQ2w1i7TY+1ETEpS/E6pYvsx
wwNGuGU1UbY8nZIQUPAybP2nnvJuVREsNmNCS7hFM20Iq8mSSpk4tz/iBil788h6
oX5PpLrqs2ZZg/6nHSRDeo3tovB87HFo6L2TlNwtIGGtKK3p6ZTT2JFxcLcij9t/
mVwd5r3+XHq23vBflayf0MnG4kv4LD6gGcre8Cs+9HaUm1eFTE1G9s1wR0LWi1ge
x01CEWJtWVHcxGySgHkFw46EBpt6Y3NslwCb2NA/owXge2efNzaTVF6vsqaFbb8f
cEdcOyDV5gLnIv+nN9s9OMoWM/ouph1EMQV4TkgGnEVIZatFNCk=
=n6qy
-END PGP 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#893574: closed by Simon McVittie <s...@debian.org> (Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat)

[Michael Biebl]

Control: reopen -1
Control: reassign -1 gnome-settings-daemon
Control: found -1 3.28.0-1

Am 27.03.2018 um 11:23 schrieb floris:
> Debian Bug Tracking System schreef op 2018-03-24 22:42:
>> This is an automatic notification regarding your Bug report
>> which was filed against the systemd package:
>>
>> #893574: gnome-shell: Suspend after 20 minutes even there is activity
>> on a seat
>>
>> It has been closed by Simon McVittie .
>>
>> Their explanation is attached below along with your original report.
>> If this explanation is unsatisfactory and you have not received a
>> better one in a separate message then please contact Simon McVittie
>>  by
>> replying to this email.
> 
> 
> Sorry, I cheered too early.
> 
> After some testing I think gsd-power from gnome-settings-daemon is
> monitoring the state of each seat, but fails to check if another one is
> still active
> (full log as attachment)
> 
> mrt 27 10:23:19 Jessica gsd-power[1568]: Starting power manager
> mrt 27 10:23:19 Jessica gsd-power[1568]: Registered client at path
> /org/gnome/SessionManager/Client17
> mrt 27 10:23:19 Jessica gsd-power[1568]: Adding suspend delay inhibitor
> 
> mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep callback 1200s
> <--- No user has a 20 minutes suspend setting in gnome-control-center
> power. Is this gdm3?

Check with systemd-cgls or pstree, which process group 1568 belongs to.

> mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep warning
> callback 96 msec
> mrt 27 10:23:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
> mrt 27 10:23:19 Jessica gsd-power[1568]: System inhibitor fd is 13
> mrt 27 10:25:20 Jessica gsd-power[1568]: disabling server builtin
> screensaver: (xset s 0 0; xset s blank; xset s expose)
> mrt 27 10:28:28 Jessica gsd-power[1568]: Received screensaver
> ActiveChanged signal: 1 (old: 0)
> mrt 27 10:28:28 Jessica gsd-power[1568]: setting up blank callback for 15s
> mrt 27 10:28:28 Jessica gsd-power[1568]: setting up sleep callback 1200s
> mrt 27 10:28:28 Jessica gsd-power[1568]: setting up sleep warning
> callback 96 msec
> mrt 27 10:28:28 Jessica gsd-power[1568]: Doing a state transition: blank
> mrt 27 10:28:28 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
> mrt 27 10:28:29 Jessica gsd-power[1568]: idletime watch: blank (3)
> mrt 27 10:28:29 Jessica gsd-power[1568]: Not going to 'less idle' mode
> blank (current: blank)
> mrt 27 10:39:18 Jessica gsd-power[1568]: idletime watch: sleep-warning (5)
> mrt 27 10:39:19 Jessica gsd-power[1568]: Doing a state transition: normal
> mrt 27 10:39:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
> mrt 27 10:39:34 Jessica gsd-power[1568]: Doing a state transition: blank
> mrt 27 10:39:34 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
> mrt 27 10:43:18 Jessica gsd-power[1568]: idletime watch: sleep (4)
> 
> mrt 27 10:43:18 Jessica gsd-power[1568]: Doing a state transition: sleep
> <-- Is gsd-power responsible for the sleep mode or only the messenger?
> 
> mrt 27 10:43:19 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
> mrt 27 10:43:19 Jessica gsd-power[1568]: Removing suspend delay inhibitor
> mrt 27 10:43:29 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
> mrt 27 10:43:29 Jessica gsd-power[1568]: Adding suspend delay inhibitor
> mrt 27 10:43:29 Jessica gsd-power[1568]: Doing a state transition: normal
> mrt 27 10:43:29 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
> mrt 27 10:43:29 Jessica gsd-power[1568]: System inhibitor fd is 14
> mrt 27 10:43:29 Jessica gsd-power[1568]: idletime reset
> 
> I hope someone can point me in the right direction to find the source.

I'm going to reopen and reassign this to gnome-settings-daemon (which
provides gsd-power)


-- 
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

Processed: Re: Bug#893574: closed by Simon McVittie <s...@debian.org> (Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #893574 {Done: Simon McVittie } [systemd] gnome-shell: 
Suspend after 20 minutes even there is activity on a seat
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 238-3.
> reassign -1 gnome-settings-daemon
Bug #893574 [systemd] gnome-shell: Suspend after 20 minutes even there is 
activity on a seat
Bug reassigned from package 'systemd' to 'gnome-settings-daemon'.
No longer marked as found in versions systemd/238-2.
Ignoring request to alter fixed versions of bug #893574 to the same values 
previously set
> found -1 3.28.0-1
Bug #893574 [gnome-settings-daemon] gnome-shell: Suspend after 20 minutes even 
there is activity on a seat
Marked as found in versions gnome-settings-daemon/3.28.0-1.

-- 
893574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893574
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#893574: closed by Simon McVittie <s...@debian.org> (Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat)

[floris]

Debian Bug Tracking System schreef op 2018-03-24 22:42:

This is an automatic notification regarding your Bug report
which was filed against the systemd package:

#893574: gnome-shell: Suspend after 20 minutes even there is activity 
on a seat


It has been closed by Simon McVittie .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Simon McVittie
 by
replying to this email.



Sorry, I cheered too early.

After some testing I think gsd-power from gnome-settings-daemon is 
monitoring the state of each seat, but fails to check if another one is 
still active

(full log as attachment)

mrt 27 10:23:19 Jessica gsd-power[1568]: Starting power manager
mrt 27 10:23:19 Jessica gsd-power[1568]: Registered client at path 
/org/gnome/SessionManager/Client17

mrt 27 10:23:19 Jessica gsd-power[1568]: Adding suspend delay inhibitor

mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep callback 1200s 
<--- No user has a 20 minutes suspend setting in gnome-control-center 
power. Is this gdm3?


mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep warning 
callback 96 msec

mrt 27 10:23:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:23:19 Jessica gsd-power[1568]: System inhibitor fd is 13
mrt 27 10:25:20 Jessica gsd-power[1568]: disabling server builtin 
screensaver: (xset s 0 0; xset s blank; xset s expose)
mrt 27 10:28:28 Jessica gsd-power[1568]: Received screensaver 
ActiveChanged signal: 1 (old: 0)
mrt 27 10:28:28 Jessica gsd-power[1568]: setting up blank callback for 
15s

mrt 27 10:28:28 Jessica gsd-power[1568]: setting up sleep callback 1200s
mrt 27 10:28:28 Jessica gsd-power[1568]: setting up sleep warning 
callback 96 msec

mrt 27 10:28:28 Jessica gsd-power[1568]: Doing a state transition: blank
mrt 27 10:28:28 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
mrt 27 10:28:29 Jessica gsd-power[1568]: idletime watch: blank (3)
mrt 27 10:28:29 Jessica gsd-power[1568]: Not going to 'less idle' mode 
blank (current: blank)
mrt 27 10:39:18 Jessica gsd-power[1568]: idletime watch: sleep-warning 
(5)
mrt 27 10:39:19 Jessica gsd-power[1568]: Doing a state transition: 
normal

mrt 27 10:39:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:39:34 Jessica gsd-power[1568]: Doing a state transition: blank
mrt 27 10:39:34 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
mrt 27 10:43:18 Jessica gsd-power[1568]: idletime watch: sleep (4)

mrt 27 10:43:18 Jessica gsd-power[1568]: Doing a state transition: sleep 
<-- Is gsd-power responsible for the sleep mode or only the messenger?


mrt 27 10:43:19 Jessica gsd-power[1568]: TESTSUITE: Blanked screen
mrt 27 10:43:19 Jessica gsd-power[1568]: Removing suspend delay 
inhibitor

mrt 27 10:43:29 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:43:29 Jessica gsd-power[1568]: Adding suspend delay inhibitor
mrt 27 10:43:29 Jessica gsd-power[1568]: Doing a state transition: 
normal

mrt 27 10:43:29 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:43:29 Jessica gsd-power[1568]: System inhibitor fd is 14
mrt 27 10:43:29 Jessica gsd-power[1568]: idletime reset

I hope someone can point me in the right direction to find the source.

Floris-- Logs begin at Fri 2017-12-08 00:08:13 CET, end at Tue 2018-03-27 11:08:45 
CEST. --
mrt 27 10:23:19 Jessica gsd-power[1568]: Starting power manager
mrt 27 10:23:19 Jessica gsd-power[1569]: Starting power manager
mrt 27 10:23:19 Jessica gsd-power[1569]: Registered client at path 
/org/gnome/SessionManager/Client19
mrt 27 10:23:19 Jessica gsd-power[1568]: Registered client at path 
/org/gnome/SessionManager/Client17
mrt 27 10:23:19 Jessica gsd-power[1568]: Adding suspend delay inhibitor
mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep callback 1200s
mrt 27 10:23:19 Jessica gsd-power[1568]: setting up sleep warning callback 
96 msec
mrt 27 10:23:19 Jessica gsd-power[1568]: TESTSUITE: Unblanked screen
mrt 27 10:23:19 Jessica gsd-power[1568]: System inhibitor fd is 13
mrt 27 10:23:19 Jessica gsd-power[1569]: Adding suspend delay inhibitor
mrt 27 10:23:19 Jessica gsd-power[1569]: setting up sleep callback 1200s
mrt 27 10:23:19 Jessica gsd-power[1569]: setting up sleep warning callback 
96 msec
mrt 27 10:23:19 Jessica gsd-power[1569]: TESTSUITE: Unblanked screen
mrt 27 10:23:19 Jessica gsd-power[1569]: System inhibitor fd is 13
mrt 27 10:23:25 Jessica gsd-power[1569]: Received session is active change: now 
inactive
mrt 27 10:23:30 Jessica gsd-power[1959]: Starting power manager
mrt 27 10:23:30 Jessica gsd-power[1959]: Registered client at path 
/org/gnome/SessionManager/Client15
mrt 27 10:23:32 Jessica gsd-power[1959]: Adding suspend delay inhibitor
mrt 27 10:23:32 Jessica gsd-power[1959]: setting up sleep callback 900s
mrt 27 10:23:32 Jessica gsd-power[1959]: setting up sleep warning 

Processing of systemd_232-25+deb9u3_source.changes

[Debian FTP Masters]

systemd_232-25+deb9u3_source.changes uploaded successfully to localhost
along with the files:
  systemd_232-25+deb9u3.dsc
  systemd_232-25+deb9u3.debian.tar.xz
  systemd_232-25+deb9u3_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.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

systemd_232-25+deb9u3_source.changes ACCEPTED into proposed-updates->stable-new

[Debian FTP Masters]

Mapping stretch to stable.
Mapping stable to proposed-updates.

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Mar 2018 13:55:43 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote 
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines 
libnss-resolve libnss-systemd libsystemd0 libsystemd-dev udev libudev1 
libudev-dev udev-udeb libudev1-udeb
Architecture: source
Version: 232-25+deb9u3
Distribution: stretch
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 libnss-myhostname - nss module providing fallback resolution for the current 
hostname
 libnss-mymachines - nss module to resolve hostnames for local container 
instances
 libnss-resolve - nss module to resolve names via systemd-resolved
 libnss-systemd - nss module providing dynamic user and group name resolution
 libpam-systemd - system and service manager - PAM module
 libsystemd-dev - systemd utility library - development files
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - libudev shared library
 libudev1-udeb - libudev shared library (udeb)
 systemd- system and service manager
 systemd-container - systemd container/nspawn tools
 systemd-coredump - tools for storing and retrieving coredumps
 systemd-journal-remote - tools for sending and receiving remote journal logs
 systemd-sysv - system and service manager - SysV links
 udev   - /dev/ and hotplug management daemon
 udev-udeb  - /dev/ and hotplug management daemon (udeb)
Closes: 892794
Changes:
 systemd (232-25+deb9u3) stretch; urgency=medium
 .
   [ Cyril Brulebois ]
   * networkd-ndisc: Handle missing mtu gracefully.
 The previous upload made networkd respect the MTU field in IPv6 RA but
 unfortunately broke setups where there's no such field. (Closes: #892794)
Checksums-Sha1:
 e4226027323eca04a2e365a1b01c2334bdc67406 4797 systemd_232-25+deb9u3.dsc
 4bc17efc2f7190c93ef29ff691f409858a96a90c 208460 
systemd_232-25+deb9u3.debian.tar.xz
 09118a902f720e9e094e51cd23aa67ea32e63bc4 9789 
systemd_232-25+deb9u3_source.buildinfo
Checksums-Sha256:
 0e93ad29a9625e1ed964e949fc6deaa0a94c041a297311cd0c53ece9c00105f1 4797 
systemd_232-25+deb9u3.dsc
 534028b7bbe42ad1b02d2ca5a5ad5e9da4f5dcbf7cdd950cb31af57e6ff80809 208460 
systemd_232-25+deb9u3.debian.tar.xz
 b6f3ef51b3c946abe3b5865fbaa06638865a430868130de14652c6ee3706c4b6 9789 
systemd_232-25+deb9u3_source.buildinfo
Files:
 c772ab338389f4fafb0460f6ba606375 4797 admin optional systemd_232-25+deb9u3.dsc
 2b5ba81a6114e320df2746359b2c727c 208460 admin optional 
systemd_232-25+deb9u3.debian.tar.xz
 99c0c3a568abd0fcdcd1be1124f77dd1 9789 admin optional 
systemd_232-25+deb9u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlq5JwkACgkQauHfDWCP
ItxFUBAAmxduN7TZpFk1Bx9o14p9cattKbpfwp7HtPFFqKmwWQnsKK6HXHtte6FI
ZbNoF3r09rGkSLZPgjbdc+T+ld0+Wf7CfwaLDZfm+5Wjma7U/Mw99b6EeSmPmbjk
3vyG754FECIR85Ks+WDwNPHrK1liKgvt0Exql9uviDXbBYKlQ0akri1FUEEy5+ZP
/8evogkjO2VdKU2OG+Gx50KbRro6VnJkFXCdT0GIadPwyLxLuvnX46zTGJFgZerY
o8uaW44GbWaAllbVR6NyDWYUqq+oLiuwd2q53K+gESMwXGL41f91IQSzE0ped2wW
E0rBgTGWei73Gf81FD8a2Obe0/R9CF/g5ZwmTvT3kQ2w1i7TY+1ETEpS/E6pYvsx
wwNGuGU1UbY8nZIQUPAybP2nnvJuVREsNmNCS7hFM20Iq8mSSpk4tz/iBil788h6
oX5PpLrqs2ZZg/6nHSRDeo3tovB87HFo6L2TlNwtIGGtKK3p6ZTT2JFxcLcij9t/
mVwd5r3+XHq23vBflayf0MnG4kv4LD6gGcre8Cs+9HaUm1eFTE1G9s1wR0LWi1ge
x01CEWJtWVHcxGySgHkFw46EBpt6Y3NslwCb2NA/owXge2efNzaTVF6vsqaFbb8f
cEdcOyDV5gLnIv+nN9s9OMoWM/ouph1EMQV4TkgGnEVIZatFNCk=
=n6qy
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
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#892302: libpam-systemd: Does not recgonize serial consoles as part of a seat

[Matthew Gabeler-Lee]

Thanks for the very fast reply :)

On Thu, 8 Mar 2018, Michael Biebl wrote:


Are you logging in via serial console as unprivileged user?


Yes.  If I'm root, that grants all access and the session/tty/etc. 
become irrelevant.  But I want to run something as not-root under 
systemd-inhibit.  Yes, I could sudo systemd-inhibit sudo -u ... but 
blech :)



/etc/securetty (pam_securetty) is not really a good idea.


Any thoughts why, other than that the default version of that file seems 
to have everything under the sun listed in it?



That all said, you should really take this up with upstream at
https://github.com/systemd/systemd/issues


ACK, though systemd's official policy is basically "go away if you 
aren't running the bleeding edge".  I can verify the problem code is in 
the git master of systemd, but their policy is to not accept bug reports 
from such "old" versions as Debian runs, and explicitly to redirect back 
to the linux distro for support.


Nevertheless, filed https://github.com/systemd/systemd/issues/8582

--
-Matt
"Reality is that which, when you stop believing in it, doesn't go away".
-- Philip K. Dick
GPG fingerprint: 0061 15DF D282 D4A9 57CE  77C5 16AF 1460 4A3C C4E9

___
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#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[Michael Biebl]

> Mar 12 08:43:37 kvm102 slim[703]: pam_unix(slim:session): session opened for 
> user kaka by (uid=0)
> Mar 12 08:43:37 kvm102 slim[703]: pam_systemd(slim:session): Failed to create 
> session: No such process

Is see that the autopkgtest for logind fails as well:

> autopkgtest [12:38:29]: test logind: [---
>  * try-restarting systemd-logind
>  * daemon is started
>  * loginctl succeeds
>  * XDG_SESSION_ID=
> FAIL: process is not in session cgroup
> /proc/self/cgroup:
> 10:cpuset:/
> 9:cpu,cpuacct:/
> 8:freezer:/
> 7:memory:/
> 6:net_cls,net_prio:/
> 5:devices:/
> 4:pids:/
> 3:perf_event:/
> 2:blkio:/
> 1:name=systemd:/
> 0::/
>SESSIONUID USER SEAT TTY 
> 
> 0 sessions listed.
> Failed to get session path: Caller does not belong to any known session
> autopkgtest [12:38:29]: test logind: ---]
> autopkgtest [12:38:29]: test logind:  - - - - - - - - - - results - - - - - - 
> - - - -
> logind   FAIL non-zero exit status 1
> autopkgtest [12:38:29]: test logind:  - - - - - - - - - - stderr - - - - - - 
> - - - -
> Failed to get session path: Caller does not belong to any known session


https://ci.debian.net/packages/s/systemd/unstable/amd64/
https://ci.debian.net/data/autopkgtest/unstable/amd64/s/systemd/64305/log.gz

Martin, do you have any idea?


-- 
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

systemd 238-3 MIGRATED to testing

[Debian testing watch]

FYI: The status of the systemd source package
in Debian's testing distribution has changed.

  Previous version: 238-2
  Current version:  238-3

-- 
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

Bug#882630: marked as done (systemd-bootchart: debian/copyright refers to CC0 by URL)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 22:21:55 +
with message-id 
and subject line Bug#882630: fixed in systemd-bootchart 233-2
has caused the Debian Bug report #882630,
regarding systemd-bootchart: debian/copyright refers to CC0 by URL
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.)


-- 
882630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-bootchart
Severity: normal
Control: tag -1 + stretch buster
Control: block -1 by 882628

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

This package refers to the text of the Creative Commons Zero license by its URL
on creativecommons.org; as far as I understand, the Debian policy requires that
we ship the actual text of the license [0].

I requested (in #882628) that CC0 be shipped in /usr/share/common-licences, so
it might become possible to refer to that file if you do not wish to include the
whole text in debian/copyright.


Best,

  nicoo

-BEGIN PGP SIGNATURE-

iQJNBAEBCgA3FiEEiWEbFKE2h/s1SpJPnU+IAQz+GeMFAloYvLAZHG5pY29sYXNA
YnJhdWQtc2FudG9uaS5ldQAKCRCdT4gBDP4Z46ptD/4htt8y2sskTGj9gEqrS6cB
ccvvPYkKqJ7an6p7BaEpA/EoAwMPJ67dFfgSw/e0s2a6Ne8asQCGH1prRtOkmXXx
bW7ZvuGzeQSbSXopGHVWHAMH7cByo5nFPZDSpqaRFaNFLSl9PTIQCrfd/TOlHXZd
iQujk/iKYyXEs41drTQKF1wxqI7twMtE9dT2osnTwNkcj3bhaOj9x6eWe0yzMCL6
zhIMkzS0ipsT5BEx6Y1Ifweu3D4dwc6Z0k0UgeueLkkzU0MitjRxBEZv1kB/qKp+
ceT+2LooMqJ/0ouhFedUqzGTn4gM8jC9bxfN3uQfwO1kXFc1eNX3IaeZY1YqZBnj
ml/yMCS0ZQ/8BTZMpLysLH7cNC6Z2AlhVLsnhk47ts75P+YFrgFbC9X2XCQ4e/LW
CakG0JvLjroHOZFxzNgc3KPUNriUifW6DSu8CMjK96dr9AzmBvzLiuE29NZj4gg/
5JokPgBXrs5g6gnleO/F+Ogrif79QVCsSxackj1ci06jW/yi1yXvUike1N8bqC7S
oXNg2TuLgTOO4yPsDcjcpL2pNiDYDCY2AMFvwC/e3PKEeNFAHhwphlz48WNXAvJe
Jz6YC+hTYLQPAy+Rh43FWEV4asYQpUII9ESnD8q3wZex5dWlJ5jqdKi+yIIZARNz
JTKkXvFo8CsCYXmiNClEQw==
=mVQK
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: systemd-bootchart
Source-Version: 233-2

We believe that the bug you reported is fixed in the latest version of
systemd-bootchart, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 882...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt  (supplier of updated systemd-bootchart package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Mar 2018 23:53:27 +0200
Source: systemd-bootchart
Binary: systemd-bootchart
Architecture: source amd64
Version: 233-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Martin Pitt 
Description:
 systemd-bootchart - boot performance graphing tool
Closes: 882630
Changes:
 systemd-bootchart (233-2) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * Update Vcs-* to point to https://salsa.debian.org
   * Set Rules-Requires-Root to no
 .
   [ Nicolas Braud-Santoni ]
   * debian/copyright: Point to CC-1.0 license in /usr/share/common-licenses/
 (Closes: #882630)
 .
   [ Martin Pitt ]
   * debian/copyright: Use https URL for Format:
   * Bump Standards-Version to 4.1.3
   * debian/copyright: Move global wildcard section to the top.
 Fixes lintian warning
 global-files-wildcard-not-first-paragraph-in-dep5-copyright.
Checksums-Sha1:
 96df85503a101b0afe7a4ba0bd457feaa423a3d3 2224 systemd-bootchart_233-2.dsc
 37748e1c6472abcf19cc6c6ba96a42b16b48f721 3976 
systemd-bootchart_233-2.debian.tar.xz
 8f236eff095456c16bb6f15afeff1cba98063514 91952 
systemd-bootchart-dbgsym_233-2_amd64.deb
 a2d2d40285bac93bff3c16d25129df981de0ad4e 6795 
systemd-bootchart_233-2_amd64.buildinfo
 640025e212cfb2f043f6cb4aa4aeff4918c95044 45276 
systemd-bootchart_233-2_amd64.deb
Checksums-Sha256:
 2426ccda61307578d882376b0566343e0fd7769b3b200fd6b31b8511fa84da1d 2224 
systemd-bootchart_233-2.dsc
 d86959f527bd0c99dc552a251acf11e3c6d9c00cf250fa34bff294e10e7f1e9f 3976 
systemd-bootchart_233-2.debian.tar.xz
 64abff7c02b55031df0a5336d0ea02e6064ce1fe71a42886c48330449ce35856 91952 
systemd-bootchart-dbgsym_233-2_amd64.deb
 

Accepted systemd-bootchart 233-2 (source amd64) into unstable

[Martin Pitt]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Mar 2018 23:53:27 +0200
Source: systemd-bootchart
Binary: systemd-bootchart
Architecture: source amd64
Version: 233-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Martin Pitt 
Description:
 systemd-bootchart - boot performance graphing tool
Closes: 882630
Changes:
 systemd-bootchart (233-2) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * Update Vcs-* to point to https://salsa.debian.org
   * Set Rules-Requires-Root to no
 .
   [ Nicolas Braud-Santoni ]
   * debian/copyright: Point to CC-1.0 license in /usr/share/common-licenses/
 (Closes: #882630)
 .
   [ Martin Pitt ]
   * debian/copyright: Use https URL for Format:
   * Bump Standards-Version to 4.1.3
   * debian/copyright: Move global wildcard section to the top.
 Fixes lintian warning
 global-files-wildcard-not-first-paragraph-in-dep5-copyright.
Checksums-Sha1:
 96df85503a101b0afe7a4ba0bd457feaa423a3d3 2224 systemd-bootchart_233-2.dsc
 37748e1c6472abcf19cc6c6ba96a42b16b48f721 3976 
systemd-bootchart_233-2.debian.tar.xz
 8f236eff095456c16bb6f15afeff1cba98063514 91952 
systemd-bootchart-dbgsym_233-2_amd64.deb
 a2d2d40285bac93bff3c16d25129df981de0ad4e 6795 
systemd-bootchart_233-2_amd64.buildinfo
 640025e212cfb2f043f6cb4aa4aeff4918c95044 45276 
systemd-bootchart_233-2_amd64.deb
Checksums-Sha256:
 2426ccda61307578d882376b0566343e0fd7769b3b200fd6b31b8511fa84da1d 2224 
systemd-bootchart_233-2.dsc
 d86959f527bd0c99dc552a251acf11e3c6d9c00cf250fa34bff294e10e7f1e9f 3976 
systemd-bootchart_233-2.debian.tar.xz
 64abff7c02b55031df0a5336d0ea02e6064ce1fe71a42886c48330449ce35856 91952 
systemd-bootchart-dbgsym_233-2_amd64.deb
 0fea1105a6e2949313680387258025eed9418cbd905d233854bd919ddd0f1786 6795 
systemd-bootchart_233-2_amd64.buildinfo
 439c2b0776bd4f5d3b3b5455b79a9c26d1c60a61a674ca3c14f2c28faff00bb4 45276 
systemd-bootchart_233-2_amd64.deb
Files:
 ec95a3d4628793c21b00b18c7716a767 2224 admin optional 
systemd-bootchart_233-2.dsc
 77a5d62ce5d709a5c40296e019c253f6 3976 admin optional 
systemd-bootchart_233-2.debian.tar.xz
 a68b0d591f51abe278c1ccdbdfcc931c 91952 debug optional 
systemd-bootchart-dbgsym_233-2_amd64.deb
 59738283f29675e84ccc9f4b0d07f132 6795 admin optional 
systemd-bootchart_233-2_amd64.buildinfo
 531aea760d55147a35f96338f74a210e 45276 admin optional 
systemd-bootchart_233-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlq4Go4ACgkQxrkYDUvY
t65SiBAAnZsXggO2fm7OXvlkWFg0phTCXkI8K5jRnbbqhW3mxagQojYzjQhQUIg9
h+qc1NSH0A/WxGLfrMU16bTBiJM4foi0bwgs483e1pR0bGvsUPbyPVU0Ml7D6Hm7
F2HEIvvhq6O9j+sd8cyeLPHoMxjPhSmcGlygGutsbLI4jVDZcjtx/R27EwX47SD1
T+gYLs5Pr1ZZsWoqGq0yHD0OPNJ9z+RQDjynouo8/vG+7Orqn4ZCd1RKKULddk7B
zoIdVsi3N8piyzX73OV5j5n4tAmAWmcriHALkNK4+T0fL+w5klfEgDhXjvt/8Ww1
sMIpJnYWDmqLL6Ey8qX/gVM3plZ2sDDBS6yDly0eCAGaq8GscN8V9XTJQlQ5Aw3l
W2jfEhhaOxgFpnQCNWFQHXomSZ4NqVmzSHV38aMeA6oOA2Ntsvx3U5S0OmQnLFyh
VUh82acU0QqlLXwz7DsKi6jJpT0xdpEvGP8VqHHUChqzx6Iba+WMYKOfhgxN5G9h
yf1PVPC92180VaU3QaZYpJ5qbo8SoKuRsuWWtKRnghal2EcS64B4H7kGKNxRDWR/
DcHEDCccosA8EvTHu/ZBO+rbvYk2dxrzIgeEgtB0Kme+iNU+tCsqz7TTEVvXhcET
4nkUctx6wXT+qSARElOUEpxoF5xVd66fk+4eiOyMBWmB4yc/FQA=
=7phi
-END PGP 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

Accepted python-systemd 234-2 (source amd64) into unstable

[Martin Pitt]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Mar 2018 00:00:00 +0200
Source: python-systemd
Binary: python-systemd python3-systemd
Architecture: source amd64
Version: 234-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Martin Pitt 
Description:
 python-systemd - Python 2 bindings for systemd
 python3-systemd - Python 3 bindings for systemd
Changes:
 python-systemd (234-2) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * Update Vcs-* to point to https://salsa.debian.org
   * Set Rules-Requires-Root to no
 .
   [ Martin Pitt ]
   * debian/copyright: Use https URL for Format:
   * debian/copyright: Move global wildcard section to the top.
 Fixes lintian warning
 global-files-wildcard-not-first-paragraph-in-dep5-copyright.
   * Bump Standards-Version to 4.1.3
Checksums-Sha1:
 2df51349c2cef088419d1a1f33d71f1e1b30f264 2187 python-systemd_234-2.dsc
 818c486e08d8110932673f74389131ec0e0d55cd 2888 
python-systemd_234-2.debian.tar.xz
 b43198823a81a3eb479a1cf623733659a0014091 93692 
python-systemd-dbgsym_234-2_amd64.deb
 bedcb14fe071468a4c32869d9a9602989b219720 7474 
python-systemd_234-2_amd64.buildinfo
 db47120832c41ac5da55f571fc94804025c0fddf 35528 python-systemd_234-2_amd64.deb
 e65829f93019d76ecb3fd640f6408344e819a03f 102456 
python3-systemd-dbgsym_234-2_amd64.deb
 6e947fea877405814b53b192fbf0de5897bc59e6 36196 python3-systemd_234-2_amd64.deb
Checksums-Sha256:
 0703203eb16554c32c456d45f5623e094178522f460e97c18134b1e735de3ec9 2187 
python-systemd_234-2.dsc
 c208c3517028b15311b8d923715af743b99e77af4e905f9abac38911b67f228d 2888 
python-systemd_234-2.debian.tar.xz
 e2159347b5b2ce363a47984aaa4529d5c15e57d6bff3a9be7ca67b3d8e90bef1 93692 
python-systemd-dbgsym_234-2_amd64.deb
 0eac52b6727c5c02edd2d3a86be83c979280693caf19f93b24d8499cec675baa 7474 
python-systemd_234-2_amd64.buildinfo
 a70b81c639088d38b4862d9f1f56548ac4b7bec84d431e3a27c94820de90e7fe 35528 
python-systemd_234-2_amd64.deb
 475d496597f3ddb96c5521e17d680ee9d4cc3d98636910fabb6ab0f41bc1f49c 102456 
python3-systemd-dbgsym_234-2_amd64.deb
 e405def9b359ea5144911e47603b7af9fd7f837ee1a4dd488e7f0da366d457b3 36196 
python3-systemd_234-2_amd64.deb
Files:
 540bacb834da846bab4b7ff9d21e615b 2187 python optional python-systemd_234-2.dsc
 676956ba9ed159087e2a9d679dd0f6d9 2888 python optional 
python-systemd_234-2.debian.tar.xz
 4717ee590effd525d2c7ae9c6b4b90eb 93692 debug optional 
python-systemd-dbgsym_234-2_amd64.deb
 f89b9218e248893dc9da948067a84934 7474 python optional 
python-systemd_234-2_amd64.buildinfo
 49c434500bd9fb8c790fe145e42cb0e4 35528 python optional 
python-systemd_234-2_amd64.deb
 afd420b5f66e0789b02395fd7b9db2eb 102456 debug optional 
python3-systemd-dbgsym_234-2_amd64.deb
 0d2b4d8f2db0896b2cd551d8aad27574 36196 python optional 
python3-systemd_234-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlq4G/UACgkQxrkYDUvY
t66+rA//UY+y5F3ah/8IlH9sN0OPNEVYruvEInYFeNFY4RzFYk1C/ptt81w9V08h
lnTRetW+B36WCmhPhv2d/D8hb6WOJBLsTllyqK7jBRpz48W67HVncm7DR37oTHIb
eEFLZywRhaAbwJ20PVoOVrv1MOJtBdjWfsnnnSnhrHGzgp/09KDe1gtu2daPYkDq
MGHp+DHyE7GF25w80R0vIy9aAnEj1cP3zdn5kKo6xNcnkxgGGnOs/51JpikuAv1p
efgQRFcP05CseMmg8tWgRn3WEn3IJA2eZ00KBpWUOIxKCsAKgaMruWFSkoJRv9Mr
dcOg5tbjxErmbg8rNNGXJNRoNIeSlpDSBJ75RVmGbykYUZ3hVt9svIsGFLPOcpUJ
fJUrGXTOsl2xDs6EZuG3YZi6WjPXh2qyC/+lQDcKju7c5NQT6tOHZCvvWxeosbox
SLQFXJ6guy0+n34iwir1zbYj/zMAK7VURwpHFjqQsjf48EbCOE9O+RM52QQsdNin
ErBpPBjWU2n2hF+rULuh1VTWoZIY12rHC3uLiRVMzTmZJWyZYsbzlN2NjdOaA/9X
NPuVM1Q8OnhbcweDwdj+RUx+kHM1y9NTvKUcIljx+DsfclYshqDn/erPG0Tcn/Dw
v8NE5Wx7DnuKekaMgKOltgGoP/x8QCugXrjD65M2+T827flS0sQ=
=qgTf
-END PGP 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

python-systemd_234-2_amd64.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 26 Mar 2018 00:00:00 +0200
Source: python-systemd
Binary: python-systemd python3-systemd
Architecture: source amd64
Version: 234-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Martin Pitt 
Description:
 python-systemd - Python 2 bindings for systemd
 python3-systemd - Python 3 bindings for systemd
Changes:
 python-systemd (234-2) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * Update Vcs-* to point to https://salsa.debian.org
   * Set Rules-Requires-Root to no
 .
   [ Martin Pitt ]
   * debian/copyright: Use https URL for Format:
   * debian/copyright: Move global wildcard section to the top.
 Fixes lintian warning
 global-files-wildcard-not-first-paragraph-in-dep5-copyright.
   * Bump Standards-Version to 4.1.3
Checksums-Sha1:
 2df51349c2cef088419d1a1f33d71f1e1b30f264 2187 python-systemd_234-2.dsc
 818c486e08d8110932673f74389131ec0e0d55cd 2888 
python-systemd_234-2.debian.tar.xz
 b43198823a81a3eb479a1cf623733659a0014091 93692 
python-systemd-dbgsym_234-2_amd64.deb
 bedcb14fe071468a4c32869d9a9602989b219720 7474 
python-systemd_234-2_amd64.buildinfo
 db47120832c41ac5da55f571fc94804025c0fddf 35528 python-systemd_234-2_amd64.deb
 e65829f93019d76ecb3fd640f6408344e819a03f 102456 
python3-systemd-dbgsym_234-2_amd64.deb
 6e947fea877405814b53b192fbf0de5897bc59e6 36196 python3-systemd_234-2_amd64.deb
Checksums-Sha256:
 0703203eb16554c32c456d45f5623e094178522f460e97c18134b1e735de3ec9 2187 
python-systemd_234-2.dsc
 c208c3517028b15311b8d923715af743b99e77af4e905f9abac38911b67f228d 2888 
python-systemd_234-2.debian.tar.xz
 e2159347b5b2ce363a47984aaa4529d5c15e57d6bff3a9be7ca67b3d8e90bef1 93692 
python-systemd-dbgsym_234-2_amd64.deb
 0eac52b6727c5c02edd2d3a86be83c979280693caf19f93b24d8499cec675baa 7474 
python-systemd_234-2_amd64.buildinfo
 a70b81c639088d38b4862d9f1f56548ac4b7bec84d431e3a27c94820de90e7fe 35528 
python-systemd_234-2_amd64.deb
 475d496597f3ddb96c5521e17d680ee9d4cc3d98636910fabb6ab0f41bc1f49c 102456 
python3-systemd-dbgsym_234-2_amd64.deb
 e405def9b359ea5144911e47603b7af9fd7f837ee1a4dd488e7f0da366d457b3 36196 
python3-systemd_234-2_amd64.deb
Files:
 540bacb834da846bab4b7ff9d21e615b 2187 python optional python-systemd_234-2.dsc
 676956ba9ed159087e2a9d679dd0f6d9 2888 python optional 
python-systemd_234-2.debian.tar.xz
 4717ee590effd525d2c7ae9c6b4b90eb 93692 debug optional 
python-systemd-dbgsym_234-2_amd64.deb
 f89b9218e248893dc9da948067a84934 7474 python optional 
python-systemd_234-2_amd64.buildinfo
 49c434500bd9fb8c790fe145e42cb0e4 35528 python optional 
python-systemd_234-2_amd64.deb
 afd420b5f66e0789b02395fd7b9db2eb 102456 debug optional 
python3-systemd-dbgsym_234-2_amd64.deb
 0d2b4d8f2db0896b2cd551d8aad27574 36196 python optional 
python3-systemd_234-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlq4G/UACgkQxrkYDUvY
t66+rA//UY+y5F3ah/8IlH9sN0OPNEVYruvEInYFeNFY4RzFYk1C/ptt81w9V08h
lnTRetW+B36WCmhPhv2d/D8hb6WOJBLsTllyqK7jBRpz48W67HVncm7DR37oTHIb
eEFLZywRhaAbwJ20PVoOVrv1MOJtBdjWfsnnnSnhrHGzgp/09KDe1gtu2daPYkDq
MGHp+DHyE7GF25w80R0vIy9aAnEj1cP3zdn5kKo6xNcnkxgGGnOs/51JpikuAv1p
efgQRFcP05CseMmg8tWgRn3WEn3IJA2eZ00KBpWUOIxKCsAKgaMruWFSkoJRv9Mr
dcOg5tbjxErmbg8rNNGXJNRoNIeSlpDSBJ75RVmGbykYUZ3hVt9svIsGFLPOcpUJ
fJUrGXTOsl2xDs6EZuG3YZi6WjPXh2qyC/+lQDcKju7c5NQT6tOHZCvvWxeosbox
SLQFXJ6guy0+n34iwir1zbYj/zMAK7VURwpHFjqQsjf48EbCOE9O+RM52QQsdNin
ErBpPBjWU2n2hF+rULuh1VTWoZIY12rHC3uLiRVMzTmZJWyZYsbzlN2NjdOaA/9X
NPuVM1Q8OnhbcweDwdj+RUx+kHM1y9NTvKUcIljx+DsfclYshqDn/erPG0Tcn/Dw
v8NE5Wx7DnuKekaMgKOltgGoP/x8QCugXrjD65M2+T827flS0sQ=
=qgTf
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

systemd-bootchart_233-2_amd64.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Mar 2018 23:53:27 +0200
Source: systemd-bootchart
Binary: systemd-bootchart
Architecture: source amd64
Version: 233-2
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Martin Pitt 
Description:
 systemd-bootchart - boot performance graphing tool
Closes: 882630
Changes:
 systemd-bootchart (233-2) unstable; urgency=medium
 .
   [ Michael Biebl ]
   * Update Vcs-* to point to https://salsa.debian.org
   * Set Rules-Requires-Root to no
 .
   [ Nicolas Braud-Santoni ]
   * debian/copyright: Point to CC-1.0 license in /usr/share/common-licenses/
 (Closes: #882630)
 .
   [ Martin Pitt ]
   * debian/copyright: Use https URL for Format:
   * Bump Standards-Version to 4.1.3
   * debian/copyright: Move global wildcard section to the top.
 Fixes lintian warning
 global-files-wildcard-not-first-paragraph-in-dep5-copyright.
Checksums-Sha1:
 96df85503a101b0afe7a4ba0bd457feaa423a3d3 2224 systemd-bootchart_233-2.dsc
 37748e1c6472abcf19cc6c6ba96a42b16b48f721 3976 
systemd-bootchart_233-2.debian.tar.xz
 8f236eff095456c16bb6f15afeff1cba98063514 91952 
systemd-bootchart-dbgsym_233-2_amd64.deb
 a2d2d40285bac93bff3c16d25129df981de0ad4e 6795 
systemd-bootchart_233-2_amd64.buildinfo
 640025e212cfb2f043f6cb4aa4aeff4918c95044 45276 
systemd-bootchart_233-2_amd64.deb
Checksums-Sha256:
 2426ccda61307578d882376b0566343e0fd7769b3b200fd6b31b8511fa84da1d 2224 
systemd-bootchart_233-2.dsc
 d86959f527bd0c99dc552a251acf11e3c6d9c00cf250fa34bff294e10e7f1e9f 3976 
systemd-bootchart_233-2.debian.tar.xz
 64abff7c02b55031df0a5336d0ea02e6064ce1fe71a42886c48330449ce35856 91952 
systemd-bootchart-dbgsym_233-2_amd64.deb
 0fea1105a6e2949313680387258025eed9418cbd905d233854bd919ddd0f1786 6795 
systemd-bootchart_233-2_amd64.buildinfo
 439c2b0776bd4f5d3b3b5455b79a9c26d1c60a61a674ca3c14f2c28faff00bb4 45276 
systemd-bootchart_233-2_amd64.deb
Files:
 ec95a3d4628793c21b00b18c7716a767 2224 admin optional 
systemd-bootchart_233-2.dsc
 77a5d62ce5d709a5c40296e019c253f6 3976 admin optional 
systemd-bootchart_233-2.debian.tar.xz
 a68b0d591f51abe278c1ccdbdfcc931c 91952 debug optional 
systemd-bootchart-dbgsym_233-2_amd64.deb
 59738283f29675e84ccc9f4b0d07f132 6795 admin optional 
systemd-bootchart_233-2_amd64.buildinfo
 531aea760d55147a35f96338f74a210e 45276 admin optional 
systemd-bootchart_233-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAlq4Go4ACgkQxrkYDUvY
t65SiBAAnZsXggO2fm7OXvlkWFg0phTCXkI8K5jRnbbqhW3mxagQojYzjQhQUIg9
h+qc1NSH0A/WxGLfrMU16bTBiJM4foi0bwgs483e1pR0bGvsUPbyPVU0Ml7D6Hm7
F2HEIvvhq6O9j+sd8cyeLPHoMxjPhSmcGlygGutsbLI4jVDZcjtx/R27EwX47SD1
T+gYLs5Pr1ZZsWoqGq0yHD0OPNJ9z+RQDjynouo8/vG+7Orqn4ZCd1RKKULddk7B
zoIdVsi3N8piyzX73OV5j5n4tAmAWmcriHALkNK4+T0fL+w5klfEgDhXjvt/8Ww1
sMIpJnYWDmqLL6Ey8qX/gVM3plZ2sDDBS6yDly0eCAGaq8GscN8V9XTJQlQ5Aw3l
W2jfEhhaOxgFpnQCNWFQHXomSZ4NqVmzSHV38aMeA6oOA2Ntsvx3U5S0OmQnLFyh
VUh82acU0QqlLXwz7DsKi6jJpT0xdpEvGP8VqHHUChqzx6Iba+WMYKOfhgxN5G9h
yf1PVPC92180VaU3QaZYpJ5qbo8SoKuRsuWWtKRnghal2EcS64B4H7kGKNxRDWR/
DcHEDCccosA8EvTHu/ZBO+rbvYk2dxrzIgeEgtB0Kme+iNU+tCsqz7TTEVvXhcET
4nkUctx6wXT+qSARElOUEpxoF5xVd66fk+4eiOyMBWmB4yc/FQA=
=7phi
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processing of python-systemd_234-2_amd64.changes

[Debian FTP Masters]

python-systemd_234-2_amd64.changes uploaded successfully to localhost
along with the files:
  python-systemd_234-2.dsc
  python-systemd_234-2.debian.tar.xz
  python-systemd-dbgsym_234-2_amd64.deb
  python-systemd_234-2_amd64.buildinfo
  python-systemd_234-2_amd64.deb
  python3-systemd-dbgsym_234-2_amd64.deb
  python3-systemd_234-2_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.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

Processing of systemd-bootchart_233-2_amd64.changes

[Debian FTP Masters]

systemd-bootchart_233-2_amd64.changes uploaded successfully to localhost
along with the files:
  systemd-bootchart_233-2.dsc
  systemd-bootchart_233-2.debian.tar.xz
  systemd-bootchart-dbgsym_233-2_amd64.deb
  systemd-bootchart_233-2_amd64.buildinfo
  systemd-bootchart_233-2_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.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

Bug#832566: systemd-machined breaks automounting nfs shares

[John Pearson]

Hi Michael,

If I disable libvirtd, systemd-machined isn't started.

Can't say if this problem also occurs in Stretch - this is the only 
machine with this configuration I have access to, and upgrading to 
Stretch is on hold due to other considerations; I'll see if I can create 
a similar environment to check, or failing that report back when it's 
upgraded.


Regards,


John Pearson.

On 25/03/18 07:11, Michael Biebl wrote:

On Tue, 28 Mar 2017 07:39:58 +0200 Michael Biebl  wrote:

Am 27.10.2016 um 23:13 schrieb John Pearson:

Hello Michael,

Thanks for looking at this.

On 22/10/16 11:07, Michael Biebl wrote:

Am 27.07.2016 um 02:59 schrieb John Pearson:

Hello Michael,

After the problem first occurred I reviewed bug #767468 and purged both
cgmanager and sytemd-shim, but the problem remained.  And, of course,
/proc shows systemd-machined (and only systemd-machined) still "thought"
/nfs/home was mounted.

Why is systemd-machined running? Do you have any systemd-nspawn
containers running where /home is symlinked or bind-mounted?

I have no idea - it was installed as part of the systemd package, and
starts automatically at boot.  The machine runs a single KVM instance
hosting Windows 7, managed by libvirtd.


If you stop systemd-machined, is the problem gone?

That seems to fix it without any obvious drawbacks, but I assume I'd
have to do the same after each reboot.


Is machined started by libvirtd then? What if you systemctl disable
libvirtd.service, does systemd-machined.service still start?

Can you reproduce the problem with stretch, i.e. with systemd v232?

Is this still reproducible with stretch?



--
*email:*j...@huiac.com  
"The greatest shortcoming of the human race
is our inability to understand
the exponential function."
- Albert Allen Bartlett
*web:*  http://www.huiac.com/
*mob:*  +61 407 391 169
*phone:*+61 8 7127 6275

___
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#783618: marked as done (systemd: journald ignores MaxLevelKMsg=warning)

[Debian Bug Tracking System]

Your message dated Sat, 24 Mar 2018 22:36:10 +0100
with message-id <6dfcea2f-7b74-aa9a-e8d3-1a06149a8...@debian.org>
and subject line Re: systemd: journald ignores MaxLevelKMsg=warning
has caused the Debian Bug report #783618,
regarding systemd: journald ignores MaxLevelKMsg=warning
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.)


-- 
783618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-17
Severity: normal

Dear Maintainer,

   * After noticing that journald fills dmesg with irrelevant messages
 such as:
> syslog:info  : [2730378.422878] systemd-journald[4060]: Deleted empty journal 
> /var/log/journal/c2544241fd44405fba80ed9cf7fe0f29/user-31146@c21ba3b937144879a1feba0ae91775ae--.journal
>  (8388608 bytes).
   * I read the documentation and tried to suppress those messages
 (since they are loglevel info) by adding MaxLevelKMsg=warning to
 journald.conf 
   * I would have expected said messages to be no longer logged to
 dmesg/kmsg.
   * Yet those messages still appear in dmesg.

-- Package-specific info:

-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.9-cip-amd64 (SMP w/16 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-17
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.16-1
ii  libpam-systemd  215-17

Versions of packages systemd suggests:
pn  systemd-ui  

-- Configuration Files:
/etc/pam.d/systemd-user changed:
@include cip-login

/etc/systemd/journald.conf changed:
[Journal]
Storage=persistent
SystemMaxUse=200M
MaxRetentionSec=1week
MaxLevelKMsg=warning

/etc/systemd/logind.conf changed:
[Login]
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore


-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 16 Dec 2016 06:06:29 +0100 Michael Biebl  wrote:
> Control: tags -1 + moreinfo
> 
> On Tue, 28 Apr 2015 14:36:26 +0200 Alexander Wuerstlein
>  wrote:
> > Package: systemd
> > Version: 215-17
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> >* After noticing that journald fills dmesg with irrelevant messages
> >  such as:
> > > syslog:info  : [2730378.422878] systemd-journald[4060]: Deleted empty 
> > > journal 
> > > /var/log/journal/c2544241fd44405fba80ed9cf7fe0f29/user-31146@c21ba3b937144879a1feba0ae91775ae--.journal
> > >  (8388608 bytes).
> >* I read the documentation and tried to suppress those messages
> >  (since they are loglevel info) by adding MaxLevelKMsg=warning to
> >  journald.conf 
> >* I would have expected said messages to be no longer logged to
> >  dmesg/kmsg.
> >* Yet those messages still appear in dmesg.
> 
> I think this is fixed in newer systemd versions.
> 
> Can you please try to reproduce the problem with systemd v232 from
> unstable/stretch.

Closing, ttbomk this is fixed in recent versions and no feedback was
provided which would indicate the contrary.

Regards,
Michael

-- 
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
--- End Message ---
___
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#799922: marked as done (systemd-machined: error: error from service: CreateMachine: Activation of org.freedesktop.machine1 timed out)

[Debian Bug Tracking System]

Your message dated Sat, 24 Mar 2018 22:44:21 +0100
with message-id <3a7169f2-aa23-2f81-0733-e2437bc4f...@debian.org>
and subject line Re: systemd-machined: error: error from service: 
CreateMachine: Activation of org.freedesktop.machine1 timed out
has caused the Debian Bug report #799922,
regarding systemd-machined: error: error from service: CreateMachine: 
Activation of org.freedesktop.machine1 timed out
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.)


-- 
799922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-17+deb8u2
Severity: normal
File: systemd-machined

Dear Maintainer,

when trying to re-start a guest machine (doing virsh shutdown to use
new library files in the qemu process), startup via
"virsh start " failed:

error: Failed to start domain 
error: error from service: CreateMachine: Activation of 
org.freedesktop.machine1 timed out


The host in question is up for around 40 days. It seems as if libvirt
needs some dbus connection and systemd-machined for guest
startup. Restarting systemd-machined via "service systemd-machined
restart" cleared the situation.

So obviously, some sort of communication between systemd and dbus was
lost unnoticed - maybe by recent library upgrades and daemon restarts
by needrestart? Maybe some restart dependency is broken?


Yours sincerely
Matthias Merz

-- Package-specific info:

-- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/48 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18+deb8u1
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-17+deb8u2
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17+deb8u2
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.20-0+deb8u1
ii  libpam-systemd  215-17+deb8u2

Versions of packages systemd suggests:
pn  systemd-ui  

-- Configuration Files:
/etc/systemd/system.conf changed:
[Manager]
ShowStatus=yes


-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 2 Jun 2017 03:01:22 +0200 Michael Biebl  wrote:
> Control: tags -1 + moreinfo
> 
> Hi Matthias
> 
> On Thu, 24 Sep 2015 11:11:23 +0200 Matthias Merz  wrote:
> > Package: systemd
> > Version: 215-17+deb8u2
> > Severity: normal
> > File: systemd-machined
> > 
> > Dear Maintainer,
> > 
> > when trying to re-start a guest machine (doing virsh shutdown to use
> > new library files in the qemu process), startup via
> > "virsh start " failed:
> > 
> > error: Failed to start domain 
> > error: error from service: CreateMachine: Activation of 
> > org.freedesktop.machine1 timed out
> > 
> > 
> > The host in question is up for around 40 days. It seems as if libvirt
> > needs some dbus connection and systemd-machined for guest
> > startup. Restarting systemd-machined via "service systemd-machined
> > restart" cleared the situation.
> > 
> > So obviously, some sort of communication between systemd and dbus was
> > lost unnoticed - maybe by recent library upgrades and daemon restarts
> > by needrestart? Maybe some restart dependency is broken?
> 
> Sorry for not getting back to you earlier.
> Is this still a problem you can reproduce? If so, I'd send you further
> instructions how to debug this.

I revisited this old bug report and with the given information I was
unable to reproduce the issue. So I'm going to close it.

Please report back, if you still run into this issue with an up-to-date
stretch system. We can then reopen the bug report.

Regards,
Michael

-- 
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
--- End Message ---
___
Pkg-systemd-maintainers mailing list

Bug#893574: marked as done (gnome-shell: Suspend after 20 minutes even there is activity on a seat)

[Debian Bug Tracking System]

Your message dated Sat, 24 Mar 2018 21:39:19 +
with message-id <20180324213900.ga29...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if 
there is activity on a seat
has caused the Debian Bug report #893574,
regarding gnome-shell: Suspend after 20 minutes even there is activity on a seat
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.)


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

Dear Maintainer,

Since version 3.27.90 the default action is to suspend after 20 minutes of
inactivity. Unfortunately, the system also suspend when there is activity on a
seat while the other is idle.

   * What led up to the situation?

create a multiseat setup with the "loginctl attach seat1" command

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Leave seat1 on the gdm3 login screen and go away.
Login on seat0 and play.

   * What was the outcome of this action?

The system go to sleep after 20 minutes

   * What outcome did you expect instead?

The system stays awake

When both seats are active the system doesn't go to sleep.

journalctl
mrt 20 00:42:21 Jessica gnome-shell[1403]: Screen lock is locked down, not
locking
mrt 20 00:42:21 Jessica kernel: PM: suspend entry (deep)
mrt 20 00:42:21 Jessica gnome-shell[3700]: Screen lock is locked down, not
locking
mrt 20 00:42:21 Jessica NetworkManager[896]:   [1521502941.3440] manager:
sleep: sleep requested (sleeping: no  enabled: yes)
mrt 20 00:42:21 Jessica NetworkManager[896]:   [1521502941.3440] manager:
NetworkManager state is now ASLEEP
mrt 20 00:42:21 Jessica systemd[1]: Reached target Sleep.
mrt 20 00:42:21 Jessica systemd[1]: Starting Suspend...
mrt 20 00:42:21 Jessica systemd-sleep[6914]: Suspending system...

See also Gnome bug 681869 https://bugzilla.gnome.org/show_bug.cgi?id=681869



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=nl_NL.utf8, LC_CTYPE=nl_NL.utf8 (charmap=UTF-8), 
LANGUAGE=nl_NL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.1-3
ii  evolution-data-server3.26.5-2
ii  gir1.2-accountsservice-1.0   0.6.45-1
ii  gir1.2-atspi-2.0 2.28.0-1
ii  gir1.2-freedesktop   1.56.0-1
ii  gir1.2-gcr-3 3.28.0-1
ii  gir1.2-gdesktopenums-3.0 3.28.0-1
ii  gir1.2-gdm-1.0   3.28.0-1
ii  gir1.2-geoclue-2.0   2.4.7-1
ii  gir1.2-glib-2.0  1.56.0-1
ii  gir1.2-gnomebluetooth-1.03.28.0-2
ii  gir1.2-gnomedesktop-3.0  3.28.0-1
ii  gir1.2-gtk-3.0   3.22.29-1
ii  gir1.2-gweather-3.0  3.28.0-2
ii  gir1.2-ibus-1.0  1.5.17-3
ii  gir1.2-mutter-2  3.28.0-2
ii  gir1.2-nm-1.01.10.6-2
ii  gir1.2-nma-1.0   1.8.10-2
ii  gir1.2-pango-1.0 1.40.14-1
ii  gir1.2-polkit-1.00.105-18
ii  gir1.2-rsvg-2.0  2.40.20-2
ii  gir1.2-soup-2.4  2.62.0-1
ii  gir1.2-upowerglib-1.00.99.7-2
ii  gjs  1.52.0-1
ii  gnome-backgrounds3.28.0-1
ii  gnome-settings-daemon3.28.0-1
ii  gnome-shell-common   3.28.0-1
ii  gsettings-desktop-schemas3.28.0-1
ii  libatk-bridge2.0-0   2.26.2-1
ii  libatk1.0-0  2.28.1-1
ii  libc62.27-2
ii  libcairo21.15.10-2
ii  libcanberra-gtk3-0   0.30-6
ii  libcanberra0 0.30-6
ii  libcroco30.6.12-2
ii  libecal-1.2-19   3.26.5-2
ii  

Bug#779612: marked as done (systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable)

[Debian Bug Tracking System]

Your message dated Sat, 24 Mar 2018 22:51:51 +0100
with message-id <16dfe332-607b-d6f7-165e-0d2b630aa...@debian.org>
and subject line Re: Bug#764555: systemd: cryptsetup password 
overwritten/hidden by status messages
has caused the Debian Bug report #764555,
regarding systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend 
plymouth; without plymouth cryptsetup prompts are unusable
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.)


-- 
764555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-sysv,cryptsetup
Severity: important

Dear Maintainer,

Booting in jessie is currently nearly impossible with multiple cryptsetup
volumes which are mounted at boot time.  systemd spews messages over the
prompt and there's a 90-second timeout while typing blind.  Please see
the bug report[1] and discussion on debian-qa[2].

The bug appears to be "fixed" by installing plymouth, so it's proposed that
systemd-sysv and cryptsetup should at least recommend plymouth.

This is a major usability problem for users with multiple required
cryptsetup volumes, e.g. on /var and /usr.  I do not believe jessie should
ship as "stable" with it unresolved.

1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768314 
2. https://lists.debian.org/debian-qa/2015/02/msg00051.html

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Wed, 08 Oct 2014 18:39:11 -0700 Nikolaus Rath  wrote:
> On 10/08/2014 06:17 PM, Michael Biebl wrote:
> > Am 09.10.2014 um 02:51 schrieb Nikolaus Rath:
> >> On 10/08/2014 05:47 PM, Michael Biebl wrote:
> >>> Am 09.10.2014 um 02:43 schrieb Nikolaus Rath:
>  Package: systemd
>  Version: 215-5+b1
>  Severity: normal
> 
>  Hello,
> 
>  I'm running Debian testing. After the last dist-upgrade, systemd has
>  started showing status messages during boot (sort of like sysvinit used
>  to do). This is certainly much prettier and more informative than the 
>  blank screen that I had before, but it has the unfortunate side-effect
>  of interfering with the cryptsetup password prompt. Sometimes the prompt
>  is several lines before the cursor with other messsages in between, and 
>  sometimes it's actually overwritten completely.
> 
>  It'd be nice if status output would be suppressed/delayed while a
>  password prompty is active.
> >>>
> >>> You'll need something like plymouth to multiplex the input/output.
> >>>
> >>> http://web.dodds.net/~vorlon/wiki/blog/Plymouth_is_not_a_bootsplash/
> >>
> >> In that case it'd be great if the systemd or the cryptsetup package
> >> could recommend or suggest the appropriate package (plymouth?).
> > 
> > Could you verify that plymouth solves your problem?
> 
> Yes it did. Thank you!
> 

I think systemd handles this case more gracefully nowadays, so having
plymouth installed is no longer a necessity. I'm thus closing this bug
report.
A Recommends in systemd wouldn't actually help in any case, as systemd
is installed during the initial bootstrap phase, where recommends are
not considered and a hard Depends doesn't seem warranted.

If we wanted to install plymouth by default, we should use another
mechanism then having systemd recommend it.

Regards,
Michael

-- 
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
--- End Message ---
___
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#764555: marked as done (Please add Recommends: plymouth)

[Debian Bug Tracking System]

Your message dated Sat, 24 Mar 2018 22:51:51 +0100
with message-id <16dfe332-607b-d6f7-165e-0d2b630aa...@debian.org>
and subject line Re: Bug#764555: systemd: cryptsetup password 
overwritten/hidden by status messages
has caused the Debian Bug report #764555,
regarding Please add Recommends: plymouth
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.)


-- 
764555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764555
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-5+b1
Severity: normal

Hello,

I'm running Debian testing. After the last dist-upgrade, systemd has
started showing status messages during boot (sort of like sysvinit used
to do). This is certainly much prettier and more informative than the 
blank screen that I had before, but it has the unfortunate side-effect
of interfering with the cryptsetup password prompt. Sometimes the prompt
is several lines before the cursor with other messsages in between, and 
sometimes it's actually overwritten completely.

It'd be nice if status output would be suppressed/delayed while a
password prompty is active.


-- Package-specific info:

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-53.4
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1
ii  libblkid1   2.20.1-5.11
ii  libc6   2.19-11
ii  libcap2 1:2.24-6
ii  libcap2-bin 1:2.24-6
ii  libcryptsetup4  2:1.6.6-1
ii  libgcrypt20 1.6.2-3
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-5+b1
ii  sysv-rc 2.88dsf-53.4
ii  udev215-5+b1
ii  util-linux  2.20.1-5.11

Versions of packages systemd recommends:
ii  dbus1.8.8-1+b1
ii  libpam-systemd  215-5+b1

Versions of packages systemd suggests:
pn  systemd-ui  

-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 08 Oct 2014 18:39:11 -0700 Nikolaus Rath  wrote:
> On 10/08/2014 06:17 PM, Michael Biebl wrote:
> > Am 09.10.2014 um 02:51 schrieb Nikolaus Rath:
> >> On 10/08/2014 05:47 PM, Michael Biebl wrote:
> >>> Am 09.10.2014 um 02:43 schrieb Nikolaus Rath:
>  Package: systemd
>  Version: 215-5+b1
>  Severity: normal
> 
>  Hello,
> 
>  I'm running Debian testing. After the last dist-upgrade, systemd has
>  started showing status messages during boot (sort of like sysvinit used
>  to do). This is certainly much prettier and more informative than the 
>  blank screen that I had before, but it has the unfortunate side-effect
>  of interfering with the cryptsetup password prompt. Sometimes the prompt
>  is several lines before the cursor with other messsages in between, and 
>  sometimes it's actually overwritten completely.
> 
>  It'd be nice if status output would be suppressed/delayed while a
>  password prompty is active.
> >>>
> >>> You'll need something like plymouth to multiplex the input/output.
> >>>
> >>> http://web.dodds.net/~vorlon/wiki/blog/Plymouth_is_not_a_bootsplash/
> >>
> >> In that case it'd be great if the systemd or the cryptsetup package
> >> could recommend or suggest the appropriate package (plymouth?).
> > 
> > Could you verify that plymouth solves your problem?
> 
> Yes it did. Thank you!
> 

I think systemd handles this case more gracefully nowadays, so having
plymouth installed is no longer a necessity. I'm thus closing this bug
report.
A Recommends in systemd wouldn't actually help in any case, as systemd
is installed during the initial bootstrap phase, where recommends are
not considered and a hard Depends doesn't seem warranted.

If we wanted to install plymouth by default, we should use another
mechanism then having systemd recommend it.

Regards,
Michael

-- 
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
--- End Message ---
___
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: found 793198 in 215-17+deb8u1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 793198 215-17+deb8u1
Bug #793198 [src:systemd] systemd: poweroff, reboot without stopping services 
and unmounting
Marked as found in versions systemd/215-17+deb8u1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
793198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793198
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

Processed: Re: Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #893054 [systemd] systemd: System failed to boot after upgrade/install 
systemd from systemd:i386
Added tag(s) moreinfo.

-- 
893054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893054
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#810247: RE: Bug#810247: Hyper-V network adapters are mapped to a different interface (ethN) on every boot

[Michael Biebl]

On Sat, 9 Jan 2016 17:20:26 + Fernando Soto
 wrote:
> Hi Martin,
> 
> Udevadm output is attached.
> 
> Thank you,
> Fernando
> 
> > -Original Message-
> > From: Martin Pitt [mailto:mp...@debian.org]
> > Sent: Saturday, January 09, 2016 10:45 AM
> > To: Fernando Soto; 810...@bugs.debian.org
> > Subject: Re: Bug#810247: Hyper-V network adapters are mapped to a different
> > interface (ethN) on every boot
> > 
> > Control: tag -1 moreinfo
> > 
> > Fernando Soto [2016-01-08 15:22 +]:
> > > The persistent-net udev rules are not created in virtual environments to 
> > > avoid
> > issues with cloning/migrating VMs.
> > 
> > This was true with the old persistent names in Jessie and before, but not 
> > true any
> > more with current testing and unstable versions. See
> > /usr/share/doc/udev/README.Debian.gz.
> > 
> > Maybe the current ifnames system cannot figure out an appropriate name for
> > Hyper-V interfaces? 


P:
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_0_16/net/eth0
E:
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/vmbus_0_16/net/eth0
E: ID_NET_DRIVER=hv_netvsc
E: ID_NET_NAME_MAC=enx00155d0ae2ad
E: ID_OUI_FROM_DATABASE=Microsoft Corporation
E: ID_PATH=acpi-VMBUS:01
E: ID_PATH_TAG=acpi-VMBUS_01
E: IFINDEX=2
E: INTERFACE=eth0
E: MATCHDEVID=0x0
E: MATCHIFTYPE=1
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0
E: TAGS=:systemd:
E: USEC_INITIALIZED=39002

Looks like this is the case.
I notice that there is

Author: Hannes Reinecke 
Date:   Fri Nov 23 14:12:39 2012 +0100

udev: path_id - handle Hyper-V devices

Hyper-V has an abstract bus, which gets renumbered on guest
startup. So instead of the bus numbers we should be using
the device GUIDs, which can be retrieved from the 'device_id'
sysfs attribute.


That doesn't seem to handle network interfaces though.

That said, this doesn't look like a Debian specific problem. So it's
probably best if you raise this upstream at
https://github.com/systemd/systemd

-- 
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#775613: marked as done (systemd: why is /run/systemd/inhibit/1.ref inherited?)

[Debian Bug Tracking System]

Your message dated Sat, 24 Mar 2018 22:33:17 +0100
with message-id <61e51f6f-157c-63e1-b20a-bea2884ad...@debian.org>
and subject line Re: systemd: why is /run/systemd/inhibit/1.ref inherited?
has caused the Debian Bug report #775613,
regarding systemd: why is /run/systemd/inhibit/1.ref inherited?
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.)


-- 
775613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-9
Severity: normal


type=AVC msg=audit(1421538903.417:232): avc:  denied  { use } for  pid=23546 
comm="kded4" path="/run/systemd/inhibit/1.ref" dev="tmpfs" ino=91124 
scontext=rjc:user_r:user_t:s0-s0:c0.c1023 
tcontext=system_u:system_r:systemd_logind_t:s0 tclass=fd permissive=0

When I login via kdm the KDE user processes (and presumably user processes
from any other desktop environment) inherit /run/systemd/inhibit/1.ref.

Is this desired?  If so why?  I have SE Linux preventing it and everything
works.

-- Package-specific info:

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-58
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-4
ii  libc6   2.19-13
ii  libcap2 1:2.24-6
ii  libcap2-bin 1:2.24-6
ii  libcryptsetup4  2:1.6.6-4
ii  libgcrypt20 1.6.2-4+b1
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-9
ii  mount   2.25.2-4
ii  sysv-rc 2.88dsf-58
ii  udev215-9
ii  util-linux  2.25.2-4

Versions of packages systemd recommends:
ii  dbus1.8.14-1
ii  libpam-systemd  215-9

Versions of packages systemd suggests:
pn  systemd-ui  

-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
SystemMaxUse=25M


-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, 1 Oct 2015 15:59:52 +1000 Russell Coker 
wrote:
> On Thu, 1 Oct 2015 08:00:45 AM Michael Biebl wrote:
> > On Sun, 18 Jan 2015 11:07:40 +1100 Russell Coker 
> > wrote:
> > > Package: systemd
> > > Version: 215-9
> > > Severity: normal
> > > 
> > > 
> > > type=AVC msg=audit(1421538903.417:232): avc:  denied  { use } for 
> > > pid=23546 comm="kded4" path="/run/systemd/inhibit/1.ref" dev="tmpfs"
> > > ino=91124 scontext=rjc:user_r:user_t:s0-s0:c0.c1023
> > > tcontext=system_u:system_r:systemd_logind_t:s0 tclass=fd permissive=0
> > > 
> > > When I login via kdm the KDE user processes (and presumably user
> > > processes from any other desktop environment) inherit
> > > /run/systemd/inhibit/1.ref.
> > > 
> > > Is this desired?  If so why?  I have SE Linux preventing it and
> > > everything works.
> > 
> > I'm not sure what the problem is here.
> > Can you elaborate?
> 
> If a socket or pipe is inherited from a system process to a process running 
> as 
> a user there is a possibility of a security problem.  Generally if there is 
> no 
> reason for such access to be granted then it should not be granted.  The file 
> handle could be closed before exec or it could be set to close on exec.

Please raise this issue upstream at
https://github.com/systemd/systemd/issues if it still persists in stretch.

Regards,
Michael

-- 
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
--- End Message ---
___
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#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

[Michael Biebl]

Control: tags -1 + moreinfo
On Mon, 19 Mar 2018 09:46:04 -0600 Jeff Ketchum  wrote:
> Second issue, I have trouble getting my system to boot reliably after the
> changes.
> It is using systemd:amd64

Ok, so what exactly is the failure then? Please describe it in more
detail. Maybe also provide a complete, verbose boot log [1].


Regards,
Michael
https://freedesktop.org/wiki/Software/systemd/Debugging/
[1]
-- 
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#876103: marked as done (systemd-nspawn: --read-only is broken)

[Debian Bug Tracking System]

Your message dated Sat, 24 Mar 2018 21:47:51 +0100
with message-id <5a21ca04-4b83-62a0-86d0-eb3c7b55e...@debian.org>
and subject line Re: Bug#876103: systemd-nspawn: --read-only is broken
has caused the Debian Bug report #876103,
regarding systemd-nspawn: --read-only is broken
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.)


-- 
876103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-container
Version: 232-25+deb9u1
Severity: normal

Dear Maintainer,

on stretch, 'systemd-nspawn --read-only' fails to start the container
entirely. Trivial test case:

# machinectl pull-tar 
https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-root.tar.gz
[ output omitted ]
# systemd-nspawn -M xenial-server-cloudimg-amd64-root -- true
# systemd-nspawn -M xenial-server-cloudimg-amd64-root --read-only -- true
Spawning container xenial-server-cloudimg-amd64-root on 
/var/lib/machines/xenial-server-cloudimg-amd64-root.
Press ^] three times within 1s to kill container.
Failed to create directory 
/var/lib/machines/xenial-server-cloudimg-amd64-root/sys: Read-only file system

(the first systemd-nspawn call is there to implicitly create some
directories inside the container root that must exist for read-only to
work)

The expected behavior is that 'true' is executed in container and exit
status 0 is returned; however, the container is not started and the exit
status is 1.

There is an upstream fix for this in
https://github.com/systemd/systemd/pull/4693 --
acbbf69b718260755a5dff60dd68ba239ac0d61b is the commit that actually
fixes read-only containers, but it requires two other commits to apply
cleanly. I applied the following sequence to systemd-container on
stretch:

https://github.com/systemd/systemd/commit/bdb4e0cb646ff33ecbb1cf4b502870f84bf4016d
https://github.com/systemd/systemd/commit/4f086aab52812472a24c9b8b627589880a38696e
https://github.com/systemd/systemd/commit/acbbf69b718260755a5dff60dd68ba239ac0d61b

and it solved my problem. Could you backport these patches to stretch?

-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-container depends on:
ii  dbus 1.10.18-1
ii  libacl1  2.2.52-3+b1
ii  libblkid12.29.2-1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.24-11+deb9u1
ii  libcurl3-gnutls  7.52.1-5
ii  libgcrypt20  1.7.6-2+deb9u2
ii  libip4tc01.6.0+snapshot20161117-6
ii  liblzma5 5.2.2-1.2+b1
ii  libseccomp2  2.3.1-2.1
ii  libselinux1  2.6-3+b1
ii  systemd  232-25+deb9u1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages systemd-container recommends:
ii  btrfs-progs4.7.3-1
ii  libnss-mymachines  232-25+deb9u1

systemd-container suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Lauri,

On Mon, 4 Dec 2017 09:29:17 +0200 Lauri Tirkkonen  wrote:
> Hi,
> 
> On Sun, Dec 03 2017 13:47:29 +0100, Michael Biebl wrote:
> > > There is an upstream fix for this in
> > > https://github.com/systemd/systemd/pull/4693 --
> > > acbbf69b718260755a5dff60dd68ba239ac0d61b is the commit that actually
> > > fixes read-only containers, but it requires two other commits to apply
> > > cleanly. I applied the following sequence to systemd-container on
> > > stretch:
> > > 
> > > https://github.com/systemd/systemd/commit/bdb4e0cb646ff33ecbb1cf4b502870f84bf4016d
> > > https://github.com/systemd/systemd/commit/4f086aab52812472a24c9b8b627589880a38696e
> > > https://github.com/systemd/systemd/commit/acbbf69b718260755a5dff60dd68ba239ac0d61b
> > > 
> > > and it solved my problem. Could you backport these patches to stretch?
> > > 
> > 
> > Those patches looks a bit invasive for a stretch stable upload.
> > But we do provide updated systemd versions with this fix via
> > stretch-backports:
> > https://packages.debian.org/source/stable-backports/systemd
> > 
> > Would that be sufficient for your case?
> 
> It turned out that we needed a couple other patches for
> systemd-container, including one yet to be released, so for our case
> it's sufficient to do nothing since we now use our own systemd-container
> package :)
> 
> 

Processed: Re: Bug#893574: gnome-shell: Suspends after 20 minutes even if there is activity on a seat

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd 238-2
Bug #893574 [gnome-shell] gnome-shell: Suspend after 20 minutes even there is 
activity on a seat
Bug reassigned from package 'gnome-shell' to 'systemd'.
No longer marked as found in versions gnome-shell/3.28.0-1.
Ignoring request to alter fixed versions of bug #893574 to the same values 
previously set
Bug #893574 [systemd] gnome-shell: Suspend after 20 minutes even there is 
activity on a seat
Marked as found in versions systemd/238-2.

-- 
893574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893574
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#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[johnw]

Hi Michael,

Michael Biebl 於 2018-03-23 23:31 寫到:


Does it work if you switch to a different display manager, like say
lightdm (which IIRC is the preferred one of xfce). Might be a problem
specific to slim, since I don't see any such issues myself here (using
GNOME/gdm).


No, I tried lightdm lxdm, they have same problem,
I tried gdm3, but can not login, do not why, the screen just become to 
blank/black.


Any idea, how to debug?

Thanks.

--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC



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#822635: udev rules for USB device access effective at boot, but not on hotplug

[Josh Triplett]

On Fri, Mar 23, 2018 at 05:17:11PM +0100, Michael Biebl wrote:
> On Mon, 22 Jan 2018 18:10:58 +0100 Michael Biebl 
> wrote:
> > Hi Josh!
> > 
> > On Wed, 21 Dec 2016 20:15:12 +0100 Michael Biebl  wrote:
> > > On Fri, 6 May 2016 18:12:27 -0500 Martin Pitt  wrote:
> > > > Control: tag -1 moreinfo
> > > > 
> > > > Hello Josh,
> > > > 
> > > > Josh Triplett [2016-04-25 13:48 -0700]:
> > > > > ~$ cat /etc/udev/rules.d/99-local-gnubby.rules
> > > > > SUBSYSTEMS=="usb", ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0200", 
> > > > > TAG+="uaccess"
> > > > >
> > > > > If I boot with the device attached, this seems to take effect:
> > > > >
> > > > > However, if I unplug and replug the device, this rule no longer seems 
> > > > > to take
> > > > > effect:
> > > > 
> > > > The uaccess tag is evaluated in /lib/udev/rules.d/73-seat-late.rules,
> > > > thus 99-* is too late. Can you please move it to e. g.
> > > > 70-gnubby.rules? I'm fairly sure it will work then, but I'll keep the
> > > > bug open until you confirm, just in case.
> > > > 
> > > 
> > > The dump from Josh shows, that the uaccess udev property is properly
> > > set. So I don't think it's an udev rules ordering issue.
> > > 
> > > I think the problem rather is, that you are already logged in and the
> > > ACLs are only applied on login or when the session becomes active.
> > > 
> > > I assume if you log out and re-login after the hotplug, the ACL is
> > > properly applied?
> > 
> > Any updates on this bug report? Is there still something which needs to
> > be addressed on the systemd side? If so we need to further investigate
> > the issue.
> 
> Josh, any updates on this?

I'm not currently using the device, so I don't know the status of this
issue.

Regarding the mention of when the ACLs are applied, though, is that true
in general? I thought that if you hotplugged a device that the user is
supposed to have access to, they'd immediately get access to it.

___
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#875557: Info received (Bug#875557: systemd: service mark as enabled but not in reality)

[Michael Biebl]

hm, the email address bounces here:

>
>The mail system
>
> : host mx.cblue.be[193.104.37.23] said: 550 Unrouteable
> address (in reply to RCPT TO command)
>
>
>
> Reporting-MTA: dns; dd17218.kasserver.com
> X-Postfix-Queue-ID: A90216801856
> X-Postfix-Sender: rfc822; bi...@debian.org
> Arrival-Date: Fri, 23 Mar 2018 17:12:34 +0100 (CET)
>
> Final-Recipient: rfc822; sth...@cblue.be
> Original-Recipient: rfc822;sth...@cblue.be
> Action: failed
> Status: 5.0.0
> Remote-MTA: dns; mx.cblue.be
> Diagnostic-Code: smtp; 550 Unrouteable address
>


-- 
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#831414: marked as done (systemd: learns IPv6 prefix from its own RAs and configures IP address on wrong interface)

[Debian Bug Tracking System]

Your message dated Fri, 23 Mar 2018 17:24:02 +0100
with message-id 
and subject line Re: Bug#831414: systemd: learns IPv6 prefix from its own RAs 
and configures IP address on wrong interface
has caused the Debian Bug report #831414,
regarding systemd: learns IPv6 prefix from its own RAs and configures IP 
address on wrong interface
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.)


-- 
831414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 230-5pitti1
Severity: minor
Tags: ipv6

Hi,

I am filing this as severity minor because this bug is in a version
that is not officially in Debian. I am filing it nevertheless because
systemd with this IPv6 user space code active should not be in Debian.
If this were an official version, this would be an important bug, with
the potential for "serious" at maintainer discretion.

While following up Martin's requests for #815793 and #815884, I have
found new misbehsvior regarding IPv6.

Given a host that also acts as a router, with the following network
setup:

2: eth0:  mtu 1500 qdisc pfifo_fast state UP 
link/ether 54:04:a6:82:21:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.182.250/32 brd 192.168.182.250 scope global eth0
   valid_lft forever preferred_lft forever
inet 192.168.182.29/24 brd 192.168.182.255 scope global dynamic eth0
   valid_lft 12650sec preferred_lft 12650sec
inet6 2001:db8:0:3282:5604:a6ff:fe82:2100/64 scope global mngtmpaddr 
noprefixroute dynamic
   valid_lft 86309sec preferred_lft 14309sec
inet6 2001:db8:0:3282::1d:250/128 scope global
   valid_lft forever preferred_lft forever
inet6 2001:db8:0:3282::1d:100/64 scope global
   valid_lft forever preferred_lft forever
inet6 fe80::5604:a6ff:fe82:2100/64 scope link
   valid_lft forever preferred_lft forever
3: br0:  mtu 1500 qdisc noqueue state UP group 
default qlen 1000
link/ether c6:f4:98:dc:5e:21 brd ff:ff:ff:ff:ff:ff
inet 192.168.29.254/24 brd 192.168.29.255 scope global br0
   valid_lft forever preferred_lft forever
inet6 2001:db8:0:328d::1d:153/64 scope global
   valid_lft forever preferred_lft forever
inet6 2001:db8:0:328d::1d:100/64 scope global
   valid_lft forever preferred_lft forever
inet6 fec0:0:0:::3/128 scope site
   valid_lft forever preferred_lft forever
inet6 fec0:0:0:::2/128 scope site
   valid_lft forever preferred_lft forever
inet6 fec0:0:0:::1/128 scope site
   valid_lft forever preferred_lft forever
inet6 fe80::c4f4:98ff:fedc:5e21/64 scope link
   valid_lft forever preferred_lft forever

On br0, there is a radvd, advertising a prefix on br0:
interface br0 {
AdvSendAdvert on;
MinRtrAdvInterval 600;
MaxRtrAdvInterval 1200;
prefix 2001:db8:0:328d::/64 {
DeprecatePrefix on;
};
RDNSS 2001:db8:0:328d::1d:153 {
AdvRDNSSLifetime 1200;
};
};

When the radvd is started, the local host seems to learn the prefix
from the locally running radvd and _configures_ _it_ _on_ _eth0_,
which is plain wrong:

2: eth0:  mtu 1500 qdisc pfifo_fast state UP gr
oup default qlen 1000
link/ether 54:04:a6:82:21:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.182.250/32 brd 192.168.182.250 scope global eth0
   valid_lft forever preferred_lft forever
inet 192.168.182.29/24 brd 192.168.182.255 scope global dynamic eth0
   valid_lft 12530sec preferred_lft 12530sec
inet6 2001:db8:0:328d:5604:a6ff:fe82:2100/64 scope global mngtmpaddr 
noprefixroute dynamic
   valid_lft 86390sec preferred_lft 14390sec
inet6 2001:db8:0:3282:5604:a6ff:fe82:2100/64 scope global mngtmpaddr 
noprefixroute dynamic
   valid_lft 86189sec preferred_lft 14189sec
inet6 2001:db8:0:3282::1d:250/128 scope global
   valid_lft forever preferred_lft forever
inet6 2001:db8:0:3282::1d:100/64 scope global
   valid_lft forever preferred_lft forever
inet6 fe80::5604:a6ff:fe82:2100/64 scope link
   valid_lft forever preferred_lft forever

It also learns a default route pointing to its own link local IP
address on br0:

[2/502]mh@fan:~$ ip -6 r
2001:db8:0:3282::1d:250 dev eth0  proto kernel  metric 256  pref medium
2001:db8:0:3282::/64 dev eth0  proto kernel  metric 256  pref medium
2001:db8:0:3282::/64 dev eth0  proto ra  metric 1024  pref medium
2001:db8:0:328d::/64 dev br0  proto kernel  metric 256  pref 

Bug#875557: systemd: service mark as enabled but not in reality

[Michael Biebl]

Control: tags -1 + moreinfo

On Tue, 12 Sep 2017 10:08:49 +0200 Michael Biebl  wrote:
> Am 12.09.2017 um 09:45 schrieb sthiry:
> > Package: systemd
> > Version: 232-25+deb9u1
> > Severity: normal
> > 
> > Hello,
> > 
> > I use multiple php-fpm process to run apache websites and I have to create 
> > one process by site, so I have a service file named php7-fpm@.service. It 
> > let me create service like this php7-fpm@mysite that 
> > I have to enable once it is created. So I notice that when I enable one 
> > service, the others are mark as enabled when I type "service php7-fpm* 
> > status", but they are not enabled. So you have to enable all
> > services.
> 
> Can you please include the full service file you are using and the
> output of the commands.

Would be great, if you can provide the requested information.


-- 
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

Processed: bug 868159 is forwarded to https://github.com/systemd/systemd/issues/8566

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 868159 https://github.com/systemd/systemd/issues/8566
Bug #868159 [systemd] systemd-setup-tmpfiles startup error when /srv is on 
read-only fs
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/8566'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
868159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868159
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

Processed: Re: Bug#875557: systemd: service mark as enabled but not in reality

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #875557 [systemd] systemd: service mark as enabled but not in reality
Added tag(s) moreinfo.

-- 
875557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875557
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#863710: marked as done (journald's most recent entries)

[Debian Bug Tracking System]

Your message dated Fri, 23 Mar 2018 17:03:19 +0100
with message-id <917a9097-0c17-577d-d435-f4154b9fc...@debian.org>
and subject line Re: Bug#863710: journald's most recent entries
has caused the Debian Bug report #863710,
regarding journald's most recent entries
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.)


-- 
863710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-17+deb8u6
Severity: normal

Dear Maintainer,

I have tried to retrieve recent journal entries (with matching fields),
but the retrieved entries were not the most recent ones:

$ journalctl OBJECT_ID=50483 -n 15 | tail -n 1 | cut -c 1-15
May 29 23:05:13
$ journalctl OBJECT_ID=50483 -n 14 | tail -n 1 | cut -c 1-15
May 29 23:05:13
$ journalctl OBJECT_ID=50483 -n 13 | tail -n 1 | cut -c 1-15
May 30 03:04:57
$ journalctl OBJECT_ID=50483 -n 12 | tail -n 1 | cut -c 1-15
May 30 07:05:03
$ journalctl OBJECT_ID=50483 -n 11 | tail -n 1 | cut -c 1-15
May 30 07:05:03
$ journalctl OBJECT_ID=50483 -n 12 | tail -n 1 | cut -c 1-15
May 30 07:05:03
$ journalctl OBJECT_ID=50483 -n 13 | tail -n 1 | cut -c 1-15
May 30 03:04:57
$ journalctl OBJECT_ID=50483 -n 14 | tail -n 1 | cut -c 1-15
May 29 23:05:13
$ journalctl OBJECT_ID=50483 -n 15 | tail -n 1 | cut -c 1-15
May 29 23:05:13

Here is another example, a bit redacted (any  is identical to
another : the same few messages get inserted there roughly
every 4 hours):

$ journalctl OBJECT_ID=50482 -n 1
-- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:09:13 
MSK. --
May 30 07:03:49 mars mmdb[131728]: 
$ journalctl OBJECT_ID=50482 -n 2
-- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:09:14 
MSK. --
May 30 03:04:11 mars mmdb[131728]: 
May 30 03:04:11 mars mmsocks[946]: 
$ journalctl OBJECT_ID=50482 -n 3
-- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:09:22 
MSK. --
May 29 23:04:18 mars mmdb[131728]: 
May 29 23:04:19 mars mmsocks[946]: 
May 29 23:05:19 mars rtms4[35053]: 
$ journalctl OBJECT_ID=50482 -n 4
-- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:09:26 
MSK. --
May 29 19:06:03 mars mmdb[131728]: 
May 29 19:06:03 mars mmsocks[946]: 
May 29 19:07:03 mars rtms4[27816]: 
May 29 19:07:03 mars mmsocks[946]: 

Repeating the same commands led to same results, as in the first
example. After that, new messages were inserted, and it got shifted:

$ journalctl OBJECT_ID=50482 -n 1
-- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:20:31 
MSK. --
May 30 11:10:06 mars mmdb[131728]: 
$ journalctl OBJECT_ID=50482 -n 2
-- Logs begin at Sat 2017-05-27 15:00:01 MSK, end at Tue 2017-05-30 11:21:14 
MSK. --
May 30 07:03:49 mars mmdb[131728]: 
May 30 07:03:51 mars mmsocks[946]: 

It doesn't seem to happen with OBJECT_ID's where the messages are not as
repetitive. And it works fine if the `-n` option is not specified, or if
its argument is greater than the amount of messages for a given
OBJECT_ID.

Looks like a similar behaviour can be reproduced using systemd units and
shell scripts (just printing the same messages), with no custom fields
or programs, but I wasn't able to get a clean example (got a few
attempts mixed together the only time when it worked that way, and then
it got fixed on its own -- unlike the above examples).

The default /etc/systemd/journald.conf was used.


-- Package-specific info:

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/32 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-59
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1+b1
ii  libblkid1   2.25.2-6
ii  libc6   2.19-18+deb8u7
ii  libcap2 1:2.24-8
ii  libcap2-bin 1:2.24-8
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20 1.6.3-2+deb8u2
ii  libkmod218-3
ii  liblzma55.1.1alpha+20120614-2+b3
ii  libpam0g1.1.8-3.1+deb8u2
ii  libselinux1 2.3-2
ii  libsystemd0 215-17+deb8u6
ii  mount   2.25.2-6
ii  sysv-rc 2.88dsf-59
ii  udev215-17+deb8u6
ii  util-linux  2.25.2-6

Versions of packages systemd recommends:
ii  dbus1.8.22-0+deb8u1
pn  libpam-systemd  

Versions of packages systemd 

Bug#803524: journalctl too slow

[Michael Biebl]

Control: tags -1 + moreinfo

On Sat, 31 Oct 2015 01:46:59 +0100 Christoph Egger
 wrote:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
> File: /bin/journalctl
> 
> Hi!
> 
> `journalctl -u nsd.service` just takes 10 minutes (!) cpu time to
> scrol to the newest entries. I'd call that too much for something
> that's supposed to replace a `grep nsd /var/log/syslog`

Is this still reproducible with a recent version of systemd?

Is this with persistent journal enabled? If so,
- how big is /var/log/journal?
- does journalctl --verify report any errors?
- is the problem reproducible after removing existing journal files?

Fwiw, if you are interested in the newest journal entries, journalctl
now provides a -r switch, ie. it shows the newest entries first.


-- 
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

Processed: Re: journalctl too slow

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #803524 [systemd] journalctl too slow
Added tag(s) moreinfo.

-- 
803524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803524
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#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

[Michael Biebl]

On Wed, 21 Mar 2018 16:16:40 +0800 johnw  wrote:
> After upgrade systemd to 238-3, I still have this problem :(
> Any one?
> Help, please.

Does it work if you switch to a different display manager, like say
lightdm (which IIRC is the preferred one of xfce). Might be a problem
specific to slim, since I don't see any such issues myself here (using
GNOME/gdm).

Regards,
Michael
-- 
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#893605: warning: #warning "Consider adding the right mmap() syscall definitions here!" [-Wcpp]

[James Cowgill]

On 23/03/18 14:25, Mathieu Malaterre wrote:
> Hi James,
> 
> On Fri, Mar 23, 2018 at 3:19 PM, James Cowgill  wrote:
>> Control: notforwarded -1
>>
>> Hi,
>>
>> On 22/03/18 14:28, Michael Biebl wrote:
>>> Am 22.03.2018 um 12:31 schrieb James Cowgill:
 I sent a patch upstream (see above).
>>>
>>> Thanks!
>>
>> Unfortunately I've had to ask for this to be reverted:
>> https://github.com/systemd/systemd/pull/8563
> 
> Are you saying that none of the unit tests failed after your changes ?
> that's kindda scary :(

No nothing failed.

James



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#893605: warning: #warning "Consider adding the right mmap() syscall definitions here!" [-Wcpp]

[Mathieu Malaterre]

Hi James,

On Fri, Mar 23, 2018 at 3:19 PM, James Cowgill  wrote:
> Control: notforwarded -1
>
> Hi,
>
> On 22/03/18 14:28, Michael Biebl wrote:
>> Am 22.03.2018 um 12:31 schrieb James Cowgill:
>>> I sent a patch upstream (see above).
>>
>> Thanks!
>
> Unfortunately I've had to ask for this to be reverted:
> https://github.com/systemd/systemd/pull/8563

Are you saying that none of the unit tests failed after your changes ?
that's kindda scary :(

> It turns out that enabling MemoryDenyWriteExecute on MIPS causes any
> applications which use threads to fail because the MIPS toolchain
> (still) does not implement PT_GNU_STACK. So this bug is going to require
> some extra toolchain support (at least glibc and one of gcc/binutils but
> I can't remember which) to fix.

___
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#893605: warning: #warning "Consider adding the right mmap() syscall definitions here!" [-Wcpp]

[Debian Bug Tracking System]

Processing control commands:

> notforwarded -1
Bug #893605 [src:systemd] warning: #warning "Consider adding the right mmap() 
syscall definitions here!" [-Wcpp]
Unset Bug forwarded-to-address

-- 
893605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893605
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