Bug#792627: linux-image-4.0.0-2-686-pae: linux-image-4.0 does not bind ethernet device

Am 29.01.2016 um 20:01 schrieb Michael Biebl: > Am 29.01.2016 um 18:05 schrieb Hans: > Is the mac address referenced in /etc/udev/70-persistent-net.rules the > one provided by the hardware or the one you've set via macchanger? Yes, it is. >>> >>> Heh, the former or the latter? >>

Bug#832566: systemd-machined breaks automounting nfs shares

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

Bug#775065: marked as done (dpkg --configure -a results in "Hangup" after first package)

Your message dated Tue, 28 Mar 2017 07:28:44 +0200 with message-id and subject line Re: Bug#775065: dpkg --configure -a results in "Hangup" after first package has caused the Debian Bug report #775065, regarding dpkg --configure -a results in

Bug#758825: marked as done (systemd: Installs without warning despite beeing unable to run)

Your message dated Tue, 28 Mar 2017 07:06:01 +0200 with message-id <4e7aafaf-48b3-ed90-bc09-328467582...@debian.org> and subject line Re: systemd: Installs without warning despite beeing unable to run has caused the Debian Bug report #758825, regarding systemd: Installs without warning despite

Processed: severity of 831466 is wishlist

Processing commands for cont...@bugs.debian.org: > severity 831466 wishlist Bug #831466 [systemd] systemd: please make IPv6 user space code run time configurable Severity set to 'wishlist' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 831466:

Processed: severity of 764555 is wishlist

Processing commands for cont...@bugs.debian.org: > severity 764555 wishlist Bug #764555 [systemd] Please add Recommends: plymouth Bug #779612 [systemd] systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable Severity set to

Processed: tagging 846377

Processing commands for cont...@bugs.debian.org: > tags 846377 + help Bug #846377 [systemd] [systemd] /lib/systemd/systemd --user starts dbus-daemon without AFS token Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 846377:

Bug#856590: systemd: Unspecified problems mounting /usr partition

Control: tags -1 + moreinfo Am 02.03.2017 um 19:20 schrieb Joel Cross: > -- Subject: Unit dev-sdb2.device has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- Unit dev-sdb2.device has failed. > -- > -- The result is timeout. > Mar 02 11:26:47 abijah

Processed: Re: Bug#856590: systemd: Unspecified problems mounting /usr partition

Processing control commands: > tags -1 + moreinfo Bug #856590 [systemd] systemd: Unspecified problems mounting /usr partition Added tag(s) moreinfo. -- 856590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#858843: marked as done (systemd: Default value of LidSwitchIgnoreInhibited should be no)

Your message dated Tue, 28 Mar 2017 06:30:34 +0200 with message-id and subject line Re: Bug#858843: systemd: Default value of LidSwitchIgnoreInhibited should be no has caused the Debian Bug report #858843, regarding systemd: Default value of

Bug#858863: udev: postinst fails if NAME_REGEX does not match "input"

2017-03-27 23:32 GMT+02:00 Michael Biebl : > Control: tags -1 + moreinfo > > Am 27.03.2017 um 23:17 schrieb Szymon S: >> Package: udev >> Version: 232-21 >> Severity: normal >> >> >> The bug is present in stable, unstable and experimental repos. >> addgroup should have

Bug#858863: udev: postinst fails if NAME_REGEX does not match "input"

Am 27.03.2017 um 23:32 schrieb Michael Biebl: > postinst does not fail here. Do you have custom configuration in > /etc/adduser.conf? Can you attach this file to the bug report please -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from

Bug#858843: systemd: Default value of LidSwitchIgnoreInhibited should be no

Am 27.03.2017 um 21:27 schrieb Martin Monperrus: >> How exactly do they compete for the "lid closed" event? > > Both try to perform an action. If they are the same, say suspend, you just > have a warning. If they > are different, you don't really understand what and why one or the other >

Processed: Re: Bug#858863: udev: postinst fails if NAME_REGEX does not match "input"

