Am Sonntag, 29. Juli 2018, 18:46:20 CEST schrieb Guilhem Moulin:
> readlink -f /lib/cryptsetup/askpass
readlink returns:
/lib/cryptsetup/askpass
Regards,
C. Dominik Bódi
signature.asc
Description: This is a digitally signed message part.
This bug affects wheezy as well. I just had trouble booting a wheezy
system after adding a second Physical Volume to my LVM setup.
The workaround is setting
GRUB_DISABLE_LINUX_UUID=true
in /etc/default/grub
That will make boot again as it will use the
root=/dev/mapper/nameofrootlv
for the kernel
ate key data.
Regards,
C. Dominik Bódi
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.17.0-monster-1 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.U
Unfortunately, I did not think of making a foto of the messages.
I've tried that new kernel on my "real" machines at home, there it
booted without problems. Both machines are using luks and lvm. One is
unlocked manually, the other via mandos in my LAN. Both machines booted
the 3.16-1 kernel withou
Package: php5-json
Version: 1.3.4-2
Severity: grave
php5-json 1.3.4-2 is missing /usr/lib/php5/20121212/json.so, completely
breaking the package and making everything dependent on this package
unusable. This effectively breaks php5 with apache on Debian sid.
Downgrading to 1.3.3-1 fixes this probl
accordingly in /etc/default/burp.
I'm not familiar with the debian policy on initscripts, but should an
init script not have an exit 0 at the end of the file?
Regards,
C. Dominik Bódi
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I've got the same problem with debian unstable amd64.
The reason for that behaviour is a link conflict between the mp3splt-gtk
binary and its dependency, libaudcore1.
mp3splt-gtk is linked against libgtk-2.0-0 and libaudcore1. However,
libaudcore1
After having enabled the debug mode via plugin-runner.conf as you suggested.
The "fatal" error occurs immediately after the first debug messages, which is:
"Initializing GNUTLS"
Then I booted the kernel with the break option and ran "sh scripts/init-
premount/udev". Indeed, it seems that both /de
Package: linux-2.6
Version: 2.6.16-6
Severity: critical
Justification: breaks the whole system
*** Please type your report below this line ***
The kernel seems to boot up normally, but then fails to mount the root device
with a message
"failed to mount root on /dev/hda8 - no such device"
according
9 matches
Mail list logo
