Bug#782971: sane-utils: saned systemd config does not allow remote scanner access

2015-04-23 Thread Jörg Frings-Fürst
Hi Michael, Am Donnerstag, den 23.04.2015, 23:15 +0200 schrieb Michael Biebl: > Hi Jörg! > > just a quick remark, when re-assigning a bug, please always CC the new > package, in that case syst...@packages.debian.org > Ok and sorry.. > On Thu, 23 Apr 2015 22:50:05 +0200 > =?ISO-8859-1?Q?J=F6rg_

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

2015-04-23 Thread Rick Thomas
On Apr 23, 2015, at 2:31 PM, Michael Biebl wrote: > Am 23.04.2015 um 21:47 schrieb Rick Thomas: >> >> On Apr 23, 2015, at 1:29 AM, Michael Biebl wrote: >> >>> There might be a race somewhere, i.e. lvm2-activation(-early).service >>> being run *before* mdadm has assembled the RAID. >>> >>> Yo

Bug#782522: still seeing multiple fsck's of /

2015-04-23 Thread Mike Kupfer
Hi, I have $ dpkg -l initramfs-tools systemd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-

Bug#781615: systemd: Only boots in rescue mode

2015-04-23 Thread Michael Biebl
Am 03.04.2015 um 23:00 schrieb Christoph Egger: > Christoph Egger writes: > >> Michael Biebl writes: >>> I assume the f2fs-tools package is installed? >>> What output (and return code) do you get, if you run >>> fsck.f2fs /dev/disk/by-uuid/691d5901-2f6b-4d33-abbb-131376511c53 >>> from a rescue m

Bug#782971: sane-utils: saned systemd config does not allow remote scanner access

2015-04-23 Thread Vincent Danjean
Hi, Le 23/04/2015 22:50, Jörg Frings-Fürst a écrit : > reassign 782971 systemd > thanks > > Hello Vincent, > > thank you for spending your time helping to make Debian better with this > bug report. > > I think that this bug comes from systemd. At irc #debian-systemd I found > on answer since

Bug#765577: debian 8.0 errata (Re: Bug#765577: netboot install writes duplicates to 70-persistent-net.rules)

2015-04-23 Thread Cyril Brulebois
Michael Biebl (2015-04-23): > Am 23.04.2015 um 22:22 schrieb Cyril Brulebois: > > Michael Biebl (2015-04-23): > > >> netboot install writes duplicate entries to 70-persistent-net.rules > >> ~~~ > > > > It might be better not to emb

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

2015-04-23 Thread Michael Biebl
Am 23.04.2015 um 21:47 schrieb Rick Thomas: > > On Apr 23, 2015, at 1:29 AM, Michael Biebl wrote: > >> There might be a race somewhere, i.e. lvm2-activation(-early).service >> being run *before* mdadm has assembled the RAID. >> >> You could test this theory, be artifically delaying those two ser

Bug#765577: debian 8.0 errata (Re: Bug#765577: netboot install writes duplicates to 70-persistent-net.rules)

2015-04-23 Thread Michael Biebl
Am 23.04.2015 um 22:22 schrieb Cyril Brulebois: > Michael Biebl (2015-04-23): >> netboot install writes duplicate entries to 70-persistent-net.rules >> ~~~ > > It might be better not to embed the “netboot install” information here,

Bug#782971: sane-utils: saned systemd config does not allow remote scanner access

2015-04-23 Thread Michael Biebl
Hi Jörg! just a quick remark, when re-assigning a bug, please always CC the new package, in that case syst...@packages.debian.org On Thu, 23 Apr 2015 22:50:05 +0200 =?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?= wrote: > reassign 782971 systemd > thanks > > > > Hello Vincent, > > thank you for spend

Processed: Re: Bug#782971: sane-utils: saned systemd config does not allow remote scanner access

2015-04-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 782971 systemd Bug #782971 [sane-utils] sane-utils: saned systemd config does not allow remote scanner access Bug reassigned from package 'sane-utils' to 'systemd'. No longer marked as found in versions sane-backends/1.0.24-8. Ignoring r

Bug#765577: debian 8.0 errata (Re: Bug#765577: netboot install writes duplicates to 70-persistent-net.rules)

2015-04-23 Thread Cyril Brulebois
Hi! Michael Biebl (2015-04-23): > I talked to the release team and they prefer to postpone a fix to 8.1. > I therefor would like to see a short paragraph added to the d-i 8.0 > errata [1]. > > Afaics, the issue so far only happened for automated installations. > There is no real solution/workaro

Re: [Pkg-xfce-devel] Bug#782456: plymouth: With plymouth installed, starting the DM sometimes fails

2015-04-23 Thread Yves-Alexis Perez
On jeu., 2015-04-23 at 12:30 +0200, intrigeri wrote: > Hi systemd and lightdm maintainer, > > please have a look at #782456 -- it might be local misconfiguration > (in which case, asking Ralf for the debugging info you need would be > very nice of you), or a bug in the new DM / systemd integration

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

2015-04-23 Thread Rick Thomas
On Apr 23, 2015, at 1:29 AM, Michael Biebl wrote: > There might be a race somewhere, i.e. lvm2-activation(-early).service > being run *before* mdadm has assembled the RAID. > > You could test this theory, be artifically delaying those two services. > Copy them to /etc/systemd/system, and add a