Processing control commands: > tags -1 + moreinfo Bug #858863 [udev] udev: postinst fails if NAME_REGEX does not match "input" Added tag(s) moreinfo. -- 858863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#858863: udev: postinst fails if NAME_REGEX does not match "input"

Control: tags -1 + moreinfo Am 27.03.2017 um 23:17 schrieb Szymon S: > Package: udev > Version: 232-21 > Severity: normal > > > The bug is present in stable, unstable and experimental repos. > addgroup should have --force-badname added (or NAME_REGEX removed from > config) postinst does not

Bug#858843: systemd: Default value of LidSwitchIgnoreInhibited should be no

> How exactly do they compete for the "lid closed" event? Both try to perform an action. If they are the same, say suspend, you just have a warning. If they are different, you don't really understand what and why one or the other happens. > I was under the impression, that XFCE nowadays uses

Bug#858818: please consider implementing or at least documenting a headless-friendly emergency target

Michael Biebl [2017-03-27 18:03 +0200]: > I don't think such a service needs to be part of ssh (or systemd for > that matter), it might actually be better if that was shipped by a > separate package, which can be installed on demand for cases likes your > (and is ideally maintained by users of

Bug#858818: please consider implementing or at least documenting a headless-friendly emergency target

Am 27.03.2017 um 18:03 schrieb Michael Biebl: > I don't think such a service needs to be part of ssh (or systemd for > that matter), it might actually be better if that was shipped by a > separate package, which can be installed on demand for cases likes your > (and is ideally maintained by users

Bug#858818: please consider implementing or at least documenting a headless-friendly emergency target

Am 27.03.2017 um 17:07 schrieb Marc Haber: > Hi Felipe, > > thanks for your fast answer. I really appreciate your consideration. > > On Mon, Mar 27, 2017 at 11:47:40AM -0300, Felipe Sateler wrote: >> On Mon, Mar 27, 2017 at 5:51 AM, Marc Haber >> wrote: >>> (1)

Bug#858843: systemd: Default value of LidSwitchIgnoreInhibited should be no

Am 27.03.2017 um 17:17 schrieb Martin Monperrus: > Package: systemd > Version: 232-19 > Severity: minor > > Dear Maintainer, > > What's the problem? > systemd and xfce4-power-manager compete to handle event "lid closed", this > yields confusing behavior and error messages. How exactly do they

Bug#858843: systemd: Default value of LidSwitchIgnoreInhibited should be no

Package: systemd Version: 232-19 Severity: minor Dear Maintainer, What's the problem? systemd and xfce4-power-manager compete to handle event "lid closed", this yields confusing behavior and error messages. What's the solution? ignore inhibited messages, as done for other events, the default

Bug#858818: please consider implementing or at least documenting a headless-friendly emergency target

Hi Felipe, thanks for your fast answer. I really appreciate your consideration. On Mon, Mar 27, 2017 at 11:47:40AM -0300, Felipe Sateler wrote: > On Mon, Mar 27, 2017 at 5:51 AM, Marc Haber > wrote: > > (1) allow regular login in emergency mode > > Instead of

Bug#858818: please consider implementing or at least documenting a headless-friendly emergency target

On Mon, Mar 27, 2017 at 5:51 AM, Marc Haber wrote: > Package: systemd > Version: 232-21 > Severity: wishlist > > Hi, > > in the pre-systemd era, a system would continue booting even after an > error. This frequently resulted in a crippled, but running system >

Bug#798083: marked as done (systemd: Systemd assumes that ESP is mounted in /boot)

Your message dated Mon, 27 Mar 2017 14:48:08 +0100 with message-id <20170327134808.r4n636gioevr6kaz@wintermute> and subject line Re: Bug#798083: systemd: Systemd assumes that ESP is mounted in /boot has caused the Debian Bug report #798083, regarding systemd: Systemd assumes that ESP is mounted

Bug#858818: please consider implementing or at least documenting a headless-friendly emergency target

Package: systemd Version: 232-21 Severity: wishlist Hi, in the pre-systemd era, a system would continue booting even after an error. This frequently resulted in a crippled, but running system which allowed a (sometimes crippled) remote login which allowed fixing things from remote without having