Bug#1079107: Reported upstream

[Akshay S Dinesh]

Have filed upstream issue here:
https://github.com/santhoshtr/sfst/issues/31

Bug#1078727: python3-notify2: outdated package causes errors in syslog

[Colin S]

Package: python3-notify2
Version: 0.3-5
Severity: normal

Dear Maintainer,

The outdated version of python3-notify2 packaged by Debian causes
errors to be raised when unrelated notification messages are seen
on DBus. This bug was fixed in notify2 0.3.1.

Notably this causes a problem with the opensnitch-ui package
 where it
spams the syslog with these errors.

Would you kindly update this package to the latest upstream
release?

Thank you,

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.10-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-notify2 depends on:
ii  python3   3.12.4-1
ii  python3-dbus  1.3.2-5+b3

Versions of packages python3-notify2 recommends:
ii  plasma-workspace [notification-daemon]  4:5.27.11.1-1+b1

python3-notify2 suggests no packages.

-- no debconf information

Bug#991815: Took over sfst package to Debian Science team maintenance

[Akshay S Dinesh]

> as permission to take over in Debian Science team and preserved your ID
> as "Uploaders".  If you might need push permissions in Science team
> just let me know.  I'd recommend you remove your local and now outdated
> repository.

This is absolutely great. Thanks a lot!

> (Admittedly I did not stripped the very
> simple, obviously LaTeX-generated PDFs and hope these are not considered
> "binary without source" in a copyright review.  If I might be wrong here
> we get some extra time in fixing this.)
>

I've asked the present upstream maintainer Santhosh Thottingal about the source 
for these. Will follow up on https://github.com/santhoshtr/sfst/issues/27

Thanks again for this great work and thanks science team for adopting.

Akshay

Bug#1072274: ITP: fcitx5-varnam -- Fcitx5 wrapper for Varnam input method.

[Anoop M S]

Hi,

On 18/07/24 23:41, Boyuan Yang wrote:

在 2024-07-18星期四的 22:00 +0530，Anoop M S写道：

Hi,
On Mon, 15 Jul 2024 00:43:38 +0530 Anoop M S  wrote:
  > Hi,
  > On Sun, 14 Jul 2024 14:44:59 -0400 Boyuan Yang  wrote:
  > > Hi,
  > >
  > > 在 2024-07-14星期日的 20:59 +0530，Anoop M S写道：
  > > > On Fri, 31 May 2024 10:48:21 -0400 Boyuan Yang 
  > wrote:
  > > >  > Hi,
  > > >  >
  > > >  > 在 2024-05-31星期五的 08:19 +，Anoop M S写道：
  > > >  > > Package: wnpp
  > > >  > > Severity: wishlist
  > > >  > > Owner: Anoop M S 
  > > >  > > X-Debbugs-Cc: debian-de...@lists.debian.org,
anoo...@disroot.org
  > > >  > >
  > > >  > > * Package name    : fcitx5-varnam
  > > >  > >   Version : 0.0.1
  > > >  > >   Upstream Contact: Anoop M S 
  > > >  > > * URL :
