Package: upgrade-reports
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
Upgrading system to the testing branch.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Just installed debian
Arturo Borrero Gonzalez писал 2015-12-15 15:16:
could you please check that the bug has been fixed in jessie-backports?
Yes, it doesn't segfault anymore.
Package: fish
Version: 2.1.2+dfsg1-1~bpo8+1
Severity: wishlist
Dear Maintainer,
Currently fish 2.1 is found in jessie-backports.
Please update to 2.2 as in stretch.
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: armhf (armv7l)
Kernel:
Package: nftables
Version: 0.5-1~bpo8+1
This is jessie with jessie-backports enabled and kernel
4.1.0-0.bpo.2-amd64 installed from backports as well.
libc version 2.19-18+deb8u1.
nft started to segfault right after update to 0.5:
(ruleset is empty)
# nft -f /etc/nftables.conf
Segmentation fau
Arturo Borrero Gonzalez писал 2015-10-06 09:47:
Could you please send me a backtrace?
Ok, this is the backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) bt
#0 0x in ?? ()
#1 0x0040b02d in ?? ()
#2 0x0040b188 in ?
Where can I download older nftables and libnftnl0 for now?
But I filed the bug against jessie-backports.
According to http://backports.debian.org/jessie-backports/overview/ it's
not updated... Is it?
Package: installation-reports
Severity: important
-- Package-specific info:
Boot method: USB stick
Image version: Lenny RC1 amd64 netinst
(http://cdimage.debian.org/cdimage/lenny_di_rc1/amd64/iso-cd/debian-testing-amd64-netinst.iso)
Date:
Machine: Athlon X2 5200+ desktop
Base System Installa
On 11 Jan 09, Ferenc Wagner wrote:
> Pyotr Berezhkov writes:
>
> > rebooting into the installed system failed, as the initrd
> > incorrectly identified the root device. As it turned out, the root
> > device specified on Lilo's kernel command line (root=fd02
Package: initramfs-tools
Version: 0.92o
Severity: important
Tags: patch
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=ru_RU.UTF8, LC_CTYPE=ru_RU.UTF8 (ch
On 15 Jan 09, maximilian attems wrote:
> i'd guess that grub is much better tested as it is the default.
> any special reason why you'd picked lilo.
> the default encrypted root install is afaik very well tested.
>
Well, the encrypted root install with LVM _failed_ for me, which is why
I reported
On 15 Jan 09, Christian Perrier wrote:
> > > Pyotr Berezhkov writes:
> > >
> > Hi, I suggest closing this bug. I'll report it with initramfs-tools, as
> > I realized it's their bug, not yours.
>
> It's maybe better to just reassign the bug as
Note: This bug began life as Bug#511447, for those who need the full
background.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 15 Jan 09, maximilian attems wrote:
> how about you debug the real cause of the failure, see
> http://wiki.debian.org/InitramfsDebug for more hints.
Thank you. I took a look at it. I'm already quite familiar with the
busybox environment in /initrd. It's what allowed me to diagnose and
solve
Well, here you have it. With this revision of the patch, the code only
runs if the user explicitly asks it to by specifying 'cryptsetroot' on
the kernel command line. Otherwise nothing happens. This was done in
response to maximilian attems' objection:
> anyway the way you tried to solve it is
On 16 Jan 09, Frans Pop wrote:
> "This is where is crashed" is not very specific. Please describe the
> excact steps you performed after starting the partitioner and indicate
> when exactly the crash happened.
> I don't see any crash in the first syslog, at most a "hang" (from looking
> at the
On 19 Feb 09, Jonas Meurer wrote:
> Hey,
>
> Maks, I spent several hours now on debugging this issue, and all I found
> out is that the patch by Pyotr is correct if you don't want to change
> the way, how initramfs manages /dev/root.
>
Thanks for taking the time to exami
This problem is still present in stable (buster 10.4):
kernel 4.19.0-9-amd64
wireguard-dkms 0.0.20181119-1
18 matches
Mail list logo
