Bug#934155: lxc: unprivileged lxc container with veth does not start since update to 1:3.1.0+really3.0.4-1 amd64

hi, i've digged more into the issue. Since update from 1:3.1.0+really3.0.3-8 to 1:3.1.0+really3.0.4-1 binary 'lxc-user-nic' is not SUID anymore. This change looks like: lxc 1:3.1.0+really3.0.3-8 /usr/lib/x86_64-linux-gnu/lxc/lxc-user-nic -rwsr-xr-x root:root lxc 1:3.1.0+really3.0.4-1

Bug#934155: lxc: unprivileged lxc container with veth does not start since update to 1:3.1.0+really3.0.4-1 amd64

attached a log file generated with : lxc-start -F tex --logile texdebug0 --logpriority DEBUG -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments lxc-start tex 20190807151922.327 INFO confile - confile.c:set_config_idmaps:162

Bug#934155: lxc: unprivileged lxc container with veth does not start since update to 1:3.1.0+really3.0.4-1 amd64

Package: lxc Version: 1:3.1.0+really3.0.4-1 Severity: important Dear Maintainer, since update to 1:3.1.0+really3.0.4-1 i cannot use my unprivileged lxc containers with network over veth. containers refuse to start with interfaces like 'lxc.net.0.type = veth'. removing 'lxc.net.0.type = veth' fr

Bug#928599: linux-image-4.19.0-5-amd64-unsigned: WARNING... dcn_bw_update_from_pplib+0x171/0x290 [amdgpu] , full call trace in syslog, system still usable

Package: src:linux Version: 4.19.37-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** this happens on every boot. full call trace in kernel log. i can't abandon the use of amdgpu module as it's required by the raven ridge gpu to