https://github.com/varnamproject/varnam-fcitx5
  > > >  > > * License : GPL
  > > >  > >   Programming Lang: C++
  > > >  > >   Description : Fcitx5 wrapper for Varnam input method.
  > > >  > >
  > > >  > > Fcitx5 wrapper for Varnam(https://www.varnamproject.com) Input
  > > > Method Engine.
  > > >  > > Easily type Indian languages on Linux desktops.
  > > >  > >
  > > >  > > I would like to join Debian Input Method Team, and package and
  > > > maintain it.
  > > >  > > And I would need a sponsor to upload it as well.
  > > >  >
  > > >  > Please prepare an initial version first. You can host it on your
  > own
  > > > Salsa git repo
  > > >  > or via mentors.debian.net , or choose whichever platform that is
  > more
  > > > convenient to you.
  > > >  > Please submit a regular RFS request and notify me once you are
  > prepared.
  > > >  >
  > > >  > If it looks good, I can help to move your git packaging repo
to the
  > > > Salsa Input Method
  > > >  > Team namespace, sponsor the upload and add you into the Salsa
Input
  > > > Method Team group.
  > > >  >
  > > >  > Thanks,
  > > >  > Boyuan Yang
  > > >
  > > > I've prepared an initial release and sent RFS (#1076334).
  > > >
  > > > Kindly review at your convenience.
  > >
  > > The following issues are critical and must be fixed:
  > >
  > > *
  >
https://github.com/varnamproject/varnam-fcitx5/blob/a2c9412461f68a5293cec24609076951e28a3b27/meson.build#L11-L29
  > > is unacceptable. The build system is only targeting on x86_64 (amd64)
  > architecture, which is
  > > not reasonable since Debian and Fedora both support multiple hardware
  > architectures.

I've addressed the raised issues in the upstream. And made few changes
in the package as well (haven't pushed the code yet).
Lintian currently showing following issues
* newer-standards-version 4.7.0
* debian-watch-does-not-check-openpgp-signature
* prefer-uscan-symlink

full text : https://paste.debian.net/plain/1323647

Are these ignorable? And is there anything else I need to follow to do
the version update
   or can I create a fresh setup with only the new version?

They are of low priority and you can revisit them later. If you would like,
you can try to solve them following the text description you just saw
in that terminal output.

Please prepare a fresh setup with updated source code and version numbers so
that Debian Developers can review.

Thanks,
Boyuan Yang
I've pushed the latest setup to 
https://salsa.debian.org/anoop/fcitx5-varnam.

Kindly review at your convenience.

Thanks,
Anoop




OpenPGP_0xDC6CE985B8F95651.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1072274: ITP: fcitx5-varnam -- Fcitx5 wrapper for Varnam input method.

[Anoop M S]

Hi,
On Mon, 15 Jul 2024 00:43:38 +0530 Anoop M S  wrote:
> Hi,
> On Sun, 14 Jul 2024 14:44:59 -0400 Boyuan Yang  wrote:
> > Hi,
> >
> > 在 2024-07-14星期日的 20:59 +0530，Anoop M S写道：
> > > On Fri, 31 May 2024 10:48:21 -0400 Boyuan Yang 
> wrote:
> > >  > Hi,
> > >  >
> > >  > 在 2024-05-31星期五的 08:19 +，Anoop M S写道：
> > >  > > Package: wnpp
> > >  > > Severity: wishlist
> > >  > > Owner: Anoop M S 
> > >  > > X-Debbugs-Cc: debian-de...@lists.debian.org, 
anoo...@disroot.org

> > >  > >
> > >  > > * Package name    : fcitx5-varnam
> > >  > >   Version : 0.0.1
> > >  > >   Upstream Contact: Anoop M S 
> > >  > > * URL : 
https://github.com/varnamproject/varnam-fcitx5

> > >  > > * License : GPL
> > >  > >   Programming Lang: C++
> > >  > >   Description : Fcitx5 wrapper for Varnam input method.
> > >  > >
> > >  > > Fcitx5 wrapper for Varnam(https://www.varnamproject.com) Input
> > > Method Engine.
> > >  > > Easily type Indian languages on Linux desktops.
> > >  > >
> > >  > > I would like to join Debian Input Method Team, and package and
> > > maintain it.
> > >  > > And I would need a sponsor to upload it as well.
> > >  >
> > >  > Please prepare an initial version first. You can host it on your
> own
> > > Salsa git repo
> > >  > or via mentors.debian.net , or choose whichever platform that is
> more
> > > convenient to you.
> > >  > Please submit a regular RFS request and notify me once you are
> prepared.
> > >  >
> > >  > If it looks good, I can help to move your git packaging repo 
to the

> > > Salsa Input Method
> > >  > Team namespace, sponsor the upload and add you into the Salsa 
Input

> > > Method Team group.
> > >  >
> > >  > Thanks,
> > >  > Boyuan Yang
> > >
> > > I've prepared an initial release and sent RFS (#1076334).
> > >
> > > Kindly review at your convenience.
> >
> > The following issues are critical and must be fixed:
> >
> > *
> 
https://github.com/varnamproject/varnam-fcitx5/blob/a2c9412461f68a5293cec24609076951e28a3b27/meson.build#L11-L29

> > is unacceptable. The build system is only targeting on x86_64 (amd64)
> architecture, which is
> > not reasonable since Debian and Fedora both support multiple hardware
> architectures.

I've addressed the raised issues in the upstream. And made few changes 
in the package as well (haven't pushed the code yet).

Lintian currently showing following issues
* newer-standards-version 4.7.0
* debian-watch-does-not-check-openpgp-signature
* prefer-uscan-symlink

full text : https://paste.debian.net/plain/1323647

Are these ignorable? And is there anything else I need to follow to do 
the version update

 or can I create a fresh setup with only the new version?

Thanks and Regards,
Anoop


OpenPGP_0xDC6CE985B8F95651.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1072274: ITP: fcitx5-varnam -- Fcitx5 wrapper for Varnam input method.

[Anoop M S]

Hi,
On Sun, 14 Jul 2024 14:44:59 -0400 Boyuan Yang  wrote:
> Hi,
>
> 在 2024-07-14星期日的 20:59 +0530，Anoop M S写道：
> > On Fri, 31 May 2024 10:48:21 -0400 Boyuan Yang  
wrote:

> >  > Hi,
> >  >
> >  > 在 2024-05-31星期五的 08:19 +，Anoop M S写道：
> >  > > Package: wnpp
> >  > > Severity: wishlist
> >  > > Owner: Anoop M S 
> >  > > X-Debbugs-Cc: debian-de...@lists.debian.org, anoo...@disroot.org
> >  > >
> >  > > * Package name    : fcitx5-varnam
> >  > >   Version : 0.0.1
> >  > >   Upstream Contact: Anoop M S 
> >  > > * URL : https://github.com/varnamproject/varnam-fcitx5
> >  > > * License : GPL
> >  > >   Programming Lang: C++
> >  > >   Description : Fcitx5 wrapper for Varnam input method.
> >  > >
> >  > > Fcitx5 wrapper for Varnam(https://www.varnamproject.com) Input
> > Method Engine.
> >  > > Easily type Indian languages on Linux desktops.
> >  > >
> >  > > I would like to join Debian Input Method Team, and package and
> > maintain it.
> >  > > And I would need a sponsor to upload it as well.
> >  >
> >  > Please prepare an initial version first. You can host it on your 
own

> > Salsa git repo
> >  > or via mentors.debian.net , or choose whichever platform that is 
more

> > convenient to you.
> >  > Please submit a regular RFS request and notify me once you are 
prepared.

> >  >
> >  > If it looks good, I can help to move your git packaging repo to the
> > Salsa Input Method
> >  > Team namespace, sponsor the upload and add you into the Salsa Input
> > Method Team group.
> >  >
> >  > Thanks,
> >  > Boyuan Yang
> >
> > I've prepared an initial release and sent RFS (#1076334).
> >
> > Kindly review at your convenience.
>
> The following issues are critical and must be fixed:
>
> * 
https://github.com/varnamproject/varnam-fcitx5/blob/a2c9412461f68a5293cec24609076951e28a3b27/meson.build#L11-L29
> is unacceptable. The build system is only targeting on x86_64 (amd64) 
architecture, which is
> not reasonable since Debian and Fedora both support multiple hardware 
architectures.

>
> To avoid headaches, I highly recommend switching to CMake buildsystem 
and reuse

> fcitx5-provided CMake infrastructure. That will make the life easier. If
> Meson is the only choice, a more elegant solution is needed.
> Will https://mesonbuild.com/CMake-module.html help?
>
> * Please explain that why you are carrying patches in debian/patches/ 
directory,

> and why they cannot enter upstream project.
>

* That was my mistake, I didn't actually considered other architectures 
at all. Let me see if its possible to handle it with Meson itself.

 If not possible I will switch to CMake.
*  And regarding those patches, I was trying to create an initial setup 
without creating a new upstream release.
 I'll prepare another release once all required changes in upstream is 
done.


 Thank you for your time!

Regards,
Anoop



OpenPGP_0xDC6CE985B8F95651.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1072274: ITP: fcitx5-varnam -- Fcitx5 wrapper for Varnam input method.

[Anoop M S]

On Fri, 31 May 2024 10:48:21 -0400 Boyuan Yang  wrote:
> Hi,
>
> 在 2024-05-31星期五的 08:19 +，Anoop M S写道：
> > Package: wnpp
> > Severity: wishlist
> > Owner: Anoop M S 
> > X-Debbugs-Cc: debian-de...@lists.debian.org, anoo...@disroot.org
> >
> > * Package name    : fcitx5-varnam
> >   Version : 0.0.1
> >   Upstream Contact: Anoop M S 
> > * URL : https://github.com/varnamproject/varnam-fcitx5
> > * License : GPL
> >   Programming Lang: C++
> >   Description : Fcitx5 wrapper for Varnam input method.
> >
> > Fcitx5 wrapper for Varnam(https://www.varnamproject.com) Input 
Method Engine.

> > Easily type Indian languages on Linux desktops.
> >
> > I would like to join Debian Input Method Team, and package and 
maintain it.

> > And I would need a sponsor to upload it as well.
>
> Please prepare an initial version first. You can host it on your own 
Salsa git repo
> or via mentors.debian.net , or choose whichever platform that is more 
convenient to you.

> Please submit a regular RFS request and notify me once you are prepared.
>
> If it looks good, I can help to move your git packaging repo to the 
Salsa Input Method
> Team namespace, sponsor the upload and add you into the Salsa Input 
Method Team group.

>
> Thanks,
> Boyuan Yang

I've prepared an initial release and sent RFS (#1076334).

Kindly review at your convenience.

Thanks and Regards,

Anoop



OpenPGP_0xDC6CE985B8F95651.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1076334: RFS: fcitx5-varnam/0.0.1-1 [ITP] -- Fcitx5 wrapper for Varnam input method.

[Anoop M S]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "fcitx5-varnam":

 * Package name : fcitx5-varnam
   Version  : 0.0.1-1
   Upstream contact : Anoop M S 
 * URL  : https://github.com/varnamproject/varnam-fcitx5
 * License  : MPL-1.1, CC0-1.0, GPL-3+
 * Vcs  : 
https://salsa.debian.org/input-method-team/fcitx5-varnam

   Section  : utils

The source builds the following binary packages:

  fcitx5-varnam - Fcitx5 wrapper for Varnam input method.

To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/fcitx5-varnam/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/f/fcitx5-varnam/fcitx5-varnam_0.0.1-1.dsc


I've also uploaded the source to the following Salsa repository:

  https://salsa.debian.org/anoop/fcitx5-varnam

Changes for the initial release:

 fcitx5-varnam (0.0.1-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1072274)
   * Patched icon destination and name
   * Add git to build-dep to fix sbuild

Regards,
--
  Anoop


OpenPGP_0xDC6CE985B8F95651.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1076034: linux-image-6.1.0-22-amd64: Frequent system lockups with "timed out waiting for forcewake ack request"

[S.]

Had the same thing happen with the 6.1.0-21 kernel, so I tried the 6.7.12 
kernel from Backports. Then while booted into that kernel it happened again, 
but this time I SSHed into the system from another computer and found a 
coredump from i915:



Jul 10 15:17:01 IntelNUC9 CRON[44323]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
Jul 10 15:17:01 IntelNUC9 CRON[44325]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
Jul 10 15:17:01 IntelNUC9 CRON[44323]: pam_unix(cron:session): session closed 
for user root
Jul 10 15:18:18 IntelNUC9 kernel: i915 :00:02.0: [drm] *ERROR* media: timed 
out waiting for forcewake ack request.
Jul 10 15:18:18 IntelNUC9 kernel: i915 :00:02.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x1f5/0x250 [i915]
Jul 10 15:18:18 IntelNUC9 kernel: i915 :00:02.0: [drm] Resetting rcs0 for 
preemption time out
Jul 10 15:18:18 IntelNUC9 kernel: i915 :00:02.0: [drm] *ERROR* GT0: rcs0 
reset request timed out: {request: 0001, RESET_CTL: 0001}
Jul 10 15:18:18 IntelNUC9 kernel: i915 :00:02.0: [drm] GPU HANG: ecode 
9:1:eedf, in zoom.real [39829]
Jul 10 15:18:28 IntelNUC9 kernel: Asynchronous wait on fence 
:00:02.0:cinnamon[1948]:137a40 timed out (hint:intel_atomic_commit_ready 
[i915])
Jul 10 15:18:31 IntelNUC9 wpa_supplicant[1392]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-69 noise= txrate=1000
Jul 10 15:18:34 IntelNUC9 kernel: BUG: kernel NULL pointer dereference, 
address: 0270
Jul 10 15:18:34 IntelNUC9 kernel: #PF: supervisor read access in kernel mode
Jul 10 15:18:34 IntelNUC9 kernel: #PF: error_code(0x) - not-present page
Jul 10 15:18:34 IntelNUC9 kernel: PGD 80018e8a8067 P4D 80018e8a8067 PUD 
6bf133067 PMD 6bf041067 PTE 0
Jul 10 15:18:34 IntelNUC9 kernel: Oops:  [#1] PREEMPT SMP PTI
Jul 10 15:18:34 IntelNUC9 kernel: CPU: 5 PID: 264 Comm: kworker/5:1H Tainted: G 
   W  6.7.12+bpo-amd64 #1  Debian 6.7.12-1~bpo12+1
Jul 10 15:18:34 IntelNUC9 kernel: Hardware name: Intel(R) Client Systems 
LAPQC71A/LAPQC71A, BIOS QCCFL357.0144.2022.0124.1433 01/24/2022
Jul 10 15:18:34 IntelNUC9 kernel: Workqueue: events_highpri heartbeat [i915]
Jul 10 15:18:34 IntelNUC9 kernel: RIP: 0010:__i915_gpu_coredump+0x227/0x760 
[i915]
Jul 10 15:18:34 IntelNUC9 kernel: Code: 44 24 08 85 c0 79 37 49 8b 74 24 08 48 8b 44 
24 20 49 8d 54 24 18 48 8b 36 48 8b 48 20 4c 8b 40 28 48 8b 7e 08 48 8b 74 24 18 
<44> 0f b7 8e 70 02 00 00 48 c7 c6 50 88 38 c1 e8 95 29 85 d1 48 8b
Jul 10 15:18:34 IntelNUC9 kernel: RSP: :b08580793c88 EFLAGS: 00010286
Jul 10 15:18:34 IntelNUC9 kernel: RAX: 9980db2e2680 RBX: 9983fa32ac00 
RCX: 1155
Jul 10 15:18:34 IntelNUC9 kernel: RDX: 997e80f74018 RSI:  
RDI: 997e81fb70c0
Jul 10 15:18:34 IntelNUC9 kernel: RBP:  R08: 398c 
R09: 
Jul 10 15:18:34 IntelNUC9 kernel: R10:  R11: e164 
R12: 997e80f74000
Jul 10 15:18:34 IntelNUC9 kernel: R13: 997f10e63000 R14: 9980030df000 
R15: 997f10e63c00
Jul 10 15:18:34 IntelNUC9 kernel: FS:  () 
GS:99861db4() knlGS:
Jul 10 15:18:34 IntelNUC9 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Jul 10 15:18:34 IntelNUC9 kernel: CR2: 0270 CR3: 000415a66004 
CR4: 003706f0
Jul 10 15:18:34 IntelNUC9 kernel: Call Trace:
Jul 10 15:18:34 IntelNUC9 kernel:  
Jul 10 15:18:34 IntelNUC9 kernel:  ? __die+0x23/0x70
Jul 10 15:18:34 IntelNUC9 kernel:  ? page_fault_oops+0x171/0x4e0
Jul 10 15:18:34 IntelNUC9 kernel:  ? intel_gt_mcr_lock+0x42/0x140 [i915]
Jul 10 15:18:34 IntelNUC9 kernel:  ? exc_page_fault+0x77/0x170
Jul 10 15:18:34 IntelNUC9 kernel:  ? asm_exc_page_fault+0x26/0x30
Jul 10 15:18:34 IntelNUC9 kernel:  ? __i915_gpu_coredump+0x227/0x760 [i915]
Jul 10 15:18:34 IntelNUC9 kernel:  ? __i915_gpu_coredump+0x1fc/0x760 [i915]
Jul 10 15:18:34 IntelNUC9 kernel:  i915_capture_error_state+0x61/0xd0 [i915]
Jul 10 15:18:34 IntelNUC9 kernel:  intel_gt_handle_error+0x3c7/0x3e0 [i915]
Jul 10 15:18:34 IntelNUC9 kernel:  ? execlists_submission_tasklet+0xfd/0x1740 
[i915]
Jul 10 15:18:34 IntelNUC9 kernel:  heartbeat+0x3c2/0x3d0 [i915]
Jul 10 15:18:34 IntelNUC9 kernel:  process_one_work+0x17c/0x350
Jul 10 15:18:34 IntelNUC9 kernel:  worker_thread+0x27b/0x3a0
Jul 10 15:18:34 IntelNUC9 kernel:  ? __pfx_worker_thread+0x10/0x10
Jul 10 15:18:34 IntelNUC9 kernel:  kthread+0xe5/0x120
Jul 10 15:18:34 IntelNUC9 kernel:  ? __pfx_kthread+0x10/0x10
Jul 10 15:18:34 IntelNUC9 kernel:  ret_from_fork+0x31/0x50
Jul 10 15:18:34 IntelNUC9 kernel:  ? __pfx_kthread+0x10/0x10
Jul 10 15:18:34 IntelNUC9 kernel:  ret_from_fork_asm+0x1b/0x30
Jul 10 15:18:34 IntelNUC9 kernel:  
Jul 10 15:18:34 IntelNUC9 kernel: Modules linked in: cpuid ufs qnx4 hfsplus hfs 
cdrom minix msdos jfs nls_ucs2_utils xfs ext4 mbcache jbd2 

Bug#1076034: linux-image-6.1.0-22-amd64: Frequent system lockups with "timed out waiting for forcewake ack request"

[S.]

Had the same thing happen again but with firmware-iwlwifi 20230625, so moving 
back to the Debian Stable version, and I'm going to test the previous 6.1.0-21 
kernel.

Bug#1076034: linux-image-6.1.0-22-amd64: Frequent system lockups with "timed out waiting for forcewake ack request"

[S.]

Package: src:linux
X-Debbugs-Cc: sb56...@gmail.com
Version: 6.1.94-1
Severity: important

Dear Maintainer,

I have been experiencing frequent system lockups when the computer is under 
moderate CPU load, usually while running an audio editing program with Wine or 
soon after closing the program. The mouse still moves, but nothing reacts and I 
can't even switch to a virtual terminal, so I have to force a hardware power 
off and reboot. This problems seems to have started since the recent Debian 
Stable update to kernel 6.1.0-22, having happened at least 5 times or more 
since the upgrade. Each time after reboot the previous boot's journalctl log 
shows the same sort of errors that I am including in this report. As of this 
current system boot that I used to generate this bug report I am trying 
firmware-iwlwifi 20230625 from Testing to see if that fixes anything, but 
before this I was running the Debian Stable version.


-- Package-specific info:
** Version:
Linux version 6.1.0-22-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21)


** Command line:
BOOT_IMAGE=/@/boot/vmlinuz-6.1.0-22-amd64 
root=UUID=9b7ad72a-c27f-41d3-8845-cd4b23197f2b ro rootflags=subvol=@ quiet 
loglevel=0 splash threadirqs

** Tainted: DOE (12416)
 * kernel died recently, i.e. there was an OOPS or BUG
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
Jul 09 12:02:01 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:02:01 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:04:41 IntelNUC9 kernel: xhci_hcd :01:00.2: xHC error in resume, 
USBSTS 0x401, Reinit
Jul 09 12:04:41 IntelNUC9 kernel: usb usb3: root hub lost power or was reset
Jul 09 12:04:41 IntelNUC9 kernel: usb usb4: root hub lost power or was reset
Jul 09 12:04:41 IntelNUC9 systemd[1740]: app-flatpak-us.zoom.Zoom-49672.scope: 
Consumed 2h 11min 57.586s CPU time.
Jul 09 12:05:16 IntelNUC9 wpa_supplicant[1386]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-72 noise= txrate=292600
Jul 09 12:05:19 IntelNUC9 wpa_supplicant[1386]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=0 signal=-76 noise= txrate=292600
Jul 09 12:05:20 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:05:20 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:05:32 IntelNUC9 wpa_supplicant[1386]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-68 noise= txrate=292600
Jul 09 12:05:53 IntelNUC9 wpa_supplicant[1386]: wlan0: CTRL-EVENT-SIGNAL-CHANGE 
above=1 signal=-66 noise= txrate=325000
Jul 09 12:07:01 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:07:01 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:07:55 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:07:55 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:07:56 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:07:56 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:08:37 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:08:37 IntelNUC9 rtkit-daemon[1640]: Supervising 0 threads of 0 
processes of 0 users.
Jul 09 12:08:40 IntelNUC9 kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* media: timed out waiting for forcewake ack request.
Jul 09 12:08:40 IntelNUC9 kernel: i915 :00:02.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x1d8/0x230 [i915]
Jul 09 12:08:40 IntelNUC9 kernel: i915 :00:02.0: [drm] Resetting rcs0 for 
preemption time out
Jul 09 12:08:40 IntelNUC9 kernel: i915 :00:02.0: [drm] *ERROR* rcs0 reset 
request timed out: {request: 0001, RESET_CTL: 0001}
Jul 09 12:08:40 IntelNUC9 kernel: i915 :00:02.0: [drm] GPU HANG: ecode 
9:1:eedf
Jul 09 12:08:42 IntelNUC9 kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* media: timed out waiting for forcewake ack request.
Jul 09 12:08:42 IntelNUC9 kernel: i915 :00:02.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x1d8/0x230 [i915]
Jul 09 12:08:49 IntelNUC9 kernel: Asynchronous wait on fence 
:00:02.0:cinnamon[1990]:1e8906 timed out (hint:intel_atomic_commit_ready 
[i915])
Jul 09 12:08:54 IntelNUC9 kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* media: timed out waiting for forcewake ack request.
Jul 09 12:08:54 IntelNUC9 kernel: i915 :00:02.0: [drm:add_taint_for_CI 
[i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x1d8/0x230 [i915]
Jul 09 12:08:55 IntelNUC9 kernel: [drm:fw_domains_get_with_fallback [i915]] 
*ERROR* media: timed out waiting for forcewake ack r

Bug#1074508: firefox-esr: a site no longer displayed correctly

[Janusz S . Bień]

On Sun, Jun 30 2024 at  9:36 +02, Janusz S. Bień wrote:
> Unable to reproduce the problem on another computer (a notebook) running
> practically identical system.
>
> It happened also on another occasions that the programs on my desktop
> behave erroneusly while on the notebook they work OK.

It started to work on the desktop, too.

Please close the bug.

JSB

-- 
     ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1074508: firefox-esr: a site no longer displayed correctly

[Janusz S . Bień]

Unable to reproduce the problem on another computer (a notebook) running
practically identical system.

It happened also on another occasions that the programs on my desktop
behave erroneusly while on the notebook they work OK.

Any idea?

Best regards

JSB


-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1067578: (no subject)

[S Page]

I suspect the changes in debian packaging are add 
`--enable-cairo-backend` to  the `dh_auto_configure` line in 
debian/rules and add `libcairo2` under `Build-depends:` in 
debian/control. But I'm on Fedora and guessing.

Bug#1072274: ITP: fcitx5-varnam -- Fcitx5 wrapper for Varnam input method.

[Anoop M S]

Package: wnpp
Severity: wishlist
Owner: Anoop M S 
X-Debbugs-Cc: debian-de...@lists.debian.org, anoo...@disroot.org

* Package name: fcitx5-varnam
  Version : 0.0.1
  Upstream Contact: Anoop M S 
* URL : https://github.com/varnamproject/varnam-fcitx5
* License : GPL
  Programming Lang: C++
  Description : Fcitx5 wrapper for Varnam input method.

Fcitx5 wrapper for Varnam(https://www.varnamproject.com) Input Method Engine.
Easily type Indian languages on Linux desktops.

I would like to join Debian Input Method Team, and package and maintain it.
And I would need a sponsor to upload it as well.

Bug#1036310: bookworm installer hangs in efi mode on virtualbox 7.0.8

[Rudy S.]

Hello Erwin,
Thanks a lot for work-around advise ;)

Sorry for late answer but I just read it and give a try to "Disabling 
paravirtualization in virtualbox acceleration"
(i.e. VBox GUI, in the 'Settings...' of the VM, go to 'System' panel than in the 'Acceleration' tab select 'None' as 
'Paravirtualization Interface' ;))


This help me to install like this a Debian-12.5 DVD as a simple SSH server on 
VBox release is 7.0.18 ;)

For what is weird: once the installation is completed , I can switch back the 'Paravirtualization Interface' to 'Default' ( 
even with 'Secure boot' enabled ;) )


Thanks a lot again,
Rudy S.

On Wed, 31 May 2023 12:04:04 +0200 Erwin Van de Velde 
 wrote:

Hi,

Encountering the same issue, I can confirm it still persists in RC4.
However, digging a bit deeper with the error I found on dmesg: "x86/PAT:
bterm:260: map pfn expected mapping type uncached-minus for ..., got
write-combining", I found this workaround:
Disabling paravirtualization in virtualbox acceleration or switching it to
legacy results in a properly booting installer.

Kind regards,
Erwin

Bug#1070784: birdfont: unable to run

[Janusz S . Bień]

On Sun, May 12 2024 at 22:20 +09, Hideki Yamane wrote:
> severity -1 normal
> tags -1 +unreproducible
> thanks
>
>
> On Thu, 09 May 2024 06:19:47 +0200
> Janusz S. Bień  wrote:
>
>> Package: birdfont
>> Version: 2.32.3-2
>
>> I get
>> 
>> birdfont: symbol lookup error: 
>> /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: 
>> gst_transcoder_get_sync_signal_adapter
>
>  I've tested it with freshly-installed Debian12.5 VM on gnome-boxes and
>  birdfont works fine, so tagged this bug as unreproducible and severity
>  as normal.

I installed the program on my notebook which in principle has the same
system version as the desktop, and there birdfont also works...

>
>
>> ii  libwebkit2gtk-4.0-37  2.42.5-1~deb12u1
>
>  Could you check its files with "LANG=C ls -l 
> /lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so*"
>  and update its package with newest libwebkit2gtk-4.0-37 package, please?
>
>  It was updated as 
> https://lists.debian.org/debian-security-announce/2024/msg00095.html

This is the output from the desktop:

LANG=C ls -l /lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so*
lrwxrwxrwx 1 root root   27 May  8 12:14 
/lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so.0 -> libwebkit2gtk-4.1.so.0.13.5
-rw-r--r-- 1 root root 76081696 May  8 12:14 
/lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so.0.13.5

jsbien@JSBbookworm:~$ birdfont
birdfont: symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: 
undefined symbol: gst_transcoder_get_sync_signal_adapter

Could the kernel be the culprit??? I avoid to reboot the system because
sometimes it fails for unknown reason (perhaps a hardware problem?). So on
the desktop the kernel is older than on the notebook, on which the
program works.

Best regards

JSB

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1070784: birdfont: unable to run

[Janusz S . Bień]

Package: birdfont
Version: 2.32.3-2
Severity: important
X-Debbugs-Cc: none, Janusz S. Bień 

Dear Maintainer,

I get

birdfont: symbol lookup error: /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37: 
undefined symbol: gst_transcoder_get_sync_signal_adapter

Yours

JSB

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

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

Versions of packages birdfont depends on:
ii  birdfont-common   2.32.3-2
ii  libc6 2.36-9+deb12u7
ii  libcairo-gobject2 1.16.0-7
ii  libcairo2 1.16.0-7
ii  libfontconfig12.14.1-4
ii  libfreetype6  2.12.1+dfsg-5
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libgee-0.8-2  0.20.6-1
ii  libglib2.0-0  2.74.6-2+deb12u1
ii  libgtk-3-03.24.38-2~deb12u1
ii  libnotify40.8.1-1
ii  libsqlite3-0  3.40.1-2
ii  libwebkit2gtk-4.0-37  2.42.5-1~deb12u1
ii  libxmlbird1   1.2.12-1

Versions of packages birdfont recommends:
ii  unicode-data  15.0.0-1

birdfont suggests no packages.

-- no debconf information

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1056120: a different workaround

[McIntyre, Vincent (S&A, Marsfield)]

I found Sebastian's patch did not fix this for me.

A simpler change seems to have sorted it out though:

--- debian.cnf.orig 2024-05-09 12:02:59.845494238 +1000
+++ debian.cnf  2024-05-09 12:03:10.213564938 +1000
@@ -3,10 +3,12 @@
  host = localhost
  user = root
  password = 
+protocol = socket
  socket   = /var/run/mysqld/mysqld.sock
  [mysql_upgrade]
  host = localhost
  user = root
  password = 
+protocol = socket
  socket   = /var/run/mysqld/mysqld.sock
  basedir  = /usr

Kind regards
Vince

Bug#1034420: grub-efi-amd64: Package update fails with error: installation script subprocess returned error exit status 128

[Markus S]

Hi,

I am running into the same problem.
One of my machines fails the install with:

installed grub-efi-amd64 package post-installation script subprocess
returned error exit status 128

here the full log with -x in and DEBCONF_DEBUG=developer

# dpkg --configure -a --debug=77
D01: root= admindir=/var/lib/dpkg
D01: ensure_diversions: new, (re)loading
D01: process queue pkg grub-efi:amd64 queue.len 1 progress 1, try 1
D40: checking dependencies of grub-efi:amd64 (- )
D000400:   checking group ...
D000400: checking possibility  -> grub-common
D000400:   checking non-provided pkg grub-common:amd64
D000400:   is installed, ok and found
D000400: found 3
D000400:   found 3 matched 0 possfixbytrig -
D000400:   checking group ...
D000400: checking possibility  -> grub-efi-amd64
D000400:   checking non-provided pkg grub-efi-amd64:amd64
D000400:   unpacked/halfconfigured, defer
D000400: found 1
D000400:   found 1 matched 0 possfixbytrig -
D40: ok 1 msgs >><<
D01: process queue pkg grub-efi-amd64:amd64 queue.len 1 progress 2, try 1
D40: checking dependencies of grub-efi-amd64:amd64 (- )
D000400:   checking group ...
D000400: checking possibility  -> debconf
D000400:   checking non-provided pkg debconf:all
D000400:   is installed, ok and found
D000400: found 3
D000400:   found 3 matched 0 possfixbytrig -
D000400:   checking group ...
D000400: checking possibility  -> grub-common
D000400:   checking non-provided pkg grub-common:amd64
D000400:   is installed, ok and found
D000400: found 3
D000400:   found 3 matched 0 possfixbytrig -
D000400:   checking group ...
D000400: checking possibility  -> grub2-common
D000400:   checking non-provided pkg grub2-common:amd64
D000400:   is installed, ok and found
D000400: found 3
D000400:   found 3 matched 0 possfixbytrig -
D000400:   checking group ...
D000400: checking possibility  -> grub-efi-amd64-bin
D000400:   checking non-provided pkg grub-efi-amd64-bin:amd64
D000400:   is installed, ok and found
D000400: found 3
D000400:   found 3 matched 0 possfixbytrig -
D000400:   checking group ...
D000400: checking possibility  -> ucf
D000400:   checking non-provided pkg ucf:all
D000400:   is installed, ok and found
D000400: found 3
D000400:   found 3 matched 0 possfixbytrig -
D40: ok 2 msgs >><<
D40: checking Breaks
D000400:   checking breaker grub2-common:amd64 virtbroken 
Setting up grub-efi-amd64 (2.06-13+deb12u1) ...
D02: trigproc_activate_packageprocessing pkg=grub-efi-amd64:amd64
D02: fork/exec /var/lib/dpkg/info/grub-efi-amd64.postinst (
configure 2.06-3~deb11u6 )
+ cached_available_ids=
+ case "$1" in
+ . /usr/share/debconf/confmodule
++ '[' '!' '' ']'
++ PERL_DL_NONLAZY=1
++ export PERL_DL_NONLAZY
++ '[' '' ']'
++ exec /usr/share/debconf/frontend
/var/lib/dpkg/info/grub-efi-amd64.postinst configure 2.06-3~deb11u6
debconf (developer): frontend started
debconf (developer): frontend running, package name is grub-efi-amd64
debconf (developer): starting /var/lib/dpkg/info/grub-efi-amd64.config
configure 2.06-3~deb11u6
debconf (developer): <-- SET grub2/linux_cmdline
debconf (developer): --> 0 value set
debconf (developer): <-- SET grub2/linux_cmdline_default
module.sig_enforce=0 i915.preliminary_hw_support=1 intel_iommu=on
amd_iommu=on kvm_amd.npt=1 kvm_amd.avic=1 iommu=pt
debconf (developer): --> 0 value set
debconf (developer): <--
debconf (developer): --> 20 Bad line "" received from confmodule.
debconf (developer): <-- INPUT medium grub2/linux_cmdline
debconf (developer): --> 30 question skipped
debconf (developer): <-- INPUT medium grub2/linux_cmdline_default
debconf (developer): --> 30 question skipped
debconf (developer): <-- INPUT low grub2/enable_os_prober
debconf (developer): --> 30 question skipped
debconf (developer): <-- INPUT low grub2/force_efi_extra_removable
debconf (developer): --> 30 question skipped
debconf (developer): <-- INPUT low grub2/update_nvram
debconf (developer): --> 30 question skipped
debconf (developer): <-- GO
debconf (developer): --> 0 ok
dpkg: error processing package grub-efi-amd64 (--configure):
 installed grub-efi-amd64 package post-installation script subprocess
returned error exit status 128
D02: post_script_tasks - ensure_diversions
D01: ensure_diversions: same, skipping
D02: post_script_tasks - trig_incorporate
D01: process queue pkg grub-efi:amd64 queue.len 0 progress 1, try 1
D40: checking dependencies of grub-efi:amd64 (- )
D000400:   checking group ...
D000400: checking possibility  -> grub-common
D000400:   checking non-provided pkg grub-common:amd64
D000400:   is installed, ok and found
D000400: found 3
D000400:   found 3 matched 0 possfixbytrig -
D000400:   checking group ...
D000400: checking possibility  -> grub-efi-amd64
D000400:   checking non-provided pkg grub-efi-amd64:amd64
D000400:   not configured/able
D00040

Bug#1068585: inkscape: crash

[Janusz S . Bień]

Package: inkscape
Version: 1.2.2-2+b1
Severity: normal
X-Debbugs-Cc: none, Janusz S. Bień 

Dear Maintainer,

When trying to compile https://github.com/rmast/revealshapes I get the
crash described here:
https://github.com/rmast/revealshapes/discussions/1#discussioncomment-9034291,
namely

Emergency save document locations:
/home/jsbien/git/revealshapes/desktopfiles/djvu.svg.2024_04_07_09_35_35.0.svg
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at 
https://inkscape.org/report
with a detailed description of the steps leading to the crash, so we can
fix it.

It was followed by
make[2]: *** [Makefile:597: 16x16/mimetypes/image-vnd.djvu.png] Segmentation 
fault


Following the instruction I reported the problem here:

https://gitlab.com/inkscape/inbox/-/issues/10195

Best regards

JSB

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

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

Versions of packages inkscape depends on:
ii  lib2geom1.2.0  1.2.2-3
ii  libatkmm-1.6-1v5   2.28.3-1
ii  libboost-filesystem1.74.0  1.74.0+ds1-21
ii  libc6  2.36-9+deb12u4
ii  libcairo-gobject2  1.16.0-7
ii  libcairo2  1.16.0-7
ii  libcairomm-1.0-1v5 1.14.4-2
ii  libcdr-0.1-1   0.1.6-2+b2
ii  libfontconfig1 2.14.1-4
ii  libfreetype6   2.12.1+dfsg-5
ii  libgc1 1:8.2.2-3
ii  libgcc-s1  12.2.0-14
ii  libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1
ii  libglib2.0-0   2.74.6-2
ii  libglibmm-2.4-1v5  2.66.5-2
ii  libgomp1   12.2.0-14
ii  libgsl27   2.7.1+dfsg-5
ii  libgspell-1-2  1.12.0-1+b2
ii  libgtk-3-0 3.24.38-2~deb12u1
ii  libgtkmm-3.0-1v5   3.24.7-1
ii  libharfbuzz0b  6.0.0+dfsg-3
ii  libjpeg62-turbo1:2.1.5-2
ii  liblcms2-2 2.14-2
ii  libmagick++-6.q16-88:6.9.11.60+dfsg-1.6+deb12u1
ii  libpango-1.0-0 1.50.12+ds-1
ii  libpangocairo-1.0-01.50.12+ds-1
ii  libpangoft2-1.0-0  1.50.12+ds-1
ii  libpangomm-1.4-1v5 2.46.3-1
ii  libpng16-161.6.39-2
ii  libpoppler-glib8   22.12.0-2+b1
ii  libpoppler126  22.12.0-2+b1
ii  libpotrace01.16-2
ii  libreadline8   8.2-1.3
ii  librevenge-0.0-0   0.0.5-3
ii  librsvg2-common2.54.7+dfsg-1~deb12u1
ii  libsigc++-2.0-0v5  2.12.0-1
ii  libsoup2.4-1   2.74.3-1
ii  libstdc++6 12.2.0-14
ii  libvisio-0.1-1 0.1.7-1+b3
ii  libwpg-0.3-3   0.3.3-1
ii  libx11-6   2:1.8.4-2+deb12u2
ii  libxml22.9.14+dfsg-1.3~deb12u1
ii  libxslt1.1 1.1.35-1
ii  python33.11.2-1+b1
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages inkscape recommends:
ii  aspell   0.60.8-4+b1
ii  fig2dev  1:3.2.8b-3
ii  imagemagick  8:6.9.11.60+dfsg-1.6+deb12u1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.6+deb12u1
ii  libimage-magick-perl 8:6.9.11.60+dfsg-1.6+deb12u1
ii  libwmf-bin   0.2.12-5.1
ii  python3-cssselect1.2.0-2
ii  python3-lxml 4.9.2-1+b1
ii  python3-numpy1:1.24.2-1
ii  python3-scour0.38.2-2

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

-- no debconf information

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1067652: RFP: logisim-evolution -- Logisim-evolution is educational software for designing and simulating digital logic circuits

[Andrew S. Rightenburg]

Package: wnpp
Severity: wishlist

* Package name: logisim-evolution
  Version : 3.8.0
  Upstream Contact: Logisim-evolution development team
* URL : https://github.com/logisim-evolution/logisim-evolution
* License : GPL-3.0
  Programming Lang: Java
  Description : Digital logic design tool and simulator

Logisim-evolution is educational software for designing and simulating digital 
logic circuits.

It is a continuation of the old "Logisim" software by Carl Burch.
It's worth noting that the origin "Logisim" software has been
abandoned, and the "logisim" package in Debian has been orphaned
for several years.

The upstream development team maintains deb-format packaging as
well as snaps and flatpacks.

This software is used by engineering students the world over to
learn about and practice with logic circuits and FPGAs. I believe
it should be included as part of Debian

Bug#1062579: /usr/bin/wasm-opt has no manpage

[H. S. Teoh]

Package: binaryen
Version: 108-1
Severity: normal

Per Debian Policy 12.1, each program, utility, and function should have
an associated manpage. Currently /usr/bin/wasm-opt is lacking one.


T

-- 
Real men don't take backups. They put their source on a public FTP-server and 
let the world mirror it. -- Linus Torvalds

Bug#1061719: libqt6gui6:amd64: QT_QPA_PLATFORM=xcb doesn't seem to work

[Janusz S . Bień]

Package: libqt6gui6
Version: 6.4.2+dfsg-10
Severity: normal
X-Debbugs-Cc: none, Janusz S. Bień 
File: /usr/lib/x86_64-linux-gnu/qt6/plugins/platforms/libqxcb.so

A program which works correctly on X is crippled on Wayland, one of the
panels is not opened. I was advised to use xcb, but it does not have any
effect.

More information at the thread:

https://forum.qt.io/topic/154144/debian-after-upgrading-the-system-the-program-became-unusable-how-to-approach-the-problem/13?_=1706499698799

BTW, when reporting this problem with Emacs debian-bug I got a strange
warning that libqt6gui6 is not installed although apt install reports
"libqt6gui6 is already the newest version (6.4.2+dfsg-10)." Quite
possible that my QT installation is somehow messed up (I use it only for
compiling two QT programs). qtchooser reports 7 versions: 4 5 default
qt4-x86_64-linux-gnu qt4 qt5-x86_64-linux-gnu qt5. QTCreator reports
5.15.8 twice: /usr/lib/qt5/bin/qmake and
/usr/lib/x86_64-linux-gnu/qt5/bin/qmake.

I will appreciate your help

JSB

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

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

Versions of packages libqt6gui6:amd64 depends on:
ii  fontconfig  2.14.1-4
ii  libc6   2.36-9+deb12u3
ii  libdrm2 2.4.114-1+b1
ii  libegl1 1.6.0-1
ii  libfontconfig1  2.14.1-4
ii  libfreetype62.12.1+dfsg-5
ii  libgcc-s1   12.2.0-14
ii  libglib2.0-02.74.6-2
ii  libglx0 1.6.0-1
ii  libharfbuzz0b   6.0.0+dfsg-3
ii  libice6 2:1.0.10-1
ii  libinput10  1.22.1-1
ii  libjpeg62-turbo 1:2.1.5-2
ii  libmd4c00.4.8-1
ii  libmtdev1   1.1.6-1
ii  libopengl0  1.6.0-1
ii  libpng16-16 1.6.39-2
ii  libqt6core6 [qt6-base-abi]  6.4.2+dfsg-10
ii  libqt6dbus6 6.4.2+dfsg-10
ii  libsm6  2:1.2.3-1
ii  libstdc++6  12.2.0-14
ii  libts0  1.22-1+b1
ii  libudev1252.19-1~deb12u1
ii  libx11-62:1.8.4-2+deb12u2
ii  libx11-xcb1 2:1.8.4-2+deb12u2
ii  libxcb-glx0 1.15-1
ii  libxcb-icccm4   0.4.1-1.1
ii  libxcb-image0   0.4.0-2
ii  libxcb-keysyms1 0.4.0-1+b2
ii  libxcb-randr0   1.15-1
ii  libxcb-render-util0 0.3.9-1+b1
ii  libxcb-render0  1.15-1
ii  libxcb-shape0   1.15-1
ii  libxcb-shm0 1.15-1
ii  libxcb-sync11.15-1
ii  libxcb-xfixes0  1.15-1
ii  libxcb-xkb1 1.15-1
ii  libxcb1 1.15-1
ii  libxkbcommon-x11-0  1.5.0-1
ii  libxkbcommon0   1.5.0-1
ii  zlib1g  1:1.2.13.dfsg-1

Versions of packages libqt6gui6:amd64 recommends:
pn  qt6-gtk-platformtheme  
ii  qt6-qpa-plugins6.4.2+dfsg-10

libqt6gui6:amd64 suggests no packages.

-- no debconf information

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1061657: xcb (was: Bug#1061657: wayland-protocols: Upgrade of Wayland broke a program)

[Janusz S . Bień]

On Sun, Jan 28 2024 at  6:48 +01, Janusz S. Bień wrote:
> Package: wayland-protocols
> Version: 1.31-1
> Severity: normal
> X-Debbugs-Cc: none, Janusz S. Bień 
>
> This is probably not the right place to report my problem, please
> reassign as appropriate.
>
> A routine upgrade of Debian to bullseye (which, I understand, included
> an upgrade of Wayland) broke a program very important for me. Here is
> more information:
>
> https://forum.qt.io/topic/154144/debian-after-upgrading-the-system-the-program-became-unusable-how-to-approach-the-problem/
> https://github.com/jsbien/djview4shapes/issues/5

This is a QT program. I understand I should use

QT_QPA_PLATFORM=xcb

but this has no effect.

Should I install some library/package?

Best regards

JSB


-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1061657: wayland-protocols: Upgrade of Wayland broke a program

[Janusz S . Bień]

Package: wayland-protocols
Version: 1.31-1
Severity: normal
X-Debbugs-Cc: none, Janusz S. Bień 

This is probably not the right place to report my problem, please
reassign as appropriate.

A routine upgrade of Debian to bullseye (which, I understand, included
an upgrade of Wayland) broke a program very important for me. Here is
more information:

https://forum.qt.io/topic/154144/debian-after-upgrading-the-system-the-program-became-unusable-how-to-approach-the-problem/
https://github.com/jsbien/djview4shapes/issues/5

I will appreciate very much your help.

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

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

-- no debconf information

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1061090: autoconf-doc: single html file should be broken into one web page per node

[Louie S.]

Package: autoconf-doc
Severity: wishlist
X-Debbugs-Cc: lshpr...@tutanota.com

Dear Maintainer,

This package ships HTML documentation in a single file, as opposed to multiple
files, with one web page per node. Generally, GNU software documentation can
target HTML format either as entirely one web page or as one web page per node
(GNU Autoconf is no exception). I believe targetting one web page per node is
better practice.


-- 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-17-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 autoconf-doc depends on:
ii  gnu-standards  2022.03.23-0.1

autoconf-doc recommends no packages.

autoconf-doc suggests no packages.

Bug#1059095: general: Unable to boot

[Janusz S . Bień]

On Wed, Dec 20 2023 at  8:47 +01, Janusz Bień wrote:
> Package: general
> Severity: grave
> X-Debbugs-Cc: jsb...@mimuw.edu.pl
>
> Since yesterday I'm unable to boot the system, it hangs after the
> messages shown in an attachment; these messages or very similar ones
> appeared earlier with no harm.
>
> I update the system almost every evening. On 18th December the system
> worked normally, in the evening libfreeimage3 has been updated. Next
> day the boot problem appeared.
>
> The same problem occurs when I try to run Debian Live, I reported it
> as the bug #1059037.
>
> The computer has Windows on another disk (which I use now), so I can
> access the Linux disk and e.g. provide you with some logs. I can also
> run hardware detection from Debian Live.

Today everything works! The installed system, the installer (#1059167)
and Debian Live (1059037). Earlier several attemps failed, it was not
just a single incident.

Should I suspect a hardware malfunction? Can you recommend some testing
program?

Best regards

JSB

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1059167: installation-reports: installer hangs while recognizing network hardware

[Janusz S . Bień]

On Wed, Dec 20 2023 at 23:24 +01, Pascal Hambourg wrote:
> Hello Janusz,
>
> On 20/12/2023 at 20:52, Janusz Bień wrote:
>> I understand the installer now includes non-free drivers,
>
> No, only non-free firmware.
>
>> but I suspect  it missing one needed for my hardware, which is
>> Intel Ethernet Connection (7) I219-V
>> Intel Dual Band Wireless-AC 3168
>> (on the mainboard ASRock B360M-ITX/AC).
>
> How does the installer hang ? Can you switch to the installer shell in
> tty2 with Ctrl+Alt+F2 ? If yes, can you post the output of
>
> lspci -nnk
>
> and attach (compressed) /var/log/syslog ?

Thanks for your suggestion.

Today the network hardware was recognized in a second or so... Yesterday
at least two attempts failed...

Should I suspect a hardware malfunctions?

Best regards

JSB

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1059037: debian-live: Unable to boot 12.4.0 gnome

[Janusz S . Bień]

On Wed, Dec 20 2023 at  8:59 +01, Roland Clobus wrote:

[...]

On Tue, Dec 19 2023 at 16:15 GMT, Janusz Bień wrote:
> Package: debian-live
> Severity: grave
> X-Debbugs-Cc: jsb...@mimuw.edu.pl
>
> Trying to boot Debian Live 12.4.0 amd 64 Gnome I get the black screen
> with a large cursor.

Today it woorks! Earlier several attempts failed, it was not just a
single incident.


[...]

> Actually the installed system no longer boots, so to be able to use
> the live version is very important for me until I solve the problem of
> the installed version.

Now it also works!

Should I suspect a hardware malfunction?

Best regards

JSB


-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#969177: debmake: cannot create deb for nodejs modeule

[Akshay S Dinesh]

On Thu, 14 Jul 2022 16:37:52 +0200 Pirate Praveen 
 wrote:

Control: reopen -1
Control: notfixed 4.4.0-1

On Thu, 14 Jul 2022 10:54:14 +0200 Pirate Praveen
 wrote:
> Control: fixed -1 4.4.0-1
> 
> Looks like it is fixed in current version, closing this bug. Thanks!


Seems like I was mistaken, tried on a fresh clean chroot and it still
fails.





There's this commit referencing 4.4.0-1 on June 25, 2021 
https://salsa.debian.org/debian/debmake/-/commit/c59f0dbc112c5aaa737e0afdacbcc193e5e17dea


And this commit which fixes the bug on June 26, 2021 
https://salsa.debian.org/debian/debmake/-/commit/7f6c310aff8bf13eb64b98aff14e5e0b2bd58301


And this commit on May 6, 2022 which talks about 4.4.0
https://salsa.debian.org/debian/debmake/-/commit/07b1e07a9d9d327778d535287fdc70ac05dbe9e4



I'm unsure what's what.

https://packages.debian.org/sid/all/debmake/filelist is missing 
/usr/share/debmake/extra0desc_long/nodejs



In any case, a workaround is to do

echo " This package contains the nodejs program." | sudo tee 
/usr/share/debmake/extra0desc_long/nodejs

Bug#991815:

[Akshay S Dinesh]

I think with the latest version from upstream it would be easier to get the 
debian package working.




With 1.5.7 version the build related issues are minimal.

Here's what I've done presently.

First, started from Rico's git. Then imported 1.4.7b after downloading 
it from debian source using


```
gbp import-dsc ../sfst_1.4.7b-1.dsc
```

Now I was able to do

gbp buildpackage -uc -us


Now for the actual work.

First I downloaded the release 1.5.7 from 
https://github.com/santhoshtr/sfst/releases/tag/1.5.7 and saved it as 
../sfst_1.5.7.orig.tar.gz


Then updated debian/changelog for 1.5.7 and

gbp import-orig ../sfst_1.5.7.orig.tar.gz


Then I deleted all the patches. Also modified debian/rules to use cmake 
as follows:


%:
dh $@ --buildsystem=cmake --builddirectory=build



I also changed the manpages, install, dirs files. And the control file.

With some more hacks (to suppress dh_installdocs missing NEWS file and 
so on), I was able to build with gbp buildpackage -uc -us again


Will have to clean things up. But I've pushed to salsa for now
https://salsa.debian.org/akshay/sfst/-/commit/612e68d5c6228bfc162876b1e33ec6c97f25e9d0

In case I don't come back someone can benefit from these.

Bug#1053161: A lot of warning tex.el and latex.el and font-latex.el and ...

[Janusz S . Bień]

On Thu, Sep 28 2023 at 12:15 -03, Marcelo Laia wrote:
> Hi Ikumi,
>
> Thank you so much!
>
> I filled a bug on Debian Bug Tracking.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053161
>
> Thank you!
>
> Marcelo Laia
>
> Enviado a partir de dispositivo móvel
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> <https://lists.gnu.org/archive/html/auctex/attachments/20230928/e698c772/attachment.htm>

Install from ELPA?

Regards

JSB

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1053120: linux-image-6.1.0-12-amd64: Kernel NULL pointer deref with XFS on kernel 6.1

[S.]

00:49:20 myserver kernel:  ? asm_exc_invalid_op+0x16/0x20
Sep 27 00:49:20 myserver kernel:  ? rcu_note_context_switch+0x4ee/0x690
Sep 27 00:49:20 myserver kernel:  __schedule+0xac/0xa20
Sep 27 00:49:20 myserver kernel:  schedule+0x5d/0xe0
Sep 27 00:49:20 myserver kernel:  rwsem_down_write_slowpath+0x34e/0x730
Sep 27 00:49:20 myserver kernel:  exit_mmap+0xf6/0x2f0
Sep 27 00:49:20 myserver kernel:  __mmput+0x3e/0x130
Sep 27 00:49:20 myserver kernel:  do_exit+0x2fc/0xb10
Sep 27 00:49:20 myserver kernel:  make_task_dead+0x8d/0x90
Sep 27 00:49:20 myserver kernel:  rewind_stack_and_make_dead+0x17/0x20
Sep 27 00:49:20 myserver kernel: RIP: 0033:0x7f6e2c752345
Sep 27 00:49:20 myserver kernel: Code: Unable to access opcode bytes at 
0x7f6e2c75231b.
Sep 27 00:49:20 myserver kernel: RSP: 002b:7ffe0d2f29a0 EFLAGS: 00010206
Sep 27 00:49:20 myserver kernel: RAX: 7ffe0d2f2a14 RBX: 33b7606e 
RCX: 8003
Sep 27 00:49:20 myserver kernel: RDX: 7f6d9f67aff4 RSI: 0007 
RDI: 33b7606e
Sep 27 00:49:20 myserver kernel: RBP: 0001 R08: 7ffe0d2f2ae0 
R09: 558ffcfe7aa0
Sep 27 00:49:20 myserver kernel: R10: 7f6e2b967510 R11: 0011 
R12: 7f6d9f687fc8
Sep 27 00:49:20 myserver kernel: R13: 7f6d9dc6b888 R14: 0009 
R15: 558ffcfe7cb0
Sep 27 00:49:20 myserver kernel:  
Sep 27 00:49:20 myserver kernel: ---[ end trace  ]---
Sep 27 00:49:41 myserver kernel: rcu: INFO: rcu_preempt detected stalls on 
CPUs/tasks:
Sep 27 00:49:41 myserver kernel: rcu: Tasks blocked on level-0 rcu_node 
(CPUs 0-3): P2155714/1:b..l
Sep 27 00:49:41 myserver kernel: (detected by 3, t=5252 jiffies, 
g=242861801, q=8379 ncpus=4)
Sep 27 00:49:42 myserver kernel: rcu: INFO: rcu_preempt detected expedited 
stalls on CPUs/tasks: { P2155714 } 5276 jiffies s: 1125909 root: 0x0/T
Sep 27 00:49:42 myserver kernel: rcu: blocking rcu_node structures (internal 
RCU debug):



However the system still stays up for a few hours after that, after which it 
throws another call trace and hard crashes soon after that:



Sep 27 03:19:24 myserver sshd[2176647]: fatal: fork of unprivileged child failed
Sep 27 03:19:53 myserver kernel: rcu: INFO: rcu_preempt detected stalls on 
CPUs/tasks:
Sep 27 03:19:59 myserver kernel: rcu: Tasks blocked on level-0 rcu_node 
(CPUs 0-3): P2155714/1:b..l
Sep 27 03:20:02 myserver kernel: (detected by 1, t=2258248 jiffies, 
g=242861801, q=5722891 ncpus=4)
Sep 27 03:20:28 myserver kernel: rcu: INFO: rcu_preempt detected expedited 
stalls on CPUs/tasks: { P2155714 } 2259100 jiffies s: 1125909 root: 0x0/T
Sep 27 03:20:31 myserver kernel: rcu: blocking rcu_node structures (internal 
RCU debug):
Sep 27 03:20:50 myserver kernel: redis-server invoked oom-killer: 
gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
Sep 27 03:20:51 myserver kernel: CPU: 2 PID: 1442 Comm: redis-server Tainted: G 
 D W  6.1.0-12-amd64 #1  Debian 6.1.52-1
Sep 27 03:20:51 myserver kernel: Hardware name: Hetzner vServer/Standard PC 
(Q35 + ICH9, 2009), BIOS 2017 11/11/2017
Sep 27 03:20:51 myserver kernel: Call Trace:
Sep 27 03:20:51 myserver kernel:  
Sep 27 03:20:51 myserver kernel:  dump_stack_lvl+0x44/0x5c
Sep 27 03:20:51 myserver kernel:  dump_header+0x4a/0x211
Sep 27 03:20:51 myserver kernel:  oom_kill_process.cold+0xb/0x10
Sep 27 03:20:51 myserver kernel:  out_of_memory+0x1fd/0x4c0
Sep 27 03:20:51 myserver kernel:  __alloc_pages_slowpath.constprop.0+0xc73/0xdc0
Sep 27 03:20:51 myserver kernel:  __alloc_pages+0x305/0x330
Sep 27 03:20:51 myserver kernel:  folio_alloc+0x17/0x50
Sep 27 03:20:51 myserver kernel:  __filemap_get_folio+0x155/0x340
Sep 27 03:20:51 myserver kernel:  filemap_fault+0x139/0x910
Sep 27 03:20:51 myserver kernel:  __do_fault+0x33/0x110
Sep 27 03:20:51 myserver kernel:  do_fault+0x1b9/0x410
Sep 27 03:20:51 myserver kernel:  __handle_mm_fault+0x660/0xfa0
Sep 27 03:20:51 myserver kernel:  handle_mm_fault+0xdb/0x2d0
Sep 27 03:20:51 myserver kernel:  do_user_addr_fault+0x19c/0x570
Sep 27 03:20:51 myserver kernel:  exc_page_fault+0x70/0x170
Sep 27 03:20:51 myserver kernel:  asm_exc_page_fault+0x22/0x30
Sep 27 03:20:51 myserver kernel: RIP: 0033:0x5557864c7fb4
Sep 27 03:20:51 myserver kernel: Code: Unable to access opcode bytes at 
0x5557864c7f8a.
Sep 27 03:20:51 myserver kernel: RSP: 002b:7ffda9044ad0 EFLAGS: 00010202
Sep 27 03:20:51 myserver kernel: RAX:  RBX: 5557867ca580 
RCX: 5557866a7fad
Sep 27 03:20:51 myserver kernel: RDX: 00813000 RSI:  
RDI: 5557869defa0
Sep 27 03:20:51 myserver kernel: RBP: 011bfff0f7c0 R08: 7ffda9044aa0 
R09: 
Sep 27 03:20:51 myserver kernel: R10: 5557866fac00 R11: 555786714e83 
R12: 5557867cbbe0
Sep 27 03:20:51 myserver kernel: R13:  R14: 207e7e5d 
R15: 042e44c6
Sep 27 03:20:51 m

Bug#1052682: pipewire-pulse: Updated section in /etc/pipewire/pipewire-pulse.conf.d/ not loading module-switch-on-connect

[S.]

Hi Dylan, ah, thanks! That works. That was the only combination of options that 
I didn't try. ;-)
This bug can be closed now.

On 9/26/23 09:28, Dylan Aïssi wrote:




It works using only:

pulse.cmd = [
 { cmd = "load-module" args = "module-switch-on-connect" }
]

Bug#1052978: linux-image-6.1.0-12-amd64: After installation of 6.1.0-12-amd64, Dell Precision laptop 5520 won't boot any more from NVME SSD

[Wolfram S]

Package: linux-image-6.1.0-12-amd64
Severity: important
Tags: newcomer
X-Debbugs-Cc: debian-bugrep...@strempfer.de

Dear Maintainer,

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

   * What led up to the situation?
=> Doing a regular apt update && apt upgrade, the newer Kernel was installed
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
=> I booted the older kernel and eventually uninstalled the -12 kernel
   * What was the outcome of this action?
=> System now runs on -11 kernel, flawlessly
   * What outcome did you expect instead?
=> To be able to normally boot up system after updating the kernel

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


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

Kernel: Linux 6.1.0-11-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 linux-image-6.1.0-12-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod30+20221128-1
ii  linux-base  4.9

Versions of packages linux-image-6.1.0-12-amd64 recommends:
ii  apparmor 3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.1.0-12-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.06-13
pn  linux-doc-6.1   

Bug#1052682: pipewire-pulse: Updated section in /etc/pipewire/pipewire-pulse.conf.d/ not loading module-switch-on-connect

[S.]

Package: pipewire-pulse
Version: 0.3.65-3
Severity: normal
X-Debbugs-Cc: sb56...@gmail.com

Dear Maintainer,

I am following these instructions to enable module-switch-on-connect for
pipewire-pulse by adding just the section I want to modify in
/etc/pipewire/pipewire-pulse.conf.d/my.conf

https://docs.pipewire.org/page_module_protocol_pulse.html#autotoc_md380


pulse.cmd = [
{ cmd = "load-module" args = "module-always-sink" flags = [ ] }
{ cmd = "load-module" args = "module-switch-on-connect" }
]


However this does not work, i.e. `pactl list modules short` does not show
`module-switch-on-connect` and streams don't switch automatically when plugging
in a new USB audio device.

Yet, when I `sudo cp /usr/share/pipewire/pipewire-pulse.conf /etc/pipewire/`
and uncomment `{ cmd = "load-module" args = "module-switch-on-connect" }` it
works as expected.

Thanks, and best regards.


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

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

Versions of packages pipewire-pulse depends on:
ii  init-system-helpers  1.65.2
ii  pipewire 0.3.65-3

Versions of packages pipewire-pulse recommends:
ii  wireplumber  0.4.13-1

Versions of packages pipewire-pulse suggests:
ii  libspa-0.2-bluetooth  0.3.65-3
ii  pulseaudio-utils  16.1+dfsg1-2+b1

-- no debconf information

Bug#1052049: bacula-director: Please amend bacula-dir.conf to include subfiles

[Niels S. Richthof]

Package: bacula-director
Version: 9.6.7-7
Severity: wishlist

Dear Maintainer,

The bacula director configuration file can get very big and messy, especially 
when backing up many clients.

bacula-director supports the inclusion of subfiles in configuration files,
as documented here:
https://www.bacula.org/9.6.x-manuals/en/main/Customizing_Configuration_F.html#SECTION002023000
(This is also the case in all newer upstream versions.)

Therefore, could you please, in keeping with the way other Debian packages are 
doing this:

1. Create a new (empty) directory "/etc/bacula/bacula-dir.conf.d/"
2. Add the following snipped to "/etc/bacula/bacula-dir.conf":

   # Include subfiles associated with configuration of clients.
   # They define the bulk of the Clients, Jobs, and FileSets.
   # Remember to "reload" the Director after adding a client file.
   #
   @|"sh -c 'for f in /etc/bacula/bacula-dir.conf.d/*.conf ; do echo @${f} ; 
done'"


Thank you
Niels

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

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

Versions of packages bacula-director depends on:
ii  bacula-common  9.6.7-7
ii  bacula-director-mysql  9.6.7-7
ii  bsd-mailx [mailx]  8.1.2-0.20220412cvs-1
ii  init-system-helpers1.65.2
ii  libc6  2.36-9+deb12u1
ii  libstdc++6 12.2.0-14
ii  sysvinit-utils 3.06-4
ii  ucf3.0043+nmu1

bacula-director recommends no packages.

Versions of packages bacula-director suggests:
pn  bacula-doc  

-- no debconf information

Bug#1051548: Regression: live-build 20230502 generates corrupted images when using bookworm-backports APT pinning for kernel

[S.]

Package: live-build
X-Debbugs-Cc: wfhnb...@duck.com
Version: 20230502
Severity: normal

Hi there,

I have used live-build 20210407 on Debian 11 to successfully build a large 
number of Debian 11 based images. Now I'm using the same config and process 
with live-build 20230502 on Debian 12 to build Debian 12 based images. There 
appears to be a major regression with live-build 20230502 on Debian 12 when 
using this APT pinning:

### config/includes.chroot/etc/apt/preferences.d/99backports ###

Package: linux-image-*
Pin: release a=stable-backports
Pin-Priority: 600

Package: linux-headers-*
Pin: release a=stable-backports
Pin-Priority: 600

Package: firmware-*
Pin: release a=stable-backports
Pin-Priority: 600

Package: nvidia-driver
Pin: release a=stable-backports
Pin-Priority: 600



With that APT pinning, live-build 20210407 on Debian 11 generates a Debian 12 
ISO with the latest Debian Stable kernel (6.1.0) as well as the latest Debian 
Backports kernel (6.4.0) that successfully boots and works as expected. Here's 
a screenshot:
https://sourceforge.net/projects/spirallinux/files/dev/SpiralLinux-built-Debian11.png/download

Here's the full live-build config I'm using:
https://sourceforge.net/projects/spirallinux/files/dev/SpiralLinux-Cinnamon.tar.gz/download

However, with the exact same config but using live-build 20230502 on Debian 12, 
it generates an ISO that shows both the 6.1.0 and the 6.4.0 kernels in the live 
system GRUB boot menu (on an EFI system), but when selecting the 6.4.0 kernel 
it boots into X11 and then completely freezes. I've confirmed this same 
behavior with VirtualBox, Qemu, and real hardware. When booting into runlevel 3 
it bizarrely says I'm running the 6.4.0 kernel and yet the 6.4.0 kernel doesn't 
appear in /boot. Here's a screenshot:
https://sourceforge.net/projects/spirallinux/files/dev/SpiralLinux-built-Debian12.png/download

Just to confirm that it's not an issue with my config, I also built an image 
with https://github.com/nodiscc/debian-live-config but added the above 
mentioned APT pinning, and the exact same thing happened.

Here's the build log with live-build 20210407 on Debian 11 and the resulting 
ISO:
- 
https://sourceforge.net/projects/spirallinux/files/dev/SpiralLinux-built-Debian11.log/download
- 
https://sourceforge.net/projects/spirallinux/files/dev/SpiralLinux-test-working.iso/download
And here's the build log with live-build 20230502 on Debian 12 and the 
resulting ISO:
- 
https://sourceforge.net/projects/spirallinux/files/dev/SpiralLinux-built-Debian12.log/download
- 
https://sourceforge.net/projects/spirallinux/files/dev/SpiralLinux-test-broken.iso/download

Please let me know if you need any more information. Thanks!

Bug#375824: closed by Andreas Metzler (Re: Bug#375824: netpbm: pgmtopbm -threshold -value 160 -> usage message)

[Silas S. Brown]

That's great, thanks
-- 
Silas S. Brown http://ssb22.user.srcf.net
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#1049409: firmware-amd-graphics: Possible missing firmware for module amdgpu

[S. M.]

Package: firmware-amd-graphics
Version: 20230210-5
Severity: normal
X-Debbugs-Cc: sm.snowstorm...@passinbox.com

Dear Maintainer,

When running update-initramfs I get the following warnings:

---

Setting up linux-image-6.1.0-10-amd64 (6.1.38-2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-10-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_toc.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module 
amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin for 
module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module 
amdgpu

---

On checking the linux-firmware tree 
(https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu)
I found that some of the blobs are available there but are not in
the Debian packages. The firmware that is *in* linux-firmware are:

gc_11_0_0_mes_2.bin
gc_11_0_1_mes_2.bin
gc_11_0_2_mes_2.bin
gc_11_0_3_imu.bin
gc_11_0_3_me.bin
gc_11_0_3_mec.bin
gc_11_0_3_mes1.bin
gc_11_0_3_mes_2.bin
gc_11_0_3_pfp.bin
gc_11_0_3_rlc.bin
gc_11_0_4_me.bin
gc_11_0_4_mec.bin
gc_11_0_4_mes1.bin
gc_11_0_4_mes_2.bin
gc_11_0_4_mes.bin
gc_11_0_4_pfp.bin
gc_11_0_4_rlc.bin
psp_13_0_10_sos.bin
psp_13_0_10_ta.bin
psp_13_0_11_ta.bin
psp_13_0_11_toc.bin
sdma_6_0_3.bin
smu_13_0_10.bin


The firmware that is *not* in linux-firmware are:

ip_discovery.bin
vega10_cap.bin
sienna_cichlid_cap.bin
navi12_cap.bin
aldebaran_cap.bin
gc_11_0_0_toc.bin
sienna_cichlid_mes1.bin
sienna_cichlid_mes.bin
navi10_mes.bin
gc_11_0_3_mes.bin


Installing the firmware-linux-nonfree and firmware-misc-nonfree packages
did not correct the issue.

The firmware for amdgpu that is currently available on linux-firmware
should also be in the firmware-amd-graphics package, also while it is
outside of Debian's scope it should be investigated upstream why there
is firmware referenced that apparently is not available on linux-firmware.

I haven't noticed any functional issues caused by the missing firmware as
of yet, only warnings.

Note that I am running a custom kernel build, but this issue affects all kernel
versions including the stock Debian kernel (hence mismatch between kernel
versions in the report).

If you need further information please let me know.

Thanks!

-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stabl

Bug#1045194: virtuabox-dkms module build fails with kernel 6.4.10

[S R Wright]

Package: virtualbox-dkms
Version: 7.0.10-dfsg-2

virtualbox-dkms module build fails when done with kernel 6.4.10

Output:

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.4.10 /boot/vmlinuz-6.4.10
Error! Bad return status for module build on kernel: 6.4.10 (x86_64)
Consult /var/lib/dkms/virtualbox/7.0.10/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-6.4.10.postinst line 391.
dpkg: error processing package linux-image-6.4.10 (--install):
 installed linux-image-6.4.10 package post-installation script subprocess 
returned error exit status 2
Errors were encountered while processing:
 linux-image-6.4.10





/var/lib/dkms/virtualbox/7.0.10/build/make.log is attached
DKMS make.log for virtualbox-7.0.10 for kernel 6.4.10 (x86_64)
Sun Aug 13 02:16:25 PM CDT 2023
make: Entering directory '/nvm/src/linux-6.4.10'
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/common/string/strformatrt.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-agnostic1.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-agnostic2.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-os-specific.o
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvTracer.o: warning: objtool: SUPR0TracerFireProbe+0x7: indirect jump found in RETPOLINE build
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/SUPDrvTracer.o: warning: objtool: supdrvTracerProbeFireStub+0x0: 'naked' return found in RETHUNK build
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-os-specific.o: warning: objtool: rtThreadCtxHooksLnxSchedOut+0x1f: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-os-specific.o: warning: objtool: rtThreadCtxHooksLnxSchedIn+0x29: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-os-specific.o: warning: objtool: VBoxHost_RTR0MemKernelCopyTo+0x13: redundant CLD
/var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/combined-os-specific.o: warning: objtool: VBoxHost_RTR0MemKernelCopyFrom+0x13: redundant CLD
  LD [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxdrv/vboxdrv.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/VBoxNetFlt.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/SUPR0IdcClient.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/SUPR0IdcClientComponent.o
  CC [M]  /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c: In function ‘vboxNetFltLinuxForwardToIntNetInner’:
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1570:40: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘skb_gso_reset’? [-Werror=implicit-function-declaration]
 1570 | struct sk_buff *pSegment = skb_gso_segment(pBuf, 0 /*supported features*/);
  |^~~
  |skb_gso_reset
/var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1570:40: warning: initialization of ‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:252: /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.o] Error 1
make[1]: *** [scripts/Makefile.build:497: /var/lib/dkms/virtualbox/7.0.10/build/vboxnetflt] Error 2
make: *** [Makefile:2032: /var/lib/dkms/virtualbox/7.0.10/build] Error 2
make: Leaving directory '/nvm/src/linux-6.4.10'

Bug#1042874: unable to reproduce the problem

[Janusz S . Bień]

On Wed, Aug 02 2023 at  8:23 +02, Janusz S. Bień wrote:
> On Wed, Aug 02 2023 at  6:09 GMT, Debian Bug Tracking System wrote:
>> Thank you for filing a new Bug report with Debian.
>>
>> You can follow progress on this Bug here: 1042874: 
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042874.
>
> There was an encoding problem with quoting the error message, so I
> enclosed it in the attachment.

I've upgraded AUCTeX to the current version and I'm unable now to
reproduce the problem. I'm still curious what information is encoded in
the error message and I will try to look into it.

Regards

JSB

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1043007: sane: xerox_mfp not working

[Janusz S . Bień]

Package: sane
Version: 1.0.14-13+b1
Severity: normal
X-Debbugs-Cc: none, Janusz S. Bień 

sbien@jsbdebian:~$ scanimage --list-devices
device `xerox_mfp:tcp  192.168.0.155' is a Samsung M2070 Series multi-function 
peripheral
jsbien@jsbdebian:~$ scanimage > image.pnm
Output format is not set, using pnm as a default.
Not a JPEG file: starts with 0x00 0x00

After the system upgrade the scanner is not accessible from GIMP, which
used to work before.

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

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

Versions of packages sane depends on:
ii  libc6   2.36-9+deb12u1
ii  libgimp2.0  2.10.34-1
ii  libglib2.0-02.74.6-2
ii  libgtk2.0-0 2.24.33-2
ii  libsane1 [libsane]  1.2.1-2

sane recommends no packages.

Versions of packages sane suggests:
ii  gimp  2.10.34-1

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1042874: Acknowledgement (auctex: )

[Janusz S . Bień]

On Wed, Aug 02 2023 at  6:09 GMT, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1042874: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042874.

There was an encoding problem with quoting the error message, so I
enclosed it in the attachment.

Regards - Janusz

LaTeX-label: Wrong type argument: symbolp, #[128 "ÀÁ\"‡" [apply reftex-label 
reftex-label nil] 4 nil nil]


-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1037039: rsyslog - SysV init file missing

[Narayanan R S]

Package: rsyslog
Version: 8.2302.0-1~bpo11+1

Can you please reinstate the missing /etc/init.d/rsyslog file in the
package?

>From the changelog notes, it appears to have been removed (intentionally)
in version 8.2110.0-2.

I'm not clear on why this is removed - one can continue to use a SysV init
and so this file is useful/important in systems that do not use systemd to
launch rsyslog. While I understand that ryslog's priority has been demoted
from important to optional (per
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018788), I see no reason
to exclude the SysV init file from the package

Thank you.

Narayanan.

Bug#1034577: Bug exists also for banks using Fiducia

[S. Seide]

Same problem exists for old Fiducia based HBCI servers as GAD and 
Fiducia joined now to Atruvia...


My bank uses https://hbci11.fiducia.de/cgi-bin/hbciservlet as HBCI url 
with the same problem.


New certificate CN is "fints2.atruvia.de" and old fiducia DNS name are 
listed as SubjectAltNames. But AQBanking shows an certificate warning.


As this problem affects a lot of german users - is there a change to 
promote this package to stable to fix this false security warning?


Thanks for the fast fix,
S. Seide

Bug#1035056: Disappointed

[x s]

It’s really disappointing that the only reason for blocking Plasma 5.27.5 and 
Frameworks 5.104 is that there’s “too many packages”. 

KDE upstream has stopped feature development for Plasma 5.x and Frameworks 5.x 
with the releases of Plasma 5.27.0 and Frameworks 5.100, because the focus has 
completely switched to developing Plasma 6.0 and Frameworks 6.0 [1] [this link 
also explains the Fibonacci release cycle that you asked about].

That means Plasma 5.27.x and Frameworks 5.1xx are strictly only bug fix 
releases, they contain absolutely no new features and no major regressions have 
been reported in the newer versions. Just check the changelogs for every Plasma 
release since 5.27.2 and every Frameworks release since 5.103 (the versions 
Testing is stuck on), there have been *hundreds* of bugs fixed since. 
Cherry-picking fixes for the most prominent crashes just isn’t practical 
considering especially how many bugs were fixed in Plasma 5.27.3 alone. 

I’d like to remind you that GNOME 43.4 was allowed to migrate recently; why 
does GNOME get special treatment and KDE has to stay stuck on an older, buggier 
version? Debian KDE users would strongly appreciate you changing your stance 
and allowing the best versions to be included on release.

If you still are not convinced on allowing these to be unblocked, would you at 
least consider allowing them to migrate for the Debian 12.1 point release? 
Again, I’d like to remind you that these are long-term support releases, they 
strictly fix bugs and contain no new features. There are absolutely no 
downsides to allowing them to migrate so they can be in Debian 12. 

Thank you for your consideration and your hard work maintaining Debian.

[1] https://community.kde.org/Schedules/Plasma_5 - “This is the last Plasma 5 
release and will receive bugfixes only, no new features. The bugfixes are 
intended to continue being integrated into 5.27 until a first version of Plasma 
6 can be released (and might continue longer).”

Bug#1035833: cpptraj: autopkgtest failure everywhere except on amd64

[Kiran S Kunjumon]

Source: cpptraj
Version:  5.1.0+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You package cpptraj has an autopkgtest, great.
However, it fails everywhere except on amd64. Can you please investigate the 
situation and fix it?

I copied some of the output at the bottom of this report.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation


https://qa.debian.org/excuses.php?package=cpptraj

https://ci.debian.net/data/autopkgtest/unstable/arm64/c/cpptraj/33255796/log.gz

=== FAILURES
===
TEST: /tmp/autopkgtest-lxc.kz5vbtvg/downtmp/build.qgE/src/test/Test_SPAM

  CPPTRAJ: SPAM Test
../MasterTest.sh: line 495:  3218 Killed  $cpptraj_cmd >> 
$CPPTRAJ_OUTPUT
Error:  cpptraj exited with status 137

  CPPTRAJ: SPAM Pure Solvent Test

  1 out of 2 executions exited with an error.
  2 out of 5 comparisons failed.

--
TEST: /tmp/autopkgtest-lxc.kz5vbtvg/downtmp/build.qgE/src/test/Test_SetVelocity

  CPPTRAJ: Set Velocity test

  CPPTRAJ: Scale velocity test

  1 out of 3 comparisons failed.

= TEST SUMMARY ==
  850 out of 859 comparisons OK (3 failed, 0 warnings, 6 skipped).
  479 out of 480 program executions completed.
  168 out of 173 tests completed with no issues.
  2 tests skipped.
=
make: *** [Makefile:662: summary] Error 4
make: Leaving directory 
'/tmp/autopkgtest-lxc.kz5vbtvg/downtmp/build.qgE/src/test'
autopkgtest [15:20:47]: test command1: ---]
autopkgtest [15:20:47]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 2
autopkgtest [15:20:47]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
../MasterTest.sh: line 495:  3218 Killed  $cpptraj_cmd >> 
$CPPTRAJ_OUTPUT
Error:  cpptraj exited with status 137
make: *** [Makefile:662: summary] Error 4
autopkgtest [15:20:48]:  summary
command1 FAIL non-zero exit status 2



OpenPGP_0x0D598BD7BC822E10.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034412: release-notes: Information about manpages-l10n for bookworm release notes

[McIntyre, Vincent (S&A, Marsfield)]

On Thu, Apr 27, 2023 at 10:07:29PM +0200, Holger Wansing wrote:
>Control: tags -1 + patch
>
>I would like to propose the attached patch for this report (mostly grabbed
>from Helge's text).
>
>-- 
>Holger Wansing 
>PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

>diff --git a/en/whats-new.dbk b/en/whats-new.dbk
>index bf290b89..91a878c4 100644
>--- a/en/whats-new.dbk
>+++ b/en/whats-new.dbk
>@@ -414,6 +414,18 @@ Some descriptions of the ports: 
>https://www.debian.org/ports/
>   
> 
> 
>+
>+  
>+  Greatly expanded translations of man pages
>+  
>+Thank to many efforts of our translators, the translation of many

'Thanks' here

>+manpages has been greatly expanded (e.g. we have complete translation
>+of systemd user pages into German now) and various new languages have
>+been added (Czech, Danish, Greek, Finnish, Indonesian, Macedonian,
>+Norwegian, Russian, Serbian, Swedish, Ukranian and Vietnamesian).

I think 'Vietnamese' is correct here.

Kind regards
Vince

Bug#1034430: kodi-inputstream-adaptive: crash when resuming video

[david s]

Package: kodi-inputstream-adaptive
Version: 20.3.2+ds-1
Severity: important
X-Debbugs-Cc: d...@fastmail.com

Dear Maintainer,

When resuming a Youtube video, Kodi will crash with the following stack
trace:

Thread 1 (Thread 0x7ff6751026c0 (LWP 100225)):
#0  0x7ff771d63ccc in  () at /lib/x86_64-linux-gnu/libc.so.6
#1  0x7ff771d14ef2 in raise () at /lib/x86_64-linux-gnu/libc.so.6
#2  0x7ff771cff472 in abort () at /lib/x86_64-linux-gnu/libc.so.6
#3  0x7ff771cff395 in  () at /lib/x86_64-linux-gnu/libc.so.6
#4  0x7ff771d0ddf2 in  () at /lib/x86_64-linux-gnu/libc.so.6
#5  0x7ff686d82a65 in webm::UnknownParser::Feed(webm::Callback*, 
webm::Reader*, unsigned long*) () at /usr/lib/x86_64-linux-gnu/libwebm.so.1
#6  0x7ff686d833f1 in webm::WebmParser::Feed(webm::Callback*, 
webm::Reader*) () at /usr/lib/x86_64-linux-gnu/libwebm.so.1
#7  0x7ff67a602558 in  () at 
/usr/lib/x86_64-linux-gnu/kodi/addons/inputstream.adaptive/inputstream.adaptive.so.20.3.2
#8  0x7ff67a5eef0d in  () at 
/usr/lib/x86_64-linux-gnu/kodi/addons/inputstream.adaptive/inputstream.adaptive.so.20.3.2
#9  0x7ff67a5eeef9 in  () at 
/usr/lib/x86_64-linux-gnu/kodi/addons/inputstream.adaptive/inputstream.adaptive.so.20.3.2
#10 0x7ff67a5f846b in  () at 
/usr/lib/x86_64-linux-gnu/kodi/addons/inputstream.adaptive/inputstream.adaptive.so.20.3.2
#11 0x7ff67a5b0189 in  () at 
/usr/lib/x86_64-linux-gnu/kodi/addons/inputstream.adaptive/inputstream.adaptive.so.20.3.2
#12 0x5650984cfb6e in CDVDDemuxClient::Read() ()
#13 0x565098552d26 in CVideoPlayer::ReadPacket(DemuxPacket*&, 
CDemuxStream*&) ()
#14 0x56509855a21d in CVideoPlayer::Process() ()
#15 0x565098809a45 in CThread::Action() ()
#16 0x56509880b46e in  ()
#17 0x56509880bfab in  ()
#18 0x7ff771ad44a3 in  () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#19 0x7ff771d61fd4 in  () at /lib/x86_64-linux-gnu/libc.so.6
#20 0x7ff771de266c in  () at /lib/x86_64-linux-gnu/libc.so.6


I noticed that the Debian version is patched to use a packaged libwebm
while upstream is using a much older version. Recompiling without this
patch seems to fix the issue, but more testing is needed.

I can provide further logs upon request

~ds

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-7-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kodi-inputstream-adaptive depends on:
ii  kodi [kodi-api-inputstream]  2:20.1+dfsg-1
ii  libc62.36-9
ii  libexpat12.5.0-1
ii  libgcc-s112.2.0-14
ii  libstdc++6   12.2.0-14
ii  libwebm1 1.0.0.29-1

kodi-inputstream-adaptive recommends no packages.

kodi-inputstream-adaptive suggests no packages.

-- no debconf information

Bug#1034207: okular: typewriter annotation ignores some letters

[Janusz S . Bień]

On Tue, Apr 11 2023 at  8:34 +02, Janusz S. Bień wrote:
> Package: okular
> Version: 4:20.12.3-2
> Severity: normal
> X-Debbugs-Cc: none, Janusz S. Bień 
>
> Looks like the annotation ignores non-ASCII letters, cf. the attachment.
>

Does this

https://bugs.kde.org/show_bug.cgi?id=445674

mean that the problem was solved upstream?

JSB

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1034207: okular: typewriter annotation ignores some letters

[Janusz S . Bień]

Package: okular
Version: 4:20.12.3-2
Severity: normal
X-Debbugs-Cc: none, Janusz S. Bień 

Looks like the annotation ignores non-ASCII letters, cf. the attachment.

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

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

Versions of packages okular depends on:
ii  kinit 5.78.0-2
ii  kio   5.78.0-5
ii  libc6 2.31-13+deb11u5
ii  libfreetype6  2.10.4+dfsg-1+deb11u1
ii  libjpeg62-turbo   1:2.0.6-4
ii  libkf5activities5 5.78.0-2
ii  libkf5archive55.78.0-2
ii  libkf5bookmarks5  5.78.0-2
ii  libkf5codecs5 5.78.0-2
ii  libkf5completion5 5.78.0-3
ii  libkf5configcore5 5.78.0-4
ii  libkf5configgui5  5.78.0-4
ii  libkf5configwidgets5  5.78.0-2
ii  libkf5coreaddons5 5.78.0-4
ii  libkf5crash5  5.78.0-3
ii  libkf5i18n5   5.78.0-2
ii  libkf5iconthemes5 5.78.0-2
ii  libkf5itemviews5  5.78.0-2
ii  libkf5jobwidgets5 5.78.0-2
ii  libkf5kexiv2-15.0.0   20.12.0-1
ii  libkf5kiocore55.78.0-5
ii  libkf5kiowidgets5 5.78.0-5
ii  libkf5parts5  5.78.0-3
ii  libkf5pty55.78.0-2
ii  libkf5purpose-bin 5.78.0-2
ii  libkf5purpose55.78.0-2
ii  libkf5service-bin 5.78.0-2
ii  libkf5service55.78.0-2
ii  libkf5textwidgets55.78.0-2
ii  libkf5wallet-bin  5.78.0-2
ii  libkf5wallet5 5.78.0-2
ii  libkf5widgetsaddons5  5.78.0-2
ii  libkf5windowsystem5   5.78.0-2
ii  libkf5xmlgui5 5.78.0-2
ii  libokular5core9   4:20.12.3-2
ii  libphonon4qt5-4   4:4.11.1-4
ii  libpoppler-qt5-1  20.09.0-3.1+deb11u1
ii  libqmobipocket2   4:20.12.0-1
ii  libqt5core5a  5.15.2+dfsg-9
ii  libqt5dbus5   5.15.2+dfsg-9
ii  libqt5gui55.15.2+dfsg-9
ii  libqt5printsupport5   5.15.2+dfsg-9
ii  libqt5svg55.15.2-3
ii  libqt5texttospeech5   5.15.2-2
ii  libqt5widgets55.15.2+dfsg-9
ii  libqt5xml55.15.2+dfsg-9
ii  libspectre1   0.2.9-1
ii  libstdc++610.2.1-6
ii  phonon4qt54:4.11.1-4
ii  zlib1g1:1.2.11.dfsg-2+deb11u2

Versions of packages okular recommends:
ii  cups-bsd  2.3.3op2-3+deb11u2

Versions of packages okular suggests:
ii  ghostscript9.53.3~dfsg-7+deb11u4
pn  okular-extra-backends  
ii  poppler-data   0.4.10-1
ii  texlive-binaries   2020.20200327.54578-7
ii  unrar  1:6.0.3-1+deb11u1

-- no debconf information



test.pdf
Description: Adobe PDF document


-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1033168: zeal: inaccurate man page

[Louie S.]

Package: zeal
Version: 1:0.6.1-1.2~bpo11+1
Severity: normal
X-Debbugs-Cc: lshpr...@tutanota.com

Dear Maintainer,

The zeal man page is inaccurate (most likely out of date) regarding the
`OPTIONS` section. The options listed by the help message differ from those
listed in the man page. In particular, the `-q` or `--query` option listed in
the man page appears to be obsolete.


-- 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_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 zeal depends on:
ii  libarchive13   3.4.3-2+deb11u1
ii  libc6  2.31-13+deb11u5
ii  libgcc-s1  10.2.1-6
ii  libqt5concurrent5  5.15.2+dfsg-9
ii  libqt5core5a   5.15.2+dfsg-9
ii  libqt5gui5 5.15.2+dfsg-9
ii  libqt5network5 5.15.2+dfsg-9
ii  libqt5sql5-sqlite  5.15.2+dfsg-9
ii  libqt5webkit5  5.212.0~alpha4-11
ii  libqt5widgets5 5.15.2+dfsg-9
ii  libqt5x11extras5   5.15.2-2
ii  libsqlite3-0   3.34.1-3
ii  libstdc++6 10.2.1-6
ii  libx11-6   2:1.7.2-1
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb11.14-3

zeal recommends no packages.

zeal suggests no packages.

Bug#1033128: 2.16.2-2 breaks pylint in emacs

[Brent S. Elmer]

Package: pylint
Version: 2.16.2-2
Severity: normal
X-Debbugs-Cc: webe...@aim.com

I upgraded pylint from 2.15.10-1 to 2.16.2-2 and emacs can no longer find
pylint.  Pylint works from a terminal but emacs can no longer find pylint.  In
my .emacs file I have require pylint and emacs cannot load pylint after the
pylint upgrade.  Reverting pylint to 2.15.10-1 makes pylint work again in
emacs.  Another upgrade of some package(maybe emacs?) removed pylint from the
python menu in emacs in python mode.  That is when I had to start using alt-x
pylint in emacs to run it since it was no longer in the menu.


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

Kernel: Linux 6.1.0-5-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 pylint depends on:
ii  python33.11.2-1
ii  python3-astroid2.14.2-1
ii  python3-dill   0.3.6-1
ii  python3-isort  5.6.4-1
ii  python3-logilab-common 1.9.8-1
ii  python3-mccabe 0.7.0-1
ii  python3-platformdirs   2.6.0-1
ii  python3-setuptools 66.1.1-1
ii  python3-tomli  2.0.1-2
ii  python3-tomlkit0.11.6-1
ii  python3-typing-extensions  4.4.0-1

Versions of packages pylint recommends:
ii  python3-tk  3.11.2-2

Versions of packages pylint suggests:
pn  pylint-doc  

-- no debconf information

Bug#1025141: powermgmt-base: Doesn't correctly detect we are on AC power

[Raymond S Brand]

Followup to Santiago's report:

The script is also reporting that my Dell 3260CFF (Compact Form Factor) 
is not on AC power when it is since it doesn't have a battery option.


The following may be of some help:

$ sh -x /sbin/on_ac_power
+ set -e
+ OFF_LINE_P=no
+ [ -d /sys/class/power_supply/ ]
+ test -d /sys/class/power_supply/hidpp_battery_0
+ test -r /sys/class/power_supply/hidpp_battery_0/type
+ cat /sys/class/power_supply/hidpp_battery_0/type
+ type=Battery
+ test -d /sys/class/power_supply/ucsi-source-psy-USBC000:001
+ test -r /sys/class/power_supply/ucsi-source-psy-USBC000:001/type
+ cat /sys/class/power_supply/ucsi-source-psy-USBC000:001/type
+ type=USB
+ [ -r /sys/class/power_supply/ucsi-source-psy-USBC000:001/online ]
+ cat /sys/class/power_supply/ucsi-source-psy-USBC000:001/online
+ online=0
+ [ 0 = 1 ]
+ [ 0 = 0 ]
+ OFF_LINE_P=yes
+ [ yes = yes ]
+ exit 1
$

The H/W doesn't actually have a battery option but does use a laptop 
style power brick or USB-C to supply power.

Bug#1030909: Unable to run xscreensaver-demo or xscreensaver-settings

[H. S. Teoh]

On Fri, Feb 10, 2023 at 08:58:41AM +0100, Tormod Volden wrote:
> On Fri, Feb 10, 2023 at 1:18 AM H. S. Teoh wrote:
> 
> > xscreensaver-settings: 16:11:29: xscreensaver-gl-visual did not report a GL 
> > visual!
> > Segmentation fault
> > --snip---
> >
> > Apparently there *is* a segfault, even though it doesn't appear that way
> > when I run the official binaries.  This looks to be the same bug as
> > #1030659 after all.
> 
> Teoh, can you please apply the patch I posted in #1030659 to get rid
> of the segfault?

Hi Tormod,

Sorry for taking so long to get back to you.  Here's the output after I
recompiled with the patch:

--snip---
xscreensaver-settings: 11:15:48: DISPLAY=:0.0
xscreensaver-settings: 11:15:48: added "/usr/libexec/xscreensaver" to $PATH
xscreensaver-settings: 11:15:48: pref changed: GtkSpinButton
xscreensaver-settings: 11:15:48: pref changed: GtkSpinButton
xscreensaver-settings: 11:15:48: pref changed: GtkSpinButton
xscreensaver-settings: 11:15:48: pref changed: GtkSpinButton
xscreensaver-settings: 11:15:48: pref changed: GtkSpinButton
xscreensaver-settings: 11:15:48: pref changed: GtkSpinButton
xscreensaver-settings: 11:15:48: pref changed: GtkSpinButton
xscreensaver-settings: 11:15:48: pref changed: GtkCheckButton
xscreensaver-settings: 11:15:48: pref changed: GtkCheckButton
xscreensaver-settings: 11:15:48: pref changed: GtkCheckButton
xscreensaver-settings: 11:15:48: pref changed: GtkRadioButton
xscreensaver-settings: 11:15:48: pref changed: GtkRadioButton
xscreensaver-settings: 11:15:48: list selection changed
xscreensaver-settings: 11:15:48: scheduling preview "moebiusgears --root"
xscreensaver-settings: 11:15:48: 
/usr/local/share/xscreensaver/config/moebiusgears.xml does not exist.
xscreensaver-settings: 11:15:48: scheduling preview "moebiusgears --root"
xscreensaver-settings: 11:15:48: 
/usr/local/share/xscreensaver/config/moebiusgears.xml does not exist.
xscreensaver-settings: 11:15:48: scheduling preview "moebiusgears --root"
xscreensaver-settings: 11:15:48: select list elt 145
xscreensaver-settings: 11:15:48: scheduling preview "moebiusgears --root"
xscreensaver-settings: 11:15:48: 
/usr/local/share/xscreensaver/config/moebiusgears.xml does not exist.
xscreensaver-settings: 11:15:48: scheduling preview "moebiusgears --root"
xscreensaver-settings: 11:15:48: xscreensaver-gl-visual did not report a GL 
visual!
xscreensaver-settings: 11:15:48: couldn't convert X Visual 0x0 to a GdkVisual; 
winging it.
xscreensaver-settings: 11:15:48: using default visual 0x0
xscreensaver-settings: 11:15:48: saved screenshot 0x1a00010 1920x1080 for 
window 0x1af 425x238+437+116

xscreensaver-settings: 11:15:48: X error:
xscreensaver-settings:   Failed request: BadMatch (invalid parameter attributes)
xscreensaver-settings:   Major opcode:   42 (X_SetInputFocus)
xscreensaver-settings:   Resource id:0x1a7
xscreensaver-settings:   Serial number:  451 / 452
--snip---


> In your first post (with the Debian binaries)
> xscreensaver-gl-visual reported 0x21, and there was no segfault. I
> wonder why xscreensaver-gl-visual is giving different results. Debian
> is not patching anything in this regard, although build flags can be
> different in your local build. Can you please attach your config.h?
> Did you install all standard build dependencies for xscreensaver?
[...]

I did an `apt-get builddep xscreensaver`.  That ought to have been
enough, right?

Here's my config.h:

--snip---
/* config.h.  Generated from config.h.in by configure.  */
/* config.h.in.  Generated from configure.ac by autoheader.  */


/* xscreensaver, Copyright © 1991-2022 Jamie Zawinski.
 * Generate this file by running 'configure' rather than editing it by hand.
 */


/* Define this to allow root to unlock, when not using PAM. */
/* #undef ALLOW_ROOT_PASSWD */

/* Define to 1 if translation of program messages to the user's native
   language is requested. */
#define ENABLE_NLS 1

/* This is the name of the gettext package to use. */
#define GETTEXT_PACKAGE "xscreensaver"

/* Define this if gettimeofday takes two arguments. */
#define GETTIMEOFDAY_TWO_ARGS 1

/* Define this for Solaris getpwanam. */
/* #undef HAVE_ADJUNCT_PASSWD */

/* Define to 1 if you have the Mac OS X function
   CFLocaleCopyPreferredLanguages in the CoreFoundation framework. */
/* #undef HAVE_CFLOCALECOPYPREFERREDLANGUAGES */

/* Define to 1 if you have the Mac OS X function CFPreferencesCopyAppValue in
   the CoreFoundation framework. */
/* #undef HAVE_CFPREFERENCESCOPYAPPVALUE */

/* Define to 1 if you have the  header file. */
#define

Bug#1030982: gscan2pdf: Not a JPEG file: starts with 0x00 0x00 (was: Segmentation fault)

[Janusz S . Bień]

On Sat, Feb 11 2023 at 14:03 GMT, Jeff wrote:
> I still don't understand. The log you provided covered a successful
> scan, with a couple of post-processing steps.
>
> Please provide a log where the scan job failed.

As I said earlier, I provided it already.

On Fri, Feb 10 2023 at 12:33 +01, Janusz S. Bień wrote:
> On Fri, Feb 10 2023 at 10:55 GMT, Jeff wrote:
>> There's no segfault there.
>
> It was at first trial, but I'm unable now to reproduce it.
>
>>
>> Please start gscan2pdf from the command line with the --log=log
>> option, if necessary, hit OK to select the crashed session, reproduce
>> the problem (i.e. the segfaul), quit, and post the log file, which
>> gscan2pdf may have compressed with xz.
>
> Now gscan2pdf offers the choice of two devices (physically it is the same
> devices), one of them works.
>
> The failure log is missing the line which appeared on the terminal:
>
> Not a JPEG file: starts with 0x00 0x00

This mail had two attachments.

The failure log was
[log1 (application/octet-stream, attachment)]

If you want something else, please specify it explicitely.

Regards - Janusz

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1030982: gscan2pdf: Segmentation fault

[Janusz S . Bień]

On Fri, Feb 10 2023 at 12:54 GMT, Jeff wrote:
> In the log you provide, you seem to have a successful scan. Is the
> problem therefore only the warning message?

It's binary: either it works or not, depending on the choice of the device.

>
> If the other device does not work, please provide a log file created
> when scanning with the other device.

It was attached to my previous mail.


On Fri, Feb 10 2023 at 12:33 +01, Janusz S. Bień wrote:

[...]

> The failure log is missing the line which appeared on the terminal:
>
> Not a JPEG file: starts with 0x00 0x00


Regards - Janusz

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1030982: gscan2pdf: Segmentation fault

[Janusz S . Bień]

On Fri, Feb 10 2023 at  8:35 GMT, Jeff wrote:
> Please start gscan2pdf from the command line with the --log=log
> option, reproduce the problem, quit, and post the log file, which
> gscan2pdf may have compressed with xz.
>

Enclosed.

Regards- Janusz




log
Description: log

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1030306: xsane experiments

[Janusz S . Bień]

xsane finds the device twice, at smfp:net and as xerox_mfp:tcp.
Using xerox_mfp:tcp fails with
Not a JPEG file: starts with 0x00 0x00

Using smfp:net seems to work.

Janusz

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1030982: gscan2pdf: Segmentation fault

[Janusz S . Bień]

Package: gscan2pdf
Version: 2.11.0-1
Severity: grave
X-Debbugs-Cc: none, Janusz S. Bień 
 
Not a JPEG file: starts with 0x00 0x00

The same bug occurs in simple-scan, cf.  Bug#1030306.

The device is  Samsung Xpress M2070FW connected by Wi-Fi, scanning with
GIMP and printing works.

I will appreciate your help.

Janusz

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

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

Versions of packages gscan2pdf depends on:
ii  imagemagick8:6.9.11.60+dfsg-1.3
ii  imagemagick-6.q16 [imagemagick]8:6.9.11.60+dfsg-1.3
ii  libconfig-general-perl 2.63-1
ii  libdate-calc-perl  6.4-1.1
ii  libfilesys-df-perl 0.92-6+b6
ii  libgoocanvas2-perl 0.06-2
ii  libgtk3-imageview-perl 6-1
ii  libgtk3-perl   0.038-1
ii  libgtk3-simplelist-perl0.21-1
ii  libhtml-parser-perl3.75-1+b1
ii  libimage-magick-perl   8:6.9.11.60+dfsg-1.3
ii  libimage-sane-perl 5-1+b1
ii  liblist-moreutils-perl 0.430-2
ii  liblocale-codes-perl   3.66-1
ii  liblocale-gettext-perl 1.07-4+b1
ii  liblog-log4perl-perl   1.54-1
ii  libossp-uuid-perl [libdata-uuid-perl]  1.6.2-1.5+b9
ii  libpdf-builder-perl3.021-2
ii  libproc-processtable-perl  0.59-2+b1
ii  libreadonly-perl   2.050-3
ii  librsvg2-common2.50.3+dfsg-1
ii  libset-intspan-perl1.19-1.1
ii  libtiff-tools  4.2.0-1+deb11u3
ii  libtry-tiny-perl   0.30-1
ii  sane-utils 1.0.31-4.1

Versions of packages gscan2pdf recommends:
ii  djvulibre-bin   3.5.28-2
ii  pdftk   2.02-5+b1
ii  pdftk-java [pdftk]  3.2.2-1
ii  tesseract-ocr   4.1.3-2
ii  unpaper 6.1-2+b2
ii  xdg-utils   1.1.3-4.1

gscan2pdf suggests no packages.

-- no debconf information

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1030909: Unable to run xscreensaver-demo or xscreensaver-settings

[H. S. Teoh]

On Thu, Feb 09, 2023 at 11:16:15AM +0100, Tormod Volden wrote:
> On Thu, Feb 9, 2023 at 10:20 AM Tormod Volden wrote:
> > Would it be possible for you to build the upstream sources, without
> > optimization, and try it out? You shouldn't need to install any of
> > it, just run driver/xscreensaver-settings --debug from the build
> > tree. And also rename your ~/.xscreensaver so that it runs with
> > default settings.
> 
> Now it gets a bit complicated if we don't want to install it, but at
> the same time let the built xscreensaver-settings find the
> screensavers from the already installed Debian packages, we need to
> set the exec-prefix. In this case do not run make install afterwards!
> >From unpacked upstream sources:
> 
> ./configure CFLAGS="-g -O0" --exec-prefix=/usr
> make -j4
> driver/xscreensaver-settings --debug
[...]

Here is the output:

--snip---
$ driver/xscreensaver-settings --debug 
xscreensaver-settings: 16:11:29: DISPLAY=:0.0
xscreensaver-settings: 16:11:29: added "/usr/libexec/xscreensaver" to $PATH
xscreensaver-settings: 16:11:29: pref changed: GtkSpinButton
xscreensaver-settings: 16:11:29: pref changed: GtkSpinButton
xscreensaver-settings: 16:11:29: pref changed: GtkSpinButton
xscreensaver-settings: 16:11:29: pref changed: GtkSpinButton
xscreensaver-settings: 16:11:29: pref changed: GtkSpinButton
xscreensaver-settings: 16:11:29: pref changed: GtkSpinButton
xscreensaver-settings: 16:11:29: pref changed: GtkSpinButton
xscreensaver-settings: 16:11:29: pref changed: GtkCheckButton
xscreensaver-settings: 16:11:29: pref changed: GtkCheckButton
xscreensaver-settings: 16:11:29: pref changed: GtkCheckButton
xscreensaver-settings: 16:11:29: pref changed: GtkRadioButton
xscreensaver-settings: 16:11:29: pref changed: GtkRadioButton
xscreensaver-settings: 16:11:29: list selection changed
xscreensaver-settings: 16:11:29: scheduling preview "polytopes -root -polytope 
120-cell"
xscreensaver-settings: 16:11:29: 
/usr/local/share/xscreensaver/config/polytopes.xml does not exist.
xscreensaver-settings: 16:11:29: scheduling preview "polytopes -root -polytope 
120-cell"
xscreensaver-settings: 16:11:29: 
/usr/local/share/xscreensaver/config/polytopes.xml does not exist.
xscreensaver-settings: 16:11:29: scheduling preview "polytopes -root -polytope 
120-cell"
xscreensaver-settings: 16:11:29: select list elt 168
xscreensaver-settings: 16:11:29: scheduling preview "polytopes -root -polytope 
120-cell"
xscreensaver-settings: 16:11:29: 
/usr/local/share/xscreensaver/config/polytopes.xml does not exist.
xscreensaver-settings: 16:11:29: scheduling preview "polytopes -root -polytope 
120-cell"
xscreensaver-settings: 16:11:29: xscreensaver-gl-visual did not report a GL 
visual!
Segmentation fault
--snip---

Apparently there *is* a segfault, even though it doesn't appear that way
when I run the official binaries.  This looks to be the same bug as
#1030659 after all.


T

-- 
If it tastes good, it's probably bad for you.

Bug#1030909: Unable to run xscreensaver-demo or xscreensaver-settings

[H. S. Teoh]

On Thu, Feb 09, 2023 at 08:57:22PM +0100, Tormod Volden wrote:
> > Since upgrading to 6.06+dfsg1-2, I have been unable to run
> > xscreensaver-settings or xscreensaver-demo.  The main xscreensaver
> 
> >From which version did you upgrade?

5.45+dfsg1-2


T

-- 
Written on the window of a clothing store: No shirt, no shoes, no service.

Bug#1030914: firmware-brcm80211 causes system to freeze and reboot

[Mathirajan S. Manoharan]

i installed 20230117-2 from unstable. Also installed 
20221214-5
 from the archive.


Both have similar issues on my system. For a moment everything looks fine and 
wifi starts working. In a few minutes the system freezes and after a little 
while it reboots.


I managed to capture just a little more information from dmesg this time before 
the system froze


[5.792752] brcmsmac bcma0:1: firmware: direct-loading firmware 
brcm/bcm43xx-0.fw
[5.793398] brcmsmac bcma0:1: firmware: direct-loading firmware 
brcm/bcm43xx_hdr-0.fw
[5.821173] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false 
(implement)
[5.821190] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: 
false (implement)
[5.873283] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false 
(implement)
[5.873297] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: 
false (implement)
[5.879522] r8188eu 1-3:1.0: firmware: direct-loading firmware 
rtlwifi/rtl8188eufw.bin
[5.879537] r8188eu 1-3:1.0: Firmware Version 11, SubVersion 1, Signature 
0x88e1
[7.880849] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false 
(implement)
[7.880861] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: 
false (implement)
[7.922274] wlp2s0b1: authenticate with cc:40:d0:bf:a6:9b
[7.922291] wlp2s0b1: 80 MHz not supported, disabling VHT
[7.924184] wlp2s0b1: send auth to cc:40:d0:bf:a6:9b (try 1/3)
[7.932168] wlp2s0b1: authenticated
[7.933930] wlp2s0b1: associate with cc:40:d0:bf:a6:9b (try 1/3)
[7.941922] wlp2s0b1: RX AssocResp from cc:40:d0:bf:a6:9b (capab=0x1411 
status=0 aid=12)
[7.944845] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: 
associated
[7.944854] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true 
(implement)
[7.944869] wlp2s0b1: associated
[7.963442] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211:  txop exceeded 
phylen 159/256 dur 1778/1504
[7.992602] brcmsmac bcma0:1: wl0: brcms_c_d11hdrs_mac80211:  txop exceeded 
phylen 137/256 dur 1602/1504
[8.034158] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0b1: link becomes ready
[9.068221] brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 
addresses (implement)
[9.432645] IPv6: ADDRCONF(NETDEV_CHANGE): wlx00e02dba0563: link becomes 
ready
[   12.674154] usb 1-5.4: reset high-speed USB device number 7 using xhci_hcd
[   52.564491] wlp2s0b1: deauthenticating from cc:40:d0:bf:a6:9b by local 
choice (Reason: 3=DEAUTH_LEAVING)
[   52.630119] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: 
disassociated
[   52.630140] brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 
addresses (implement)
[   52.630148] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false 
(implement)
[   52.713824] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false 
(implement)
[   52.713844] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: 
false (implement)


Please let me know if you need any more logs. I can upload them.

Bug#1030852: unable to run "aideinit" successfully

[David S]

Hi,

File "aide-common_0.17.3-4+deb11u1_all.deb" contains
"/usr/share/aide/config/aide/aide.conf.d/31_aide_munin-nodes"
where the three lines below are present :

printf
"/var/cache/munin/www/%s/(index\\.html|%s/[-_[:alnum:]]+\\.(png|html))$ f
VarFile" "${DOMAIN}*\\n*" "${DHOST}"
printf "/var/lib/munin/%s/%s-.*\\.rrd$ f VarFile" "${DOMAIN}" "${DHOST}*\\n*
"
printf "/@@{RUN}/munin/munin-(update|datafile|%s-%s|limits)\\.lock$ f
VarFile\\n" "${DOMAIN}" "${DHOST}

when I run aideinit without changes, this doesn't work. When I correct the
file like that :

printf
"/var/cache/munin/www/%s/(index\\.html|%s/[-_[:alnum:]]+\\.(png|html))$ f
VarFile*\\n*" "${DOMAIN}" "${DHOST}"
printf "/var/lib/munin/%s/%s-.*\\.rrd$ f VarFile*\\n*" "${DOMAIN}" "${DHOST}
"
printf "/@@{RUN}/munin/munin-(update|datafile|%s-%s|limits)\\.lock$ f
VarFile\\n" "${DOMAIN}" "${DHOST}

it works.

>>   I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13
>>   and libc6 2.1.3-10.
>Are you joking?

Sorry for that, it's a copy/paste that I forgot to update. Here is the good
configuration :
Linux 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux

Regards,

David

On Wed, 8 Feb 2023 at 17:17, Marc Haber 
wrote:

> Control: tags -1 moreinfo unreproducible
> thanks
>
> On Wed, Feb 08, 2023 at 02:01:13PM +0100, David S wrote:
> >   When I invoke `aideinit' without arguments from an ordinary shell
> >   prompt it prints:
> >
> > `ERROR: /etc/aide/aide.conf.d/31_aide_munin-nodes (stdout):1:
> > unexpected character: '/' (line:
> >
> '/var/cache/munin/www/uaegeas1/(index\.html|uaegeas1\n/[-_[:alnum:]]+\.(png|html))$
> > f VarFile/var/lib/munin/uaegeas1/uaegeas1\n-.*\.rrd$ f
> >
> VarFile/@@{RUN}/munin/munin-(update|datafile|uaegeas1-uaegeas1|limits)\.lock$
> > f VarFile')
>
> This does not happen on current sid. Can you show bash -x
> /etc/aide/aide.conf.d/31_aide_munin-nodes output and probably your
> munin.conf file? This looks like the parsing of your munin.conf
> incorrectly includes line feeds into the parsed HOSTS variable.
>
> >   I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13
> >   and libc6 2.1.3-10.
>
> Are you joking?
>
> Grüße
> Marc
>
>
>

Bug#1030914: firmware-brcm80211 causes system to freeze and reboot

[Mathirajan S. Manoharan]

Package: firmware-brcm80211
Version: 20221214-5
Severity: important
X-Debbugs-Cc: mathi...@hotmail.com

Dear Maintainer,

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

   * What led up to the situation?

My system has the following network card
02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43225 
802.11b/g/n [14e4:4357] (rev 01)

If i install the firmware for this card (firmware-brcm80211), the system 
freezes and reboots by itself.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

install the firmware with the command "sudo nala install firmware-brcm80211"
This causes the system to freeze and reboot.

I could not even collect any logs. When the system boots up, "dmesg" is clean. 
There are no errors.

Please let me know if there is somewhere else i should be looking for logs, 
errors and useful info to troubleshoot this issue.

   * What was the outcome of this action?

Installing the firmware gets the network card to work. But in a short while (1 
min approx) the system freezes and reboots.

   * What outcome did you expect instead?

I expect the system to funtion normally and not freeze/reboot

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


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

Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
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

firmware-brcm80211 depends on no packages.

firmware-brcm80211 recommends no packages.

Versions of packages firmware-brcm80211 suggests:
ii  initramfs-tools  0.142

Bug#1030909: Unable to run xscreensaver-demo or xscreensaver-settings

[H. S. Teoh]

Package: xscreensaver
Version: 6.06+dfsg1-2
Severity: important

Since upgrading to 6.06+dfsg1-2, I have been unable to run
xscreensaver-settings or xscreensaver-demo.  The main xscreensaver
binary still runs and works correctly; however, I can no longer
configure which screensavers show up except by editing .xscreensaver by
hand.  So marking this as important.

Here's the typical output from xscreensaver-settings:

xscreensaver-settings: 15:24:45: X error:
xscreensaver-settings:   Failed request: BadMatch (invalid parameter 
attributes)
xscreensaver-settings:   Major opcode:   42 (X_SetInputFocus)
xscreensaver-settings:   Resource id:0x187
xscreensaver-settings:   Serial number:  440 / 441

Here's the output from xscreensaver-settings --debug:

xscreensaver-settings: 15:25:11: DISPLAY=:0
xscreensaver-settings: 15:25:11: added "/usr/libexec/xscreensaver" to 
$PATH
xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton
xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton
xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton
xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton
xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton
xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton
xscreensaver-settings: 15:25:11: pref changed: GtkSpinButton
xscreensaver-settings: 15:25:11: pref changed: GtkCheckButton
xscreensaver-settings: 15:25:11: pref changed: GtkCheckButton
xscreensaver-settings: 15:25:11: pref changed: GtkCheckButton
xscreensaver-settings: 15:25:11: pref changed: GtkRadioButton
xscreensaver-settings: 15:25:11: pref changed: GtkRadioButton
xscreensaver-settings: 15:25:11: list selection changed
xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root"
xscreensaver-settings: 15:25:11: reading 
/usr/share/xscreensaver/config/hextrail.xml...
xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root"
xscreensaver-settings: 15:25:11: reading 
/usr/share/xscreensaver/config/hextrail.xml...
xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root"
xscreensaver-settings: 15:25:11: select list elt 114
xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root"
xscreensaver-settings: 15:25:11: reading 
/usr/share/xscreensaver/config/hextrail.xml...
xscreensaver-settings: 15:25:11: scheduling preview "hextrail --root"
xscreensaver-settings: 15:25:12: xscreensaver-gl-visual says the GL 
visual is 0x21.
xscreensaver-settings: 15:25:12: using non-default visual 0x21
xscreensaver-settings: 15:25:12: saved screenshot 0x1800010 1920x1080 
for window 0x18f 425x238+437+116

xscreensaver-settings: 15:25:12: X error:
xscreensaver-settings:   Failed request: BadMatch (invalid parameter 
attributes)
xscreensaver-settings:   Major opcode:   42 (X_SetInputFocus)
xscreensaver-settings:   Resource id:0x187
xscreensaver-settings:   Serial number:  440 / 441

I found bug #1030659, which seems to be related to this issue (it also
has the X_SetInputFocus error), but in my case there is no segfault so I
decided to file a separate bug.

Some other information that may be pertinent:
- CPU: AMD Ryzen 7 5700G with Radeon Graphics
- GPU: Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)
- glxinfo output: please see attached.
- Desktop environment: none, using minimal XDM + ratpoison as WM.

Possibly relevant packages:

hi  ratpoison  1.4.8-2+b1amd64keyboard-only 
window manager
ii  xdm1:1.1.11-3+b2 amd64X display manager
ii  xserver-common 2:21.1.6-1all  common files used 
by various X servers
ii  xserver-xorg-core  2:21.1.6-1amd64Xorg X server - 
core server
ii  xserver-xorg-input-evdev   1:2.10.6-2+b1 amd64X.Org X server -- 
evdev input driver
ii  xserver-xorg-input-kbd 1:1.9.0-1+b3  amd64X.Org X server -- 
keyboard input driver
ii  xserver-xorg-input-libinput1.2.1-1+b1amd64X.Org X server -- 
libinput input driver
ii  xserver-xorg-input-mouse   1:1.9.3-1+b1  amd64X.Org X server -- 
mouse input driver
ii  xserver-xorg-video-amdgpu  22.0.0-3  amd64X.Org X server -- 
AMDGPU display driver


T

-- 
Recently, our IT department hired a bug-fix engineer. He used to work for 
Volkswagen.

Bug#1030852: unable to run "aideinit" successfully

[David S]

Package: aide
  Version: 0.17.3-4+deb11u1

  When I invoke `aideinit' without arguments from an ordinary shell
  prompt it prints:

`ERROR: /etc/aide/aide.conf.d/31_aide_munin-nodes (stdout):1:
unexpected character: '/' (line:
'/var/cache/munin/www/uaegeas1/(index\.html|uaegeas1\n/[-_[:alnum:]]+\.(png|html))$
f VarFile/var/lib/munin/uaegeas1/uaegeas1\n-.*\.rrd$ f
VarFile/@@{RUN}/munin/munin-(update|datafile|uaegeas1-uaegeas1|limits)\.lock$
f VarFile')

  I suggest that /etc/aide/aide.conf.d/31_aide_munin-nodes should be
corrected on two lines with correctly placed line feed :

printf "/var/cache/munin/www/%s/(index\\.html|%s/[-_[:alnum:]]+\\.(png|html))$
f VarFile\\n" "${DOMAIN}" "${DHOST}"

printf "/var/lib/munin/%s/%s-.*\\.rrd$ f VarFile\\n" "${DOMAIN}" "${DHOST}"


  I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13
  and libc6 2.1.3-10.

Bug#1030741: firmware-brcm80211: Package firmware-brcm80211 not found in bookworm

[Mathirajan S. Manoharan]

hi Salvatore,

Thank you for your prompt replies.

The system hang is unpredictable. When it reboots after the hang, there are no 
errors on "dmesg".
How and where can i find the relevant logs, errors which could help to 
troubleshoot this issue?

regards,
-Mathi

From: Salvatore Bonaccorso  on behalf of 
Salvatore Bonaccorso 
Sent: Tuesday, February 7, 2023 1:21 PM
To: Mathirajan S. Manoharan 
Cc: 1030...@bugs.debian.org <1030...@bugs.debian.org>
Subject: Re: Bug#1030741: firmware-brcm80211: Package firmware-brcm80211 not 
found in bookworm

Hi Mathi,

On Tue, Feb 07, 2023 at 06:45:03PM +0000, Mathirajan S. Manoharan wrote:
> Thank you very much. I was able to install this package
> firmware-brcm80211 to get the wifi card working on my pc.
>
> But i'm running into a strange problem now. The system freezes and
> reboots after a few seconds. I have never experienced anything like
> this with Linux past several years.
>
> If i boot into single user mode and uninstall this package
> firmware-brcm80211, the system functions normally.
>
> If i install firmware-brcm80211, this makes the system unstable. The
> system freezes and reboots.
>
> Should i file a new bug for this?

Not good :(

yes can you please fill a new bug for this issue, please make sure to
attach as well kernel dmesg from the system, ideally if we catch the
error.

Regards,
Salvatore

Bug#1030741: firmware-brcm80211: Package firmware-brcm80211 not found in bookworm

[Mathirajan S. Manoharan]

Thank you very much. I was able to install this package firmware-brcm80211 to 
get the wifi card working on my pc.

But i'm running into a strange problem now. The system freezes and reboots 
after a few seconds. I have never experienced anything like this with Linux 
past several years.

If i boot into single user mode and uninstall this package firmware-brcm80211, 
the system functions normally.

If i install firmware-brcm80211, this makes the system unstable. The system 
freezes and reboots.

Should i file a new bug for this?

regards,
-Mathi


From: Salvatore Bonaccorso 
Sent: Monday, February 6, 2023 9:43 PM
To: Mathirajan S. Manoharan ; 
1030741-d...@bugs.debian.org <1030741-d...@bugs.debian.org>
Cc: Debian Bug Tracking System 
Subject: Re: Bug#1030741: firmware-brcm80211: Package firmware-brcm80211 not 
found in bookworm

Hi,

On Mon, Feb 06, 2023 at 08:05:29PM -0800, Mathirajan S. Manoharan wrote:
> Package: firmware-brcm80211
> Severity: important
> X-Debbugs-Cc: mathi...@hotmail.com
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>
> I'm using bookworm as my desktop OS. I have the following wireless card.
>
> 02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43225 
> 802.11b/g/n [14e4:4357] (rev 01)
>
> This card is not working. It displays a message that "Firmware is missing".
>
>60.592279] brcmsmac bcma0:1: firmware: failed to load brcm/bcm43xx-0.fw 
> (-2)
> [   60.593680] firmware_class: See https://wiki.debian.org/Firmware for 
> information about missing firmware
> [   60.594859] brcmsmac bcma0:1: firmware: failed to load brcm/bcm43xx-0.fw 
> (-2)
>
>
> i already have firmware-linux-free, firmware-iwlwifi, firmware-misc-nonfree 
> installed on my system. None of these have the file brcm/bcm43xx-0.fw
>
> I also tried installing "firmware-b43-installer". This also didn't install 
> the required files. So, the wifi card is unusable on bookwork.
>
> I found that the package firmware-brcm80211 has these files, but it is not 
> present in bookworm repo

It is in bookworm, but it moved to the non-free-firmware archive
component (cf.
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#non-free-split)

Regards,
Salvatore

Bug#1030741: firmware-brcm80211: Package firmware-brcm80211 not found in bookworm

[Mathirajan S. Manoharan]

Package: firmware-brcm80211
Severity: important
X-Debbugs-Cc: mathi...@hotmail.com

Dear Maintainer,

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

   * What led up to the situation?

I'm using bookworm as my desktop OS. I have the following wireless card.

02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43225 
802.11b/g/n [14e4:4357] (rev 01)

This card is not working. It displays a message that "Firmware is missing".

   60.592279] brcmsmac bcma0:1: firmware: failed to load brcm/bcm43xx-0.fw (-2)
[   60.593680] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   60.594859] brcmsmac bcma0:1: firmware: failed to load brcm/bcm43xx-0.fw (-2)


i already have firmware-linux-free, firmware-iwlwifi, firmware-misc-nonfree 
installed on my system. None of these have the file brcm/bcm43xx-0.fw

I also tried installing "firmware-b43-installer". This also didn't install the 
required files. So, the wifi card is unusable on bookwork.

I found that the package firmware-brcm80211 has these files, but it is not 
present in bookworm repo

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * 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: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
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

Bug#1030306: simple-scan: Not a JPEG file: starts with 0x00 0x00

[Janusz S . Bień]

On Sat, Feb 04 2023 at 12:50 +01, Jörg Frings-Fürst wrote:
> Hello Janusz,
>
>
> can you send the output of
>
> - avahi-browse -rt _uscan._tcp
> - avahi-browse -rt _ipp._tcp

I had to install avahi-utils.

Both commands give no output.

> - scanimage -L

device `xerox_mfp:tcp  192.168.0.155' is a Samsung M2070 Series multi-function 
peripheral

> and the files
>
> - /etc/sane.d/net.conf
> - /etc/sane.d/xerox_mfp.conf
> - /etc/sane.d/dll.conf

Attached.

Best regards

Janusz



net.conf
Description: net.conf


xerox_mfp.conf
Description: xerox_mfp.conf


dll.conf
Description: dll.conf



-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1030306: simple-scan: Not a JPEG file: starts with 0x00 0x00

[Janusz S . Bień]

option_descriptor (6)
[+16.81s] DEBUG: scanner.vala:760: Option 6: name='geometry' title='Geometry' 
type=group size=4
[+16.81s] DEBUG: scanner.vala:763:   Description: Scan area and media size 
options
[+16.81s] DEBUG: scanner.vala:910: sane_get_option_descriptor (7)
[+16.81s] DEBUG: scanner.vala:760: Option 7: name='tl-x' title='Top-left x' 
type=fixed size=4 unit=mm min=0.00, max=216.069321, quant=65536 
cap=soft-select,soft-detect
[+16.81s] DEBUG: scanner.vala:763:   Description: Top-left x position of scan 
area.
[+16.81s] DEBUG: scanner.vala:910: sane_get_option_descriptor (8)
[+16.81s] DEBUG: scanner.vala:760: Option 8: name='tl-y' title='Top-left y' 
type=fixed size=4 unit=mm min=0.00, max=297.179993, quant=65536 
cap=soft-select,soft-detect
[+16.81s] DEBUG: scanner.vala:763:   Description: Top-left y position of scan 
area.
[+16.81s] DEBUG: scanner.vala:910: sane_get_option_descriptor (9)
[+16.81s] DEBUG: scanner.vala:760: Option 9: name='br-x' title='Bottom-right x' 
type=fixed size=4 unit=mm min=0.00, max=216.069321, quant=65536 
cap=soft-select,soft-detect
[+16.81s] DEBUG: scanner.vala:763:   Description: Bottom-right x position of 
scan area.
[+16.81s] DEBUG: scanner.vala:910: sane_get_option_descriptor (10)
[+16.81s] DEBUG: scanner.vala:760: Option 10: name='br-y' title='Bottom-right 
y' type=fixed size=4 unit=mm min=0.00, max=297.179993, quant=65536 
cap=soft-select,soft-detect
[+16.81s] DEBUG: scanner.vala:763:   Description: Bottom-right y position of 
scan area.
[+16.81s] DEBUG: scanner.vala:910: sane_get_option_descriptor (11)
[+16.81s] DEBUG: scanner.vala:571: sane_control_option (5, 
SANE_ACTION_SET_VALUE, source="Auto") -> (SANE_STATUS_GOOD, "Auto")
[+16.81s] DEBUG: scanner.vala:571: sane_control_option (3, 
SANE_ACTION_SET_VALUE, mode="Color") -> (SANE_STATUS_GOOD, "Color")
[+16.81s] DEBUG: scanner.vala:483: sane_control_option (2, 
SANE_ACTION_SET_VALUE, resolution=300) -> (SANE_STATUS_GOOD, 300)
[+16.81s] DEBUG: scanner.vala:523: sane_control_option (9, 
SANE_ACTION_SET_VALUE, br-x=148.00) -> (SANE_STATUS_GOOD, 148.00)
[+16.81s] DEBUG: scanner.vala:523: sane_control_option (10, 
SANE_ACTION_SET_VALUE, br-y=210.00) -> (SANE_STATUS_GOOD, 210.00)
[+16.94s] DEBUG: app-window.vala:2065: Saving state to 
/home/jsbien/.cache/simple-scan/state
[+17.86s] DEBUG: app-window.vala:2065: Saving state to 
/home/jsbien/.cache/simple-scan/state
[+21.95s] DEBUG: scanner.vala:1284: sane_start (page=0, pass=0) -> 
SANE_STATUS_GOOD
[+21.95s] DEBUG: scanner.vala:1321: sane_get_parameters () -> SANE_STATUS_GOOD
[+21.95s] DEBUG: scanner.vala:1333: Parameters: format=SANE_FRAME_RGB 
last_frame=SANE_TRUE bytes_per_line=5244 pixels_per_line=1748 lines=2522 depth=8
[+21.96s] DEBUG: simple-scan.vala:1712: Page is 1748 pixels wide, 2522 pixels 
high, 8 bits per pixel
[+21.96s] DEBUG: simple-scan.vala:1646: Getting color profile for device 
xerox_mfp:tcp  192.168.0.155
[+21.97s] DEBUG: simple-scan.vala:1666: Unable to find colord device 
xerox_mfp:tcp  192.168.0.155: property match 'Serial'='sane:xerox_mfp:tcp  
192.168.0.155' does not exist
Not a JPEG file: starts with 0x00 0x00
jsbien@JSBbuster:~$
--8<---cut here---end--->8---


When I print, the device is recognized as two, and only one works. I
decided to live with it and not trying to solve it.

At first simple-scan also was finding two devices and one of them
worked. Now it finds only one them, the non-working one...

However I have vague memories that the problem occurred also from time
to time with USB connection.

Best regards

Janusz

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1030306: simple-scan: Not a JPEG file: starts with 0x00 0x00

[Janusz S . Bień]

Package: simple-scan
Version: 3.38.1-1
Severity: grave
X-Debbugs-Cc: none, Janusz S. Bień 

Dear Maintainer,

-- Package-specific info:
-- BEGIN ATTACHMENTS --
/tmp/tmp.dgtNgi4r0Z/logfile.user
/tmp/tmp.dgtNgi4r0Z/scanimage.user
/tmp/tmp.dgtNgi4r0Z/lsusb.user
-- END ATTACHMENTS --

After I switched Samsung Xpress M2070FW from USB to W-Fi practically every 
attempt to scan ends
with this bug. Scanning with GIMP and SANE still works.

I will appreciate your help.

Regards - Janusz

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

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

Versions of packages simple-scan depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.24-0+deb11u1
ii  dbus-x11 [dbus-session-bus]   1.12.24-0+deb11u1
ii  dconf-gsettings-backend [gsettings-backend]   0.38.0-2
ii  libc6 2.31-13+deb11u5
ii  libcairo2 1.16.0-5
ii  libcolord21.4.5-3
ii  libgdk-pixbuf2.0-02.40.2-2
ii  libglib2.0-0  2.66.8-1
ii  libgtk-3-03.24.24-4+deb11u2
ii  libgusb2  0.3.5-1
ii  libpackagekit-glib2-181.2.2-2
ii  libsane1  1.0.31-4.1
ii  libwebp6  0.6.1-2.1
ii  libwebpmux3   0.6.1-2.1
ii  xdg-utils 1.1.3-4.1
ii  zlib1g1:1.2.11.dfsg-2+deb11u2

simple-scan recommends no packages.

simple-scan suggests no packages.

-- no debconf information

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1029257: webcamoid: segmentation fault

[Janusz S . Bień]

On Fri, Jan 20 2023 at 12:19 GMT, Barak A. Pearlmutter wrote:

[...]

> So I'm going to mark this as done as of 9.0.0-5, after merging it with
> 979029 which seems to be the same issue.

OK

Best regards

Janusz

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1029257: webcamoid: segmentation fault

[Janusz S . Bień]

Package: webcamoid
Version: 8.6.1+dfsg-2.1
Severity: grave
X-Debbugs-Cc: none, Janusz S. Bień 

Hi!

The first try:

--8<---cut here---start->8---
webcamoid 
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
WARNING: Cannot find style "Universal" - fallback: 
"/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Desktop"
qrc:/Webcamoid/share/qml/RecordConfig.qml:82:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/RecordConfig.qml:74:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/RecordConfig.qml:126:5: QML Label: Detected anchors on 
an item that is managed by a layout. This is undefined behavior; use 
Layout.alignment instead.
qrc:/Webcamoid/share/qml/EffectConfig.qml:58:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/EffectConfig.qml:53:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/AudioInfo.qml:190:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/MediaConfig.qml:46:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/MediaConfig.qml:40:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/OutputConfig.qml:35:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/VirtualCamera/share/qml/main.qml:47:5: QML Connections: Implicitly defined 
onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo() { ... }
qrc:/Webcamoid/share/qml/RecordBar.qml:87:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/EffectBar.qml:93:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/AudioConfig.qml:78:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/MediaBar.qml:53:5: QML Connections: Implicitly defined 
onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo() { ... }
qrc:/Webcamoid/share/qml/main.qml:127:5: QML Connections: Implicitly defined 
onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo() { ... }
qrc:/Webcamoid/share/qml/main.qml:122:5: QML Connections: Implicitly defined 
onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo() { ... }
qrc:/Webcamoid/share/qml/main.qml:117:5: QML Connections: Implicitly defined 
onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo() { ... }
qrc:/Webcamoid/share/qml/main.qml:102:5: QML Connections: Implicitly defined 
onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo() { ... }
qrc:/Webcamoid/share/qml/OutputConfig.qml:26:1: QML OutputConfig: Detected 
anchors on an item that is managed by a layout. This is undefined behavior; use 
Layout.alignment instead.
qrc:/MultiSink/share/qml/main.qml:144:5: QML Connections: Implicitly defined 
onFoo properties in Connections are deprecated. Use this syntax instead: 
function onFoo() { ... }
Segmentation fault
--8<---cut here---end--->8---

The second try:

--8<---cut here---start->8---
jsbien@jsbdebian:~$ export QT_QPA_PLATFORM=wayland
jsbien@jsbdebian:~$ webcamoid 
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use 
QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QSocketNotifier: Can only be used with threads started with QThread
WARNING: Cannot find style "Universal" - fallback: 
"/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Desktop"
qrc:/Webcamoid/share/qml/RecordConfig.qml:82:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function onFoo() { ... }
qrc:/Webcamoid/share/qml/RecordConfig.qml:74:5: QML Connections: Implicitly 
defined onFoo properties in Connections are deprecated. Use this syntax 
instead: function

Bug#991815:

[Akshay S Dinesh]

I tried to do some work on this in here: https://salsa.debian.org/akshay/sfst/

Was facing issues with debian build not succeeding.

That led to two PRs in the upstream repo. But once those were merged I didn't 
get a chance to try this again.

I think with the latest version from upstream it would be easier to get the 
debian package working.

As of now I'm finding it hard to find time for this. So, if anyone else wants 
to work on this, please feel free to!

Bug#1021685: upgrading from 40.1-1 to 43.0-2 breaks xfce

[Brent S. Elmer Ph.D.]

Is this bug going to be looked into?  This is still a problem
preventing me from upgrading the package.  If there is additional
information that could be collected let me know the steps to collect
the information.

Brent

On Wed, 12 Oct 2022 17:33:53 -0500 "Brent S. Elmer" 
wrote:
> Package: libwnck3
> Version: libwnck-3-0
> Severity: normal
> X-Debbugs-Cc: webe...@aim.com
> 
> When I upgrade from 40.1-1 to 43.0-2 on a debian testing system, xfce
breaks.
> I see no xfce items at all on the screen(i.e. top bar, application
menu, bottom
> bar, desktop icons)
> I am accessing the machine through x2go.  I am not near the machine
to see if
> xfce works directly on the machine.  When I downgrade to 40.1-1 then
xfce works
> again.
> 
> I see these lines over and over in syslog.
> 
> Oct 12 16:58:49 mj04lv70 x2gogetstatus: db_getstatus called, session
ID:
> bselme-50-1665611527_stDXFCE_dp32, return value: R
> Oct 12 16:58:51 mj04lv70 x2gocleansessions: executing external
command
> ,,/usr/lib/x2go/x2golistsessions_sql'' with args: mj04lv70.ds.xxx.com
> Oct 12 16:58:51 mj04lv70 x2golistsessions_sql: executing external
command
> ,,x2gopath'' with args: libexec
> Oct 12 16:58:51 mj04lv70 x2golistsessions_sql: executing external
command
> ,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
> listsessionsroot,mj04lv70.ds.xxx.com
> 
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.19.0-2-amd64 (SMP w/16 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
> 
> 

Bug#1023658: clipit: Please change base to newer repo

[S.]

Package: clipit
Version: 1.4.4+git20190202-2
Severity: important
X-Debbugs-Cc: sb56...@gmail.com


Hello, would it be possible to change the base of the clipit package to this 
newer fork?
https://github.com/CristianHenzel/ClipIt

The clipit 1.4.4+git20190202-2 version has a number of major bugs, like 
selecting the wrong item from history, and it comes with that weird /usr/bin/ 
redirect to Diodon.

The CristianHenzel fork is what most other Linux distros use for their Clipit 
package. I installed the version 1.4.5+git20210313-1bionicppa1 for Ubuntu on my 
Debian Stable system, and it works much better than the Debian version.

Clipit is an extremely important utility for my workflow, and for the Cinnamon 
or Mate or Budgie desktop environments there are really no other options for a 
clipboard manager with a long and editable history manager option, I've tried 
them all.

Thanks a lot.

Bug#1021685: upgrading from 40.1-1 to 43.0-2 breaks xfce

[Brent S. Elmer]

Package: libwnck3
Version: libwnck-3-0
Severity: normal
X-Debbugs-Cc: webe...@aim.com

When I upgrade from 40.1-1 to 43.0-2 on a debian testing system, xfce breaks.
I see no xfce items at all on the screen(i.e. top bar, application menu, bottom
bar, desktop icons)
I am accessing the machine through x2go.  I am not near the machine to see if
xfce works directly on the machine.  When I downgrade to 40.1-1 then xfce works
again.

I see these lines over and over in syslog.

Oct 12 16:58:49 mj04lv70 x2gogetstatus: db_getstatus called, session ID:
bselme-50-1665611527_stDXFCE_dp32, return value: R
Oct 12 16:58:51 mj04lv70 x2gocleansessions: executing external command
,,/usr/lib/x2go/x2golistsessions_sql'' with args: mj04lv70.ds.xxx.com
Oct 12 16:58:51 mj04lv70 x2golistsessions_sql: executing external command
,,x2gopath'' with args: libexec
Oct 12 16:58:51 mj04lv70 x2golistsessions_sql: executing external command
,,/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper'' with args:
listsessionsroot,mj04lv70.ds.xxx.com


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/16 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

Bug#1018873: live-build --firmware-chroot option is broken due to nvidia-tesla{-470,}-kernel-support

[S.]

On Mon, 05 Sep 2022 16:24:45 + Witold Baryluk  
wrote:

Package: nvidia-tesla-kernel-support
Followup-For: Bug #1018873
X-Debbugs-Cc: witold.bary...@gmail.com

Just for reference if somebody needs to workaround this quickly, this patch 
should help:

--- /usr/share/live/build/functions/firmwarelists.sh2022-09-05 
16:23:22.053130441 +
+++ /usr/share/live/build/functions/firmwarelists.sh.new2022-09-05 
16:22:05.412045133 +
@@ -48,7 +48,7 @@
fi
 
	local PACKAGES

-   PACKAGES="$(gunzip -c "${CONTENTS_FILE}" | awk 
'/^lib\/firmware/ { print $2 }' | sort -u )"
+   PACKAGES="$(gunzip -c "${CONTENTS_FILE}" | awk 
'/^lib\/firmware/ { print $2 }' | grep -v nvidia | sort -u)"
FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} ${PACKAGES}"
 
	# Don't waste disk space, if not making use of caching






Apply from /, with patch -p0 < nvidia-fix.patch


Thank you!! This was driving me crazy, I couldn't figure out why my recent builds were 
including nvidia-* packages by default when none of the requested packages needed them as 
dependencies. I can't get the patch to apply, it fails with "Hunk #1 FAILED at 
48." But I manually edited /usr/share/live/build/functions/firmwarelists.sh with 
your workaround and it does the job.

Bug#1019461: ipheth-utils: iPhone SE 1st Gen. doesn't negotiate a ip out of the dhcp pool with the computer

[Jannick S.]

Package: ipheth-utils
Version: 1.0-5
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
I am trying to connect my iPhone Se 1st Gen USB Hotspot to my Linux PC, that 
runs Kubuntu 22.04.1 LTS. Following a guide online I installed ipheth-utils, 
usbmuxd, libimobiledevice and libimobiledevice-utils.
I connected my phone and the greenbar on the top of the phone designated that a 
device had connected to my phone over usb (since I have wlan and bluetooth 
off.) Though if I ran 'ip a' I could clearly see that
my ip address had been set to a fallback IP address and not one in the range of 
the DHCP pool of my phone (172.20.10.0 - 172.20.10.15). A logical solution for 
me was to set my network settings manually
to be in the range of the phone and was greeted with a connection confirmed. 
Weirdly when I pinged 172.20.10.1 (the phone) I got 'Destination Host 
Unreachable'. I also couldn't connect to any websites. Thinking
it might be a conflict between KDE and ipheth utils I switched to a blank 
raspberry pi. Getting the same result. When I tried to renegotiate the ip with 
'dhclient -v eth1' no change was found. 
In dmesg the connection also was always confirmed.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
After 5 hours of headscratching I tried the newer iPhone Se 2nd Gen of my 
brother, while not changing a thing, only setting the network interface back to 
automatic. The Computer was directly given a ip in the pool.
This got me to think that it might be a version mismatch between ipheth-utils 
and my older iPhone.

Some Information about my iPhone:
Model: iPhone SE 1st Gen
iOS Version: 15.6.1


-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
Architecture: armv7l

Kernel: Linux 5.15.61-v7+ (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 ipheth-utils depends on:
ii  libc6  2.31-13+rpt2+rpi1+deb11u4
ii  libimobiledevice6  1.3.0-6

ipheth-utils recommends no packages.

ipheth-utils suggests no packages.

-- no debconf information

Bug#1019153: php-horde-turba: fatal error: $name must be a string

[s...@uni-paderborn.de (Cyrus)]

Apparently in
/usr/share/horde/turba/lib/Driver/Share.php:47
the change from create to createFromConfig is missing.

If changed manually it seems to work like intended

Regards,
Sebastian

Bug#987116: firmware-iwlwifi: AX20* bluetooth random disconnects

[S.]

Hi there, for those that have tried the newer version of the firmware and 
didn't see any improvements, it turns out that you have to **power-cycle** (not 
just reboot) the machine after installing the newer firmware package. Some 
users even recommend pulling the laptop battery and letting it sit for a few 
minutes:

https://www.reddit.com/r/debian/comments/x0rfwu/psa_fix_for_ax200_random_bluetooth_headset/

I made a request to the Backports folks for the 20210818-1 version to be 
backported. This is a major bug in the Debian Stable version, so it would be 
great if it could be updated there too, but I don't know if the Debian Stable 
policies would allow that.

Bug#1014659: logrotate: error: state file /var/lib/logrotate/status is world-readable

[McIntyre, Vincent (S&A, Marsfield)]

I am seeing this issue as well.

In particular I see it with a state file that, when I check,
is mode 0640.  e.g.
error: state file /var/log/rsync/.logrotate.status.rsync_ is world-readable
and thus can be locked from other unprivileged users.
Skipping lock acquisition..

These are the state and config files
-rw-r-  1 root root145 Jul 18 01:30 .logrotate.status.rsync_
-rw-r--r--  1 root root162 Apr 25 02:30 .logrotate.conf.rsync_


But when I try to reproduce the issue (below), it goes away.

testbox-142% ls -al
total 1912
   4 drwx-- 3 joe staff4096 Jul 18 09:13 ./
   4 drwxrwxrwt 6 root   root4096 Jul 18 09:08 ../
   4 -rw-r--r-- 1 joe staff 212 Jul 18 09:08 conf
   4 -rw-r- 1 joe staff  71 Jul 18 09:10 state.groupread
   4 -rw--- 1 joe staff 112 Jul 18 09:12 state.ownerread
   4 -rw-r--r-- 1 joe staff 112 Jul 18 09:13 state.worldread
1884 -rw-r--r-- 1 joe staff 1925683 Jul 18 02:02 test.log

% cat conf
/var/tmp/test/test.log {
missingok
create 0644
compress
daily
rotate 7
# log will be rotated when larger than this,
# but only if the minimum time interval has passed
minsize 5M
}

% /usr/sbin/logrotate -v -s state.worldread  conf
reading config file conf
error: state file state.worldread is world-readable and thus can be locked from 
other unprivileged users. Skipping lock acquisition...
Reading state from file: state.worldread
Allocating hash table for state file, size 64 entries
Creating new state

Handling 1 logs

rotating pattern: /var/tmp/test/test.log  after 1 days (7 rotations)
empty log files are rotated, only log files >= 5242880 bytes are rotated, old 
logs are removed
considering log /var/tmp/test/test.log
Creating new state
  Now: 2022-07-18 09:13
  Last rotated at 2022-07-18 09:00
  log does not need rotating (log has already been rotated)


% /usr/sbin/logrotate -v -s state.groupread conf
reading config file conf
Reading state from file: state.groupread
Allocating hash table for state file, size 64 entries
Creating new state

Handling 1 logs

rotating pattern: /var/tmp/test/test.log  after 1 days (7 rotations)
empty log files are rotated, only log files >= 5242880 bytes are rotated, old 
logs are removed
considering log /var/tmp/test/test.log
Creating new state
  Now: 2022-07-18 09:14
  Last rotated at 2022-07-18 09:00
  log does not need rotating (log has already been rotated)

% /usr/sbin/logrotate -v -s state.ownerread conf
reading config file conf
Reading state from file: state.ownerread
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state

Handling 1 logs

rotating pattern: /var/tmp/test/test.log  after 1 days (7 rotations)
empty log files are rotated, only log files >= 5242880 bytes are rotated, old 
logs are removed
considering log /var/tmp/test/test.log
  Now: 2022-07-18 09:15
  Last rotated at 2022-07-18 09:00
  log does not need rotating (log has already been rotated)

% cat state.worldread
logrotate state -- version 2
"/var/tmp/test//test.log" 2022-2-21-2:0:0
"/var/tmp/test/test.log" 2022-7-18-9:0:0
% cat state.groupread
logrotate state -- version 2
"/var/tmp/test//test.log" 2022-2-21-2:0:0
"/var/tmp/test/test.log" 2022-7-18-9:0:0
% cat state.ownerread
logrotate state -- version 2
"/var/tmp/test//test.log" 2022-2-21-2:0:0
"/var/tmp/test/test.log" 2022-7-18-9:0:0

At this point I discovered that rotatelog changes the world-readable
state file to mode 0640, so a subsequent run works ok.

% /usr/sbin/logrotate -v -s state.worldread conf
reading config file conf
Reading state from file: state.worldread
Allocating hash table for state file, size 64 entries
Creating new state

Handling 1 logs

rotating pattern: /var/tmp/test/test.log  after 1 days (7 rotations)
empty log files are rotated, only log files >= 5242880 bytes are rotated, old 
logs are removed
considering log /var/tmp/test/test.log
  Now: 2022-07-18 09:24
  Last rotated at 2022-07-18 09:00
  log does not need rotating (log has already been rotated)

I edited away the lines with double slash (//) entry and tested
again, that didn't seem to make a difference.

% cat state.worldread
logrotate state -- version 2
"/var/tmp/test/test.log" 2022-7-18-9:0:0
% cat state.groupread
logrotate state -- version 2
"/var/tmp/test/test.log" 2022-7-18-9:0:0
% cat state.ownerread
logrotate state -- version 2
"/var/tmp/test/test.log" 2022-7-18-9:0:0

I think it would be helpful if rotatelog printed a message that
it was forcibly changing the state file permissions. Otherwise
the only way to resolve the confusion is a series of tests such
as I have shown here.

Vince

Bug#1012647: (no subject)

[S.]

Hi there, thanks very much for this speedy fix!
I confirm that broadcom-sta-dkms_6.30.223.271-20 from Testing also fixes the 
compilation issue on a Bullseye system with the 5.18 kernel from Backports. 
Would it be possible to send the fixed DKMS package to Bullseye-Backports as 
well?
Thanks again!

Bug#1013329: razor 2.85 is really 2.84

[Malte S. Stretz]

Hi vagrant,

thanks for pushing this to bdo.


On 21/06/2022 23:41, Vagrant Cascadian wrote:

On 2022-06-20, Malte S. Stretz wrote:

TL;DR: It looks like the Debian 2.85 razor package you've been recently
working on according to
https://salsa.debian.org/debian/razor/-/commits/debian/latest is really 2.84


>> […]


The current "upstream" version was uploaded to debian in 2008 currently
present in old-old-stable (e.g. two releases prior to the current stable
release):

   https://tracker.debian.org/news/303771/accepted-razor-1285-1-source-amd64/

The best thing might be to actually update to the newest upstream
release, if there is indeed one newer than 2.85... and kind of ignore
that unfortunate problem...

... though there might be security issues that are not correctly tracked
that are fixed in the upstream 2.85, but not in the debian packages
because of the version discrepancy; that might be worth confirming and
possibly notifying the security team.


The good news:  There doesn't seem to be any security relevant changes 
in https://github.com/toddr/Razor2-Client-Agent/compare/v2.84...v2.85


There even don't seem to be many functional changes, most of the changes 
are cleanup/build related things.  v2.86 also was just a build related 
thing.


The bad news:  All the current Debian patches won't apply anymore since 
there was some excessive reformatting applied upstream.


OTOH will some of them not be needed anymore since it looks they were 
partially incorporated upstream.



All that said, not sure I have the energy to tackle this kind of tangled
problem at the moment...


Would you like help with that?  My Debian packaging know how is a bit 
rusty but I could create a PR on Salsa which


* Merges the Upstream repo into the current Salsa repo (ie. switching it 
over to https://wiki.debian.org/PackagingWithGit#Using_the_upstream_repo 
without losing any history) at upstream v2.84

* Fixes up the Quilt patches and merge that state with upstream v2.85
* Bump the whole stuff to v2.86

What do I get out of that?  I'd like to include my IPv6 patch on top of 
all of this.


Regards,
Malte

Bug#1013184: bind9-dnsutils: dig returns an akamai server IP address when it should find nothing

[Mike S]

Package: bind9-dnsutils
Version: 1:9.16.27-1~deb11u1
Architecture: amd64

Dear Maintainer,

I needed to use docker under linux for testing purposes at work, where I 
only have a Windows 11 PC. I installed a vagrant box under hyper-v, and 
since I use bullseye on my own network at home, I chose the 
'generic/debian11' vagrant box.


I had problems with connectivity from containers via the docker 
'host-gateway', so started running tests.


I logged into a container and ran 'ping host-gateway' and found to my 
surprise that the target IP address was an external address and not my 
vagrant box (i.e. not actually the docker gateway host). This prevented 
messages from inside my docker containers being forwarded to the correct 
proxy.


I then ran 'dig host-gateway' on the container and on the debian11 
vagrant box, and got the IP address 23.217.138.108. I logged onto one of 
my home debian servers and confirmed that this is a public address 
mapped to an akamaitechnologies.com host name.


My home debian11 server did not initially exhibit the same issue, so I 
assumed there was something wrong with the vagrant box I was using, or 
possibly the vagrant deployment script. However, the resolv.conf files 
were pointing to different DNS servers - my server uses a local bind9 
service on my LAN, which forwards to my ISP, while the vagrant box 
configuration is using a few public DNS servers including 4.2.2.1 and 
4.2.2.2.


I thought I should also check if there was an issue with the DNS server, 
so I tried three further tests:


1) On the vagrant box I ran 'dig @[my local DNS server address] 
host-gateway'. This time I got the expected response (no ANSWER section, 
i.e. 'host-gateway not found'.


2) On my home server I ran 'dig @4.2.2.1 host-gateway', so forcing it to 
use the same DNS server that the vagrant box had been using. Now I once 
again got an ANSWER section including the address 23.217.138.108. My 
home server runs debian 11 on bare metal, so this is not an issue with 
vagrant or the vagrant box, or indeed with the Windows 11 hosting the box.


3) On my Windows PC I ran 'nslookup', set the DNS server to 4.2.2.1 and 
asked it for the address of 'host-gateway'. I got the expected response 
(service not found). This shows that this DNS server is not the source 
of the spurious address.


These tests appear to demonstrate that the problem is not in the vagrant 
deployment process, the vagrant box, or the DNS server at 4.2.2.1. The 
only common factor associated with the spurious reply is the Debian 11 
distro.


A few more tests revealed that this seems to happen whenever the 
requested host name ends with the string 'gateway', and the DNS server 
used is either 4.2.2.1 or 4.2.2.2. I did not get the same behaviour 
using 8.8.8.8, nor with my employer's DNS servers or my own server, but 
I didn't have time to try any others.


Obviously the case I stumbled on involved the docker 'host-gateway' 
name, which was chosen by docker because it should not resolve to any 
host on the Internet, allowing docker to insert its own binding with 
local scope. I don't know if the 'fake' ANSWER section is inserted when 
the real response contains an ANSWER. If yes, clients woud be unable to 
access the expected functions of the real server. If not, then clients 
would be directed to the wrong host only if there is no right host, so 
no functionality would be affected. But either way clients may send 
sensitive information to the akamaitechnologies host.


This seems to be very significant. Something seems to be recognising DNS 
requests to 4.2.2.1, and injecting a fake ANSWER section in the reply, 
directing clients to an akamaitechnologies host.


It seems possible this behaviour may be the result of malicious 
contamination rather than an accidental bug.



-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-15-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bind9-dnsutils depends on:
ii bind9-host [host] 1:9.16.27-1~deb11u1
ii bind9-libs 1:9.16.27-1~deb11u1
ii libc6 2.31-13+deb11u3
ii libedit2 3.1-20191231-2+b1
ii libidn2-0 2.3.0-5
ii libkrb5-3 1.18.3-6+deb11u1
ii libprotobuf-c1 1.3.3-1+b2

bind9-dnsutils recommends no packages.

bind9-dnsutils suggests no packages.

Bug#1002059: regression: 2:4.9.5+dfsg-5+deb10u2 breaks SID to UID conversion

[McIntyre, Vincent (S&A, Marsfield)]

On Fri, Jun 10, 2022 at 02:11:21PM +1000, Vincent McIntyre wrote:
>
>Yes, we have the same usernames (and uids) in both.
>This is by design and has worked for many years.
>It continues to work, I have machines running version
>2:4.5.16+dfsg-1+deb9u4
>with no issue.

doh, wrong version.
I have machines running 2:4.9.5+dfsg-5+deb10u3 that work with
the config change mentioned in #20.
Sorry for the confusion.

Bug#1002059: regression: 2:4.9.5+dfsg-5+deb10u2 breaks SID to UID conversion

[McIntyre, Vincent (S&A, Marsfield)]

Just saw the updates to this bug...

Hi Michael

thanks for your work on knocking samba packages into better shape
over the last few months.

You asked:
> Vincent, do you, by a chance, have the same usernames in
> /etc/passwd and in the AD your samba server joined?

Yes, we have the same usernames (and uids) in both.
This is by design and has worked for many years.
It continues to work, I have machines running version
 2:4.5.16+dfsg-1+deb9u4
with no issue.

I think this bug can be closed.
I was actually doing something unsupoprted before,
but got away with it for a while. As I outlined in message #20
making the now-required config change fixed it in my environment.

I think Thibalt's issue is different, he has kerberos set up
and security = ads on version 4.13, all of which means quite
different code paths.

Kind regards
Vince

Bug#1012084: systemd-zram-generator: Old version, please update 0.3.x -> 1.x.x

[Andrei S]

Package: systemd-zram-generator
Version: 0.3.2-1
Severity: wishlist
X-Debbugs-Cc: 4tn223y6z...@opayq.com

Hello!
Is it possible to update this package to a more recent version? Latest upstream 
version is 1.1.2.

Best regards


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

Kernel: Linux 5.15.0-33-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages systemd-zram-generator depends on:
ii  libc6  2.33-7
ii  libgcc-s1  12.1.0-2

systemd-zram-generator recommends no packages.

systemd-zram-generator suggests no packages.

Bug#1011973: node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function

[Akshay S Dinesh]

with node-source-map 0.7 built from salsa master branch, there is only 
1 failure. 26 tests were failing earlier with node-source-map 0.6.





This is a red herring.

The autopkgtest fails aren't related to node-source-map at all.

Specifically, the tests don't fail in gbp buildpackage, but only in 
autopkgtest, that too only in one particular stage.


That's because the __mocks__ that jest relies on are in the lib/helpers/ 
directory and that's not available somehow to the autopkgtest run. For 
example, if you do autopkgtest with --shell-fail and after it fails copy 
__mocks__ to /usr/share/nodejs/webpack-sources/lib/helpers and rerun the 
test with /usr/share/pkg-js-autopkgtest/runner it passes


You can replicate it by downloading upstream code and removing 
`__mocks__` folder and running yarnpkg test



https://wiki.debian.org/ContinuousIntegration/AutopkgtestBestPractices#Recommendations

> Use upstream test-suite if they have as-installed test

The jest tests are not as-installed

Bug#1004658: [Pkg-javascript-devel] Bug#1004658: Bug#1004658: Help to compile a wasm package

[Akshay S Dinesh]

anywhere else). The job is done (see debian/rules), we just have to find 
the good dependencies and fix the build since built wasm isn't exactly 
what upstream embeds in node-source-map, maybe some unpublished work...





I'm not exactly sure if the build is broken. The artifact generated by 
the rust code goes through multiple tools - rust-opt, rust-gc, etc... It 
is likely that one of these tools have changed how they work in the past 
4 years.


But the actual npm package and crate were all last released 4 years ago.

In all, I feel like all that's happening is we are unable to build a 
byte to byte matching reproducible build.


How exactly are we testing the output? For one the node-clean-css 
package seems to be doing some of its own wrapping on the 
originalPositionFor function and the error in clean-css tests could be 
because of an error in that.

Bug#1010681: arqiver: wrong dependency

[S. 7]

On Fri, 6 May 2022 23:59:31 +0200 Kacper Gutowski  
wrote:

> Package: arqiver
> Version: 0.9.0-1+b1
> Severity: normal
>
> Currently arqiver depends on '7zip' but it makes no use of it at all.
> On the other hand it complains about '7z' command being missing when
> opening or creating 7z file unless 'p7zip-full' package that provides
> the 7z command is installed.
>
> Either '7zip' dependency needs to be replaced with 'p7zip-full', or
> the package patched to use '7zz' command instead of '7z' (or, even
> better, make it work with either).
>
> -k
>
> -- System Information:
> Debian Release: bookworm/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.17.0-1-amd64 (SMP w/1 CPU thread; PREEMPT)
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /bin/dash
> Init: sysvinit (via /sbin/init)
> LSM: AppArmor: enabled
>
> Versions of packages arqiver depends on:
> ii 7zip 21.07+dfsg-4
> ii gzip 1.12-1
> ii libarchive-tools 3.6.0-1
> ii libc6 2.33-7
> ii libgcc-s1 12-20220428-1
> ii libqt5core5a 5.15.2+dfsg-16+b1
> ii libqt5gui5 5.15.2+dfsg-16+b1
> ii libqt5svg5 5.15.2-4
> ii libqt5widgets5 5.15.2+dfsg-16+b1
> ii libstdc++6 12-20220428-1
>
> arqiver recommends no packages.
>
> arqiver suggests no packages.
>
> -- no debconf information
>

Thank you for reporting this bug.

I have made a patch so that now both 7zip and p7zip-full are supported. 
I will also report this upstream, but I don't think my patch can be 
accepted there, because I use an absolute path to check for 7zip 
(/usr/bin/7zz). This is acceptable for Debian, but upstream has to 
support non-standard paths too.

Bug#1009598: reassigned this bug to node-postcss-loader

[Akshay S Dinesh]

On Wed, 11 May 2022 11:23:52 +0200 Georges Khaznadar 
 wrote:

Hello,

the errors raised during the build of node-ktex are due to an error
which comes from node-postcss-loader



I can confirm the bug is in node-postcss-loader

It is because webpack 5 is required for this version of postcss-loader.

https://github.com/webpack-contrib/postcss-loader/issues/514

Bug#945788: lightdm: Language support is broken

[S.]

I confirm that this bug still exists as described on Bullseye. The weird 
behavior of not using the selected language until the second login is an 
upstream issue present (for years and years) in all distros I've tried. But the 
/etc/pam.d/lightdm quirk is unique to Debian. Could at least that last 
sub-issue be fixed? Thanks a lot.

Bug#1009245: ruby-autoprefixer-rails: broken build (TypeError: Cannot read property 'env' of undefined)

[Akshay S Dinesh]

On the other hand, the autoprefixer.js from the gem (about 1 MB) and the 
autoprefixer.js that's generated through build from the upstream repo 
(about 8 MB) seems to be different. This is unexplained by the dev.




I was comparing an older version of the gem actually. Please ignore this 
comment.




On the other hand, I have found that the node-resolve is somehow 
resolving util.js from the system (/usr/share/nodejs) instead of 
node_modules (possibly related to the patch we're applying) and that 
causes process.env to be read directly (without handling it as if it is 
inside browser)

Bug#1010314: ca-certificates: Executable search ordering for OpenSSL?

[S. Egbert]

Package: ca-certificates
Version: 20210119
Severity: normal
X-Debbugs-Cc: s.egb...@sbcglobal.net

Dear Maintainer,

A group of auditors were reviewing the CA inclusion process
and have examined the `update-ca-certificates` and its code.

This issue is not about the PKI nor its certificate handling.

One auditor noticed that the ordering of looking for OpenSSL
executable file (`openssl`) seems ... counterintuitive?

I would imagine that the correct ordering for searching this `openssl`
executable file be something like:

1.  /usr/local/sbin/openssl
2.  /usr/local/bin/openssl
3.  /usr/sbin/openssl
4.  /usr/bin/openssl


The actually and current order by the latest `update-ca-certificates`
in looking for this `openssl` exectuable is currently:

1.  $CWD/openssl 
2.  /usr/local/bin/openssl
3.  /usr/local/sbin/openssl
4.  /usr/bin/openssl
5.  /usr/sbin/openssl

Please note the inversal of `sbin` and `bin`.  (The ordering of
`/usr`/`/usr/local` complies with FSSTD v2.3).

ANALYSIS

If a single-user binary (such as `openssl`) is the official and resides
within the `sbin` as a single-user file, why is `update-ca-certificates` 
looking to 
circumvent this official binary with something outside of `sbin`?

Please note that I did not say 'system binary' here that is often
mistaken for `sbin`.

In these transitory age (of Fedora squeezing `/sbin` into `/usr/bin`)
why would an auditor want to use the `bin` firstly before the `sbin`
for finding the 'official' executable?

What gain of system integrity can be had by evoking the non-single-user
`bin`-variant before the single-user `sbin`-variant?


AUDITOR ALERT: As an unrelated note but for auditors especially in area
of CA certificates, auditors should be forewarned that the 
current (`$CWD`) directory should be empty before conducting their 
examination effort using `openssl` 
executable by others (most notably and currently the `update-ca-certificates`).


Of course, I am not the UNIX expert here but merely a multi-decade 
user of UNIX.  This bug report is merely to point out if this 
inversal of `sbin`/`bin` executable lookup is
the standard expected way of doing searches for a specific executable file.


-- System Information:
Debian Release: 11.3
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages ca-certificates depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  openssl1.1.1n-0+deb11u1

ca-certificates recommends no packages.

ca-certificates suggests no packages.

-- debconf information:
  ca-certificates/trust_new_crts: yes
  ca-certificates/title:
  ca-certificates/new_crts:
  ca-certificates/enable_crts: mozilla/ACCVRAIZ1.crt, 
mozilla/AC_RAIZ_FNMT-RCM.crt, mozilla/Actalis_Authentication_Root_CA.crt, 
mozilla/AffirmTrust_Commercial.crt, mozilla/AffirmTrust_Networking.crt, 
mozilla/AffirmTrust_Premium.crt, mozilla/AffirmTrust_Premium_ECC.crt, 
mozilla/Amazon_Root_CA_1.crt, mozilla/Amazon_Root_CA_2.crt, 
mozilla/Amazon_Root_CA_3.crt, mozilla/Amazon_Root_CA_4.crt, 
mozilla/Atos_TrustedRoot_2011.crt, 
mozilla/Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.crt, 
mozilla/Baltimore_CyberTrust_Root.crt, mozilla/Buypass_Class_2_Root_CA.crt, 
mozilla/Buypass_Class_3_Root_CA.crt, mozilla/CA_Disig_Root_R2.crt, 
mozilla/Certigna.crt, mozilla/Certigna_Root_CA.crt, 
mozilla/certSIGN_ROOT_CA.crt, mozilla/certSIGN_Root_CA_G2.crt, 
mozilla/Certum_Trusted_Network_CA_2.crt, mozilla/Certum_Trusted_Network_CA.crt, 
mozilla/CFCA_EV_ROOT.crt, mozilla/Chambers_of_Commerce_Root_-_2008.crt, 
mozilla/Comodo_AAA_Services_root.crt, 
mozilla/COMODO_Certification_Authority.crt, 
mozilla/COMODO_ECC_Certification_Authority.crt, 
mozilla/COMODO_RSA_Certification_Authority.crt, 
mozilla/Cybertrust_Global_Root.crt, mozilla/DigiCert_Assured_ID_Root_CA.crt, 
mozilla/DigiCert_Assured_ID_Root_G2.crt, 
mozilla/DigiCert_Assured_ID_Root_G3.crt, mozilla/DigiCert_Global_Root_CA.crt, 
mozilla/DigiCert_Global_Root_G2.crt, mozilla/DigiCert_Global_Root_G3.crt, 
mozilla/DigiCert_High_Assurance_EV_Root_CA.crt, 
mozilla/DigiCert_Trusted_Root_G4.crt, mozilla/DST_Root_CA_X3.crt, 
mozilla/D-TRUST_Root_Class_3_CA_2_2009.crt, 
mozilla/D-TRUST_Root_Class_3_CA_2_EV_2009.crt, mozilla/EC-ACC.crt, 
mozilla/emSign_ECC_Root_CA_-_C3.crt, mozilla/emSign_ECC_Root_CA_-_G3.crt, 
mozilla/emSign_Root_CA_-_C1.crt, mozilla/emSign_Root_CA_-_G1.crt, 
mozilla/Entrust.net_Premium_2048_Secure_Server_CA.crt, 
mozilla/Entrust_Root_Certification_Authority.crt, 
mozilla/Entrust_Root_Certification_Authority_-_EC1.crt, 
mozilla/Entrust_Root_Certification_A

Bug#170850: opportunity

[Allen S]

Hello,

I lead family investment vehicles who want to invest a proportion of their 
funds with a trust party .

Please if you are interested in discussing investment in your sector?

Please email, or simply write to me here. I value promptness and will make 
every attempt to respond within a short time.

Thank you.
Allen S.