Bug#1070672: azure-cli: should not request surveys from the user

[brian m. carlson]

tags 1070672 + patch
kthxbye

On 2024-05-06 at 21:59:34, brian m. carlson wrote:
> azure-cli prompts the user for surveys in at least some circumstances
> when running `az login`.  This is done using a bright blue, three-line
> banner that is large and distracting, and totally unnecessary.
> 
> The Unix philosophy is that software should be silent unless it has
> something relevant to say to the user.  Survey requests benefit
> Microsoft, but are not actually relevant to the user, and if the user
> wanted to provide feedback, it would be just as easy to find the
> appropriate website to do so.  In addition, terminal users do not expect
> software in Debian to print lots of noisy messages to the terminal, and
> in general, when software does so, it's considered a bug.
> 
> Please disable the survey requests in Debian to keep azure-cli quiet.

I've included a Git format patch as an attachment.  This is not against
the Debian repository since salsa.debian.org was down at the time I was
looking at this, but it's against a `git init` of the latest package.

It should be pretty straightforward and easy to read.
-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
From 0000 Mon Sep 17 00:00:00 2001
From: "brian m. carlson" 
Date: Tue, 7 May 2024 00:58:28 +
Subject: [PATCH] Don't prompt user for surveys

The survey message that is used is three lines and has a bright blue
background and is very distracting compared to other text on the screen.
In addition, the Unix philosophy states that software should avoid
unnecessary output, and upstream's desire for users to complete a survey
is not functionally necessary or useful for end users.  Remove this
prompt since it is noisy and annoying to terminal users.

Users wanting to access the survey can still run `az survey` if they
want.
---
 src/azure-cli/azure/cli/__main__.py | 6 --
 1 file changed, 6 deletions(-)

diff --git a/src/azure-cli/azure/cli/__main__.py b/src/azure-cli/azure/cli/__main__.py
index 513e914..1b983d1 100644
--- a/src/azure-cli/azure/cli/__main__.py
+++ b/src/azure-cli/azure/cli/__main__.py
@@ -13,7 +13,6 @@ import uuid
 
 from azure.cli.core import telemetry
 from azure.cli.core import get_default_cli
-from azure.cli.core.intercept_survey import prompt_survey_message
 from knack.completion import ARGCOMPLETE_ENV_NAME
 from knack.log import get_logger
 
@@ -119,11 +118,6 @@ finally:
 logger.warning("Auto upgrade failed. %s", str(ex))
 telemetry.set_exception(ex, fault_type='auto-upgrade-failed')
 
-try:
-prompt_survey_message(az_cli)
-except Exception as ex:  # pylint: disable=broad-except
-logger.debug("Intercept survey prompt failed. %s", str(ex))
-
 telemetry.set_init_time_elapsed("{:.6f}".format(init_finish_time - start_time))
 telemetry.set_invoke_time_elapsed("{:.6f}".format(invoke_finish_time - init_finish_time))
 telemetry.conclude()


signature.asc
Description: PGP signature

Bug#1070673: azure-cli: contains telemetry

[brian m. carlson]

Source: azure-cli
Version: 2.50.0-2
Severity: normal

The documentation in this package indicates that telemetry collection is
on by default, and I don't see any patches that indicate that that has
been removed.

Debian should not ship software that sends telemetry by default because
it violates the privacy of users, and it is typically only in the
interest of the maintainer, not the users.  It's not reasonable to
expect users to configure every package they might install separately
not to send telemetry, since that's impractical and it's nearly
impossible to configure every piece of software to do so, especially in
environments like containers where users' settings are often not
persisted.

Please remove the telemetry functionality from the package or ensure
that it is rendered completely nonfunctional, and add a note to the
README.Debian indicating this change so that users can feel more
confident in using the package.


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

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

-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1070672: azure-cli: should not request surveys from the user

[brian m. carlson]

Package: azure-cli
Version: 2.50.0-2
Severity: normal

azure-cli prompts the user for surveys in at least some circumstances
when running `az login`.  This is done using a bright blue, three-line
banner that is large and distracting, and totally unnecessary.

The Unix philosophy is that software should be silent unless it has
something relevant to say to the user.  Survey requests benefit
Microsoft, but are not actually relevant to the user, and if the user
wanted to provide feedback, it would be just as easy to find the
appropriate website to do so.  In addition, terminal users do not expect
software in Debian to print lots of noisy messages to the terminal, and
in general, when software does so, it's considered a bug.

Please disable the survey requests in Debian to keep azure-cli quiet.


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

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

Versions of packages azure-cli depends on:
ii  python33.11.8-1
ii  python3-azure-cli  2.50.0-2

azure-cli recommends no packages.

azure-cli suggests no packages.

-- no debconf information

-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1070031: heimdal-kdc: fails to install if /usr/bin/kadmin is not Heimdal kadmin

[Brian May]

Ryan Tandy  writes:

> # update-alternatives --display kadmin
> kadmin - auto mode
>   link best version is /usr/bin/kadmin.mit
>   link currently points to /usr/bin/kadmin.mit
>   link kadmin is /usr/bin/kadmin
>   slave kadmin.1.gz is /usr/share/man/man1/kadmin.1.gz
> /usr/bin/kadmin.heimdal - priority 23
>   slave kadmin.1.gz: /usr/share/man/man1/kadmin.heimdal.1.gz
> /usr/bin/kadmin.mit - priority 30
>   slave kadmin.1.gz: /usr/share/man/man1/kadmin.mit.1.gz

I am wondering if maybe kadmin should not be using update-alternatives.

I think it is policy - although I can't find it right now - that update
alternatives should only be used for similar commands, i.e. similiar
command line parsing, does the same thing, etc.

But I don't think any of this applies for kadmin. It could be very
confusing if you are kadmin by hand, not realizing you are running the
wrong command.

Any thoughts?

Maybe I should ask the MIT kerberos maintainer for opinions here also.
-- 
Brian May @ Debian

Bug#1068118: bullseye-pu: package amavisd-new/2.11.1-5+deb11u1

[Brian May]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: amavisd-...@packages.debian.org, b...@debian.org
Control: affects -1 + src:amavisd-new

[ Reason ]

* Fix CVE-2024-28054.

[ Impact ]

Without this path:

* CVE-2024-28054 won't be fixed, and amavisd-new could potentially let through
mallacious emails.

[ Tests ]

No tests.

[ Risks ]

Patch could break with risk that geniune emails get blocked.

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]

As below.

[ Other info ]

Patch could break with risk that geniune emails get blocked.

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]

As below.

[ Other info ]

I hope I am doing this right :-)

I accidentally uploaded 2.11.1-6, I tried to delete it, but if that didn't 
work, please just delete.

=== deb diff ===
diff -Nru amavisd-new-2.11.1/debian/changelog 
amavisd-new-2.11.1/debian/changelog
--- amavisd-new-2.11.1/debian/changelog 2021-06-07 22:51:44.0 +
+++ amavisd-new-2.11.1/debian/changelog 2024-03-31 07:16:32.0 +
@@ -1,3 +1,10 @@
+amavisd-new (1:2.11.1-5+deb11u1) oldstable; urgency=medium
+
+  * CVE-2024-28054: Handle multiple boundary parameters that contain
+conflicting values.
+
+ -- Brian May   Sun, 31 Mar 2024 18:16:32 +1100
+
 amavisd-new (1:2.11.1-5) unstable; urgency=medium

   * Add missing dependency on libnet-snmp-perl. Closes: #936052.
diff -Nru amavisd-new-2.11.1/debian/gbp.conf amavisd-new-2.11.1/debian/gbp.conf
--- amavisd-new-2.11.1/debian/gbp.conf  1970-01-01 00:00:00.0 +
+++ amavisd-new-2.11.1/debian/gbp.conf  2024-03-31 07:16:32.0 +
@@ -0,0 +1,2 @@
+[DEFAULT]
+debian-branch=debian/bullseye
diff -Nru amavisd-new-2.11.1/debian/patches/0011-fix-CVE-2024-28054 
amavisd-new-2.11.1/debian/patches/0011-fix-CVE-2024-28054
--- amavisd-new-2.11.1/debian/patches/0011-fix-CVE-2024-28054   1970-01-01 
00:00:00.0 +
+++ amavisd-new-2.11.1/debian/patches/0011-fix-CVE-2024-28054   2024-03-31 
07:15:01.0 +
@@ -0,0 +1,175 @@
+--- /dev/null
 b/README_FILES/README.CVE-2024-28054
+@@ -0,0 +1,54 @@
++# Problem description
++
++Emails which consist of multiple parts (`Content-Type: multipart/*`)
++incorporate boundary information stating at which point one part ends and the
++next part begins.
++
++A boundary is announced by an Content-Type header's `boundary` parameter. To
++our current knowledge, RFC2046 and RFC2045 do not explicitly specify how a
++parser should handle multiple boundary parameters that contain conflicting
++values. As a result, there is no canonical choice which of the values should 
or
++should not be used for mime part decomposition.
++
++It turns out that MIME::Parser from MIME-tools chooses the last `boundary`
++parameter of a Content-Type-header, while several mail user agents choose the
++first occuring one. As a consequence, Amavis will apply some of its routines 
to
++content that a receiving MUA will not see, and vice-versa will not apply them
++to content that the receiving MUA will see. Such routines are at least
++- the banned-files check, and
++- the virus check, unless
++  - Amavis feeds the whole email into the virus scanner, and
++  - the virus scanner implements its own email parsing that aligns with the
++receiving MUA's parser implementation.
++
++MIME::Parser does not provide a choice which of multiple `boundary` parameters
++shall be used for parsing, but it will give feedback in such a case [1], which
++Amavis can react to.
++Emails with ambiguous content, like multiple `boundary` parameters as 
described
++above, will be categorized as `CC_UNCHECKED,3`, since Amavis has no 
information
++about the recipient's MUA's parser implementation.
++
++# Recommendation
++
++Legitimate emails are not expected to have ambiguous content, so an Amavis 
setup
++should treat them harshly. The new default configuration for `CC_UNCHECKED,3` 
is
++defanging:
++
++```
++$defang_by_ccat{CC_UNCHECKED.",3"} = 1; # ambiguous content (e.g. multipart 
boundary)
++```
++
++Another possibility would be quarantining, e.g. via
++
++```
++$quarantine_to_maps_by_ccat{CC_UNCHECKED.",3"} = [1];
++$quarantine_method_by_ccat{CC_UNCHECKED.",3"} = 
'local:unchecked-ambiguous-%m';
++```
++
++and/or discarding/rejecting the email:
++
++```
++$final_destiny_maps_by_ccat{CC_UNCHECKED.",3"} = D_REJECT; # or D_DISCARD
++```
++
++[1] https://metacpan.org/release/DSKOLL/MIME-tools-5.514/changes
+--- a/amavisd
 b/amavisd
+@@ -1374,6 +1374,7 @@
+ CC_UNCHECKED,  'Unchecked',
+   

Bug#1067206: bookworm-pu: package amavisd-new/1:2.13.0-3+deb12u1

[Brian May]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: amavisd-...@packages.debian.org, b...@debian.org
Control: affects -1 + src:amavisd-new

[ Reason ]

* Fix race condition on initial install. Closes: #1064349.
* Fix CVE-2024-28054.

[ Impact ]

Without this path:

* Possible errors on initial installation.
* CVE-2024-28054 won't be fixed, and amavisd-new could potentially let through 
mallacious emails.

[ Tests ]

No tests.

[ Risks ]

Patch could break with risk that geniune emails get blocked.

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]

As below.

[ Other info ]

I hope I am doing this right :-)


=== debdiff ===

root@08c7f517533c:/tmp/brian/tmp5u_5mq1q/build# debdiff 
old/amavisd-new_2.13.0-3.dsc  amd64/amavisd-new_2.13.0-3+deb12u1.dsc
diff -Nru amavisd-new-2.13.0/debian/amavisd-new.postinst 
amavisd-new-2.13.0/debian/amavisd-new.postinst
--- amavisd-new-2.13.0/debian/amavisd-new.postinst  2023-02-23 
04:59:36.0 +
+++ amavisd-new-2.13.0/debian/amavisd-new.postinst  2024-02-29 
22:56:51.0 +
@@ -95,6 +95,8 @@
fi
done
fi
+
+   deb-systemd-invoke start amavis amavis-mc amavisd-snmp-subagent
 ;;

 abort-upgrade|abort-remove|abort-deconfigure)
diff -Nru amavisd-new-2.13.0/debian/changelog 
amavisd-new-2.13.0/debian/changelog
--- amavisd-new-2.13.0/debian/changelog 2023-05-11 22:52:23.0 +
+++ amavisd-new-2.13.0/debian/changelog 2024-02-29 22:56:51.0 +
@@ -1,3 +1,11 @@
+amavisd-new (1:2.13.0-3+deb12u1) stable; urgency=medium
+
+  * Fix race condition in postinst. Closes: #1064349.
+  * CVE-2024-28054: Handle multiple boundary parameters that contain
+conflicting values.
+
+ -- Brian May   Fri, 01 Mar 2024 09:56:51 +1100
+
 amavisd-new (1:2.13.0-3) unstable; urgency=medium

   * Fix failure to purge without adduser. Closes: #1035841.
diff -Nru amavisd-new-2.13.0/debian/gbp.conf amavisd-new-2.13.0/debian/gbp.conf
--- amavisd-new-2.13.0/debian/gbp.conf  1970-01-01 00:00:00.0 +
+++ amavisd-new-2.13.0/debian/gbp.conf  2024-02-29 22:56:51.0 +
@@ -0,0 +1,2 @@
+[DEFAULT]
+debian-branch=debian/bookworm
diff -Nru 
amavisd-new-2.13.0/debian/patches/0010-Apply-fix-for-CVE-2024-28054.patch 
amavisd-new-2.13.0/debian/patches/0010-Apply-fix-for-CVE-2024-28054.patch
--- amavisd-new-2.13.0/debian/patches/0010-Apply-fix-for-CVE-2024-28054.patch   
1970-01-01 00:00:00.0 +
+++ amavisd-new-2.13.0/debian/patches/0010-Apply-fix-for-CVE-2024-28054.patch   
2024-02-29 22:56:51.0 +
@@ -0,0 +1,213 @@
+From: Brian May 
+Date: Tue, 12 Mar 2024 09:34:58 +1100
+Subject: Apply fix for CVE-2024-28054
+
+---
+ README_FILES/README.CVE-2024-28054 | 54 ++
+ conf/amavisd.conf  |  1 +
+ lib/Amavis.pm  |  8 +++---
+ lib/Amavis/Conf.pm |  2 ++
+ lib/Amavis/Unpackers.pm|  5 ++--
+ lib/Amavis/Unpackers/MIME.pm   | 19 ++
+ lib/Amavis/Unpackers/Part.pm   |  3 ++-
+ 7 files changed, 86 insertions(+), 6 deletions(-)
+ create mode 100644 README_FILES/README.CVE-2024-28054
+
+diff --git a/README_FILES/README.CVE-2024-28054 
b/README_FILES/README.CVE-2024-28054
+new file mode 100644
+index 000..757c5c1
+--- /dev/null
 b/README_FILES/README.CVE-2024-28054
+@@ -0,0 +1,54 @@
++# Problem description
++
++Emails which consist of multiple parts (`Content-Type: multipart/*`)
++incorporate boundary information stating at which point one part ends and the
++next part begins.
++
++A boundary is announced by an Content-Type header's `boundary` parameter. To
++our current knowledge, RFC2046 and RFC2045 do not explicitly specify how a
++parser should handle multiple boundary parameters that contain conflicting
++values. As a result, there is no canonical choice which of the values should 
or
++should not be used for mime part decomposition.
++
++It turns out that MIME::Parser from MIME-tools chooses the last `boundary`
++parameter of a Content-Type-header, while several mail user agents choose the
++first occuring one. As a consequence, Amavis will apply some of its routines 
to
++content that a receiving MUA will not see, and vice-versa will not apply them
++to content that the receiving MUA will see. Such routines are at least
++- the banned-files check, and
++- the virus check, unless
++  - Amavis feeds the whole email into the virus scanner, and
++  - the virus scanner implements its own email parsing that aligns with the
++receiving MUA's parser implementation.
++
++MIME::Parser does not provide a choice which of multiple `boundary` parameters
++shall be used for parsing, but it will give feedback

Bug#1064349: amavisd-new: fails to install with sysvinit-core

[Brian May]

Michal Mauser  writes:

> we are trying to install new KVM virtual machines with Debian 12 and 
> here is what happens after reboot with sysvinit and apt install:
>
> Creating group 'amavis' with GID 996.
> Creating user 'amavis' (AMaViS system user) with UID 996 and GID 996.
> Starting amavisd: You are missing a dpkg-statoverride on 
> /var/run/amavis.  Fix it, otherwise you risk silent breakage on
>   upgrades.
> invoke-rc.d: initscript amavis, action "start" failed.
>
> The installation works on systemd. /var/run/amavis doesn't exist. I 
> haven't checked it on Debian 11 but we use amavis on Debian 10
> sysvinit.

