Processed: fixed 876103 in 233-1

Processing commands for cont...@bugs.debian.org: > fixed 876103 233-1 Bug #876103 [systemd-container] systemd-nspawn: --read-only is broken There is no source info for the package 'systemd-container' at version '233-1' with architecture '' Unable to make a source version for version '233-1'

Processed: reopening 876103

Processing commands for cont...@bugs.debian.org: > reopen 876103 Bug #876103 {Done: Michael Biebl } [systemd-container] systemd-nspawn: --read-only is broken 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may

Processed: closing 876103

Processing commands for cont...@bugs.debian.org: > close 876103 Bug #876103 [systemd-container] systemd-nspawn: --read-only is broken Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 876103:

Bug#886914: systemd: Kernel Panic on systemctl daemon-relaod, unit enable/disable when libvirt vms are running

On Thu, 11 Jan 2018 11:01:03 +0200 "Plamen K. Kosseff" wrote: > Package: systemd > Version: 236-2 > Severity: normal > > Dear Maintainer, > > > This is new debian buster install on HP z600 workstation (for hardware spec > see below). > The issue has manifested first during

Bug#870301: systemd: Touchpad fix Dell Inspiron Mini 1012

On Tue, 30 Jan 2018 04:30:58 -0500 (EST) bw wrote: > I'll go back and read your earlier posts, and see what I need to do. I > guess you are recommending that I upgrade systemd and use upstream bug > reporting instead of debian bugtracker? Yes, please upgrade to v238, try

Bug#884784: systemd-network segfaults

On Tue, 19 Dec 2017 19:50:49 +0200 =?utf-8?q?R=C3=A9mi_Denis-Courmont?= wrote: > Package: systemd > Version: 235-3 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > > systemd-networkd from version 236-1 systematically segfaults at

Bug#888955: marked as done (open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc)

Your message dated Sat, 17 Mar 2018 03:12:26 +0100 with message-id and subject line Re: Bug#888955: open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc has caused the Debian Bug report #888955, regarding open-vm-tools.service

Bug#892321: attempts to suspend failing after crash

On Thu, 8 Mar 2018 10:02:32 + Daniel Pocock wrote: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > > Laptop was connected to a Thunderbolt dock, lid closed, using desktop > monitor and keyboard, everything connected through the dock.  It is a >

Bug#807041: logind: laptop unexpectedly auto-suspends after some time of inactivity

Package: systemd Version: 238-2 Followup-For: Bug #807041 Actuall, having said that, I have found https://github.com/systemd/systemd/issues/786 and my new laptop does have Nvidia with closed source driver so this would explain it. Will dig up my old laptop and test again with that... George

Bug#892989: weird chars found in dpkg output

Am 16.03.2018 um 08:45 schrieb Harald Dunkel: > On 03/15/18 18:46, Michael Biebl wrote: >> >> With a UTF-8 locale (which you really should enable), systemctl will use >> '→', for a non-UTF8 locale, systemctl will fall back to '->' >> >> > > Sorry to say, but thats ridiculous. Shouldn't it work no

Bug#892989: weird chars found in dpkg output

On 03/15/18 18:46, Michael Biebl wrote: With a UTF-8 locale (which you really should enable), systemctl will use '→', for a non-UTF8 locale, systemctl will fall back to '->' Sorry to say, but thats ridiculous. Shouldn't it work no matter what? Ain't that "if locale == xxx" just asking for