Bug#765577: debian 8.0 errata (Re: Bug#765577: netboot install writes duplicates to 70-persistent-net.rules)

2015-04-23 Thread Michael Biebl
Hi everyone! I talked to the release team and they prefer to postpone a fix to 8.1. I therefor would like to see a short paragraph added to the d-i 8.0 errata [1]. Afaics, the issue so far only happened for automated installations. There is no real solution/workaround ttbomk besides rebuilding d

Re: Bug#782456: plymouth: With plymouth installed, starting the DM sometimes fails

2015-04-23 Thread Ralf Jung
Hi all, I finally had the time to experiment a bit more. Here are my latest findings: I removed all non-Debian kernels, just to be sure. Immediately after enabling "splash" in grub again, the behavior of "lightdm always fails to start" reappeared. Then I changed plymouth to text mode, re-generate

Bug#783182: Uses /bin/systemd-run which is 69-lvm-metad.rules

2015-04-23 Thread Michael Biebl
Package: lvm2 Version: 2.02.111-2.2 Severity: normal File: /lib/udev/rules.d/69-lvm-metad.rules /lib/udev/rules.d/69-lvm-metad.rules contains the following line: ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm pvscan --cache $major:$minor", GOTO="lvm_end" In Debian, sy

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

2015-04-23 Thread Rick Thomas
On Apr 23, 2015, at 1:29 AM, Michael Biebl wrote: > Can you boot with systemd.log_level=debug on the kernel command line and > attach the journal output of this boot, so we have more information out > the timing, i.e. when certain services are started > > There might be a race somewhere, i.e. l

Bug#783170: marked as done ("systemd should document distinction between $FOO and ${FOO})

2015-04-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Apr 2015 12:32:23 +0200 with message-id <201504231232.25121.hol...@layer-acht.org> and subject line Re: use $FOO instead of ${FOO} ? has caused the Debian Bug report #783170, regarding "systemd should document distinction between $FOO and ${FOO} to be marked as done. Thi

Re: Bug#782456: plymouth: With plymouth installed, starting the DM sometimes fails

2015-04-23 Thread intrigeri
Hi systemd and lightdm maintainer, please have a look at #782456 -- it might be local misconfiguration (in which case, asking Ralf for the debugging info you need would be very nice of you), or a bug in the new DM / systemd integration. Cheers, -- intrigeri __

Bug#783170: use $FOO instead of ${FOO} ?

2015-04-23 Thread Michael Biebl
Am 23.04.2015 um 11:45 schrieb Holger Levsen: > clone 783088 -1 > retitle -1 "systemd should document distinction between $FOO and ${FOO} > reassign -1 systemd > tags -1 + upstream > thanks > > Hi Rian, > > On Mittwoch, 22. April 2015, Rian Hunter wrote: >>> thanks for your bugreport. Can you con

Processed: Re: use $FOO instead of ${FOO} ?

2015-04-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 783088 -1 Bug #783088 [tlsdate] tlsdate: systemd service file appends erroneous command line arguments Bug 783088 cloned as bug 783170 > retitle -1 "systemd should document distinction between $FOO and ${FOO} Bug #783170 [tlsdate] tlsdate:

Re: use $FOO instead of ${FOO} ?

2015-04-23 Thread Holger Levsen
clone 783088 -1 retitle -1 "systemd should document distinction between $FOO and ${FOO} reassign -1 systemd tags -1 + upstream thanks Hi Rian, On Mittwoch, 22. April 2015, Rian Hunter wrote: > > thanks for your bugreport. Can you confirm that using $FOO instead of > > ${FOO} fixes the issue? > Ye

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

2015-04-23 Thread Rick Thomas
On Apr 21, 2015, at 11:17 AM, Michael Biebl wrote: > If you have the sysvinit package installed, > you can try booting with sysvinit temporarily via > init=/lib/sysvinit/init on the kernel command line. > > Does that work? I had to install sysvinit. And I had to make up a suitable /etc/initta

Hello.

2015-04-23 Thread Elizabeth Denis.
My dear good Friend, Hello. I write you again in good faith, in need of your assistance to welcome my Children to complete their education in your Country, because of the up-coming 2015 presidential elections. I am afraid that another political crisis may start again and I am surprised of not g

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

2015-04-23 Thread Michael Biebl
Am 23.04.2015 um 09:21 schrieb Rick Thomas: > > On Apr 22, 2015, at 8:17 AM, Michael Biebl wrote: > >> Am 22.04.2015 um 12:10 schrieb Rick Thomas: >>> This works. Interestingly, without the sleep loop the vgchange >>> fails. >>> >>> Now, you say that a VM with two virtual disks configured as RA

Bug#782793: systemd: ext4 filesystem on lvm on raid causes boot to enter emergency shell

2015-04-23 Thread Rick Thomas
On Apr 22, 2015, at 8:17 AM, Michael Biebl wrote: > Am 22.04.2015 um 12:10 schrieb Rick Thomas: >> This works. Interestingly, without the sleep loop the vgchange >> fails. >> >> Now, you say that a VM with two virtual disks configured as RAID1 >> with a logical volume works fresh out of the bo