If all goes to plan, I am about to upload version 1:2.13.0-4 which I
think should fix this problem.

It seems to work OK for me, but would appreciate it if you can test it
and confirm it works for you.

If it fails, please reopen the bug report.
-- 
Brian May @ Debian

Bug#1064097: heimdal: NMU diff for 64-bit time_t transition

[Brian May]

Steve Langasek  writes:

> Please find the patch for this NMU attached.

I added these patches to the github repo at
https://salsa.debian.org/debian/heimdal/ in the debian/experimental
branch.

Wondering if it still makes sense to have the -heimdal prefix in the
library package names. Sort of have conflicting opinions here. But if we
wanted to get rid of them, now would probably be a really good time.
-- 
Brian May @ Debian

Bug#1064349: amavisd-new: fails to install with sysvinit-core

[Brian May]

Michal Mauser  writes:

> we are trying to install new KVM virtual machines with Debian 12 and 
> here is what happens after reboot with sysvinit and apt install:
>
> Creating group 'amavis' with GID 996.
> Creating user 'amavis' (AMaViS system user) with UID 996 and GID 996.
> Starting amavisd: You are missing a dpkg-statoverride on 
> /var/run/amavis.  Fix it, otherwise you risk silent breakage on
>   upgrades.
> invoke-rc.d: initscript amavis, action "start" failed.
>
> The installation works on systemd. /var/run/amavis doesn't exist. I 
> haven't checked it on Debian 11 but we use amavis on Debian 10
> sysvinit.

The postinst script should be installing the dpkg-statoverride, but no
idea why this isn't working

Hmmm. Wonder if the problem is that the postinst script is trying to
start the daemon first before it sets the dpkg-statoverride stuff.

But if that is the case, I would have thought it would fail with systemd
also.

Just my random thoughts, I don't have time to look at this right now.
-- 
Brian May @ Debian

Bug#1062724: node-cbor: cbor2comment throws exception on decoding null

[brian m. carlson]

Package: node-cbor
Version: 8.1.0+dfsg+~cs5.2.1-3
Severity: normal
File: /usr/bin/cbor2comment

cbor2comment can throw an exception when a null is deserialized:

$ cat >data <<-EOF
AKViaWQAaHNlbGVjdG9yoWRwYXRoTi9tZW1vcnkvdmF1bHQvZ3JlY3Vyc2WhZ2Jvb2xlYW71ZGtp
bmRqY3JlZGVudGlhbGRib2R5rGh1c2VybmFtZaFnbGl0ZXJhbENmb29mc2VjcmV0oWNhbnn2aGF1
dGh0eXBloWNhbnn2ZGtpbmShZ2xpdGVyYWxjYXBpaHByb3RvY29soWdsaXRlcmFsZWh0dHBzZGhv
c3ShZ2xpdGVyYWxvZ2l0LmV4YW1wbGUuY29tZXRpdGxloWdsaXRlcmFseB1HaXQ6IGh0dHBzOi8v
Z2l0LmV4YW1wbGUuY29tL2tkZXNjcmlwdGlvbqFjYW559mRwYXRooWNhbnn2Z3NlcnZpY2WhZ2xp
dGVyYWxjZ2l0ZWV4dHJhoGJpZKFnbGl0ZXJhbFiAODhkMmQ3Njc4YzEyNzdmODFiMzhmZWJkOWQ5
M2Y0ZDc0ZGY4OGYyNzIwOTYwMzA4YTFjY2VjZmI1N2QzNjVmNTNiMTAyMjc2YmQ1YjQ0MjcwMjkz
ZDQzNDU4M2RkMmVmNmMxZGViODdmYzI5NTA4YTc2YjI3YjA3OTgyNmI3MDYK
EOF
$ base64 -d data | cbor2comment
[Some data...]
f6  -- {Val:0}, TypeError: Cannot read properties of null 
(reading 'Symbol(nodejs.util.inspect.custom)')
at Object.cborValueToString (/usr/share/nodejs/cbor/lib/utils.js:246:21)
at Commented._on_value (/usr/share/nodejs/cbor/lib/commented.js:336:23)
at Decoder.emit (node:events:517:28)
at Decoder._parse (/usr/share/nodejs/cbor/lib/decoder.js:555:12)
at _parse.next ()
at Decoder._transform 
(/usr/share/nodejs/cbor/vendor/binary-parse-stream/index.js:53:29)
at Transform._write (node:internal/streams/transform:175:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Writable.write (node:internal/streams/writable:337:10)

I expected cbor2comment to print the data, including the null, without
throwing an exception or truncating the dump.

I should note that cbor2json works, but because my data structure uses
byte strings heavily, the dump is effectively unreadable.  I have not
found other non-null data that triggers an error.

In case it is useful to know, the data structure was serialized using
the Rust library serde_cbor.  It's test data and is not sensitive, so
feel free to share it, add it to the testsuite, etc.

I believe this may be fixed with PR #188 upstream (in v9.0.2), but I'm
unsure.  In any event, I expect it's easy to verify one way or the other
with the steps above.

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

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

Versions of packages node-cbor depends on:
ii  node-bignumber  9.1.1-1
ii  node-commander  9.4.1-1
ii  nodejs  18.19.0+dfsg-6

node-cbor recommends no packages.

node-cbor suggests no packages.

-- no debconf information

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1060795: Bug #1060795

[Brian Tarricone]

Can confirm that the patch in the comment at 
https://github.com/bluez/bluez/issues/686#issuecomment-1858902231 fixes the 
issue for me.

Bug#1060795: bluez: Troubles with bluetooth after upgrade from bookworm to testing (trixie): br-connection-unknown

[Brian Tarricone]

I'm running into this too, poked around a little bit, and found an issue filed 
on BlueZ's github repo that seems like it might be related: 
https://github.com/bluez/bluez/issues/686

Unclear what the proper fix is; there's some complaint on there that what they 
merged requires a new, unreleased kernel.  But there's also a patch posted in a 
comment that some people claim fixes it (I have not yet tested): 
https://github.com/bluez/bluez/issues/686#issuecomment-1858902231

Bug#1061182: libsdl2: native gamecube controllers are unsupported because `--enable-hidapi-libusb` is not set

[Brian Smith]

Package: libsdl2
Version: 2.28.5+dfsg-3
Severity: wishlist
Tags: newcomer
X-Debbugs-Cc: 315kol...@mozmail.com

Dear Maintainer,

As of https://github.com/libsdl-
org/SDL/commit/c528615626d9f7789a5681a946cb3d5bd5d68c2c, SDL2 supports gamecube
controllers using the Switch/Wii U USB GameCube controller adapter. To use
this, however, one must build SDL using `--enable-hidapi-libusb`.

I was able to get this working on my machine by using apt source, editing the
`confflags` in `rules` to include `--enable-hidapi-libusb`, installing `libusb-
dev` and `libusb-1.0-0-dev`, and building with `dpkg-buildpackage`.

I'd love to hear any thoughts about adding `--enable-hidapi-libusb`.

Thank you so much for your time!

- Brian


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

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

Versions of packages libsdl2-2.0-0 depends on:
ii  libasound2  1.2.10-3
ii  libc6   2.37-13
ii  libdecor-0-00.2.2-1
ii  libdrm2 2.4.120-1
ii  libgbm1 23.3.3-3
ii  libpulse0   16.1+dfsg1-3
ii  libsamplerate0  0.2.2-4
ii  libwayland-client0  1.22.0-2.1
ii  libwayland-cursor0  1.22.0-2.1
ii  libwayland-egl1 1.22.0-2.1
ii  libx11-62:1.8.7-1
ii  libxcursor1 1:1.2.1-1
ii  libxext62:1.3.4-1+b1
ii  libxfixes3  1:6.0.0-2
ii  libxi6  2:1.8-1+b1
ii  libxkbcommon0   1.6.0-1
ii  libxrandr2  2:1.5.2-2+b1
ii  libxss1 1:1.2.3-1

libsdl2-2.0-0 recommends no packages.

Versions of packages libsdl2-2.0-0 suggests:
ii  xdg-utils  1.1.3-4.1

-- no debconf information

Bug#886247: Upstream patch

[Brian Murray]

Upstream list admin fixed this with the following commit:

https://sourceforge.net/p/listadmin/code/ci/ad51019ef5b493aa3ce6720cae88153c1b39776d

--
Brian Murray @ubuntu.com

Bug#1059497: update

[Brian Sturgill]

Tried a 32 bit base install of debian on the raspberry Pi 4. I have the
same results. i have a Fedora install on a laptop with CubicSDR 0.2.7 amd
it works correctly. Both my RaspberryPi and my Debian Workstation have the
modem waterfall issue after installing Bookworm. Same results using a
SDRPlay RSP2 and a HackRF clone.

Thanks,
Brian

Bug#1059457:

[Brian Sammon]

> 
> If qemu-system-gui package is already installed you can just look at the l
> in it, - the list gives a good hint.  It should, - I hope anyway - be 
> enough to read the
> description already.  At the very least, almost no one looks at READMEs 
> inside packages,
> but some do look at the descriptions, especially before installing something. 
>  Maybe
> the description should be improved a bit.

Okay... it sounds like we're approaching agreement here.  I _did_ read the 
package description of qemu-system-gui (before creating this bug) and I'm still 
not clear what the package is for, or whether I should install it.

I have a suspicion that this is an important (for qemu) package, but I'm 
unclear about how/why.

I created this bug to say in essence that I think the documentation of this 
package needs to be improved.  I don't have my heart set on README.Debian as 
the means of doing it.  I would be happy with an improved package description.

I would be willing to submit a patch, if/when I understand the package enough 
that I could compose such documentation.

> Let's use another example. qemu-system-arm recommends (or suggests, don't 
> but let's assume it is Recommends) samba.  The reason is that qemu can us
> mode to share a directory on the host to the guest system it is running.  
> samba should carry a README explaining how it is used with qemu-system-arm

To follow this example-- I think samba should contain documentation explaining 
its primary purpose.  I suspect it does.  If there was a package called 
something like qemu-system-samba, I would expect that its primary purpose would 
be something directly related to qemu, and I would hope its documentation would 
explain how to use it with qemu.

> Your question comes from the lack of understanding what qemu itself is 
> and how to use it.

That's for sure!  I've never used qemu before.  I've used virtualbox and VMWare 
in the past.

> (and this is obvious from the list of files in the package).

I've had a lot of people on the internet lately tell me that something I'm 
confused about is "obvious".  Usually it means "if you've used this thing for 
as many years as I have, it's obvious".

> https://www.qemu.org/docs/master/system/invocation.html#hxtool-3 is the 
> part relevant to
> this context - qemu-system-gui provides sdl and gtk *modules* for qemu-
> system-* packages

Ah, yes!  This URL (and the fact that you suggested it) are very informative.

Would it be correct to say:
  This package enables the "gtk" and "sdl" display types used with the
  "-display" argument of qemu
?

If that is accurate, I think a sentence like that would be exactly the kind of 
addition to the qemu-system-gui documentation that I'm looking for (whether 
it's the package description, or README.Debian, or some other place)

Bug#1059457:

[Brian Sammon]

I fear that my bug report has sounded like a criticism or an argument.  I 
apologize for that.

Let me try to further describe my dilemma.

I want to use qemu.  I read the description of qemu-system-arm, and I believe 
that is a package that I want to use.
The packager of qemu-system-arm appears to believe that I should use 
qemu-system-gui, since qemu-system-arm "recommends" qemu-system-gui.
I've looked into qemu-system-gui, and I can't figure out what it does.  Is it a 
VM-launcher app?  Something else?

Now I agree that I shouldn't be using a package that I don't understand.
So how do I learn what qemu-system-gui is, so I can decide whether to follow 
the recommendation of qemu-system-arm and use it?

If I can't understand what qemu-system-gui is, does that mean that I'm better 
off using qemu without qemu-system-gui?

Bug#1059457: closed by Michael Tokarev (Re: Bug#1059457: qemu-system-gui: README.Debian or manpage needed)

[Brian Sammon]

The problem is:  The package is recommended by qemu-system-*, but I can't 
figure out why, or what it adds.

So I'm faced with either "install a package which I don't know how to use", or 
ignore the recommend.

And... if I don't know how to use it, how do I figure out how to use it if 
there's no documentation?

Bug#1059497: cubicsdr: No waterfall in modem window

[Brian]

Package: cubicsdr
Version: 0.2.7+dfsg-2+b3
Severity: important
X-Debbugs-Cc: brian.sturgil...@gmail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? Base install on pc and raspberry pi
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Any time modem bandwidth is lowed to below normal FM stereo
bandwitch such as AM mode, the modem waterfall disappears
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages cubicsdr depends on:
ii  libc6  2.36-9+deb12u3
ii  libgcc-s1  12.2.0-14
ii  libglx01.6.0-1
ii  libhamlib4 4.5.4-1+b1
ii  libliquid1 1.5.0-2
ii  libopengl0 1.6.0-1
ii  librtaudio65.2.0~ds1-2
ii  libsoapysdr0.8 0.8.1-3
ii  libstdc++6 12.2.0-14
ii  libtinyxml2.6.2v5  2.6.2-6
ii  libwxbase3.2-1 3.2.2+dfsg-2
ii  libwxgtk-gl3.2-1   3.2.2+dfsg-2
ii  libwxgtk3.2-1  3.2.2+dfsg-2

Versions of packages cubicsdr recommends:
ii  soapysdr-module-all  0.8.1-3

cubicsdr suggests no packages.

-- no debconf information

Bug#1059457: qemu-system-gui: README.Debian or manpage needed

[Brian Sammon]

Package: qemu-system-gui
Severity: normal

Dear Maintainer,

This package could really use a README.Debian or something to explain how to 
use it. 
Perhaps it's because I'm not using a standard desktop environment like Gnome or 
KDE, but I can't figure out what this package does.  It doesn't seem to install 
a program in /usr/bin/ , for example.

-- 
Brian Sammon 

Bug#1055316: heimdal: fails to build against glibc 2.38

[Brian May]

Samuel Thibault  writes:

>> Whaat is the process for a breaks transition?
>
> Some details examples are discussed in Bug#1043184 in the case of krb5.

Thinking if I just drop the symbols, this is going to break
libafsauthent2 while we still have glibc 2.37 in unstable. Does this
sound correct?

Although maybe this does not matter, I see that there is already a
serious bug against openafs anyway since
August... https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043131
-- 
Brian May @ Debian

Bug#1055316: heimdal: fails to build against glibc 2.38

[Brian May]

Samuel Thibault  writes:

> I checked all *_amd64.so packages, apparently libafsauthent2 is using
> rk_strlcpy and rk_strlcat from libroken, so a Breaks transition is
> needed for that.

Whaat is the process for a breaks transition?
-- 
Brian May @ Debian

Bug#1056329: Cannot create simple TCPMUXPLUS service - produces seg fault

[Brian Blood]

Disregard,

I did not see in the xinetd.conf manpage that you have to also add the base 
tcpmux service file.

Bug#1056329: xinetd: Cannot create simple TCPMUXPLUS service - produces seg fault

[Brian Blood]

Package: xinetd
Version: 1:2.3.15.3-1+b1
Severity: important

Dear Maintainer,

I'm trying to create a simple TCPMUXPLUS service that takes a TCP connection 
and returns a predetermined amount a entropy.

Here is my xinet.d conf file:

# default: off
# description: An xinetd service which provides entropy.
# the shell script called will return 128 bytes of entropy to the caller.
service entropy
{
id  = entropy
type= TCPMUXPLUS UNLISTED
socket_type = stream
protocol= tcp
disable = no
#flags   = KEEPALIVE IPv4
instances   = 40
server  = /srv/xinetd-entropy.sh
log_type= FILE /var/log/entropy-xinetd.log
log_on_success  = PID HOST USERID EXIT DURATION
log_on_failure  = HOST USERID ATTEMPT
user= nobody
wait= no
}

In this form, restarting xinetd produces this syslog output:

systemd[1]: Started xinetd.service - LSB: Starts or stops the xinetd daemon..
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/chargen 
[file=/etc/xinetd.conf] [line=14]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/chargen-udp 
[file=/etc/xinetd.d/chargen-udp] [line=28]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/daytime 
[file=/etc/xinetd.d/daytime] [line=14]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/daytime-udp 
[file=/etc/xinetd.d/daytime-udp] [line=26]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/discard 
[file=/etc/xinetd.d/discard] [line=14]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/discard-udp 
[file=/etc/xinetd.d/discard-udp] [line=25]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/echo 
[file=/etc/xinetd.d/echo] [line=14]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/echo-udp 
[file=/etc/xinetd.d/echo-udp] [line=26]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/egd-py 
[file=/etc/xinetd.d/egd-py] [line=14]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/entropy 
[file=/etc/xinetd.d/entropy] [line=21]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/servers 
[file=/etc/xinetd.d/servers] [line=21]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/services 
[file=/etc/xinetd.d/services] [line=13]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/time 
[file=/etc/xinetd.d/time] [line=13]
xinetd[9295]: Reading included configuration file: /etc/xinetd.d/time-udp 
[file=/etc/xinetd.d/time-udp] [line=28]
xinetd[9295]: 2.3.15.3 started with libwrap loadavg labeled-networking options 
compiled in.
xinetd[9295]: Started working: 0 available services





When I comment out the socket_type and protocol lines in the conf (since they 
are redundant to type being TCPMUXPLUS), restarting xinetd segfaults:


systemd[1]: Started xinetd.service - LSB: Starts or stops the xinetd daemon..
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/chargen 
[file=/etc/xinetd.conf] [line=14]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/chargen-udp 
[file=/etc/xinetd.d/chargen-udp] [line=28]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/daytime 
[file=/etc/xinetd.d/daytime] [line=14]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/daytime-udp 
[file=/etc/xinetd.d/daytime-udp] [line=26]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/discard 
[file=/etc/xinetd.d/discard] [line=14]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/discard-udp 
[file=/etc/xinetd.d/discard-udp] [line=25]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/echo 
[file=/etc/xinetd.d/echo] [line=14]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/echo-udp 
[file=/etc/xinetd.d/echo-udp] [line=26]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/egd-py 
[file=/etc/xinetd.d/egd-py] [line=14]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/entropy 
[file=/etc/xinetd.d/entropy] [line=21]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/servers 
[file=/etc/xinetd.d/servers] [line=21]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/services 
[file=/etc/xinetd.d/services] [line=13]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/time 
[file=/etc/xinetd.d/time] [line=13]
xinetd[9364]: Reading included configuration file: /etc/xinetd.d/time-udp 
[file=/etc/xinetd.d/time-udp] [line=28]
xinetd[9364]: 9364 {general_handler} (9364) Unexpected signal: 11 (Segmentation 
fault)
xinetd[9364]: 9364 {general_handler} (9364) Unexpected signal: 11 (Segmentation 
fault)
xinetd[9364]: 9364 {general_handler} (9364) Unexpected signal: 11 (Segmentation 
fault)
xinetd[9364]: 9364 {general_handler} (9364) Unexpected signal: 11 (Segmentation 
fault)
xinetd[9364]: 9364 

Bug#1056141: nvenc encoder not available after installing libnvidia-encode1 and enabling ffnvcodec

[Brian Bostwick]

Package: ffmpeg
Version: 7:6.1-2

Hi in Trixie, using nvidia-driver 525.125.06-2, libnvidia-encode1
525.125.06-2, and ffmpeg 7:6.1-2, I can't seem to get the nvenc codec
built into ffmpeg.

$ ffmpeg -codecs | grep 264
H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_v4l2m2m
h264_qsv h264_cuvid ) (encoders: libx264 libx264rgb h264_omx h264_qsv
h264_v4l2m2m h264_vaapi )

