Bug#1071988: radicale: After upgrade, radicale fails to serve calendar: An exception occurred during GET request

[Ralf Jung]

Package: radicale
Version: 3.2.0-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

after upgrading radicale, my devices are no longer able to access my calendar. 
The same calendar worked perfectly fine before the upgrade.
I am seeing errors like this in the log:

Mai 27 08:48:39 r-ethtop radicale[313128]: [313128/Thread-15 
(process_request_thread)] [ERROR] An exception occurred during PROPFIND request 
on '/ralfj/kalender.cal/': Failed to load item 
'87a651b3-153b-46e5-bd26-d9fa5beb21b8.ics' in 'ralfj/kalender.cal': At line 32: 
Failed to parse line:  \n   

Mai 27 08:49:29 r-ethtop radicale[313128]: [313128/Thread-18 
(process_request_thread)] [ERROR] An exception occurred during PROPFIND request 
on '/ralfj/kalender.cal/': Failed to load item 
'87a651b3-153b-46e5-bd26-d9fa5beb21b8.ics' in 'ralfj/kalender.cal': At line 32: 
Failed to parse line:  \n   

Mai 27 08:49:41 r-ethtop radicale[313128]: [313128/Thread-19 
(process_request_thread)] [ERROR] An exception occurred during PROPFIND request 
on '/ralfj/kalender.cal/': Failed to load item 
'87a651b3-153b-46e5-bd26-d9fa5beb21b8.ics' in 'ralfj/kalender.cal': At line 32: 
Failed to parse line:  \n   


Looks like I now have to try to manually repair the internal data storage, or 
something like that.
This calendar was only ever managed by radicale itself, so if past versions of 
radicale created invalid calendar entries
then future versions shouldn't make that the admin's problem.

Kind regards,
Ralf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.12-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages radicale depends on:
ii  adduser3.137
ii  init-system-helpers1.66
ii  python33.11.8-1
ii  python3-radicale   3.2.0-1
ii  sysvinit-utils [lsb-base]  3.09-1

Versions of packages radicale recommends:
ii  ssl-cert  1.1.2

Versions of packages radicale suggests:
pn  apache2 
pn  apache2-utils   
pn  libapache2-mod-proxy-uwsgi  
ii  python3-bcrypt  3.2.2-1
ii  python3-passlib 1.7.4-4
pn  uwsgi   
pn  uwsgi-plugin-python3

-- Configuration Files:
/etc/radicale/config changed [not included]
/etc/radicale/rights changed [not included]

-- no debconf information

Bug#1070863: inkscape: "Import Web Image" fails with ModuleNotFoundError: No module named 'appdirs'

[Ralf Jung]

Package: inkscape
Version: 1.2.2-2+b3
Severity: normal

Dear Maintainer,

to reproduce, simply click File - Import Web Image. I then get an error dialog 
showing
a Python exception:

Traceback (most recent call last):
  File "/usr/share/inkscape/extensions/other/clipart/import_web_image.py", line 
35, in 
from appdirs import user_cache_dir
ModuleNotFoundError: No module named 'appdirs'

Looks like maybe a dependency on python3-appdirs is missing?
Once I install that, I get another error about importing 'cachecontrol'.
After also installing python3-cachecontrol, the import web window finally 
appears.

Kind regards,
Ralf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.15-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages inkscape depends on:
ii  lib2geom1.2.0  1.2.2-3
ii  libatkmm-1.6-1v5   2.28.4-1
ii  libboost-filesystem1.83.0  1.83.0-2+b2
ii  libc6  2.37-15
ii  libcairo-gobject2  1.18.0-1+b1
ii  libcairo2  1.18.0-1+b1
ii  libcairomm-1.0-1v5 1.14.5-1
ii  libcdr-0.1-1   0.1.7-1
ii  libfontconfig1 2.15.0-1.1
ii  libfreetype6   2.13.2+dfsg-1+b1
ii  libgc1 1:8.2.6-1
ii  libgcc-s1  14-20240201-3
ii  libgdk-pixbuf-2.0-02.42.10+dfsg-3+b1
ii  libglib2.0-0   2.78.4-1
ii  libglibmm-2.4-1v5  2.66.6-2+b1
ii  libgomp1   14-20240201-3
ii  libgsl27   2.7.1+dfsg-6+b1
ii  libgspell-1-2  1.12.2-1+b1
ii  libgtk-3-0 3.24.41-1
ii  libgtkmm-3.0-1v5   3.24.8-2+b1
ii  libharfbuzz0b  8.3.0-2
ii  libjpeg62-turbo1:2.1.5-2+b2
ii  liblcms2-2 2.14-2+b1
ii  libmagick++-6.q16-98:6.9.12.98+dfsg1-5+b1
ii  libpango-1.0-0 1.52.0+ds-1
ii  libpangocairo-1.0-01.52.0+ds-1
ii  libpangoft2-1.0-0  1.52.0+ds-1
ii  libpangomm-1.4-1v5 2.46.4-1
ii  libpng16-161.6.43-1
ii  libpoppler-glib8   22.12.0-2+b1
ii  libpoppler126  22.12.0-2+b1
ii  libpotrace01.16-2+b1
ii  libreadline8   8.2-3+b1
ii  librevenge-0.0-0   0.0.5-3
ii  librsvg2-common2.54.7+dfsg-2
ii  libsigc++-2.0-0v5  2.12.1-1
ii  libsoup2.4-1   2.74.3-3
ii  libstdc++6 14-20240201-3
ii  libvisio-0.1-1 0.1.7-1+b3
ii  libwpg-0.3-3   0.3.4-3
ii  libx11-6   2:1.8.7-1
ii  libxml22.9.14+dfsg-1.3+b2
ii  libxslt1.1 1.1.35-1
ii  python33.11.6-1
ii  zlib1g 1:1.3.dfsg-3+b1

Versions of packages inkscape recommends:
ii  aspell   0.60.8.1-1+b1
ii  fig2dev  1:3.2.9-3
ii  imagemagick  8:6.9.12.98+dfsg1-5+b1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.12.98+dfsg1-5+b1
ii  libimage-magick-perl 8:6.9.12.98+dfsg1-5
ii  libwmf-bin   0.2.13-1.1
ii  python3-cssselect1.2.0-2
ii  python3-lxml 5.1.0-1
ii  python3-numpy1:1.24.2-2
ii  python3-scour0.38.2-4.1

Versions of packages inkscape suggests:
pn  dia   
pn  inkscape-tutorials
pn  libsvg-perl   
pn  pstoedit  
ii  python3-packaging 24.0-1
pn  python3-uniconvertor  
ii  ruby  1:3.1

-- no debconf information

Bug#767756: glibc: Consider providing a libc build compiled with -fno-omit-frame-pointer to help with profiling

[Ralf Jung]

Hi all,

Fedora and Ubuntu [1] have now enabled frame pointers on amd64 by default, 
providing a great profiling experience out-of-the-box. I think it may be time 
for Debian to reconsider its position here; the performance overhead is very 
small and meanwhile this lack of frame pointers is preventing other, much more 
significant performance improvements by making it hard or impossible to properly 
profile applications.


[1]: 
https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-pointers-by-default


Kind regards,
Ralf

Bug#1064103: qt5-gtk-platformtheme: Qt and KDE applications look pretty bad on a Gnome desktop (even with qt5-gtk-platformtheme installed)

[Ralf Jung]

Package: qt5-gtk-platformtheme
Version: 5.15.10+dfsg-6
Severity: normal

Dear Maintainer,

the default experience of starting a Qt or KDE application in a Gnome desktop on
Debian is not great: the default widget style is very different from what one
sees in a KDE desktop (and it's not very pretty either), and the cursor is way
too big. I will attach a screenshot demonstrating the problem (if reportbug lets
me). This is despite installing qt5-gtk-platformtheme.

So far, I have managed to partially work around this:
- I have installed qt5ct
- I have edited my ~/.profile to set QT_QPA_PLATFORMTHEME=qt5ct
- I have selected the "Breeze" theme in qt5ct

This helps a lot, but few non-experts are going to be able to find these steps.

And even after all these steps, the cursor is still way too big when moving 
into Qt or KDE windows.
(I originally reported this as a KDE bug: 
https://bugs.kde.org/show_bug.cgi?id=480272,
but I was told that I should report this against the distro.)

Kind regards,
Ralf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.15-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qt5-gtk-platformtheme depends on:
ii  libc6  2.37-15
ii  libglib2.0-0   2.78.3-2
ii  libgtk-3-0 3.24.41-1
ii  libpango-1.0-0 1.51.0+ds-4
ii  libqt5core5a [qtbase-abi-5-15-10]  5.15.10+dfsg-6
ii  libqt5dbus55.15.10+dfsg-6
ii  libqt5gui5 5.15.10+dfsg-6
ii  libstdc++6 14-20240201-3
ii  libx11-6   2:1.8.7-1

qt5-gtk-platformtheme recommends no packages.

qt5-gtk-platformtheme suggests no packages.

-- no debconf information

Bug#1055757: webext-browserpass: extension shows warning in browser: "Update native host app"

[Ralf Jung]

Package: webext-browserpass
Version: 3.7.2-1+b13
Severity: normal

Dear Maintainer,

When activating the extension in Firefox, I now get a warning in the "pass" 
menu. It says in red text "Update native host app".

The package here in Debian has not been updated in over 2 years, so I assume 
this simply needs the latest upstream version to be packaged.

Kind regards,
Ralf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-3-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages webext-browserpass depends on:
ii  fonts-open-sans  1.11-2
ii  libc62.37-12

Versions of packages webext-browserpass recommends:
pn  firefox | firefox-esr | chromium  

webext-browserpass suggests no packages.

-- no debconf information

Bug#1055389: libgccjit-12-dev: gccjit is not added to the usual library search paths

[Ralf Jung]

Package: libgccjit-12-dev
Version: 12.3.0-9
Severity: normal

Dear Maintainer,

when installing libgccjit-12-dev, I'd expect to be able to write applications 
that link against gccjit.
(The GCC codegen backend for the Rust compiler is one example for such an 
application.)
However, strangely, that does not work: instead I get a linker error telling me 
that the library was not found.

The reason for this is that libgccjit.so is located in 
/usr/lib/gcc/x86_64-linux-gnu/12, rather than /usr/lib/x86_64-linux-gnu/.
It would be great if a symlink could be added to the usual linker locations, so 
that people linking against gccjit
do not have to resort to ugly work-arounds such as `sudo ln -s 
/usr/lib/gcc/x86_64-linux-gnu/12/libgccjit.so 
/usr/lib/x86_64-linux-gnu/libgccjit.so`.

Kind regards,
Ralf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgccjit-12-dev depends on:
ii  gcc-12-base  12.3.0-9
ii  libgccjit0   13.2.0-4

libgccjit-12-dev recommends no packages.

Versions of packages libgccjit-12-dev suggests:
pn  libgccjit-12-dbg  

-- no debconf information

Bug#1050413: etckeeper: Verbose cron job leads to daily email: "Auto packing the repository in background for optimum performance"

[Ralf Jung]

Package: etckeeper
Version: 1.18.20-1
Severity: normal

Dear Maintainer,

since very recently, etckeeper started to become rather verbose, and I now get 
a daily email from the cronjob:

/etc/cron.daily/etckeeper:
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.

Since this does not indicate any kind of error, it would be better not to 
bother the admin with such emails.

Kind regards,
Ralf


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-2-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages etckeeper depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  git1:2.40.1-1

Versions of packages etckeeper recommends:
ii  cron [cron-daemon]  3.0pl1-163

Versions of packages etckeeper suggests:
ii  sudo  1.9.14p2-1

-- debconf information:
  etckeeper/purge: true

Bug#1049962: closed by Stefano Rivera (Re: Bug#1049962: python3-pip: Misleading error message on "pip install --user")

[Ralf Jung]

I still think the text and definitely the README.venv could be written in a less 
confusing way. For instance, README.venv starts out saying



It is recommended to let Debian's package managers manage Python packages in
/usr/lib/ and /usr/share/.


So for my case ("pip install --user"), obviously this document is not relevant, 
since indeed I do want to let Debian manage the packages in /usr. Nothing in 
that file even mentions ~/.local.


; Ralf

Bug#1049962: python3-pip: Misleading error message on "pip install --user"

[Ralf Jung]

Package: python3-pip
Version: 23.2+dfsg-1
Severity: normal

Dear Maintainer,

When I try to install something to my user directory, I get a confusing error 
message:

error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.

If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.

If you wish to install a non-Debian packaged Python application,
it may be easiest to use pipx install xyz, which will manage a
virtual environment for you. Make sure you have pipx installed.

See /usr/share/doc/python3.11/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation 
or OS distribution provider. You can override this, at the risk of breaking 
your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

This is confusing because the error, and the README.venv file, all talk about 
system-wide installation (in /usr). But I am not trying to do a system-wide 
installation!
I just want a user-wide installation. Somehow that leads to the same error 
message though.

Kind regards,
Ralf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-2-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-pip depends on:
ii  ca-certificates 20230311
ii  python3 3.11.4-5
ii  python3-distutils   3.11.4-1
ii  python3-setuptools  68.0.0-1
ii  python3-wheel   0.38.4-2

Versions of packages python3-pip recommends:
ii  build-essential  12.10
ii  python3-dev  3.11.4-5

python3-pip suggests no packages.

-- no debconf information

Bug#1049349: valgrind: DWARF5 not supported: "Possibly corrupted debuginfo file"

[Ralf Jung]

Package: valgrind
Version: 1:3.19.0-1
Severity: normal

Dear Maintainer,

trying to use valgrind on programs that contain DWARF5 debuginfo leads to an 
error message:

==92495== Valgrind: debuginfo reader: Possibly corrupted debuginfo file.
==92495== Valgrind: I can't recover.  Giving up.  Sorry.

This is a problem, since e.g. for over a year now, more and more Rust programs 
contain DWARF5 debuginfo (see ).
They all cannot be debugged or profiled with valgrind.

Reportedly, valgrind 3.20 improves the situation greatly, but unfortunately 
that only has an experimental package available right now.

Kind regards,
Ralf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-2-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages valgrind depends on:
ii  libc6  2.37-7
ii  libc6-dbg  2.37-7

Versions of packages valgrind recommends:
ii  gdb   13.2-1
ii  valgrind-dbg  1:3.19.0-1

Versions of packages valgrind suggests:
pn  alleyoop  
pn  kcachegrind   
pn  valgrind-mpi  
pn  valkyrie  

-- no debconf information

Bug#1039893: steam-installer: Dangling symlink in package: /usr/share/pixmaps/steam_tray_mono.png, breaks tray icon

[Ralf Jung]

Hi,

On 26.07.23 13:37, Simon McVittie wrote:

On Thu, 29 Jun 2023 at 11:53:53 +0200, Ralf Jung wrote:

this package ships a symlink /usr/share/pixmaps/steam_tray_mono.png that points 
to
../icons/hicolor/48x48/apps/steam_tray_mono.png. However, that target file does 
not exist:

...

As a consequence of this, the systray icon for steam is broken.


Broken in what environment? What component are you using to display tray
icons? It's working OK in GNOME with gnome-shell-extension-appindicator,
but there are several code paths that a tray icon could potentially
go through (KDE status notifier, Ubuntu appindicators, legacy Xembed,
and probably more).


I am using gnome-shell-extension-appindicator and it didn't use to work here 
when I made the bugreport.
However I have since then done a big apt upgrade and that must have changed 
something, because when I now tried it again it actually did work. :)

(But the nextcloud icon is broken now. *sigh* )

The dangling symlink should probably still be removed, though.



We are no longer able to ship Valve's proprietary steam_tray_mono.png
in /usr, in order to make steam-installer a pure "installer" package
that can be in contrib. When a user runs /usr/games/steam, the actual
proprietary files get downloaded, and a symbolic link to the icon is
created in ~/.local/share/icons/hicolor/48x48/apps/steam_tray_mono.png
(but this happens in an unprivileged process with no access to /usr).

As a first attempt at fixing this, I'm going to remove the dangling
symlink, which will hopefully result in the icon being loaded from
~/.local/share/icons/hicolor/48x48/apps/steam_tray_mono.png. If that
isn't successful, please reopen the bug and provide more details of your
environment: it's possible that for some desktop environments it will need
a symlink in some other location like ~/.icons or ~/.local/share/icons.


Sounds good, thanks!
Ralf

Bug#1041765: nextcloud-desktop: Tray icon no longer works with gnome + indicator extension

[Ralf Jung]

Package: nextcloud-desktop
Version: 3.9.0-1
Severity: normal

Dear Maintainer,

since installing nextcloud-desktop 3.9, the systray icon no longer works as 
expected in Gnome (with the AppIndicator extension):
it shows shows three white dots instead of the nextcloud icon.
Nextcloud shows everything as fully synced, so I am fairly sure that these are 
the three dots Gnome shows when it cannot find the icon.
However, I am not sure why the icon can no longer be found -- it used to work 
fine before I did a big "apt upgrade" yesterday.

Here's another report of the same problem, with a screenshot:
https://forum.manjaro.org/t/nextcloud-client-icon-is-not-showing-correctly/138545

Kind regards,
Ralf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_DIE, TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nextcloud-desktop depends on:
ii  libc6  2.37-5
ii  libcloudproviders0 0.3.1-2
ii  libgcc-s1  13.1.0-6
ii  libglib2.0-0   2.74.6-2
ii  libkf5archive5 5.107.0-1
ii  libnextcloudsync0  3.9.0-1
ii  libqt5core5a   5.15.8+dfsg-12
ii  libqt5dbus55.15.8+dfsg-12
ii  libqt5gui5 5.15.8+dfsg-12
ii  libqt5keychain10.14.1-1
ii  libqt5network5 5.15.8+dfsg-12
ii  libqt5qml5 5.15.8+dfsg-3
ii  libqt5quick5   5.15.8+dfsg-3
ii  libqt5quickcontrols2-5 5.15.8+dfsg-2
ii  libqt5sql5-sqlite  5.15.8+dfsg-12
ii  libqt5svg5 5.15.8-3
ii  libqt5webenginecore5   5.15.13+dfsg-1~deb12u1
ii  libqt5webenginewidgets55.15.13+dfsg-1~deb12u1
ii  libqt5widgets5 5.15.8+dfsg-12
ii  libstdc++6 13.1.0-6
ii  nextcloud-desktop-common   3.9.0-1
ii  nextcloud-desktop-l10n 3.9.0-1
ii  qml-module-qt-labs-platform5.15.8+dfsg-2
ii  qml-module-qtgraphicaleffects  5.15.8-2
ii  qml-module-qtqml   5.15.8+dfsg-3
ii  qml-module-qtqml-models2   5.15.8+dfsg-3
ii  qml-module-qtquick-controls2   5.15.8+dfsg-2
ii  qml-module-qtquick-dialogs 5.15.8-2
ii  qml-module-qtquick-layouts 5.15.8+dfsg-3
ii  qml-module-qtquick-window2 5.15.8+dfsg-3
ii  qml-module-qtquick25.15.8+dfsg-3

Versions of packages nextcloud-desktop recommends:
ii  nextcloud-desktop-doc  3.9.0-1

nextcloud-desktop suggests no packages.

-- no debconf information

Bug#1039893: steam-installer: Dangling symlink in package: /usr/share/pixmaps/steam_tray_mono.png, breaks tray icon

[Ralf Jung]

Package: steam-installer
Version: 1:1.0.0.78~ds-2
Severity: normal

Dear Maintainer,

this package ships a symlink /usr/share/pixmaps/steam_tray_mono.png that points 
to
../icons/hicolor/48x48/apps/steam_tray_mono.png. However, that target file does 
not exist:

$ dpkg -L steam-installer | grep png
/usr/share/icons/hicolor/16x16/apps/steam.png
/usr/share/icons/hicolor/24x24/apps/steam.png
/usr/share/icons/hicolor/256x256/apps/steam.png
/usr/share/icons/hicolor/32x32/apps/steam.png
/usr/share/icons/hicolor/48x48/apps/steam.png
/usr/share/pixmaps/steam.png
/usr/share/pixmaps/steam_tray_mono.png

As a consequence of this, the systray icon for steam is broken.

Kind regards,
Ralf

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages steam-installer depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  steam-libs 1:1.0.0.78~ds-2
ii  steam-libs-i3861:1.0.0.78~ds-2
ii  zenity 3.44.0-1

steam-installer recommends no packages.

steam-installer suggests no packages.

Versions of packages steam-libs depends on:
ii  ca-certificates  20230311
ii  curl 7.88.1-10
ii  file 1:5.44-3
ii  libc62.36-9
ii  libcrypt11:4.4.33-2
ii  libgcc-s1 [libgcc1]  12.2.0-14
ii  libgl1   1.6.0-1
ii  libgl1-mesa-dri  22.3.6-1+deb12u1
ii  libgpg-error01.46-1
ii  libstdc++6   12.2.0-14
ii  libudev1 252.6-1
ii  libva-x11-2  2.18.0-1
ii  libva2   2.18.0-1
ii  libxcb-dri3-01.15-1
ii  libxcb1  1.15-1
ii  libxi6   2:1.8-1+b1
ii  libxinerama1 2:1.1.4-3
ii  xz-utils 5.4.1-0.2

Versions of packages steam-libs recommends:
ii  fontconfig 2.14.1-4
ii  fonts-liberation   1:1.07.4-11
ii  gnome-terminal [x-terminal-emulator]   3.46.8-1
ii  i965-va-driver [va-driver] 2.4.1+dfsg1-1
ii  intel-media-va-driver [va-driver]  23.1.2+dfsg1-1
ii  konsole [x-terminal-emulator]  4:22.12.3-1
ii  libasound2-plugins 1.2.7.1-1
ii  libegl11.6.0-1
ii  libexpat1  2.5.0-1
ii  libfontconfig1 2.14.1-4
ii  libgbm122.3.6-1+deb12u1
ii  libsdl2-2.0-0  2.26.5+dfsg-1
ii  libva-drm2 2.18.0-1
ii  libva-glx2 2.18.0-1
ii  libx11-6   2:1.8.4-2
ii  libx11-xcb12:1.8.4-2
ii  libxau61:1.0.9-1
ii  libxcb-dri2-0  1.15-1
ii  libxcb-glx01.15-1
ii  libxcb-present01.15-1
ii  libxcb-sync1   1.15-1
ii  libxdamage11:1.1.6-1
ii  libxdmcp6  1:1.1.2-3
ii  libxext6   2:1.3.4-1+b1
ii  libxfixes3 1:6.0.0-2
ii  libxss11:1.2.3-1
ii  libxxf86vm11:1.1.4-1+b2
ii  mesa-va-drivers [va-driver]22.3.6-1+deb12u1
ii  mesa-vulkan-drivers22.3.6-1+deb12u1
ii  steam-devices  1:1.0.0.78~ds-2
ii  va-driver-all  2.18.0-1
ii  xdg-desktop-portal 1.16.0-2
ii  xdg-desktop-portal-gnome [xdg-desktop-portal-backend]  43.1-2
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]1.14.1-1
ii  xdg-utils  1.1.3-4.1
ii  xterm [x-terminal-emulator]379-1
ii  zenity 3.44.0-1

Versions of packages steam-libs suggests:
pn  libudev0
pn  nvidia-driver-libs  
pn  nvidia-vulkan-icd   
ii  pipewire0.3.65-3

Versions of packages steam-libs:i386 depends on:
ii  ca-certificates  20230311
ii  curl 7.88.1-10
ii  file 1:5.44-3
ii  

Bug#1037199: evince: Cannot open links in browser due to Apparmor profile

[Ralf Jung]

Package: evince
Version: 43.1-2+b1
Severity: normal

Dear Maintainer,

clicking a link to open things in my browser works in basically all 
applications, except evince. It took me a long whole to realize that this is 
due to apparmor:

Jun 07 15:53:03 r-ethtop audit[1165140]: AVC apparmor="DENIED" operation="exec" 
profile="/usr/bin/evince" name="/home/r/bin/firefox" pid=1165140 
comm="gio-launch-desk" requested_mask="x" denied_mask="x" fsuid=1000 ouid=1000
Jun 07 15:53:03 r-ethtop kernel: audit: type=1400 audit(1686145983.857:133): 
apparmor="DENIED" operation="exec" profile="/usr/bin/evince" 
name="/home/r/bin/firefox" pid=1165140 comm="gio-launch-desk" 
requested_mask="x" denied_mask="x" fsuid=1000 ouid=1000

Looks like this would happen to anyone who set their default browser to 
something they installed themselves as a user rather than using a system 
package.
That's quite surprising and most people will probably never figure out why 
things are broken.

I am still trying to figure out how to work around this, Apparmor seems super 
complicated and I don't have the time to learn it just to fix clicking links in 
a PDF... I'll probably end up just disabling it as that seems like the only 
thing that's reasonably easy to do. :/

Kind regards,
Ralf


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  evince-common43.1-2
ii  gsettings-desktop-schemas43.0-1
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libevdocument3-4 43.1-2+b1
ii  libevview3-3 43.1-2+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgnome-desktop-3-2043.2-2
ii  libgtk-3-0   3.24.37-2
ii  libhandy-1-0 1.8.1-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libsecret-1-00.20.5-3
ii  shared-mime-info 2.2-1

Versions of packages evince recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.14.6-1

Versions of packages evince suggests:
ii  gvfs 1.50.3-1
pn  nautilus-sendto  
ii  poppler-data 0.4.12-1
pn  unrar

-- no debconf information

Bug#1032517: nginx settings deleted on upgrade

[Ralf Jung]

Package: nginx
Version: 1.22.1-7
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

last weekend I did an "apt upgrade" of my system as usual, asking apt to prune 
configuration files for packages that are being uninstalled.
Now I realize that my nginx stopped working, and it turns out its configuration 
files are just completely gone.
Look like the recent package reorganization went wrong and actually deletes 
configuration under certain conditions -- that's pretty bad.
Package updates shouldn't cause a loss of configuration files, even when 
pruning packages that are not present any more.

Kind regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nginx depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  iproute2   6.1.0-1
ii  libc6  2.36-8
ii  libcrypt1  1:4.4.33-2
ii  libpcre2-8-0   10.42-1
ii  libssl33.0.8-1
ii  zlib1g 1:1.2.13.dfsg-1

nginx recommends no packages.

Versions of packages nginx suggests:
ii  fcgiwrap   1.1.0-14
pn  nginx-doc  
ii  ssl-cert   1.1.2

-- Configuration Files:
/etc/nginx/fastcgi.conf [Errno 2] No such file or directory: 
'/etc/nginx/fastcgi.conf'
/etc/nginx/fastcgi_params [Errno 2] No such file or directory: 
'/etc/nginx/fastcgi_params'
/etc/nginx/koi-utf [Errno 2] No such file or directory: '/etc/nginx/koi-utf'
/etc/nginx/koi-win [Errno 2] No such file or directory: '/etc/nginx/koi-win'
/etc/nginx/mime.types [Errno 2] No such file or directory: 
'/etc/nginx/mime.types'
/etc/nginx/nginx.conf [Errno 2] No such file or directory: 
'/etc/nginx/nginx.conf'
/etc/nginx/proxy_params [Errno 2] No such file or directory: 
'/etc/nginx/proxy_params'
/etc/nginx/scgi_params [Errno 2] No such file or directory: 
'/etc/nginx/scgi_params'
/etc/nginx/sites-available/default [Errno 2] No such file or directory: 
'/etc/nginx/sites-available/default'
/etc/nginx/snippets/fastcgi-php.conf [Errno 2] No such file or directory: 
'/etc/nginx/snippets/fastcgi-php.conf'
/etc/nginx/snippets/snakeoil.conf [Errno 2] No such file or directory: 
'/etc/nginx/snippets/snakeoil.conf'
/etc/nginx/uwsgi_params [Errno 2] No such file or directory: 
'/etc/nginx/uwsgi_params'
/etc/nginx/win-utf [Errno 2] No such file or directory: '/etc/nginx/win-utf'

-- debconf information:
  nginx/log-symlinks:

Bug#1030329: Proposing NMU

[Ralf Jung]

Hi Sergei,

Sure, please go ahead and thanks!
Feel free to add this patch in  as well.

; Ralf

On 04.02.23 14:17, Sergei Golovan wrote:

Hi Ralf,

If you don't mind, I'd suggest doing NMU for this bug. I've tested
myself, simply adding pipewire-pulse to the dependencies list allows
osspd to work with pipewire (in the modern Gnome desktop pipewire is
installed by default and cannot be easily replaced with pulseaudio).

The diff for the proposed NMU is attached.

Cheers!

Bug#1024001: flatpak should Recommend: xdg-desktop-portal-gtk (without alternative)

[Ralf Jung]

Package: flatpak
Version: 1.14.0-2
Severity: normal

Dear Maintainer,

