Bug#1051546: jstest-gtk: Unable to open file "data/generic.png"
Package: jstest-gtk Version: 0.1.1~git20180602-1 Severity: important X-Debbugs-Cc: arnaudme...@gmx.com Dear Maintainer, jstest-gtk immediately crashes on start, regardless on whether a controller is connected or not. When run on a terminal, it issues a message telling that it cannot open file "data/generic.png". A workaround is to change directories on the terminal and run jstest-gtk directly from its data directory: $ cd /usr/share/jstest-gtk $ jstest-gtk Regards, Arnaud Meyer. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') 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 jstest-gtk depends on: ii libatkmm-1.6-1v52.28.3-1 ii libc6 2.37-7 ii libcairomm-1.0-1v5 1.14.4-2 ii libgcc-s1 13.2.0-2 ii libglibmm-2.4-1v5 2.66.6-2 ii libgtkmm-3.0-1v53.24.8-2 ii libsigc++-2.0-0v5 2.12.0-1 ii libstdc++6 13.2.0-2 ii libx11-62:1.8.6-1 Versions of packages jstest-gtk recommends: ii joystick 1:1.8.1-1 jstest-gtk suggests no packages. -- no debconf information
Bug#1042922: scid: Crash at startup: can't set "tooltip::labelOpts": parent namespace doesn't exist
Package: scid
Version: 1:4.7.4+dfsg1-2
Severity: important
Tags: patch
X-Debbugs-Cc: arnaudme...@gmx.com
Dear Maintainer,
Upon fresh installation, Scid does not run and displays the following
message when run in a terminal:
$ scid
can't set "tooltip::labelOpts": parent namespace doesn't exist
while executing
"set tooltip::labelOpts [list -highlightthickness 0 -relief solid -bd 1
-background lightyellow -fg black -font $font]"
(in namespace eval "::utils::tooltip" script line 10)
invoked from within
"namespace eval ::utils::tooltip {
global ::utils::tooltip::font
if {![info exists font]} {
set font TkDefaultFont
}
# Undocumented toolt..."
(file "/usr/share/scid/tcl/utils/tooltip.tcl" line 11)
invoked from within
"source -encoding utf-8 [file nativename [file join $::scidTclDir "$f"]]"
("foreach" body line 2)
invoked from within
"foreach f $tcl_files {
source -encoding utf-8 [file nativename [file join $::scidTclDir "$f"]]
}"
(file "/usr/games/scid" line 674)
The problem appears to come from a very small mistake in line 20 of file
/usr/share/scid/utils:
--- original/tooltip.tcl2023-08-02 22:51:16.416479228 +0200
+++ patch/tooltip.tcl 2023-08-02 22:51:27.480313699 +0200
@@ -17,7 +17,7 @@
# Undocumented tooltip variable that allows users to extend / override
# label creation options.
- set tooltip::labelOpts [list -highlightthickness 0 -relief solid -bd 1 \
+ set ::tooltip::labelOpts [list -highlightthickness 0 -relief solid -bd 1 \
-background lightyellow -fg black -font $font]
proc Set {button msg} {
It also appears this bug was fixed in the new upstream versions.
Thanks,
Arnaud Meyer.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 scid depends on:
ii libc6 2.37-6
ii libstdc++6 13.1.0-9
ii libtcl8.6 8.6.13+dfsg-2
ii python3 3.11.4-5
ii scid-data 1:4.7.4+dfsg1-2
ii tcl 8.6.13
ii tk 8.6.13
ii zlib1g 1:1.2.13.dfsg-1
Versions of packages scid recommends:
ii libtk-img 1:1.4.14+dfsg-2
ii tcl-snack [libsnack2] 2.2.10.20090624+dfsg-1
ii tcllib 1.21+dfsg-1
ii tdom 0.9.3-1
ii texlive-games 2022.20230122-4
Versions of packages scid suggests:
pn crafty
pn glaurung
pn phalanx
pn scid-spell-data | scid-rating-data
ii stockfish 15.1-4
pn toga2
-- no debconf information
--- original/tooltip.tcl2023-08-02 22:51:16.416479228 +0200
+++ patch/tooltip.tcl 2023-08-02 22:51:27.480313699 +0200
@@ -17,7 +17,7 @@
# Undocumented tooltip variable that allows users to extend / override
# label creation options.
- set tooltip::labelOpts [list -highlightthickness 0 -relief solid -bd 1 \
+ set ::tooltip::labelOpts [list -highlightthickness 0 -relief solid -bd 1 \
-background lightyellow -fg black -font $font]
proc Set {button msg} {
Bug#955757: wxhexeditor: Some differing bytes are missed by the comparison engine
Package: wxhexeditor
Version: 0.24+repack-1
Severity: normal
Tags: patch
Dear Maintainer,
Using the (immensely useful) comparison feature in wxHexEditor, I
noticed some bytes are being "missed" by the comparison engine: they are
not marked as differing even though they actually are.
Here is a minimal working example with two files of 12 bytes:
Int | 012
Byte | 0 1 2 3 4 5 6 7 8 9 10 11
---+--
test_file0 | 00 00 00 00 00 00 00 00 00 00 00 00
test_file1 | 00 00 00 11 00 00 00 00 22 33 00 00
Differing bytes at offsets 3 and 9 are detected successfully, but not
the one at offset 8.
This appears to be due to the comparison engine switching back and forth
between integer comparison (for increased performance) and byte comparison.
This process involves a pointer which is increased either by increments
of 1 (when comparing bytes) or sizeof(int) (when comparing integers). In
some situations like the one above, it may happen that the coarse
increase can cause the pointer to skip a byte.
A patch is attached with a quick fix for this problem: a small check is
added to ensure that coarse increase of the pointer is disabled if
pointer value is not a multiple of sizeof(int).
Thanks,
Arnaud Meyer.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled
Versions of packages wxhexeditor depends on:
ii libc6 2.30-2
ii libdisasm00.23-6+b1
ii libgcc-s1 [libgcc1] 10-20200324-1
ii libgcc1 1:9.2.1-25
ii libgomp1 10-20200324-1
ii libmhash2 0.9.9.9-8
ii libstdc++610-20200324-1
ii libwxbase3.0-0v5 3.0.4+dfsg-15
ii libwxgtk3.0-gtk3-0v5 3.0.4+dfsg-15
wxhexeditor recommends no packages.
wxhexeditor suggests no packages.
-- no debconf information
Fixes a bug that causes some bytes to be skipped when comparing two files.
This bug happens because the comparison engine switches from integer (for
performance) to byte (for accuracy) comparison whenever a difference is
detected. When switching back to integer comparison, an offset of sizeof(int)
is applied to the pointer. Under some configurations, this can cause at least
one byte to be missed by the comparison engine.
This quick fix ensures that applying an offset of sizeof(int) to the pointer is
performed only when said pointer position is a multiple of sizeof(int).
--- a/src/HexDialogs.cpp
+++ b/src/HexDialogs.cpp
@@ -2347,7 +2347,7 @@
//Here we made the comparison on
INTEGER for speedup
if(
bfr_int1[i/sizeof(int)]==bfr_int2[i/sizeof(int)] ){
//bytes are eq, goto check next
integer
- if( !diff ){
+ if( !diff && ((i % sizeof(int))
== 0) ){
i+=sizeof(int);
continue;
}
Bug#906516: gimp: Segfault with libopenblas-base
Package: gimp Version: 2.10.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, On my very first try running GIMP 2.10 since it finally was available to testing, it was unusable, giving only a segfault message on command line after hitting CTRL+C : $ gimp [CTRL+C] ^CErreur de segmentation $ Looking for an already registered bug for this obvious problem, I found somebody in #906244 suggesting to remove libopenblas-base. This was not the solution to #906244, but it worked perfectly in my case. So, on my system, libopenblas-base renders GIMP unusable. Removing it makes GIMP 2.10 work again. I have no use for libopenblas-base, which was probably installed as a dependecy for something else, but there surely are other users who would like to work with both packages. Thank you in advance, Arnaud Meyer. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.2-1 ii libaa1 1.4p5-44+b2 ii libbabl-0.1-00.1.54-1 ii libbz2-1.0 1.0.6-8.1 ii libc62.27-5 ii libcairo21.15.10-3 ii libfontconfig1 2.13.0-5 ii libfreetype6 2.8.1-2 ii libgcc1 1:8.2.0-3 ii libgdk-pixbuf2.0-0 2.36.12-1 ii libgegl-0.4-00.4.6-1 ii libgexiv2-2 0.10.8-1 ii libgimp2.0 2.10.2-1 ii libglib2.0-0 2.56.1-2 ii libgs9 9.22~dfsg-2.1 ii libgtk2.0-0 2.24.32-2 ii libgudev-1.0-0 232-2 ii libharfbuzz0b1.8.7-1 ii libheif1 1.3.2-1 ii libilmbase23 2.2.1-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-2 ii liblzma5 5.2.2-1.3 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.3-0 1.3.0-2 ii libopenexr23 2.2.1-4 ii libopenjp2-7 2.3.0-1 ii libpango-1.0-0 1.42.1-2 ii libpangocairo-1.0-0 1.42.1-2 ii libpangoft2-1.0-01.42.1-2 ii libpng16-16 1.6.34-2 ii libpoppler-glib8 0.63.0-2 ii librsvg2-2 2.40.20-2 ii libstdc++6 8.2.0-3 ii libtiff5 4.0.9-6 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2 ii libwmf0.2-7 0.2.8.4-12 ii libx11-6 2:1.6.5-1 ii libxcursor1 1:1.1.15-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gimp recommends: ii ghostscript 9.22~dfsg-2.1 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help pn gimp-python ii gvfs-backends 1.36.2-1 ii libasound21.1.6-1 -- no debconf information
Bug#897958: plymouth: long delay before splashscreen with kernel 4.16
From discussion in Bug#897572, I confirm that with kernel 4.16, the Plymouth password prompt brings up in mere instants when randomly moving the mouse.
Bug#897958: plymouth: long delay before splashscreen with kernel 4.16
Package: plymouth Followup-For: Bug #897958 Dear Maintainer, I found the same issue on my system, also just after upgrading to kernel 4.16, once available in testing. I also use full-disk encryption, so I need to input the volume password using Plymouth interface each time the computer boots (don't know whether this is related). Now, after loading the 4.16 kernel, an empty Plymouth splash screen (properly themed) is displayed for approx. 1 minute, during which the ESC key has no effect. After that delay, the input field for entering encryption passphrase is shown and everything boots up and works properly after. (If ESC was pressed during the wait, the text interface also shows up properly after the delay, asking passphrase). Booting kernel 4.16 with 'nosplash' does not reproduce this problem. Booting kernel 4.15 with 'splash' does not reproduce this problem. Thank you in advance and regards, Arnaud Meyer. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-1-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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plymouth depends on: ii init-system-helpers 1.51 ii initramfs-tools 0.130 ii libc62.27-3 ii libdrm2 2.4.91-2 ii libplymouth4 0.9.3-2 ii lsb-base 9.20170808 ii systemd 238-4 ii udev 238-4 plymouth recommends no packages. Versions of packages plymouth suggests: ii desktop-base 9.0.5 ii plymouth-themes 0.9.3-2 -- Configuration Files: /etc/plymouth/plymouthd.conf changed: [Daemon] Theme=solar -- no debconf information
Bug#878022: plymouth-themes: Solar theme animation is broken
Package: plymouth-themes Followup-For: Bug #878022 Dear Laurent, After upgrading plymouth* packages AND libplymouth4 (thank you, bug reporting system), the solar theme animation seems to be working fine again. Because I didn't upgrade all packages at once (I upgraded libplymouth4 at last), I first had the right animation during shutdown only. To correct this, I manually updated initramfs : sudo plymouth-set-default-theme -R solar After that, the animation was displayed properly during both shutdown and startup. Thank you for your work and best regards, Arnaud Meyer. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-2-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 /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plymouth-themes depends on: ii fontconfig-config 2.12.6-0.1 ii fonts-dejavu-core 2.37-1 ii libc6 2.26-4 ii libplymouth4 0.9.3-2 ii plymouth 0.9.3-2 ii plymouth-label 0.9.3-2 ii ttf-dejavu-core2.37-1 plymouth-themes recommends no packages. plymouth-themes suggests no packages. -- no debconf information
Bug#878022: plymouth-themes: Solar theme animation is broken
Package: plymouth-themes Version: 0.9.3-1 Severity: normal Dear Maintainer, Since the update of all plymouth packages from 0.9.2-5 to 0.9.3-1, the animation of the "solar" theme is not working properly anymore. When booting and stopping, the animation plays in a kind of "glitched" way, constantly blinking between the proper animation and a still frame. It does not seem to affect other themes so far, for instance the "lines" theme is working properly with the same setup. Thank you in advance and regards, Arnaud Meyer. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-2-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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plymouth-themes depends on: ii fontconfig-config 2.12.3-0.2 ii fonts-dejavu-core 2.37-1 ii libc6 2.24-17 ii libplymouth4 0.9.3-1 ii plymouth 0.9.3-1 ii plymouth-label 0.9.3-1 ii ttf-dejavu-core2.37-1 plymouth-themes recommends no packages. plymouth-themes suggests no packages. -- no debconf information
Bug#873342: libretro-beetle-psx: Update to latest version
Package: libretro-beetle-psx Version: 0.9.38.6+git20151019-2 Severity: wishlist Dear Maintainer, The package libretro-beetle-psx has not been updated for a while, whereas it looks to be still quite active upstream. The current version in Debian repositories looks to be dated 2015 and misses some new and interesting features like internal GPU resolution upscaling. I understand that there seems to be no versioning upstream, which makes it difficult to track signficant changes, but I believe an update once in a while could greatly contribute to PSX emulation in Debian. As a workaround, building from up-to-date git worked really well ans easily, as there is only one file to build and replace. Thank you in advance, Arnaud Meyer. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (500, 'oldoldstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libretro-beetle-psx depends on: ii libc6 2.24-14 ii libgcc1 1:7.2.0-1 ii libstdc++6 7.2.0-1 ii libtrio21.16+dfsg1-3+b2 ii retroarch 1.3.6+dfsg1-1 libretro-beetle-psx recommends no packages. libretro-beetle-psx suggests no packages. -- no debconf information
Bug#856980: librecad: Files ending with uppercase extension do not appear in file selection dialogs
Package: librecad Version: 2.1.2-1 Severity: minor Dear Maintainer, LibreCAD file selection dialogs are not listing files which end up with an uppercase extension (for instance, ".DXF" instead of ".dxf"). Renaming the file to lowercase extension makes it appear immediately in the selection dialog. As far as I can see, it applies to all file selection dialogs : - Open - Save - Import - ... I would expect such files with an uppercase extension to be listed as well as the lowercase ones within selection dialogs. Regards, Arnaud Meyer. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages librecad depends on: ii libc6 2.24-9 ii libgcc1 1:6.3.0-6 ii libgl1-mesa-glx [libgl1] 13.0.5-1 ii libmuparser2v52.2.3-6 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5printsupport5 5.7.1+dfsg-3+b1 ii libqt5svg55.7.1~20161021-2 ii libqt5widgets55.7.1+dfsg-3+b1 ii librecad-data 2.1.2-1 ii libstdc++66.3.0-6 librecad recommends no packages. librecad suggests no packages. -- no debconf information
Bug#845943: zotero-standalone: Unable to run, 'Error opening input stream'
Package: zotero-standalone
Version: 4.0.29.5+dfsg-2
Severity: important
Dear Maintainer,
Upon starting Zotero, it crashes immediately, displaying a message box
"There was an error starting Zotero.". The program exits immediately
after confirming the message, without displaying anything else.
When running from a terminal, I get the following output :
xulrunner not found, trying firefox instead.
Error opening input stream (invalid filename?):
chrome://global/content/nsTransferable.js
Error opening input stream (invalid filename?):
chrome://global/content/nsTransferable.js
Error opening input stream (invalid filename?):
chrome://global/content/nsTransferable.js
(The last message is displayed only after confirming the message box).
Running Zotero with options "--help" or "--version" only displays the
first line ("xulrunner not found...") and behave normally. Any other
option produces the same as above.
The expected behaviour would be the software running, or giving details
about an hypothetical missing package.
Using Zotero plugin for Firefox (4.0.29.16) with the same database, it
displays and behaves normally.
Regards,
Arnaud Meyer.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages zotero-standalone depends on:
ii firefox 50.0-3
zotero-standalone recommends no packages.
zotero-standalone suggests no packages.
-- no debconf information