These are the additional enable flags I added to the debian/rules file:

--enable-nonfree \
--enable-cuda-llvm \
--enable-ffnvcodec

Full build configuration:

  configuration:
--prefix=/usr
--extra-version=9
--toolchain=hardened
--libdir=/usr/lib/x86_64-linux-gnu
--incdir=/usr/include/x86_64-linux-gnu
--arch=amd64
--enable-gpl
--disable-stripping
--enable-gnutls
--enable-ladspa
--enable-libaom
--enable-libass
--enable-libbluray
--enable-libbs2b
--enable-libcaca
--enable-libcdio
--enable-libcodec2
--enable-libdav1d
--enable-libflite
--enable-libfontconfig
--enable-libfreetype
--enable-libfribidi
--enable-libglslang
--enable-libgme
--enable-libgsm
--enable-libjack
--enable-libmp3lame
--enable-libmysofa
--enable-libopenjpeg
--enable-libopenmpt
--enable-libopus
--enable-libpulse
--enable-librabbitmq
--enable-librist
--enable-librubberband
--enable-libshine
--enable-libsnappy
--enable-libsoxr
--enable-libspeex
--enable-libsrt
--enable-libssh
--enable-libtheora
--enable-libtwolame
--enable-libvidstab
--enable-libvorbis
--enable-libvpx
--enable-libwebp
--enable-libx265
--enable-libxml2
--enable-libxvid
--enable-libzimg
--enable-libzmq
--enable-libzvbi
--enable-lv2
--enable-omx
--enable-openal
--enable-opencl
--enable-opengl
--enable-sdl2
--enable-nonfree
--enable-cuda-llvm
--enable-ffnvcodec
--disable-sndio
--enable-libjxl
--enable-pocketsphinx
--enable-librsvg
--enable-libvpl
--disable-libmfx
--enable-libdc1394
--enable-libdrm
--enable-libiec61883
--enable-chromaprint
--enable-frei0r
--enable-libsvtav1
--enable-libx264
--enable-libplacebo
--enable-librav1e
--enable-shared

After being built I just installed the ffmpeg and libavcodec debs.

$ dpkg -i': sudo dpkg -i ffmpeg_6.0-9_amd64.deb
libavcodec60_6.0-9_amd64.deb libavcodec-extra*

I originally had the proprietary driver installed via the vendor's
script, but it has since been removed.

My goal is to have nvenc appear as an option in OBS, which depends on
ffmpeg to have the codec available.

Bug#1051418: Info received (obs-studio: clicking on an xcomposite window source makes obs segfault)

[Brian Bostwick]

On Mon, 23 Oct 2023 22:20:04 + (UTC) Michael Neilly 
wrote:
> Sending in plain text so it is readable:
>
>
> I'm seeing the same bug in the latest Debian testing updated this
> morning. Specifically, if I have the following github page open in my
> browser clicking the xcomposite window source cases a seg fault as
> reported.
>
>
> Â  Â  https://github.com/pjreddie/darknet/issues/553
>
>
> This results in a window name of
>
>
>     "Error on make: 'cuda_runtime.h: No such file or directory' ·
Issue #553 · pjreddie/darknet - Brave"
>
>
> In xcompcap_props(), the name_lower variable has zero values in the
> struct which is then pushed to window_strings.array. I can't currently
> step into dstr_to_lower().
>
>
> The following shows the array entry in window_strings.array:
>
>
> Â  Â  $18 = {
> Â  Â  name_lower = {array = 0x0, len = 0, capacity = 0},
> Â  Â  name = {
> Â  Â  Â  Â  array = 0x570b88e0 "Error on make: 'cuda_runtime.h: No
such file or directory' · Issue #553 · pjreddie/darknet - Brave",
> Â  Â  Â  Â  len = 100,
> Â  Â  Â  Â  capacity = 101
> Â  Â  },
> Â  Â  desc = {
> Â  Â  Â  Â  array = 0x55c24560 "54525967\r\nError on make:
'cuda_runtime.h: No such file or directory' · Issue #553 ·
pjreddie/darknet - Brave\r\nbrave-browser",
> Â  Â  Â  Â  len = 125,
> Â  Â  Â  Â  capacity = 126
> Â  Â  }
> Â  Â  }
>
>
> The following is the gdb backtrace with frame 11 being the frame where
> the above was observed.
>
>
> (gdb) bt
> #0Â  __strcmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:283
> #1Â  0x73e5de65 in msort_with_tmp (p=p@entry=0x7fffc510,
b=b@entry=0x7fffc448, n=n@entry=3) at ./stdlib/msort.c:123
> #2Â  0x73e5ddb1 in msort_with_tmp (n=3, b=0x7fffc448,
p=0x7fffc510) at ./stdlib/msort.c:44
> #3Â  msort_with_tmp (p=p@entry=0x7fffc510, b=b@entry=0x7fffc430,
n=n@entry=6) at ./stdlib/msort.c:53
> #4Â  0x73e5dd94 in msort_with_tmp (n=6, b=0x7fffc430,
p=0x7fffc510) at ./stdlib/msort.c:44
> #5Â  msort_with_tmp (p=p@entry=0x7fffc510, b=b@entry=0x7fffc430,
n=n@entry=12) at ./stdlib/msort.c:52
> #6Â  0x73e5ddb1 in msort_with_tmp (n=12, b=0x7fffc430,
p=0x7fffc510) at ./stdlib/msort.c:44
> #7Â  msort_with_tmp (p=p@entry=0x7fffc510, b=0x7fffc3d8, n=n@entry=23)
at ./stdlib/msort.c:53
> #8Â  0x73e5e23b in msort_with_tmp (n=23, b=,
p=0x7fffc510) at ./stdlib/msort.c:44
> #9Â  __GI___qsort_r (b=b@entry=0x570e2320, n=n@entry=23, s=s@entry=72,
cmp=cmp@entry=0x7fffe1fdaac0 , arg=arg@entry=0x0) at
./stdlib/msort.c:253
> #10 0x73e5e3c8 in __GI_qsort (b=b@entry=0x570e2320, n=n@entry=23,
s=s@entry=72, cmp=cmp@entry=0x7fffe1fdaac0 ) at ./stdlib/msort.c:307
> #11 0x7fffe1fdbcb5 in xcompcap_props (unused=) at
./plugins/linux-capture/xcomposite-input.c:750
> #12 0x765629f6 in obs_source_properties () at
/lib/x86_64-linux-gnu/libobs.so.0
> #13 0x5564c3d5 in SourceToolbar::SourceToolbar(QWidget*,
OBSSafeRef)
(source=..., parent=0x55ea89a0, this=0x56074fd0) at
./libobs/obs.hpp:103

Installing testing's nvidia-cuda-toolkit and nvidia-driver packages
resolved this for me. Originally, I installed the driver via the .run file,
which I still think can work if you ensure the cuda libs are selected
during the setup process.

Bug#1039050: Please test latest upload

[Brian Vaughan]

foliate 2.6.4-1+dfsg5 wasn't in unstable, but it was in experimental. I tried 
it and it seems to be working.

Bug#1054622: im-config: can set GTK_IM_MODULE to xim, which causes GTK 4 to complain

[brian m. carlson]

On 2023-10-26 at 22:51:19, Gunnar Hjalmarsson wrote:
> On 2023-10-26 23:51, brian m. carlson wrote:
> > I have a system with Zoom installed, which necessitates installing
> > ibus, which I don't want to use (because it overrides my shortcut
> > keys without consent).  Thus, the advice I've received is to install
> > im-config and use to set the module to "xim".
> 
> That's bad advice. Where did you get it?
> 
> Don't set it to "xim", set it to "none" instead, which means that im-config
> does not touch any environment variables (and does not launch ibus-daemon).

I believe I got it when I filed a bug report on ibus about some bug
where it affected my input in some way.  I don't recall, since it's been
some time.

> > I don't think, given that GTK+ 4 is used for a wide variety of
> > software in Debian, that it's safe to set GTK_IM_MODULE to "xim"
> > anymore, and im-config needs to not do that.
> 
> Your observation is not a sufficient reason to conclude that "xim" is never
> useful and should be removed as an option. im-config does not set that
> option automatically, but only if the user chooses it explicitly. In your
> case due to a bad advice. ;)
> 
> So I'm inclined to close this bug as a "wontfix", but await possible further
> input on the matter.

I'd argue that setting any environment variables that make programs
scream to the terminal is not okay.  I'm fine with im-config setting any
value that doesn't do that.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1054622: im-config: can set GTK_IM_MODULE to xim, which causes GTK 4 to complain

[brian m. carlson]

none


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

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

Versions of packages im-config depends on:
ii  gettext-base  0.21-13+b1

Versions of packages im-config recommends:
ii  whiptail0.52.23-1+b1
ii  x11-common  1:7.7+23
ii  zenity  3.44.2-1

im-config suggests no packages.

-- no debconf information

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1021339: Offer to help with some neovim packaging

[brian m. carlson]

Hey,

I noticed that there's some dependencies that need to be packaged for
Debian in order to update to the latest neovim.  I'm not a Debian
developer, but I'm familiar enough with Debian packaging and such.

Is there a way I can contribute to packaging the necessary dependencies
or helping in some other way with the upgrade to a newer version of
Neovim?  (This isn't a long-term commitment, just some help for the
immediate upgrade.)  I do already have a salsa.debian.org account, so if
you give me a little bit of direction as to the tooling you'd like to
use and/or an example of how it's done (say, another repo), I can take
it from there.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#998408: "good password" advice in installer is still bad two years after this was reported

[Brian Potkin]

On Thu 07 Sep 2023 at 01:27:23 +0200, Philip Hands wrote:

> Jonathan Kamens  writes:
> 
> > Oh, I see now that the fact that the installer shouldn't recommend 
> > changing one's password regularly was also reported previously, in bug 
> > #868869.
> 
> Also, in #656509 (in which Cyril states that the effort of translating a
> new message outweighs the importance of the change).
> 
> I've no idea if that justification for inaction still stands, but I
> thought this would make a nice little example for the use of the
> salsa-CI pipeline (and my branch2repo variant of that), so here's an MR:
> 
>   https://salsa.debian.org/installer-team/user-setup/-/merge_requests/7
> 
> and here's a screenshot of what the change looks like:
> 
>   https://openqa.debian.net/tests/185853#step/passwords/1
> 
> I'm not 100% happy with the wording (and the underlines around 'should'
> need to go) so I'm very likely to tweak it tomorrow.
> 
> Suggestions for improvement welcome, although be aware that given the
> resistance to fixing this in the past, it's always possible such a
> change will also be deemed unjustified now.
> 
> I think it's probably about time we fixed it, since even the civil
> servants in the UK have stopped recommending password changes by now,
> and they tend to make such changes at least a decade late. ;-)

The password strength advice in d-i has been there from the year dot.
Irrespective of what GCHQ and others say now, it was a load of nonsense
then and remains so.

The vast majority of users ignore it; some might schedule a password
change at the same time they change the locks on all outside doors of
their residence or on their cars.

Debian has no need to offer password advice (as opposed to roo vs sudo).
So leave it there as a historical oddity or delete the d-i advice. The
latter route does not involve anyone in any great effort to maintain
the staus quo.

-- 
Brian.

Bug#1042570: ippsample: ippserver and ippfind are non-functional

[Brian Potkin]

Package: ippsample
Version: 0.0~git20220607.72f89b3
Severity: grave
Justification: renders package unusable


In spite of having the printing system wiped out (Bug#1040699) I installed
this package to try out ippserver.

brian@test-new:~$ /usr/sbin/ippserver -c $HOME/pdfsave -f application/pdf 
"Print to PDF"
/usr/sbin/ippserver: error while loading shared libraries: libcups.so.3: cannot 
open shared object file: No such file or directory
brian@test-new:~$

ippfind produces the same output.

Regards,

Brian.

Bug#1040507: golang-1.21-go: downloads and runs binaries from the Internet without permission

[brian m. carlson]

Package: golang-1.21-go
Version: 1.21~rc2-2
Severity: grave
Tags: security

Go 1.21 provides the `GOTOOLCHAIN` environment variable and associated
functionality[0].  As part of this code, if go.mod indicates that a
newer version of Go is required than the current toolchain supports, it
proceeds by default to attempt to download a toolchain from the Internet
and runs it without prompting the user.

It is unclear what, if any cryptographic verification it performs,
especially if the user has disabled GOPROXY and GOSUMDB for privacy
reasons.  As far as I know, the Go core team does not sign Linux
binaries cryptographically, so at best the data would be verified by a
hash, which is not sufficient.  Debian itself uses a strong
cryptographic signature for APT archives.

In addition, it's possible that a newer version of the toolchain might
contain some vulnerability which is not present in the current
toolchain, and therefore might expose the user to new vulnerabilities
that are not patched.  This is not at all far-fetched, since Go is known
to have regressions all the time, so security-based regressions are not
at all out of the question.

I don't believe this is an appropriate way for software distributed in
Debian to behave, especially by default, and I'd like to request that it
be patched out for security reasons.

Steps to reproduce:
1. Clone a Go project (e.g., Git LFS).
2. Update go.mod to state "go 1.22".
3. Run /usr/lib/go-1.21/bin/go build
4. Notice the following output:

go: downloading go1.22 (linux/amd64)
go: download go1.22 for linux/amd64: toolchain not available

[0] https://tip.golang.org/doc/toolchain



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

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

Versions of packages golang-1.21-go depends on:
ii  golang-1.21-src  1.21~rc2-2

Versions of packages golang-1.21-go recommends:
ii  g++   4:12.3.0-1
ii  gcc   4:12.3.0-1
ii  libc6-dev 2.37-3
ii  pkg-config1.8.1-1
ii  pkgconf [pkg-config]  1.8.1-1

Versions of packages golang-1.21-go suggests:
pn  bzr | brz
ii  ca-certificates  20230311
ii  git  1:2.40.1+next.20230427-1
pn  mercurial
pn  subversion   

-- no debconf information

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1039983: cups: CMYK capable printer does not print in colour

[Brian Potkin]

tags 1039983 upstream
retitle 1039983 CMYK capable printer does not print in colour
thanks



On Fri 30 Jun 2023 at 17:56:08 +0200, Kerstin Hoef-Emden wrote:

> Package: cups
> Version: 2.4.2-3
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> Upgrade from bullseye to bookworm
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> First of all, the printer drivers for my printer (Kyocera FS-C5250dn) were not
> anymore available in the printers list. The original Kyocera PPD files were
> still present in the file system. I chose them by browsing the file system.
> Although the printer was now identified as capable of doing CMYK and it was 
> set
> to color in the cups browser interface. I also tried to change the setting in
> printer.conf a) by hand to printer-color-mode CMYK and I tried the command
> lpoptions -p Kyocera -o printer-colormode=CMYK.
> 
>* What was the outcome of this action?
> It did not work, the printer still prints only Black & White and I am not able
> to change the setting in printer.conf.
> 
>* What outcome did you expect instead?
> 
> For sure I want my color printer to print color again.

