Bug#783618: marked as done (systemd: journald ignores MaxLevelKMsg=warning)

2018-03-24 Thread 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)

2018-03-24 Thread 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)

2018-03-24 Thread 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)

2018-03-24 Thread 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)

2018-03-24 Thread 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

2018-03-24 Thread 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

2018-03-24 Thread 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

2018-03-24 Thread 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?)

2018-03-24 Thread 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

2018-03-24 Thread 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)

2018-03-24 Thread 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

2018-03-24 Thread 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

2018-03-24 Thread 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