Bug#1072166: python-zombie-imp: Missing build dependency

[Antoine Le Gonidec]

Source: python-zombie-imp
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

The python-zombie-imp source requires the "setuptools" Python module,
but python3-setuptools is not included in its build dependencies.

This has been noticed when trying to build a local backport of
python3-zombie-imp for Bookworm, I have not checked yet if the same
problem happens when building on top of Trixie or Sid.

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

Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

Bug#1044135: openmw: Crosshair, interactive prompts and character creation menus not visible.

[Antoine Le Gonidec]

In addition to the missing UI, OpenMW RAM usage is very high if
-DCMAKE_BUILD_TYPE=RelWithDebInfo is not set when building mygui.

I see a fix for this is already included in the Salsa repository for
mygui.  Please consider uploading a new release based on the current
state of the git repository, as it would make OpenMW usable again
without the need to locally build updated packages.


pgp0GRibRNn4c.pgp
Description: Signature digitale OpenPGP

Bug#1069962: renpy: Missing dependency on python3-ecdsa

[Antoine Le Gonidec]

Package: renpy
Version: 8.1.3+dfsg-1
Severity: normal

`import ecdsa` is called from /usr/share/games/renpy/renpy/savetoken.py,
but the renpy package has no dependency on python3-ecdsa.

This leads to a crash when this file is loaded:

Traceback (most recent call last):
  File "/usr/games/renpy", line 252, in 
main()
  File "/usr/games/renpy", line 248, in main
renpy.bootstrap.bootstrap(renpy_base)
  File "/usr/share/games/renpy/renpy/bootstrap.py", line 250, in bootstrap
renpy.import_all()
  File "/usr/share/games/renpy/renpy/__init__.py", line 428, in import_all
import renpy.savetoken
  File "/usr/share/games/renpy/renpy/savetoken.py", line 26, in 
import ecdsa
ModuleNotFoundError: No module named 'ecdsa'

Installing the python3-ecdsa package is enough to avoid this error, but
it should probably be added to the direct dependencies of the renpy
package.

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

Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 renpy depends on:
ii  fonts-dejavu-core 2.37-8
ii  fonts-motoya-l-cedar  1.01-5
ii  fonts-nanum   20200506-1
ii  fonts-roboto-hinted   2:0~20170802-3
ii  python3   3.11.8-1
ii  python3-pefile2023.2.7-3
ii  python3-pygame-sdl2   8.2.1-1
ii  python3-renpy 8.1.3+dfsg-1+b1
ii  python3-six   1.16.0-6

Versions of packages renpy recommends:
pn  python3-tk  
pn  zenity  

renpy suggests no packages.

-- no debconf information

Bug#1069961: ImportError: cannot import name 'RWops_from_file' from 'pygame_sdl2.rwobject'

[Antoine Le Gonidec]

Package: renpy
Version: 8.1.3+dfsg-1
Severity: important

When trying to run commercial games with Debian-provided renpy (I tried
Slay the Princess and Roadwarden), a crash is triggered before the game
window would be shown:

Traceback (most recent call last):
  File "/usr/games/renpy", line 252, in 
main()
  File "/usr/games/renpy", line 248, in main
renpy.bootstrap.bootstrap(renpy_base)
  File "/usr/share/games/renpy/renpy/bootstrap.py", line 250, in bootstrap
renpy.import_all()
  File "/usr/share/games/renpy/renpy/__init__.py", line 409, in import_all
import renpy.loader
  File "/usr/share/games/renpy/renpy/loader.py", line 37, in 
from pygame_sdl2.rwobject import RWops_from_file, RWops_create_subfile
ImportError: cannot import name 'RWops_from_file' from 'pygame_sdl2.rwobject' 
(/usr/lib/python3/dist-packages/pygame_sdl2/rwobject.cpython-311-x86_64-linux-gnu.so)

The import line triggering this error is no longer part of the upstream
codebase, it has been replaced with the following commit:
https://github.com/renpy/renpy/commit/13cfd68491a38ca1d864c6b668b8c527e58923e2

Applying this patch on top of the cuurent sid build does indeed avoid
this crash, and allow to run the games I tested.

I suggest either backporting this patch, or, better, packaging the
current upstream release (8.2.1).

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

Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 renpy depends on:
ii  fonts-dejavu-core 2.37-8
ii  fonts-motoya-l-cedar  1.01-5
ii  fonts-nanum   20200506-1
ii  fonts-roboto-hinted   2:0~20170802-3
ii  python3   3.11.8-1
ii  python3-pefile2023.2.7-3
ii  python3-pygame-sdl2   8.2.1-1
ii  python3-renpy 8.1.3+dfsg-1+b1
ii  python3-six   1.16.0-6

Versions of packages renpy recommends:
pn  python3-tk  
pn  zenity  

renpy suggests no packages.

-- no debconf information

Bug#1068704: login: Wrong comment in login.defs about USERGROUPS_ENAB

[Antoine Le Gonidec]

Package: login
Version: 1:4.13+dfsg1-4
Severity: normal

>From /etc/login.defs, part of the comment above USERGROUPS_ENAB is no
longer describing the actual behaviour:

> Other former uses of this variable such as setting the umask when
> user==primary group are not used in PAM environments, such as Debian

Recent changes in src:pam made this configuration value change the
setting of umask when the user name and its primary group name are the
same, cf. https://bugs.debian.org/1065806 and https://bugs.debian.org/583958

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

Kernel: Linux 6.7.7-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 login depends on:
ii  libaudit1   1:3.1.2-2.1
ii  libc6   2.37-15.1
ii  libcrypt1   1:4.4.36-4
ii  libpam-modules  1.5.3-7
ii  libpam-runtime  1.5.3-7
ii  libpam0g1.5.3-7

login recommends no packages.

login suggests no packages.

-- no debconf information

Bug#1065806: pam: recent upgrade changes previous default umask

[Antoine Le Gonidec]

The change of behaviour can have an unexpected and quite nasty
side-effect, by applying a misconfiguration that was ignored until this
update.

A setting of "UMASK 077" in /etc/login.defs was ignored before this
update, and is now applied (as it should) leading to unreadable files
if the user is not expecting it.

In my case this was a misconfiguration, as I thought it was a setting
applied only to the $HOME directory itself (I should have used
"HOME_MODE 0700" instead). But since it had no effect until the recent
update, I got taken by surprise with files generated with rw-rw
permissions when I was expecting the regular rw-r--r--.

I am not bumping the severity of this bug report because the new
behaviour is the correct one, but it should be kept in mind that other
people might get unexpected effects from this update.

Bug#1061965: snac2: A new upstream release is available: 2.46

[Antoine Le Gonidec]

Package: snac2
Version: 2.45-1
Severity: wishlist

A new release of snac2 is available:
https://codeberg.org/grunfink/snac2/releases/tag/2.46

This one adds something I had been wishing for: support for following
Peertube channels, with new videos being included in the activity feed.
So snac2 can be used as a substitute to an RSS feed reader to follow the
activity of video channels.

It would be really nice if this build could be available from Debian
repositories.

As usual, big thanks for your work maintaining this package in Debian!

Bug#1055793: snac2: A new upstream release is available: 2.42

[Antoine Le Gonidec]

Package: snac2
Version: 2.41-1
Severity: wishlist

Please consider packaging the new 2.42 upstream release:
https://codeberg.org/grunfink/snac2/releases/tag/2.42

It has been requested by a reader of my snac instance, because it
includes a fix for the broken RSS feed:
https://codeberg.org/grunfink/snac2/issues/81
(the bug report has not been closed yet, but the fix is listed in the
release notes of version 2.42)

Thanks for your work on maintaining the package for snac2, I would have
never considered connecting to the Fediverse without it ;)

Bug#1054127: scummvm: Please consider enabling support for grim:monkey4

[Antoine Le Gonidec]

Package: scummvm
Version: 2.7.0+dfsg-1
Severity: wishlist

Upstream build rules do not include the grim:monkey4 engine in the
generated binary.

Please consider tweaking debian/rules to enable it in the Debian build
of ScummVM, so it could be used as an alternative to WINE when someone
wants to play Monkey Island 4.

While this engine is still in an unfinished state, an explicit warning
is shown when trying to use it. So even if support for it is included,
users are warned that they should not get their expectations too high.

In addition it might provide us with more bug reports using this engine,
leading to more help in getting it to a more complete state.

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

Kernel: Linux 6.5.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 scummvm depends on:
ii  liba52-0.7.4   0.7.4-20
ii  libasound2 1.2.9-2 # Not upgraded to 1.2.10-1 because of bug 
#1051901
ii  libc6  2.37-12
ii  libcurl3-gnutls8.4.0-2
ii  libfaad2   2.10.1-1
ii  libflac12  1.4.3+ds-2
ii  libfluidsynth3 2.3.4-1
ii  libfreetype6   2.13.2+dfsg-1
ii  libfribidi01.0.13-3
ii  libgif75.2.1-2.5
ii  libglib2.0-0   2.78.0-2
ii  libgtk-3-0 3.24.38-5
ii  libieee1284-3  0.2.11-14
ii  libjpeg62-turbo1:2.1.5-2
ii  libmad00.15.1b-10.1+b1
ii  libmpeg2-4 0.5.1-9
ii  libogg01.3.5-3
ii  libpng16-161.6.40-2
ii  libsdl2-2.0-0  2.28.4+dfsg-1
ii  libsdl2-net-2.0-0  2.2.0+dfsg-2
ii  libsndio7.01.9.0-0.3+b2
ii  libspeechd20.11.5-2
ii  libstdc++6 13.2.0-5
ii  libtheora0 1.1.1+dfsg.1-16.1+b1
ii  libvorbis0a1.3.7-1
ii  libvorbisfile3 1.3.7-1
ii  scummvm-data   2.7.0+dfsg-1
ii  zlib1g 1:1.2.13.dfsg-3

scummvm recommends no packages.

Versions of packages scummvm suggests:
pn  beneath-a-steel-sky 
pn  drascula
pn  flight-of-the-amazon-queen  
ii  fluidsynth  2.3.4-1
pn  lure-of-the-temptress   

-- no debconf information

Bug#1053708: gitlab: merge request do not reflect the current state of the branch

[Antoine Le Gonidec]

Package: gitlab
Version: 16.0.8+ds1-2~fto12+1
Severity: important

Since the 6.0.7 → 6.0.8 upgrade, pushing new commits to a branch that
has an associated merge request no longer updates the merge request.

Showing the branch history or browsing its files tree shows that the new
commits are included as expected, but the merge request stays stuck in
its old state.

Reverting to 6.0.7 brings the normal behaviour back, with the merge
request commits list reflecting the commits list of the branch it is
related to.