THank you for your report,  Kerstin. Your issue sounds like the on at

  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1971242

Does the lpadmin workaround do anything for you?

Regards,

Brian.

Bug#1039952: alacritty: broken rendering with Source Code Pro

[brian m. carlson]

Package: alacritty
Version: 0.11.0-4
Severity: normal
Tags: upstream fixed-upstream

If the user has configured Source Code Pro as the terminal font, then
text is rendered very tiny and squashed at the top of the window.

To reproduce:

1. Install texlive-fonts-extra.
2. mkdir -p ~/.fonts
3. ln -s /usr/share/texlive/texmf-dist/fonts/opentype/adobe ~/.fonts
4. Run fc-cache.
5. Modify the configuration file to contain this block:


font:
  normal:
family: Source Code Pro
style: Regular


6. Restart Alacritty if `live_config_reload` isn't specified.
7. Notice that the text is tiny and squashed at the top of the terminal
and you can't read anything at all.

I believe this is fixed in 0.12.0 and was tracked upstream at
https://github.com/alacritty/alacritty/issues/6048.  This will probably
be fixed simply by updating Alacritty to the latest version, so it would
be great if that could happen.

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

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

Versions of packages alacritty depends on:
ii  libc6   2.36-9
ii  libfontconfig1  2.14.1-4
ii  libfreetype62.12.1+dfsg-5
ii  libgcc-s1   13.1.0-6
ii  libxcb1 1.15-1

alacritty recommends no packages.

alacritty suggests no packages.

-- no debconf information

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1039532: debvm: autopkgtest fails due to missing testdep on debian-archive-keyring

[Brian Murray]

Package: debvm
Version: 0.2.12
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic
X-Debbugs-Cc: br...@ubuntu.com

Dear Maintainer,

This bug report was also filed in Ubuntu and can be found at
https://launchpad.net/bugs/2025093

The description, from Brian Murray, follows:

Two autopkgtests, command1 and command2, included with debvm are failing in 
Ubuntu due to a missing test dependency on debian-archive-keyring. Sample 
failure:

Get:1 http://deb.debian.org/debian sid InRelease [195 kB]
Err:1 http://deb.debian.org/debian sid InRelease
  The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9
Reading package lists...
W: GPG error: http://deb.debian.org/debian sid InRelease: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9
E: The repository 'http://deb.debian.org/debian sid InRelease' is not signed.
E: command failed: /usr/share/mmdebstrap/hooks/maybe-merged-usr/setup00.sh
I: main() received signal PIPE: waiting for setup...
bash: line 1:  1306 Hangup  bash -ec './tests/create-and-run.sh 
$(dpkg --print-architecture) sid' 2> >(tee -a 
/tmp/autopkgtest.k9nz7H/command1-stderr 1>&2) > >(tee -a 
/tmp/autopkgtest.k9nz7H/command1-stdout)
Hangup
autopkgtest [18:43:46]: test command1: ---]
command1 FAIL non-zero exit status 255

A full log file can be found at:
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/d/debvm/20230602_184405_93dba@/log.gz

Adding debian-archive-keyring to the dependencies in debian/tests/control will 
resolve the issue.

Bug#1039050: foliate: Suddenly aborts after about a minute

[Brian Vaughan]

Package: foliate
Version: 2.6.4-1+dfsg3
Severity: important
X-Debbugs-Cc: bgvaug...@gmail.com

After opening a document, foliate suddenly aborts, after perhaps a minute.
There's no action being taken by the user at the moment it exits.

Console showed these two errors after launch:

(com.github.johnfactotum.Foliate:33325): Gjs-WARNING **: 19:42:48.901:
Unhandled promise rejection. To suppress this warning, add an error handler to
your promise chain with .catch() or a try-catch block around your await
expression. Stack trace of the failed promise:
  main@resource:///com/github/johnfactotum/Foliate/js/main.js:478:24
  run@resource:///org/gnome/gjs/modules/script/package.js:206:19
  @/usr/bin/foliate:9:17


(com.github.johnfactotum.Foliate:33325): Gjs-WARNING **: 19:43:09.468:
Unhandled promise rejection. To suppress this warning, add an error handler to
your promise chain with .catch() or a try-catch block around your await
expression. Stack trace of the failed promise:
  main@resource:///com/github/johnfactotum/Foliate/js/main.js:478:24
  run@resource:///org/gnome/gjs/modules/script/package.js:206:19
  @/usr/bin/foliate:9:17


And this error after foliate aborts:

***MEMORY-ERROR***: com.github.johnfactotum.Foliate[33325]: GSlice: assertion
failed: sinfo->n_allocated > 0
Aborted



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

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

Versions of packages foliate depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-webkit2-4.0   2.40.2-1
ii  gjs  1.74.3-1
ii  python3  3.11.2-1+b1

Versions of packages foliate recommends:
ii  gnome-epub-thumbnailer  1.7-3

foliate suggests no packages.

-- no debconf information

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

I hadn't even noticed Synaptic kept logs.

There was one other set of updates, after the last time I saw the error 
in Spyder:


Commit Log for Wed May 31 16:06:10 2023


Upgraded the following packages:
chromium (113.0.5672.126-1) to 114.0.5735.90-1
chromium-common (113.0.5672.126-1) to 114.0.5735.90-1
chromium-sandbox (113.0.5672.126-1) to 114.0.5735.90-1
libgc1 (1:8.2.2-3) to 1:8.2.4-1
libnautilus-extension4 (43.2-1) to 43.4-1
libssl-dev (3.0.8-1) to 3.0.9-1
libssl3 (3.0.8-1) to 3.0.9-1
libssl3:i386 (3.0.8-1) to 3.0.9-1
needrestart (3.6-3) to 3.6-4
openssl (3.0.8-1) to 3.0.9-1
signal-desktop (6.19.0) to 6.20.0
syncthing-gtk (0.9.4.4+ds+git20221205+12a9702d29ab-1) to 
0.9.4.4+ds+git20221205+12a9702d29ab-2

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

I have good news and bad news.

The good news is that the issue seems to have been fixed as of today. I 
don't get the error popup, and Help > Dependencies shows pylsp_black 
installed and at version 1.21.


The bad news is I'm not sure what fixed it. I realized I made the 
mistake of following my daily routine of updating my system, which is 
not a good idea when troubleshooting. I checked the changelog dates on 
the dependencies for python3-spyder, and the most recently updated were 
python3-pygments on April 19, and python3-cookiecutter and 
python3-sphinx on March 29.


The only updates today were chromium, chromium-common, and 
chromium-sandbox, updated to 114.0.5735.90-2. Maybe those are indirect 
dependencies?

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

That rgrep didn't find anything.

Executing 'spyder' from the command line while in an empty directory 
still got the same 'pylsp_black' warning.

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

It didn't return anything. Neither did "locate 
'v0.9.4.4-ds-git20221205-12a9702d29ab'".

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

Yes, that's what it starts with.

Metadata-Version: 2.1
Name: python-lsp-black
Version: 1.2.1
Summary: Black plugin for the Python LSP Server
Home-page: https://github.com/python-lsp/python-lsp-black
Author: Python LSP contributors
Author-email: f...@fidelramos.net
Project-URL: Bug Tracker, 
https://github.com/python-lsp/python-lsp-black/issues
Project-URL: Changelog, 
https://github.com/python-lsp/python-lsp-black/blob/master/CHANGELOG.md

Project-URL: Source Code, https://github.com/python-lsp/python-lsp-black
Classifier: Programming Language :: Python
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Requires-Python: >=3.7
Description-Content-Type: text/markdown
Provides-Extra: dev
License-File: LICENSE

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

Yes, the other commands returned "file not found". (I hit send prematurely.)

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

$ ls -lR /usr/lib/python3/dist-packages/python_lsp_black*
/usr/lib/python3/dist-packages/python_lsp_black-1.2.1.egg-info:
total 20
-rw-r--r-- 1 root root    1 Dec  9 22:58 dependency_links.txt
-rw-r--r-- 1 root root   41 Dec  9 22:58 entry_points.txt
-rw-r--r-- 1 root root 4077 Dec  9 22:58 PKG-INFO
-rw-r--r-- 1 root root   96 Dec  9 22:58 requires.txt
-rw-r--r-- 1 root root   12 Dec  9 22:58 top_level.txt


$ ls -lR /usr/lib/python3/dist-packages/pylsp_black*
/usr/lib/python3/dist-packages/pylsp_black:
total 12
-rw-r--r-- 1 root root    0 Apr 12  2022 __init__.py
-rw-r--r-- 1 root root 6337 Apr 12  2022 plugin.py
drwxr-xr-x 2 root root 4096 May 24 16:59 __pycache__

/usr/lib/python3/dist-packages/pylsp_black/__pycache__:
total 16
-rw-r--r-- 1 root root  163 May 24 16:59 __init__.cpython-311.pyc
-rw-r--r-- 1 root root 8963 May 24 16:59 plugin.cpython-311.pyc

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

Thank you for the clear instructions. I appreciate it.

The complete output is here:

https://www.geany.org/p/TQ2R2/

I believe this is the relevant part:

2023-05-29 09:28:09,387 [DEBUG] [spyder.dependencies] -> 
Dependency(pylsp, pytho

n_lsp_server) starting
2023-05-29 09:28:09,387 [DEBUG] [spyder.dependencies] -> Dependency: 
get_module_version returned 1.7.1 for pylsp
2023-05-29 09:28:09,387 [DEBUG] [spyder.dependencies] -> 
Dependency(pylsp_black, python_lsp_black) starting
2023-05-29 09:28:09,471 [DEBUG] [spyder.dependencies] -> Dependency: 
exception raised: Invalid version: 'v0.9.4.4-ds-git20221205-12a9702d29ab'
2023-05-29 09:28:09,471 [DEBUG] [spyder.dependencies] -> Dependency: 
when exception raised: sys.path = ['', 
'/usr/lib/python3/dist-packages/spyder/plugins/help/utils', '/usr/bin', 
'/usr/lib/python311.zip', '/usr/lib/python3.11', 
'/usr/lib/python3.11/lib-dynload', 
'/usr/local/lib/python3.11/dist-packages', 
'/usr/lib/python3/dist-packages', '/usr/lib/python3.11/dist-packages']

Bug#1036928: RFP: astro -- a gemini web browser

[Brian Mayer]

Package: astro
Severity: wishlist

* Package name: astro
  Version : 0.20.0
  Upstream Author : blmayer
* URL : https://github.com/blmayer/astro
* License : MIT
  Programming Lang: Shell
  Description : A Gemini web browser written in POSIX shell script

Hi Debian Team.

The Gemini web is a new protocol for content publishing that is focused on
content and user privacy. It stays between Gopher and HTTP, as the authors
describe it.

Astro is a browser that helps users to find and navigate the Gemini web, it
is a FOSS  with a stable version with all needed features described on the
protocol. Using only a few utilities it has minimal dependencies, as it is
written in POSIX shell script it is know to work well on many platforms.
Currently it is being packaged for Archlinux and it's user base is
increasing, hence, having it on Debian systems would be a great addition to
the community.

The Gemini community is growing fast and having astro packaged will
continue this movement.

Thank you!

Bug#1035679: [Pkg-zsh-devel] Bug#1035679: zsh: can misprocess continue in a loop

[brian m. carlson]

On 2023-05-08 at 00:58:24, Axel Beckert wrote:
> brian m. carlson wrote:
> > This breaks the Git testsuite under zsh's sh mode,
> 
> Hmmm, actually, your example code shows "set" for me even without sh
> emulation mode:
> 
>   → zsh continue.sh
>   set
>   → zsh --emulate sh continue.sh
>   set

Correct.  The Git testsuite only runs under sh mode, not zsh mode, but
it affects all modes.

> > which was formerly passing.
> 
> When was "formerly", i.e. in which package or upstream version?

Git 2.25.  It may be that Git has changed the testsuite to make use of
that syntax between now and then, but as of that revision, it passed.

> > since the release cycle tends to be long
> 
> Well, 5.9 is out for quite a while already. So I think we can expect a
> new release before the the Debian 13 release. ;-)
> 
> But yeah, I think we can cherry-pick this from upstream after the
> Bookworm release.

Great, I appreciate that.

> > and it prevents the shell from being effectively used as a POSIX sh.
> 
> Well, zsh's POSIX mode is officially declared as being incomplete and
> it's IIRC also not recommended to actually use it or at least not rely
> on it.

zsh should be able to run as a POSIX sh.  The reason that we only
support sh mode in Git is that we rely on every command in a pipeline
being run in a subshell, since we only recently introduced the use of
`local` in the shell and otherwise our variables get messed up.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

# Spyder, Help > Dependencies

# Mandatory:
atomicwrites >=1.2.0  :  1.4.1 (OK)
chardet >=2.0.0   :  5.1.0 (OK)
cloudpickle >=0.5.0   :  2.2.0 (OK)
cookiecutter >=1.6.0  :  1.7.3 (OK)
diff_match_patch >=2018   :  20200713 (OK)
intervaltree >=3.0.2  :  3.0.2 (OK)
IPython >=7.31.1;<9.0.0   :  8.5.0 (OK)
jedi >=0.17.2;<0.19.0 :  0.18.2 (OK)
jellyfish >=0.7   :  0.8.9 (OK)
jsonschema >=3.2.0    :  4.10.3 (OK)
keyring >=17.0.0  :  23.9.3 (OK)
nbconvert >=4.0   :  6.5.3 (OK)
numpydoc >=0.6.0  :  1.5.0 (OK)
parso >=0.7.0;<0.9.0  :  0.8.3 (OK)
pexpect >=4.4.0   :  4.8.0 (OK)
pickleshare >=0.4 :  0.7.5 (OK)
psutil >=5.3  :  5.9.4 (OK)
pygments >=2.0    :  2.15.1 (OK)
pylint >=2.5.0;<3.0   :  2.16.2 (OK)
pylint_venv >=2.1.1   :  2.3.0 (OK)
pyls_spyder >=0.4.0   :  0.4.0 (OK)
pylsp >=1.7.1;<1.8.0  :  1.7.1 (OK)
pylsp_black >=1.2.0   :  None (NOK)
qdarkstyle >=3.0.2;<3.2.0 :  3.1 (OK)
qstylizer >=0.2.2 :  0.2.2 (OK)
qtawesome >=1.2.1 :  1.2.2 (OK)
qtconsole >=5.4.0;<5.5.0  :  5.4.0 (OK)
qtpy >=2.1.0  :  2.3.0 (OK)
rtree >=0.9.7 :  1.0.1 (OK)
setuptools >=49.6.0   :  66.1.1 (OK)
sphinx >=0.6.6    :  5.3.0 (OK)
spyder_kernels >=2.4.2;<2.5.0 :  2.4.2 (OK)
textdistance >=4.2.0  :  4.5.0 (OK)
three_merge >=0.1.1   :  0.1.1 (OK)
watchdog >=0.10.3 :  2.2.1 (OK)
xdg >=0.26    :  0.28 (OK)
zmq >=22.1.0  :  24.0.1 (OK)

# Optional:
cython >=0.21 :  None (NOK)
matplotlib >=3.0.0    :  3.6.3 (OK)
numpy >=1.7   :  1.24.2 (OK)
pandas >=1.1.1    :  None (NOK)
scipy >=0.17.0    :  1.10.1 (OK)
sympy >=0.7.3 :  1.11.1 (OK)


# Spyder, Help > About Spyder

* Spyder version: 5.4.2  (pip)
* Python version: 3.11.2 64-bit
* Qt version: 5.15.8
* PyQt5 version: 5.15.9
* Operating System: Linux 6.1.0-9-amd64


# Commands in the iPython console

Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
Type "copyright", "credits" or "license" for more information.

IPython 8.5.0 -- An enhanced Interactive Python.

import sys

sys.executable
Out[2]: '/usr/bin/python3'

sys.path
Out[3]:
['/usr/lib/python311.zip',
 '/usr/lib/python3.11',
 '/usr/lib/python3.11/lib-dynload',
 '',
 '/usr/local/lib/python3.11/dist-packages',
 '/usr/lib/python3/dist-packages',
 '/usr/lib/python3.11/dist-packages']

