Bug#898260: systemd: HP notebook ZBook 17 G4 - WLAN hardware button not working

Hello Michael, yes, I'm interested, but I still had no success when following the rough advises. I need more time for another attempt. René On Sat, 2018-06-23 at 00:29 +0200, Michael Biebl wrote: > On Wed, 9 May 2018 13:53:29 +0200 Michael Biebl > wrote: > > Control: reassign -1 udev 238-4 >

Bug#902314: marked as done (libudev1: Installing libudev1 239-1 removes 48 critical packages)

Your message dated Mon, 25 Jun 2018 00:09:12 +0200 with message-id <62df060d-8377-9e1d-5d70-7f84aa60d...@debian.org> and subject line Re: Bug#902314: libudev1: Installing libudev1 239-1 removes 48 critical packages has caused the Debian Bug report #902314, regarding libudev1: Installing libudev1

Processed: severity of 902314 is normal

Processing commands for cont...@bugs.debian.org: > severity 902314 normal Bug #902314 [libudev1] libudev1: Installing libudev1 239-1 removes 48 critical packages Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 902314:

Bug#902314: libudev1: Installing libudev1 239-1 removes 48 critical packages

Package: libudev1 Version: 239-1 Severity: critical Tags: d-i Justification: breaks unrelated software Dear Maintainer, Running apt dist-upgrade when the only thing being upgraded is libudev-dev libudev1 libudev1:i386 Removed the following packages, leaving X unuseable, not network, not mouse,

Processed: affects 902287

Processing commands for cont...@bugs.debian.org: > affects 902287 + avahi Bug #902287 [systemd] systemctl unmask --runtime no longer supported Added indication that 902287 affects avahi > thanks Stopping processing here. Please contact me if you need assistance. -- 902287:

Bug#902287: systemctl unmask --runtime no longer supported

Package: systemd Version: 239-1 Severity: serious upstream has removed support for systemctl unmask --runtime [1] According to codesearch we currently have two packages in the archive using unmask --runtime: avahi and policykit-1

Bug#901991: LogLevel vs log_level vs --log-level

Am 21.06.2018 um 07:36 schrieb Harald Dunkel: > Package: systemd > Version: 232-25+deb9u2 > Severity: wishlist > > systemd has several naming schemes for the same configuration option, > e.g. > > LogLevel    (/etc/systemd/system.conf) > --log-level    (systemd command line) >

Re: new version of systemd seems to break autopkgtests of policykit-1, kwin and python-dbusmock

Hi systemd and kwin maintainers, On 23-06-18 14:38, Paul Gevers wrote: >> The breakage in kwin looks unrelated to me (maybe caused by the libinput >> update, dunno). > > To avoid any doubt, I have triggered a reference run, with only testing > (results in a hour or so). But the last successful

Bug#900956: marked as done (systemd-container: doesn't reboot containter, exit with error "Parent died too early")

Your message dated Sun, 24 Jun 2018 11:29:18 +0200 with message-id <434ecc0f-d114-3e57-1e70-e4197f7ac...@debian.org> and subject line Re: systemd-container: doesn't reboot containter, exit with error "Parent died too early" (SOLVED) has caused the Debian Bug report #900956, regarding

Bug#900956: systemd-container: doesn't reboot containter, exit with error "Parent died too early" (SOLVED)

New version 239 solve (for me) the problem, now i can reboot again. Regards, Antonio. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@alioth-lists.debian.net