Bug#1067733: iptables: regression in 1.8.9 with -n breaks portblock in resource-agents

On Tue, Mar 26, 2024 at 09:56:57AM +0100, Fabio Pedretti wrote: > > Version 1.8.10 fixed this bug (see "udp" and "tcp" in "prot") in > > https://git.netfilter.org/iptables/commit/?id=34f085b1607364f4eaded1140060dcaf965a2649 > > iptables 1.8.10 was released on 2023-10-10, but this commit was

Bug#1067733: iptables: regression in 1.8.9 with -n breaks portblock in resource-agents

Package: iptables Version: 1.8.9-2 Severity: important Tags: upstream Dear Maintainer, there is a known (and fixed) bug in iptables where it prints the "prot" as numerical value if "-n" is given (see 17 and 6): # iptables --version iptables v1.8.9 (legacy) # iptables -nL Chain LIBVIRT_OUT (1

Bug#932433: lvm2: lvm expects udev, even if obtain_device_list_from_udev=0, which breaks container work loads

Package: lvm2 Version: 2.03.02-3 Severity: important Dear Maintainer, * What led up to the situation? Using lvm tools in a buster docker container. * What exactly did you do (or not do) that was effective (or ineffective)? Prepare a VG on the host (or have an existing one): dd

Bug#906034: temporary fix

If somebody finds that bug by coincidence, a temporary fix for me wass to switch from fb to another driver. In my case this was the intel one: /etc/X11/xorg.conf.d/20-intel.conf ection "Device" Identifier "Intel Graphics" Driver "intel" EndSection Regards, rck

Bug#906034: xserver-xorg-core: back screen with fb rotate/failed to add rotate fb

Package: xserver-xorg-core Version: 2:1.20.0-3 Severity: important Tags: upstream Dear Maintainer, * What led up to the situation? Upgrading to version 1.20 * What exactly did you do (or not do) that was effective (or ineffective)? xrandr --output DP-2 --auto --rotate left --output DP-1 --auto

Bug#865975: docker.io breaks (bridged) network for VMs

Hi, docker is not configured in any special way, the only change to the config file was attached in the original report. Here are the relevant outputs of a full session after a fresh boot: after boot $ ip a s 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group

Bug#865975: docker.io breaks (bridged) network for VMs

Package: docker.io Version: 1.13.1~ds1-2 Severity: critical Tags: upstream Justification: breaks unrelated software Dear Maintainer, * What led up to the situation? Any docker command like "docker images" * What was the outcome of this action? Network breaks for all libvirt VMs (i.e., they are

Bug#863248: containerd 0.2.3+git20170126.85.aa8187d~ds1-1: container not started (docker.io 1.13.0~ds1-3)

Package: containerd Version: 0.2.3+git20170126.85.aa8187d~ds1-1 Severity: grave Justification: renders package unusable Dear Maintainer, I have the following versions: containerd: 0.2.3+git20170126.85.aa8187d~ds1-1 docker.io: 1.13.0~ds1-3 I report the bug against containerd because it shows up

Bug#855407: docker.io: Dependency missmatch (docker.io 1.11.2~ds1-6 vs. containerd 0.2.3~git20161117.78.03e5862~ds1-1)

Package: docker.io Version: 1.11.2~ds1-6 Severity: grave Justification: renders package unusable Dear Maintainer, After the upgrade docker does not start anymore. Starting it manually produces the following output: sudo docker daemon --debug DEBU[] docker group found. gid: 125 DEBU[]

Bug#829245: /etc/os-release: Please specify VERSION_CODENAME

Hi, I also find setting VERSION_CODENAME useful. For the stable vs. testing/sid situation I would suggest that VERSION_CODENAME is only set in stable. For example "VERSION" and "VERSION_ID" are now only set on my jessie boxes, but not on my stretch boxes. We could do the same with

Bug#790345: same problem on my stretch box

I suffer from the same problem (gdm3/3.14.1-8). Today I updated to the current version in sid (gdm3/3.14.2-1) but no change. $ lspci |egrep VGA 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) For now I switched to slim. Regards, rck -- To