import pylsp_black

sys.modules["pylsp_black"]
Out[5]: '/usr/lib/python3/dist-packages/pylsp_black/__init__.py'>

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

I'm seeing the same issue, on two different systems, both running Debian 
Sid.


On one system, there were some libraries under ~/.local/lib/python3.10; 
I deleted those, deleted the config files for spyder, reinstalled it, 
and rebooted, but still saw the error.

Bug#1036735: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

Package: spyder
Version: 5.4.2+ds-5
Severity: minor
X-Debbugs-Cc: bgvaug...@gmail.com



-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages spyder depends on:
ii  python3 3.11.2-1+b1
ii  python3-spyder  5.4.2+ds-5

spyder recommends no packages.

Versions of packages spyder suggests:
pn  python3-spyder-unittest  

Versions of packages python3-spyder depends on:
ii  ipython3   8.5.0-4
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-mathjax  2.7.9+dfsg-1
ii  pyflakes3  2.5.0-1
ii  pylint 2.16.2-2
ii  python33.11.2-1+b1
ii  python3-atomicwrites   1.4.1-1
ii  python3-autopep8   2.0.1-1
ii  python3-chardet5.1.0+dfsg-2
ii  python3-cloudpickle2.2.0-1
ii  python3-cookiecutter   1.7.3-3
ii  python3-diff-match-patch   20200713-2
ii  python3-docutils   0.19+dfsg-6
ii  python3-flake8 5.0.4-4
ii  python3-intervaltree   3.0.2-1.1
ii  python3-ipython8.5.0-4
ii  python3-jedi   0.18.2-1
ii  python3-jellyfish  0.8.9-1+b4
ii  python3-jsonschema 4.10.3-1
ii  python3-keyring23.9.3-2
ii  python3-mccabe 0.7.0-1
ii  python3-nbconvert  6.5.3-3
ii  python3-numpydoc   1.5.0-1
ii  python3-parso  0.8.3-1
ii  python3-pexpect4.8.0-4
ii  python3-pickleshare0.7.5-5
ii  python3-pkg-resources  66.1.1-1
ii  python3-psutil 5.9.4-1+b1
ii  python3-pycodestyle2.10.0-1
ii  python3-pydocstyle 6.2.3-3
ii  python3-pygments   2.15.1+dfsg-1
ii  python3-pylint-venv2.3.0-2
ii  python3-pyls-spyder0.4.0-2
ii  python3-pylsp  1.7.1-1
ii  python3-pylsp-black1.2.1-2
ii  python3-pyqt5  5.15.9+dfsg-1
ii  python3-pyqt5.qtwebengine  5.15.6-1
ii  python3-qdarkstyle 3.1+ds1-1
ii  python3-qstylizer  0.2.2-1
ii  python3-qtawesome  1.2.2+dfsg-1
ii  python3-qtconsole  5.4.0-1
ii  python3-qtpy   2.3.0-1
ii  python3-rope   1.7.0-1
ii  python3-rtree  1.0.1-1
ii  python3-setuptools 66.1.1-1
ii  python3-sphinx 5.3.0-4
ii  python3-spyder-kernels 2.4.2-1
ii  python3-textdistance   4.5.0-1
ii  python3-three-merge0.1.1-4
ii  python3-watchdog   2.2.1-1
ii  python3-xdg0.28-2
ii  python3-zmq24.0.1-4+b1
ii  spyder-common  5.4.2+ds-5
ii  yapf3  0.32.0-1

python3-spyder recommends no packages.

Versions of packages python3-spyder suggests:
pn  cython3 
ii  python3-matplotlib  3.6.3-1+b1
ii  python3-numpy   1:1.24.2-1
pn  python3-pandas  
ii  python3-pil 9.4.0-1.1+b1
ii  python3-scipy   1.10.1-2
ii  python3-sympy   1.11.1-1

Versions of packages python3-pyqt5 depends on:
ii  libc6 2.36-9
ii  libgcc-s1 12.2.0-14
ii  libpython3.11 3.11.2-6
ii  libqt5core5a [qtbase-abi-5-15-8]  5.15.8+dfsg-10
ii  libqt5dbus5   5.15.8+dfsg-10
ii  libqt5designer5   5.15.8-2
ii  libqt5gui55.15.8+dfsg-10
ii  libqt5help5   5.15.8-2
ii  libqt5network55.15.8+dfsg-10
ii  libqt5printsupport5   5.15.8+dfsg-10
ii  libqt5test5   5.15.8+dfsg-10
ii  libqt5widgets55.15.8+dfsg-10
ii  libqt5xml55.15.8+dfsg-10
ii  libstdc++612.2.0-14
ii  python3   3.11.2-1+b1
ii  python3-pyqt5.sip 12.11.1-1

-- no debconf information

Bug#1036734: RFP: astro -- a gemini web browser

[Brian Mayer]

Package: astro
Severity: wishlist

* Package name: astro
  Version : 0.20.0
  Upstream Author : blmayer
* URL : https://github.com/blmayer/astro
* License : MIT
  Programming Lang: Shell
  Description : A Gemini web browser written in POSIX shell script

Hi Debian Team.

The Gemini web is a new protocol for content publishing that is focused on
content and user privacy. It stays between Gopher and HTTP, as the authors
describe it.

Astro is a browser that helps users to find and navigate the Gemini web, it
is a FOSS  with a stable version with all needed features described on the
protocol. Using only a few utilities it has minimal dependencies, as it is
written in POSIX shell script it is know to work well on many platforms.
Currently it is being packaged for Archlinux and it's user base is
increasing, hence, having it on Debian systems would be a great addition to
the community.

The Gemini community is growing fast and having astro packaged will
continue this movement.

Thank you!

Bug#1035841: fixed in amavisd-new 1:2.13.0-3

[Brian May]

Johannes Schauer Marin Rodrigues  writes:

> thank you! Would you like me to take care of filing the unblock request with
> release.debian.org or would you like to take care of that yourself?

Can you please do this?

Thanks
-- 
Brian May @ Debian

Bug#1035679: zsh: can misprocess continue in a loop

[brian m. carlson]

Package: zsh
Version: 5.9-4+b1
Severity: normal
Tags: patch

If a continue occurs in an && chain inside a loop, the continue is not
effective.  For example, if you save the following as foo.sh:


msg=unset
for x in 1 2 3 4 5; do
  continue && msg=set && print Not executed
  print Not executed, neither.
done
echo $msg


The output should be "unset", but zsh prints "set":


$ bash foo.sh
unset
$ dash foo.sh
unset
$ zsh foo.sh
set


This breaks the Git testsuite under zsh's sh mode, which was formerly
passing.

There's a patch upstream at
https://github.com/zsh-users/zsh/commit/12e5db145b098a62ff11b88eea26f473ea2ecdcf.
It would be great if this could be backported to zsh in Debian, since
the release cycle tends to be long and it prevents the shell from being
effectively used as a POSIX sh.

-- Package-specific info:

Packages which provide vendor completions:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version Architecture Description
+++-=-===--===
ii  alacritty 0.11.0-4amd64Fast, cross-platform, 
OpenGL terminal emulator
ii  bubblewrap0.8.0-2 amd64utility for unprivileged 
chroot and namespace manipulation
ii  containerd1.6.20~ds1-1+b1 amd64open and reliable 
container runtime
ii  curl  7.88.1-9amd64command line tool for 
transferring data with URL syntax
ii  docker.io 20.10.24+dfsg1-1+b2 amd64Linux container runtime
ii  dpkg-dev  1.21.21 all  Debian package 
development tools
ii  gh2.23.0+dfsg1-1  amd64GitHub CLI, GitHub’s 
official command line tool
ii  pulseaudio-utils  16.1+dfsg1-2+b1 amd64Command line tools for 
the PulseAudio sound server
ii  qpdf  11.3.0-1amd64tools for transforming 
and inspecting PDF files
ii  systemd   252.6-1 amd64system and service 
manager
ii  systemd-container 252.6-1 amd64systemd container/nspawn 
tools
ii  systemd-resolved  252.6-1 amd64systemd DNS resolver
ii  tmuxinator3.0.5-1 all  Create and manage tmux 
sessions easily
ii  udev  252.6-1 amd64/dev/ and hotplug 
management daemon
ii  vagrant   2.3.4+dfsg-1all  Tool for building and 
distributing virtualized development environments
ii  vlc-bin   3.0.18-2amd64binaries from VLC

The following files were modified:

/etc/systemd/resolved.conf

dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/


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

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

Versions of packages zsh depends on:
ii  debianutils  5.7-0.4
ii  libc62.36-9
ii  libcap2  1:2.66-3
ii  libtinfo66.4-2
ii  zsh-common   5.9-4

Versions of packages zsh recommends:
ii  libc6 2.36-9
ii  libgdbm6  1.23-3
ii  libncursesw6  6.4-2
ii  libpcre3  2:8.39-15

Versions of packages zsh suggests:
pn  zsh-doc  

-- no debconf information

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1034774: Acknowledgement (xine-ui: aborts/killed when trying to play certain videos)

[Brian Sammon]

Since I have successfully watched this video in the past, I decided to try 
rolling back some of the recent package upgrades I've done, in attempt to see 
which one broke this.
I've learned that if I downgrade xserver-xorg-video-intel to 
2:2.99.917+git20161206-1 (and xserver-xorg-core to 2:1.19.2-1+deb9u8) the 
problem goes away, and I can watch the video.

The following three combinations of packages trigger the problem:
v1/buster
xserver-xorg-core 2:1.20.4-1+deb10u9
xserver-xorg-video-intel 2:2.99.917+git20180925-2

v2/bullseye
xserver-xorg-core 1.20.11-1+deb11u3
xserver-xorg-video-intel 2.99.917+git20200714-1+deb11u1

v3/bookworm
xserver-xorg-core 21.1.7-2
xserver-xorg-video-intel 2.99.917+git20210115-1

(v1, v2, and v3 differ only in those two packages)

I can go to snapshot.debian.org and bisect between the Stretch and the Buster 
if you think that would be useful.

More details about my system:
This is a "Mac Mini (Mid 2007)" with a Intel 945-something chipset with a GMA 
950 video hardware.

Info gathered by "reportbug xserver-xorg-video-intel" (I didn't actually submit 
another bug):

