Bug#1009889: bind9 depends on too old libuv1 package
Package: bind9 Version: 1:9.16.27-1~deb11u1 I've started to upgrading stretch to bullseye, and noticed that bind9 depends on libuv1 (>= 1.4.2) which is rather old. It causes named[22885]: udp.c:229: fatal error: named[22885]: udp.c:229: fatal error: uv_udp_init_ex failed: invalid argument named[22885]: udp.c:229: fatal error: uv_udp_init_ex failed: invalid argument named[22885]: uv_udp_init_ex failed: invalid argument named[22885]: exiting (due to fatal error in library) ...because of old libuv1=1.9.1-3. It's still newer than the recommended 1.4.2 but it's not enough. Please refresh the dependencies of bind9 package with libuv1 (>= 1.40.0-2)
Bug#925581: impossible to scroll in mate-panel
Package: libgtk-3-0 Version: 3.24.5-1 It's impossible to select new keyboard layout, due to can't scroll in mate-keyboard-preferences . It is a known bug discussed at: https://github.com/mate-desktop/mate-panel/issues/920 The bug was fixed in gtk 3.24.6 with this patch: https://gitlab.gnome.org/GNOME/gtk/commit/1d4eac211c09624d29b9309e2b92173f7477a9b7 Please backport this patch for 3.24.5 before first Buster release.
Bug#893237: spacefm: failed postrm script on upgrade
Package: spacefm Version: 1.0.6-1 Severity: normal Dear Maintainer, When I'm trying to update spacefm from 1.0.5 to 1.0.6, there is an error: postrm called with unknown argument `upgrade' dpkg: warning: old spacefm package post-removal script subprocess returned error exit status 1 dpkg: trying script from the new package instead ... postrm called with unknown argument `failed-upgrade' It is always failed on upgrade, because `upgrade` is interpreted as unknown parameter and generates `exit 1` code instantly. I could fix it by myself with adding these line to spacefm.postrm: upgrade) #do nothing true ;; -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (303, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-rc5-debcfg+uksm+nodbg+slub-sandy (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages spacefm depends on: ii desktop-file-utils0.23-2 ii e2fsprogs 1.44.0-1 ii libc6 2.27-2 pn libcairo2 pn libffmpegthumbnailer4v5 pn libgdk-pixbuf2.0-0 ii libglib2.0-0 2.55.2-1+nomount+nohard~tecra pn libgtk2.0-0 pn libpango-1.0-0 pn libpangocairo-1.0-0 pn libstartup-notification0 pn libudev1 pn libx11-6 ii shared-mime-info 1.9-2 ii spacefm-common1.0.6-1 Versions of packages spacefm recommends: ii udisks2 2.7.6-1+nosysd+nolvm~tecra Versions of packages spacefm suggests: ii dbus1.13.0-3+nosysd+nose+noapp~tecra ii eject 2.1.5+deb1+cvs20081104-13.2 ii gksu2.0.2-9+b1 pn ktsuss ii lsof4.89+dfsg-0.1 pn sshfs pn udevil ii wget1.19.4-1+libre~tecra -- no debconf information
Bug#892825: xxkb doesn't search for a new system tray if one was closed
Package: xxkb Version: 1.11-2.1+b2 Severity: normal Dear Maintainer, When I reload icewm 1.4.3.0~pre with `icewm -r` or `killall -HUP icewm`, then xxkb is still running but it disappeared from system tray. Icewm developers told me it's xxkb's fault, because sbxkb or fbxkb can redraw themselves after reloading icewm (with the new internal systemtray). -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (303, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-rc4-debcfg+uksm+nodbg+slub-sandy (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages xxkb depends on: ii libc6 2.27-1 pn libx11-6 pn libxext6 pn libxpm4 pn libxt6 xxkb recommends no packages. xxkb suggests no packages. -- no debconf information
Bug#855863: libfltk1.3 doesn't depend on xcursors
Package: libfltk1.3 Version: 1.3.4-2 I'm using xtigervncviewer, and cursor doesn't changing based on remote desktop. It is a known bug with Debian, discussed at: https://github.com/TigerVNC/tigervnc/issues/351 When i manually recompiled libfltk1.3 with --enable-xcursor everything goes to normal, cursor is changing its shape. Please include this parameter in debian/rules on further builds.
