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

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 lxd

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

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 f

Bug#832566: systemd-machined breaks automounting nfs shares

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 t

Bug#876103: marked as done (systemd-nspawn: --read-only is broken)

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.

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

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 co

Bug#775613: marked as done (systemd: why is /run/systemd/inhibit/1.ref inherited?)

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

Bug#810247: 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.

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

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.

Processed: found 793198 in 215-17+deb8u1

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 assistanc

Bug#764555: marked as done (Please add Recommends: plymouth)

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

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

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

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

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

Bug#799922: marked as done (systemd-machined: error: error from service: CreateMachine: Activation of org.freedesktop.machine1 timed out)

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

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

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