-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 0

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.19.0-23-686-pae (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.269-1 (2022-12-20)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 22113 Apr 24 21:24 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[71.577] 
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[71.580] Current Operating System: Linux macmini 4.19.0-23-686-pae #1 SMP 
Debian 4.19.269-1 (2022-12-20) i686
[71.581] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-23-686-pae 
root=LABEL=120gb-1308c ro quiet
[71.583] xorg-server 2:21.1.7-2 (https://www.debian.org/support) 
[71.584] Current version of pixman: 0.42.2
[71.587]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[71.587] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[71.593] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 24 21:24:25 
2023
[71.685] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[71.704] (==) No Layout section.  Using the first Screen section.
[71.704] (==) No screen section available. Using defaults.
[71.704] (**) |-->Screen "Default Screen Section" (0)
[71.704] (**) |   |-->Monitor ""
[71.727] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[71.727] (==) Automatically adding devices
[71.727] (==) Automatically enabling devices
[71.727] (==) Automatically adding GPU devices
[71.727] (==) Automatically binding GPU devices
[71.727] (==) Max clients allowed: 256, resource mask: 0x1f
[71.784] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[71.784]Entry deleted from font path.
[71.784] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[71.784]Entry deleted from font path.
[71.816] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[71.816]Entry deleted from font path.
[71.816] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/75dpi,
built-ins
[71.816] (==) ModulePath set to "/usr/lib/xorg/modules"
[71.816] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[71.816] (II) Loader magic: 0x7537a0
[71.816] (II) Module ABI versions:
[71.816]X.Org ANSI C Emulation: 0.4
[71.816]X.Org Video Driver: 25.2
[71.817]X.Org XInput driver : 24.4
[71.817]X.Org Server Extension : 10.0
[71.817] (--) using VT number 2

[71.817] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[71.819] (II) xfree86: Adding drm device (/dev/dri/card0)
[71.819] (II) Platform probe for 
/sys/devices/pci:00/:00:02.0/drm/card0
[

Bug#1034774: xine-ui: aborts/killed when trying to play certain videos

[Brian Sammon]

Package: xine-ui
Version: 0.99.14-1
Severity: normal

Dear Maintainer,

When I try to view certain videos (one example is at
http://br1an.fastmail.fm.user.fm/debian/The_Banshees_Of_Inisherin.mp4 [4MB 
movie trailer] )
xine aborts/is killed immediately (sometimes after 1/2 sec of sound, but
never any video).

The following messages appear on the commandline where I ran xine:
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/i386-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  150 (XVideo)
  Minor opcode of failed request:  13 ()
  Value in failed request:  0x2
  Serial number of failed request:  772
  Current serial number in output stream:  774

Let me know if there's things I can do to troubleshoot this further.

-- System Information:
Architecture: i386 (i686)

Kernel: Linux 4.19.0-23-686-pae (SMP w/2 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 xine-ui depends on:
ii  libc62.36-9
ii  libcurl3-gnutls  7.43.0-1
ii  libjpeg62-turbo  1:2.0.6-4
ii  liblirc-client0  0.9.4c-9
ii  libpng16-16  1.6.37-3
ii  libreadline8 8.1-2
ii  libx11-6 2:1.8.4-2
ii  libxext6 2:1.3.4-1+b1
ii  libxft2  2.3.1-2
ii  libxine2 1.2.13-1
ii  libxine2-ffmpeg  1.2.13-1
ii  libxine2-x   1.2.13-1
ii  libxinerama1 2:1.1.4-2
ii  libxtst6 2:1.2.2-1
ii  libxv1   2:1.0.11-1.1
ii  libxxf86vm1  1:1.1.3-1+b1

Versions of packages xine-ui recommends:
ii  xdg-utils  1.1.3-1+deb10u1

xine-ui suggests no packages.

-- no debconf information

Bug#1034503: telegram-desktop: segmentation fault at ../sysdeps/x86_64/dl-machine.h:463

[Brian]

Package: telegram-desktop
Version: 3.1.1+ds-1~deb11u2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Was using telegram-desktop(3.1.1+ds-1~deb11u2) for a while then it stopped 
working.

When I tried to use it again, it got a segmentation fault.

I then used GDB to figure out if it can tell me what failed.
Looks like it died somewhere at ../sysdeps/x86_64/dl-machine.h:463 due to no 
such file or directory.

```bash
$ gdb telegram-desktop 
GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from telegram-desktop...
(No debugging symbols found in telegram-desktop)
(gdb) r
Starting program: /usr/bin/telegram-desktop 

Program received signal SIGSEGV, Segmentation fault.
0x77fde89b in elf_machine_rela (skip_ifunc=, 
reloc_addr_arg=0x58b4a758, version=, 
sym=0x55564688, reloc=0x558ed4b8, map=0x77ffe180)
at ../sysdeps/x86_64/dl-machine.h:463
463 ../sysdeps/x86_64/dl-machine.h: No such file or directory.
```

-- Package-specific info:

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

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

Versions of packages telegram-desktop depends on:
ii  libavcodec58  7:4.3.5-0+deb11u1
ii  libavformat58 7:4.3.5-0+deb11u1
ii  libavutil56   7:4.3.5-0+deb11u1
ii  libc6 2.31-13+deb11u5
ii  libdbusmenu-qt5-2 0.9.3+16.04.20160218-2+b1
ii  libgcc-s1 10.2.1-6
ii  libglib2.0-0  2.66.8-1
ii  libglibmm-2.4-1v5 2.64.2-2
ii  libhunspell-1.7-0 1.7.0-3
ii  libjpeg62-turbo   1:2.0.6-4
ii  libkf5waylandclient5  4:5.78.0-2
ii  liblz4-1  1.9.3-2
ii  libminizip1   1.1-8+b1
ii  libopenal11:1.19.1-2
ii  libopus0  1.3.1-0.1
ii  libqrcodegencpp1  1.6.0-1
ii  libqt5core5a [qtbase-abi-5-15-2]  5.15.2+dfsg-9
ii  libqt5dbus5   5.15.2+dfsg-9
ii  libqt5gui55.15.2+dfsg-9
ii  libqt5network55.15.2+dfsg-9
ii  libqt5svg55.15.2-3
ii  libqt5waylandclient5 [qtwayland-client-abi-5-15-  5.15.2-3
ii  libqt5widgets55.15.2+dfsg-9
ii  librlottie0-1 0.1+dfsg-2
ii  libsigc++-2.0-0v5 2.10.4-2
ii  libssl1.1 1.1.1n-0+deb11u4
ii  libstdc++610.2.1-6
ii  libswresample37:4.3.5-0+deb11u1
ii  libswscale5   7:4.3.5-0+deb11u1
ii  libx11-6  2:1.7.2-1
ii  libxcb-keysyms1   0.4.0-1+b2
ii  libxcb-record01.14-3
ii  libxcb-screensaver0   1.14-3
ii  libxcb1   1.14-3
ii  libxcomposite11:0.4.5-1
ii  libxdamage1   1:1.1.5-2
ii  libxext6  2:1.3.3-1.1
ii  libxfixes31:5.0.3-2
ii  libxrandr22:1.5.1-1
ii  libxtst6  2:1.2.3-1
ii  libxxhash0 

Bug#1033755: heimdal: CVE-2022-3116

[Brian May]

Salvatore Bonaccorso  writes:

> Version: 7.8.git20221117.28daf24+dfsg-1.1

Are you sure this applies to the unstable version?

I can only find one out of two chunks in the patch. Maybe it was already
fixed in the stable branch which we use for unstable?
-- 
Brian May @ Debian

Bug#1033745: sequeler: Unlisted dependency on libgda-5.0-mysql

[Brian Vaughan]

Package: sequeler
Version: 0.8.0-1+b2
Severity: normal
X-Debbugs-Cc: bgvaug...@gmail.com

Without libgda-5.0-mysql installed, Sequeler will fail to connect to a MariaDB
database, with the error message, "No provider 'MySQL' installed".

sequeler 0.8.0-1+b2 lists libgda-5.0-4 as a dependency. libgda-5.0-4 suggests
libgda-5.0-bin, libgda-5.0-mysql, and libgda-5.0-postgres.

According to this upstream bug, sequeler should list as dependencies
libgda-5.0-mysql and libgda-5.0-postgres.
https://github.com/Alecaddd/sequeler/issues/26


-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages sequeler depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  libc62.36-8
ii  libcairo21.16.0-7
ii  libgda-5.0-4 5.2.10-3
ii  libgee-0.8-2 0.20.6-1
ii  libglib2.0-0 2.74.6-1
ii  libgranite6  6.2.0-3
ii  libgtk-3-0   3.24.37-2
ii  libgtksourceview-3.0-1   3.24.11-2+b1
ii  libsecret-1-00.20.5-3
ii  libssh2-11.10.0-3+b1

sequeler recommends no packages.

sequeler suggests no packages.

-- no debconf information

Bug#1033625: closed by Brian Potkin (Re: Bug#1033625:)

[Brian Potkin]

On Thu 30 Mar 2023 at 15:54:09 +0200, Johan Kröckel wrote:

> Hi Brian,
> 
> thanks for your help. But isn't it still a bug that cups is creating a
> printer(-queue) that not only does not work, but also when using it opens
> connections to the printer for hours? I think about the situation, that you
> have many bookworm clients in the network, this could amount to a denial of
> service.
> 
> I deleted the not working Kyocera_ECOSYS_M5526cdw but cups keeps recreating
> it when I connect to the corresponding network.

The auto-creation of the queue (the one shown by 'lpstat -t' and that keeps
coming back after deletion) is done by cups-browsed, not by CUPS. Let's try
this:

Purge cups-browsed with

 apt purge cups-browsed

Then do 

 rm  rm /var/cache/cups/*

(the files will be regenerated) and restart cups.

 systemctl restart cups

'lstsat -l -e' should show a printer name. Can it be used to print? 'lpstat -t'
should not have implicitclass and should show the manually set up printer,

Cheers,

Brian.

Bug#1033616: cups prepends job number to job-name so job names near 255 characters may be too long

[Brian Potkin]

On Tue 28 Mar 2023 at 18:45:02 +0200, John Hughes wrote:

> Package: cups
> Version: 2.3.3op2-3+deb11u2
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> I printed a page from firefox with a very, very long URL.  Firefox used the 
> first 255 bytes of the URL as the job name.
> 
>* What was the outcome of this action?
> 
> The job mysteriously didn't print.  Lookin in the cups log (with debug on) I 
> found the lines:
> 
> D [28/Mar/2023:18:14:44 +0200] [Job 365] job-name nameWithoutLanguage 365 - 
> https://xxx//xx
> 
> D [28/Mar/2023:18:27:36 +0200] [Job 369] Validate-Job: 
> client-error-request-value-too-long (client-error-request-value-too-long)
> 
> notice how the job name passed to cups ("https://xxx...;) is shorter than 255 
> characters, but when the job number "365 - " is prepended it is longer tnan 
> 255 characters and so overflows.
> 
>* What outcome did you expect instead?
> 
> That my print job be printed rather than just geting stuck in the print queue 
> forever.
> 
> How to reproduce:
> 
>   lp -o 
> 'job-name=https://xxx//xx'

Thank you for your report, John.

I think it would be better if you took this upstream:

  https://github.com/OpenPrinting/cups/issues

Regards,

Brian.

Bug#1033625:

[Brian Potkin]

On Wed 29 Mar 2023 at 11:36:50 +0200, Johan Kröckel wrote:

> root@stockholm:~#  lpstat -l -e
> Kyocera_ECOSYS_M5526cdw network none
> ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/

Printiing should take place with

  lp -d Kyocera_ECOSYS_M5526cdw /etc/nsswitch.conf

Does it?

> root@stockholm:~# driverless
> ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/

A print queue can also be manually set up by

  lpadmin -p M5526cdw -v "ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/" 
-E -m everywhere

Test printing with

  lp -d M5526cdw /etc/nsswitch.conf

Cheers,

Brian.

Bug#1033625: cups constantly without timeout connects to network printer, does not print

[Brian Potkin]

On Tue 28 Mar 2023 at 23:01:47 +0200, Johan Kröckel wrote:

> Package: cups
> Version: 2.4.2-2
> Severity: important
> X-Debbugs-Cc: johan.kroec...@gmail.com
> 
> I am using a Kyocera Ecosys m5526cdw over the network. Printing
> stopped working (worked with this version before).
> 
> Now when I try to start a print job cups ends with a message "Der
> Druckauftrag wurde nicht angenommen.". BUT:
> 
> Now cups connects to the printer (LED on printer lights up as long as
> the pc is on) but nothing is printed. When I reboot, the LED stops to
> blink as long as the system is not completely booted, then the
> connection starts again.
> 
> After running cupsctl --debug-logging, error_log grows by around 30
> megabytes per hour.

Thank you for your report, Johan.

Please provude outputs for

  lpstat -l -e
  lpstat -t
  avahi-browse -rt _ipp._tcp
  avahi-browse -rt _uscan._tcp
  driverless
  lpoptions -p PRINTER_NAME

avahi-browse is in the avahi-utils package.

Regards,

Brian.

Bug#1032954: vboot-kernel-utils: futility manpage references missing info file

[Brian Sammon]

Package: vboot-kernel-utils
Version: 0~R106-15054.B-1
Severity: normal

The manpage for futility refers (at bottom) to texinfo documentation.  I can't 
find the info doc packaged for Debian.
Is it packaged?  Or maybe the reference to the info doc should be removed from 
the manpage.

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.19.1-stb-cbq+ (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 vboot-kernel-utils depends on:
ii  coreboot-utils  4.15~dfsg-3
ii  flashrom1.2-5
ii  libc6   2.36-8
ii  libflashrom11.2-5
ii  libssl3 3.0.8-1

vboot-kernel-utils recommends no packages.

vboot-kernel-utils suggests no packages.

-- no debconf information

Bug#1032464: Acknowledgement (ca-certificates-java post-install script requires bash)

[Brian de Alwis]

I see that the debian/ca-certificates-java.postinst script has already been
fixed to be based on /bin/sh.

https://salsa.debian.org/java-team/ca-certificates-java/-/commit/62313abf3dfc0e760fe0af6edf44b8b958e9a89f

On Tue, Mar 7, 2023 at 9:48 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1032464:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032464.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Java Maintainers 
>
> If you wish to submit further information on this problem, please
> send it to 1032...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1032464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032464
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1032464: ca-certificates-java post-install script requires bash

[Brian de Alwis]

Package: ca-certificates-java
Version: 20190909

ca-certificates-java has an undeclared dependency on bash which leads to
installation failure on systems without bash.

`openjdk-17-jre-headless` fails to install on minimal debian base, such as
gcr.io/gke-release/debian-base:bullseye-v1.4.2-gke.3, due to a failure in
`ca-certificates-java`'s post-install script:

```
# apt-get install --no-install-recommends -y openjdk-17-jre-headless
...
Setting up ca-certificates-java (20190909) ...
dpkg (subprocess): unable to execute installed ca-certificates-java package
post-installation script
(/var/lib/dpkg/info/ca-certificates-java.postinst): No such file or
directory
dpkg: error processing package ca-certificates-java (--configure):
 installed ca-certificates-java package post-installation script subprocess
returned error exit status 2
dpkg: dependency problems prevent configuration of
openjdk-17-jre-headless:amd64:
 openjdk-17-jre-headless:amd64 depends on ca-certificates-java (>=
20190405~); however:
  Package ca-certificates-java is not configured yet.
...
```

The root cause is that
/var/lib/dpkg/info/ca-certificates-java.postinst's shebang specifies
`#!/bin/bash`, but bash is not a declared dependency of the
ca-certificates-java package.

Either the ca-certificates-java package should have a dependency on bash,
or the scripts should be rewritten to not require bash.

Workaround: `apt-get install --no-install-recommends -y bash
openjdk-17-jre-headless`

Bug#1031233: hplip: hp-plugin unable to download plugin

[Brian Potkin]

tags 1031233 upstream
merge 1031233 1029459
severity 103123 important
thanks



On Mon 13 Feb 2023 at 09:20:49 -0800, Curtis Dean Smith wrote:

> Package: hplip
> Version: 3.22.10+dfsg0-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: smit...@hush.com
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> The cups hplip suddenly stopped working and initiated the plugin
>download, which failed.
>  
> 
> -- Package-specific info:
> Saving output in log file: /home/cds/hp-check.log
> 
> HP Linux Imaging and Printing System (ver. 3.22.10)
> Dependency/Version Check Utility ver. 15.1
> 
> Copyright (c) 2001-18 HP Development Company, LP
> This software comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to distribute it
> under certain conditions. See COPYING file for more details.
> 
> Note: hp-check can be run in three modes:
> 1. Compile-time check mode (-c or --compile): Use this mode before compiling 
> the
> HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
> dependencies
> are installed to successfully compile HPLIP.  
>   
> 2. Run-time check mode (-r or --run): Use this mode to determine if a distro  
>   
> supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
>   
> has the proper dependencies installed to successfully run.
>   
> 3. Both compile- and run-time check mode (-b or --both) (Default): This mode  
>   
> will check both of the above cases (both compile- and run-time dependencies). 
>   
> 
> Check types:  
>   
> a. EXTERNALDEP - External Dependencies
>   
> b. GENERALDEP - General Dependencies (required both at compile and run time)  
>   
> c. COMPILEDEP - Compile time Dependencies 
>   
> d. [All are run-time checks]  
>   
> PYEXT SCANCONF QUEUES PERMISSION  
>   
> 
> Status Types:
> OK
> MISSING   - Missing Dependency or Permission or Plug-in
> INCOMPAT  - Incompatible dependency-version or Plugin-version
> 
> Traceback (most recent call last):
>   File "/usr/bin/hp-check", line 860, in 
> dep =  DependenciesCheck(MODE_CHECK,INTERACTIVE_MODE,ui_toolkit)
>^
>   File "/usr/bin/hp-check", line 175, in __init__
> self.core = CoreInstall(mode, ui_mode, ui_toolkit)
> ^^
>   File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
> self.passwordObj = password.Password(ui_mode)
>^^
>   File "/usr/share/hplip/base/password.py", line 94, in __init__
> self.__readAuthType()  # self.__authType
> ^
>   File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
> distro_name = get_distro_std_name(os_name)
>   ^^^^^^^
> NameError: name 'get_distro_std_name' is not defined. Did you mean: 
> 'get_distro_name'?

Thank you for your report, Curtis. This looks like #1029459:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029459

A nice confirmation that something is amiss.

Regards,

Brian.

Bug#858039: lintian: Graph (SVG) files on https://lintian.debian.org/ lack tag name

[Brian Thompson]

I've submitted a PR to get this change in as proposed by Axel:

https://salsa.debian.org/lintian/lintian/-/merge_requests/455
-- 
Sincerely,

Brian


signature.asc
Description: This is a digitally signed message part


publickey - brianrobt@proton.me - 688c834d.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#1007922: false positive spelling: substract and subtract is both correct

[Brian Thompson]

I like the idea of keeping the spelling correction in place.  I've never seen 
"substract" being used.  Keeping the correction reduces ambiguity and keeps 
language consistent.

Motion to close.

Sincerely,

Brian

publickey - brianrobt@pm.me - 0xC8F2EC48.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#695188: 2017 patch review

[Brian Thompson]

Does anyone have time to review the patch that was submitted back in 2017?

2017 patch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=695188;filename=0001-Fix-695188-intelligent-add-of-Bug-XX.patch;msg=60

-- 
Brian Thompson 


signature.asc
Description: This is a digitally signed message part

Bug#1030043: hplip-gui: traceback when launching hp-toolbox

[Brian Potkin]

tags 1029459 upstream
severity 1029459 important
thanks




On Mon 30 Jan 2023 at 17:27:10 +0100, Julien Patriarca wrote:

> Package: hplip-gui
> Version: 3.22.10+dfsg0-1
> Severity: grave
> Tags: patch
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> Trying to launch hp-toolbox software, got this output:
> 
> Traceback (most recent call last):
>   File "/usr/bin/hp-toolbox", line 280, in 
> toolbox = ui.DevMgr5(__version__, device_uri,  None)
>   ^^
>   File "/usr/share/hplip/ui5/devmgr5.py", line 238, in __init__
> core =  CoreInstall(MODE_CHECK)
> ^^^
>   File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
> self.passwordObj = password.Password(ui_mode)
>^^
>   File "/usr/share/hplip/base/password.py", line 94, in __init__
> self.__readAuthType()  # self.__authType
> ^
>   File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
> distro_name = get_distro_std_name(os_name)
>   ^^^
> NameError: name 'get_distro_std_name' is not defined. Did you mean: 
> 'get_distro_name'?
> 
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> I patched the password.py file with the correct function name and 
> delete the os_name parameter when being called.
> 
>* What was the outcome of this action?
> 
> Positive. The hp-toolbox launched succesfully.

Thank you for your report, Julien. This issue does not
appear too dissimilar to #1029459:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029459

Reducing severity because not all hp-* utilities are
affected. hp-wificonfig, for instance.

Regards,

Brian.

Bug#1030084: heimdal: Please provide systemd units

[Brian May]

Chris Hofstaedtler  writes:

> your packages heimdal-kcm and heimdal-kdc currently ship init.d
> scripts and rely on systemd-sysv-generator(8) to integrate with
> systemd, Debians default init.
>
> Please ship systemd unit files instead of relying on the sysv shim.
> When doing so, you could consider taking advantage of new features,
> like sandboxing.
>
> In case upstream does not ship unit files, maybe what Fedora ships
> could serve as a starting point:
> https://src.fedoraproject.org/rpms/heimdal/tree/rawhide>

My time is somewhat restricted at the moment. If somebody wants to
contribute a tested merge request to
https://salsa.debian.org/debian/heimdal to do this, that would be
appreciated :-)
-- 
Brian May 

Bug#1029779: cups: Can't add printers after fresh install.

[Brian Potkin]

tags 1029779 unreproducible
thanks



On Sat 28 Jan 2023 at 13:11:20 +0100, Ignacio Encinas Rubio wrote:

> Yes. Originally root and user had same password. Couldn't login and luckily
> found that old issue, changed root password and then the problem was
> solved.
> 
> I'm unable to reproduce this issue on another Debian machine I have which
> has the same cups package but has been updated more recently.
> 
> Right now I don't have access to the machine that had the problem, but I'll
> try to reproduce the error again on monday changing the password to the old
> one.
> 
> Let me know if there is any other information I could provide that would be
> useful to you.

I used an up-to-date unstable and made the root and user
passwords the same. Logged out and back in. I was able to
complete administrative tasks. Let's see how you go on.

Cheers,

Brian.

Bug#1029779: cups: Can't add printers after fresh install.

[Brian Potkin]

tags 1029779 moreinfo
thanks



On Fri 27 Jan 2023 at 15:53:28 +0100, Ignacio Encinas Rubio wrote:

> Package: cups
> Version: 2.4.2-1+b2
> Severity: important
> X-Debbugs-Cc: iencinasru...@gmail.com
> 
> Dear Maintainer,
> 
> After freshly installing cups I tried adding a printer, but I couldn't
> because login kept failing. Luckily enough after random googling I 
> stumbled upon this GitHub issue (https://github.com/apple/cups/issues/4840).
> 
> I changed the root password, and after that I could login.
> 
> It's the first bug report I ever do, so sorry if the severity field
> results missleading or any other inconvenience. 
> 
> Thank you for your work.


Thank you for your report, Ignacio.

Some clarification, please. Are you saying you origianally
had root and user with identical passwords?

Regards,

Brian.

Bug#1029459: hp-plugin crashes when trying to download plugin with error NameError: name 'get_distro_std_name' is not defined. Did you mean: 'get_distro_name'?

[Brian Potkin]

forwarded 1029459 https://bugs.launchpad.net/hplip/+bug/2003739
thanks




> On Mon, Jan 23 2023 at 04:57:16 PM +00:00:00 +00:00:00, Brian Potkin
>  wrote:

> > My attempt with
> > 
> >   sh -i hplip-3.22.10-plugin.run
> > 
> > failed over an ssh link. This is an upstream issue.
> > get_distro_std_name is not used in hplip-3.22.6.
> > Please report at
> > 
> >   https://bugs.launchpad.net/hplip/+bugs
> > 
> 
> If you are already familiar with launchpad, can you file it?

OK.

> > I would query the severity of grave rather than
> > imortant. Plugin files can be installed with
> > 
> >   sh hplip--plugin.run --tar vxf
> >   python3 installPlugin.py
> > 
> 
> Lowered severity to important. Though we probably have to document it
> somewhere more visible until this is fixed.

Thanks. The technique is not well knwn but it is viable.

Regards,

Brian.

Bug#1029459: hp-plugin crashes when trying to download plugin with error NameError: name 'get_distro_std_name' is not defined. Did you mean: 'get_distro_name'?

[Brian Potkin]

On Mon 23 Jan 2023 at 01:39:46 +0530, Pirate Praveen wrote:

> Package: hplip
> Version: 3.22.10+dfsg0-1
> Severity: grave
> Justification: makes it unusable
> 
> $ hp-plugin
> 
> HP Linux Imaging and Printing System (ver. 3.22.10)
> Plugin Download and Install Utility ver. 2.1
> 
> Copyright (c) 2001-18 HP Development Company, LP
> This software comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to distribute it
> under certain conditions. See COPYING file for more details.
> 
> 
> HP Linux Imaging and Printing System (ver. 3.22.10)
> Plugin Download and Install Utility ver. 2.1
> 
> Copyright (c) 2001-18 HP Development Company, LP
> This software comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to distribute it
> under certain conditions. See COPYING file for more details.
> 
> QSocketNotifier: Can only be used with threads started with QThread
> Checking for network connection...
> Downloading plug-in from:
> Traceback (most recent call last):
>   File "/usr/share/hplip/ui5/plugindialog.py", line 248, in
> NextButton_clicked
> status, download_plugin_file, error_str =
> self.pluginObj.download(self.plugin_path,self.plugin_download_callback)
> 
> ^^^
>   File "/usr/share/hplip/installer/pluginhandler.py", line 257, in download
> core = core_install.CoreInstall()
>^^
>   File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
> self.passwordObj = password.Password(ui_mode)
>^^
>   File "/usr/share/hplip/base/password.py", line 94, in __init__
> self.__readAuthType()  # self.__authType
> ^
>   File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
> distro_name = get_distro_std_name(os_name)
>   ^^^
> NameError: name 'get_distro_std_name' is not defined. Did you mean:
> 'get_distro_name'?
> Aborted

Thank you for you report, Pirate Praveen.

My attempt with

  sh -i hplip-3.22.10-plugin.run

failed over an ssh link. This is an upstream issue.
get_distro_std_name is not used in hplip-3.22.6.
Please report at

  https://bugs.launchpad.net/hplip/+bugs

I would query the severity of grave rather than
imortant. Plugin files can be installed with

  sh hplip--plugin.run --tar vxf
  python3 installPlugin.py

Regards,

Brian.

  
 

Bug#1029226: [Pkg-xmpp-devel] Bug#1029226: gajim: Crashes at startup: "No translations found for en_US"

[Brian Vaughan]

$ pdb3 /usr/bin/gajim
> /usr/bin/gajim(3)()
-> import re
(Pdb) cont
No translations found for en_US
Dirs searched: [PosixPath('/home/brian/.local/share'), 
PosixPath('/usr/share/xfce4'), PosixPath('/usr/local/share'), 
PosixPath('/usr/share'), PosixPath('/usr/share')]

No plugin translation path available
Segmentation fault

On 1/19/23 20:17, Brian Vaughan wrote:

$ gajim -v
No translations found for en_US
Dirs searched: [PosixPath('/home/brian/.local/share'), 
PosixPath('/usr/share/xfce4'), PosixPath('/usr/local/share'), 
PosixPath('/usr/share'), PosixPath('/usr/share')]

No plugin translation path available
Logger gajim level set to 10
Logger nbxmpp level set to 20
01/19/2023 20:13:08 (I) gajim  Gajim Version: 1.6.1
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
01/19/2023 20:13:08 (I) gajim  English (en) dict 
available
01/19/2023 20:13:08 (I) gajim  English (Australia) 
(en_AU) dict available
01/19/2023 20:13:08 (I) gajim  English (Canada) 
(en_CA) dict available
01/19/2023 20:13:08 (I) gajim  English (United 
Kingdom) (en_GB) dict available
01/19/2023 20:13:08 (I) gajim  English (United 
States) (en_US) dict available

01/19/2023 20:13:08 (I) gajim  FARSTREAM True
01/19/2023 20:13:08 (I) gajim  GST True
01/19/2023 20:13:08 (I) gajim  AV True
01/19/2023 20:13:08 (I) gajim  GEOCLUE True
01/19/2023 20:13:08 (I) gajim  UPNP False
01/19/2023 20:13:08 (I) gajim  GSOUND True
01/19/2023 20:13:08 (I) gajim  GSPELL True
01/19/2023 20:13:08 (I) gajim  IDLE True
01/19/2023 20:13:08 (I) gajim  APPINDICATOR False
01/19/2023 20:13:08 (I) gajim AYATANA_APPINDICATOR True
01/19/2023 20:13:08 (I) gajim  SENTRY_SDK True
01/19/2023 20:13:08 (I) gajim  Used language: en_US
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.libsecret.Keyring (priority: 4.8)
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.SecretService.Keyring (priority: 5)
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.fail.Keyring (priority: 0)
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.chainer.ChainerBackend (priority: 10)
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.kwallet.DBusKeyring (priority: 4.9)
01/19/2023 20:13:08 (I) gajim.c.passwords  Select 
keyring.backends.chainer.ChainerBackend (priority: 10) backend

01/19/2023 20:13:08 (I) gajim.c.settings   Load app settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load soundevents 
settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load status_presets 
settings

01/19/2023 20:13:08 (I) gajim.c.settings   Load proxies settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load plugins settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load workspaces 
settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: xmpp.earth
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: conversations.im
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: jabber.ccc.de
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: jabber.org
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: lightwitch.org

01/19/2023 20:13:08 (I) gajim.c.settings   Commit
01/19/2023 20:13:08 (I) gajim.c.storage.cache  Connect to 
/home/brian/.cache/gajim/cache.db
01/19/2023 20:13:08 (I) gajim.c.storage.cache  1 DiscoInfo entries 
loaded
01/19/2023 20:13:08 (D) gajim.c.storage.cache  Execution time for 
_fill_disco_info_cache: 18 ms
01/19/2023 20:13:08 (D) gajim.c.storage.cache  Execution time for 
_clean_caps_table: 1 ms
01/19/2023 20:13:08 (D) gajim.c.storage.cache  Execution time for 
_load_caps_data: 1 ms

01/19/2023 20:13:08 (I) gajim.c.storage.events Creating in memory
01/19/2023 20:13:08 (I) gajim.c.storage.events Connect to None
01/19/2023 20:13:08 (I) gajim.c.storage.archive    Connect to 
/home/brian/.local/share/gajim/logs.db
01/19/2023 20:13:08 (D) gajim.c.storage.archive    Execution time for 
_get_jid_ids_from_db: 1 ms

01/19/2023 20:13:08 (I) gajim.c.cert_store 0 Certificates loaded
01/19/2023 20:13:08 (I) gajim.client   Create new nbxmpp 
client
01/19/2023 20:13:08 (I) gajim.c.settings   Set account 
settings: xmpp.earth
01/19/2023 20:13:08 (I) gajim.c.settings   Signal: re

Bug#1029226: [Pkg-xmpp-devel] Bug#1029226: gajim: Crashes at startup: "No translations found for en_US"

[Brian Vaughan]

$ gajim -v
No translations found for en_US
Dirs searched: [PosixPath('/home/brian/.local/share'), 
PosixPath('/usr/share/xfce4'), PosixPath('/usr/local/share'), 
PosixPath('/usr/share'), PosixPath('/usr/share')]

No plugin translation path available
Logger gajim level set to 10
Logger nbxmpp level set to 20
01/19/2023 20:13:08 (I) gajim  Gajim Version: 1.6.1
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
01/19/2023 20:13:08 (I) gajim  English (en) dict 
available
01/19/2023 20:13:08 (I) gajim  English (Australia) 
(en_AU) dict available
01/19/2023 20:13:08 (I) gajim  English (Canada) 
(en_CA) dict available
01/19/2023 20:13:08 (I) gajim  English (United 
Kingdom) (en_GB) dict available
01/19/2023 20:13:08 (I) gajim  English (United 
States) (en_US) dict available

01/19/2023 20:13:08 (I) gajim  FARSTREAM True
01/19/2023 20:13:08 (I) gajim  GST True
01/19/2023 20:13:08 (I) gajim  AV True
01/19/2023 20:13:08 (I) gajim  GEOCLUE True
01/19/2023 20:13:08 (I) gajim  UPNP False
01/19/2023 20:13:08 (I) gajim  GSOUND True
01/19/2023 20:13:08 (I) gajim  GSPELL True
01/19/2023 20:13:08 (I) gajim  IDLE True
01/19/2023 20:13:08 (I) gajim  APPINDICATOR False
01/19/2023 20:13:08 (I) gajim AYATANA_APPINDICATOR True
01/19/2023 20:13:08 (I) gajim  SENTRY_SDK True
01/19/2023 20:13:08 (I) gajim  Used language: en_US
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.libsecret.Keyring (priority: 4.8)
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.SecretService.Keyring (priority: 5)
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.fail.Keyring (priority: 0)
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.chainer.ChainerBackend (priority: 10)
01/19/2023 20:13:08 (I) gajim.c.passwords  Found keyring 
backend: keyring.backends.kwallet.DBusKeyring (priority: 4.9)
01/19/2023 20:13:08 (I) gajim.c.passwords  Select 
keyring.backends.chainer.ChainerBackend (priority: 10) backend

01/19/2023 20:13:08 (I) gajim.c.settings   Load app settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load soundevents settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load status_presets 
settings

01/19/2023 20:13:08 (I) gajim.c.settings   Load proxies settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load plugins settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load workspaces settings
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: xmpp.earth
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: conversations.im
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: jabber.ccc.de
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: jabber.org
01/19/2023 20:13:08 (I) gajim.c.settings   Load account 
settings: lightwitch.org

01/19/2023 20:13:08 (I) gajim.c.settings   Commit
01/19/2023 20:13:08 (I) gajim.c.storage.cache  Connect to 
/home/brian/.cache/gajim/cache.db
01/19/2023 20:13:08 (I) gajim.c.storage.cache  1 DiscoInfo entries 
loaded
01/19/2023 20:13:08 (D) gajim.c.storage.cache  Execution time for 
_fill_disco_info_cache: 18 ms
01/19/2023 20:13:08 (D) gajim.c.storage.cache  Execution time for 
_clean_caps_table: 1 ms
01/19/2023 20:13:08 (D) gajim.c.storage.cache  Execution time for 
_load_caps_data: 1 ms

01/19/2023 20:13:08 (I) gajim.c.storage.events Creating in memory
01/19/2023 20:13:08 (I) gajim.c.storage.events Connect to None
01/19/2023 20:13:08 (I) gajim.c.storage.archive    Connect to 
/home/brian/.local/share/gajim/logs.db
01/19/2023 20:13:08 (D) gajim.c.storage.archive    Execution time for 
_get_jid_ids_from_db: 1 ms

01/19/2023 20:13:08 (I) gajim.c.cert_store 0 Certificates loaded
01/19/2023 20:13:08 (I) gajim.client   Create new nbxmpp client
01/19/2023 20:13:08 (I) gajim.c.settings   Set account settings: 
xmpp.earth

01/19/2023 20:13:08 (I) gajim.c.settings   Signal: resource changed
01/19/2023 20:13:08 (I) gajim.c.passwords  Request password from 
keyring
01/19/2023 20:13:08 (I) gajim.c.settings   Set account settings: 
xmpp.earth

01/19/2023 20:13:08 (I) gajim.c.settings   Signal: password changed
01/19/2023 20:13:09 (I) gajim.client   Create new nbxmpp client
01/19/2023 20:13:09 (I) gajim.c.settings

Bug#1029226: gajim: Crashes at startup: "No translations found for en_US"

[Brian Vaughan]

Package: gajim
Version: 1.6.1-2
Severity: important
X-Debbugs-Cc: bgvaug...@gmail.com

Dear Maintainer,

On starting gajim through the applications menu, the interface appears briefly
before disappearing.

On starting gajim from the command line, an error message appears on the
terminal, then the application interface appears briefly before disappearing.

No translations found for en_US
Dirs searched: [PosixPath('/home/brian/.local/share'),
PosixPath('/usr/share/xfce4'), PosixPath('/usr/local/share'),
PosixPath('/usr/share'), PosixPath('/usr/share')]
No plugin translation path available
Aborted


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

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

Versions of packages gajim depends on:
ii  desktop-file-utils   0.26-1
ii  gir1.2-gst-plugins-base-1.0  1.20.5-1
ii  gir1.2-gtk-3.0   3.24.36-1
ii  gir1.2-gtksource-4   4.8.4-4
ii  python3  3.11.1-1
ii  python3-cairo1.20.1-5
ii  python3-cryptography 38.0.4-2
ii  python3-css-parser   1.0.8-1
ii  python3-gi   3.42.2-3
ii  python3-gi-cairo 3.42.2-3
ii  python3-idna 3.3-1
ii  python3-keyring  23.9.3-2
ii  python3-nbxmpp   4.0.1-1
ii  python3-packaging23.0-1
ii  python3-pil  9.4.0-1+b1
ii  python3-precis-i18n  1.0.5-1

Versions of packages gajim recommends:
ii  alsa-utils   1.2.8-1
ii  aspell-en [aspell-dictionary]2018.04.16-0-1
ii  ca-certificates  20211016
ii  dbus 1.14.4-1
ii  fonts-noto-color-emoji   2.038-1
ii  gajim-omemo  2.9.0-1
ii  gajim-openpgp1.5.0-1
ii  gir1.2-farstream-0.2 0.2.9-1
ii  gir1.2-geoclue-2.0   2.6.0-2
ii  gir1.2-gsound-1.01.0.3-2
ii  gir1.2-gspell-1  1.12.0-1+b1
ii  gir1.2-gstreamer-1.0 1.20.5-1
ii  gir1.2-gupnpigd-1.0  1.2.0-3
ii  gir1.2-secret-1  0.20.5-3
ii  gstreamer1.0-gl  1.20.5-1
ii  gstreamer1.0-nice0.1.18-2
ii  gstreamer1.0-plugins-ugly1.20.5-1
ii  notification-daemon  3.20.0-4+b1
ii  pulseaudio-utils 16.1+dfsg1-2+b1
ii  python3-dbus 1.3.2-4
ii  python3-gssapi   1.8.2-1
ii  python3-sentry-sdk   1.9.10-2
ii  xfce4-notifyd [notification-daemon]  0.6.5-1

Versions of packages gajim suggests:
ii  libxss1  1:1.2.3-1
pn  nautilus-sendto  

-- no debconf information

Bug#1028158: atril: prints messages to the console

[brian m. carlson]

Package: atril
Version: 1.26.0-2
Severity: normal

I typically compose letters, documents, and other things I turn into
PDFs with a text editor and convert them at the terminal using Make.
Once I've converted them to a PDF, I then open them using "atril
FILE-NAME &" from the shell so I can view them while I continue to work
on them using the command line.

However, atril prints a message like the following when I do so:

  (atril:454002): EggSMClient-WARNING **: 21:15:31.545: Failed to connect to 
the session manager: Could not open network socket

Such messages are unwanted because they clutter up my terminal and
interfere with the prompt and other running programs.  I've in the past
asked GTK+ and its appurtenant libraries to avoid printing
non-user-caused warnings to the console by default, but they've chosen
not to, instead preferring to have individual programs address these
issues, so I'm filing a bug report here.

Note that I am running MATE and have mate-session running, and my
sessions are correctly saved with the session manager, so I believe the
message to be generally in error.  In any event, Atril is fully
functional (and I'm otherwise happy with the way it works), so I don't
think a diagnostic is needed here.

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

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

Versions of packages atril depends on:
ii  atril-common 1.26.0-2
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  libatk1.0-0  2.46.0-4
ii  libatrildocument31.26.0-2
ii  libatrilview31.26.0-2
ii  libc62.36-7
ii  libcaja-extension1   1.26.1-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.4-1
ii  libgtk-3-0   3.24.35-3
ii  libice6  2:1.0.10-1
ii  libsecret-1-00.20.5-3
ii  libsm6   2:1.2.3-1
ii  libxml2  2.9.14+dfsg-1.1+b2
ii  shared-mime-info 2.2-1

Versions of packages atril recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.14.4-1
ii  dbus-x11 [dbus-session-bus]   1.14.4-1
ii  gvfs  1.50.2-2

Versions of packages atril suggests:
ii  caja  1.26.1-1
ii  poppler-data  0.4.11-1
pn  unrar 

-- no debconf information

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1026006: heimdal FTCBFS: multiple reasons

[Brian May]

Helmut Grohne  writes:

> Maybe you could later try converting it to dh_auto_configure? Doing so
> would significantly simplify the invocation:
>  * debhelper automatically passes --disable-slient-rules unless
>DEB_BUILD_OPTIONS contains "terse".
>  * debhelper automatically passes --prefix, --includedir, --infodir and
> --libdir.
>  * And of course --build and --host.

Patches welcome :-)

I assume something like the following?

override_dh_auto_configure:
dh_auto_configure -- \
  --with-openldap=/usr \
  --with-sqlite3=/usr \
  --with-libedit=/usr \
  --enable-kcm \
  --with-hdbdir=/var/lib/heimdal-kdc \
  --without-openssl \
  --without-krb4

-- 
Brian May 

Bug#1026006: heimdal FTCBFS: multiple reasons

[Brian May]

Helmut Grohne  writes:

> Is there a significant advantage over "apt-get build-dep -y ./"?

I wasn't aware that apt-get build-dep could now use a local source
directory. Thanks, will try that,
-- 
Brian May 

Bug#1026006: heimdal FTCBFS: multiple reasons

[Brian May]

Helmut Grohne  writes:

>> When I tried to build this with my build system I get:
>> 
>> $ apt-get-build-depends --yes
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> E: Unable to locate package heimdal-multidev-bin
>> E: Unable to locate package 
>> 
>> Is "heimdal-multidev-bin ," correct syntax? If so, maybe
>> apt-get-build-depends doesn't support it.
>
> The problem is not with the syntax, but with the package. Look closely
> which package provides it. It comes from heimdal itself and is added by
> my patch. So you first need to perform a native build and then once that
> native build is accessible, you can perform a cross build.

Hmmm. Not entirely convinced here. If you look at the messages, it is
clearly trying to locate a package called "" in addition to the
correct package name.
-- 
Brian May 

Bug#1026006: heimdal FTCBFS: multiple reasons

[Brian May]

Helmut Grohne  writes:


> Note that python3 is used
> as a code generator, so rather than a host architecture python3 a build
> architecture python3 is needed. To achieve that, it should be annotated
> :native or :any.

Sounds reasonable.

> Once that has changed, one can actually attempt a cross build. That
> attempt quickly ends due to not finding ncurses, because it didn't do
> a cross build. The relevant --build and --host flags are missing from
> configure. Is there a reason for not using dh_auto_configure?

No idea now, sorry. I think this stuff was contributed by others.
Probably legacy reasons now.

> It would automatically pass them as needed. Once
> added, the build progresses quite far until it fails finding
> asn1_compile. The build system is clever enough to recognize that it
> cannot run the built asn1_compile and tries running the system copy
> instead, which isn't there. Unfortunately, asn1_compile does not reside
> in a Multi-Arch: foreign package and thus is not readily available. I
> propose splitting it out of heimdal-multidev into a heimdal-multidev-bin
> package that contains architecture-independent tools. Once done, we can
> depend on it (for cross compilation only to avoid a recursive
> depdendency in native builds). Are you ok with such a split? We have
> quite some prior art for this if you look for other packages matching
> the pattern "*-bin", especially in the qt/kde ecosystem. I'm attaching a
> patch for your convenience.

When I tried to build this with my build system I get:

$ apt-get-build-depends --yes
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package heimdal-multidev-bin
E: Unable to locate package 

Is "heimdal-multidev-bin ," correct syntax? If so, maybe
apt-get-build-depends doesn't support it.
-- 
Brian May 

Bug#1022974: hplip: Needs sudo but does not depend on it

[Brian Potkin]

tags 1022974 moreinfo
thanks



On Fri 28 Oct 2022 at 19:11:36 +0300, Teemu Ikonen wrote:

> Package: hplip
> Version: 3.22.6+dfsg0-1
> Severity: normal
> X-Debbugs-Cc: tpiko...@gmail.com
> 
> When installing the non-free plugin with hp-plugin, the installer
> authenticates using 'sudo'. If sudo is not installed, the password
> prompt always reports an invalid password error.
> 
> hplip package should depend on sudo. Bonus points for checking that the
> sudo configuration works before starting the installation.

Thank you for your report, Teemu. Please inicate whether Debian was
installed with or without a root account.

Regards,
Brian.

Bug#1023764: Bug 1023764

[Brian Haley]

This change has merged:

https://review.opendev.org/c/x/networking-l2gw/+/866620

If you want to try and build again.

Bug#1023764: Bug 1023764

[Brian Haley]

It looks like the problem is that networking-l2gw is requiring a version 
of neutron that doesn't have this method. I've pushed a change that 
might solve the issue:


https://review.opendev.org/c/x/networking-l2gw/+/866620

Unless it's easier to just dump this in a package file?

Bug#1023871: automake: Missing amhello-1.0.tar.gz

[Brian Flaherty]

Package: automake
Version: 1:1.16.5-1.3
Severity: minor
X-Debbugs-Cc: b...@yahoo.com

Dear Maintainer,

   * What led up to the situation?
   
I was reading the info for automake. Section 2.2 references amhello-1.0.tar.gz 
in PREFIX/share/doc/automake. It was not there.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 
I found it on a webpage and shall create the files myself.
   https://www.gnu.org/software/automake/manual/html_node/Creating-amhello.html

   * What outcome did you expect instead?

I expected the file to be where the documentation said it should be.

Thank you.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages automake depends on:
ii  autoconf   2.71-2
ii  autotools-dev  20220109.1

automake recommends no packages.

Versions of packages automake suggests:
ii  autoconf-doc   2.71-2
ii  gnu-standards  2022.03.23-0.1

-- no debconf information

Bug#1023778: TMPDIR behaviour in maintainer scripts [was: Re: Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir]

[brian m. carlson]

On 2022-11-10 at 16:37:53, Tollef Fog Heen wrote:
> ]] Robie Basak 
> 
> > But are you in essence saying that libpam-tmpdir requires that *every
> > maintainer script* that runs things as non-root, or starts processes
> > that do that, unset TMPDIR first?
> 
> I think it's more wide than that: If you change UID, you need to
> sanitise the environment.  Your HOME is likely to be wrong.  PATH might
> very well be pointing at directories which are not appropriate for the
> user you're changing the UID to, etc.

I believe this is the best practice.  For example, sudo typically passes
through only a handful of environment variables, such as TERM, to avoid
things like insecure PATH entries.  For example, if MySQL invoked a
binary in PATH and I had a custom script named the same thing that had
insecure behaviour when invoked as another user, that would be bad.
OpenSSH also sanitizes the environment passed over the connection.

Without getting into a debate about systemd, this is one the pieces of
functionality it provides, since it runs binaries in a clean
environment.  You can probably get most of that in a sysvinit script by
using `env -i` with a handful of environment variables specifically
overridden if necessary.  Then it would be very obvious what
dependencies the binary had on the outside environment.

> > I think the answer to this should probably be established by the
> > libpam-tmpdir maintainer and documented first, for fear of someone else
> > later coming along and saying that the maintainer script incorrectly
> > ignores TMPDIR because we started ignoring it to resolve this bug. So I
> > copied debian-devel@ for comment.
> 
> I'm not sure this is libpam-tmpdir specific, but rather a bit more
> general: what are the expectations that maintainer scripts can have
> about the environment they're running in, and how do we make those
> expectations hold?  This should probably then be documented in policy.

I agree documentation here is helpful.  For reference, this was an
invocation from `sudo aptitude` as part of a normal package upgrade,
which I think is a relatively common situation to be in.

Possibly also an initscript helper which enables developers to do the
right thing automatically, or a flag to start-stop-daemon, or other
tooling would be beneficial to help people easily solve this problem
without thinking too much about it.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1023778: mysql-server-8.0: fails to restart on upgrade with libpam-tmpdir

[brian m. carlson]

f8  

Versions of packages mysql-server-8.0 suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20220412cvs-1
pn  tinyca 

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1020957: RFP: gcadapter-oc-kmod -- Kernel module for overclocking the Nintendo Wii U/Mayflash GameCube adapter.

[Brian Smith]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: 51vd21...@mozmail.com

* Package name: gcadapter-oc-kmod
  Version : 1.4
  Upstream Author : Hannes Mann 
* URL : https://github.com/HannesMann/gcadapter-oc-kmod
* License : GPL
  Programming Lang: C
  Description : Kernel module for overclocking the Nintendo Wii U/Mayflash 
GameCube adapter.

Bug#1020442: heimdal breaks openldap autopkgtest: test smbk5pwd

[Brian May]

On Wed, Sep 21, 2022 at 09:30:23PM +0200, Paul Gevers wrote:
> Currently this regression is blocking the migration of heimdal to testing
> [1]. Due to the nature of this issue, I filed this bug report against both
> packages. Can you please investigate the situation and reassign the bug to
> the right package?

The only recent changes to Heimdal have been minor changes to the
packaging. Plus a change to the rpath in krb5-config.heimdal which
doesn't look relevant.

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openldap/26275057/log.gz

As a result, I am inclined to believe this is an openldap issue.
-- 
Brian May 

Bug#1019593: hp-plugin: Failure to download plugin

[Brian Potkin]

On Wed 14 Sep 2022 at 21:04:41 +0200, martin f krafft wrote:

> Thanks Brian for your quick response. Yeah, it's cool that I can use 
> the printer for driverless printing, but unfortunately, the scanning 
> functionality still requires the plugin.

On unstable libsane1 installs the recommended sane-airscan. This
gives driverless scanning, which is supported by your deice. Color
me perplexed! Please give

 scanimage -L
 airscan-discover

> It is also true that the issue seems to be in code downloaded 
> on-the-fly from upstream, so you're right in closing the bug.

Coincidentally; another two reports:

 https://bugs.launchpad.net/hplip/+bug/1989508
 https://bugs.launchpad.net/hplip/+bug/1989592

Cheers,

Brian.

Bug#1012026: Confirming #1012026 on Debian sid

[brian m. carlson]

I can confirm this bug using an Intel Alder Lake-P Integrated Graphics
Controller as well (on a ThinkPad X1 Carbon Gen 10).

The backtrace looks like this:

  [317658.882] (EE) Backtrace:
  [317658.882] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x5600e5903bf9]
  [317658.883] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x40) 
[0x7fdf7b847af0]
  [317658.883] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(pthread_key_delete+0x15c) [0x7fdf7b89383c]
  [317658.883] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (raise+0x12) 
[0x7fdf7b847a52]
  [317658.883] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0xcf) 
[0x7fdf7b832469]
  [317658.883] (EE) unw_get_proc_name failed: no unwind info found [-10]
  [317658.883] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7fdf7b832395]
  [317658.883] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x42) 
[0x7fdf7b840b02]
  [317658.883] (EE) 7: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc33) 
[0x5600e58bc113]
  [317658.884] (EE) 8: /usr/lib/xorg/Xorg (DRI2Authenticate+0xad) 
[0x5600e58be3ad]
  [317658.884] (EE) 9: /usr/lib/xorg/Xorg (DRI2GetParam+0x6cb) [0x5600e58bf12b]
  [317658.884] (EE) 10: /usr/lib/xorg/Xorg (SendErrorToClient+0x3d4) 
[0x5600e5790724]
  [317658.884] (EE) 11: /usr/lib/xorg/Xorg (InitFonts+0x3bc) [0x5600e57946bc]
  [317658.884] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_init_first+0x8a) [0x7fdf7b83320a]
  [317658.884] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0x7c) [0x7fdf7b8332bc]
  [317658.884] (EE) 14: /usr/lib/xorg/Xorg (_start+0x2a) [0x5600e577db6a]
  [317658.884] (EE)
  [317658.884] (EE)
  Fatal server error:
  [317658.884] (EE) Caught signal 6 (Aborted). Server aborting
  [317658.884] (EE)
  [317658.884] (EE)

I can reliably reproduce it by invoking picard from the package of the
same name under MATE.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1015044: Not a setuptools-scm issue?

[Brian May]

On Wed, Aug 03, 2022 at 12:22:32PM +0200, julien.pu...@gmail.com wrote:
> I'm sorry, but I don't see why you think this is a problem with
> setuptools-scm.
> 
> sshuttle's debian/rules asks setuptools-scm to generate a version file
> in its clean target. So setuptools-scm does so, and it doesn't look
> invalid.
> 
> But it doesn't not correspond to the version file as shipped, so dpkg
> protests that the source tree has been modified.

Please make sure you CC responses to me. Otherwise I won't get them.

At first glance I thought this was invalid Python code, but oh wait, I
think this is valid. Problem when dealing with too many languages.

__version__ = version = '1.1.0'
__version_tuple__ = version_tuple = (1, 1, 0)

But what seems to be the problem here is that setuptools-scm has
silently changed how it generates this file. Which breaks Debian
packages.

If you don't agree with me, then assign this bug back to sshuttle and I
will deal with it. In fact latest upstream sshuttle removes
setuptools-scm support anyway.
-- 
Brian May 

Bug#1015044: Reassign to sshuttle from setuptools-scm

[Brian May]

On Sat, Aug 06, 2022 at 03:57:47PM +0200, julien.pu...@gmail.com wrote:
> reassign 1015044 sshutle 1.0.1-1

errr, typo here in the package name.
-- 
Brian May 

Bug#964008: heimdal-kdc: kadmind unusable in default configuration, looks for m-key in the wrong path

[Brian May]

> Debian places the key in /var/lib/heimdal-kdc/heimdal.mkey, and the
> comments in /etc/heimdal-kdc/kdc.conf state that this is the default
> location. Adding the path explicitly in the config file had no effect,
> so I suspect kadmind has the path hardcoded somewhere.


See #868638, where it was found that we had to use
/var/lib/heimdal-kdc/heimdal.mkey not /var/lib/heimdal-kdc/m-key

I am guessing that the default must have changed somewhere.
-- 
Brian May 

Bug#519666: Heimdal with Samba - sambaPwdMustChange is depreciated

[Brian May]

On Sat, Mar 14, 2009 at 05:35:55AM -0300, Eduardo Sachs wrote:
> When using Heimdal with Samba, the Heimdal beginning to use the attribute
> sambaPwdMustChange, however, the sambaPwdMustChange changed to 
> sambaPwdLastSet, 
> in Samba 3.2.x and 3.3.x.
> 
> I find the code in heimdal-1.2.dfsg.1/lib/hdb/hdb-ldap.c.
> 
> Its now calculated dynamically. sambaPwdLastSet + sambaMaxPwdAge

This was forwarded upstream, but probably lost many years ago.

Do we need to open a new upstream bug report?
-- 
Brian May 

Bug#579573: no longer gets forwardable tickets

[Brian May]

On Sat, Jul 03, 2010 at 01:23:36PM +0200, Per Olofsson wrote:
> This bug still exists in the latest version.

Over 10 years later, is this still an issue?

If so we need to create a new upstream report.

If not we need to close this bug report.
-- 
Brian May 

Bug#574774: Bisected problem commit

[Brian May]

On Thu, Aug 04, 2011 at 12:29:30PM -0400, Chris Chiappa wrote:
> I tracked the problem down to this commit:
> 
> commit 6df0783c7eef0984b712792a25dd2f5a39f8f337
> Author: Love Hornquist Astrand 
> Date:   Wed Sep 23 00:14:57 2009 -0700
> 
> Redo client key handling for AS
> 
> Pick the replykey to be the same as the preauth key, this allows
> us to delay the picking of client key to when its needed, this
> means that we can have a reply keys for PKINIT that is independant
> of what keys the client have.
> 
> The attached dif (which is probably totally wrong and shouldn't be
> applied anywhere outside of a test instance) to Heimdal 1.5 makes the
> kdc work again with no error.

Over 10 years later, anyone know if this is still an issue?

If no response, will assume fixed and close this bug report.

Otherwise we should open a new upstream bug report.
-- 
Brian May 

Bug#761933: Using libroken through heimdal-multidev

[Brian May]

On Sat, Apr 25, 2015 at 04:23:14PM +, Jelmer Vernooij wrote:
> I think a separate pkg-config file for libroken would be reasonable.
> Ideally this would be upstream rather than Debian-specific. Let's take
> this to the upstream bug tracker.

Splitting up libroken into a shared package would probably be good.

But I don't see this happening anytime spoon. There simply isn't anyone
willing to do the work. Plus there has to be people willing to use it if
the work was done, not convinced that will happen either.

As this is outside the scope of what I can do as a package maintainer I
have tagged this "wontfix".
-- 
Brian May