Bug#801342:

2018-12-09 Thread Rodolfo Sanchez
Tengo dudas ,una de ella es cuanto es el impuesto y la otra se paga cuando se esté entregando

Bug#801342: systemd: plain dm-crypt volumes not brought up on boot

2018-10-29 Thread Michael Biebl
Control: tags -1 + moreinfo On Thu, 08 Oct 2015 21:21:36 +0200 =?UTF-8?B?UmVuw6kgV2FnbmVy?= wrote: > Package: systemd > Version: 215-17+deb8u2 > Severity: normal > > [This was originally meant as a followup to #712439 which has been > archived.] > > Dear maintainers, > > I upgraded a laptop

Bug#801342: systemd: plain dm-crypt volumes not brought up on boot

2017-04-19 Thread Jamesc Netvalue
I can confirm this bug is still present. My /etc/crypttab is correct, verified with 'cryptdisks_start bobfred' My /etc/fstab is correct, can mount /dev/mapper/bobfred on /bobfred On boot systemd handles my LUKS root partition correctly. bobfred is where systemd gets stuck. It prompts for a

Bug#801342: 801342

2015-11-05 Thread Matteo Hirschstein
I'm experiencing the same issue, It's pretty annoying. I would like this bug to be fixed, I don't like the "restart" workaround (anyway, it's working). Any news about it?

Bug#801342: systemd: plain dm-crypt volumes not brought up on boot

2015-10-11 Thread René Wagner
Dear maintainers, it turns out that other users are affected by this, too. Over on debian-user@ Arno Schuring suggested [1] to add service files that override the default ones and call cryptdisks_start/stop as a workaround. I can confirm that with the following service files for swap and tmp my

Bug#801342: systemd: plain dm-crypt volumes not brought up on boot

2015-10-08 Thread René Wagner
Package: systemd Version: 215-17+deb8u2 Severity: normal [This was originally meant as a followup to #712439 which has been archived.] Dear maintainers, I upgraded a laptop from wheezy to jessie last weekend using dist-upgrade which installed systemd as the init system. Since the upgrade