GTK3 and/or GTK4 applications running inside flatpak on a Wayland host need the
xdg-desktop-portal-gtk package to be installed or else font rendering will look
terrible (see https://github.com/flatpak/flatpak/issues/2861). So the flatpak
package should Recommend: xdg-desktop-portal-gtk. Right now it recommends
'xdg-desktop-portal-gtk | xdg-desktop-portal-packend', which in my case is
satisfied by xdk-desktop-portal-kde, but that is not enough to get proper font
rendering.

Kind regards,
Ralf

-- Package-specific info:
Permissions of /usr/bin/bwrap:
-rwxr-xr-x 1 root root 72080 Nov  7 18:57 /usr/bin/bwrap
/etc/sysctl.d/*-bubblewrap.conf:
cat: '/etc/sysctl.d/*-bubblewrap.conf': No such file or directory
/usr/lib/sysctl.d/50-bubblewrap.conf:
# Enable unprivileged creation of new user namespaces in older Debian
# kernels.
#
# If this is not desired, copy this file to
# /etc/sysctl.d/50-bubblewrap.conf and change the value of this parameter
# to 0, then use dpkg-statoverride to make /usr/bin/bwrap setuid root.
#
# For more details see https://deb.li/bubblewrap or
# /usr/share/doc/bubblewrap/README.Debian
kernel.unprivileged_userns_clone=1
/proc/sys/kernel/unprivileged_userns_clone:
1
/proc/sys/user/max_cgroup_namespaces:
127534
/proc/sys/user/max_ipc_namespaces:
127534
/proc/sys/user/max_mnt_namespaces:
127534
/proc/sys/user/max_net_namespaces:
127534
/proc/sys/user/max_pid_namespaces:
127534
/proc/sys/user/max_time_namespaces:
127534
/proc/sys/user/max_user_namespaces:
127534
/proc/sys/user/max_uts_namespaces:
127534

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages flatpak depends on:
ii  adduser 3.129
ii  bubblewrap  0.7.0-1
ii  dbus [default-dbus-system-bus]  1.14.4-1
ii  fuse3   3.12.0-1
ii  libappstream4   0.15.5-1
ii  libarchive133.6.0-1
ii  libc6   2.36-4
ii  libcurl3-gnutls 7.86.0-1
ii  libdconf1   0.40.0-3
ii  libfuse3-3  3.12.0-1
ii  libgdk-pixbuf-2.0-0 2.42.9+dfsg-1
ii  libglib2.0-02.74.1-2
ii  libgpgme11  1.18.0-1
ii  libjson-glib-1.0-0  1.6.6-1
ii  libmalcontent-0-0   0.11.0-3
ii  libostree-1-1   2022.6-1+b1
ii  libpolkit-agent-1-0 122-1
ii  libpolkit-gobject-1-0   122-1
ii  libseccomp2 2.5.4-1+b2
ii  libsystemd0 252.1-1
ii  libxau6 1:1.0.9-1
ii  libxml2 2.9.14+dfsg-1+b1
ii  libzstd11.5.2+dfsg-1
ii  xdg-dbus-proxy  0.1.4-1

Versions of packages flatpak recommends:
ii  ca-certificates  20211016
ii  desktop-file-utils   0.26-1
ii  gtk-update-icon-cache3.24.34-3
ii  hicolor-icon-theme   0.17-2
ii  libpam-systemd   252.1-1
ii  p11-kit  0.24.1-1
ii  policykit-1  122-1
ii  polkitd  122-1
ii  shared-mime-info 2.2-1
ii  xdg-desktop-portal   1.15.0-2+b1
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.14.0-1
ii  xdg-desktop-portal-kde [xdg-desktop-portal-backend]  5.26.0-1
ii  xdg-user-dirs0.18-1

Versions of packages flatpak suggests:
ii  avahi-daemon0.8-6+b1
pn  malcontent-gui  

Versions of packages bubblewrap depends on:
ii  libc62.36-4
ii  libcap2  1:2.44-1
ii  libselinux1  3.4-1+b3

Versions of packages bubblewrap recommends:
ii  procps  2:3.3.17-7.1

-- no debconf information

Bug#1023928: evince: Incorrect 'desktopFileName' for wayland surface leads to missing icon in KDE Wayland session

[Ralf Jung]

Package: evince
Version: 43.0-1
Severity: minor

Dear Maintainer,

evince windows do not have a proper icon in a KDE Wayland session.
This is caused by the fact that the 'desktopFileName' of the Wayland surface is 
set to 'evince', when it should be 'org.gnome.Evince'. There is no 
`evince.desktop` so KDE cannot find an icon.
Other gnome applications have the expected 'desktopFileName' (I checked the 
calculator), so this seems to be something specific to evince.

I also reported this upstream at 
; it is hard to tell where 
the issue originates.

Kind regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  evince-common43.0-1
ii  gsettings-desktop-schemas43.0-1
ii  libatk1.0-0  2.46.0-3
ii  libc62.36-4
ii  libcairo-gobject21.16.0-6
ii  libcairo21.16.0-6
ii  libevdocument3-4 43.0-1
ii  libevview3-3 43.0-1
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.74.1-1
ii  libgnome-desktop-3-2043-2
ii  libgtk-3-0   3.24.34-3
ii  libhandy-1-0 1.8.0-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libsecret-1-00.20.5-3
ii  shared-mime-info 2.2-1

Versions of packages evince recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.14.4-1

Versions of packages evince suggests:
ii  gvfs 1.50.2-2
pn  nautilus-sendto  
ii  poppler-data 0.4.11-1
ii  unrar1:6.2.1-2

-- no debconf information

Bug#1023771: mumble: No icon for mumble window under KDE wayland

[Ralf Jung]

Package: mumble
Version: 1.3.4-1.1
Severity: minor

Dear Maintainer,

The subject pretty much says it all: when opening Mumble on a KDE wayland 
session, the window has no icon.
This means something is going wrong in associating the wayland surface with the 
mumble desktop file.

Looking at the surface properties, its desktopFileName is set to 
'net.sourceforge.mumble.mumble', so probably the desktop file needs to be 
renamed to match that.

Kind regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mumble depends on:
ii  libasound21.2.7.2-1
ii  libavahi-compat-libdnssd1 0.8-6+b1
ii  libc6 2.36-4
ii  libgcc-s1 12.2.0-9
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-1
ii  libprotobuf23 3.12.4-1+b5
ii  libpulse0 16.1+dfsg1-2+b1
ii  libqt5core5a  5.15.6+dfsg-2
ii  libqt5dbus5   5.15.6+dfsg-2
ii  libqt5gui55.15.6+dfsg-2
ii  libqt5network55.15.6+dfsg-2
ii  libqt5sql55.15.6+dfsg-2
ii  libqt5sql5-sqlite 5.15.6+dfsg-2
ii  libqt5svg55.15.6-2
ii  libqt5widgets55.15.6+dfsg-2
ii  libqt5xml55.15.6+dfsg-2
ii  libsndfile1   1.1.0-3+b1
ii  libspeechd2   0.11.4-1
ii  libspeex1 1.2.1-1
ii  libspeexdsp1  1.2.1-1
ii  libssl3   3.0.7-1
ii  libstdc++612.2.0-9
ii  libx11-6  2:1.8.1-2
ii  libxi62:1.8-1+b1
ii  lsb-release   12.0-1

mumble recommends no packages.

Versions of packages mumble suggests:
pn  mumble-server  
pn  speech-dispatcher  

-- no debconf information

Bug#907178: gimp-plugin-registry: resynthesizer not appearing in menu Filters/Enhance

[Ralf Jung]

Hi,

the version packaged in Debian seems to be the same that is offered for download 
on the gimp website.


This seems to be an upstream problem: Gimp 3 will be required for Python 3 
support, and Gimp 3 has been delayed ~forever -- Gimp 3 is the GTK 3 port, which 
is not even done yet and meanwhile Gnome is already being ported to GTK 4!


Kind regards,
Ralf

On 07.11.22 21:27, Ying-Chun Liu (PaulLiu) wrote:

Hi,

Yes, we ported that plugin to Python3.
However, gimp in Debian is too old.
There was a package called gimp-python which is python2 and got removed.
Thus right now in Debian we have to disable all python plugins temporarily.
We will bring those plugins back when gimp-python3 is available.

This is not a bug of this package. This should be a bug of gimp.

Yours,
Paul

Bug#1023331: pass: Needs wl-copy but there is no "Depends:"

[Ralf Jung]

Hi,


An "apt install wl-clipboard" fixes that. Looks like a missing dependency?


There's already a Recommends on "xclip | wl-clipboard", attempting to
express the fact that (a) only some pass functionality uses either
utility and pass is otherwise usable without it (I don't use the
clipboard functionality myself), and (b) pass uses one or the other
depending on whether you're using X or Wayland.  I certainly don't think
a Depends is necessary here, but you evidently missed the Recommends as
well.


The recommends is satisfied because I have xclip installed. The "|" doesn't 
really help when one switches from X11 to wayland (which means one still has all 
the X11 things installed).
In fact I assume most wayland users will have X11 installed, and the xclip 
alternative comes first here, so it is probably rather rare that this would 
actually end up installing wl-clipboard.



It's not entirely clear how to improve this without annoying some
constituencies of pass users with excess dependencies.  Maybe if it were
"Recommends: xclip, wl-clipboard" instead then it would be less likely
that people would miss the wl-clipboard recommendation?


Yeah it's not clear what the best solution is here... ideally you'd be able to 
say "if some wayland compositor is installed, also recommend wl-clipboard", but 
that is not something dpkg can express.


wl-clipboard has very few dependencies though -- libwayland-client0 is already a 
dependency of libgtk3 and libgtk4 and plasma-desktop. So yeah I think 
"Recommends: wl-clipboard" would probably make sense.


; Ralf

Bug#1023331: pass: Needs wl-copy but there is no "Depends:"

[Ralf Jung]

Package: pass
Version: 1.7.4-5
Severity: normal

Dear Maintainer,

when being run under Wayland, pass uses 'wl-copy' to copy things to the 
clipboard.
This leads to the following error on my system:

/usr/bin/pass: line 180: wl-copy: command not found

An "apt install wl-clipboard" fixes that. Looks like a missing dependency?

Kinds regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pass depends on:
ii  gnupg  2.2.40-1
ii  tree   2.0.4-1

Versions of packages pass recommends:
ii  git   1:2.35.1-1
ii  qrencode  4.1.1-1
ii  wl-clipboard  2.1.0-0.1+b1
ii  xclip 0.13-2

Versions of packages pass suggests:
ii  libxml-simple-perl  2.25-1
ii  perl5.36.0-4
pn  python  
ii  python3 3.10.6-1
ii  ruby1:3.0+3.1

-- no debconf information

Bug#1023296: plasma-workspace: ssh-agent not working in KDE Plasma Wayland session

[Ralf Jung]

Package: plasma-workspace
Version: 4:5.26.0-2
Severity: normal

Dear Maintainer,

when I start a KDE Plasma Wayland session, the ssh-agent is not working: 
attempting to load my SSH key into the agent (in Konsole via ssh-add) fails 
saying
"Could not open a connection to your authentication agent."

This is probably caused by the fact that the SSH_AUTH_SOCK env var is not set. 
(I am now setting it in my .bashrc to work around the issue.)
I have no idea how that env var is *supposed* to end up in the plasma session, 
but whatever mechanism is supposed to achieve that is not working.
I can see that ssh-agent comes with a systemd user service, which is setting 
the required variable in "dbus-update-activation-environment", so maybe KDE is 
somehow supposed to fetch that and that is not working?
Or maybe it's something else entirely. From feedback I got on IRC, it seems 
other distros have special ssh-agent scripts in /etc/xdg/plasma-workspace/env/, 
but I don't know if that is something standard.

Kind regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-workspace depends on:
ii  dbus-user-session [default-dbus-session-bus]1.14.4-1
ii  drkonqi 5.26.0-2
ii  frameworkintegration5.98.0-1
ii  gdb 12.1-3
ii  init-system-helpers 1.65.2
ii  iso-codes   4.11.0-1
ii  kactivitymanagerd   5.26.0-1
ii  kded5   5.98.0-1
ii  kinit   5.98.0-1
ii  kio 5.98.0-1
ii  kpackagetool5   5.98.0-1
ii  kwin-common 4:5.26.0-1
ii  libappstreamqt2 0.15.5-1
ii  libc6   2.35-4
ii  libcolorcorrect54:5.26.0-2
ii  libcrypt1   1:4.4.28-2
ii  libfontconfig1  2.13.1-4.5
ii  libfreetype62.12.1+dfsg-3
ii  libgcc-s1   12.2.0-3
ii  libgps283.22-4.1+b1
ii  libice6 2:1.0.10-1
ii  libicu7171.1-3
ii  libkf5activities5   5.98.0-1
ii  libkf5activitiesstats1  5.98.0-1
ii  libkf5archive5  5.98.0-1
ii  libkf5authcore5 5.98.0-1
ii  libkf5baloo55.98.0-1+b1
ii  libkf5bookmarks55.98.0-1
ii  libkf5calendarevents5   5.98.0-2
ii  libkf5completion5   5.98.0-1
ii  libkf5config-bin5.98.0-2
ii  libkf5configcore5   5.98.0-2
ii  libkf5configgui55.98.0-2
ii  libkf5configwidgets55.98.0-1
ii  libkf5coreaddons5   5.98.0-1
ii  libkf5crash55.98.0-1
ii  libkf5dbusaddons5   5.98.0-1
ii  libkf5declarative5  5.98.0-2
ii  libkf5globalaccel-bin   5.98.0-1
ii  libkf5globalaccel5  5.98.0-1
ii  libkf5guiaddons55.98.0-2
ii  libkf5holidays5 1:5.98.0-1
ii  libkf5i18n5 5.98.0-1+b1
ii  libkf5iconthemes5   5.98.0-2+b1
ii  libkf5idletime5 5.98.0-1
ii  libkf5jobwidgets5   5.98.0-1
ii  libkf5kcmutils5 5.98.0-1
ii  libkf5kexiv2-15.0.0 21.12.3-1
ii  libkf5kiocore5  5.98.0-1
ii  libkf5kiofilewidgets5   5.98.0-1
ii  libkf5kiogui5   5.98.0-1
ii  libkf5kiowidgets5   5.98.0-1
ii  libkf5networkmanagerqt6 

Bug#1023174: Acknowledgement (plasma-desktop: Plasma toolbar tooltip window previews not working under wayland: module "org.kde.pipewire" is not installed)

[Ralf Jung]

Turns out the missing package is "qml-module-org-kde-pipewire". It should be 
added as a dependency of plasma-desktop.


; Ralf

Bug#1023174: plasma-desktop: Plasma toolbar tooltip window previews not working under wayland: module "org.kde.pipewire" is not installed

[Ralf Jung]

Package: plasma-desktop
Version: 4:5.26.0-1
Severity: normal

Dear Maintainer,

when starting a Plasma Wayland session, window previews are missing in the 
toolbar tooltips.
This is probably related to the fact that the following shows up in the logs:

file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/PipeWireThumbnail.qml:11:1:
 module "org.kde.pipewire" is not installed

Looks like a missing dependency somewhere? I tried installing libkpipewire by 
hand but that did not help.

Kind regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-desktop depends on:
ii  accountsservice  22.08.8-1+b1
ii  breeze   4:5.26.0-1
ii  kactivitymanagerd5.26.0-1
ii  kde-cli-tools4:5.26.0-1
ii  kded55.98.0-1
ii  kio  5.98.0-1
ii  kpackagetool55.98.0-1
ii  layer-shell-qt   5.26.0-1
ii  libaccounts-qt5-11.16-2
ii  libc62.35-4
ii  libglib2.0-0 2.74.0-3
ii  libibus-1.0-51.5.27-2+b1
ii  libkaccounts24:21.12.3-1
ii  libkf5activities55.98.0-1
ii  libkf5activitiesstats1   5.98.0-1
ii  libkf5authcore5  5.98.0-1
ii  libkf5baloo5 5.98.0-1+b1
ii  libkf5bookmarks5 5.98.0-1
ii  libkf5codecs55.98.0-1
ii  libkf5completion55.98.0-1
ii  libkf5configcore55.98.0-1
ii  libkf5configgui5 5.98.0-1
ii  libkf5configwidgets5 5.98.0-1
ii  libkf5coreaddons55.98.0-1
ii  libkf5crash5 5.98.0-1
ii  libkf5dbusaddons55.98.0-1
ii  libkf5declarative5   5.98.0-2
ii  libkf5globalaccel-bin5.98.0-1
ii  libkf5globalaccel5   5.98.0-1
ii  libkf5guiaddons5 5.98.0-2
ii  libkf5i18n5  5.98.0-1+b1
ii  libkf5iconthemes55.98.0-2+b1
ii  libkf5itemviews5 5.98.0-1
ii  libkf5jobwidgets55.98.0-1
ii  libkf5kcmutils5  5.98.0-1
ii  libkf5kcmutilscore5  5.98.0-1
ii  libkf5kdelibs4support5   5.98.0-1
ii  libkf5kiocore5   5.98.0-1
ii  libkf5kiofilewidgets55.98.0-1
ii  libkf5kiogui55.98.0-1
ii  libkf5kiowidgets55.98.0-1
ii  libkf5newstuffcore5  5.98.0-1
ii  libkf5notifications5 5.98.0-1
ii  libkf5notifyconfig5  5.98.0-1
ii  libkf5package5   5.98.0-1
ii  libkf5plasma55.98.0-1
ii  libkf5plasmaquick5   5.98.0-1
ii  libkf5quickaddons5   5.98.0-2
ii  libkf5runner55.98.0-1
ii  libkf5service-bin5.98.0-1
ii  libkf5service5   5.98.0-1
ii  libkf5solid5 5.98.0-1
ii  libkf5sonnetcore55.98.0-1
ii  libkf5sonnetui5  5.98.0-1
ii  libkf5widgetsaddons5 5.98.0-1
ii  libkf5windowsystem5  5.98.0-1
ii  libkf5xmlgui55.98.0-1+b1
ii  libkuserfeedbackcore11.2.0-2
ii  libkworkspace5-5 4:5.26.0-2
ii  libnotificationmanager1  4:5.26.0-2
ii  libpackagekitqt5-1   1.0.2-1
ii  libphonon4qt5-4  4:4.11.1-4
ii  libprocesscore9  4:5.26.0-2+b1
ii  libqt5concurrent55.15.6+dfsg-2
ii  libqt5core5a 5.15.6+dfsg-2
ii  libqt5dbus5  5.15.6+dfsg-2
ii  libqt5gui5   5.15.6+dfsg-2
ii  libqt5network5   5.15.6+dfsg-2
ii  libqt5qml5   5.15.6+dfsg-2
ii  libqt5quick5 5.15.6+dfsg-2
ii  libqt5quickwidgets5  5.15.6+dfsg-2
ii  libqt5sql5

Bug#1019554: Bug#1021496: anacron: cron.daily stopped executing a month ago

[Ralf Jung]

Hi all,

FWIW, just enabling and starting both the service and the timer did solve the 
problem.


systemctl enable anacron.service anacron.timer
systemctl start anacron.service anacron.timer

; Ralf

Bug#1021496: anacron: cron.daily stopped executing a month ago

[Ralf Jung]

Dear Lance,


This is a problem, since obviously many things rely on these cron jobs running 
regularly.
For example, one of my SSL certificates expired because of this.




Kind regards,
Ralf


I have merged this bug with #1019554.

The problem was introduced in -33. I've noticed that it resulted in an 
incomplete cleanup on upgrade. It has been fixed in -35 but the service still 
doesn't start due to the cleanup.


Ah, indeed the service was 'disabled'.



My tested working solution is to backup existing cron files, remove anacron, 
manually remove the files and install the -35 version.

Specifically, I removed:
/var/lib/systemd/deb-systemd-helper-*/ ... anacron files
/var/lib/dpkg/info/anacron.* files
/var/spool/anacron
/etc/anacrontab

Sorry for the inconvenience. Please let me know if this works as it seems to 
fix it on my system.


Uh, that sounds pretty scary. I already have the -35 installed so the buggy 
postrm should be gone. Shouldn't it be enough to manually enable and start the 
service and timer? I have done that now.


FWIW I agree with the sentiment in that bug that anacron should not touch any of 
these systemd files in its postrm or purge logic. That's what the 
init-system-helpers are for. They are very well-tested and if they leave behind 
dangling symlinks that should be brought up with them. Fixing it only for 
anacron wouldn't help other packages.


Kind regards,
Ralf

Bug#1021496: anacron: cron.daily stopped executing a month ago

[Ralf Jung]

Package: anacron
Version: 2.3-35
Severity: important

Dear Maintainer,

I just realized that my cron.daily jobs stopped being executed about a month 
ago.
'sudo journalctl | grep cron.daily' shows

Sep 04 14:28:19 r-thinktop anacron[12633]: Job `cron.daily' started
Sep 04 14:28:19 r-thinktop anacron[13691]: Updated timestamp for job 
`cron.daily' to 2022-09-04
Sep 04 14:28:20 r-thinktop anacron[12633]: Job `cron.daily' terminated
Sep 05 09:59:36 r-thinktop anacron[34905]: Will run job `cron.daily' in 5 min.
Sep 05 10:04:36 r-thinktop anacron[34905]: Job `cron.daily' started
Sep 05 10:04:36 r-thinktop anacron[36056]: Updated timestamp for job 
`cron.daily' to 2022-09-05
Sep 05 10:04:37 r-thinktop anacron[34905]: Job `cron.daily' terminated
Sep 06 09:24:00 r-thinktop anacron[40089]: Will run job `cron.daily' in 5 min.
Sep 06 09:29:00 r-thinktop anacron[40089]: Job `cron.daily' started
Sep 06 09:29:00 r-thinktop anacron[40715]: Updated timestamp for job 
`cron.daily' to 2022-09-06
Sep 06 09:29:01 r-thinktop anacron[40089]: Job `cron.daily' terminated
Sep 07 09:46:33 r-thinktop anacron[54913]: Will run job `cron.daily' in 5 min.
Sep 07 09:51:33 r-thinktop anacron[54913]: Job `cron.daily' started
Sep 07 09:51:33 r-thinktop anacron[55857]: Updated timestamp for job 
`cron.daily' to 2022-09-07
Sep 07 09:51:33 r-thinktop anacron[54913]: Job `cron.daily' terminated
Sep 08 11:38:05 r-thinktop anacron[67536]: Will run job `cron.daily' in 5 min.
Sep 08 11:43:05 r-thinktop anacron[67536]: Job `cron.daily' started
Sep 08 11:43:05 r-thinktop anacron[69218]: Updated timestamp for job 
`cron.daily' to 2022-09-08
Sep 08 11:43:06 r-thinktop anacron[67536]: Job `cron.daily' terminated

and then it ends.
This is a problem, since obviously many things rely on these cron jobs running 
regularly.
For example, one of my SSL certificates expired because of this.

Kind regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages anacron depends on:
ii  libc6  2.35-1
ii  lsb-base   11.4
ii  sysvinit-utils [lsb-base]  3.05-6

Versions of packages anacron recommends:
ii  cron [cron-daemon]  3.0pl1-149

Versions of packages anacron suggests:
ii  postfix [mail-transport-agent]  3.6.4-1+b3
ii  powermgmt-base  1.37
ii  rsyslog [system-log-daemon] 8.2208.0-1

-- no debconf information

Bug#1017613: kwin-x11 session stops working (semi-freeze) every few days

[Ralf Jung]

Package: kwin-x11
Version: 4:5.25.4-2
Severity: important

Dear Maintainer,

The latest update from kwin 4:5.24.5-1+b1 to 4:5.25.4-2 has made KDE very 
unreliable for me: every other day, the entire session just basically freezes 
up; I can still move the cursor, but that's about it.
Just before that happens, I usually get a black rectangle in the bottom right 
corner of the screen, where the Plasma notifications usually appear.
At that point I can still interact with the foreground application, but if I do 
alt-tab, then the session is doomed and I need to Ctrl-Alt-Backspace, losing 
all unsaved data.

Also see https://bugs.kde.org/show_bug.cgi?id=457847.

Kind regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kwin-x11 depends on:
ii  kwin-common4:5.25.4-2
ii  libc6  2.34-3
ii  libepoxy0  1.5.10-1
ii  libgcc-s1  12.1.0-8
ii  libkdecorations2-5v5   4:5.25.4-1
ii  libkf5configcore5  5.96.0-1
ii  libkf5configgui5   5.96.0-1
ii  libkf5configwidgets5   5.96.0-1
ii  libkf5coreaddons5  5.96.0-1
ii  libkf5crash5   5.96.0-1
ii  libkf5globalaccel-bin  5.96.0-1
ii  libkf5globalaccel5 5.96.0-1
ii  libkf5i18n55.96.0-1
ii  libkf5notifications5   5.96.0-1
ii  libkf5plasma5  5.96.0-1
ii  libkf5service-bin  5.96.0-1
ii  libkf5service5 5.96.0-1
ii  libkf5windowsystem55.96.0-1
ii  libkwineffects13   4:5.25.4-2
ii  libkwinglutils13   4:5.25.4-2
ii  libkwinxrenderutils13  4:5.25.4-2
ii  libqaccessibilityclient-qt5-0  0.4.1-1+b1
ii  libqt5core5a   5.15.4+dfsg-5
ii  libqt5dbus55.15.4+dfsg-5
ii  libqt5gui5 5.15.4+dfsg-5
ii  libqt5qml5 5.15.4+dfsg-4
ii  libqt5widgets5 5.15.4+dfsg-5
ii  libqt5x11extras5   5.15.4-2
ii  libstdc++6 12.1.0-8
ii  libx11-6   2:1.8.1-2
ii  libxcb-composite0  1.15-1
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb-randr0  1.15-1
ii  libxcb-render0 1.15-1
ii  libxcb-shape0  1.15-1
ii  libxcb-xfixes0 1.15-1
ii  libxcb11.15-1
ii  libxi6 2:1.8-1

kwin-x11 recommends no packages.

kwin-x11 suggests no packages.

-- no debconf information

Bug#1014651: firmware-misc-nonfree: Missing latest i915/skl_guc firmware

[Ralf Jung]

Package: firmware-misc-nonfree
Version: 20210818-1
Severity: normal

Dear Maintainer,

on boot, my system says it needs this firmware:

Jul 09 09:59:17 r-thinktop kernel: i915 :00:02.0: firmware: failed to load 
i915/skl_guc_69.0.3.bin (-2)
Jul 09 09:59:17 r-thinktop kernel: firmware_class: See 
https://wiki.debian.org/Firmware for information about missing firmware
Jul 09 09:59:17 r-thinktop kernel: i915 :00:02.0: Direct firmware load for 
i915/skl_guc_69.0.3.bin failed with error -2
Jul 09 09:59:17 r-thinktop kernel: i915 :00:02.0: [drm] GuC firmware 
i915/skl_guc_69.0.3.bin: fetch failed with error -2
Jul 09 09:59:17 r-thinktop kernel: i915 :00:02.0: [drm] GuC firmware(s) can 
be downloaded from 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
Jul 09 09:59:17 r-thinktop kernel: i915 :00:02.0: [drm] GuC firmware 
i915/skl_guc_69.0.3.bin version 0.0
Jul 09 09:59:17 r-thinktop kernel: i915 :00:02.0: [drm] GuC is uninitialized

However, it looks like this package is missing the required version of that 
firmware:

$ dpkg -S i915/skl_guc
firmware-misc-nonfree: /lib/firmware/i915/skl_guc_33.0.0.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_guc_ver1.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_guc_32.0.3.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_guc_49.0.1.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_guc_ver9_33.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_guc_62.0.0.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_guc_ver6_1.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_guc_ver6.bin
firmware-misc-nonfree: /lib/firmware/i915/skl_guc_ver4.bin

Would be nice to get an update with the firmware needed for current kernels. :)

Kind regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.141

-- no debconf information

Bug#1014649: linux-image-5.18.0-2-amd64: System fails to sspend when bluetooth headset is connected

[Ralf Jung]

Package: src:linux
Version: 5.18.5-1
Severity: normal

Dear Maintainer,

starting a month or so ago, I can no longer suspend my system when a bluetooth
headset is connected. When I select "Sleep" in KDE, the screen goes black, but
the laptop keeps running. I have to press the power button for around a second
to get the system back up. After turning off by bluetooth headset, suspend works
as expected.

This seems to be the relevant part of the kernel log:

Jul 09 09:07:48 r-thinktop kernel: Freezing user space processes ... (elapsed 
0.002 seconds) done.
Jul 09 09:07:48 r-thinktop kernel: OOM killer disabled.
Jul 09 09:07:48 r-thinktop kernel: Freezing remaining freezable tasks ... 
(elapsed 0.001 seconds) done.
Jul 09 09:07:48 r-thinktop kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
Jul 09 09:07:48 r-thinktop kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Jul 09 09:07:48 r-thinktop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 09 09:07:48 r-thinktop kernel: sd 3:0:0:0: [sdb] Stopping disk
Jul 09 09:07:48 r-thinktop kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 09 09:07:48 r-thinktop kernel: e1000e: EEE TX LPI TIMER: 0011
Jul 09 09:07:48 r-thinktop kernel: xhci_hcd :00:14.0: PM: pci_pm_suspend(): 
hcd_pci_suspend+0x0/0x30 [usbcore] returns -16
Jul 09 09:07:48 r-thinktop kernel: xhci_hcd :00:14.0: PM: 
dpm_run_callback(): pci_pm_suspend+0x0/0x160 returns -16
Jul 09 09:07:48 r-thinktop kernel: xhci_hcd :00:14.0: PM: failed to suspend 
async: error -16
Jul 09 09:07:48 r-thinktop kernel: PM: Some devices failed to suspend, or early 
wake event detected
Jul 09 09:07:48 r-thinktop kernel: sd 0:0:0:0: [sda] Starting disk
Jul 09 09:07:48 r-thinktop kernel: sd 3:0:0:0: [sdb] Starting disk
Jul 09 09:07:48 r-thinktop kernel: i915 :00:02.0: [drm] GuC firmware 
i915/skl_guc_69.0.3.bin version 0.0
Jul 09 09:07:48 r-thinktop kernel: i915 :00:02.0: [drm] GuC is uninitialized
Jul 09 09:07:48 r-thinktop kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 
SControl 300)
Jul 09 09:07:48 r-thinktop kernel: ata4.00: ACPI cmd 
f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out
Jul 09 09:07:48 r-thinktop kernel: ata4.00: ACPI cmd ef/10:03:00:00:00:a0(SET 
FEATURES) filtered out
Jul 09 09:07:48 r-thinktop kernel: ata4.00: ACPI cmd 
f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out
Jul 09 09:07:48 r-thinktop kernel: ata4.00: ACPI cmd ef/10:03:00:00:00:a0(SET 
FEATURES) filtered out
Jul 09 09:07:48 r-thinktop kernel: ata4.00: configured for UDMA/133
Jul 09 09:07:48 r-thinktop kernel: e1000e :00:1f.6 enp0s31f6: Failed to 
disable ULP
Jul 09 09:07:48 r-thinktop kernel: OOM killer enabled.
Jul 09 09:07:48 r-thinktop kernel: Restarting tasks ... done.
Jul 09 09:07:48 r-thinktop bluetoothd[990]: src/profile.c:ext_io_disconnected() 
Unable to get io data for Hands-Free Voice gateway: getpeername: Transport 
endpoint is not connected (107)
Jul 09 09:07:48 r-thinktop bluetoothd[990]: Controller resume with wake event 
0x0
Jul 09 09:07:48 r-thinktop kernel: PM: suspend exit
Jul 09 09:07:48 r-thinktop kernel: PM: suspend entry (s2idle)
Jul 09 09:07:48 r-thinktop kernel: Filesystems sync: 0.008 seconds
Jul 09 09:07:48 r-thinktop PackageKit[2193]: get-updates transaction 
/7679_daadcccd from uid 1000 finished with success after 4895ms
Jul 09 09:07:59 r-thinktop kernel: Freezing user space processes ... (elapsed 
0.002 seconds) done.
Jul 09 09:07:59 r-thinktop kernel: OOM killer disabled.
Jul 09 09:07:59 r-thinktop kernel: Freezing remaining freezable tasks ... 
(elapsed 0.001 seconds) done.
Jul 09 09:07:59 r-thinktop kernel: printk: Suspending console(s) (use 
no_console_suspend to debug)
Jul 09 09:07:59 r-thinktop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jul 09 09:07:59 r-thinktop kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
Jul 09 09:07:59 r-thinktop kernel: sd 3:0:0:0: [sdb] Stopping disk
Jul 09 09:07:59 r-thinktop kernel: sd 0:0:0:0: [sda] Stopping disk
Jul 09 09:07:59 r-thinktop kernel: e1000e: EEE TX LPI TIMER: 0011
Jul 09 09:07:59 r-thinktop kernel: ACPI: EC: interrupt blocked
Jul 09 09:07:59 r-thinktop kernel: ACPI: EC: interrupt unblocked
Jul 09 09:07:59 r-thinktop kernel: pcieport :00:1c.0: Intel SPT PCH root 
port ACS workaround enabled
Jul 09 09:07:59 r-thinktop kernel: pcieport :00:1d.0: Intel SPT PCH root 
port ACS workaround enabled
Jul 09 09:07:59 r-thinktop kernel: nvidia :01:00.0: Enabling HDA controller
Jul 09 09:07:59 r-thinktop kernel: pcieport :00:1c.4: Intel SPT PCH root 
port ACS workaround enabled
Jul 09 09:07:59 r-thinktop kernel: i915 :00:02.0: [drm] GuC firmware 
i915/skl_guc_69.0.3.bin version 0.0
Jul 09 09:07:59 r-thinktop kernel: i915 :00:02.0: [drm] GuC is uninitialized
Jul 09 09:07:59 r-thinktop kernel: sd 0:0:0:0: [sda] Starting disk
Jul 09 09:07:59 r-thinktop kernel: sd 3:0:0:0: [sdb] Starting disk
Jul 09 09:07:59 r-thinktop kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 
SControl 300)
Jul 09 

Bug#1013797: grub-efi: grub no longer offers to boot Windows

[Ralf Jung]

Ah, turns out I need to add "GRUB_DISABLE_OS_PROBER=false" in /etc/default/grub.
I think it is bad to silently change the default in an upgrade here, since it 
can leave people locked out of an OS they need.

GRUB_DISABLE_OS_PROBER is not even listed in /etc/default/grub.ucf-dist.

Kind regards,
Ralf

Bug#1013797: grub-efi: grub no longer offers to boot Windows

[Ralf Jung]

Package: grub-efi
Version: 2.06-3
Severity: important

Dear Maintainer,

After doing a system update, the option to boot Windows has disappeared from 
Grub.
I have not changed anything else.
This will be a big problem the next time I actually need to boot Windows.

Kind regards,
Ralf

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/mapper/vg-root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sda2 /boot ext4 rw,relatime 0 0
/dev/mapper/vg-home /home ext4 rw,relatime 0 0
/dev/sda1 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/mapper/store /mnt/store ext4 rw,relatime 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="2"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 
--hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  
2af046c2-1c1f-43ca-9692-7ea1d357493b
else
  search --no-floppy --fs-uuid --set=root 2af046c2-1c1f-43ca-9692-7ea1d357493b
fi
font="/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1920x1080,1024x768,auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=3
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=3
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 
--hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  
2af046c2-1c1f-43ca-9692-7ea1d357493b
else
  search --no-floppy --fs-uuid --set=root 2af046c2-1c1f-43ca-9692-7ea1d357493b
fi
insmod png
if background_image /grub/.background_cache.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=keep
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-8f0db0a1-2c26-4b6c-a132-e8292709197e' {
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 
--hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  
2af046c2-1c1f-43ca-9692-7ea1d357493b
else
  search --no-floppy --fs-uuid --set=root 
2af046c2-1c1f-43ca-9692-7ea1d357493b
fi
echo'Loading Linux 5.18.0-2-amd64 ...'
linux   /vmlinuz-5.18.0-2-amd64 root=/dev/mapper/vg-root ro  quiet 
splash
echo'Loading initial ramdisk ...'
initrd  /initrd.img-5.18.0-2-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-8f0db0a1-2c26-4b6c-a132-e8292709197e' {
menuentry 'Debian GNU/Linux, with Linux 5.18.0-2-amd64' --class debian 
--class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-5.18.0-2-amd64-advanced-8f0db0a1-2c26-4b6c-a132-e8292709197e' {
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; 

Bug#1007822: "ssh -XAf localhost xeyes" uses 100% CPU after losing tty

[Ralf Jung]

Hi all,

I am also seeing 100% CPU load from SSH when using it with autossh to set up 
port forwarding in the background (no X11 forwarding involved):


/usr/bin/autossh -M 0 -N -o "ServerAliveInterval 30" -R $IP:$PORT1:localhost:443 
-R $IP:$PORT2:localhost:80 $USER@$HOST -i $KEY


This only recently started with the latest 'apt upgrade'.

; Ralf

On Thu, 17 Mar 2022 13:26:09 +0100 Harald Dunkel  wrote:

Package: openssh-client
Version: 1:8.9p1-3

If I use

ssh -XAf localhost xterm

to run a second xterm, then ssh eats up 100% CPU after closing the
first xterm.

Same happens for xeyes or other XWindow apps. It doesn't have to be
localhost, either.

"nohup ssh -XAf ..." seems to work, but for Bullseye it works very well
without nohup.

SHELL is bash 5.1-6


Regards
Harri

Bug#1006626: biber: Lots of "Use of uninitialized value" warnings after biber update

[Ralf Jung]

Package: biber
Version: 2.17-2
Severity: normal

Dear Maintainer,

I updated biber to 2.17, and now I am getting many warnings (thousands of them
for large bib files, which significantly slows down biber itself) from files
that were clean before. The warnings all look like this:
```
Use of uninitialized value $opt in hash element at 
/usr/share/perl5/Biber/Config.pm line 977.
Use of uninitialized value within %Biber::Config::CONFIG_OPTSCOPE_BIBLATEX in 
hash dereference at /usr/share/perl5/Biber/Config.pm line 977.
```
Sometimes the line numbers are different (I have seen 967, 972, 977).

*Any* use of biber causes that warning for me, so here is an arbitrary example:
```
\documentclass[10pt,a4paper]{article}
\usepackage[backend=biber]{biblatex}

\addbibresource{bib.bib}

\begin{document}

\fullcite{iris}

\end{document}
```
With `bib.bib` being
```
@inproceedings{iris,
  author= {Ralf Jung and
   David Swasey and
   Filip Sieczkowski and
   Kasper Svendsen and
   Aaron Turon and
   Lars Birkedal and
   Derek Dreyer},
  title = {{Iris}: Monoids and Invariants as an Orthogonal Basis for 
Concurrent
   Reasoning},
  booktitle = {{POPL}},
  year  = {2015},
  doi   = {10.1145/2676726.2676980},
}
```

I reported this upstream at https://github.com/plk/biber/issues/403, but the
maintainer suggested this might be a packaging issues since they could not
reproduce the problem.

Kind regards,
Ralf

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages biber depends on:
ii  libautovivification-perl  0.18-1+b4
ii  libbusiness-isbn-perl 3.006-1
ii  libbusiness-ismn-perl 1.202-1
ii  libbusiness-issn-perl 1.005-1
ii  libclass-accessor-perl0.51-1
ii  libdata-compare-perl  1.27-1
ii  libdata-dump-perl 1.25-1
ii  libdata-uniqid-perl   0.12-1.1
ii  libdate-simple-perl   3.0300-3+b2
ii  libdatetime-calendar-julian-perl  0.107-1
ii  libdatetime-format-builder-perl   0.8300-1
ii  libdatetime-perl  2:1.55-1+b1
ii  libencode-eucjpms-perl0.07-3+b10
ii  libencode-hanextra-perl   0.23-5+b4
ii  libencode-jis2k-perl  0.03-1+b8
ii  libfile-slurper-perl  0.013-1
ii  libipc-run3-perl  0.048-2
ii  liblingua-translit-perl   0.28-1
ii  liblist-allutils-perl 0.19-1
ii  liblist-moreutils-perl0.430-2
ii  liblog-log4perl-perl  1.54-1
ii  liblwp-protocol-https-perl6.10-1
ii  libparse-recdescent-perl  1.967015+dfsg-2
ii  libreadonly-perl  2.050-3
ii  libregexp-common-perl 2017060201-1
ii  libsort-key-perl  1.33-2+b4
ii  libtext-bibtex-perl   0.88-3+b3
ii  libtext-csv-perl  2.01-1
ii  libtext-csv-xs-perl   1.47-1+b1
ii  libtext-roman-perl3.5-2.1
ii  libunicode-collate-perl   1.31-1+b1
ii  libunicode-linebreak-perl 0.0.20190101-1+b4
ii  liburi-perl   5.10-1
ii  libwww-perl   6.61-1
ii  libxml-libxml-simple-perl 1.01-1
ii  libxml-libxslt-perl   1.99-1+b2
ii  libxml-writer-perl0.900-1
ii  perl [libunicode-collate-perl]5.34.0-3
ii  tex-common6.17

Versions of packages biber recommends:
ii  texlive-bibtex-extra  2021.20220204-1

biber suggests no packages.

-- no debconf information

Bug#907178: gimp-plugin-registry: resynthesizer not appearing in menu Filters/Enhance

[Ralf Jung]

Hi again,

the latest changelog for version 9.20200927 of this package says

"resynthesizer: ported to python3"

However, the resynthesizer still does not work after installing the package (the 
menu entries simply do not appear). So one of the best features of Gimp is 
broken for several years now. :(
I think the severity of this bug should be raised, since it makes the package 
entirely useless -- at least for people that care about resynthesizer but none 
of the other plugins.


Kind regards,
Ralf

Bug#998220: [Pkg-utopia-maintainers] Bug#998220: pipewire: libspa-0.2-bluetooth not installed

[Ralf Jung]

I don't think this is true at least I don't see any dependency changes in Debian which would automatically install pipewire-pulse. 


Well, all I can say is that I did a regular system update and now I have 
pipewire-pulse installed. I certainly did not choose to do this myself, so 
something did it automatically.



Ok, thanks for the clarification. I guess this was an unintentional
change/result?


Unfortunately, yes :-( and I am still unsure how to fix that because
if we remove pipewire-pulse from recommends of wireplumber that will
completely break sound.
I try to reintroduce pipewire-media-session (still in NEW), but it is
a temporary workaround as it it not recommended by upstream devs.


So is the recommendation that users switch back to PulseAudio? What would be the 
process for that, i.e., which packages do I have to (un)install?


Kind regards,
Ralf

Bug#998220: pipewire: libspa-0.2-bluetooth not installed

[Ralf Jung]

This however did not solve my problem, I will file another bug report for the
remaining part


I am also still struggling with getting BT working again; do you have a link to 
the other bug report?


Addendum: the missing bit in my case (besides installing libspa-0.2-bluetooth 
package and removing pulseaudio-module-bluetooth) was that I had to re-pair the 
device. Now it seems things are working again as before.


Kind regards,
Ralf

Bug#998220: pipewire: libspa-0.2-bluetooth not installed

[Ralf Jung]

Hi all,


The first problem was that the headset disconnected immediately after
connecting. There was an associated error in journalctl :

src/service.c:btd_service_connect() a2dp-sink profile connect failed for  Protocol not available

Some search engine pointed to me that this may be associated with missing
libspa-0.2-bluetooth, so I installed it and this first error disappeared. So a
first suggestion would be to make sure that libspa-0.2-bluetooth is added as a
dependency to some of the pipewire set.


I am having the same problem. According to 
https://wiki.debian.org/BluetoothUser/a2dp, one also has to uninstall 
pulseaudio-module-bluetooth.


This is one of the rare cases where upgrading Debian just silently broke the 
system -- all bluetooth audio functionality just stopped working without 
warning. I hope something can be done to avoid this.


Amusingly, the description of the libspa package says " It is considered to be 
experimental, and is disabled by default (even if installed) to avoid conflicts 
with equivalent functionality in PulseAudio. " -- however, since upgrades now 
seem to automatically switch people over from PA to pipewire, does this still 
make sense? So far certainly one cannot speak of "equivalent functionality", 
since the bluetooth support in PA actually worked out of the box without any 
fiddling...



This however did not solve my problem, I will file another bug report for the
remaining part


I am also still struggling with getting BT working again; do you have a link to 
the other bug report?


Kind regards,
Ralf

Bug#990121: osspd: revert debhelper compat bump to get #986662 fixed in bullseye

[Ralf Jung]

Hi Simon,

my Salsa account was approved. I have replaced the old git repository by a 
reference to the new one, so that's the canonical location now. :)


Kind regards,
Ralf

On 22.06.21 12:33, Simon McVittie wrote:

On Tue, 22 Jun 2021 at 12:02:35 +0200, Ralf Jung wrote:

Btw, I'm not using osspd any more, and I am not very skilled with Debian
packaging tools since all I do with them is upload a new osspd release every
2 years or so. So help would be welcome. :)


Moving the version control onto salsa.debian.org, either in your personal
namespace if you want tight control over it, in the debian namespace if
you want minimum friction for contributions from Debian Developers, or
in some suitable team's namespace, would probably make it easier to
collaborate. I can help with this.


Sure, that works for me. The "debian" namespace seems fine.


I've created https://salsa.debian.org/debian/osspd/, added Sébastien
as a co-maintainer and invited you by email. I'll use that git repository
as the Vcs-Git in my next upload.

 smcv

Bug#990121: osspd: revert debhelper compat bump to get #986662 fixed in bullseye

[Ralf Jung]

Hi,


Sure, that works for me. The "debian" namespace seems fine.


I've created https://salsa.debian.org/debian/osspd/, added Sébastien
as a co-maintainer and invited you by email. I'll use that git repository
as the Vcs-Git in my next upload.


Great! My gitlab account is awaiting approval from an admin. :)

Kind regards,
Ralf

Bug#990121: osspd: revert debhelper compat bump to get #986662 fixed in bullseye

[Ralf Jung]

Hi Simon,


Btw, I'm not using osspd any more, and I am not very skilled with Debian
packaging tools since all I do with them is upload a new osspd release every
2 years or so. So help would be welcome. :)


Moving the version control onto salsa.debian.org, either in your personal
namespace if you want tight control over it, in the debian namespace if
you want minimum friction for contributions from Debian Developers, or
in some suitable team's namespace, would probably make it easier to
collaborate. I can help with this.


Sure, that works for me. The "debian" namespace seems fine.


I wonder whether it'd make sense for the Games Team to absorb it, since
its major use-case in 2021 is probably running ancient binary-only games
like Unreal Tournament? You could still be in Uploaders if you're
interested in it.


If the Games Team is willing to do this, sure, why not. :)
I seem to recall there is also some organization/group/team for packages that 
are "jointly maintained", I guess that would be the other obvious alternative.


Kind regards,
Ralf

Bug#990121: osspd: revert debhelper compat bump to get #986662 fixed in bullseye

[Ralf Jung]

Hi Simon,


Ralf, may I do another NMU dropping those patches to keep this moving
along? And then we can discuss how this package is going to be maintained
post-bullseye without being on a time limit.


Sure. Feel free to put it in DELAYED/0 right away.

; Ralf

Bug#990013: pulseaudio: Volume reset to mute each time I (un)plug my speakers

[Ralf Jung]

Dear Maintainer,

I am not entirely sure what happened, but the issue went away again when I 
connected by bluetooth headset the next time. Very strange.

I guess I will avoid muting my speakers again...

Kind regards,
Ralf

Bug#990121: osspd: revert debhelper compat bump to get #986662 fixed in bullseye

[Ralf Jung]

Hi Simon,


If you are happy with this change, please say so, and I can move the upload
out of the DELAYED queue and into unstable immediately.


Thanks a lot! Yes I am happy with the change.


I am unsure whether the release team will be willing to unblock with the
two commits cherry-picked from upstream git included in the package. If
they are not, another upload that additionally reverts one or both of
those commits might be necessary. We are less likely to need to revert
them if we can justify why they are required.

d/p/GIT-fix-adsp_se.patch looks like it might be fixing a genuine bug. Can
you describe the bug that it is fixing and why it should be applied in
bullseye?

d/p/GIT-fix-compiler-warnings.patch looks like it is just silencing
compiler warnings by removing unreachable code. Do we really need this
for bullseye? If it is not strictly necessary then it might be safer to
revert it until after bullseye has been released.


Those changes were suggested for inclusion by Sébastien (CC'ed). I don't know 
more about them than what it says in the patch files. They both come from 
upstream osspd git.



After bullseye is released and the freeze is over, you can reapply the
changes that I've reverted and upload to unstable in the usual way.


So, the recommended way is that I pull your changes into my git repo, and then 
apply reverts of the reverts? Sure, works for me.



Thanks for maintaining osspd,


Btw, I'm not using osspd any more, and I am not very skilled with Debian 
packaging tools since all I do with them is upload a new osspd release every 2 
years or so. So help would be welcome. :)


Kind regards,
Ralf

Bug#990013: pulseaudio: Volume reset to mute each time I (un)plug my speakers

[Ralf Jung]

Package: pulseaudio
Version: 14.2-2
Severity: normal

Dear Maintainer,

I have recently made the mistake of muting my laptop speakers in PulseAudio.
Ever since then, each time I (un)plug my external headphones, or (dis)connect by
Bluetooth headset, the sound mutes again. I am unmuting it each time, of course,
but Pulseaudio does not remember that and resets it back to muted the next time.

This already happened a few months ago, but then stopped with a Pulseaudio
update. Now the problem seems to be back. I am using KDE as my desktop
environment; I do not know how to begin debugging if KDE or Pulseaudio is doing
the muting here.

I tried following the logging instructions at
https://wiki.ubuntu.com/PulseAudio/Log, but that does not seem to work as
intended:
(   0.010|   0.000) E: [pulseaudio] pid.c: Daemon already running.
(   0.011|   0.000) E: [pulseaudio] main.c: pa_pid_file_create() failed.
(Yes, I did put the "autospawn = no" as described. It seems to have no effect.)

Kind regards,
Ralf

-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-security'), (500, 
'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libasound2   1.2.4-1.1
ii  libasound2-plugins   1.2.2-2
ii  libc62.31-12
ii  libcap2  1:2.44-1
ii  libdbus-1-3  1.12.20-2
ii  libgcc-s110.2.1-6
ii  libice6  2:1.0.10-1
ii  libltdl7 2.4.6-15
ii  liborc-0.4-0 1:0.4.32-1
ii  libpulse014.2-2
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.31-1
ii  libsoxr0 0.1.3-4
ii  libspeexdsp1 1.2~rc1.2-1.1
ii  libstdc++6   10.2.1-6
ii  libsystemd0  247.3-5
ii  libtdb1  1.4.3-1+b1
ii  libudev1 247.3-5
ii  libwebrtc-audio-processing1  0.3-1+b1
ii  libx11-6 2:1.7.1-1
ii  libx11-xcb1  2:1.7.1-1
ii  libxcb1  1.14-3
ii  libxtst6 2:1.2.3-1
ii  lsb-base 11.1.0
ii  pulseaudio-utils 14.2-2

Versions of packages pulseaudio recommends:
ii  dbus-user-session1.12.20-2
ii  libpam-systemd [logind]  247.3-5
ii  rtkit0.13-4

Versions of packages pulseaudio suggests:
pn  paprefs  
ii  pavucontrol  4.0-2
pn  pavumeter
ii  udev 247.3-5

-- Configuration Files:
/etc/pulse/default.pa changed:
.fail
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-augment-properties
load-module module-switch-on-port-available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
load-module module-detect
.endif
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix
.ifexists module-gsettings.so
.nofail
load-module module-gsettings
.fail
.endif
load-module module-default-device-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-intended-roles
load-module module-suspend-on-idle
.ifexists module-console-kit.so
load-module module-console-kit
.endif
.ifexists module-systemd-login.so
load-module module-systemd-login
.endif
load-module module-position-event-sounds
load-module module-filter-heuristics
load-module module-filter-apply


-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with 

Bug#987874: [pre-approval] unblock: osspd/1.3.2-12

[Ralf Jung]

Hi Simon,


On Thu, 10 Jun 2021 at 17:27:48 +0200, Paul Gevers wrote:

If you really think another upload is too much hassle, you could
convince us to unblock regardless if you build twice and show with
diffoscope that the compat bump doesn't impact the (binary) packages at all.


I'm not the maintainer, but I'd like to see osspd get into bullseye:
it's good to have around for the benefit of old binary-only games,
some of which are supported by game-data-packager.

Unfortunately the compat bump from 9 to 13 does make a difference to the
built binaries (mostly due to the addition of dh_dwz and the switch from
dh_installinit to dh_systemd for systemd units, I think).

Ralf, would you accept an NMU with the compat level bump reverted?


Sure. I don't know what the process is for this, but if you want to fix osspd in
bullseye, feel free to do whatever is necessary, and then please let me know 
what I have to do to get the compat-level-13 version back into unstable after 
the bullseye release. :)


Kind regards,
Ralf

Bug#987874: [pre-approval] unblock: osspd/1.3.2-12

[Ralf Jung]

Dear release team,

osspd maintainer here. Version 1.3.2-12 has hit unstable now that my new key is 
finally in the keyring.



> diff --git a/debian/changelog b/debian/changelog
> index c412732..9481d07 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,17 @@
> +osspd (1.3.2-12) unstable; urgency=low
> +
> +  [ Sébastien Noel ]
> +  * cherrypick 2 commits from upstream GIT:
> ++ d/p/GIT-fix-adsp_se.patch
> ++ d/p/GIT-fix-compiler-warnings.patch
> +  * Add workaround for pulseaudio >= 13
> +d/p/Hack-to-work-with-modern-PulseAudio.patch  (Closes: #986662)
> +
> +  [ Ralf Jung ]
> +  * Switch to debhelper compat level 13.

Changing compat levels is no longer acceptable for bullseye. Please
revert.


Ah, that's a bummer. I was not aware of this policy, sorry for that.
Doing a revert upload sounds like a lot of hassle though that this package is 
probably not worth -- so in this case it likely makes more sense to simply 
remove the package from testing, and let it re-migrate after the release. The 
current testing version (1.3.2-11) is broken with current PulseAudio, so 
shipping it as-is makes no sense.



+Pre-Depends: ${misc:Pre-Depends}


Why?


Because lintian told me a pre-depends on "init-system-helpers" was missing, and 
this was the easiest way to get that dependency.


Kind regards,
Ralf

Bug#986662: ossp-padsp not working with recent Pulseaudio

[Ralf Jung]

Hi all,

Meanwhile, the version of osspd that I had uploaded a while ago finally got 
accepted to unstable. :)



When we prepared the fix, we were not aware that this would become an RC bug, so
we didn't strive for a minimal fix.


Okay. Then I'll open a bugreport with release.debian.org and ask if
this not so minimal
update can propagate to testing. If yes, I'll reupload it.


Sergei, have you created this bugreport already? If so, could you link us to it? 
Asking for migration to testing now is the only thing missing here I think.


Kind regards,
Ralf

Bug#986662: ossp-padsp not working with recent Pulseaudio

[Ralf Jung]

Hi Sergei,


When we prepared the fix, we were not aware that this would become an RC bug, so
we didn't strive for a minimal fix.


Okay. Then I'll open a bugreport with release.debian.org and ask if
this not so minimal
update can propagate to testing. If yes, I'll reupload it.


That sounds great, thanks for your help. :)

Kind regards,
Ralf

Bug#986662: ossp-padsp not working with recent Pulseaudio

[Ralf Jung]

Hi Sergei,

Our current problem is that we cannot even upload the package to unstable since 
my key in the debian keyring expired (and the updated key missed the April 
keyring update), and Sebastien is not yet allowed to upload osspd.
I've done the upload before figuring this out, so now revision 12 is sitting on 
the ftp server and waiting for my key to become valid...


If you are a DD, maybe you can help by uploading the package for us? I guess 
we'd have to prepare a revision 13, but that should be easy.


When we prepared the fix, we were not aware that this would become an RC bug, so 
we didn't strive for a minimal fix.


Kind regards,
Ralf

On 30.04.21 12:02, Sergei Golovan wrote:

Hi Ralf, Sebastien,

If you need any help with uploading the osspd package, please let me
know. I've looked at the current 1.3.2-12 in Git, and it looks fine
with the exception that it adds more changes than the fix of this bug
(which is not advisable during freeze periods). So, I'd start to ask
the release team if they are willing to grant a freeze exception for
the new version prior to upload.

Cheers!

Bug#986662: ossp-padsp not working with recent Pulseaudio

[Ralf Jung]

Dear Sébastien,


The current osspd packages isn't working with current pulseaudio and it hasn't
for more than a year. I didn't file a bug back then, but I can confirm that
at the time it was a pulseaudio update that broke osspd.
Downgrading to an earlier version fixed the problem.

Here is what the osspd logs says:
ossp-padsp[] WARN: failed to subscribe to context events (Bad state)
ossp-padsp[] ERR: failed to connect context, state=5 (Bad state)

This bug has also been reported on launchpad for Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/osspd/+bug/1857810

Almost 18 months later, I did found (by pure luck) that the ArchLinux package
has a fix for this problem.
Please find a debdiff in attachment so that you can upload the fix in Debian.


Thanks a lot for this! I have applied the patch in the git version of the 
package. I'll look into moving to a non-deprecated debhelper compat level, and 
then upload a new version.


Would you be interested in helping maintain osspd? As you can tell from it not 
working for more than a year, I am not actually using this package any more. I 
am also not maintaining any other Debian packages, so each time something comes 
up I have to re-learn how to use the involved tools.^^


Kind regards,
Ralf

Bug#986049: firejail: Chromium profile breaks webext-browserpass

[Ralf Jung]

Package: firejail
Version: 0.9.64.4-2
Severity: normal

Dear Maintainer,

some time earlier this year, Chromium started to show an error message on each 
start that the "browserpass" extension could not be properly loaded.
I finally got around to investigate this, and realized it is caused by 
firejail: something changed in firejail or the extension, such that extension 
paths are not longer available to chromium.
The extension folder looks like this:

$ ls /usr/share/chromium/extensions/browserpass/ -lah
total 44K
drwxr-xr-x 2 root root 4,0K  6. Mär 23:07 .
drwxr-xr-x 3 root root 4,0K 28. Dez 15:41 ..
lrwxrwxrwx 1 root root   95 23. Jun 2020  css -> 
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/css
lrwxrwxrwx 1 root root   97 23. Jun 2020  fonts -> 
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/fonts
lrwxrwxrwx 1 root root  102 16. Feb 11:32 icon16.png -> 
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/icon16.png
lrwxrwxrwx 1 root root  100 16. Feb 11:32 icon.png -> 
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/icon.png
lrwxrwxrwx 1 root root  100 16. Feb 11:32 icon.svg -> 
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/icon.svg
lrwxrwxrwx 1 root root   94 23. Jun 2020  js -> 
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/js
-rw-r--r-- 1 root root 2,0K 16. Feb 11:32 manifest.json
lrwxrwxrwx 1 root root   99 23. Jun 2020  options -> 
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/options
lrwxrwxrwx 1 root root   97 23. Jun 2020  popup -> 
../../../mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/browserp...@maximbaz.com/popup

Inside the firejail, those symlinks are dead, since the "mozilla" folder seems 
to be blocked.

Kind regards,
Ralf

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-security'), (500, 
'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firejail depends on:
ii  libapparmor1  2.13.6-9
ii  libc6 2.31-10
ii  libselinux1   3.1-3

Versions of packages firejail recommends:
ii  firejail-profiles  0.9.64.4-2
ii  iproute2   5.10.0-4
ii  iptables   1.8.7-1
ii  xauth  1:1.1-1
ii  xdg-dbus-proxy 0.1.2-2
ii  xserver-xephyr 2:1.20.10-3

firejail suggests no packages.

-- no debconf information

Bug#945824: [python3-numpy] Depends on python3.8 and python3.7

[Ralf Jung]

On 23.11.20 16:21, Sandro Tosi wrote:
>> But now it depends on both python3.8:any and python3.9:any.
> 
> and this will continue to be the case for as long as we have 2
> supported python3 versions.

But why do all of your users have to install two Python versions just because
you support both of them? It seems to me the way to express that both versions
are supported would be a dependency on python 3.8 *or* python 3.9.

; Ralf

Bug#969039: kwin-x11: Cannot scroll in some windows (e.g. Firefox) while Plasma notification is shown

[Ralf Jung]

Package: kwin-x11
Version: 4:5.17.5-2+b1
Severity: important

Dear Maintainer,

since the update to Firefox 81 (which presumably switched to Xinput 2), I cannot
scroll in Firefox any more when a Plasma notification is shown.  I think this is
an instance of https://bugs.kde.org/show_bug.cgi?id=394772, which means updating
to 5.19.3 would likely fix the problem.

Kind regards,
Ralf

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.13 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kwin-x11 depends on:
ii  kwin-common4:5.17.5-2+b1
ii  libc6  2.31-2
ii  libepoxy0  1.5.4-1
ii  libgcc-s1  10.1.0-6
ii  libkf5configcore5  5.70.0-1
ii  libkf5coreaddons5  5.70.0-1
ii  libkf5crash5   5.70.0-1
ii  libkf5i18n55.70.0-1
ii  libkf5quickaddons5 5.70.0-1
ii  libkf5waylandserver5   4:5.70.0-1
ii  libkf5windowsystem55.70.0-1
ii  libkwineffects12   4:5.17.5-2+b1
ii  libkwinglutils12   4:5.17.5-2+b1
ii  libkwinxrenderutils12  4:5.17.5-2+b1
ii  libqt5core5a   5.14.2+dfsg-4
ii  libqt5gui5 5.14.2+dfsg-4
ii  libqt5widgets5 5.14.2+dfsg-4
ii  libqt5x11extras5   5.14.2-2
ii  libstdc++6 10.1.0-6
ii  libx11-6   2:1.6.10-3
ii  libxcb-composite0  1.14-2
ii  libxcb-cursor0 0.1.1-4
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb-randr0  1.14-2
ii  libxcb-render0 1.14-2
ii  libxcb-shape0  1.14-2
ii  libxcb-xfixes0 1.14-2
ii  libxcb11.14-2
ii  libxi6 2:1.7.10-1

kwin-x11 recommends no packages.

kwin-x11 suggests no packages.

-- no debconf information

Bug#968828: systemsettings: Extern screen is put at the wrong position on each reconnect

[Ralf Jung]

Package: systemsettings
Version: 4:5.17.5-2
Severity: important

Dear Maintainer,

After conencting my external HDMI screen, I set it up (with resolution
1920x1200) to be to the left of my laptop screen (1920x1080, on a 4k screen but
using a lower resolution as scaling just does not work well enough), with their
bottom edges aligned.  However, after unplugging and replugging the screen, it
puts them into a different position, where just their corners touch, so it is
impossible to move the cursor from one screen to another. I have to fix this
manually every single time I connect my laptop back to my screen.

As a work-around, I am now using a different connector on my laptop with an
adapter, just because the HDMI port is made unusable by this bug.

(Usually I would report this upstream, but systemsettings is rather outdated in
Debian, with a new major version availabke for more than half a year, so it
doesn't make sense to bother the upstream developers I think.)

Kind regards,
Ralf

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.13 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemsettings depends on:
ii  kio   5.70.1-1
ii  kpackagetool5 5.70.0-1
ii  libc6 2.31-2
ii  libkf5activities5 5.70.0-1
ii  libkf5activitiesstats15.70.0-1
ii  libkf5auth5   5.70.0-1
ii  libkf5authcore5   5.70.0-1
ii  libkf5completion5 5.70.0-1
ii  libkf5configcore5 5.70.0-1
ii  libkf5configgui5  5.70.0-1
ii  libkf5configwidgets5  5.70.0-2
ii  libkf5coreaddons5 5.70.0-1
ii  libkf5crash5  5.70.0-1
ii  libkf5dbusaddons5 5.70.0-1
ii  libkf5declarative55.70.0-1
ii  libkf5i18n5   5.70.0-1
ii  libkf5iconthemes5 5.70.0-1
ii  libkf5itemviews5  5.70.0-1
ii  libkf5kcmutils5   5.70.0-1
ii  libkf5kiowidgets5 5.70.1-1
ii  libkf5package55.70.0-1
ii  libkf5quickaddons55.70.0-1
ii  libkf5service-bin 5.70.0-1
ii  libkf5service55.70.0-1
ii  libkf5widgetsaddons5  5.70.0-1
ii  libkf5windowsystem5   5.70.0-1
ii  libkf5xmlgui5 5.70.0-1+b1
ii  libkworkspace5-5  4:5.17.5-4
ii  libqt5core5a  5.14.2+dfsg-4
ii  libqt5dbus5   5.14.2+dfsg-4
ii  libqt5gui55.14.2+dfsg-4
ii  libqt5qml55.14.2+dfsg-3
ii  libqt5quick5  5.14.2+dfsg-3
ii  libqt5quickwidgets5   5.14.2+dfsg-3
ii  libqt5widgets55.14.2+dfsg-4
ii  libstdc++610.1.0-6
ii  qml-module-org-kde-kcm5.70.0-1
ii  qml-module-org-kde-kirigami2  5.70.0-1
ii  qml-module-qtquick-controls   5.14.2-2
ii  qml-module-qtquick-layouts5.14.2+dfsg-3
ii  qml-module-qtquick2   5.14.2+dfsg-3

systemsettings recommends no packages.

systemsettings suggests no packages.

-- no debconf information

Bug#907178: GIMP-Error: Unable to run plug-in: Failed to execute child process “python” (ENOENT)

[Ralf Jung]

Hi all,

unfortunately it looks like the gimp-python package was lust during the Python
2->3 transition, and now the resynth plugin is entirely impossible to use.

; Ralf

Bug#961194: warning: Using the last argument as keyword parameters is deprecated

[Ralf Jung]

It looks like this warning would be fixed by updating to Jekyll 3.8.7:


; Ralf

Bug#963679: sqlitebrowser: Support for encrypted databases via sqlcipher

[Ralf Jung]

Package: sqlitebrowser
Version: 3.11.2-1+b1
Severity: wishlist

Dear Maintainer,

According to 
https://github.com/sqlitebrowser/sqlitebrowser/wiki/Encrypted-Databases,
sqlitebrowser has support for encrypted SQLite databases when built with 
SQLCipher.
SQLCipher is packaged in Debian, so it would be great to have a version of 
sqlitebrowser
with support for encrypted databases.

Kind regards,
Ralf

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.13 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sqlitebrowser depends on:
ii  libc6  2.30-8
ii  libgcc-s1 [libgcc1]10.1.0-3
ii  libqscintilla2-qt5-15  2.11.2+dfsg-6+b1
ii  libqt5core5a   5.12.5+dfsg-10+b1
ii  libqt5gui5 5.12.5+dfsg-10+b1
ii  libqt5network5 5.12.5+dfsg-10+b1
ii  libqt5printsupport55.12.5+dfsg-10+b1
ii  libqt5widgets5 5.12.5+dfsg-10+b1
ii  libqt5xml5 5.12.5+dfsg-10+b1
ii  libsqlite3-0   3.31.1-5
ii  libstdc++6 10.1.0-3

sqlitebrowser recommends no packages.

sqlitebrowser suggests no packages.

-- no debconf information

Bug#962469: node-gyp broken because it uses the wrong Python version

[Ralf Jung]

Package: node-gyp
Version: 6.1.0-3
Severity: normal

Dear Maintainer,

current node-gyp on Debian seems to be broken: trying to build a package that 
relies on node-gyp fails, saying

Traceback (most recent call last):
  File "/usr/share/nodejs/node-gyp/gyp/gyp_main.py", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3251, 
in 
@_call_aside
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3235, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3264, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 583, 
in _build_master
ws.require(__requires__)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 900, 
in require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 786, 
in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'gyp==0.1' distribution was not found 
and is required by the application

This is after I had to install the Python 2 version of pkg_resources to even 
get to far. Probably, node-gyp is using Python 2, even though its own 
dependencies point to Python 2.
I think I got everything to work by patching lib/find-python.js to disable the 
"python" and "python2" detectors.

Kind regards,
Ralf

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.13 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages node-gyp depends on:
ii  gyp   0.1+20200513gitcaa6002-1
ii  libnode-dev   12.13.1~dfsg-1
ii  node-glob 7.1.6-1
ii  node-graceful-fs  4.2.4-1
ii  node-mkdirp   0.5.1-2
ii  node-nopt 3.0.6-4
ii  node-npmlog   4.1.2-2
ii  node-osenv0.1.5-1
ii  node-request  2.88.1-4
ii  node-rimraf   2.6.3-1
ii  node-semver   7.1.3-1
ii  node-tar  4.4.10+ds1-2
ii  node-which2.0.2-1
ii  nodejs12.13.1~dfsg-1

Versions of packages node-gyp recommends:
ii  build-essential  12.8

node-gyp suggests no packages.

-- no debconf information

Bug#945824: [python3-numpy] Depends on python3.8 and python3.7

[Ralf Jung]

Oh, I see latest unstable version 1:1.18.4-1 fixes this.
Thanks a lot. :)

; Ralf

Bug#945824: [python3-numpy] Depends on python3.8 and python3.7

[Ralf Jung]

Dear numpy maintainers,

python3-numpy is the only reason python3.7 is installed on my system at all.  In
fact, right now it is not installed, but doing "apt full-upgrade" will pull in
the outdated python3.7 even though I already have python3.8 installed. (I will
explore if I can uninstall numpy to avoid this problem, but I suspect it is
installed for a reason.)

Clearly, that is rather silly, so I would much appreciate if the maintainers
could fix that. :)

Kind regards,
Ralf

Bug#954137: virtualbox: Cannot boot VM: kernel modules fails with VERR_VMM_SMAP_BUT_AC_CLEAR

[Ralf Jung]

Potentially related upstream bug:


; Ralf

Bug#954137: virtualbox: Cannot boot VM: kernel modules fails with VERR_VMM_SMAP_BUT_AC_CLEAR

[Ralf Jung]

Package: virtualbox
Version: 6.1.2-dfsg-1
Severity: important

Dear Maintainer,

One of my previously-working VMs stopped booting now.  Instead VirtualBox just 
shows this error:

Failed to open a session for the virtual machine $NAME.

Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: ModuleInit failed: -2717 
(VERR_VMM_SMAP_BUT_AC_CLEAR).

Failed to load VMMR0.r0 (VERR_VMM_SMAP_BUT_AC_CLEAR).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

This makes virtualbox effectively useless right now, unfortunately.

Kind regards,
Ralf


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox depends on:
ii  adduser   3.118
ii  iproute2  5.5.0-1
ii  libc6 2.29-10
ii  libcurl3-gnutls   7.68.0-1
ii  libdevmapper1.02.12:1.02.167-1+b1
ii  libgcc-s1 [libgcc1]   10-20200304-1
ii  libgcc1   1:10-20200304-1
ii  libgl11.3.1-1
ii  libgsoap-2.8.91   2.8.91-2
ii  libopus0  1.3-1+b1
ii  libpng16-16   1.6.37-2
ii  libpython3.7  3.7.7-1
ii  libsdl1.2debian   1.2.15+dfsg2-5
ii  libssl1.1 1.1.1d-2
ii  libstdc++610-20200304-1
ii  libvncserver1 0.9.12+dfsg-8
ii  libvpx6   1.8.2-1
ii  libx11-6  2:1.6.9-2
ii  libxcursor1   1:1.2.0-2
ii  libxml2   2.9.10+dfsg-4
ii  libxt61:1.1.5-1+b3
ii  procps2:3.3.16-4
ii  python3   3.7.5-3
ii  python3.7 3.7.7-1
ii  virtualbox-dkms [virtualbox-modules]  6.1.4-dfsg-2
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages virtualbox recommends:
ii  libqt5core5a5.12.5+dfsg-9
ii  libqt5gui5  5.12.5+dfsg-9
ii  libqt5opengl5   5.12.5+dfsg-9
ii  libqt5widgets5  5.12.5+dfsg-9
ii  libxcb1 1.13.1-5
ii  libxext62:1.3.3-1+b2
ii  libxmu6 2:1.1.2-2+b3
ii  virtualbox-qt   6.1.2-dfsg-1

Versions of packages virtualbox suggests:
pn  vde2
ii  virtualbox-guest-additions-iso  6.1.5-136327-1

-- no debconf information

Bug#935760: libfontconfig1-dev: install fails trying to overwrite fontconfig-devel.pdf.gz

[Ralf Jung]

Package: libfontconfig1-dev
Version: 2.13.1-2+b1
Followup-For: Bug #935760

Dear Maintainer,

This problem is still present in the current version of the package.  It makes
libgtk-3-dev:i386 uninstallable if the 64bit version of that package is already
installed, which is quite the severe limitation.

Unfortunately it looks like this issue is long-standing, and the package
seemingly is not maintained much any more.

Kind regards,
Ralf

Bug#953291: linux-image-amd64: udp SO_REUSEPORT broken (fix in 4.19.75)

[Ralf Jung]

Package: linux-image-amd64
Version: 4.19+105+deb10u1~bpo9+1
Severity: normal
Tags: upstream

Dear Maintainer,

Since kernel 4.5, SO_REUSEPORT was somewhat broken for UDP when [1] landed. The
fix for this was backported to the 4.19 series in 4.19.75 [2].  However, both
kernels available on Debian oldstable (4.9.189 and 4.19.67) are affected by the
problem. It would be great if the backports oldstable kernel could be upgraded
to 4.19.75 or later (like what was done for the stable kernel) so that a fix is
available in oldstable.

[1]: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e32ea7e74727
[2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fdd60d80c4294b7203d6f9d075a57da0a8d85fba

Kind regards,
Ralf

Bug#942854: virtualbox: Guest additions ISO image fails to download

[Ralf Jung]

Hi,

> Hello, can you please try version 6.1.0-2 in sid?

I tried 6.1.0-dfsg-3 and the download seems to work now, thanks. :-)

Kind regards,
Ralf

> 
> 
> thanks
> 
> G.
>> Installing the guest-additions-iso package fixes the problem, but it's still 
>> a
>> bug to show a useless error message and have a broken downloader without that
>> package.
>>
>> Kind regards,
>> Ralf
>>
>> -- System Information:
>> Debian Release: bullseye/sid
>>   APT prefers testing
>>   APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
>> Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
>> (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>> LSM: AppArmor: enabled
>>
>> Versions of packages virtualbox depends on:
>> ii  adduser   3.118
>> ii  iproute2  5.3.0-1
>> ii  libc6 2.29-2
>> ii  libcurl3-gnutls   7.66.0-1
>> ii  libdevmapper1.02.12:1.02.155-3
>> ii  libgcc1   1:9.2.1-8
>> ii  libgl11.1.0-1+b1
>> ii  libgsoap-2.8.75   2.8.75-2
>> ii  libopus0  1.3-1+b1
>> ii  libpng16-16   1.6.37-1
>> ii  libpython3.7  3.7.5~rc1-2
>> ii  libqt5core5a  5.11.3+dfsg1-4
>> ii  libqt5gui55.11.3+dfsg1-4
>> ii  libqt5opengl5 5.11.3+dfsg1-4
>> ii  libqt5widgets55.11.3+dfsg1-4
>> ii  libqt5x11extras5  5.11.3-2
>> ii  libsdl1.2debian   1.2.15+dfsg2-5
> 

Bug#947076: xchat.desktop file has invalid Exec line (at least for KDE)

[Ralf Jung]

Package: xchat
Version: 2.8.8-18
Severity: grave
Justification: renders package unusable

Dear Maintainer,

since the most recent update, trying to start xchat via the KDE launcher just 
shows an error:

  Error processeing Exec field in /usr/share/applications/xchat.desktop

And indeed that fileld looks suspicious:

  Exec=xchat --existing --url %U"

Notice the unmatched quote.

Kind regards,
Ralf

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xchat depends on:
ii  libc6   2.29-3
ii  libdbus-glib-1-20.110-5
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-1
ii  libglib2.0-02.62.3-2
ii  libgtk2.0-0 2.24.32-4
ii  libgtkspell02.0.16-1.2+b1
ii  libpango-1.0-0  1.42.4-7
ii  libperl5.30 5.30.0-9
ii  libpython2.72.7.17-1
ii  libssl1.1   1.1.1d-2
ii  libtcl8.6   8.6.10+dfsg-1
ii  libx11-62:1.6.8-1
ii  xchat-common2.8.8-18

Versions of packages xchat recommends:
ii  alsa-utils   1.1.9-1
ii  libnotify-bin0.7.8-1
ii  libnotify4   0.7.8-1
pn  xchat-indicator  
ii  xdg-utils1.1.3-1

xchat suggests no packages.

-- no debconf information

Bug#923314: unbound: Regression: systemctl reload unbound broken after upgrade from 1.8.1-1 to 1.9.0-2

[Ralf Jung]

I can confirm this, I just spent half an hour debugging this exact problem until
I realized the package is buggy, not my server.

Kind regards,
Ralf

Bug#942854: virtualbox: Guest additions ISO image fails to download

[Ralf Jung]

Package: virtualbox
Version: 6.0.14-dfsg-1
Severity: normal

Dear Maintainer,

I have now repeatedly (on several days) tried to download the latest Windows
Guest Additions ISO file (by clicking "Devices - Insert Guest Additions CD
image"). Every time, the download seems to complete but then finally shows an
error:

> The network operation failed with the following error: 
> During network request: Unknown reason.

My network is otherwise working fine, this seems to be an issue with VirtualBox
or the server it is fetching this from.

I reported this before at
 which got closed, but
the bug is not actually fixed.

Installing the guest-additions-iso package fixes the problem, but it's still a
bug to show a useless error message and have a broken downloader without that
package.

Kind regards,
Ralf

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox depends on:
ii  adduser   3.118
ii  iproute2  5.3.0-1
ii  libc6 2.29-2
ii  libcurl3-gnutls   7.66.0-1
ii  libdevmapper1.02.12:1.02.155-3
ii  libgcc1   1:9.2.1-8
ii  libgl11.1.0-1+b1
ii  libgsoap-2.8.75   2.8.75-2
ii  libopus0  1.3-1+b1
ii  libpng16-16   1.6.37-1
ii  libpython3.7  3.7.5~rc1-2
ii  libqt5core5a  5.11.3+dfsg1-4
ii  libqt5gui55.11.3+dfsg1-4
ii  libqt5opengl5 5.11.3+dfsg1-4
ii  libqt5widgets55.11.3+dfsg1-4
ii  libqt5x11extras5  5.11.3-2
ii  libsdl1.2debian   1.2.15+dfsg2-5
ii  libssl1.1 1.1.1d-2
ii  libstdc++69.2.1-8
ii  libvncserver1 0.9.11+dfsg-1.3
ii  libvpx6   1.8.1-2
ii  libx11-6  2:1.6.8-1
ii  libxcursor1   1:1.2.0-2
ii  libxext6  2:1.3.3-1+b2
ii  libxml2   2.9.4+dfsg1-7+b3
ii  libxmu6   2:1.1.2-2+b3
ii  libxt61:1.1.5-1+b3
ii  procps2:3.3.15-2+b1
ii  python3   3.7.5-1
ii  python3.7 3.7.5~rc1-2
ii  virtualbox-dkms [virtualbox-modules]  6.0.14-dfsg-1
ii  zlib1g1:1.2.11.dfsg-1+b1

Versions of packages virtualbox recommends:
ii  libxcb11.13.1-2
ii  virtualbox-qt  6.0.14-dfsg-1

-- no debconf information

Bug#942700: linux-image-5.2.0-3-amd64: Regularly, 1 CPU core is entirely hogged by kworker/0:1+kacpid

[Ralf Jung]

Package: src:linux
Version: 5.2.17-1
Severity: important

Dear Maintainer,

Since the most recent kernel update, I regularly have 100% load on one CPU 
core, According to top, the load is caused by "kworker/0:1+kacpid".
I have never seen this effect before so this is a recent regression.

This happens roughly once or twice a day.
To get rid of this, I have to put the machine to suspend and resume it again.

Here are the dpkg logs from that kernel update:

2019-10-12 17:16:36 install linux-image-5.2.0-3-amd64:amd64  5.2.17-1
2019-10-12 17:16:36 status half-installed linux-image-5.2.0-3-amd64:amd64 
5.2.17-1
2019-10-12 17:16:44 status unpacked linux-image-5.2.0-3-amd64:amd64 5.2.17-1
2019-10-12 17:16:45 upgrade linux-image-amd64:amd64 5.2+106 5.2+107
2019-10-12 17:16:45 status half-configured linux-image-amd64:amd64 5.2+106
2019-10-12 17:16:45 status unpacked linux-image-amd64:amd64 5.2+106
2019-10-12 17:16:45 status half-installed linux-image-amd64:amd64 5.2+106
2019-10-12 17:16:45 status unpacked linux-image-amd64:amd64 5.2+107
2019-10-12 17:21:59 configure linux-image-5.2.0-3-amd64:amd64 5.2.17-1 
2019-10-12 17:21:59 status unpacked linux-image-5.2.0-3-amd64:amd64 5.2.17-1
2019-10-12 17:21:59 status half-configured linux-image-5.2.0-3-amd64:amd64 
5.2.17-1
2019-10-12 17:22:56 status installed linux-image-5.2.0-3-amd64:amd64 5.2.17-1
2019-10-12 17:23:01 configure linux-image-amd64:amd64 5.2+107 
2019-10-12 17:23:01 status unpacked linux-image-amd64:amd64 5.2+107
2019-10-12 17:23:01 status half-configured linux-image-amd64:amd64 5.2+107
2019-10-12 17:23:01 status installed linux-image-amd64:amd64 5.2+107
2019-10-12 21:07:30 status installed linux-image-4.19.0-5-amd64:amd64 4.19.37-6
2019-10-12 21:07:30 remove linux-image-4.19.0-5-amd64:amd64 4.19.37-6 
2019-10-12 21:07:30 status half-configured linux-image-4.19.0-5-amd64:amd64 
4.19.37-6
2019-10-12 21:07:31 status half-installed linux-image-4.19.0-5-amd64:amd64 
4.19.37-6
2019-10-12 21:07:44 status config-files linux-image-4.19.0-5-amd64:amd64 
4.19.37-6
2019-10-12 21:07:46 purge linux-image-4.19.0-5-amd64:amd64 4.19.37-6 
2019-10-12 21:07:46 status config-files linux-image-4.19.0-5-amd64:amd64 
4.19.37-6
2019-10-12 21:07:47 status not-installed linux-image-4.19.0-5-amd64:amd64 

So, looks like 4.19.37-6 was fine but 5.2.17-1 has this bug.

Kind regards,
Ralf


-- Package-specific info:
** Version:
Linux version 5.2.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 
(Debian 8.3.0-22)) #1 SMP Debian 5.2.17-1 (2019-09-26)

** Command line:
BOOT_IMAGE=/vmlinuz-5.2.0-3-amd64 root=/dev/mapper/vg-root ro quiet splash

** Tainted: UOE (12352)
 * Userspace-defined naughtiness.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[235833.744783] input: HID 046a:0023 as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:046A:0023.0022/input/input52
[235833.808644] cherry 0003:046A:0023.0022: input,hidraw2: USB HID v1.11 
Keyboard [HID 046a:0023] on usb-:00:14.0-1.2/input0
[235833.816037] input: HID 046a:0023 as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1.2/1-1.2:1.1/0003:046A:0023.0023/input/input53
[235833.876857] cherry 0003:046A:0023.0023: input,hidraw3: USB HID v1.11 Device 
[HID 046a:0023] on usb-:00:14.0-1.2/input1
[235834.281211] Bluetooth: hci0: Waiting for firmware download to complete
[235834.281734] Bluetooth: hci0: Firmware loaded in 1581442 usecs
[235834.281749] Bluetooth: hci0: Waiting for device to boot
[235834.292848] Bluetooth: hci0: Device booted in 10814 usecs
[235834.292857] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[235834.296864] Bluetooth: hci0: Applying Intel DDC parameters completed
[235835.831037] wlp2s0: authenticate with 
[235835.841303] wlp2s0: send auth to  (try 1/3)
[235835.848871] wlp2s0: authenticated
[235835.852477] wlp2s0: associate with  (try 1/3)
[235835.861758] wlp2s0: RX AssocResp from  (capab=0x411 status=0 aid=1)
[235835.864046] wlp2s0: associated
[235835.915890] wlp2s0: Limiting TX power to 20 (23 - 3) dBm as advertised by 

[235838.108682] e1000e: enp0s31f6 NIC Link is Down
[235838.118650] wlp2s0: deauthenticating from  by local choice (Reason: 
3=DEAUTH_LEAVING)
[235856.856999] wlp2s0: authenticate with 
[235856.868498] wlp2s0: send auth to  (try 1/3)
[235856.876405] wlp2s0: authenticated
[235856.884644] wlp2s0: associate with  (try 1/3)
[235856.888084] wlp2s0: RX AssocResp from  (capab=0x411 status=0 aid=1)
[235856.891195] wlp2s0: associated
[235856.906791] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[235856.908319] wlp2s0: Limiting TX power to 20 (23 - 3) dBm as advertised by 

[238195.801553] mce: CPU1: Core temperature above threshold, cpu clock 
throttled (total events = 488)
[238195.801554] mce: CPU5: Core temperature above threshold, cpu clock 
throttled (total events = 488)
[238195.801556] mce: CPU0: Package temperature above threshold, cpu clock 
throttled (total events = 802)
[238195.801557] mce: CPU7: 

Bug#935914: kinit: Signal: Segmentation fault (11) after rebooting

[Ralf Jung]

After a big dist-upgrade I just did (and a reboot), I am not also experiencing
kdeinit5 crashes.  There's a notification popping up every now and then telling
me it crashed.  However it doesn't let me report a bug (looks like no bug
reporting URL is set, or so); so I am not sure how to even capture a stacktrace
of this.

; Ralf

Bug#930232: vlc: No video output in any video

[Ralf Jung]

Hi again,

> The weirdest thing is that I just tried VLC after disconnecting the HDMI 
> screen,
> and then it worked fine with the default video output mode.  And then I tried 
> it
> again on the HDMI screen and it still works.  I will have to do a reboot to 
> see
> if this sticks.  I have not installed any updates since yesterday when I
> installed VLC 3.0.7 from testing and the bug was still present.

After a reboot things still work.  I don't understand why I cannot reproduce the
issue any more -- I've had this problem several times across a week or two
before I reported it.  Maybe the update to 3.0.7 did help but for some reason
did not take "immediate effect"?  Not that that makes any sense.^^

But, either way, I cannot reproduce this any more with 3.0.7.

; Ralf

Bug#930232: vlc: No video output in any video

[Ralf Jung]

Hi,

> On 2019-06-08 23:37:18, Ralf Jung wrote:
>>> Control: tags -1 moreinfo
>>> Control: severity -1 important
>>> Control: found -1 3.0.6-1
>>>
>>> On 2019-06-08 23:20:15, Ralf Jung wrote:
>>>> Package: vlc
>>>> Version: 3.0.7-1
>>>> Severity: grave
>>>> Justification: renders package unusable
>>>>
>>>> Dear Maintainer,
>>>>
>>>> No matter which video file I try to open with VLC, VLC fails to display any
>>>> image.  All I get is a flickering VLC icon.  I will attach a "-vv" log for 
>>>> one
>>>> of the many files that I tried.  The same files all work fine with mpv.
>>>
>>> What type of GPU do you use?
>>
>> (Sorry, I thought the debug log would have all that stuff.)
>> This is a dual-GPU system, with an HD Graphics P530 and an NVidia Quadro 
>> M2000M.
>>  The Intel card is the master, the NVidia card is used as an output slave 
>> (i.e.,
>> my HDMI port is actually connected to the NVidia card).
> 
> I didn't find anything in the log. Looks like vlc or the underlying
> libraries failed to detect the hardware. Is this an NVIDIA Optimus-type
> setup that requires bumblebee to work properly? The logs suggest that
> some OpenGL related functions failed.

Bumblebee is for using the NVidia card as an accelerator while rendering the
image on a screen controlled by the Intel card *without* support from either of
the two involved drivers.  I am not using that.  Also this doesn't even apply
because the NVidia card is not involved as an accelerator here, or at least
should not be.

Instead what happens is that DMA-BUF "output slave" mode is used to use the
NVidia card as an *output* together with the internal laptop screen that is
accessed directly by the Intel card.  All the rendering is done by the Intel 
card.

There are two ways in which a "master" GPU can use the "service" of another one:

* It uses the other card to render stuff, then copies the result back to its own
frame buffer for some output it controls.  This is the "bumblebee" situation.
Bumblebee makes this work with the proprietary NVidia drivers without them
having dedicated support for this situation.  When using the open-source noveau
driver, there is no need for bumblebee: the driver can natively just do this
using DMA-BUF, and I can set "DRI_PRIME=1" to activate this mode.  I don't do
that though, the nouveau drivers are so slow that it's not actually noticeably
faster than just using the Intel drivers for rendering.
* Another situation is when the laptop has some of its display connectors
connected to one GPU and some to the other GPU, but you still want a shared
desktop across all of them. Some modern hardware unfortunately does that. My
internal laptop screen is connected to the Intel card but my HDMI port is
connected to the NVidia card. I use the Intel card as the "master" so that the
NVidia card can turn off when no screen is connected. But when a screen is
connected, the image rendered by the Intel card somehow needs to get to the
frame buffer on the NVidia card. This is an "output slave" in DMA-BUF
terminology, and bumblebee doesn't help here.  The NVidia proprietary drivers
don't support this, which is why I use nouveau.

I can try to explain more about this setup if you want, though I am far from an
expert myself -- just enough to get my system to run.^^

The weirdest thing is that I just tried VLC after disconnecting the HDMI screen,
and then it worked fine with the default video output mode.  And then I tried it
again on the HDMI screen and it still works.  I will have to do a reboot to see
if this sticks.  I have not installed any updates since yesterday when I
installed VLC 3.0.7 from testing and the bug was still present.

>>> Do you have the corresponding hardware
>>> decoding driver installed?
>> How can I find that out?  I am using the Mesa drivers for both cards, as far 
>> as
>> OpenGL goes.  (The proprietary NVidia drivers don't support being an output 
>> slave.)
> 
> For the Intel card that'd be i965-va-driver (or intel-media-va-driver
> and setting LIBVA_DRIVER_NAME to iHD). You'll probably also need
> non-free firmware for that. For NVIDIA you'd need the non-free drivers
> together nvidia-vdpau-driver. As far as I am aware, the hardware
> decoding experience with nouveau is suboptimal.

i965-va-driver is installed. (Though IMO it would be a bug if VLC broke when a
non-depended packet is not installed.)
As mentioned above I cannot use the non-free NVidida drivers as they don't
support output slave mode.

Kind regards,
Ralf

Bug#930232: vlc: No video output in any video

[Ralf Jung]

Hi,

> Control: tags -1 moreinfo
> Control: severity -1 important
> Control: found -1 3.0.6-1
> 
> On 2019-06-08 23:20:15, Ralf Jung wrote:
>> Package: vlc
>> Version: 3.0.7-1
>> Severity: grave
>> Justification: renders package unusable
>>
>> Dear Maintainer,
>>
>> No matter which video file I try to open with VLC, VLC fails to display any
>> image.  All I get is a flickering VLC icon.  I will attach a "-vv" log for 
>> one
>> of the many files that I tried.  The same files all work fine with mpv.
> 
> What type of GPU do you use?

(Sorry, I thought the debug log would have all that stuff.)
This is a dual-GPU system, with an HD Graphics P530 and an NVidia Quadro M2000M.
 The Intel card is the master, the NVidia card is used as an output slave (i.e.,
my HDMI port is actually connected to the NVidia card).

> Do you have the corresponding hardware
> decoding driver installed?
How can I find that out?  I am using the Mesa drivers for both cards, as far as
OpenGL goes.  (The proprietary NVidia drivers don't support being an output 
slave.)

>> This is with the default video output setting ("Preferences - Video - Output"
>> set to "Automatic").  If I change it to XVideo, things work fine.
> 
> So not grave after all.

Fair enough.  The default settings are broken though.

Kind regards,
Ralf

Bug#930232: vlc: No video output in any video

[Ralf Jung]

Package: vlc
Version: 3.0.7-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

No matter which video file I try to open with VLC, VLC fails to display any
image.  All I get is a flickering VLC icon.  I will attach a "-vv" log for one
of the many files that I tried.  The same files all work fine with mpv.

This bug occurs with with the version currently in testing (3.0.6-1) as well as
unstable (3.0.7-1).

This is with the default video output setting ("Preferences - Video - Output"
set to "Automatic").  If I change it to XVideo, things work fine.

Kind regards,
Ralf

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vlc depends on:
ii  vlc-bin  3.0.7-1
ii  vlc-plugin-base  3.0.7-1
ii  vlc-plugin-qt3.0.7-1
ii  vlc-plugin-video-output  3.0.7-1

Versions of packages vlc recommends:
ii  vlc-l10n   3.0.7-1
ii  vlc-plugin-notify  3.0.7-1
ii  vlc-plugin-samba   3.0.7-1
ii  vlc-plugin-skins2  3.0.7-1
ii  vlc-plugin-video-splitter  3.0.7-1
ii  vlc-plugin-visualization   3.0.7-1

vlc suggests no packages.

Versions of packages libvlc-bin depends on:
ii  libc62.28-10
ii  libvlc5  3.0.7-1

Versions of packages libvlc5 depends on:
ii  libc62.28-10
ii  libvlccore9  3.0.7-1

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.7-1

Versions of packages vlc-bin depends on:
ii  libc6   2.28-10
ii  libvlc-bin  3.0.7-1
ii  libvlc5 3.0.7-1

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-19
ii  libaom0  1.0.0-3
ii  libarchive13 3.3.3-4
ii  libaribb24-0 1.0.3-2
ii  libasound2   1.1.8-1
ii  libass9  1:0.14.0-2
ii  libavahi-client3 0.7-4+b1
ii  libavahi-common3 0.7-4+b1
ii  libavc1394-0 0.5.4-5
ii  libavcodec58 7:4.1.3-1
ii  libavformat587:4.1.3-1
ii  libavutil56  7:4.1.3-1
ii  libbasicusageenvironment12018.11.26-1.1
ii  libbluray2   1:1.1.0-1
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcddb2 1.3.2-6
ii  libchromaprint1  1.4.3-3
ii  libcrystalhd31:0.0~git20110715.fdd2f19-13
ii  libdbus-1-3  1.12.14-1
ii  libdc1394-22 2.2.5-1
ii  libdca0  0.0.6-1
ii  libdvbpsi10  1.3.2-1
ii  libdvdnav4   6.0.0-1
ii  libdvdread4  6.0.1-1
ii  libebml4v5   1.3.6-2
ii  libfaad2 2.8.8-2
ii  libflac8 1.3.2-3
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3
ii  libfribidi0  1.0.5-3.1
ii  libgcc1  1:8.3.0-6
ii  libgcrypt20  1.8.4-5
ii  libglib2.0-0 2.58.3-2
ii  libgnutls30  3.6.7-3
ii  libgpg-error01.35-1
ii  libgroupsock82018.11.26-1.1
ii  libharfbuzz0b2.3.1-1
ii  libixml101:1.8.4-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libkate1 0.4.1-9
ii  liblirc-client0  0.10.1-5.2
ii  liblivemedia64   2018.11.26-1.1
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libmad0  0.15.1b-10
ii  libmatroska6v5   1.4.9-1
ii  libmicrodns0 0.0.10-1
ii  libmpcdec6   2:0.1~r495-1+b2
ii  libmpeg2-4   0.5.1-8
ii  libmpg123-0  1.25.10-2
ii  libmtp9  1.1.16-2
ii  libncursesw6 6.1+20181013-2
ii  libnfs12 3.0.0-2
ii  libogg0  1.3.2-1+b1
ii  libopenmpt-modplug1  0.4.3-1
ii  libopus0 1.3-1
ii  libpng16-16  1.6.36-6
ii  libpostproc557:4.1.3-1
ii  libprotobuf-lite17   3.6.1.3-2

Bug#930213: bzr: "bzr branch" fails: NameError: global name 'self' is not defined

[Ralf Jung]

Package: bzr
Version: 2.7.0+bzr6622-15
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The command `bzr branch lp:mailman/2.1` (which
https://code.launchpad.net/~mailman-coders/mailman/2.1 tells me to run to get
the mailman source code) fails, with the following error:

```
/usr/lib/python2.7/dist-packages/paramiko/ecdsakey.py:164: 
CryptographyDeprecationWarning: Support for unsafe construction of public 
numbers from encoded data will be removed in a future version. Please use 
EllipticCurvePublicKey.from_encoded_point
  self.ecdsa_curve.curve_class(), pointinfo
Connected (version 2.0, client Twisted)
/usr/lib/python2.7/dist-packages/paramiko/kex_ecdh_nist.py:39: 
CryptographyDeprecationWarning: encode_point has been deprecated on 
EllipticCurvePublicNumbers and will be removed in a future version. Please use 
EllipticCurvePublicKey.public_bytes to obtain both compressed and uncompressed 
point encoding.
  m.add_string(self.Q_C.public_numbers().encode_point())
/usr/lib/python2.7/dist-packages/paramiko/kex_ecdh_nist.py:96: 
CryptographyDeprecationWarning: Support for unsafe construction of public 
numbers from encoded data will be removed in a future version. Please use 
EllipticCurvePublicKey.from_encoded_point
  self.curve, Q_S_bytes
/usr/lib/python2.7/dist-packages/paramiko/kex_ecdh_nist.py:111: 
CryptographyDeprecationWarning: encode_point has been deprecated on 
EllipticCurvePublicNumbers and will be removed in a future version. Please use 
EllipticCurvePublicKey.public_bytes to obtain both compressed and uncompressed 
point encoding.
  hm.add_string(self.Q_C.public_numbers().encode_point())
bzr: ERROR: exceptions.NameError: global name 'self' is not defined

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 930, in 
exception_to_return_code
return the_callable(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 1121, in 
run_bzr
ret = run(*run_argv)
  File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 673, in 
run_argv_aliases
return self.run(**all_cmd_args)
  File "/usr/lib/python2.7/dist-packages/bzrlib/commands.py", line 697, in run
return self._operation.run_simple(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/cleanup.py", line 136, in 
run_simple
self.cleanups, self.func, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/cleanup.py", line 166, in 
_do_with_cleanups
result = func(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/bzrlib/builtins.py", line 1452, in run
from_location)
  File "/usr/lib/python2.7/dist-packages/bzrlib/controldir.py", line 780, in 
open_tree_or_branch
controldir = klass.open(location)
  File "/usr/lib/python2.7/dist-packages/bzrlib/controldir.py", line 689, in 
open
_unsupported=_unsupported)
  File "/usr/lib/python2.7/dist-packages/bzrlib/controldir.py", line 723, in 
open_from_transport
return format.open(transport, _found=True)
  File "/usr/lib/python2.7/dist-packages/bzrlib/bzrdir.py", line 1486, in open
return self._open(transport)
  File "/usr/lib/python2.7/dist-packages/bzrlib/remote.py", line 317, in _open
return RemoteBzrDir(transport, self)
  File "/usr/lib/python2.7/dist-packages/bzrlib/remote.py", line 436, in 
__init__
self._probe_bzrdir()
  File "/usr/lib/python2.7/dist-packages/bzrlib/remote.py", line 448, in 
_probe_bzrdir
self._rpc_open_2_1(path)
  File "/usr/lib/python2.7/dist-packages/bzrlib/remote.py", line 455, in 
_rpc_open_2_1
response = self._call('BzrDir.open_2.1', path)
  File "/usr/lib/python2.7/dist-packages/bzrlib/remote.py", line 73, in _call
return self._client.call(method, *args)
  File "/usr/lib/python2.7/dist-packages/bzrlib/smart/client.py", line 59, in 
call
result, protocol = self.call_expecting_body(method, *args)
  File "/usr/lib/python2.7/dist-packages/bzrlib/smart/client.py", line 72, in 
call_expecting_body
method, args, expect_response_body=True)
  File "/usr/lib/python2.7/dist-packages/bzrlib/smart/client.py", line 55, in 
_call_and_read_response
return request.call_and_read_response()
  File "/usr/lib/python2.7/dist-packages/bzrlib/smart/client.py", line 155, in 
call_and_read_response
return self._call_determining_protocol_version()
  File "/usr/lib/python2.7/dist-packages/bzrlib/smart/client.py", line 218, in 
_call_determining_protocol_version
response_tuple, response_handler = self._call(protocol_version)
  File "/usr/lib/python2.7/dist-packages/bzrlib/smart/client.py", line 189, in 
_call
response_handler = self._send(protocol_version)
  File "/usr/lib/python2.7/dist-packages/bzrlib/smart/client.py", line 267, in 
_send
self._send_no_retry(encoder)
  File "/usr/lib/python2.7/dist-packages/bzrlib/smart/client.py", line 315, in 
_send_no_retry
encoder.call(self.method, *self.args)
  File "/usr/lib/python2.7/dist-packages/bzrlib/smart/protocol.py", line 1308, 
in 

Bug#929314: lxqt-openssh-askpass: Typo in package description

[Ralf Jung]

Package: lxqt-openssh-askpass
Version: 0.14.1-1
Severity: minor

Dear Maintainer,

the package description says "will perform security tast over scale access 
privilegies".
I don't know what that is supposed to mean, but it seems fairly far from an 
English sentence.

Kind regards,
Ralf

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lxqt-openssh-askpass depends on:
ii  libc6   2.28-10
ii  liblxqt00.14.1-1
ii  libqt5core5a5.11.3+dfsg1-1
ii  libqt5widgets5  5.11.3+dfsg1-1
ii  libstdc++6  8.3.0-6

Versions of packages lxqt-openssh-askpass recommends:
ii  lxqt-openssh-askpass-l10n  0.14.1-1
pn  lxqt-qtplugin  
pn  lxqt-session   

Versions of packages lxqt-openssh-askpass suggests:
pn  lxqt | lxqt-core  

-- no debconf information

Bug#869890: gnome-keyring breaks SSH logins

[Ralf Jung]

This bug is also reported upstream as
https://bugzilla.gnome.org/show_bug.cgi?id=790921 and
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/32.

; Ralf

Bug#929074: virtualbox: Guest additions ISO image fails to download

[Ralf Jung]

Package: virtualbox
Version: 6.0.8-dfsg-2
Severity: normal

Dear Maintainer,

I have now repeatedly (on several days) tried to download the latest Windows
Guest Additions ISO file (by clicking "Devices - Insert Guest Additions CD
image"). Every time, the download seems to complete but then finally shows an
error:

> The network operation failed with the following error: 
> During network request: Unknown reason.

My network is otherwise working fine, this seems to be an issue with VirtualBox
or the server it is fetching this from.

Kind regards,
Ralf

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox depends on:
ii  adduser   3.118
ii  iproute2  4.20.0-2
ii  libc6 2.28-10
ii  libcurl3-gnutls   7.64.0-2
ii  libdevmapper1.02.12:1.02.155-2
ii  libgcc1   1:8.3.0-6
ii  libgl11.1.0-1
ii  libgsoap-2.8.75   2.8.75-1
ii  libopus0  1.3-1
ii  libpng16-16   1.6.36-5
ii  libpython3.7  3.7.3~rc1-1
ii  libqt5core5a  5.11.3+dfsg1-1
ii  libqt5gui55.11.3+dfsg1-1
ii  libqt5opengl5 5.11.3+dfsg1-1
ii  libqt5widgets55.11.3+dfsg1-1
ii  libqt5x11extras5  5.11.3-2
ii  libsdl1.2debian   1.2.15+dfsg2-4
ii  libssl1.1 1.1.1b-2
ii  libstdc++68.3.0-6
ii  libvncserver1 0.9.11+dfsg-1.3
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.7-1
ii  libxcursor1   1:1.1.15-2
ii  libxext6  2:1.3.3-1+b2
ii  libxml2   2.9.4+dfsg1-7+b3
ii  libxmu6   2:1.1.2-2+b3
ii  libxt61:1.1.5-1+b3
ii  procps2:3.3.15-2
ii  python3   3.7.2-1
ii  python3.7 3.7.3~rc1-1
ii  virtualbox-dkms [virtualbox-modules]  6.0.8-dfsg-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages virtualbox recommends:
ii  libxcb11.13.1-2
ii  virtualbox-qt  6.0.8-dfsg-2

Versions of packages virtualbox suggests:
pn  vde2
pn  virtualbox-guest-additions-iso  

-- no debconf information

Bug#924349: linux-image-4.19.0-2-amd64: IPv6 reverse path filtering incorrectly removes IPv6 traffic from bridge

[Ralf Jung]

Hi,

>> No, I have not.
>> We are having a string of weird issues in our network (that we run in our 
>> free
>> time) so far this year so all the time I had went into debugging this and 
>> other
>> issues.
>>
>> Would it be helpful for you to know the fixing commit?
> 
> If the fixing commit can be identified and if it's not too intrusive to
> backport, it could be considered for the 4.19 stable backports and would
> thus be fixed in Buster (as buster is following the 4.19.x kernels both
> in the freeze and during the lifetime of the buster stable release.

I could try a bisect, but I think the full set of commits is rather big... do
you have a good guess for a subdirectory that I could meaningfully restrict the
bisect to?

No promises, not sure yet how much time I will really have.

; Ralf

Bug#924349: linux-image-4.19.0-2-amd64: IPv6 reverse path filtering incorrectly removes IPv6 traffic from bridge

[Ralf Jung]

Hi Salvatore,

>> A self-compiled upstream 4.20.14 kernel does not show this problem, but the
>> latest kernel in testing still does.
> 
> have you tried to isolate the fixing commit for this issue?

No, I have not.
We are having a string of weird issues in our network (that we run in our free
time) so far this year so all the time I had went into debugging this and other
issues.

Would it be helpful for you to know the fixing commit?

; Ralf

Bug#925462: iputils-ping: ping rounds up 13.979 ms to 13.10 ms (incorrect handling of decimal overflow?)

[Ralf Jung]

Package: iputils-ping
Version: 3:20180629-2
Severity: normal

Dear Maintainer,

I just got the following output from "ping ipv6-test.com":

PING ipv6-test.com (5.135.165.173) 56(84) bytes of data.
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=1 ttl=54 time=13.7 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=2 ttl=54 time=13.10 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=3 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=4 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=5 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=6 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=7 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=8 ttl=54 time=13.8 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=9 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=10 ttl=54 time=13.7 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=11 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=12 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=13 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=14 ttl=54 time=13.6 ms
^C
--- ipv6-test.com ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 33ms
rtt min/avg/max/mdev = 13.586/13.671/13.979/0.156 ms

The second response looks rather curious: why would it print that with a
precision of 2 digits when everything else is printed with 1 digit?  Looking,
however, and the min/max numbers in the end, the min time is 13.586 ms -- so
there actually was no measurement of 13.10 ms!  And moreover, the maximum is
13.979 ms, so there should be a 14.0 ms in the list, but there is not.  My guess
is that ping incorrectly "rounds up" 13.979 to 13.10 (10 being "first digit
after the period + 1" = 9+1) , not realizing that it should instead increment
the number of seconds by 1 (and set the digit after the period to 0).  In other
words, it looks like decimal overflow is not handled properly.

Kind regards,
Ralf

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iputils-ping depends on:
ii  libc6   2.28-8
ii  libcap2 1:2.25-2
ii  libidn2-0   2.0.5-1
ii  libnettle6  3.4.1-1

Versions of packages iputils-ping recommends:
ii  libcap2-bin  1:2.25-2

iputils-ping suggests no packages.

-- no debconf information

Bug#923249: [Pkg-libvirt-maintainers] Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking

[Ralf Jung]

Hi,

> https://bugzilla.redhat.com/show_bug.cgi?id=1680681 indicates it's a
> kernel issue. Can you add a link to the debian bug you filed so I can
> close this issue but mark the other one as affecting libvirt?
> Cheers
>  -- Guido

That Debian kernel bug is at
.

; Ralf

Bug#924349: linux-image-4.19.0-2-amd64: IPv6 reverse path filtering incorrectly removes IPv6 traffic from bridge

[Ralf Jung]

Package: src:linux
Version: 4.19.16-1
Severity: normal

Dear Maintainer,

since a recent update, IPv6 communication between two of my VMs stopped working.
You can see some of the debugging effort at
.  It turned out that
setting IPv6_rpfilter=no in /etc/firewalld/firewalld.conf fixes the problem---so
the ip6tables reverse path filtering is incorrectly dropping packets here.

A self-compiled upstream 4.20.14 kernel does not show this problem, but the
latest kernel in testing still does.

Kind regards,
Ralf

-- Package-specific info:
** Version:
Linux version 4.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.2.0 (Debian 8.2.0-14)) #1 SMP Debian 4.19.16-1 (2019-01-17)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-2-amd64 root=/dev/mapper/vg-root ro quiet splash

** Tainted: UOE (12352)
 * Userspace-defined naughtiness.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20ENCTO1WW
product_version: ThinkPad P50
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N1EET79W (1.52 )
board_vendor: LENOVO
board_name: 20ENCTO1WW
board_version: Not Defined

** Loaded modules:
nfnetlink_queue
nfnetlink_log
vhost_net
vhost
tap
xt_CHECKSUM
tun
ipt_MASQUERADE
nf_conntrack_netlink
xfrm_user
xfrm_algo
xt_addrtype
iptable_filter
br_netfilter
bridge
stp
llc
overlay
pci_stub
vboxpci(OE)
vboxnetadp(OE)
vboxnetflt(OE)
vboxdrv(OE)
ctr
ccm
xt_tcpudp
ip6t_rpfilter
ip6t_REJECT
nf_reject_ipv6
ipt_REJECT
nf_reject_ipv4
xt_conntrack
nft_counter
devlink
nft_chain_nat_ipv6
nf_nat_ipv6
nft_chain_route_ipv6
nft_chain_nat_ipv4
nf_nat_ipv4
nf_nat
nft_chain_route_ipv4
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
ip6_tables
nft_compat
ip_set
nf_tables
nfnetlink
bnep
binfmt_misc
nls_ascii
arc4
nls_cp437
vfat
fat
btusb
btrtl
btbcm
btintel
bluetooth
uvcvideo
videobuf2_vmalloc
iwlmvm
videobuf2_memops
intel_rapl
videobuf2_v4l2
videobuf2_common
x86_pkg_temp_thermal
intel_powerclamp
drbg
mac80211
videodev
ansi_cprng
snd_hda_codec_realtek
snd_hda_codec_generic
media
coretemp
ecdh_generic
kvm_intel
snd_hda_intel
kvm
snd_hda_codec
iwlwifi
snd_hda_core
irqbypass
tpm_tis
snd_hwdep
tpm_tis_core
efi_pstore
rtsx_pci_ms
joydev
tpm
snd_pcm
intel_cstate
thinkpad_acpi
snd_timer
cfg80211
intel_uncore
serio_raw
memstick
wmi_bmof
nvram
mei_me
intel_rapl_perf
iTCO_wdt
iTCO_vendor_support
sg
mei
efivars
pcspkr
intel_pch_thermal
ie31200_edac
rng_core
snd
soundcore
rfkill
ac
battery
evdev
pcc_cpufreq
nfsd
cuse
fuse
auth_rpcgss
nfs_acl
parport_pc
lockd
ppdev
grace
lp
sunrpc
parport
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
fscrypto
ecb
btrfs
zstd_decompress
zstd_compress
xxhash
algif_skcipher
af_alg
dm_crypt
dm_mod
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid1
raid0
multipath
linear
md_mod
hid_cherry
hid_generic
usbhid
hid
sd_mod
nouveau
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
pcbc
i915
rtsx_pci_sdmmc
mmc_core
mxm_wmi
ttm
ahci
i2c_algo_bit
libahci
xhci_pci
drm_kms_helper
rtsx_pci
psmouse
xhci_hcd
libata
aesni_intel
aes_x86_64
drm
usbcore
e1000e
crypto_simd
cryptd
scsi_mod
glue_helper
i2c_i801
usb_common
thermal
wmi
video
button

** Network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: enp0s31f6:  mtu 1500 qdisc pfifo_fast 
state DOWN group default qlen 1000
link/ether c8:5b:76:1b:c1:50 brd ff:ff:ff:ff:ff:ff
3: wlp2s0:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether e4:a4:71:65:d2:a4 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.30/24 brd 192.168.178.255 scope global dynamic 
noprefixroute wlp2s0
   valid_lft 863824sec preferred_lft 863824sec
inet6 2a01:c23:7c45:b400:8f5e:4a73:f0b5:5280/64 scope global dynamic 
noprefixroute 
   valid_lft 7126sec preferred_lft 3526sec
inet6 fe80::bcf2:b485:9f96:e957/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever
4: docker0:  mtu 1500 qdisc noqueue state 
DOWN group default 
link/ether 02:42:d6:da:98:4e brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
   valid_lft forever preferred_lft forever
5: virbr0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether 52:54:00:f5:09:38 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
   valid_lft forever preferred_lft forever
6: virbr0-nic:  mtu 1500 qdisc pfifo_fast master virbr0 
state 

Bug#923249: [Pkg-libvirt-maintainers] Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking

[Ralf Jung]

Btw, I reported this upstream at
, and made some headway
debugging things there.

; Ralf

Bug#923345: evince cannot start default browser due to AppArmor

[Ralf Jung]

Package: evince
Version: 3.30.2-3
Severity: normal

Dear Maintainer,

To reproduce:
* Install a browser, e.g. Firefox Beta, from upstream (instead of the Debian 
repo).
* When the browser asks you, tell it that yes you want it to become the default 
browser.
* Start evince and click a link in a PDF file.

Expected behavior:
The link should be opened in the default browser.

Actual behavior:
Nothing happens when I click the link.

Further information:
It has puzzled me for quite some time why my default browser works in all
applications, but not in evince.  Through some help from upstream (unfortunately
I had to bother them with this Debian-specific issue), I realized that I have
AppArmor enabled on my system and that it has a profile for evince.  My default
browser is Firefox Beta, which is not shipped by Debian and hence installed in
my home directory -- and that gets blocked by AppArmor.  The blocking happens
without any notice on the command line.  I just noticed it *does* get logged in
`dmesg`, but (not even knowing that AppArmor got enabled on my system), I did
not think to look there.

I think the default configuration should enable people to choose their default
browser, and should at least tell them why their setup does not work.
Currently, the failure mode for "someone downloads Firefox from the web and
installs it and tells it to become the default browser" is a siltently
half-broken default browser setup, which is not how things should work.


Kind regards,
Ralf

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages evince depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  evince-common3.30.2-3
ii  gsettings-desktop-schemas3.28.1-1
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-7
ii  libcairo-gobject21.16.0-2
ii  libcairo21.16.0-2
ii  libevdocument3-4 3.30.2-3
ii  libevview3-3 3.30.2-3
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-7
ii  libglib2.0-0 2.58.3-1
ii  libgnome-desktop-3-173.30.2.1-1
ii  libgtk-3-0   3.24.5-1
ii  libnautilus-extension1a  3.30.5-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libsecret-1-00.18.7-1
ii  shared-mime-info 1.10-1

Versions of packages evince recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]   1.12.12-1

Versions of packages evince suggests:
ii  gvfs 1.38.1-3
pn  nautilus-sendto  
ii  poppler-data 0.4.9-2
ii  unrar1:5.6.6-1

-- no debconf information

Bug#923249: [Pkg-libvirt-maintainers] Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking

[Ralf Jung]

Hi,

>> It turns out that setting disable_ipv6=0 is not enough to regain working 
>> IPv6:
>> Now the RAs from the router arrive at the client, but when the client sends a
>> neighbor discovery, it never makes its way to the router, so the client 
>> cannot
>> actually communicate via IPv6. I can see the ND packages on vnet2 on the 
>> host,
>> but not on virbr1 (which vnet2 is attached to). Again this is something that
>> worked just fine before the update.
>>
>> I have no idea what is preventing the ND packages to be forwarded by the 
>> bridge.
>> I always thought bridges are just switches operating on layer 2, but it seems
>> that's as from the truth...
> 
> Can you check if downgrading the kernel helps?

I downgraded back to 4.18, which definitely used to work. No change in behavior.
Seems like it was a libvirt/firewalld upgrade that broke it.

; Ralf

Bug#923249: [Pkg-libvirt-maintainers] Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking

[Ralf Jung]

Hi again,

It turns out that setting disable_ipv6=0 is not enough to regain working IPv6:
Now the RAs from the router arrive at the client, but when the client sends a
neighbor discovery, it never makes its way to the router, so the client cannot
actually communicate via IPv6. I can see the ND packages on vnet2 on the host,
but not on virbr1 (which vnet2 is attached to). Again this is something that
worked just fine before the update.

I have no idea what is preventing the ND packages to be forwarded by the bridge.
I always thought bridges are just switches operating on layer 2, but it seems
that's as from the truth...

Kind regards,
Ralf

Bug#923249: [Pkg-libvirt-maintainers] Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking

[Ralf Jung]

Hi Guido,

thanks for the quick reply!

>> After a recent upgrade, IPv6 communication between a virtual router and 
>> another
>> virtual client over an isolated network stopped working. I am seeing the 
>> rotuer
>> advertisments sent by the router on vnet0, which is attached to the bridge
>> virbr1, but when I capture packages on the bridge, the IPv6 traffic is gone. 
>>  It
>> just took me several hours of debugging to realize that the reason for this 
>> is
>> that /proc/sys/net/ipv6/conf/virbr1/disable_ipv6 is set to 1.  After setting 
>> it
>> to 0, IPv6 is working as expected now.
>>
>> This is a regression, IPv6 used to work between virtual clients just fine
>> without having to manually fiddle with the network configuration.
> 
> I'm not near a ipv6 setup atm but according to the git logs nothing
> changed in that area for quite some time. Please indicate which version
> you updated from so it's easier to check for related changes and also
> provide details about your setup (preferably network XML and domain XML).

I updated from 4.10.0-2 to 5.0.0-1.

Looking at the code in bridge_driver.c, I also came to the conclusion that
nothing changed, and that setting disable_ipv6 like this is intended behavior --
it happens whenever the network has no host IPv6 address.  The docs say that
guest-to-guest IPv6 communication can be enabled with the `ipv6` attribute, but
that attribute has no bearing on whether `disable_ipv6` gets set. It only
controls some firwall stuff. Maybe disable_ipv6 was always set but it somehow
used to not kill the entire IPv6 traffic on the bridge? A kernel update happened
together with all the other updates (from 4.19.12-1 to 4.19.16-1).

The network config now is (after adding the `ipv6` attribute, which however made
no difference):

> 
>   ffnet
>   cfd2c92a-db77-4b27-ad78-a8a81ace32b6
>   
>   
>   
> 

The part where the virtual router gets attached is

> 
>   
>   
>   
>queues='5'>
>  mrg_rxbuf='off'/>
> 
>   
>function='0x0'/>
> 

And for the virtual client

> 
>   
>   
>   
>queues='5'>
>  mrg_rxbuf='off'/>
> 
>   
>function='0x0'/>
> 


> There were some ipv6 related changes with firewalld though which might be 
> worth
> investigating.

firewalld got updated from 0.6.3-4 to 0.6.3-5 at the same time.
I have set `FirewallBackend=iptables` some time ago because the default
(`nftables`) broke libvirt.

; Ralf

Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking

[Ralf Jung]

Package: libvirt0
Version: 5.0.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After a recent upgrade, IPv6 communication between a virtual router and another
virtual client over an isolated network stopped working. I am seeing the rotuer
advertisments sent by the router on vnet0, which is attached to the bridge
virbr1, but when I capture packages on the bridge, the IPv6 traffic is gone.  It
just took me several hours of debugging to realize that the reason for this is
that /proc/sys/net/ipv6/conf/virbr1/disable_ipv6 is set to 1.  After setting it
to 0, IPv6 is working as expected now.

This is a regression, IPv6 used to work between virtual clients just fine
without having to manually fiddle with the network configuration.

Kind regards,
Ralf

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libvirt0 depends on:
ii  libacl1 2.2.52-3+b1
ii  libapparmor12.13.2-7
ii  libaudit1   1:2.8.4-2
ii  libavahi-client30.7-4+b1
ii  libavahi-common30.7-4+b1
ii  libc6   2.28-7
ii  libcap-ng0  0.7.9-2
ii  libcurl3-gnutls 7.64.0-1
ii  libdbus-1-3 1.12.12-1
ii  libdevmapper1.02.1  2:1.02.155-2
ii  libgcc1 1:8.2.0-21
ii  libgnutls30 3.6.6-2
ii  libnl-3-200 3.4.0-1
ii  libnl-route-3-200   3.4.0-1
ii  libnuma12.0.12-1
ii  libsasl2-2  2.1.27+dfsg-1
ii  libselinux1 2.8-1+b1
ii  libssh2-1   1.8.0-2
ii  libxml2 2.9.4+dfsg1-7+b3
ii  libyajl22.1.0-3

Versions of packages libvirt0 recommends:
ii  lvm2  2.03.02-2

libvirt0 suggests no packages.

-- no debconf information

Bug#922488: linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation

[Ralf Jung]

Oh, I should probably also mention that these machines all run an extra kernel
module compiled via dkms: batman-adv 2019.0 from .
The same kernel module also runs on a fourth machine with the same setup, but
which hasn't gotten the kernel update yet, and that machine runs stable.

; Ralf

Bug#922488: linux-image-4.9.0-8-amd64: Kernel panic in IPv6 stack after some hours of operation

[Ralf Jung]

Package: linux-image-4.9.0-8-amd64
Version: 4.9.144-3
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

after installing the kernel updates that got released to Debian stable earlier
today or yesterday, we saw all the three updated systems fail in the same way:
after 3-5h, they stop responding. We managed to grab a picture of the kernel
console on one of them, which showed a kernel panic in the IPv6 stack:

  https://imgur.com/7Teb8BV

The topmost stack items are (hoping I got no typos)

  __pskb_pull_tail
  ip6_dst_lookup_tail
  _decode_session6
  __xfrm_decode_session
  icmpv6_route_lookup
  icmp6_send

That system was using the kernel this bug is reported against 
(linux-image-4.9.0-8-amd64 4.9.144-3).
The other two affected systems used a backports kernel instead 
(linux-image-4.19.0-0.bpo.2-amd65 4.19.16-1~bpo9+1).
Unfortunately we have no console access there, all we can do there is a hard 
reboot from the web interface.

These servers are all operating as gateway servers for our Freifunk network, 
meaning they mostly forward traffic and their network setup is very 
non-standard.
Please let me know if there is any configuration details that would be helpful 
to track this down.

Kind regards,
Ralf

Bug#917827: osspd FTCBFS: uses the wrong pkg-config

[Ralf Jung]

Hi Helmut,

sorry for this!  Somehow the patch you sent me previously got un-applied in my
last update.  I am not entirely sure what happened.  But anyway I just uploaded
a new version that should fix this.

Kind regards,
Ralf

On 30.12.18 20:29, Helmut Grohne wrote:
> Source: osspd
> Version: 1.3.2-10
> Tags: patch upstream
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> osspd fails to cross build from source, because it uses the wrong
> pkg-config and thus fails to find cuse_lowlevel.h. The attached patch
> makes pkg-config substitutable (dh_auto_build supplies the correct
> value) and thus makes osspd cross buildable. Please consider applying
> the attached patch.
> 
> Helmut
> 

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

[Ralf Jung]

Hi,

> Once a version uploaded to sid, migrates to testing, it can be
> prepared for stable-backports based on that.
> 
> So what will need to happen here: upload of 4.19.13-2 to unstable
> (actually possibly only >= 4.19.14-1 if we do not have pressure to
> upload 4.19.13-2), then wait it migrates to testing, then the
> stretch-backports upload can be done.
> 
> Hope this helps,

It does, thanks. :)

Kind regards,
Ralf

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

[Ralf Jung]

Hi,

> On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote:
>> Package: linux-image-4.18.0-0.bpo.3-amd64
>> Version: 4.18.20-2~bpo9+1
>> Severity: normal
>> Tags: upstream
>>
>> Dear Maintainer,
>>
>> I reported an upstream bug at 
>> <https://marc.info/?l=linux-netdev=154635529809577=2> that got a patch 
>> submitted with <https://marc.info/?l=linux-netdev=154648423826010=2>.
>> It would be great to have this patch applied to the next Debian kernel 
>> update.
> 
> Queued it up for our next sid upload, as per
> https://salsa.debian.org/kernel-team/linux/commit/c91e16558f8fe6f1fa4df2faa27ad69afa397d03

Thanks a lot!

How are updates to the stable-backports kernel usually handled?

Kind regards,
Ralf

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

[Ralf Jung]

Package: linux-image-4.18.0-0.bpo.3-amd64
Version: 4.18.20-2~bpo9+1
Severity: normal
Tags: upstream

Dear Maintainer,

I reported an upstream bug at 
 that got a patch 
submitted with .
It would be great to have this patch applied to the next Debian kernel update.

Kind regards,
Ralf

Bug#917217: npm breaks other packages' bash-completion

[Ralf Jung]

Hi,

> I don't see such a line here.
> https://salsa.debian.org/js-team/npm/blob/master/lib/utils/completion.sh
> 
> May be that came from an older version? Can you purge npm, reinstall and 
> confirm
> if you still see it?

I just extracted the package and to my surprise found the file somewhere in
usr/share.

In any case it seems like npm updates don't properly upgrade/remove the file in
/etc, because I had an up-to-date npm and still had those lines in there (and I
never locally edited that file, so I should have gotten all upgrades).

Kind regards,
Ralf

Bug#916231: Including sys/ioctl.h helps

[Ralf Jung]

Hi Sergei,

thanks a lot!  At least it still builds here, so I just made an upload with this
fix.

Kind regards,
Ralf

On 25.12.18 12:34, Sergei Golovan wrote:
> Hey Ralf,
> 
> Including sys/ioctl.h into ossp.h doesn't help as it is included into
> osspd.c too late (sys/socket.h already did harm by undefining IOC_IN
> and IOC_OUT).
> 
> But including sys/ioctl.h directly into osspd.c before sys/socket.h
> works. Here is a possible patch:
> 
> --- a/osspd.c
> +++ b/osspd.c
> @@ -22,6 +22,7 @@
>  #include 
>  #include 
>  #include 
> +#include 
>  #include 
>  #include 
>  #include 
> 
> Hopefully, it won't cause damage for other architectures.
> 
> Cheers!
> 

Bug#917371: rust-doc package outdated on stable

[Ralf Jung]

Package: rust-doc
Version: 1.14.0+dfsg1-3

While [rustc] has been updated to 1.24.1 on stretch, [rust-doc] is still on
1.14.0.  Looks like the packages somehow got out-of-sync.

[rustc]: https://packages.debian.org/stretch/rustc
[rust-doc]: https://packages.debian.org/stretch/rust-doc

Kind regards,
Ralf