-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (100, 'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.18-2
ii  bc  1.07.1-3+b1
ii  bundler 2.3.15-2
ii  bzip2   1.0.8-5+b1
ii  dbconfig-pgsql  2.0.24
ii  debconf [debconf-2.0]   1.5.82
ii  fonts-font-awesome [node-font-awesome]  5.0.10+really4.7.0~dfsg-4.1
ii  gitlab-common   16.0.8+ds1-1~bpo12+1
ii  gitlab-workhorse16.0.8+ds1-2~fto12+1
ii  katex [node-katex]  0.16.4+~cs6.1.0-1
ii  libjs-bootstrap4 [node-bootstrap]   4.6.1+dfsg1-4
ii  libjs-pdf [node-pdfjs-dist] 2.14.305+dfsg-2
ii  libjs-popper.js [node-popper.js]1.16.1+ds-6
ii  libruby3.1 [ruby-rexml] 3.1.2-7
ii  libssl-dev  3.0.11-1~deb12u1
ii  lsb-base11.6
ii  nginx [httpd]   1.22.1-9
ii  node-autosize   4.0.4~dfsg1+~4.0.0-2
ii  node-axios  1.2.1+dfsg-1
ii  node-babel-loader   9.1.0-3
ii  node-babel-plugin-lodash3.3.4+~cs2.0.1-6
ii  node-babel7 7.20.15+ds1+~cs214.269.168-3
ii  node-brace-expansion2.0.1-2
ii  node-cache-loader   4.1.0+~cs2.0.0-4
ii  node-clipboard  2.0.11+ds+~cs9.6.11-1
ii  node-compression-webpack-plugin 10.0.0-2
ii  node-copy-webpack-plugin11.0.0-3
ii  node-core-js3.26.1-3
ii  node-core-js-compat 3.26.1-3
ii  node-core-js-pure   3.26.1-3
ii  node-cron-validator 1.3.1-3
ii  node-css-loader 6.7.2+~cs14.0.11-1
ii  node-d3 5.16.0-10
ii  node-d3-selection   1.4.0-8
ii  node-dateformat 5.0.3-5
ii  node-dompurify  2.4.1+dfsg+~2.4.0-1
ii  node-exports-loader 4.0.0-1
ii  node-file-loader6.2.0-3
ii  node-fuzzaldrin-plus0.6.0+dfsg+~0.6.2-3
ii  node-glob   8.0.3+~cs8.4.15-1
ii  node-imports-loader 0.8.0-6
ii  node-jed1.1.1-4
ii  node-jquery 3.6.1+dfsg+~3.5.14-1
ii  node-jquery-ujs 1.2.3-2
ii  node-js-cookie  3.0.1+~3.0.0-3
ii  node-js-yaml4.1.0+dfsg+~4.0.5-7
ii  node-jszip  3.10.1+dfsg-1
ii  node-jszip-utils0.1.0+dfsg-1
ii  node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9
ii  node-marked 4.2.3+ds+~4.0.7-2
ii  node-minimatch  5.1.1+~5.1.2-1
ii  node-miragejs   0.1.46+~cs5.6.11-1
ii  node-mousetrap  1.6.5~ds+~1.6.8-1
ii  node-postcss8.4.20+~cs8.0.23-1
ii  node-prismjs1.29.0+dfsg+~1.26.0-1
ii  node-prosemirror-markdown   1.8.0-1
ii  node-prosemirror-model  1.16.1+~cs1.1.5-2
ii  node-prosemirror-state  1.3.4-2
ii  node-prosemirror-view   1.23.13-2
ii  node-raven-js   3.22.1+dfsg-7
ii  node-raw-loader 4.0.2-3
ii  node-style-loader   3.3.1-2
ii  node-three-orbit-controls   82.1.0-3
ii  node-three-stl-loader   1.0.6-4
ii  node-timeago.js 4.0.2-7
ii  node-underscore 1.13.4~dfsg+~1.11.4-3
ii  node-url-loader 4.1.1-5
ii  node-uuid   8.3.2+~8.3.3-3
ii  node-vue

Bug#920523: Neverwinter Nights segfault

[Antoine Le Gonidec]

It took me a while to understand that, but the crash is actually due to a 
symbol conflict between the old game binaries and current libstdc++.so.6.

Patched binaries are available here: 
https://downloads.dotslashplay.it/games/neverwinter-nights-1/

And the explanation about how they have been patched:
"""
The original binaries nwmain and nwserver have a symbol conflict with modern 
libstdc++.so.6.
patchelf has been used to patch the binaries and rename the conflicting symbol 
(__dynamic_cast).

Big thanks to Phil Morrell, who used a similar method to patch Unreal 
Tournament libraries.
Without their work I would not have known how to fix this.
"""

I suggest closing this bug report, especially now that we know that this was 
not really related to libgl1-mesa-dri in the first place.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1052359: wine: Ghost Master - Failure to render anything but the mouse cursor

[Antoine Le Gonidec]

Package: wine
Version: 8.0.1~repack-3
Severity: normal
Control: merge -1 1051492

When trying to play Ghost Master [1] using the Debian-provided WINE
packages, nothing is rendered in the game window but the mouse cursor,
while music is playing in the background.

This is most probably another symptom of the bug causing a similar
rendering failure with Syberia [2], but I think it is worth opening a
distinct bug report so people getting this rendering failure with Ghost
Master can find this report more easily.

[1]: https://en.wikipedia.org/wiki/Ghost_Master
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051492

-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

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

Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 wine depends on:
ii  wine32  8.0.1~repack-3
ii  wine64  8.0.1~repack-3

wine recommends no packages.

Versions of packages wine suggests:
ii  dosbox0.74-3-4+b1
pn  exe-thumbnailer | kio-extras  
pn  playonlinux   
pn  q4wine
pn  winbind   
pn  wine-binfmt   
ii  winetricks20230212-2

Versions of packages libwine depends on:
ii  libasound2   1.2.9-2
ii  libc62.37-10
ii  libcapi20-3  1:3.27-3+b1
ii  libfontconfig1   2.14.2-6
ii  libfreetype6 2.13.2+dfsg-1
ii  libglib2.0-0 2.78.0-2
ii  libgphoto2-6 2.5.30-1
ii  libgphoto2-port122.5.30-1
ii  libgstreamer-plugins-base1.0-0   1.22.5-1
ii  libgstreamer1.0-01.22.5-1
ii  libpcap0.8   1.10.4-4
ii  libpulse016.1+dfsg1-2+b1
ii  libudev1 254.3-1
ii  libunwind8   1.6.2-3
ii  libusb-1.0-0 2:1.0.26-1
ii  libx11-6 2:1.8.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libz-mingw-w64   1.3+dfsg-1
ii  ocl-icd-libopencl1 [libopencl1]  2.3.2-1

Versions of packages libwine recommends:
ii  fonts-liberation   1:2.1.5-3
ii  fonts-wine 8.0.1~repack-3
ii  gstreamer1.0-plugins-good  1.22.5-1
ii  libasound2-plugins 1.2.7.1-1+b1
ii  libcups2   2.4.2-5
ii  libdbus-1-31.14.10-1
ii  libgl1 1.6.0-1
ii  libgl1-mesa-dri23.2.0~rc3-2
ii  libgnutls303.8.1-4+b1
ii  libgssapi-krb5-2   1.20.1-4
ii  libkrb5-3  1.20.1-4
ii  libodbc2   2.3.12-1
pn  libosmesa6 
ii  libsdl2-2.0-0  2.28.3+dfsg-3
ii  libv4l-0   1.24.1-3
ii  libvulkan1 1.3.250.0-1
ii  libxcomposite1 1:0.4.5-1
ii  libxcursor11:1.2.1-1
ii  libxfixes3 1:6.0.0-2
ii  libxi6 2:1.8-1+b1
ii  libxinerama1   2:1.1.4-3
ii  libxrandr2 2:1.5.2-2+b1
ii  libxrender11:0.9.10-1.1
ii  libxxf86vm11:1.1.4-1+b2

Versions of packages libwine suggests:
pn  cups-bsd   
ii  gstreamer1.0-libav 1.22.5-1
pn  gstreamer1.0-plugins-bad   
ii  gstreamer1.0-plugins-ugly  1.22.5-1
pn  ttf-mscorefonts-installer  

Versions of packages wine32 depends on:
ii  libc62.37-10
ii  libwine  8.0.1~repack-3

wine32 recommends no packages.

Versions of packages wine32 suggests:
pn  wine32-preloader  

Versions of packages wine64 depends on:
ii  libc62.37-10
ii  libwine  8.0.1~repack-3

Versions of packages wine64 recommends:
ii  wine32  8.0.1~repack-3

Versions of packages wine64 suggests:
pn  wine64-preloader  

Versions of packages wine is related to:
pn  dxvk 
pn  dxvk-wine32-development  
pn  dxvk-wine64-development  
ii  fonts-wine   8.0.1~repack-3

-- no debconf information

Bug#1051901: libasound2: 1.2.10 breaks ability to play audio using i386 binaries on amd64 host

[Antoine Le Gonidec]

tags -1 upstream
thanks

Similar symptoms have been reported by Arch Linux users: 
https://bugs.archlinux.org/task/79628
So this bug is most probably not specific to the Debian packaging.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1051901: 1.2.10 breaks ability to play audio using i386 binaries on amd64 host

[Antoine Le Gonidec]

I ran more tests, and could reproduce what I think is the same bug without 
relying on WINE.

Trying to play an audio file using mpv:i386 [1] on an amd64 host causes a 
segfault. While mpv:amd64 has no issue.

[1]: https://packages.debian.org/sid/mpv

I think the problem might actually be related to trying to play sounds using 
any i386 binary (so the i386 libasound.so.2) on an amd64 host.


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1051901: libasound2: 1.2.10 breaks ability to run i386 WINE on an amd64 host

[Antoine Le Gonidec]

Package: libasound2
Version: 1.2.10-1
Severity: important

Since the alsa-lib 1.2.9-2 → 1.2.10 upgrade, trying to run an i386 game
through WINE results in a game crash. This is not specific to some game,
it happened with all games I tried with this release of alsa-lib.

amd64 WINE does not seem to be affected, during my tests the breakages
were specifif to i386 WINE.

As an extra symptom, if at the moment I try to start a game I have some
music playing in the background, using mpd [1], the playback will stop
and mpd will start using 100% of a CPU core until it is killed.

[1]: https://packages.debian.org/sid/mpd

Downgrading libasound2:amd64, libasound2:i386 and libasound2-data to
1.2.9-2 seems to get rid of these unexpected crashes. The other packages
built from the alsa-lib source can stay in the 1.2.10-1 version with no
noticeable breakage.

PS: I wanted to report this bug with severity "serious" due to the
breakage of other software, but reportbug would not let me do that
without quoting some part of the Debian Policy Manual, and I could not
find anything in this manual about not breaking unrelated software.

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

Kernel: Linux 6.4.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 libasound2 depends on:
ii  libasound2-data  1.2.10-1
ii  libc62.37-8

libasound2 recommends no packages.

Versions of packages libasound2 suggests:
ii  libasound2-plugins  1.2.7.1-1+b1

-- no debconf information

Bug#1051492: wine32: Syberia - Failure to render anything in the game window

[Antoine Le Gonidec]

I ran more tests using builds from snapshot.debian.org:
the last build I found with no rendering failure is 7.0~repack-2,
the first build failing to render anything in the game window is 7.0~repack-3.

Unless I missed something, there is only one commit between these two builds:
https://salsa.debian.org/wine-team/wine/-/commit/e055001f272c3a3d7a0b28865f1de9fda13c2f10

Bug#1051492: wine32: Syberia - Failure to render anything in the game window

[Antoine Le Gonidec]

Package: wine32
Version: 8.0.1~repack-3
Severity: normal

When trying to play Syberia [1] using the Debian-provided WINE packages,
nothing is rendered in the game window. Sound is played and clicking
blindly where the menu buttons should be triggers the expected sounds,
so this is almost certainly a rendering failure.

This seems to be specific to the WINE build packaged in Debian, because
I could not reproduce this failure with the WineHQ builds [2], even when
targeting the same upstream version (8.0.1).

I can reproduce this bug with the following Debian builds:
- 8.0.1~repack-3 on Trixie/Sid
- 8.0~repack-4 on Bookworm

I do not reproduce it with the following Debian build:
- 5.0.3-3 (from Bullseye) on Trixie/Sid

When I get a bit of free time I will try more builds from the Salsa
repository [3], hoping I can pinpoint a more specific build that broke
the rendering in this game.

[1]: https://en.wikipedia.org/wiki/Syberia_(video_game)
[2]: https://dl.winehq.org/wine-builds/debian/
[3]: https://salsa.debian.org/wine-team/wine

-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

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

Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 wine32 depends on:
ii  libc62.37-7
ii  libwine  8.0.1~repack-3

Versions of packages wine32 recommends:
ii  wine [wine]  8.0.1~repack-3

Versions of packages wine32 suggests:
pn  wine32-preloader  

wine depends on no packages.

Versions of packages wine suggests:
ii  dosbox0.74-3-4+b1
pn  exe-thumbnailer | kio-extras  
pn  playonlinux   
pn  q4wine
pn  winbind   
pn  wine-binfmt   
ii  winetricks20230212-2

Versions of packages libwine depends on:
ii  libasound2   1.2.9-2
ii  libc62.37-7
ii  libcapi20-3  1:3.27-3+b1
ii  libfontconfig1   2.14.2-5
ii  libfreetype6 2.13.2+dfsg-1
ii  libglib2.0-0 2.77.3-1
ii  libgphoto2-6 2.5.30-1
ii  libgphoto2-port122.5.30-1
ii  libgstreamer-plugins-base1.0-0   1.22.5-1
ii  libgstreamer1.0-01.22.5-1
ii  libpcap0.8   1.10.4-4
ii  libpulse016.1+dfsg1-2+b1
ii  libudev1 254.1-3
ii  libunwind8   1.6.2-3
ii  libusb-1.0-0 2:1.0.26-1
ii  libx11-6 2:1.8.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libz-mingw-w64   1.3+dfsg-1
ii  ocl-icd-libopencl1 [libopencl1]  2.3.2-1

Versions of packages libwine recommends:
ii  fonts-liberation   1:2.1.5-3
ii  fonts-wine 8.0.1~repack-3
ii  gstreamer1.0-plugins-good  1.22.5-1
ii  libasound2-plugins 1.2.7.1-1+b1
ii  libcups2   2.4.2-5
ii  libdbus-1-31.14.10-1
ii  libgl1 1.6.0-1
ii  libgl1-mesa-dri23.1.7-1
ii  libgnutls303.8.1-4+b1
ii  libgssapi-krb5-2   1.20.1-3
ii  libkrb5-3  1.20.1-3
ii  libodbc2   2.3.12-1
pn  libosmesa6 
ii  libsdl2-2.0-0  2.28.3+dfsg-1
ii  libv4l-0   1.24.1-3
ii  libvulkan1 1.3.250.0-1
ii  libxcomposite1 1:0.4.5-1
ii  libxcursor11:1.2.1-1
ii  libxfixes3 1:6.0.0-2
ii  libxi6 2:1.8-1+b1
ii  libxinerama1   2:1.1.4-3
ii  libxrandr2 2:1.5.2-2+b1
ii  libxrender11:0.9.10-1.1
ii  libxxf86vm11:1.1.4-1+b2

Versions of packages libwine suggests:
pn  cups-bsd   
ii  gstreamer1.0-libav 1.22.5-1
pn  gstreamer1.0-plugins-bad   
ii  gstreamer1.0-plugins-ugly  1.22.5-1
pn  ttf-mscorefonts-installer  

Versions of packages wine64 depends on:
ii  libc62.37-7
ii  libwine  8.0.1~repack-3

Versions of packages wine64 recommends:
ii  wine [wine]  8.0.1~repack-3

Versions of packages wine64 suggests:
pn  wine64-preloader  

Versions of packages wine32 is related to:
pn  dxvk 
pn  dxvk-wine32-development  
pn  dxvk-wine64-development  
ii  fonts-wine   8.0.1~repack-3

-- no debconf information

Bug#1051106: libsdl1.2debian: Mark of the Ninja - Failure to render anything but a black screen

[Antoine Le Gonidec]

Package: libsdl1.2debian
Version: 1.2.64-5
Severity: normal
Tags: upstream

Initially reported on ./play.it forge[1], this has been triggered using the 
Linux build of Mark of the Ninja that used to be provided by Humble Bundle 
(markoftheninja_linux38_1380755375.zip).

[1]: https://forge.dotslashplay.it/play.it/games/-/issues/895

When using sdl12-compat to provide libSDL-1.2.so.0, the game fails to render 
anything but a black screen.

Ambient music can be heard in the background and the menu can be navigated 
using the keyboard (navigation sound effects are played as expected), so I 
guess this can be narrowed down to a rendering failure.

This does not happen when using a real libSDL-1.2.so.0, then the game menu is 
rendered with no problem.

This is not limited to the menu: I can blindly start a game and try moving 
around the character, then I hear the footsteps sound effect. Meanwhile the 
screen is still black.

Upstream bug report: https://github.com/libsdl-org/sdl12-compat/issues/315

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

Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 libsdl1.2debian depends on:
ii  libc6  2.37-7
ii  libsdl2-2.0-0  2.28.3+dfsg-1

libsdl1.2debian recommends no packages.

libsdl1.2debian suggests no packages.

-- no debconf information

Bug#1036646: libhyperscan5: prevents rspamd from starting

[Antoine Le Gonidec]

On Thu, 25 May 2023 01:32:33 +0200 Sebastien Badia  wrote:

I'm maybe wrong, but Bookworm will be released with libhyperscan5 = 5.4.0-2 
(like bullseye).
So this bug (#1036646) is a RC for Trixie but not for Bookworm ?


I was not sure if the 5.4.2-1 build of libhyperscan5 would migrate 
automatically to Bookworm before the release, so I initially set the severity 
high enough to block the package migration.

Now that the bug report has been reassigned to rspamd (I submitted against 
libhyperscan5 initially), the high severity is no longer justified so I think 
you were right to lower it.

As long as Bookworm is released with libhyperscan5 = 5.4.0-2 and rspamd = 
3.4-1, there should be no problem.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1036646: libhyperscan5: prevents rspamd from starting

[Antoine Le Gonidec]

I bumped the bug severity to prevent the automatic migration to Bookworm, but 
feel free to lower it if you think it is not warranted.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1036646: libhyperscan5: prevents rspamd from starting

[Antoine Le Gonidec]

It looks like an update of rspamd should fix this:
https://github.com/rspamd/rspamd/issues/4409

I am reassigning this bug report to rspamd since it seems that a fix is 
available from their upstream.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1036646: libhyperscan5: prevents rspamd from starting

[Antoine Le Gonidec]

Package: libhyperscan5
Version: 5.4.2-1
Severity: important

After upgrading libhyperscan5 from 5.4.0-2 to 5.4.2-1, rspamd no longer starts.
Even with debug output it does not seem to give any information on what 
prevents it to run:

/usr/bin/rspamd -c /etc/rspamd/rspamd.conf -f -u _rspamd -d
2023-05-23 21:09:58 #1829280(main) ; main; main: rspamd 3.4 is loading 
configuration, build id: release
Aborted

After reverting to libhyperscan5 5.4.0-2, rspamd can run again with no 
noticeable issue.

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-debug'), (500, 'oldstable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 libhyperscan5 depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libc6  2.36-9
ii  libgcc-s1  12.2.0-14
ii  libstdc++6 12.2.0-14

libhyperscan5 recommends no packages.

libhyperscan5 suggests no packages.

-- debconf information:
  libhyperscan/cpu-ssse3: false

Bug#1019731: gitlab: failed to fetch comments in merge requests (500 Internal Server Error)

[Antoine Le Gonidec]

The attached patch works around the failure to display comments on diffs.

It has been submitted and included upstream already, see:
- https://gitlab.com/gitlab-org/gitlab/-/issues/374174#note_1238695337
- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/108902
diff --git a/config/application.rb b/config/application.rb
index a3fe4935fdf..88fd66f0baf 100644
--- a/config/application.rb
+++ b/config/application.rb
@@ -595,6 +595,15 @@ class Application < Rails::Application
 Gitlab::Color, # https://gitlab.com/gitlab-org/gitlab/-/issues/368844,
 Hashie::Array # https://gitlab.com/gitlab-org/gitlab/-/issues/378089
   ]
+  # 
+  # it seems that setting config.active_record.yaml_column_permitted_classes in an after_initialize does not update
+  # the value in ActiveRecord::Base.yaml_column_permitted_classes. We can not move the setting of
+  # config.active_record.yaml_column_permitted_classes out of the after_initialize because then the gitlab classes
+  # are not loaded yet.
+  #
+  # Manually set ActiveRecord::Base.yaml_column_permitted_classes
+  #
+  ActiveRecord::Base.yaml_column_permitted_classes = config.active_record.yaml_column_permitted_classes
 
   # on_master_start yields immediately in unclustered environments and runs
   # when the primary process is done initializing otherwise.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032259: conky: High CPU usage

[Antoine Le Gonidec]

The bug is fixed upstream, with their new release v1.18.2: 
https://github.com/brndnmtthws/conky/releases/tag/v1.18.2

Here is the targeted update: https://github.com/brndnmtthws/conky/pull/1444
I attached a copy of the .diff for convenience.
diff --git a/src/colours.cc b/src/colours.cc
index aa9446cd0..fe16c2fd2 100644
--- a/src/colours.cc
+++ b/src/colours.cc
@@ -31,6 +31,10 @@
 #include "logging.h"
 #include "x11-color.h"
 
+#ifdef BUILD_X11
+std::unordered_map Colour::x11_pixels;
+#endif /* BUILD_X11 */
+
 static int hex_nibble_value(char c) {
   if (c >= '0' && c <= '9') {
 return c - '0';
diff --git a/src/colours.h b/src/colours.h
index 18ed55b89..f383422ef 100644
--- a/src/colours.h
+++ b/src/colours.h
@@ -33,6 +33,7 @@
 #include 
 #include 
 #include 
+#include 
 #ifdef BUILD_X11
 #include "x11.h"
 #endif /* BUILD_X11 */
@@ -51,7 +52,7 @@ struct Colour {
   }
 
   // Express the color as a 32-bit ARGB integer (alpha in MSB).
-  uint32_t to_argb32(void) {
+  uint32_t to_argb32(void) const {
 uint32_t out;
 out = alpha << 24 | red << 16 | green << 8 | blue;
 return out;
@@ -61,6 +62,12 @@ struct Colour {
   static Colour from_argb32(uint32_t argb);
 
 #ifdef BUILD_X11
+  class Hash {
+   public:
+size_t operator()(const Colour ) const { return c.to_argb32(); }
+  };
+
+  static std::unordered_map x11_pixels;
   unsigned long to_x11_color(Display *display, int screen,
  bool premultiply = false) {
 if (display == nullptr) {
@@ -68,16 +75,29 @@ struct Colour {
   return 0;
 }
 
-XColor xcolor{};
-xcolor.red = red * 257;
-xcolor.green = green * 257;
-xcolor.blue = blue * 257;
-if (XAllocColor(display, DefaultColormap(display, screen), ) == 0) {
-  // NORM_ERR("can't allocate X color");
-  return 0;
+unsigned long pixel;
+
+/* Either get a cached X11 pixel or allocate one */
+if (auto pixel_iter = x11_pixels.find(*this);
+pixel_iter != x11_pixels.end()) {
+  pixel = pixel_iter->second;
+} else {
+  XColor xcolor{};
+  xcolor.red = red * 257;
+  xcolor.green = green * 257;
+  xcolor.blue = blue * 257;
+  if (XAllocColor(display, DefaultColormap(display, screen), ) ==
+  0) {
+// NORM_ERR("can't allocate X color");
+return 0;
+  }
+
+  /* Save pixel value in the cache to avoid reallocating it */
+  x11_pixels[*this] = xcolor.pixel;
+  pixel = static_cast(xcolor.pixel);
 }
 
-unsigned long pixel = static_cast(xcolor.pixel) & 0xff;
+pixel &= 0xff;
 #ifdef BUILD_ARGB
 if (have_argb_visual) {
   if (premultiply)


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032259: conky: High CPU usage

[Antoine Le Gonidec]

I think I can confirm that the high Xorg memory usage is due to this update, I 
am now sitting at 3.30GB after a dozen hours.

To make really sure of the cause, I am going to revert to the 1.17 build of 
Conky and let it run for a dozen hours too.

In the meantime I am bumping the bug severity again to prevent this memory leak 
to reach Bookworm, once again feel free to revert that if you think that is not 
such a big deal (I guess not everyone have X sessions running for several days).


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032259: conky: High CPU usage

[Antoine Le Gonidec]

I bumped the severity of the bug report, because the memory leak could cause 
more issues than the increase in CPU load. Feel free to change the severity 
level if you think I did not chose the right one.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032259: conky: High CPU usage

[Antoine Le Gonidec]

I noticed that Xorg memory usage grows over time to unexpected levels. I think 
it started at the same time than the high CPU usage so it might be related, but 
I do not know how to make sure of that.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032259: conky: High CPU usage

[Antoine Le Gonidec]

In case it might help finding the root cause of the increased CPU load, I am 
attaching the Conky configuration file I use to this message.
conky.config = {
alignment = 'top_right',
default_graph_height = 30,
default_color = 'white',
double_buffer = true,
use_xft = true,
font = 'DejaVu Sans Condensed:style=Bold:size=9',
gap_y = 0,
maximum_width = 300,
minimum_height = 1024,
minimum_width = 300,
own_window = true,
own_window_type = 'desktop',
own_window_hints = 'undecorated,below,sticky,skip_taskbar,skip_pager',
short_units = true,
update_interval = 1.0,
show_graph_scale = true,
}

conky.text = [[
${time %A %d %B}${alignr}${time %R}

Uptime ${alignr} $uptime
Mises-à-jour disponibles ${alignr} ${texeci 1800 echo $(apt list --upgradable 
2>/dev/null | tail +2 | wc -l)}
En attente de redémarrage ${alignr} ${execi 1800 test -e 
/var/run/reboot-required && echo oui || echo non}

${font DejaVu Sans Condensed:style=Bold:size=12}Réseau ${hr}${font}

${if_up enp3s0}${downspeedgraph enp3s0 30,145 FFC5B1 982700 6500 
-t}${alignr}${upspeedgraph enp3s0 30,145 B1C5FF 002798 6500 -t}
${font DejaVu Sans Condensed:style=Bold:size=12}${voffset -34}${alignc}${offset 
-75}${downspeedf enp3s0} K/s ⬇${font}
${font DejaVu Sans Condensed:style=Bold:size=12}${voffset -19}${alignc}${offset 
85}${upspeedf enp3s0} K/s ⬆${font}
${endif}

${font DejaVu Sans Condensed:style=Bold:size=12}CPU ${hr}${font}

$alignr ${execpi 60 show_cpu_temperature conky}
${cpugraph cpu0 40,298 C5FFC5 279827 -t}
${top name 1} $alignr ${top cpu 1}%
${top name 2} $alignr ${top cpu 2}%
${top name 3} $alignr ${top cpu 3}%

${font DejaVu Sans Condensed:style=Bold:size=12}RAM ${hr}${font}

${alignr}$mem / $memmax
${memgraph 40,298 B1 989800 -t}
${top_mem name 1} $alignr ${top_mem mem_res 1}
${top_mem name 2} $alignr ${top_mem mem_res 2}
${top_mem name 3} $alignr ${top_mem mem_res 3}

${font DejaVu Sans Condensed:style=Bold:size=12}Disques ${hr}${font}

/
${diskiograph /dev/disk/by-id/ata-Samsung_SSD_860_PRO_256GB_S42VNGAK102577V 
30,298 FFB1B1 98 26000 -t}
${font DejaVu Sans Condensed:style=Bold:size=12}${voffset -34}${alignc}${diskio 
/dev/disk/by-id/ata-Samsung_SSD_860_PRO_256GB_S42VNGAK102577V}/s${font}

/srv
${diskiograph /dev/disk/by-id/ata-TOSHIBA_HDWD110_58PM6KGFS 30,298 B1 
989800 19000 -t}
${font DejaVu Sans Condensed:style=Bold:size=12}${voffset -34}${alignc}${diskio 
/dev/disk/by-id/ata-TOSHIBA_HDWD110_58PM6KGFS}/s${font}

/home/jeux
${diskiograph /dev/disk/by-id/ata-WDC_WD120EFBX-68B0EN0_5QKWL5UB 30,298 B1FFB1 
009800 2 -t}
${font DejaVu Sans Condensed:style=Bold:size=12}${voffset -34}${alignc}${diskio 
/dev/disk/by-id/ata-WDC_WD120EFBX-68B0EN0_5QKWL5UB}/s${font}

/home/media
${diskiograph /dev/disk/by-id/ata-WDC_WD80EFAX-68KNBN0_VGHBTWAG 30,298 B1 
009898 19000 -t}
${font DejaVu Sans Condensed:style=Bold:size=12}${voffset -34}${alignc}${diskio 
/dev/disk/by-id/ata-WDC_WD80EFAX-68KNBN0_VGHBTWAG}/s${font}

/home/musique
${diskiograph /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N6CPH7RD 30,298 
B1B1FF 98 15000 -t}
${font DejaVu Sans Condensed:style=Bold:size=12}${voffset -34}${alignc}${diskio 
/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N6CPH7RD}/s${font}

/home/vrac
${diskiograph /dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7K4UYYUJ1 30,298 
FFB1FF 980098 17000 -t}
${font DejaVu Sans Condensed:style=Bold:size=12}${voffset -34}${alignc}${diskio 
/dev/disk/by-id/ata-WDC_WD40EFRX-68N32N0_WD-WCC7K4UYYUJ1}/s${font}

${if_running mpd}${if_mpd_playing}
${font DejaVu Sans Condensed:style=Bold:size=12}Musique ${hr}${font}

${alignc}$mpd_title
${alignc}$mpd_album
${alignc}$mpd_artist
]]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1032259: conky: High CPU usage

[Antoine Le Gonidec]

Source: conky
Version: 1.18.1-1
Severity: normal

Before the upgrade to 1.18.1, Conky had a low CPU usage, around 2~5%.
Since the upgrade to 1.18.1, it has a much higher CPU usage, around 10~20%. In 
addition, Xorg CPU usage is increased to 15~30%.

Reverting to Conky 1.17.0-1 the CPU usage goes back to the low values.

I have not tried the upstream releases yet, but I can do that and run a bisect 
to find the first commit increasing CPU usage. Please tell me if that would be 
helpful.

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

Kernel: Linux 6.1.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

Bug#1031521: Acknowledgement (openjdk-17: ld.so assertion failure with multiple commercial games)

[Antoine Le Gonidec]

While I ensured that the assertion failure happens for all builds I assigned 
this bug to (OpenJDK 11, 17, 18, 19, 20 and 21), I only checked the proposed 
workaround against the following source packages:
- openjdk-11
- openjdk-17
- openjdk-21


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1031521: openjdk-17: ld.so assertion failure with multiple commercial games

[Antoine Le Gonidec]

Source: openjdk-17
Severity: normal

Multiple Java games fail to launch when trying to run them with Debian builds 
of OpenJDK, including:
- Blocks That Matter
- Gathering Sky
- Lenna's Inception
- Slay the Spire
- The Count Lucanor
- Urtuk: The Desolation

All of these games fail to run with OpenJDK > 8, throwing the following error:

Inconsistency detected by ld.so: dl-lookup.c: 107: check_match: Assertion 
`version->filename == NULL || ! _dl_name_match_p (version->filename, map)' 
failed!

Due to the similarities with bug report #982443 
(https://bugs.debian.org/982443), we gave a try to the proposed workaround:

DEB_LDFLAGS_SET='-Wl,-z,relro,--no-as-needed' DEB_BUILD_OPTIONS=nocheck debuild 
--no-sign -b -j4

Using this build of OpenJDK, the listed games work nicely.

More details can be found on ./play.it forge, where we did the original 
investigation:
https://forge.dotslashplay.it/play.it/games/-/issues/880

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

Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

Bug#1019731: Suggested fix

[Antoine Le Gonidec]

On Tue, 07 Feb 2023 19:02:46 +0100 Pirate Praveen  
wrote:

diff --git a/config/application.rb b/config/application.rb
index 249db9c6a6..e7481e12e1 100644
--- a/config/application.rb
+++ b/config/application.rb
@@ -234,6 +234,12 @@ class Application < Rails::Application
 config.active_record.has_many_inversing = false
 config.active_record.belongs_to_required_by_default = false

+ # Allow Gitlab::Diff::Position because it was disallowed
+ # with Rails 6.1.6.4 security update. Whilst they have
+ # re-added support for Symbol, they expect the projects
+ # to add the classes they need to be explicitly allowed.
+ config.active_record.yaml_column_permitted_classes = [Symbol, 
DateTime, Gitlab::Diff::Position]

+
 # Enable the asset pipeline
 config.assets.enabled = true


With this patch, gitlab-puma.service fails to start with the following trace:

/usr/share/gitlab/config/application.rb:241:in `': 
uninitialized constant Gitlab::Diff (NameError)
Did you mean?  Diffy
from /usr/share/gitlab/config/application.rb:18:in `'
from /usr/share/gitlab/config/application.rb:17:in `'
from /usr/share/gitlab/config/environment.rb:4:in `require'
from /usr/share/gitlab/config/environment.rb:4:in `'
from config.ru:5:in `require'
from config.ru:5:in `block in '
from /var/lib/gitlab/.gem/gems/rack-2.2.6.2/lib/rack/builder.rb:116:in 
`eval'
from /var/lib/gitlab/.gem/gems/rack-2.2.6.2/lib/rack/builder.rb:116:in 
`new_from_string'
from /var/lib/gitlab/.gem/gems/rack-2.2.6.2/lib/rack/builder.rb:105:in 
`load_file'
from /var/lib/gitlab/.gem/gems/rack-2.2.6.2/lib/rack/builder.rb:66:in 
`parse_file'
from 
/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/puma-5.6.5/lib/puma/configuration.rb:348:in
 `load_rackup'
from 
/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/puma-5.6.5/lib/puma/configuration.rb:270:in
 `app'
from 
/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/puma-5.6.5/lib/puma/runner.rb:150:in
 `load_and_bind'
from 
/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/puma-5.6.5/lib/puma/single.rb:44:in
 `run'
from 
/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/puma-5.6.5/lib/puma/launcher.rb:193:in
 `run'
from 
/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/puma-5.6.5/lib/puma/cli.rb:81:in
 `run'
from 
/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/puma-5.6.5/bin/puma:10:in 
`'
from /usr/bin/puma:23:in `load'
from /usr/bin/puma:23:in `'


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1027435: ncurses-base: Breaks pasting in vim within tmux

[Antoine Le Gonidec]

Package: ncurses-base
Version: 6.3+20221224-2
Severity: important

Since the 6.3+20221224-2 update, vim pasting behaviour is broken when
TERM is set to "tmux" or "tmux-256color".

To reproduce it, open vim, type a few word, then try to copy/paste them
using selection then middle mouse clic, or Ctrl + Shift + C then Ctrl +
Shift + V. The pasting then has a strange behaviour, it looks like vim
automatically goes back to edition mode (instead of insertion mode) at
the beginning of the paste process, then treat the following characters
as commands (so it will go back to insertion mode at the first "i", "a"
or "s").

This issue does not happen outside of tmux, or if TERM is set to "xterm"
instead of "tmux". Reverting to ncurses-base 6.3+20220423-2 is another
way to work around this unexpected behaviour.

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

Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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

-- no debconf information

Bug#1019731: gitlab: failed to fetch comments in merge requests (500 Internal Server Error)

[Antoine Le Gonidec]

My bad, I mixed things up: the 500 error I am experiencing is the one from 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019403 (undefined method `h' 
for LabelsHelper:Module).

Sorry for the noise.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019731: gitlab: failed to fetch comments in merge requests (500 Internal Server Error)

[Antoine Le Gonidec]

On Thu, 22 Sep 2022 07:08:46 +0200 Maximilian Stein  wrote:
As discussed in the upstream Gitlab bug report [1], apparently the 
package `ruby-activerecord` in version 6.1.6.1 
(2:6.1.6.1+dfsg-3~fto11+1) is broken as it appears to contain file from 
version 6.1.6 (specifically 
/usr/share/rubygems-integration/all/gems/activerecord-6.1.6.1/lib/active_record/railtie.rb). 
So, probably, that package needs to be fixed to get merge request 
comments working again.


In the meantime, there is a workaround available for Gitlab [2].


Could you please give a bit more details about the workaround?

I tried copying config/initializers/rails_safe_load_yaml_patch.rb from upstream 
merge request !92400 to /etc/gitlab/initializers/rails_safe_load_yaml_patch.rb, 
but I still get the 500 error (after a full rebuild of the assets). So I guess 
I am missing a step.

I run gitlab 15.4.2+ds1-1~fto11+3 from bullseye-fasttrack.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1019403: gitlab: failed to fetch comments in issue (500 Internal Server Error)

[Antoine Le Gonidec]

On Thu, 08 Sep 2022 17:04:31 +0200 Maximilian Stein  wrote:

To me, this seemed like a typo, so I simply removed "h " in
labels_helper.rb:250. This fixed the issue for me, as far as I can
tell.


This might not be a typo. It has been added in the following upstream commit:
https://gitlab.com/gitlab-org/gitlab/-/commit/513066c360bcfaa8d5cd40795f7d98d46b9e1e44
(I could not find the original merge request discussion, its access might be 
restricted)

An alternative fix is to replace:
#{"style=\"background-color: #{h bg_color}\"" if bg_color}
with:
#{"style=\"background-color: #{html_escape bg_color}\"" if bg_color}

I think "h" is supposed to be a method alias for "html_escape", but is not 
loaded due to something missing in our setup.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1020581: ITP: play.it-contrib -- ./play.it game scripts collection

[Antoine Le Gonidec]

Package: wnpp
Severity: wishlist
Owner: Antoine Le Gonidec 
X-Debbugs-Cc: debian-de...@lists.debian.org, 
debian-devel-ga...@lists.debian.org, deb...@dotslashplay.it

* Package name: play.it-contrib
  Version : 2022.09.23
  Upstream Author : Multiple ./play.it contributors 
* URL : https://forge.dotslashplay.it/play.it/games/
* License : BSD 2-Clause
  Programming Lang: Shell
  Description : ./play.it game scripts collection

./play.it is a packages generator for commercial games, that is already 
included in the contrib section of Debian repositories: 
https://wiki.debian.org/Games/PlayIt

Starting with its 2.14 release, its development has been splitted over two 
repositories: one including the library and main wrapper, following a cycle of 
stable feature releases and bugfix releases, and one including the collection 
of game scripts, with no stable releases.

Starting with its 2.16 release, the game scripts are no longer included in the 
main repository. That means that we can not update the Debian package to builds 
more recent than the current 2.15.1 without making it useless to most users.

By adding this package providing the main game scripts collection, we would 
unlock the ability to update the library and main wrapper up to the most 
current upstream build (2.18.0 at the time of writing this ITP).

I wish to maintain this new package under the Games team umbrella, while still 
planning to handle the updates myself most of the time. I hope the sponsor of 
the current play.it package (Phil Morrell) will be OK with sponsoring this 
package too, otherwise I hope someone else from the Games team would be willing 
to sponsor it.

Bug#1020213: libatk1.0 pulls in at-spi2-core

[Antoine Le Gonidec]

On Sun, 18 Sep 2022 09:59:01 +0200 Dominick Grift  
wrote:

libatk1.0-0 (2.46.0-1) pulls in at-spi2-core (and
gsettings-desktop-schemas). It would be really nice if we could
opt out of at-spi2-core. at-spi2-core is very intrusive and by itself it
does not add any value.


at-spi2-core is only a recommended dependency of libatk1.0-0, not a hard 
dependency:

$ apt depends libatk1.0-0
libatk1.0-0
  Depends: libc6 (>= 2.4)
  Depends: libglib2.0-0 (>= 2.62)
  Recommends: at-spi2-core
at-spi2-core:i386

You should be able to remove at-spi2-core, or prevent its installation, and 
keep libatk1.0-0 installed at the same time.

Bug#996858: libllvm12:i386 uninstallable and uninstall my desktop

[Antoine Le Gonidec]

Your issue (libllvm12:amd64 and libllvm12:i386 not co-installable) is most 
probably due to the i386 build of libllvm12 1:12.0.1-10 failing, leading to its 
absence from Debian Sid repositories. You can see more details about this build 
failure here: https://bugs.debian.org/996796

I expect libllvm12:i386 1:12.0.1-10 to be available as soon as #996796 is 
fixed. In the meantime, if you need this package in both architecture you would 
need to stay on 1:12.0.1-9 even for the amd64 build. You can download this 
package from snapshot.debian.org: 
https://snapshot.debian.org/package/llvm-toolchain-12/1%3A12.0.1-9/#libllvm12_1:3a:12.0.1-9



OpenPGP_signature
Description: OpenPGP digital signature

Bug#995305: wine: New upstream release available (6.0.1)

[Antoine Le Gonidec]

On Wed, 29 Sep 2021 09:47:59 -0400 Christopher Martin  
wrote:

Wine upstream has released 6.0.1 (stable), while Debian remains on
5.0.3. An update would be great.


Debian 6.0 (but not 6.0.1 yet) is already available on Debian Sid, through the 
package wine-development.

There are plans to drop the dedicated wine-development source package and go 
with a single wine source package, cf. https://bugs.debian.org/988246
This change in WINE packaging might be what is delaying the updates of the 
current wine (stable) package.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#992069: marked as done (libvkd3d-doc is not installable besides libvkd3d-dev)

[Antoine Le Gonidec]

Le 25/08/2021 à 14:21, Antoine Le Gonidec a écrit :

Le 23/08/2021 à 22:44, Sveinar Søpler a écrit :

Can anyone CONFIRM that libvkd3d-dev and libvkd3d-doc (1.2-6) is installable at 
the same time without a conflict?


I wanted to give it a try, but the dependencies of experimental version of 
libvkd3d1 prevent its installation on a current Debian Sid/Bookworm:
(…)
See the "Depends: mesa-vulkan-drivers (<< 21)" from libvkd3d1 1.2-6 
dependencies, it clashes with the version of mesa-vulkan-drivers provided in both unstable and 
experimental.


I gave it a new try after a downgrade to the testing version of 
mesa-vulkan-drivers (20.3.5-1), and I end up with a file conflict error between 
libvkd3d-doc and libvkd3d-dev (both in version 1.2-6):

Unpacking libvkd3d-doc (1.2-6) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-o7eou1/7-libvkd3d-doc_1.2-6_all.deb (--unpack):
 trying to overwrite '/usr/share/doc/libvkd3d-dev/ANNOUNCE.gz', which is also 
in package libvkd3d-dev:amd64 1.2-6



OpenPGP_signature
Description: OpenPGP digital signature

Bug#992069: marked as done (libvkd3d-doc is not installable besides libvkd3d-dev)

[Antoine Le Gonidec]

Le 23/08/2021 à 22:44, Sveinar Søpler a écrit :

Can anyone CONFIRM that libvkd3d-dev and libvkd3d-doc (1.2-6) is installable at 
the same time without a conflict?


I wanted to give it a try, but the dependencies of experimental version of 
libvkd3d1 prevent its installation on a current Debian Sid/Bookworm:

root@hal9000:~# apt depends libvkd3d-dev/experimental
libvkd3d-dev
  Depends: libvkd3d1 (= 1.2-6)
  Depends: libvkd3d-utils1 (= 1.2-6)
  Depends: libvkd3d-shader1 (= 1.2-6)
  Depends: libvkd3d-headers (= 1.2-6)
  Suggests: libvkd3d-doc (= 1.2-6)

root@hal9000:~# apt depends libvkd3d1=1.2-6
libvkd3d1
  Depends: libvulkan1 (>= 1.1.70)
  Depends: libc6 (>= 2.14)
  Depends: libvkd3d-shader1 (>= 1.2)
  Depends: mesa-vulkan-drivers (<< 21)

root@hal9000:~# apt policy mesa-vulkan-drivers
mesa-vulkan-drivers:
  Installed: 21.2.1-1
  Candidate: 21.2.1-1
  Version table:
 *** 21.2.1-1 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
 21.2.0-1 1
  1 http://deb.debian.org/debian experimental/main amd64 Packages
 20.3.5-1 500
500 http://deb.debian.org/debian stable/main amd64 Packages
500 http://deb.debian.org/debian testing/main amd64 Packages
 18.3.6-2+deb10u1 500
500 http://deb.debian.org/debian oldstable/main amd64 Packages

See the "Depends: mesa-vulkan-drivers (<< 21)" from libvkd3d1 1.2-6 
dependencies, it clashes with the version of mesa-vulkan-drivers provided in both unstable and 
experimental.

This is most probably related to the 1.2-5 → 1.2-6 vkd3d update, see this line 
from the changelog:
« Require mesa-vulkan-drivers before version 21 (causes test failures). »



OpenPGP_signature
Description: OpenPGP digital signature

Bug#989791: gitlab: Some views broken by Rails 6.0.3.7 upgrade

[Antoine Le Gonidec]

On Sun, 13 Jun 2021 11:49:12 +0200 Antoine Le Gonidec 
 wrote:

I am going to answer to this report with a suggested patch.


See the attached gzipped diff for a minimal diff that seems to be enough to 
avoid the internal errors I got since the Rails upgrade to 6.3.0.7.


id-upgrade-rails-to-6.0.3.7.diff.gz
Description: application/gzip


OpenPGP_signature
Description: OpenPGP digital signature

Bug#989791: gitlab: Some views broken by Rails 6.0.3.7 upgrade

[Antoine Le Gonidec]

Package: gitlab
Version: 13.11.5+ds1-1~fto10+1
Severity: important

Since Rails 6.0.3.6 → Rails 6.0.3.7 upgrade, some views fail to load
with internal errors similar to this one:

ActionView::Template::Error (Please use symbols for polymorphic route 
arguments.):  
18:   %span.issuable-number= issuable.to_reference  
  
19: 
  
20: - labels.each do |label|
  
21:   = render_label(label.present(issuable_subject: project), link: 
polymorphic_path(issuable_type_args, { milestone_title: @milestone.title, 
label_na
me: label.title, state: 'all' }), small: true)  
  
22: 
  
23: %span.assignee-icon 
  
24:   - assignees.each do |assignee|
  

This is due to the following upstream change to polymorphic routes:
https://github.com/rails/rails/commit/c4c21a9f8d7c9c8ca6570bdb82d64e2dc860e62c

GitLab has been patched 2 weeks ago, but I think it would be worth to
backport this fix.

I am going to answer to this report with a suggested patch.

-- System Information:
Debian Release: 10.9
  APT prefers stable
  APT policy: (500, 'stable'), (100, 'buster-fasttrack'), (100, 
'buster-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.10-2~bpo10+1
ii  bc  1.07.1-2+b1
ii  bundler 1.17.3-3+deb10u1
ii  bzip2   1.0.6-9.2~deb10u1
ii  dbconfig-pgsql  2.0.11+deb10u1
ii  debconf [debconf-2.0]   1.5.71
ii  fonts-font-awesome [node-font-  5.0.10+really4.7.0~dfsg-4~bpo10+1
ii  gitlab-common   13.11.2+dfsg-2~fto10+1
ii  gitlab-workhorse13.11.5+ds1-1~fto10+1
ii  katex [node-katex]  0.10.2+dfsg-8~bpo10+1
ii  libjs-bootstrap4 [node-bootstr  4.3.1+dfsg2-1
ii  libjs-codemirror [node-codemir  5.54.0-2~bpo10+1
ii  libjs-pdf [node-pdfjs-dist] 2.6.347+dfsg-3~bpo10+1
ii  libjs-popper.js [node-popper.j  1.16.1+ds-2~bpo10+1
ii  libruby2.7 [ruby-rexml] 2.7.3-2~fto10+1
ii  lsb-base10.2019051400
ii  nginx   1.14.2-2+deb10u4
ii  nginx-full [nginx]  1.14.2-2+deb10u4
ii  node-autosize   4.0.2~dfsg1-5~bpo10+1
ii  node-axios  0.17.1+dfsg-2
ii  node-babel-loader   8.2.2-1~bpo10+1
ii  node-babel-plugin-lodash3.3.4+~cs2.0.1-3~bpo10+1
ii  node-babel7 7.12.12+~cs150.141.84-2~bpo10+1
ii  node-brace-expansion1.1.8-1
ii  node-cache-loader   4.1.0-6~bpo10+1
ii  node-chart.js   2.7.3+dfsg-5
ii  node-clipboard  2.0.6+ds-1~bpo10+1
ii  node-compression-webpack-plugi  3.0.1-4~bpo10+1
ii  node-copy-webpack-plugin5.1.2+~cs9.0.2-4~bpo10+1
ii  node-core-js3.6.1-2~bpo10+2
ii  node-css-loader 5.0.1+~cs14.0.5-1~bpo10+1
ii  node-d3 5.16.0-1~bpo10+1
ii  node-d3-scale   2.2.2-2~bpo10+1
ii  node-d3-selection   1.4.0-3~bpo10+1
ii  node-dateformat 3.0.0-1
ii  node-exports-loader 0.7.0-2~bpo10+1
ii  node-file-loader6.2.0-2~bpo10+1
ii  node-fuzzaldrin-plus0.5.0+dfsg-1
ii  node-glob   7.1.6-1~bpo10+1
ii  node-imports-loader 0.8.0-2~bpo10+1
ii  node-jed1.1.1-2~bpo10+1
ii  node-jquery 3.5.1+dfsg-4~bpo10+1
ii  node-jquery-ujs 1.2.2-2
ii  node-js-cookie  2.2.0-2
ii  node-js-yaml3.13.1+dfsg-2~bpo10+1
ii  node-jszip  3.2.2+dfsg-1~bpo10+1
ii  node-jszip-utils0.0.2+dfsg-2~bpo10+1
ii  node-lodash 4.17.21+dfsg+~cs8.31.189.20210220-1~bpo10+1
ii  node-marked 0.5.1+dfsg-1
ii  node-mermaid

Bug#988232: wine64-development: new wine 5.9 always fails with chdir to /tmp/.wine-... : No such file or directory

[Antoine Le Gonidec]

This is most probably the same bug than already reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988195



OpenPGP_signature
Description: OpenPGP digital signature

Bug#987203: gitlab: can not set user avatar

[Antoine Le Gonidec]

I do not reproduce my initial issue on a fresh install of GitLab using Buster 
Fast Track, so I think it was due to some misconfiguration of my previous 
instance.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#987203: gitlab: can not set user avatar

[Antoine Le Gonidec]

Package: gitlab
Version: 13.9.6+ds1-1~fto10+1
Severity: normal

Setting the avatar for a user account fails, due to the JavaScript
"pop-up" titled "Position and size your new avatar" being broken. Some
script fails, and cause this pop-up to be unusable, it buttons having no
effect (zoom buttons, and validation button).

On opening this pop-up, the following JavaScript error is thrown:
Uncaught TypeError: this.modalCropImg.cropper is not a function
The JavaScript file spawning this error is:
(…)/assets/webpack/commons-pages.profiles-pages.profiles.accounts.show-pages.profiles.index-pages.profiles.keys-pages.(…).chunk.js

Setting the avatar of a project is not affected, since it does not
rely on this zoom/crop JavaScript step.

The GitLab instance I experience this issue on is installed using the
buster-fasttrack repository,
cf. https://wiki.debian.org/gitlab#Buster_Fast_Track_.28Recommended.29

Bug#969174: firefox: FF80 broke webext-* add-ons on existing profiles and new profiles after three restarts

[Antoine Le Gonidec]

On Wed, 10 Mar 2021 06:00:12 +0900 Mike Hommey  wrote:

> While add-ons get "eventually" loaded, there seems to be a small time
> window in which they're not and during that, content is already loaded.
> (…)

This is not the same issue at all, and this is not new in FF80 either.
It has been this way for, essentially, ever. If you want to file a
separate bug for this, fine, but piling on this unrelated bug, with all
its history being unrelated to this, is not helpful.


There is probably some confusion here.

The issue described by Christoph Anton Mitterer does not happen on a Debian 
Buster using Firefox ESR 78.9.0. I only see it on Debian Sid with Firefox 87.0.

I have not tried older versions of Firefox yet, and do not remember if this is a new 
behaviour introduced by Firefox 87 or if it already happened since Firefox 85 and the 
original report that the loading failure was "fixed". I am quite sure I never 
saw that before the issue that triggered the current bug report.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#969174: firefox: FF80 broke webext-* add-ons on existing profiles and new profiles after three restarts

[Antoine Le Gonidec]

On Thu, 25 Mar 2021 01:54:53 +0100 Christoph Anton Mitterer 
 wrote:

Anyway, it seems with FF87, Mozilla blessed people with further
goodness and the old bug is also back again... at least I see add-ons
like ublock or no-script ineffective, even though their icon is
displayed this time...

Firefox 87.0-1 here, from Debian Sid repositories.
The following add-ons installed from Debian repositories seem to work as 
expected:
- webext-ublock-origin-firefox 1.33.0+dfsg-1
- webext-umatrix 1.4.0+dfsg-1

Requests that are supposed to be blocked are indeed blocked according to 
Firefox network inspection tool.

Bug#983242: wine-development recent upgrade (5.6-1?) broke levelator.exe

[Antoine Le Gonidec]

On Sun, 21 Feb 2021 14:22:19 +0100 Alex Andreotti  
wrote:

I been using a script to level wav files for more than a year without problems, 
until few day ago, I guess it was the upgrade to version 5.6-1 but I'm not sure


In bug #983117 there is a series of commands showing how to downgrade to 
wine-development 5.5-9:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983117#5

Following it would allow you to check is your issue happens with 5.5-9 too, or 
if actually started happening with 5.6-1.

Here is a copy for convenience (all commands as root):

cat > /etc/apt/sources.list.d/snapshot-20201026T024334Z.list << EOF
# wine-development 5.5-9
# cf. https://snapshot.debian.org/package/wine-development/5.5-9/
deb [check-valid-until=no] 
https://snapshot.debian.org/archive/debian/20201026T024334Z/ sid main
EOF
apt update
apt install 
{libwine-development:{amd64,i386},wine32-development:i386,wine64-development,wine-development}=5.5-9



OpenPGP_signature
Description: OpenPGP digital signature

Bug#983117: dxvk: failure to apply on a clean prefix, due to a symlink creation issue

[Antoine Le Gonidec]

After a bit more thinking it probably makes more sense to assign this bug to 
wine-development, as this is a wine-development update that broke dxvk.

Severity should probably be adjusted too, as this does not make 
wine-development unusable but still breaks dxvk, a related package.
But I am not sure what severity level would be appropriate for such an issue.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#962259: Creating Webhooks fails and returns error 500

[Antoine Le Gonidec]

Le 16/02/2021 à 21:50, Maximilian Stein a écrit :

I used apt-rdepends(1) to limit the output of dpkg to (recursive) dependencies 
of gitlab:

apt-rdepends gitlab | grep '^\w' | awk '{print "^ii  " $0}' > gitlab-rdepends

dpkg -l | grep --file=gitlab-rdepends


Attached is the output on my own server, where the issue is not triggered.


gitlab-dependencies-versions.txt.gz
Description: application/gzip


OpenPGP_signature
Description: OpenPGP digital signature

Bug#962259: Creating Webhooks fails and returns error 500

[Antoine Le Gonidec]

On Tue, 16 Feb 2021 18:38:42 +0100 Maximilian Stein  wrote:
This is weird, it still fails for me. I tested on two independent 
instances both using gitlab 13.6.7-1~fto10+1 and ruby-attr-encrypted 
3.1.0-3~bpo10+1. I tested with a user with activated and with 
deactivated 2FA. In all cases, accessing "-/profile/two_factor_auth" 
failed with error 500.


From what I remember of your interventions in other bug reports, you tend to 
favour the packages versions from buster-backports?
Here I try to minimise the use of buster-backports in favour of regular buster 
versions as much as possible, so the differences between our instances might be 
on this front.

Registrations are open on my instance, that can be found at 
forge.my-email-domain
Feel free to open an account there for testing purposes, as I am not a user of 
2FA I might have missed something in my quick test.

If the bug end up happening only on your instances and not on mine, we might 
find what triggers it by comparing `dpkg -l | grep ^ii` output and being 
careful about differences in packages versions.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#962259: Creating Webhooks fails and returns error 500

[Antoine Le Gonidec]

This issue should have been fixed by ruby-attr-encrypted 3.1.0-3~bpo10+1 from 
buster-backports.
See the following bug report for more details: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968971



OpenPGP_signature
Description: OpenPGP digital signature

Bug#958445: gitlab: 500 error on two-factor auth page

[Antoine Le Gonidec]

This issue should have been fixed by ruby-attr-encrypted 3.1.0-3~bpo10+1 from 
buster-backports.
See the following bug report for more details: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968971

A quick test from a GitLab instance using gitlab 13.6.7-1~fto10+1 and 
ruby-attr-encrypted 3.1.0-3~bpo10+1 did not trigger any issue on the 
/profile/two_factor_auth page.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

[Antoine Le Gonidec]

After a couple days of regular Web browsing on two different computers running 
Debian Sid, the silent add-on disabling did not happen again.
I marked this bug as fixed in version 85.0.1-1 since no one reported otherwise, 
but feel free to chime in if you actually still get this issue with 85.0.1-1 
(or newer).



OpenPGP_signature
Description: OpenPGP digital signature

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

[Antoine Le Gonidec]

On Tue, 9 Feb 2021 06:41:20 +0900 Mike Hommey  wrote:

I can confirm, but while I was also able to reproduce with older
versions of Firefox, I can't reproduce it anymore... so I'm not sure...


I still reproduce the silent disabling of add-ons when reverting to firefox 
84.0.2-1.

Here is how I reproduce it:
1. Download and install old packages from 
https://snapshot.debian.org/package/firefox/84.0.2-1/
- 
https://snapshot.debian.org/archive/debian/20210107T083505Z/pool/main/f/firefox/firefox_84.0.2-1_amd64.deb
- 
https://snapshot.debian.org/archive/debian/20210107T023443Z/pool/main/f/firefox/firefox-l10n-fr_84.0.2-1_all.deb
2. Create an empty directory to use as a Firefox profile, then run/quit Firefox 
3 times using the options proposed by Paul Wise
- firefox -no-remote -profile tmp-firefox-profile (×3)

With 84.0.2-1, the add-ons are disabled as soon as the third launch.
With 85.0.1-1, the add-ons are not disabled. But the add-on icons "flash" once, 
like they were quickly disabled/enabled on launch. Icons from add-ons that are not 
installed from Debian repositories do not show this quick disabling/enabling behaviour on 
launch.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

[Antoine Le Gonidec]

With firefox 85.0.1-1, my extensions installed from Debian repositories are no 
longer disabled on launch.

I made sure to restart Firefox several times to not get tricked by the 
temporary normal behaviour right after a firefox update. I browsed a couple Web 
pages too, to check that the add-ons are actually working and not merely 
showing as active.

- firefox 85.0.1-1
- webext-ublock-origin-firefox 1.32.0+dfsg-1
- webext-umatrix 1.4.0+dfsg-1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977701: gitlab: Missing assets, breaking some functionalities

[Antoine Le Gonidec]

On Fri, 22 Jan 2021 21:00:52 +0100 Antoine Le Gonidec 
 wrote:

As I am affected too I am going to give it a try, and report the result here.


After a couple days using the packaged 13.5.7-1~fto+1 version of GitLab, I have 
no issue to report. None of the bugs I initially reported are still happening.
Thanks for the good work fixing this ;)



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977701: gitlab: Missing assets, breaking some functionalities

[Antoine Le Gonidec]

On Thu, 21 Jan 2021 20:21:38 +0100 Maximilian Stein  wrote:
My broken pages are actually fixed with Gitlab 13.5.7-1. So for my side, 
this issue can be closed.


Great news!
As I am affected too I am going to give it a try, and report the result here.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977701: gitlab: Missing assets, breaking some functionalities

[Antoine Le Gonidec]

Oops, sorry for the extra messages quoting the opening message of this thread, 
Thunderbird decided to act funny.
They can be discarded, the message about the upcoming 13.5.6 package was the 
only one that was supposed to be sent.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977701: gitlab: Missing assets, breaking some functionalities

[Antoine Le Gonidec]

I see a new update (13.5.6) is available through fasttrack-staging. Is it 
supposed to include a fix for the missing assets issue discussed here, or would 
it probably still trigger it?

I should be able to give it a try on my server, reverting to a snapshot 
afterwards if the issue is not fixed yet.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977701: gitlab: Missing assets, breaking some functionalities

[Antoine Le Gonidec]

On Sat, 19 Dec 2020 07:03:18 +0100 Antoine Le Gonidec 
 wrote:

Reverting the gitlab package to 13.4.7-1~fto10+1 did not fix the issue. I have 
yet to try a full update of the update I did that included this package, here 
are the details according to APT history:

Start-Date: 2020-12-18  22:00:20
Commandline: apt install gitlab node-autosize/buster-backports fonts-font-awesome/buster-backports node-uuid/buster-backports node-request/buster-backports   
Install: fonts-katex:amd64 (0.10.2+dfsg-4~bpo10+1, automatic), node-match-at:amd64 (0.1.1-1, automatic), katex:amd64 (0.10.2+dfsg-4~bpo10+1, automatic), libjs-katex:amd64 (0.10.2+dfsg-4~bpo10+1, automatic), node-mermaid:amd64 (8.7.0+ds+~cs27.17.17-2~bpo10+1, automatic)
Upgrade: fonts-font-awesome:amd64 (5.0.10+really4.7.0~dfsg-1, 5.0.10+really4.7.0~dfsg-4~bpo10+1), node-autosize:amd64 (4.0.2~dfsg1-3, 4.0.2~dfsg1-5~bpo10+1), node-request:amd64 (2.88.1-2, 2.88.1-5~bpo10+1), gitlab:amd64 (13.4.7-1~fto10+1, 13.4.7-2~fto10+1), node-uuid:amd64 (3.3.2-2, 8.3.2+~8.3.0-1~bpo10+1)  
Error: Sub-process /usr/bin/dpkg returned an error code (1)

End-Date: 2020-12-18  22:21:04


Reverting this update did not fix the issue, I ended up restoring a server 
backup prior to it.

This update is the only difference I can see between the restored backup and 
the situation triggering the JavaScript-related issues, so I guess it applies 
some change than is not reverted by going back to the previous package versions.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977701: gitlab: Missing assets, breaking some functionalities

[Antoine Le Gonidec]

Package: gitlab
Version: 13.4.7-2~fto10+1
Severity: important

On a Debian Buster using the buster-fasttracks, the update from 
13.4.7-1~fto10+1 to 13.4.7-2~fto10+1 included some changes in the assets 
generation process, that broke some parts of the JavaScript interactions with 
GitLab.

Two examples allowing to observe this issue:
- From a merge request edition form, the target branch can not be changed
- From the list of merge requests in a user dashboard, the top right green menu 
supposed to allow the creation of a new merge request show an ininfinite 
spinning animation instead

I suspect this is related to a 404 error I get when trying to fetch 
/assets/webpack/components/app.vue
There is indeed no such file generated in /usr/share/gitlab/public

Reverting the gitlab package to 13.4.7-1~fto10+1 did not fix the issue. I have 
yet to try a full update of the update I did that included this package, here 
are the details according to APT history:

Start-Date: 2020-12-18  22:00:20
Commandline: apt install gitlab node-autosize/buster-backports 
fonts-font-awesome/buster-backports node-uuid/buster-backports 
node-request/buster-backports   
Install: fonts-katex:amd64 (0.10.2+dfsg-4~bpo10+1, automatic), 
node-match-at:amd64 (0.1.1-1, automatic), katex:amd64 (0.10.2+dfsg-4~bpo10+1, 
automatic), libjs-katex:amd64 (0.10.2+dfsg-4~bpo10+1, automatic), 
node-mermaid:amd64 (8.7.0+ds+~cs27.17.17-2~bpo10+1, automatic)  
  
Upgrade: fonts-font-awesome:amd64 (5.0.10+really4.7.0~dfsg-1, 
5.0.10+really4.7.0~dfsg-4~bpo10+1), node-autosize:amd64 (4.0.2~dfsg1-3, 
4.0.2~dfsg1-5~bpo10+1), node-request:amd64 (2.88.1-2, 2.88.1-5~bpo10+1), 
gitlab:amd64 (13.4.7-1~fto10+1, 13.4.7-2~fto10+1), node-uuid:amd64 (3.3.2-2, 
8.3.2+~8.3.0-1~bpo10+1)  
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2020-12-18  22:21:04

The dpkg error code is actually a recurring issue I have that does not seem to 
be related to the issue at hand, and is always fixed by running `dpkg 
--configure -a`.

-- System Information:
Debian Release: 10.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (150, 
'buster-fasttrack'), (150, 'buster-backports'), (110, 'testing'), (100, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gitlab depends on:
ii  asciidoctor   2.0.10-2~bpo10+1
ii  bc1.07.1-2+b1
ii  bundler   2.1.4-2~bpo10+1
ii  bzip2 1.0.6-9.2~deb10u1
ii  dbconfig-pgsql2.0.11+deb10u1
ii  debconf [debconf-2.0] 1.5.71
ii  fonts-font-awesome [node-font-awesome]5.0.10+really4.7.0~dfsg-4~bpo10+1
ii  gitlab-common 13.4.6+dfsg1-2~fto10+1
ii  gitlab-workhorse  8.46.0+debian-1~bpo10+1
ii  katex [node-katex]0.10.2+dfsg-4~bpo10+1
ii  libjs-bootstrap4 [node-bootstrap] 4.3.1+dfsg2-1
ii  libjs-codemirror [node-codemirror]5.54.0-2~bpo10+1
ii  libjs-pdf [node-pdfjs-dist]   2.6.347+dfsg-3~bpo10+1
ii  libjs-popper.js [node-popper.js]  1.14.6+ds2-1
ii  libjs-uglify  2.8.29-6
ii  libruby2.7 [ruby-json]2.7.1-3+fto10+2
ii  lsb-base  10.2019051400
ii  nginx 1.14.2-2+deb10u3
ii  nginx-full [nginx]1.14.2-2+deb10u3
ii  node-autosize 4.0.2~dfsg1-5~bpo10+1
ii  node-axios0.17.1+dfsg-2
ii  node-babel-loader 8.2.2-1~bpo10+1
ii  node-babel7   7.4.5+~cs7.3.8-1~bpo10+1
ii  node-brace-expansion  1.1.8-1
ii  node-cache-loader 4.1.0-6~bpo10+1
ii  node-chart.js 2.7.3+dfsg-5
ii  node-clipboard2.0.6+ds-1~bpo10+1
ii  node-compression-webpack-plugin   3.0.1-4~bpo10+1
ii  node-copy-webpack-plugin  5.1.2+~cs9.0.2-4~bpo10+1
ii  node-core-js  3.6.1-2~bpo10+2
ii  node-css-loader   3.2.1+~cs21.3.8.1-2~bpo10+1
ii  node-d3   5.16.0-1~bpo10+1
ii  node-d3-scale 2.2.2-2~bpo10+1
ii  node-d3-selection 1.4.0-3~bpo10+1
ii  node-dateformat   3.0.0-1
ii  node-exports-loader   0.7.0-2~bpo10+1
ii  node-file-loader  6.2.0-2~bpo10+1
ii  node-fuzzaldrin-plus  0.5.0+dfsg-1
ii  node-glob  

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

[Antoine Le Gonidec]

Le 30/11/2020 à 18:02, Mourad De Clerck a écrit :

Can you verify in "about:support" whether webrender is really disabled? I see:
* "Compositing: Basic"
* "WEBRENDER: disabled by user: User force-disabled WR"


Informations from the "WEBRENDER" tab are:
- available by default
- disabled by user: User force-disabled WR
- disabled by env: Not qualified

"Composition" is set to "Basic".

My add-ons installed from Debian repositories are still silently disabled on 
launch, I have to switch them off then on again to get them working for the 
current session. And of course start again when I restart Firefox.

It does not seem the disabling of webrender changed anything for me. Actually I 
did not check if it was in use before I force-disabled it.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

[Antoine Le Gonidec]

Le 29/11/2020 à 16:25, Mourad De Clerck a écrit :

As a workaround, I disabled webrender using "gfx.webrender.force-disabled" set to 
"true", and my extensions (ublock, bitwarden) seem to work properly again.


Did you check that the add-ons are still active after a couple restarts of 
Firefox?
The suggested workaround seems to have no effect here.

All installed from Debian Sid repositories:
- Firefox 83.0-1
- webext-ublock-origin-firefox 1.30.0+dfsg-1
- webext-umatrix 1.4.0+dfsg-1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#968971: gitlab: Can't create new project: undefined method `set_attribute_was'

[Antoine Le Gonidec]

Here I am running 13.2.8-1+fto10+2 on top of a Debian Buster, following the recommended 
"FastTrack" installation method.

I get a similar error related to a missing "set_attribute_was" method when 
trying to add a new push mirror to an existing repository.

The only mentions I found of this method are in the following packages:
- ruby-acts-as-taggable-on: 
/usr/lib/ruby/vendor_ruby/acts_as_taggable_on/taggable/core.rb
- ruby-attr-encrypted: 
/usr/lib/ruby/vendor_ruby/attr_encrypted/adapters/active_record.rb

Both are installed from Buster backports:
- ruby-acts-as-taggable-on: 6.5.0-2~bpo10+1
- ruby-attr-encrypted: 3.1.0-2~bpo10+1

The method "set_attribute_was" used to be provided by ruby-activemodel in its 
5.* version (Buster and official Buster backports), but is not part of the 6.* version 
(FastTrack-provided backports).

If I remove the calls to "set_attribute_was" from the two listed .rb files and 
restart the gitlab service, I no longer get the crash on addition of a new push mirror. I 
attached the edited source files to this e-mail for testing purposes, but keep in mind 
that I am not a Ruby developer, I only removed some part of the scripts without worrying 
about the consequences. If you use these edited files without a careful review, things 
are expected to break in unexpected ways ;)


gitlab-set_attribute_was-crash-fixed-source-files.tar.xz
Description: application/xz


OpenPGP_0x4E34F6017289428A.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

[Antoine Le Gonidec]

On Wed, 23 Sep 2020 15:54:06 +0800 Paul Wise  wrote:
> This appears to be fixed for me in 81.0-1, can anyone else confirm?

Here it looked like it was fixed right after the update.

But very quickly after that (3 browser restarts), the add-ons are disabled once 
again. Now I’m back to the previous behaviour, with add-ons silently disabled 
on launch.

I get the same behaviour on two distinct Debian Bullseye/Sid, on each one the 
add-ons disabling is back on the third Firefox restart.

Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles

[Antoine Le Gonidec]

I think the severity of this bug should be upped to at least "important".

The reasoning here is that any privacy-related add-on installed through Debian 
repositories is automatically (and silently) disabled on launch, leading to 
privacy leaks when opening a link in Firefox from another application (like a 
mail client or a chat application). So the issues related to this bug are not 
limited to quality of life, they can have a real impact on user privacy and 
could hurt the trust users have for the Debian-packaged versions of Firefox and 
WebExtensions.

Bug#966653: gitlab: [BUG] Segmentation fault at 0x0000000000000000

[Antoine Le Gonidec]

I got bitten by the same crash during a system upgrade from Buster 10.4 to 
Buster 10.5, on a system using the Buster Fasttrack repositories.

Reverting the older versions of the following packages allowed me to avoid the 
crash:
- ruby-google-protobuf:amd64=3.11.4-5+fto10+1
- ruby-grpc:amd64=1.26.0-3+fto10+1

So the following command might help work around it for people that get this 
crash on a Debian Buster:
apt install ruby-google-protobuf:amd64=3.11.4-5+fto10+1 
ruby-grpc:amd64=1.26.0-3+fto10+1

I use no instance of GitLab on Bullseye/Sid, so sadly I am not able to run 
tests in this context.

Bug#962259: Creating Webhooks fails and returns error 500

[Antoine Le Gonidec]

I think I found another issue that has the same source than the one reported 
here.

When trying to enable 2-factor authentication on a user account:

Started GET "/profile/two_factor_auth" for :::: at 
2020-08-08 22:28:29 +0200
Processing by Profiles::TwoFactorAuthsController#show as HTML
Completed 500 Internal Server Error in 419ms (ActiveRecord: 18.7ms | 
Elasticsearch: 0.0ms | Allocations: 113618)
  
NoMethodError (undefined method `set_attribute_was' for #
Did you mean?  custom_attributes):
  
app/controllers/profiles/two_factor_auths_controller.rb:8:in `show'
app/controllers/application_controller.rb:497:in `set_current_admin'
lib/gitlab/session.rb:11:in `with_session'
app/controllers/application_controller.rb:488:in `set_session_storage'
lib/gitlab/i18n.rb:55:in `with_locale'
lib/gitlab/i18n.rb:61:in `with_user_locale'
app/controllers/application_controller.rb:482:in `set_locale'
lib/gitlab/error_tracking.rb:51:in `with_context'
app/controllers/application_controller.rb:547:in `sentry_context'
app/controllers/application_controller.rb:475:in `block in set_current_context'
lib/gitlab/application_context.rb:52:in `block in use'
lib/gitlab/application_context.rb:52:in `use'
lib/gitlab/application_context.rb:20:in `with_context'
app/controllers/application_controller.rb:468:in `set_current_context'
lib/gitlab/request_profiler/middleware.rb:17:in `call'
lib/gitlab/middleware/go.rb:20:in `call'
lib/gitlab/etag_caching/middleware.rb:13:in `call'
lib/gitlab/middleware/multipart.rb:125:in `call'
lib/gitlab/middleware/read_only/controller.rb:51:in `call'
lib/gitlab/middleware/read_only.rb:18:in `call'
lib/gitlab/middleware/same_site_cookies.rb:27:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/middleware/handle_ip_spoof_attack_error.rb:25:in `call'
lib/gitlab/middleware/request_context.rb:23:in `call'
config/initializers/fix_local_cache_middleware.rb:9:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:60:in `call'
lib/gitlab/middleware/release_env.rb:12:in `call'



signature.asc
Description: OpenPGP digital signature

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

[Antoine Le Gonidec]

On Thu, 28 Sep 2017 23:15:27 +0200 Salvo Tomaselli 
wrote:
> I had downgraded my mesa. I wanted to try again but I can't upgrade it
> because of some llvm breakage at the moment.
> (…)
> I seguenti pacchetti hanno dipendenze non soddisfatte:
> libllvm5.0 : Rompe: libllvm5.0:i386 (!= 1:5.0-2) but 1:5.0-1 is to be 
> installed
> libllvm5.0:i386 : Rompe: libllvm5.0 (!= 1:5.0-1) but 1:5.0-2 is installed

You can still install these packages without waiting for the resolution
of bug #876752 by forcing the highest common version for these two
architectures:
apt install libllvm5.0{,:i386}=1:5.0~+rc2-1

You need to have the testing repositories in your APT sources or this
won’t work.



signature.asc
Description: OpenPGP digital signature

Bug#761189: coreutils: wrong 'info' command in ls manpage

[Antoine Le Gonidec]

Package: coreutils
Version: 8.23-2
Severity: minor

Dear Maintainer,
At the end of the ls manpage we have the following instruction :

SEE ALSO
   The  full documentation for ls is maintained as a Texinfo manual.  If 
the info and ls programs are properly installed at your site, the command

  info coreutils 'ls invocation'

   should give you access to the complete manual.

-

The command should be :
info ls

instead of :
info coreutils 'ls invocation'

The latter returns :
No menu in node `(coreutils.info.gz)coreutils invocation'.

-- System Information:
Debian Release: jessie/sid
  APT prefers stable-updates
  APT policy: (900, 'stable-updates'), (900, 'unstable'), (900, 'testing'), 
(900, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages coreutils depends on:
ii  libacl1  2.2.52-2
ii  libattr1 1:2.4.47-2
ii  libc62.19-10
ii  libselinux1  2.3-2

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#728842: libtag1c2a: tag display messed up with mpd clients

[Antoine Le Gonidec]

Package: libtag1c2a
Version: 1.9.1-2
Severity: normal
Tags: upstream

Dear Maintainer,
After editing tags in ncmpcpp or sonata, the tag display is messed up for the 
files edited.
The tag itself remains right (reverting back to Jessie version of the lib gives 
back the correct display),
but it is displayed with Chinese characters instead of Latin ones.

Easy to reproduce: in any MPD client (wild guess, tested with sonata and 
ncmpcpp only),
edit one tag field in any music file (tested with FLAC only),
and once the editing is done every other field on the same file will be 
displayed with Chinese characters.
I found no other way to get back the correct display than reverting back to 
libtag1c2a 1.8-2.

Tested with MPD 0.18-1 only.

Ask me if any other information would be useful ;)

PS: I tagged upstream because I've seen this bug reported on archlinux forums 
too.
I didn't try to compile the upstream version of the library to check.

-- System Information:
Debian Release: jessie/sid
  APT prefers stable-updates
  APT policy: (900, 'stable-updates'), (900, 'oldstable-updates'), (900, 
'unstable'), (900, 'testing'), (900, 'stable'), (900, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libtag1c2a depends on:
ii  libtag1-vanilla  1.9.1-2

libtag1c2a recommends no packages.

libtag1c2a suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#713808: minetest: icon filename and Icon field in .desktop file don't match

[Antoine Le Gonidec]

Package: minetest
Version: 0.4.7+repack-2
Severity: minor

from minetest.desktop:
Icon=minetest-icon

list of icons provided by the package:
/usr/share/icons/hicolor/24x24/apps/minetest.xpm
/usr/share/icons/hicolor/24x24/apps/minetest.png
/usr/share/icons/hicolor/scalable/apps/minetest.svg

The Icon line in minetest.desktop should probably be changed to:
Icon=minetest

-- System Information:
Debian Release: jessie/sid
  APT prefers stable-updates
  APT policy: (600, 'stable-updates'), (600, 'unstable'), (600, 'testing'), 
(600, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages minetest depends on:
ii  libc62.17-5
ii  libcurl3-gnutls  7.30.0-2
ii  libfreetype6 2.4.9-1.1
ii  libgcc1  1:4.8.1-3
ii  libirrlicht1.8   1.8+dfsg1-2
ii  libjsoncpp0  0.6.0~rc2-3
ii  libjthread1.3.1  1.3.1-3
ii  libluajit-5.1-2  2.0.2+dfsg-1
ii  libogg0  1.3.1-1
ii  libopenal1   1:1.14-4
ii  libsqlite3-0 3.7.17-1
ii  libstdc++6   4.8.1-3
ii  libvorbis0a  1.3.2-1.3
ii  libvorbisfile3   1.3.2-1.3
ii  minetest-data0.4.7+repack-2
ii  zlib1g   1:1.2.8.dfsg-1

minetest recommends no packages.

Versions of packages minetest suggests:
ii  minetest-server  0.4.7+repack-2

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711990: midori: Program received signal SIGFPE on specific website

[Antoine Le Gonidec]

I've done some tests:
the crash only appear if WebGL is enabled.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711990: midori: Program received signal SIGFPE on specific website

[Antoine Le Gonidec]

Package: midori
Version: 0.4.3+dfsg-0.1
Severity: normal

Dear Maintainer,
midori crash with a SIGFPE arithmetic exception error when trying to load this 
website:
http://www.klaire.fr/
I didn't find any other website giving this error yet.
It is not reproductible with WebKit's GtkLauncher.

Here is the backtrace provided by gdb:

 Starting program: /usr/bin/midori 
 warning: no loadable sections found in added symbol-file system-supplied DSO 
at 0x77ffa000
 warning: Could not load shared library symbols for linux-vdso.so.1.
 Do you need set solib-search-path or set sysroot?
 [Thread debugging using libthread_db enabled]
 Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
 [New Thread 0x7fffe862a700 (LWP 24175)]
 [New Thread 0x7fffa7d27700 (LWP 24176)]
 [New Thread 0x7fffa7115700 (LWP 24177)]
 [New Thread 0x7fffa52ee700 (LWP 24178)]
 /usr/share/themes/Shiki-Wise/gtk-2.0/gtkrc:126: Murrine configuration option 
gradients is no longer supported and will be ignored.
 [New Thread 0x7fff8f3a7700 (LWP 24179)]
 [New Thread 0x7fff8d11c700 (LWP 24180)]
 [New Thread 0x7fff87fff700 (LWP 24181)]
 [New Thread 0x7fff877fe700 (LWP 24182)]
 [New Thread 0x7fff86ffd700 (LWP 24183)]
 [New Thread 0x7fff867fc700 (LWP 24184)]
 [New Thread 0x7fff85ffb700 (LWP 24185)]
 [New Thread 0x7fff84cb3700 (LWP 24186)]
 
 Program received signal SIGFPE, Arithmetic exception.
 0x7fff84cb8edc in ?? () from /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1

-

libdrm_radeon.so.1 is part of the libdrm-radeon1 package, present in version 
2.4.45-3 on my system.

Tell me if you need any other information ;)

-- System Information:
Debian Release: jessie/sid
  APT prefers stable-updates
  APT policy: (600, 'stable-updates'), (600, 'unstable'), (600, 'testing'), 
(600, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.9-5.slh.1-aptosid-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages midori depends on:
ii  dbus-x111.6.10-1
ii  libc6   2.17-5
ii  libcairo2   1.12.14-4
ii  libgdk-pixbuf2.0-0  2.28.2-1
ii  libglib2.0-02.36.1-2build1
ii  libgtk2.0-0 2.24.18-1
ii  libjavascriptcoregtk-1.0-0  1.8.1-3.4
ii  libnotify4  0.7.5-2
ii  libpango1.0-0   1.32.5-5+b1
ii  libsoup2.4-12.42.2-5
ii  libsqlite3-03.7.17-1
ii  libunique-1.0-0 1.1.6-4
ii  libwebkitgtk-1.0-0  1.8.1-3.4
ii  libx11-62:1.5.0-1+deb7u1
ii  libxml2 2.8.0+dfsg1-7+nmu1
ii  libxss1 1:1.2.2-1

Versions of packages midori recommends:
ii  gnome-icon-theme  3.4.0-2

midori suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711990: midori: Program received signal SIGFPE on specific website

[Antoine Le Gonidec]

I forgot a part of gdb speech on my first post, here it is:
(gdb) bt
 #0  0x7fff84cb8edc in ?? () from
/usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1
 #1  0x7fff84cb926b in ?? () from
/usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1
 #2  0x7fff851e2ae1 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
 #3  0x7fff851e3177 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
 #4  0x7fff851f59a6 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
 #5  0x7fff851f4315 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
 #6  0x7fff850466c6 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
 #7  0x7fff85047903 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
 #8  0x7fff851f3a3a in dri_make_current () from
/usr/lib/x86_64-linux-gnu/dri/r600_dri.so
 #9  0x7fff84f215f6 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
 #10 0x7fffecdf6baf in ?? () from /usr/lib/x86_64-linux-gnu/libGL.so.1
 #11 0x7fffecdcf476 in glXMakeCurrentReadSGI () from
/usr/lib/x86_64-linux-gnu/libGL.so.1
 #12 0x74ab6e5b in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 #13 0x74ab6ee5 in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 #14 0x74abc48a in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 #15 0x74ab24c5 in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 #16 0x74441ea1 in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 #17 0x741ad13c in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 #18 0x74c0260b in ?? () from /usr/lib/libwebkitgtk-1.0.so.0
 #19 0x7fffa7d29258 in ?? ()
 #20 0x7fff8e7d82d0 in ?? ()
 #21 0x7fffa7dc61a2 in ?? ()
 #22 0x7fff0051 in ?? ()
 #23 0x7fff8c213720 in ?? ()
 #24 0x7fff8e0d6330 in ?? ()
 #25 0x0007 in ?? ()
 #26 0x7fffa7dc218a in ?? ()
 #27 0x in ?? ()

-

I just compiled midori 0.5.2 from the sources provided there:
http://www.twotoasts.de/index.php/midori/
The crash does happen with 0.5.2 too.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#711990: midori: Program received signal SIGFPE on specific website

[Antoine Le Gonidec]

I have been able to reproduce the crash with this website:
http://notfound.org/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#708219: libwine-bin-unstable: Package is empty

[Antoine Le Gonidec]

Package: libwine-bin-unstable
Version: 1.5.7-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,
Since update 1.5.7-2, this package is nearly empty.

Here are the filelist for 1.5.6-2 and 1.5.7-4 for comparison:

root@HAL9000:/var/cache/apt/archives# dpkg-deb -c 
libwine-bin-unstable_1.5.6-2_i386.deb 
drwxr-xr-x root/root 0 2012-07-13 00:53 ./
drwxr-xr-x root/root 0 2012-07-13 00:51 ./usr/
drwxr-xr-x root/root 0 2012-07-13 00:51 ./usr/lib/
drwxr-xr-x root/root 0 2012-07-13 00:51 ./usr/lib/i386-linux-gnu/
drwxr-xr-x root/root 0 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/
-rw-r--r-- root/root280860 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/winhlp32.exe.so
-rw-r--r-- root/root 87236 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/hostname.exe.so
-rw-r--r-- root/root110024 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/rpcss.exe.so
-rw-r--r-- root/root101640 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/ipconfig.exe.so
-rw-r--r-- root/root426144 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/wordpad.exe.so
-rw-r--r-- root/root 75516 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/unlodctr.exe.so
-rw-r--r-- root/root124664 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/taskkill.exe.so
-rw-r--r-- root/root183900 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/winemine.exe.so
-rw-r--r-- root/root 75440 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/aspnet_regiis.exe.so
-rw-r--r-- root/root224568 2012-07-13 00:52 
./usr/lib/i386-linux-gnu/wine-unstable/inetcpl.cpl.so
drwxr-xr-x root/root 0 2012-07-13 00:51 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/
-rw-r--r-- root/root  4792 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/write.exe
-rw-r--r-- root/root754960 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/winecfg.exe
-rw-r--r-- root/root  8820 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/hostname.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/cabarc.exe
-rw-r--r-- root/root109356 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/xcopy.exe
-rw-r--r-- root/root 32380 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/attrib.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/expand.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/winevdm.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/sc.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/lodctr.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/regsvcs.exe
-rw-r--r-- root/root  2472 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/winver.exe
-rw-r--r-- root/root 28232 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/msiexec.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/regasm.exe
-rw-r--r-- root/root 23120 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/ipconfig.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/rpcss.exe
-rw-r--r-- root/root131820 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/inetcpl.cpl
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/control.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/winemsibuilder.exe
-rw-r--r-- root/root  5268 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/explorer.exe
-rw-r--r-- root/root 41980 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/taskkill.exe
-rw-r--r-- root/root513104 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/taskmgr.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/netsh.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/secedit.exe
-rw-r--r-- root/root 18332 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/clock.exe
-rw-r--r-- root/root 91920 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/winemine.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/svchost.exe
-rw-r--r-- root/root 67816 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/net.exe
-rw-r--r-- root/root  1032 2012-07-13 00:48 
./usr/lib/i386-linux-gnu/wine-unstable/fakedlls/cscript.exe
-rw-r--r-- root/root 29236 2012-07-13 00:48 

Bug#694677: flight-of-the-amazon-queen: no icon for .desktop file

[Antoine Le Gonidec]

Package: flight-of-the-amazon-queen
Version: 1.0.0-7
Severity: minor

Hello!

flight-of-the-amazon-queen.desktop contains the following entry:
Icon=flight-of-the-amazon-queen

No such file is provided with the package, so there is no icon for the menu 
entry (or anything using the .desktop file).

It might be modified to the following entry to use Scummvm icon:
Icon=scummvm

Anyway I intend to learn to write patches, and will submit one in a couple 
days! ;)

-- System Information:
Debian Release: wheezy/sid
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages flight-of-the-amazon-queen depends on:
ii  scummvm  1.4.1-1

flight-of-the-amazon-queen recommends no packages.

Versions of packages flight-of-the-amazon-queen suggests:
ii  gettext-base  0.18.1.1-9


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#694677: flight-of-the-amazon-queen: no icon for .desktop file - patch

[Antoine Le Gonidec]

Here is a patch which modify the desktop file to use ScummVM's icon
instead of the non-existing one.

First time I submit a patch, I hope I'm doing it right… ;)
# Description: Use ScummVM icon
#  The original desktop file tries to use a non-existing icon file resulting
#  in no icon at all being used.
#  The patched desktop file uses the existing scummvm icon instead.
# Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;bug=694677
# Author: Antoine Le Gonidec antoine.legonidec@gmail.com

--- a/debian/flight-of-the-amazon-queen.desktop
+++ b/debian/flight-of-the-amazon-queen.desktop
@@ -6,5 +6,5 @@
 Comment=Embark on a quest to rescue a kidnapped princess and in the process, discover the true sinister intentions of a suspiciously located Lederhosen company
 Type=Application
 Exec=/usr/games/scummvm -p /usr/share/scummvm/flight-of-the-amazon-queen queen
-Icon=flight-of-the-amazon-queen
+Icon=scummvm
 Categories=AdventureGame;Game;RolePlaying;