Bug#1053117: r8152 driver unable to bring up RTL8156BG

Package: linux-image-6.5.0-1-amd64 Version: 6.5.3-1 The r8152 driver is unable to bring up a RTL8156BG device. It's able to enumerate and present some info, but actually passing packets fails. I will note that the RTL8156BG firmware is not in the the firmware-realtek package, unlike its sister

Bug#1053116: cdc_ncm driver fails to bring up RTL8156BG

Package: linux-image-6.1.0-11-amd64-unsigned Version: 6.1.38-4 The cdc_ncm driver is able to enumerate an RTL8156BG device, and glean some capabilities, but it is unable to fully bring up and utilize it, for unknown errors. (The systemd log doesn't contain any details, just a generic failed

Bug#1037549: Support for RTL8156BG broken

Package: linux-image-6.1.0-9-amd64 Version: 6.1.27-1 Currently, Debian tries to use the cdc_ncm driver with the RTL8156BG, which fails without useful error. (ifup says the interface doesn't exist, neither systemd nor dmesg log anything notable, ip addr reports a mac address.) I think it's

Bug#971881: gnome-shell: cursor disappearing

Package: gnome-shell Version: 3.38.0-2 Severity: normal X-Debbugs-Cc: ja...@ivyleav.es GPU: Radeon RX 580 Series (POLARIS10, DRM 3.38.0, 5.8.0-2-amd64, LLVM 10.0.1) Driver: amdgpu I built this computer a few weeks ago, and the cursor has been glitching the entire time (trails, bounding boxes).

Bug#944104: Please install binary to /usr/bin

On Mon, Nov 4, 2019, at 07:04, Dmitry Smirnov wrote: > Package: conmon > Version: 2.0.2-1 > Severity: normal > > "conmon" installs its executable to "/usr/libexec/podman/conmon" > which is not where executable should be in Debian. > > Please ensure FHS compliance. > > Why not

Bug#930781: python3-socks: Deprecation warning emitted on import

Package: python3-socks Version: 1.6.8+dfsg-1 Severity: normal Dear Maintainer, PySocks 1.6.8 has a deprecated import and a warning is emitted on import. This is triggered by importing requests, an extremely common HTTP library. It has been fixed in upstream 1.7.0 This happens for any software

Bug#894245: Salt, Tornado Incompatibility, and ZMQ Timeline

With the acceptance of pyzmq 17 into unstable and testing, this should be fixed. However, further problems have since been revealed; see below for further information. On Wed, May 2, 2018 at 11:34 AM, Jamie Bliss <jamie.bl...@astro73.com> wrote: > > Hokay, so, > > Both #89381

Bug#893817: Satl, Tornado incompatibility, and ZMQ Timeline

Hokay, so, Both #893817 and #896921 fall into the category "Tornado 5 incompatibility". Thomas's #893817 is specifically a ZeroMQ/Tornado 5 incompatibility which has since been fixed, but doing so revealed my #896921. To explain: * February 10: ZeroMQ release pyzmq 17.0.0 to PyPI * March 22:

Bug#896921: salt-minion does not start: TypeError: add_accept_handler() got an unexpected keyword argument 'io_loop'

Package: salt-minion Version: 2017.7.4+dfsg1-1 salt-minion in testing is no longer able to start due to API bugs: # salt-minion -l debug [DEBUG ] Reading configuration from /etc/salt/minion [DEBUG ] Including configuration from '/etc/salt/minion.d/_schedule.conf' [DEBUG ] Reading

Bug#760343: Python3 Package?

Thanks for getting this into jessie. I noticed there isn't a a python3-protobuf package to go with the python-protobuf package. Since 2.6.0 added Python 3 support, shouldn't this be available?