Bug#1008181: CVE-2017-5715

[Salvatore Bonaccorso]

Hi

On Wed, Mar 30, 2022 at 09:31:32AM +, Holger Levsen wrote:
> On Wed, Mar 30, 2022 at 09:36:58AM +0200, Sylvestre Ledru wrote:
> > Le 30/03/2022 à 07:07, Salvatore Bonaccorso a écrit :
> > > Sylvestre and Holger, would you have time to include the bugfix as
> > > well in the future bullseye point release?
> > Sure, should be easy.
> > Is there a timeline?
> 
> as the last point release was last weekend the next one will probably
> happen in around two months.
> 
> that said, one can file an SRM bug now and do the upload now as well too. :)

Right. And additionally in cases where there is some need (maybe not
here), but like tzdata updates or clamav, updates can go earlier as
well via a SUA and stable-updates.

Regards,
Salvatore

Bug#1009020: blender: GPU support on AMD A8-3870 APU

[Alexandre Lymberopoulos]

Package: blender
Version: 3.0.1+dfsg-7+b1
Severity: normal

Dear Maintainer,

This is not a proper bugreport, just wondering if there is any chance
of some GPU support on AMD A8-3870 APU (Radeon HD 6550D) to accelerate
rendering images or videos in blender?

Thanks in advance.

Best,
Alexandre

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
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=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages blender depends on:
ii  blender-data  3.0.1+dfsg-7
ii  fonts-dejavu  2.37-2
ii  libavcodec58  7:4.4.1-3+b2
ii  libavdevice58 7:4.4.1-3+b2
ii  libavformat58 7:4.4.1-3+b2
ii  libavutil56   7:4.4.1-3+b2
ii  libboost-locale1.74.0 1.74.0-14
ii  libc6 2.33-7
ii  libembree3-3  3.13.3+dfsg-1
ii  libfftw3-double3  3.3.8-2
ii  libfreetype6  2.11.1+dfsg-1
ii  libgcc-s1 12-20220319-1
ii  libgl11.4.0-1
ii  libglew2.22.2.0-4
ii  libgomp1  12-20220319-1
ii  libilmbase25  2.5.7-2
ii  libjack-jackd2-0 [libjack-0.125]  1.9.20~dfsg-1+b1
ii  libjemalloc2  5.2.1-4
ii  libjpeg62-turbo   1:2.1.2-1
ii  libopenal11:1.19.1-2
ii  libopenexr25  2.5.7-1
ii  libopenimageio2.2 2.2.18.0+dfsg-2+b1
ii  libopenjp2-7  2.4.0-6
ii  libopenvdb8.1 8.1.0-3
ii  libosdcpu3.4.43.4.4-2
ii  libpcre3  2:8.39-13
ii  libpng16-16   1.6.37-3
ii  libpugixml1v5 1.12.1-1
ii  libpulse0 15.0+dfsg1-4
ii  libpython3.10 3.10.4-1
ii  libsdl2-2.0-0 2.0.20+dfsg-2
ii  libsndfile1   1.0.31-2
ii  libspnav0 0.2.3-1+b2
ii  libstdc++612-20220319-1
ii  libswscale5   7:4.4.1-3+b2
ii  libtbb2   2020.3-1
ii  libtiff5  4.3.0-6
ii  libx11-6  2:1.7.2-2+b1
ii  libxfixes31:6.0.0-1
ii  libxi62:1.8-1
ii  libxml2   2.9.13+dfsg-1
ii  libxrender1   1:0.9.10-1
ii  libxxf86vm1   1:1.1.4-1+b2
ii  libzstd1  1.4.10+dfsg-1
ii  zlib1g1:1.2.11.dfsg-4

blender recommends no packages.

blender suggests no packages.

-- no debconf information

Bug#1009018: linux-image-5.16.0-5-amd64: Shutdown, reboot, and suspend broken on chromebook when module cros_ec_typec is loaded.

[Dan Bassett]

Package: src:linux
Version: 5.16.14-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: b...@fizix.org

Dear Maintainer,

   * What led up to the situation?

   I upgraded my system from Stable (5.10 kernel) to Testing in order
   to get sound working, however, upon upgrade, my system was no longer
   able to shutdown, reboot, or suspend properly.  All of these actions
   would result in the system hanging, requiring a hard reset.


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

   I manually built a series of kernels to try to narrow down where
   the issue was occuring and found that when I disabled the building of
   chromebook related platform drivers, my system would happily reboot
   and suspend.  I also noticed that the kernel was throwing an error 
   at boot when attempting to load the cros_ec_typec module.  Given this
   information, I attempted to boot the stock debian kernel
   (5.16.0-5-amd64) with the option module_blacklist=cros_ec_typec,
   which resulted in a system that rebooted and suspended as expected.
   I am unaware of any functionality that I may be losing by not loading
   the cros_ec_typec module.


   * What was the outcome of this action?

   I have a working system, though ideally this module would properly
   load on boot (as my hardware configuration seems to want it), and not
   break shutdown/reboot/suspend.


   * What outcome did you expect instead?

   The system should work without disabling relevant kernel modules.



-- Package-specific info:
** Version:
Linux version 5.16.0-5-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.2.0-18) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Debian 
5.16.14-1 (2022-03-15)

** Command line:
BOOT_IMAGE=linux initrd=initrd root=LABEL=root net.ifnames=0 
snd_intel_dspcfg.dsp_driver=3 i915.enable_guc=3

** Tainted: UD (192)
 * taint requested by userspace application
 * kernel died recently, i.e. there was an OOPS or BUG

** Kernel log:
[4.970325]  i2c_hid_acpi i2c_hid hid battery video i2c_algo_bit ttm 
drm_kms_helper xhci_pci xhci_hcd usbcore cec sdhci_pci rc_core cqhci sdhci drm 
button intel_lpss_pci intel_lpss pinctrl_jasperlake mmc_core idma64 usb_common
[4.970335] CR2: 0070
[4.970337] ---[ end trace b75001be1263bffa ]---
[4.976732] RIP: 0010:mutex_lock+0x19/0x30
[5.043109] Code: 00 0f 1f 44 00 00 be 02 00 00 00 e9 11 fb ff ff 90 0f 1f 
44 00 00 55 48 89 fd e8 82 e8 ff ff 31 c0 65 48 8b 14 25 c0 fb 01 00  48 0f 
b1 55 00 75 02 5d c3 48 89 ef 5d eb c7 0f 1f 80 00 00 00
[5.043112] RSP: 0018:ad7c005bbbe8 EFLAGS: 00010246
[5.043114] RAX:  RBX:  RCX: 
[5.043116] RDX: 95344dcc1840 RSI: 9534421503e0 RDI: 0070
[5.043117] RBP: 0070 R08: 0002 R09: 9534421503e0
[5.043118] R10: 9534badaa000 R11:  R12: 
[5.043118] R13: 0070 R14: 0001 R15: ad7c005bbc7c
[5.043120] FS:  7ff3123db8c0() GS:9534bbf0() 
knlGS:
[5.043121] CS:  0010 DS:  ES:  CR0: 80050033
[5.043122] CR2: 0070 CR3: 00010d542000 CR4: 00350ee0
[5.049424] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[5.085084] XFS (mmcblk1p3): Mounting V5 Filesystem
[5.359289] intel_rapl_common: Found RAPL domain package
[5.360833] intel_rapl_common: Found RAPL domain core
[5.362277] intel_rapl_common: Found RAPL domain uncore
[5.363948] intel_rapl_common: Found RAPL domain psys
[5.386279] XFS (mmcblk1p3): Ending clean mount
[5.396452] xfs filesystem being mounted at /home/dbassett supports 
timestamps until 2038 (0x7fff)
[5.555928] cryptd: max_cpu_qlen set to 1000
[5.608899] SSE version of gcm_enc/dec engaged.
[5.659945] usb 1-6: Found UVC 1.00 device HP Wide Vision HD Camera 
(30c9:004d)
[5.671680] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data 
may be corrupt. Please run fsck.
[5.682965] input: HP Wide Vision HD Camera: HP Wi as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/input/input5
[5.683111] usbcore: registered new interface driver uvcvideo
[5.728985] rtw_8822ce :01:00.0: firmware: direct-loading firmware 
rtw88/rtw8822c_fw.bin
[5.728994] rtw_8822ce :01:00.0: Firmware version 9.9.10, H2C version 15
[5.732851] rtw_8822ce :01:00.0: firmware: direct-loading firmware 
rtw88/rtw8822c_wow_fw.bin
[5.732860] rtw_8822ce :01:00.0: Firmware version 9.9.4, H2C version 15
[5.759507] sof-audio-pci-intel-icl :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
[5.759670] sof-audio-pci-intel-icl :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[5.766920] sof-audio-pci-intel-icl :00:1f.3: use msi interrupt mode
[5.808203] sof-audio-pci-intel-icl :00:1f.3: hda codecs 

Bug#1009016: xpad: Disabling the display of window decorations no longer works.

[Tomasz Kapias]

Package: xpad
Version: 5.7.0-2
Severity: normal
Tags: upstream

Dear Maintainer,

   - After version 5.4.0-2 disabling the display of window decorations no
longer works. I'm using Debian 11 with the i3wm-gaps (i3wm fork) window manager
and Compton (Picom fork). I still see the window borders.

   - APT installed version 5.7.0-2, I removed it to roll back to 5.4.0-2, from
Debian snapshots, manually for the moment.
   - I opened a bug report upstream :
https://bugs.launchpad.net/xpad/+bug/1967964

   - Reading other bug reports upstream I saw that since version 5.5 of Xpad,
they are preparing the ground for the switch to GTK4. And removed some support
of the GTK3 framework.

   - THere was another bug after this change : clicking in the notification
area no longer toggles the appearance of notes. As seen in the bug report
n°1965034: https://bugs.launchpad.net/xpad/+bug/1965034. No solution for this
one.




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

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

Versions of packages xpad depends on:
ii  libc6   2.33-7
ii  libglib2.0-02.72.0-1+b1
ii  libgtk-3-0  3.24.33-1
ii  libgtksourceview-3.0-1  3.24.11-2+b1
ii  libice6 2:1.0.10-1
ii  libpango-1.0-0  1.50.6+ds-2
ii  libsm6  2:1.2.3-1

xpad recommends no packages.

xpad suggests no packages.

-- no debconf information

Bug#1009014: installation-reports: Successful install on Pine64 Rock64 using serial console

[Vagrant Cascadian]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org


Boot method: microSD
Image version: 
https://d-i.debian.org/daily-images/arm64/20220405-02:29/netboot/SD-card-images/
  firmware.rock64-rk3328.img.gz partition.img.gz
Date: 2022-04-05 ~16:10 -0700

Machine: Pine64 Rock64
Partitions:
major minor  #blocks  name

 1790   30924800 mmcblk0
 1791 133616 mmcblk0p1
 17924882432 mmcblk0p2


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

That was too easy!

I should see if it works via HDMI sometime...


live well,
  vagrant

-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20220405-02:04:02"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux rk64w 5.16.0-6-arm64 #1 SMP Debian 5.16.18-1 (2022-03-29) 
aarch64 GNU/Linux
usb-list: 
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 5.16.0-6-arm64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 01: Generic Platform OHCI controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 5.16.0-6-arm64 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 03 Device 01: DWC OTG Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 5.16.0-6-arm64 dwc2_hsotg
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 04 Device 01: xHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 5.16.0-6-arm64 xhci-hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 05 Device 01: xHCI Host Controller [1d6b:0003]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 03
usb-list:Manufacturer: Linux 5.16.0-6-arm64 xhci-hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
lsmod: Module  Size  Used by
lsmod: dm_mod143360  0
lsmod: md_mod163840  0
lsmod: xfs  1384448  0
lsmod: jfs   200704  0
lsmod: btrfs1478656  0
lsmod: xor20480  1 btrfs
lsmod: xor_neon   16384  1 xor
lsmod: raid6_pq  106496  1 btrfs
lsmod: zstd_compress 253952  1 btrfs
lsmod: libcrc32c  16384  2 btrfs,xfs
lsmod: vfat   28672  0
lsmod: fat81920  1 vfat
lsmod: ext4  765952  1
lsmod: crc16  16384  1 ext4
lsmod: mbcache24576  1 ext4
lsmod: jbd2  151552  1 ext4
lsmod: crc32c_generic 16384  3
lsmod: usb_storage73728  0
lsmod: scsi_mod  229376  1 usb_storage
lsmod: scsi_common16384  2 scsi_mod,usb_storage
lsmod: realtek32768  1
lsmod: xhci_plat_hcd  24576  0
lsmod: xhci_hcd  253952  1 xhci_plat_hcd
lsmod: rk808_regulator40960  13
lsmod: dwmac_rk   28672  0
lsmod: stmmac_platform24576  1 dwmac_rk
lsmod: stmmac237568  2 stmmac_platform,dwmac_rk
lsmod: dwc2  241664  0
lsmod: rockchipdrm   122880  0
lsmod: ohci_platform  16384  0
lsmod: dw_hdmi45056  1 rockchipdrm
lsmod: pcs_xpcs   24576  1 stmmac
lsmod: ohci_hcd   57344  1 ohci_platform
lsmod: cec49152  1 dw_hdmi
lsmod: rc_core53248  1 cec
lsmod: dwc3  159744  0
lsmod: phylink45056  1 stmmac
lsmod: ehci_platform  20480  0
lsmod: of_mdio20480  3 stmmac_platform,stmmac
lsmod: ehci_hcd   90112  1 ehci_platform
lsmod: dw_mipi_dsi20480  1 rockchipdrm
lsmod: analogix_dp49152  1 rockchipdrm
lsmod: udc_core   5324

Bug#1008966: libopenmpi-dev: IO (and UCX) problems causing mpi4py test failures

[Drew Parsons]

On 2022-04-06 01:06, Drew Parsons wrote:

dalcini from mpi4py and ggouaillardet from openmpi both raised the
same question in their respective upstream issues:  why is our MCA io
running through   romio321 instead of the default "native" ompio?
Sounds like it might be the key to multiple problems.



Likely related to that question, ompio seems to have gone missing (which 
could explain why romio321 is getting used)


$ dlocate ompio
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi/openmpi/ompi/mca/common/ompio
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi/openmpi/ompi/mca/common/ompio/common_ompio.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi/openmpi/ompi/mca/common/ompio/common_ompio_aggregators.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi/openmpi/ompi/mca/common/ompio/common_ompio_buffer.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi/openmpi/ompi/mca/common/ompio/common_ompio_print_queue.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/fortran/gfortran-mod-15/openmpi/openmpi/ompi/mca/common/ompio/common_ompio_request.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/ompi/mca/common/ompio
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/ompi/mca/common/ompio/common_ompio.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/ompi/mca/common/ompio/common_ompio_aggregators.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/ompi/mca/common/ompio/common_ompio_buffer.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/ompi/mca/common/ompio/common_ompio_print_queue.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/ompi/mca/common/ompio/common_ompio_request.h
libopenmpi-dev:amd64: 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmca_common_ompio.so
libopenmpi3:amd64: 
/usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_io_ompio.so


$ dpkg -l libopenmpi-dev libopenmpi3
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version  Architecture Description
+++----==
ii  libopenmpi-dev:amd64 4.1.3-1  amd64high performance 
message passing library -- header files
ii  libopenmpi3:amd644.1.3-1  amd64high performance 
message passing library -- shared library


$ ls -l /usr/lib/x86_64-linux-gnu/openmpi/lib/libmca_common_ompio.so
lrwxrwxrwx 1 root root 30 Apr  2 10:05 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmca_common_ompio.so -> 
libmca_common_ompio.so.41.29.3


$ ls -l /usr/lib/x86_64-linux-gnu/openmpi/lib/*ompio*
lrwxrwxrwx 1 root root 30 Apr  2 10:05 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmca_common_ompio.so -> 
libmca_common_ompio.so.41.29.3

Bug#1008966: libopenmpi-dev: IO (and UCX) problems causing mpi4py test failures

[Drew Parsons]

dalcini from mpi4py and ggouaillardet from openmpi both raised the same 
question in their respective upstream issues:  why is our MCA io running 
through   romio321 instead of the default "native" ompio?  Sounds like 
it might be the key to multiple problems.


Drew

Bug#1008997: further information

[Till Kamppeter]

First step is to go to

http://www.openprinting.org/

There you scroll down and find a link to the "Driverless Printers" list. 
Click "Browse". You get onto


https://openprinting.github.io/printers/

into the search field enter "Envy 553". The last digit does not matter. 
Different last digits usually only mean different power plugs for the 
different destination countries.


So your printer supports AirPrint, one of the driverless IPP standards.

Your printer's Wi-Fi is flaky, so use IPP-over-USB. Keep the printer 
connected to USB and install the "ipp-usb" package. Having done this 
your printer should appear already in the print dialogs of many 
applications.


If not, create a driverless print queue:

First, run

driverless

You will get an URI for your printer, most probably

ipp://localhost:6/ipp/print

Create a driverless queue with this URI:

lpadmin -p envy -E -v ipp://localhost:6/ipp/print -m everywhere

Now all your apps should show your printer with queue name "envy". Can 
you print on this queue?


   Till

P. S.: Avoid HPLIP if you do not REALLY need it.

Bug#1009013: krita: registers desktop file for csv (wtf)

[Bernd Zeimetz]

Package: krita
Version: 1:5.0.2+dfsg-2+b1
Severity: normal

Hi,

krita ships

/usr/share/applications/krita_csv.desktop

and will be registered as tool to open csv files.
But it can't handle csv files and it really doesn't make sense to open
them in Krita... Please fix that.

Thanks.

Bernd


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

Kernel: Linux 5.17.0-rc6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 krita depends on:
ii  krita-data1:5.0.2+dfsg-2
ii  libc6 2.33-7
ii  libexiv2-27   0.27.5-3
ii  libfftw3-double3  3.3.8-2
ii  libgcc-s1 12-20220319-1
ii  libgif7   5.1.9-2
ii  libgsl27  2.7.1+dfsg-3
ii  libheif1  1.12.0-2+b3
ii  libilmbase25  2.5.7-2
ii  libjpeg62-turbo   1:2.1.2-1
ii  libkf5completion5 5.90.0-1
ii  libkf5configcore5 5.90.0-1
ii  libkf5configgui5  5.90.0-1
ii  libkf5coreaddons5 5.90.0-1
ii  libkf5crash5  5.90.0-1
ii  libkf5guiaddons5  5.90.0-2
ii  libkf5i18n5   5.90.0-1
ii  libkf5itemviews5  5.90.0-1
ii  libkf5widgetsaddons5  5.90.0-1
ii  libkf5windowsystem5   5.90.0-1
ii  libkseexpr4   4.0.4.0-2
ii  libkseexprui4 4.0.4.0-2
ii  liblcms2-22.12~rc1-2
ii  libmypaint-1.5-1  1.6.0-2
ii  libopencolorio1v5 1.1.1~dfsg0-7.1+b1
ii  libopenexr25  2.5.7-1
ii  libopenjp2-7  2.4.0-6
ii  libpng16-16   1.6.37-3
ii  libpoppler-qt5-1  22.02.0-3
ii  libpython3.10 3.10.4-2
ii  libqt5concurrent5 5.15.2+dfsg-16
ii  libqt5core5a  5.15.2+dfsg-16
ii  libqt5dbus5   5.15.2+dfsg-16
ii  libqt5gui55.15.2+dfsg-16
ii  libqt5multimedia5 5.15.2-3
ii  libqt5network55.15.2+dfsg-16
ii  libqt5printsupport5   5.15.2+dfsg-16
ii  libqt5qml55.15.2+dfsg-10
ii  libqt5quick5  5.15.2+dfsg-10
ii  libqt5quickwidgets5   5.15.2+dfsg-10
ii  libqt5sql55.15.2+dfsg-16
ii  libqt5sql5-sqlite 5.15.2+dfsg-16
ii  libqt5svg55.15.2-4
ii  libqt5widgets55.15.2+dfsg-16
ii  libqt5x11extras5  5.15.2-2
ii  libqt5xml55.15.2+dfsg-16
ii  libquazip5-1  0.9.1-2
ii  libraw20  0.20.2-2
ii  libstdc++612-20220319-1
ii  libtiff5  4.3.0-6
ii  libwebp7  1.2.2-2+b1
ii  libx11-6  2:1.7.5-1
ii  zlib1g1:1.2.11.dfsg-4

Versions of packages krita recommends:
pn  krita-gmic   
ii  python3-pyqt55.15.6+dfsg-1+b2
ii  python3-sip  4.19.25+dfsg-3+b1
pn  qml-module-qtmultimedia  

Versions of packages krita suggests:
ii  colord  1.4.6-1
ii  ffmpeg  7:4.4.1-3+b2
pn  krita-l10n  

-- no debconf information

Bug#1008507:

[Aurelien Jarno]

Hi,

On 2022-03-29 17:53, Joshua Hudson wrote:
> diff -ur glibc.orig/glibc/sysdeps/unix/sysv/linux/pathconf.c
> glibc/glibc/sysdeps/unix/sysv/linux/pathconf.c
> --- glibc.orig/glibc/sysdeps/unix/sysv/linux/pathconf.c2022-03-29
> 17:50:12.558027042 -0700
> +++ glibc/glibc/sysdeps/unix/sysv/linux/pathconf.c2022-03-29
> 17:52:33.262157543 -0700
> @@ -183,6 +183,11 @@
>  case XFS_SUPER_MAGIC:
>return XFS_LINK_MAX;
> 
> +case MSDOS_SUPER_MAGIC:
> +#ifdef EXFAT_SUPER_MAGIC // For when it gets added in about 30 years
> +case EXFAT_SUPER_MAGIC:
> +#endif
> +  return 1;
>  case LUSTRE_SUPER_MAGIC:
>return LUSTRE_LINK_MAX;

If you ended with a patch, the best is probably to submit it upstream to
libc-al...@sourceware.org .

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#1008997: further information

[alain]

here are the responses to your questions , Bryan potkin :


yes, I am on unstable sid.
Its great strength is that its packages are constantly evolving. 
Unfortunately, this is also sometimes its great weakness.


My printer is the hp envy 5536 that I use in USB. The wifi, on this 
printer, works particularly badly. (design errors ?)


Thank you very much for your help.

friendly.
respectfully.
alain .

Bug#999204: whereami: diff for NMU version 0.3.34-0.5

[Joao Eriberto Mota Filho]

Control: tags 999204 + patch
Control: tags 999204 + pending

Dear maintainer,

I've prepared an NMU for whereami (versioned as 0.3.34-0.5) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

Eriberto

diff -u whereami-0.3.34/debian/changelog whereami-0.3.34/debian/changelog
--- whereami-0.3.34/debian/changelog
+++ whereami-0.3.34/debian/changelog
@@ -1,3 +1,11 @@
+whereami (0.3.34-0.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: added missing targets build-arch and build-indep.
+(Closes: #999204)
+
+ -- Joao Eriberto Mota Filho   Tue, 05 Apr 2022 17:58:14 
-0300
+
 whereami (0.3.34-0.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u whereami-0.3.34/debian/rules whereami-0.3.34/debian/rules
--- whereami-0.3.34/debian/rules
+++ whereami-0.3.34/debian/rules
@@ -105,4 +105,6 @@
 source diff:
@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
 
-.PHONY: binary-arch binary-indep clean
+build-arch: build
+build-indep: build
+.PHONY: build-arch build-indep binary-arch binary-indep clean

Bug#999009: scanssh: diff for NMU version 2.0-4.2

[Joao Eriberto Mota Filho]

Control: tags 999009 + patch
Control: tags 999009 + pending

Dear maintainer,

I've prepared an NMU for scanssh (versioned as 2.0-4.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

Eriberto

diff -u scanssh-2.0/debian/changelog scanssh-2.0/debian/changelog
--- scanssh-2.0/debian/changelog
+++ scanssh-2.0/debian/changelog
@@ -1,3 +1,11 @@
+scanssh (2.0-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: added missing targets build-arch and build-indep.
+(Closes: #999009)
+
+ -- Joao Eriberto Mota Filho   Tue, 05 Apr 2022 17:50:08 
-0300
+
 scanssh (2.0-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u scanssh-2.0/debian/rules scanssh-2.0/debian/rules
--- scanssh-2.0/debian/rules
+++ scanssh-2.0/debian/rules
@@ -91,4 +91,6 @@
dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+build-arch: build
+build-indep: build
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary 
install configure

Bug#1009012: bacula FTCBFS: uses the build architecture qmake

[Helmut Grohne]

Source: bacula
Version: 9.6.7-4
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

bacula fails to cross build from source, because it attempts to use the
build architecture qmake while Build-Depends requested the host
architecture one. To make matters worse, this is only visible much later
in the build as the qmake failure is swallowed. Such behaviour arguably
runs afoul Debian policy section 4.6 and should likely be considered a
serious policy violation.

In any case, bacula's configure.ac uses AC_PATH_PROG to locate qmake.
Once changing that to AC_PATH_TOOL, the host architecture qmake is being
used and this part magically works. This is what this bug is about. I'm
attaching a patch for your convenience.

Beyond this, bacula uses mysql_config to discover mysql client
libraries. Cross building with mysql_config is not something we can fix.
If bacula is to support cross building, it will need to use pkg-config
(or pkgconf) instead. The relevant code is quite non-trivial and I
couldn't come up with a working version. Would you be interested in
looking into this? The following link describes a way that is
automatically compatible with cross building. The module name is
"mysqlclient". https://autotools.info/pkgconfig/pkg_check_modules.html

So please close this bug when fixing the qmake invocation and
preferably also the policy violation.

Helmut
--- bacula-9.6.7.orig/autoconf/configure.in
+++ bacula-9.6.7/autoconf/configure.in
@@ -157,7 +157,7 @@
 dnl The macro PKG_PROG_PKG_CONFIG avoids this problem.
 dnl AC_PATH_PROG(PKGCONFIG, pkg-config, pkg-config)
 PKG_PROG_PKG_CONFIG()
-AC_PATH_PROG(QMAKE, qmake, none)
+AC_PATH_TOOL(QMAKE, qmake, none)
 AC_PATH_PROG(GMAKE, gmake, none)
 AC_PATH_PROG(PIDOF, pidof, pidof)
 AC_PROG_AWK

Bug#999064: parchive: diff for NMU version 1.1-4.2

[Joao Eriberto Mota Filho]

Control: tags 999064 + patch
Control: tags 999064 + pending

Dear maintainer,

I've prepared an NMU for parchive (versioned as 1.1-4.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

Eriberto

diff -u parchive-1.1/debian/changelog parchive-1.1/debian/changelog
--- parchive-1.1/debian/changelog
+++ parchive-1.1/debian/changelog
@@ -1,3 +1,11 @@
+parchive (1.1-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: added missing targets build-arch and build-indep.
+(Closes: #999064)
+
+ -- Joao Eriberto Mota Filho   Tue, 05 Apr 2022 17:41:54 
-0300
+
 parchive (1.1-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u parchive-1.1/debian/rules parchive-1.1/debian/rules
--- parchive-1.1/debian/rules
+++ parchive-1.1/debian/rules
@@ -82,4 +82,6 @@
dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+build-arch: build
+build-indep: build
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary 
install configure

Bug#1009011: ITP: r-cran-flextable -- GNU R functions for tabular reporting

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-flextable -- GNU R functions for tabular reporting
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-flextable
  Version : 0.7.0
  Upstream Author : David Gohel,
* URL : https://cran.r-project.org/package=flextable
* License : GPL-3
  Programming Lang: GNU R
  Description : GNU R functions for tabular reporting
 Create pretty tables for 'HTML', 'PDF', 'Microsoft Word' and 'Microsoft
 PowerPoint' documents from 'R Markdown'. Functions are provided to let
 users create tables, modify and format their content. It also extends
 package 'officer' that does not contain any feature for customized
 tabular reporting.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-flextable

Bug#999020: devio: diff for NMU version 1.2-1.3

[Joao Eriberto Mota Filho]

Control: tags 999020 + patch
Control: tags 999020 + pending

Dear maintainer,

I've prepared an NMU for devio (versioned as 1.2-1.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

Eriberto

diff -u devio-1.2/debian/changelog devio-1.2/debian/changelog
--- devio-1.2/debian/changelog
+++ devio-1.2/debian/changelog
@@ -1,3 +1,11 @@
+devio (1.2-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: added missing targets build-arch and build-indep.
+(Closes: #999020)
+
+ -- Joao Eriberto Mota Filho   Tue, 05 Apr 2022 17:25:12 
-0300
+
 devio (1.2-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u devio-1.2/debian/rules devio-1.2/debian/rules
--- devio-1.2/debian/rules
+++ devio-1.2/debian/rules
@@ -83,4 +83,6 @@
dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install
+build-arch: build
+build-indep: build
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary 
install

Bug#1009010: slop: maim: error while loading shared libraries: libslopy.so.7.5: cannot open shared object file: No such file or directory

[Axel Beckert]

Package: slop
Version: 7.6-1
Severity: serious
Control: affects -1 maim

Slop seems to provide a shared library without having a proper SONAME or
ABI in the package name and bumping the library made at least "maim" to
fail to work:

maim: error while loading shared libraries: libslopy.so.7.5: cannot open shared 
object file: No such file or directory

>From my point of view, it is an error of slop to provide a shared
library but not having a proper library package with proper SONAME or
ABI version in the package name.

In case you disagree, please do not provide a shared library at all and
do compile this library directly into the binary "slop".

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

Kernel: Linux 5.16.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, 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 slop depends on:
ii  libc62.33-7
ii  libgcc-s112-20220319-1
ii  libgl1   1.4.0-1
ii  libglew2.2   2.2.0-4
ii  libicu67 67.1-7
ii  libstdc++6   12-20220319-1
ii  libx11-6 2:1.7.5-1
ii  libxext6 2:1.3.4-1
ii  libxrender1  1:0.9.10-1

slop recommends no packages.

slop suggests no packages.

-- no debconf information

Bug#1009009: RM: libgweather --RoM; obsolete, replaced by libgweather4

[Jeremy Bicha]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: libgweat...@packages.debian.org

The libgweather source package is no longer used and has been replaced
by libgweather4. Upstream did some creative version numbering which
required us to use a separate source package.

Therefore, please remove source libgweather.


There is one remaining reverse dependency: gnome-shell-xrdesktop which
already has unfulfillable dependencies and should probably be removed
from Unstable soon anyway. See https://bugs.debian.org/1008471 but I
think it's appropriate to give a little more time to the Maintainer to
respond before taking further action there.

The only open libgweather bugs in Debian are very old and I'm fine
with having them closed since they don't look valid any more to me.

On behalf of the Debian GNOME Team,
Jeremy Bicha

Bug#1009008: Development package should depend in libsqlite3-dev

[Pierre Gruet]

Package: libdlib-dev
Version: 19.10-3.1
Severity: normal

Dear Maintainer,

I think libdlib-dev should depend on libsqlite3-dev. For instance the former
installs /usr/include/dlib/sqlite/sqlite.h, which attempts to include
/usr/include/sqlite3.h, which lies in the latter.

Kind regards,

-- 
Pierre Gruet

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

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

Versions of packages libdlib-dev depends on:
pn  libdlib19  

libdlib-dev recommends no packages.

libdlib-dev suggests no packages.

Bug#1005140: ujson: CVE-2021-45958

[Salvatore Bonaccorso]

Hi,

On Mon, Feb 07, 2022 at 08:55:00PM +0100, Salvatore Bonaccorso wrote:
> On Mon, Feb 07, 2022 at 08:48:13PM +0100, Salvatore Bonaccorso wrote:
> > Source: ujson
> > Version: 5.1.0-1
> > Severity: important
> > Tags: security upstream
> > Forwarded: https://github.com/ultrajson/ultrajson/issues/502 
> > https://github.com/ultrajson/ultrajson/issues/501
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> > 
> > Control: found -1 4.0.2-1
> > Control: found -1 1.35-3
> > 
> > Hi,
> > 
> > The following vulnerability was published for ujson.
> > 
> > CVE-2021-45958[0]:
> > | ** https://cve.mitre.org/about/faqs.html#disputed_signify_in_
> > | cve_entry">DISPUTED ** UltraJSON (aka ujson) 4.0.2 through 5.0.0
> > | has a stack-based buffer overflow in Buffer_AppendIndentUnchecked
> > | (called from encode). NOTE: multiple third parties dispute whether
> > | this is a confirmed finding, because the event that caused the
> > | Reproducer Testcase to stop indicating a buffer overflow was a change
> > | to the AFLplusplus project (5525f8c9ef8bb879dadd0eb942d524827d1b0362),
> > | not a change to the UltraJSON project.
> 
> Just some context: The CVE was initially disputed since it was not
> quite clear if this is a flaw in ujson and later just not triggered
> anymore or if an issue in the AFL++ fuzzer. Upstream issues 501 and
> 502 though give more details and as well information on how to
> reproduce.

Upstream has addressed this issue by means of
https://github.com/ultrajson/ultrajson/pull/519 .

Regards,
Salvatore

Bug#1009007: ITP: r-cran-officer -- GNU R manipulation of Microsoft Word and PowerPoint documents

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-officer -- GNU R manipulation of Microsoft Word and 
PowerPoint documents
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-officer
  Version : 0.4.2
  Upstream Author : David Gohel,
* URL : https://cran.r-project.org/package=officer
* License : GPL-3
  Programming Lang: GNU R
  Description : GNU R manipulation of Microsoft Word and PowerPoint 
documents
 Access and manipulate 'Microsoft Word' and 'Microsoft PowerPoint'
 documents from R. The package focuses on tabular and graphical reporting
 from R; it also provides two functions that let users get document
 content into data objects. A set of functions lets add and remove
 images, tables and paragraphs of text in new or existing documents. The
 package does not require any installation of Microsoft products to be
 able to write Microsoft files.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-officer

Bug#999287: binfmtc: diff for NMU version 0.17-2.1

[Marcos Talau]

Control: tags 999287 + patch
Control: tags 999287 + pending

Dear maintainer,

I've prepared an NMU for binfmtc (versioned as 0.17-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u binfmtc-0.17/debian/changelog binfmtc-0.17/debian/changelog
--- binfmtc-0.17/debian/changelog
+++ binfmtc-0.17/debian/changelog
@@ -1,3 +1,10 @@
+binfmtc (0.17-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999287).
+
+ -- Marcos Talau   Tue, 05 Apr 2022 14:14:58 -0300
+
 binfmtc (0.17-2) unstable; urgency=medium
 
   * Update debheper compat level 9, and check with debdiff.
diff -u binfmtc-0.17/debian/rules binfmtc-0.17/debian/rules
--- binfmtc-0.17/debian/rules
+++ binfmtc-0.17/debian/rules
@@ -81,4 +81,6 @@
 	dh_builddeb
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+build-arch: build
+build-indep: build
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install configure

Bug#1009006: cntlm: Switch to (likely) maintained fork of upstream project

[Salvatore Bonaccorso]

Source: cntlm
Version: 0.92.3-1
Severity: normal
X-Debbugs-Cc: car...@debian.org,t...@security.debian.org

Hi

For cntlm there seem a maintained fork upstream at
https://github.com/versat/cntlm .

If cntlm is continued to be provided in Debian, probably we should
switch to the active project.

Alternatively, cntlm could be removed as a first strep from unstable
(it is already gone in testing due to #965463).

Regards,
Salvatore

Bug#999197: bitlbee: diff for NMU version 3.6-1.3

[Marcos Talau]

Control: tags 999197 + patch
Control: tags 999197 + pending

Dear maintainer,

I've prepared an NMU for bitlbee (versioned as 3.6-1.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u bitlbee-3.6/debian/changelog bitlbee-3.6/debian/changelog
--- bitlbee-3.6/debian/changelog
+++ bitlbee-3.6/debian/changelog
@@ -1,3 +1,10 @@
+bitlbee (3.6-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999197).
+
+ -- Marcos Talau   Tue, 05 Apr 2022 14:18:09 -0300
+
 bitlbee (3.6-1.2) unstable; urgency=medium
 
   [ Matthias Klose ]
diff -u bitlbee-3.6/debian/rules bitlbee-3.6/debian/rules
--- bitlbee-3.6/debian/rules
+++ bitlbee-3.6/debian/rules
@@ -125,4 +125,6 @@
 	DH_OPTIONS=-p$* $(MAKE) -f debian/rules binary-common
 
 binary: binary-arch
-.PHONY: build clean binary-arch binary-common binary install
+build-arch: build
+build-indep: build
+.PHONY: build build-arch build-indep clean binary-arch binary-common binary install

Bug#1008741: whipper: please update to latest upstream version

[Krzysztof Krzyżaniak]

Ok, I'll do that. Thnx. Patches are trivial (attached initial version) but
of course, I can push them (or anyone can) later.

  eloy

wt., 5 kwi 2022 o 19:27 Louis-Philippe Véronneau 
napisał(a):

> On Tue, 5 Apr 2022 11:17:07 -0400
> =?UTF-8?Q?Louis-Philippe_V=c3=a9ronneau?=  wrote:
> > On 2022-04-04 09 h 10, Krzysztof Krzyżaniak wrote:
> > > Feel free to move the project into Debian Python Team. As for the last
> > > upstream version either the missing dependency has to be packaged first
> > > (discid) or a small patch that replaces discid with python-libdiscid
> which
> > > is already packaged in debian.
> >
> > I'd be happy to take care of this issue and upload the latest upstream
> > version.
> >
> > Could you move the repository to the DPT yourself? I can't do this
> > myself, as I'm not the owner :) That would entail you asking to join the
> > Team if you are not already part of it though [1].
> >
> > Otherwise, I can also ask the Salsa Team to move it for you.
>
> Oh, I just realised it's in /debian, so only the Salsa Admins can move
> it. As such, I've opened an issue to ask them to do so [1].
>
> It would still probably be a good idea for you to join the DPT if it's
> not already the case, as otherwise you'll loose access to it.
>
> [1]: https://salsa.debian.org/salsa/support/-/issues/293
>
> --
>   ⢀⣴⠾⠻⢶⣦⠀
>   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
>   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
>   ⠈⠳⣄
>


whipper_0.10.0-1.diff.HrGIjP
Description: Binary data


whipper_0.10.0-1.diff.HPlec9
Description: Binary data

Bug#1009005: clockdiff: host is down

[Jaap van Wingerde]

Package: iputils-clockdiff
Version: 3:20211215-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

jaap@jaap:~$ sudo clockdiff -V
clockdiff from iputils 20211215
jaap@jaap:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
jaap@jaap:~$ ping -c 1 google.com
PING google.com(ams15s40-in-x0e.1e100.net (2a00:1450:400e:80d::200e)) 56 data
bytes
64 bytes from ams15s40-in-x0e.1e100.net (2a00:1450:400e:80d::200e): icmp_seq=1
ttl=118 time=11.9 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 11.930/11.930/11.930/0.000 ms
jaap@jaap:~$ sudo clockdiff google.com
clockdiff: google.com is down
jaap@jaap:~$ sudo clockdiff -o google.com
clockdiff: google.com is down
jaap@jaap:~$ sudo clockdiff -o1 google.com
clockdiff: google.com is down
jaap@jaap:~$ ping -c 1 google.com
PING google.com(ams15s22-in-x0e.1e100.net (2a00:1450:400e:801::200e)) 56 data
bytes
64 bytes from ams15s22-in-x0e.1e100.net (2a00:1450:400e:801::200e): icmp_seq=1
ttl=118 time=11.9 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 11.879/11.879/11.879/0.000 ms
jaap@jaap:~$

Maybe there is upstream a fix: .


-- 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.16.0-0.bpo.4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8),
LANGUAGE=nl:en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iputils-clockdiff depends on:
ii  libc62.31-13+deb11u3
ii  libcap2  1:2.44-1

iputils-clockdiff recommends no packages.

iputils-clockdiff suggests no packages.

Bug#999104: brag: diff for NMU version 1.4.1-2.2

[Marcos Talau]

Control: tags 999104 + patch
Control: tags 999104 + pending

Dear maintainer,

I've prepared an NMU for brag (versioned as 1.4.1-2.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -u brag-1.4.1/debian/changelog brag-1.4.1/debian/changelog
--- brag-1.4.1/debian/changelog
+++ brag-1.4.1/debian/changelog
@@ -1,3 +1,10 @@
+brag (1.4.1-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules: Add build-{arch,indep} (Closes: #999104).
+
+ -- Marcos Talau   Tue, 05 Apr 2022 14:22:15 -0300
+
 brag (1.4.1-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u brag-1.4.1/debian/rules brag-1.4.1/debian/rules
--- brag-1.4.1/debian/rules
+++ brag-1.4.1/debian/rules
@@ -32,7 +32,9 @@
 binary: binary-indep
 binary-arch:
 build:
-.PHONY: build clean binary-indep binary-arch binary
+build-arch: build
+build-indep: build
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary
 
 
 

Bug#1009004: src:mlpack: fails to migrate to testing for too long: depends on non-existing packages

[Paul Gevers]

Source: mlpack
Version: 3.4.2-1
Severity: serious
Control: close -1 3.4.2-5
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:mlpack has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package python3-mlpack 
depends on packages that don't exist (3.9 and 3.10). It looks like 
that's a mistake in the build as these look like the python versions 
(there seems to be one "," too many in the debian/control file). Also, 
it build-depends on libomp-dev which isn't available on s390x, 
preventing a build on that architecture.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=mlpack



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009003: Please be prepared for hmat-oss upcoming transition

[Pierre Gruet]

Source: openturns
Version: 1.10-5
Severity: important

Hello,

This is to inform you that hmat-oss, a dependency of openturns, is in
experimental and waits for a transition. It will cause openturns to ftbfs.

Right now I am working on openturns so that it is ready for the transition of
hmat-oss. I won't ask for a transition slot before I am ready to source-upload
openturns accordingly.

Best,

-- 
Pierre

Bug#1008998: pkexec: getting blank lines in a loop on the console

[Patrice Duroux]

Very clear explanation but not easy to solve if I understand!
Sorry for the noise.
Thanks,
Patrice

Bug#961970: vmpk: Please change to Architecture: linux-any

[Pedro Lopez-Cabanillas]

> vmpk is linux specific (#557899).

This was true many years ago, when vmpk was based on RtMidi. It was  
replaced by drumstick-rt in vmpk-0.6.0 released in 2014-09-07.

Since then, vmpk has been successfully ported to FreeBSD.
https://www.freshports.org/audio/vmpk
https://www.freshports.org/audio/drumstick

Regards,
Pedro

Bug#1009002: simple-cdd: Upcoming change to debian-cd will break BOOT_TIMEOUT parameter

[Samuel Thibault]

Hello,

Jonathan Hettwer (bauen1), le mar. 05 avril 2022 20:45:09 +0200, a ecrit:
> The commit is 
> https://salsa.debian.org/installer-team/debian-installer/-/commit/3010162acb02dae36db6354e9ad13891dff980c2
> 
> After this change specifying BOOT_TIMEOUT no longer changes the actual
> timeout, it will be 30s regardless of the value specified.

Which is because simple-cdd patches the existing "timeout 0" line, but
now it's before the spk*.cfg timeout lines, and thus overriden by them.

simple-cdd can instead just append a timeout line to the main
configuration file, thus overriding anything else.

> The default boot option will also not be the "Graphic Installation", but
> the speech synthesis installation.

Indeed, that's intentional. I guess a simple way to patch over it would
be to drop any ontimeout line with

sed -i '/^ontimeout /d' *.cfg

so that it's indeed the default selection line which gets booted.

Samuel

Bug#1008752: avifile: autopkgtest regression on armhf: Bus error

[Paul Gevers]

Hi,

On 04-04-2022 23:11, Ying-Chun Liu (PaulLiu) wrote:
It is because your environment supports "neon" and ffmpeg will use that 
for acceleration.


I wonder.


But abel and qemu-user-static doesn't support neon.
I think if you "cat /proc/cpuinfo" and neon will be in the Features.


root@ci-worker-armel-01:~# cat /proc/cpuinfo | grep neon
root@ci-worker-armel-01:~#

Nope.

Features: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics 
fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs


I now notice that the list of flags is also in the gdb output. If 
anything, it more looks like ffmpeg *thinks* it can use neon, but can't. 
Would that be a bug in ffmpeg?


I'll see if I can use cpuflags in ffmpeg to disable neon on my test. So 
that it can pass.


Ack, but I wonder if the bug needs to be cloned an reassigned to ffmpeg 
then, for detecting neon when not available.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

[Maximilian Stein]

Run 'gem env gempath' and set GEM_PATH variable with this value and 
/var/lib/gitlab/.gem added in /etc/gitlab/gitlab-debian.conf

I will try to do this automatically too.



This has indeed worked immediately. Thank you very much for the fast 
support!


Best
Maximilian



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1009002: simple-cdd: Upcoming change to debian-cd will break BOOT_TIMEOUT parameter

[Jonathan Hettwer (bauen1)]

Package: simple-cdd
Severity: normal
X-Debbugs-Cc: j24...@gmail.com

Hi,

An upcoming change in debian-cd makes changes to the isolinux
configuration, thus simple-cdds BOOT_TIMEOUT no longer has the expected
effect.

The commit is 
https://salsa.debian.org/installer-team/debian-installer/-/commit/3010162acb02dae36db6354e9ad13891dff980c2

After this change specifying BOOT_TIMEOUT no longer changes the actual
timeout, it will be 30s regardless of the value specified.
The default boot option will also not be the "Graphic Installation", but
the speech synthesis installation.

I was asked on the #debian-boot irc channel to report this here.

Thanks,
Jonathan Hettwer

-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.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: SELinux: enabled - Mode: Enforcing - Policy name: bauen1-policy

Versions of packages simple-cdd depends on:
pn  dctrl-tools 
pn  debian-cd   
pn  lsb-release 
ii  python3 3.9.8-1
pn  python3-simple-cdd  
pn  reprepro
ii  rsync   3.2.3-8
ii  wget1.21.2-2+b1

Versions of packages simple-cdd recommends:
ii  dose-distcheck  7.0.0-1+b1

Versions of packages simple-cdd suggests:
ii  qemu-system 1:6.2+dfsg-3
ii  qemu-system-x86 [qemu-kvm]  1:6.2+dfsg-3

Bug#920485: mplayer gets signal 6 when playing ogg video files

[Reimar Döffinger]

> On 19 Mar 2022, at 15:03, Diederik de Haas  wrote:
> 
> On Saturday, 19 March 2022 13:57:49 CET Reimar Döffinger wrote:
>>> On 16 Mar 2022, at 20:01, Diederik de Haas  wrote:
>>> [VD_FFMPEG] DRI failure.
>>> mplayer: libmpcodecs/vf.c:286: vf_get_image: Assertion `w == -1 || w >=
>>> vf->w' failed.
>> Is it intentional that debian compiles with --enable-debug?
>> That's the reason I could never reproduce this, as it's off by default.
>> I think this is simply a case of bad asserts, but I should double-check.
>> The video plays fine with 1.5 if compiled without --enable-debug, I suspect
>> it's the same for 1.4.
> 
> I don't know, but searching the repo, I found the following commit:
> https://salsa.debian.org/multimedia-team/mplayer/-/commit/63f84eb8b014724263447bc37927154bec2ac5e7
> 
> It's from 12 years ago, so I don't know if the logic from then still applies.
> It does talk about 'mplayer-dbg', but AFAIK nowadays there should be
> (automatic?) debug packages and those are (usually?)named -dbgsym.
> You as one of the (new) maintainers can make a different choice then was made
> back then.

I suspect the problem might be that MPlayer by default does not compile with 
debug symbols.
This should be addressed by adding the desired -g options to --extra-cflags and 
--extra-ldflags configure options instead.
Admittedly --enable-debug is documented doing that, but it does more... Sigh... 
Fixed that as well upstream.

> OTOH, I'd guess that an assert would signal an actual problem and *hiding* it
> by no longer compiling with '--enable-debug' seems wrong.
> When the assert itself is wrong, then that should be corrected.

The problem is that too few people run MPlayer with --enable-debug, so the 
quality of the asserts is not well tested.
I removed the 2 relevant asserts in MPlayer SVN r38362.

--- libmpcodecs/vf.c(revision 38361)
+++ libmpcodecs/vf.c(working copy)
@@ -283,8 +283,6 @@
   int missing_palette;
 
 #ifdef MP_DEBUG
-  assert(w == -1 || w >= vf->w);
-  assert(h == -1 || h >= vf->h);
   assert(vf->w > 0);
   assert(vf->h > 0);
 #endif

Bug#1008998: pkexec: getting blank lines in a loop on the console

[Simon McVittie]

Control: reassign -1 src:mutter
Control: forwarded -1 https://gitlab.gnome.org/GNOME/mutter/-/issues/2194
Control: affects -1 + gnome-shell policykit-1

On Tue, 05 Apr 2022 at 19:50:55 +0200, Patrice Duroux wrote:
> I am using a GNOME desktop session (Wayland) and use synaptic(-pkexec) to
> upgrade my system.
> But once, I run it through a terminal and the output was feed by new lines in 
> a
> kind of loop
> while 'sudo synaptic' was not.
> Finally I found that this can be reproduced by any 'pkexec ...' command, for
> instance 'pkexec ls'.

This is a problem with the implementation of the password prompt in GNOME
Shell, rather than a polkit bug as such. The problem is that when you
press Enter to run the pkexec command, the modal password prompt can pop up
before you have released the key; then the terminal in the background
doesn't get the key-release event, so it thinks the Enter key is still
being held down. I think this is a GNOME 42 regression. Upstream are aware
and are looking into it.

https://gitlab.gnome.org/GNOME/mutter/-/issues/2194 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5242 upstream.

smcv

Bug#1008932: gitlab-sidekiq cannot find graphiql-rails

[Maximilian Stein]

A little addition: To also get gitlab-rake working, I needed to add 
GEM_PATH to the list of exported variables in /usr/sbin/gitlab-rake.


Best,
Maximilian



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008997: cups: impossible to print on hp envy 5536 from sid

[Brian Potkin]

severity 1008997 normal
tags 1008997 - upstream
thanks



On Tue 05 Apr 2022 at 19:10:14 +0200, alain wrote:

> Package: cups
> Version: 2.4.1op1-2
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: compte.perso.de-al...@bbox.fr
> 
> Hello.
> I'm writing to you because for the last week ,
> I have printing problems with cups.
> I can't get anything despite my research.
> I don't even have the test page.

Thank you for your report, Alain. However, it reads more like a request
for help rather than pointing to a a bug in the printing system. Still,
we can help you with that.

> Here is my research:
> https://debian-facile.org/viewtopic.php?id=31739
> old thread : (abandoned)
> https://debian-facile.org/viewtopic.php?id=31698
> 
> I thought, at the beginning, that the problem came from dpkg.
> because of the concomitance with its update.
> I asked the bts for help but it failed.
> Maybe I did too much?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008716
> 
> under bullseye stable, everything works perfectly.
> either under bookkworm or testing (tested quickly)
M
> and even more so, under sid (my distribution),
> nothing works. no way to print even a test page.
> 
> I tried everything, I can't get anything.
> That's why I write to you.
> Can you help me ?
> please ?
> Thank you.
> respectfully,
> alain .

Let's be clear; you are using unstable? Is the printer USB or network
connected?

Regards,

Brian.

Bug#1009001: ITP: golang-github-99designs-httpsignatures-go -- Go library for creating and handling http-signatures

[Sebastian Crane]

Package: wnpp
Severity: wishlist
Owner: Sebastian Crane 

* Package name: golang-github-99designs-httpsignatures-go
  Version : 0.0~git20170731.88528bf-1
  Upstream Author : Adam Scarr 
* URL : https://github.com/99designs/httpsignatures-go
* License : Expat
  Programming Lang: Go
  Description : Go library for creating and handling http-signatures

This library allows Go programs to create and verify cryptographic
signatures that follow the HTTP Message Signatures specification
(currently an IETF draft).

This is a required dependency of Woodpecker CI (see ITP #1008934). I
intend to maintain this package as a member of the Debian Go Packaging
Team.

Bug#1008546: gnome-shell-extension-easyscreencast: does not declare compatibility with GNOME Shell 42

[Samuel Henrique]

Control: forwarded -1
https://github.com/EasyScreenCast/EasyScreenCast/issues/323

Now that Gnome 42 comes with an improved screencasting feature, this
extension might become obsolete.

I suggest users try it out since this extension doesn't support the
new release: You can try the new tool by pressing the print screen
button (it's not the same thing as the screenshot application Gnome
has).

I'll also update this extension in case upstream makes a new release
supporting Gnome 42.

Cheers,

-- 
Samuel Henrique 

Bug#1008999: xfburn: Homepage moved

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, 2022-04-05 at 13:57 -0400, Boyuan Yang wrote:
> Dear Debian xfburn package maintainer,
> 
> Currently the documented xfburn homepage information is defunct. The new
> homepage is located at https://docs.xfce.org/apps/xfburn/start .
> 
> Such information change can be found at
> https://gitlab.xfce.org/apps/xfburn/-/commit/400c9fdabe6310ef88896156fa3d25778291350e
> . 
Thanks, I've updated the repository and it should be fixed in the next upload.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmJMhFwACgkQ3rYcyPpX
RFsdTQf/Yu1OTzL0w98DfDNncENz3A9VlNi2IwLYdz3Y53yjAoH86iBoVxeYGJI2
e/ucgiKFSGlgJgwENxj9f9v0wp8SQr6bxOw8ZiKjfWvGuB6n81BOes/hyLUmwQSG
IOeJga2Sm9nvMZ/myL65vqYgNa0XW/asfd5cu7R3IeQy1zpg8r91II3miym29sJf
9nD21ehbDIH3pNVjFBP6WqxEL+Jrotamwpnlj8hfVUoxM+x8oIsriJMLaioWkE2a
xtZlVdRXgV5E+RkR4HB9kzb/UAtnJeAQKU+V59tRIPQFwp/KrLaF02BNyblaQgfU
5jBPTOvzxhOm0N3Xq5oSoco8y4EQmg==
=mqbF
-END PGP SIGNATURE-

Bug#1009000: paprefs: Please package 1.2

[Jeremy Bicha]

Source: paprefs
Version: 1.1-2
Severity: wishlist

Please package paprefs. It adds compatibility with PulseAudio 16

https://freedesktop.org/software/pulseaudio/paprefs/

Thank you,
Jeremy Bicha

Bug#1008999: xfburn: Homepage moved

[Boyuan Yang]

Package: xfburn
Severity: normal
Version: 0.6.2-1
X-Debbugs-CC: cor...@debian.org

Dear Debian xfburn package maintainer,

Currently the documented xfburn homepage information is defunct. The new
homepage is located at https://docs.xfce.org/apps/xfburn/start .

Such information change can be found at
https://gitlab.xfce.org/apps/xfburn/-/commit/400c9fdabe6310ef88896156fa3d25778291350e
. 

Thanks,
Boyuan Yang


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

Bug#1008998: pkexec: getting blank lines in a loop on the console

[Patrice Duroux]

Package: pkexec
Version: 0.105-33
Severity: normal

Dear Maintainer,

I am using a GNOME desktop session (Wayland) and use synaptic(-pkexec) to
upgrade my system.
But once, I run it through a terminal and the output was feed by new lines in a
kind of loop
while 'sudo synaptic' was not.
Finally I found that this can be reproduced by any 'pkexec ...' command, for
instance 'pkexec ls'.

Regards,
Patrice


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

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

Versions of packages pkexec depends on:
ii  libc6  2.33-7
ii  libglib2.0-0   2.72.0-1+b1
ii  libpam0g   1.4.0-11
ii  libpolkit-agent-1-00.105-33
ii  libpolkit-gobject-1-0  0.105-33
ii  polkitd0.105-33

pkexec recommends no packages.

pkexec suggests no packages.

Versions of packages pkexec is related to:
pn  elogind 
pn  libpam-elogind  
ii  libpam-systemd  250.4-1
ii  systemd 250.4-1

-- no debconf information

Bug#1008741: whipper: please update to latest upstream version

[Louis-Philippe Véronneau]

On Tue, 5 Apr 2022 11:17:07 -0400
=?UTF-8?Q?Louis-Philippe_V=c3=a9ronneau?=  wrote:
> On 2022-04-04 09 h 10, Krzysztof Krzyżaniak wrote:
> > Feel free to move the project into Debian Python Team. As for the last
> > upstream version either the missing dependency has to be packaged first
> > (discid) or a small patch that replaces discid with python-libdiscid which
> > is already packaged in debian.
> 
> I'd be happy to take care of this issue and upload the latest upstream
> version.
> 
> Could you move the repository to the DPT yourself? I can't do this
> myself, as I'm not the owner :) That would entail you asking to join the
> Team if you are not already part of it though [1].
> 
> Otherwise, I can also ask the Salsa Team to move it for you.

Oh, I just realised it's in /debian, so only the Salsa Admins can move
it. As such, I've opened an issue to ask them to do so [1].

It would still probably be a good idea for you to join the DPT if it's
not already the case, as otherwise you'll loose access to it.

[1]: https://salsa.debian.org/salsa/support/-/issues/293

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Bug#1008997: cups: impossible to print on hp envy 5536 from sid

[alain]

Package: cups
Version: 2.4.1op1-2
Severity: important
Tags: upstream
X-Debbugs-Cc: compte.perso.de-al...@bbox.fr

Hello.
I'm writing to you because for the last week ,
I have printing problems with cups.
I can't get anything despite my research.
I don't even have the test page.

Here is my research:
https://debian-facile.org/viewtopic.php?id=31739
old thread : (abandoned)
https://debian-facile.org/viewtopic.php?id=31698

I thought, at the beginning, that the problem came from dpkg.
because of the concomitance with its update.
I asked the bts for help but it failed.
Maybe I did too much?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008716

under bullseye stable, everything works perfectly.
either under bookkworm or testing (tested quickly)
and even more so, under sid (my distribution),
nothing works. no way to print even a test page.

I tried everything, I can't get anything.
That's why I write to you.
Can you help me ?
please ?
Thank you.
respectfully,
alain .




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

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

Versions of packages cups depends on:
ii  cups-client2.4.1op1-2
ii  cups-common2.4.1op1-2
ii  cups-core-drivers  2.4.1op1-2
ii  cups-daemon2.4.1op1-2
ii  cups-filters   1.28.13-1
ii  cups-ppdc  2.4.1op1-2
ii  cups-server-common 2.4.1op1-2
ii  debconf [debconf-2.0]  1.5.79
ii  ghostscript9.56.0~dfsg-1
ii  libavahi-client3   0.8-5
ii  libavahi-common3   0.8-5
ii  libc6  2.33-7
ii  libcups2   2.4.1op1-2
ii  libgcc-s1  12-20220319-1
ii  libstdc++6 12-20220319-1
ii  libusb-1.0-0   2:1.0.25-1
ii  poppler-utils  22.02.0-3
ii  procps 2:3.3.17-7+b1

Versions of packages cups recommends:
ii  avahi-daemon  0.8-5
ii  colord1.4.6-1

Versions of packages cups suggests:
ii  cups-bsd   2.4.1op1-2
pn  cups-pdf   
pn  foomatic-db-compressed-ppds | foomatic-db  
pn  smbclient  
ii  udev   250.4-1

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: lpd, socket, usb, snmp, dnssd

Bug#1008996: opentsne builds with -march=native on amd64

[Adrian Bunk]

Source: opentsne
Version: 0.6.1-2
Severity: serious

Building with -march=native means the package will only work
on machines compatible with whatever buildd built it.

Please remove the -march=native from setup.py.

Bug#1008995: netplan.io: Two minute delay during startup caused by systemd-networkd-wait-online.service

[Lupe Christoph]

Package: netplan.io
Version: 0.101-4
Severity: normal




-- 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-13-amd64 (SMP w/1 CPU thread)
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 netplan.io depends on:
ii  iproute2   5.10.0-4
ii  libc6  2.31-13+deb11u3
ii  libglib2.0-0   2.66.8-1
ii  libnetplan00.101-4
ii  libsystemd0247.3-7
ii  libuuid1   2.36.1-8+deb11u1
ii  python33.9.2-3
ii  python3-netifaces  0.10.9-0.2+b3
ii  python3-yaml   5.3.1-5
ii  systemd247.3-7

netplan.io recommends no packages.

Versions of packages netplan.io suggests:
pn  network-manager | wpasupplicant  
pn  openvswitch-switch   

-- no debconf information

I had already filed this as #1008955, but was asked to refile against 
netplan.io. I'm just pasting the original text.

This is on a server that has gone through many Debian releases. We
have not noticed until recently that ifupdown is deprecated. I started
converting from ifupdown to Netplan first on my home machines (Ubuntu
21.10), then worked on the server I'm sending this bug report from
(Debian 11). I'm sorry, but I did not yet try to see if the same is
happening on the two Ubuntu machines.

When I first rebooted the machine to see if the new configuration
was being stared OK (I had left out a Netplan configuration for lo,
noticing that lo was configured by default), there was a significant
delay. I later found out that it was exactly two minutes long.

systemd-analyze blame pointed to systemd-networkd-wait-online.service:
2min 363ms systemd-networkd-wait-online.service

I tried ignoring unimportant interfaces, but no dice. So I ran an strace
on /lib/systemd/systemd-networkd-wait-online (attached). I failed to
understand what is really going on, but the program configures a epoll
instance. After some successful use of that something fails to happen
and the two minute timeout strikes. During that timeout, the program is
repeatedly looking at /run/systemd/netif/links/1, but it does not change.

The machine has four interfaces: lo, ens3, dummy1 and
tun0. /run/systemd/netif/links/2 and /run/systemd/netif/links/3 are ens3
and dummy1, 4 is probably tun0, being the last created, and the state
is ADDRESS_STATE=routable.

But /run/systemd/netif/links/1 is strange. This should be lo, but lo is 
configured:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever

but /run/systemd/netif/links/1 is
ADMIN_STATE=unmanaged
OPER_STATE=carrier
CARRIER_STATE=carrier
ADDRESS_STATE=off

So I thought that adding a netplan configuration for lo might help. Well,
it doesn't. The strace is the same, except for the contents of the
netif file.
389   22:18:52.615037 execve("/lib/systemd/systemd-networkd-wait-online", 
["/lib/systemd/systemd-networkd-wait-online", "--ignore=tun0", 
"--ignore=dummy1"], 0x7fffbc86c690 /* 5 vars */) = 0
389   22:18:52.616756 brk(NULL) = 0x55e209ce8000
389   22:18:52.616818 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such 
file or directory)
389   22:18:52.616924 openat(AT_FDCWD, 
"/lib/systemd/tls/haswell/x86_64/libsystemd-shared-247.so", O_RDONLY|O_CLOEXEC) 
= -1 ENOENT (No such file or directory)
389   22:18:52.617325 stat("/lib/systemd/tls/haswell/x86_64", 0x7fff73610790) = 
-1 ENOENT (No such file or directory)
389   22:18:52.617759 openat(AT_FDCWD, 
"/lib/systemd/tls/haswell/libsystemd-shared-247.so", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
389   22:18:52.617790 stat("/lib/systemd/tls/haswell", 0x7fff73610790) = -1 
ENOENT (No such file or directory)
389   22:18:52.617814 openat(AT_FDCWD, 
"/lib/systemd/tls/x86_64/libsystemd-shared-247.so", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
389   22:18:52.617839 stat("/lib/systemd/tls/x86_64", 0x7fff73610790) = -1 
ENOENT (No such file or directory)
389   22:18:52.617861 openat(AT_FDCWD, 
"/lib/systemd/tls/libsystemd-shared-247.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT 
(No such file or directory)
389   22:18:52.617885 stat("/lib/systemd/tls", 0x7fff73610790) = -1 ENOENT (No 
such file or directory)
389   22:18:52.617908 openat(AT_FDCWD, 
"/lib/systemd/haswell/x86_64/libsystemd-shared-247.so", O_RDONLY|O_CLOEXEC) = 
-1 ENOENT (No such file or directory)
389   22:18:52.617932 stat("/lib/systemd/haswell/x86_64", 0x7fff73610790) = -1 
ENOENT (No such file or directory)
389   22:18:52.617955 openat(AT_FDCWD, 
"/lib/systemd/haswell/libsystemd-shared-247.so", 

Bug#1008776: intel-media-va-driver: Segmentation fault with gstreamer based applications

[Sebastian Ramacher]

Control: tags -1 moreinfo

Hi Kai

On 2022-04-01 20:10:56, Kai Weber wrote:
> Package: intel-media-va-driver
> Version: 22.3.0+dfsg1-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: kai.weber+deb...@glorybox.de
> 
> Dear Maintainer,
> 
> since a recent update (can not excalty determine the date) gstreamer based 
> applications like totem or gst-play-1.0 itself segfault on video files.
> 
> Removing intel-media-va-driver resolves the issue.
> Installing intel-media-va-driver-non-free resolves the issue.
> 
> Attached is a backtrace. I have no experience getting backtraces. This one 
> was achieved after install the intel-media-va-driver-dbgsym package and 
> running
> 
> $ export DEBUGINFOD_URLS="https://debuginfod.debian.net;
> $ gdb --args gst-play-1.0 /home/kai/Downloads/pony.mp4 --videosink=glimagesink
> Thread 14 "qtdemux0:sink" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffb77fe640 (LWP 22147)]
> 0x7fffb5f906be in KernelDll_AllocateStates (pKernelBin=, 
> uKernelSize=0, pFcPatchCache=0x0, 
> uFcPatchCacheSize=, pDefaultRules=0x0, 
> ModifyFunctionPointers=0x0)
> at ./media_driver/agnostic/common/vp/kdll/hal_kerneldll.c:2791
> Download failed: Invalid argument.  Continuing without source file 
> ./obj-x86_64-linux-gnu/media_driver/./media_driver/agnostic/common/vp/kdll/hal_kerneldll.c.
> 2791./media_driver/agnostic/common/vp/kdll/hal_kerneldll.c: No such file 
> or directory.
> (gdb) set logging file backtrace.log
> (gdb) set logging on
> Copying output to backtrace.log.
> (gdb) bt
> ...
> (gdb) set logging off
> Done logging to backtrace.log.
> (gdb) quit

That could be another case of the driver expecting to have a kernel
available which in fact is disabled in the open source build. If
22.3.1+dfsg1-1 doesn't fix the issue for you, please let my know your
CPU/GPU so that the issue can be reported upstream.

Cheers

> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.16.0-6-amd64 (SMP w/8 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 intel-media-va-driver depends on:
> ii  libc6   2.33-7
> ii  libgcc-s1   12-20220319-1
> ii  libigdgmm12 22.1.2+ds1-1
> ii  libstdc++6  12-20220319-1
> ii  libva2 [libva-driver-abi-1.14]  2.14.0-1
> 
> intel-media-va-driver recommends no packages.
> 
> intel-media-va-driver suggests no packages.
> 
> -- no debconf information

> #0  0x7fffb5f906be in KernelDll_AllocateStates (pKernelBin= out>, uKernelSize=0, pFcPatchCache=0x0, 
> uFcPatchCacheSize=, pDefaultRules=0x0, 
> ModifyFunctionPointers=0x0)
> at ./media_driver/agnostic/common/vp/kdll/hal_kerneldll.c:2791
> #1  0x7fffb5f82028 in VphalRenderer::Initialize (this=0x7fffa813d480, 
> pSettings=0x7fffb77fae80, isApoEnabled=)
> at ./media_driver/agnostic/common/vp/hal/vphal_renderer.cpp:1418
> #2  0x7fffb5f67a89 in VphalState::Allocate (this=0x7fffa8123e50, 
> pVpHalSettings=0x7fffb77fae80)
> at ./media_driver/agnostic/common/vp/hal/vphal.cpp:201
> #3  0x7fffb61848a2 in DdiVp_InitVpHal (pVpCtx=0x7fffa812add0) at 
> ./media_driver/linux/common/vp/ddi/media_libva_vp.c:1811
> #4  0x7fffb6189460 in DdiVp_InitCtx (pVaDrvCtx=, 
> pVpCtx=0x7fffa812add0)
> at ./media_driver/linux/common/vp/ddi/media_libva_vp.c:1671
> #5  0x7fffb618985e in DdiVp_CreateContext 
> (pVaDrvCtx=pVaDrvCtx@entry=0x7fffa8081e20, vaConfigID=vaConfigID@entry=0, 
> iWidth=iWidth@entry=0, iHeight=iHeight@entry=0, iFlag=iFlag@entry=0, 
> vaSurfIDs=vaSurfIDs@entry=0x0, iNumSurfs=0, 
> pVaCtxID=0x7fffb77fb1ac) at 
> ./media_driver/linux/common/vp/ddi/media_libva_vp.c:3291
> #6  0x7fffb6147be2 in DdiMedia_PutImage (ctx=0x7fffa8081e20, surface=0, 
> image=, src_x=0, src_y=0, src_width=64, 
> src_height=64, dest_x=0, dest_y=0, dest_width=64, dest_height=64) at 
> ./media_driver/linux/common/ddi/media_libva.cpp:5535
> #7  0x7fffd425521c in vaPutImage () from /lib/x86_64-linux-gnu/libva.so.2
> #8  0x7fffd42def8d in ?? () from 
> /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
> #9  0x7fffd429d686 in ?? () from 
> /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
> #10 0x7fffd42a480e in ?? () from 
> /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
> #11 0x777ac5cb in ?? () from /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
> #12 0x777b014d in ?? () from /lib/x86_64-linux-gnu/libgstbase-1.0.so.0
> #13 0x77b912f0 in gst_pad_query () from 
> /lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
> #14 

Bug#1008994: qpdfview: Please build using QT6

[Louis-Philippe Véronneau]

Package: src:qpdfview
Severity: wishlist

Upstream now supports QT6 [1] and when the next upstream release is
made, we should aim to build it using QT6 in preparation for the
Bookworm release.

The current packaging depends on the following QT libs:

libpoppler-qt5-dev -> #1008990
libqt5svg5-dev -> libqt6svg6-dev
qt5-qmake:native   -> qmake6
qtbase5-dev-> qt6-base-dev
qttools5-dev-tools -> qt6-tools-dev-tools

So it seems the only blocker would be Poppler?

[1]: https://launchpad.net/qpdfview/+announcement/28501

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Bug#1008993: libmimalloc-dev: please include cmake config files

[Sebastian Ramacher]

Package: libmimalloc-dev
Version: 2.0.5+ds-2
Severity: wishlist

As per $subject: please include the cmake configuration files that are
installed also in the -dev package. They are very useful to work with
mimalloc from within cmake-based projects.

Cheers
-- 
Sebastian Ramacher

Bug#864555: lintian: please use a more reliable heuristic than line length to detect source-is-missing

[Bill Allombert]

On Sat, Jun 10, 2017 at 12:11:51PM -0300, David Bremner wrote:
> Package: lintian
> Version: 2.5.50.4
> Severity: normal
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> On polymake 3.1 source lintian reports:
> 
> E: polymake source: source-is-missing external/js/renderers/SVGRenderer.js 
> line length is 258 characters (>256)
> 
> An examination reveals this to be a false positive. The file is not minified, 
> but happens to contain long lines like
> 
> _svgNode.setAttribute( 'style', 'fill: none; stroke: ' + 
> material.color.getStyle() + '; stroke-width: ' + material.linewidth + '; 
> stroke-opacity: ' + material.opacity + '; stroke-linecap: ' + 
> material.linecap + '; stroke-linejoin: ' + material.linejoin );
> 
> One can argue about whether that's nice programming style, but that's not 
> really lintian's job.
> Presumably that's the way the upstream author likes to edit code.

I agree source-is-missing has far too much false positive to be useful.

To detect minified js, maybe one should also check that the lines only
have very few whitespaces, or even only whitespace between quotes.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#1008989: systemd- hwdb unexpected abort

[Michael Biebl]

Control: found -1 247.3-6
Control: forwarded -1 https://github.com/systemd/systemd/issues/22976

Thanks for your bug report.
Since I could reproduce it both on bullseye and bookworm, I've forwarded 
it upstream.


Regards,
Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008992: xwayland: all X clients hang indefinitely waiting for /tmp/.X11-unix/X0

[Harlan Lieberman-Berg]

Package: xwayland
Version: 2:22.1.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: hlieber...@debian.org

After upgrade to 2:22.1.1-1, all X applications refuse to start.  strace shows 
that they hang on connect(2), waiting for the /tmp/.X11-unix/X0 socket.

XWayland on my system is being started by Gnome/mutter, with the following 
command line showing in ps:

/usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth 
/run/user/1000/.mutter-Xwaylandauth.A4B0J1 -listen 4 -listen 5 -displayfd 6 
-initfd 7

A full strace of an xeyes session (up through ^C) is attached.


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

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xwayland depends on:
ii  libc6   2.33-7
ii  libdrm2 2.4.110-1
ii  libepoxy0   1.5.10-1
ii  libgbm1 21.3.7-1
ii  libgcrypt20 1.10.1-2
ii  libgl1  1.4.0-1
ii  libpixman-1-0   0.40.0-1
ii  libtirpc3   1.3.2-2
ii  libwayland-client0  1.20.0-1
ii  libxau6 1:1.0.9-1
ii  libxcvt00.1.1-3
ii  libxdmcp6   1:1.1.2-3
ii  libxfont2   1:2.0.5-1
ii  libxshmfence1   1.3-1
ii  xserver-common  2:21.1.3-2

xwayland recommends no packages.

xwayland suggests no packages.

-- no debconf information


xeyes.log.13007.gz
Description: application/gzip

Bug#1008991: qtsvg-opensource-src: please provide QT6 libraries

[Louis-Philippe Véronneau]

Package: src:qtsvg-opensource-src
Severity: wishlist

Dear maintainers,

Would it be possible to start providing QT6 libraries for this package?

QT6 packaging in Debian has started and a bunch of core libs and tools
are already in the archive.

If possible, I would like be able to build qpdfview using QT6 in time
for the Bookworm freeze :)

Cheers,

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Bug#1008990: poppler: please provide QT6 libraries

[Louis-Philippe Véronneau]

Package: src:poppler
Severity: wishlist

Dear maintainers,

Would it be possible to start providing QT6 libraries for this package?

QT6 packaging in Debian has started and a bunch of core libs and tools
are already in the archive.

If possible, I would like be able to build qpdfview using QT6 in time
for the Bookworm freeze :)

Cheers,

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Bug#1001661: notcurses: flaky autopkgtests on armhf

[Diederik de Haas]

On Mon, 4 Apr 2022 02:05:15 -0400 nick black  wrote:
> i'm pretty sure raspberry pi is armhf, so i ought be able to dig
> that one RPi4 i've got up and explore this. if we can reproduce
> the problem interactively, it ought fall pretty quickly.

Note that on Debian, the RPi 0/0w/1 use armel, the RPi 2 uses armhf and RPi 3
and 4 use arm64. I know RPi 0/0w/1/2/3 can (also) run in 32-bit 'mode' and
I think the RPi 4 does too (but I don't have that version).

On Mon, 4 Apr 2022 02:20:40 -0400 nick black  wrote:
> wait...even the most recent of these logs shows that it is
> testing notcurses 3.0.4, which indeed had this timing problem on
> input, which was fixed in notcurses 3.0.5:

I guess you checked the wrong log? The highest version is:
https://ci.debian.net/data/autopkgtest/testing/armhf/n/notcurses/20022214/log.gz

starting date: 2022-03-15
...
autopkgtest [22:12:59]: testbed dpkg architecture: armhf
autopkgtest [22:13:00]: testbed running kernel: Linux 5.10.0-12-arm64 #1 SMP 
Debian 5.10.103-1 (2022-03-07)
autopkgtest [22:13:00]:  apt-source notcurses
Get:1 http://deb.debian.org/debian testing/main notcurses 3.0.7+dfsg.1-1 (dsc) 
[3,148 B]
Get:2 http://deb.debian.org/debian testing/main notcurses 3.0.7+dfsg.1-1 (tar) 
[7,399 kB]
Get:3 http://deb.debian.org/debian testing/main notcurses 3.0.7+dfsg.1-1 (asc) 
[833 B]
Get:4 http://deb.debian.org/debian testing/main notcurses 3.0.7+dfsg.1-1 (diff) 
[17.3 kB]

> oh, i guess "No testing version" indicates it's gone from
> testing. so why isn't 3.0.7 in unstable the candidate for
> testing? 3.0.4 is definitely known to be bad.

https://tracker.debian.org/pkg/notcurses shows there is a version in testing.

root@bagend:~# aptitude versions notcurses-bin
Package notcurses-bin:  
p   2.2.3+dfsg.1-1stable
 500 
i   3.0.7+dfsg.1-1  
testing,unstable500 
root@bagend:~# apt-show-versions notcurses-bin
notcurses-bin:amd64/testing 3.0.7+dfsg.1-1 uptodate
notcurses-bin:arm64 not installed

And both aptitude and apt-show-versions confirm that on my machine.

HTH,
  Diederik

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

Bug#1008989: systemd- hwdb unexpected abort

[Эрик Шахов]

Package: systemd 
Version: 247 

Hi. 

Error message: Code should not be reached 'Unknown option' at 
src/hwdb/hwdb.c:102, function parse_argv(). Aborting. Aborted 

To reproduce this bug we just need to run command "systemd-hwdb 
-ust"/"systemd-hwdb -u". In normal way it must finish with "invalid option" 
error. 
Technical description: Program systemd-hwdb call function parse_argv(file 
hwdb.c:57). In « while ((c = getopt_long (argc, argv, " ust:r:h " , options, 
NULL )) >= 0 ) » (file hwdb.c:77) when we send "-u" or anything starting at 
"-u" the program will received Aborting 

System information: Linux debian 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 
(2022-03-07 ) x86_64 GNU/Linux 
libc-2.31.so 

CWE identifier for this bug: CWE- 617 : Reachable Assertion 

Way to fix this bug: Delete "ust" from « while ((c = getopt_long (argc, argv, " 
ust:r:h " , options, NULL )) >= 0 )» (file hwdb.c:77) 


Regards, 

Shahov Erik 

Bug#1008955: Bad subject, sorry

[Michael Biebl]

Am 05.04.22 um 14:25 schrieb Lupe Christoph:

My recommendation is to use systemd-timesyncd if you want to use
systemd-time-wait-sync (or disable the use systemd-time-wait-sync.service)


You seem to not have read more than the subject, where I made a
copy-and-paste-o. The entire *text* of the bug report is about
systemd-networkd-wait-online.

I can't correct the bad subject. If you can, please replace
systemd-time-wait-sync with systemd-networkd-wait-online.

Then, please read the body.
Thanks.


Please file this bug report against netplan.io.

I have no idea how it configures your network and what it does.
(and why it enabled systemd-networkd-wait-online.service).
The netplan.io maintainers can probably help you better debug netplan.io 
related issues.
If the netplan.io maintainers think there is a valid bug in 
systemd-networkd-wait-online, they can reassign this to systemd.


Regards,
Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008741: whipper: please update to latest upstream version

[Louis-Philippe Véronneau]

On 2022-04-04 09 h 10, Krzysztof Krzyżaniak wrote:
> Feel free to move the project into Debian Python Team. As for the last
> upstream version either the missing dependency has to be packaged first
> (discid) or a small patch that replaces discid with python-libdiscid which
> is already packaged in debian.

I'd be happy to take care of this issue and upload the latest upstream
version.

Could you move the repository to the DPT yourself? I can't do this
myself, as I'm not the owner :) That would entail you asking to join the
Team if you are not already part of it though [1].

Otherwise, I can also ask the Salsa Team to move it for you.

[1]:
https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst#joining-the-team

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Bug#1008984: Acknowledgement (dolphin: Restore windows after logout and next login does not work correct.)

[Günter Frenz]

Sorry, this bug was send twice due to an error message of my ISP. This
bug can be deleted.

Günter

-- 
---
Günter Frenz
Börschgasse 16a, D-51143 Köln
(h) gu...@guefz.de, gu...@freenet.de
(w) g.frenz@gso.schule.koeln
---




pgpB72yGTCusD.pgp
Description: Digitale Signatur von OpenPGP

Bug#1008984: dolphin: Restore windows after logout and next login does not work correct.

[Günter Frenz]

Package: dolphin
Version: 4:21.12.3-1
Severity: normal

Dear Maintainer,

on my desktop (KDE-plasma) I'm using 3 windows of dolphin with
different often needed folders. When I log out and subsequently log in
again the 3 windows are not restored correct. They all have the same
coordinates and the same size, so I have to rearrange the windows at
each login. The system remembers the number and content of the windows
correct, but not coordinates and size. In the previous version
everything worked fine.

Regards

Günter

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

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de:en_US Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dolphin depends on:
ii  baloo-kf5 5.90.0-1
ii  kinit 5.90.0-1
ii  kio   5.90.0-3
ii  libc6 2.33-7
ii  libdolphinvcs54:21.12.3-1
ii  libkf5activities5 5.90.0-1
ii  libkf5baloo5  5.90.0-1
ii  libkf5baloowidgets5   4:21.12.3-1
ii  libkf5bookmarks5  5.90.0-1
ii  libkf5codecs5 5.90.0-1
ii  libkf5completion5 5.90.0-1
ii  libkf5configcore5 5.90.0-1
ii  libkf5configgui5  5.90.0-1
ii  libkf5configwidgets5  5.90.1-4
ii  libkf5coreaddons5 5.90.0-1
ii  libkf5crash5  5.90.0-1
ii  libkf5dbusaddons5 5.90.0-1
ii  libkf5filemetadata3   5.90.0-1
ii  libkf5i18n5   5.90.0-1
ii  libkf5iconthemes5 5.90.0-1
ii  libkf5itemviews5  5.90.0-1
ii  libkf5jobwidgets5 5.90.0-1
ii  libkf5kcmutils5   5.90.0-2
ii  libkf5kiocore55.90.0-3
ii  libkf5kiofilewidgets5 5.90.0-3
ii  libkf5kiogui5 5.90.0-3
ii  libkf5kiowidgets5 5.90.0-3
ii  libkf5newstuff5   5.90.0-2
ii  libkf5notifications5  5.90.0-1
ii  libkf5parts5  5.90.0-1
ii  libkf5service-bin 5.90.0-1
ii  libkf5service55.90.0-1
ii  libkf5solid5  5.90.0-1
ii  libkf5textwidgets55.90.0-1
ii  libkf5widgetsaddons5  5.90.0-1
ii  libkf5windowsystem5   5.90.0-1
ii  libkf5xmlgui5 5.90.0-1
ii  libkuserfeedbackcore1 1.2.0-2
ii  libkuserfeedbackwidgets1  1.2.0-2
ii  libpackagekitqt5-11.0.2-1
ii  libphonon4qt5-4   4:4.11.1-4
ii  libqt5core5a  5.15.2+dfsg-16
ii  libqt5dbus5   5.15.2+dfsg-16
ii  libqt5gui55.15.2+dfsg-16
ii  libqt5widgets55.15.2+dfsg-16
ii  libqt5xml55.15.2+dfsg-16
ii  libstdc++612-20220319-1
ii  phonon4qt54:4.11.1-4

Versions of packages dolphin recommends:
pn  ffmpegthumbs  
pn  kdegraphics-thumbnailers  
pn  kimageformat-plugins  
ii  kio-extras4:21.12.3-1

Versions of packages dolphin suggests:
pn  dolphin-plugins  

-- no debconf information





pgp4zxnSXLnZf.pgp
Description: Digitale Signatur von OpenPGP

Bug#1008983: dolphin: Restore windows after logout and next login does not work correct.

[Günter Frenz]

Package: dolphin
Version: 4:21.12.3-1
Severity: normal

Dear Maintainer,

on my desktop (KDE-plasma) I'm using 3 windows of dolphin with different often 
needed folders. When I log out and subsequently log in again the 3 windows are 
not restored correct. They all have the same coordinates and the same size, so 
I have to rearrange the windows at each login. The system remembers the number 
and content of the windows correct, but not coordinates and size. In the 
previous version everything worked fine.

Regards

Günter

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

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dolphin depends on:
ii  baloo-kf5 5.90.0-1
ii  kinit 5.90.0-1
ii  kio   5.90.0-3
ii  libc6 2.33-7
ii  libdolphinvcs54:21.12.3-1
ii  libkf5activities5 5.90.0-1
ii  libkf5baloo5  5.90.0-1
ii  libkf5baloowidgets5   4:21.12.3-1
ii  libkf5bookmarks5  5.90.0-1
ii  libkf5codecs5 5.90.0-1
ii  libkf5completion5 5.90.0-1
ii  libkf5configcore5 5.90.0-1
ii  libkf5configgui5  5.90.0-1
ii  libkf5configwidgets5  5.90.1-4
ii  libkf5coreaddons5 5.90.0-1
ii  libkf5crash5  5.90.0-1
ii  libkf5dbusaddons5 5.90.0-1
ii  libkf5filemetadata3   5.90.0-1
ii  libkf5i18n5   5.90.0-1
ii  libkf5iconthemes5 5.90.0-1
ii  libkf5itemviews5  5.90.0-1
ii  libkf5jobwidgets5 5.90.0-1
ii  libkf5kcmutils5   5.90.0-2
ii  libkf5kiocore55.90.0-3
ii  libkf5kiofilewidgets5 5.90.0-3
ii  libkf5kiogui5 5.90.0-3
ii  libkf5kiowidgets5 5.90.0-3
ii  libkf5newstuff5   5.90.0-2
ii  libkf5notifications5  5.90.0-1
ii  libkf5parts5  5.90.0-1
ii  libkf5service-bin 5.90.0-1
ii  libkf5service55.90.0-1
ii  libkf5solid5  5.90.0-1
ii  libkf5textwidgets55.90.0-1
ii  libkf5widgetsaddons5  5.90.0-1
ii  libkf5windowsystem5   5.90.0-1
ii  libkf5xmlgui5 5.90.0-1
ii  libkuserfeedbackcore1 1.2.0-2
ii  libkuserfeedbackwidgets1  1.2.0-2
ii  libpackagekitqt5-11.0.2-1
ii  libphonon4qt5-4   4:4.11.1-4
ii  libqt5core5a  5.15.2+dfsg-16
ii  libqt5dbus5   5.15.2+dfsg-16
ii  libqt5gui55.15.2+dfsg-16
ii  libqt5widgets55.15.2+dfsg-16
ii  libqt5xml55.15.2+dfsg-16
ii  libstdc++612-20220319-1
ii  phonon4qt54:4.11.1-4

Versions of packages dolphin recommends:
pn  ffmpegthumbs  
pn  kdegraphics-thumbnailers  
pn  kimageformat-plugins  
ii  kio-extras4:21.12.3-1

Versions of packages dolphin suggests:
pn  dolphin-plugins  

-- no debconf information

Bug#1008952: grep FTBFS on musl: requires regex library

[Santiago Ruano Rincón]

Control: tags -1 + pending

El 04/04/22 a las 22:05, Helmut Grohne escribió:
> Source: grep
> Version: 3.7-1
> Tags: ftbfs patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> grep fails to build from source on musl-linux-any, because it assumes a
> regex library, but musl doesn't provide it. Indeed, grep has its own
> regex library and the packaging unconditionally disables that during
> build. We should enable it for musl. Please consider applying the
> attached patch.
> 
> Helmut

> --- a/debian/rules
> +++ b/debian/rules
> @@ -26,10 +26,12 @@
>  DEB_CONFIGURE_SCRIPT_ENV += CPPFLAGS="$(CPPFLAGS)"
>  ##
> 
> +include /usr/share/dpkg/architecture.mk
> +
>  DEB_UPSTREAM_URL = http://ftp.gnu.org/gnu/grep/
>  DEB_UPSTREAM_TARBALL_EXTENSION = tar.xz
> 
> -DEB_CONFIGURE_EXTRA_FLAGS += --without-included-regex
> +DEB_CONFIGURE_EXTRA_FLAGS += --with$(if $(filter 
> $(DEB_HOST_ARCH_LIBC),musl),,out)-included-regex
>  DEB_CONFIGURE_SCRIPT_ENV += LIBS="$(LIBS)"
> 
>  # FIXME: CDBS should include a specific var for this

Thanks for you filing the issue and providing the patch. I have applied
a different solution, just for more readability.

Cheers!

 -- S


signature.asc
Description: PGP signature

Bug#1008982: adacontrol: depends on unavailable asis

[Nicolas Boulenguez]

Source: adacontrol
Severity: serious
Tags: upstream ftbfs
Justification: Policy 2.2.1

ASIS will soon be removed from Debian.
Adacontrol depends on ASIS and should also be removed.

Bug#1008981: libaws: depends on unavailable asis

[Nicolas Boulenguez]

Source: libaws
Severity: serious
Tags: upstream ftbfs
Justification: Policy 2.2.1

ASIS will soon be removed from Debian.
AWS depends on ASIS and should also be removed.

Next AWS version will depend on langkit instead,
but langkit is not packaged yet.

Bug#1008980: adabrowse: depends on unavailable asis

[Nicolas Boulenguez]

Package: adabrowse
Severity: serious
Tags: upstream ftbfs
Justification: Policy 2.2.1

ASIS will soon be removed from Debian.
adabrowse depends on ASIS and should also be removed.

Bug#1008979: asis: depends on gnat-util, almost orphaned upstream

[Nicolas Boulenguez]

Source: asis
Severity: serious
Tags: upstream ftbfs
Justification: Policy 2.2.1

gcc-11 has stopped building the libgnat-util library (again).  This
issue alone could be circumvented by Debian efforts (and has been for
more than a decade), but the only consumer left is ASIS.

AdaCore does not release ASIS publicly anymore.
https://www.adalog.fr/en/adacontrol.html#download
gives much more details and describes possible work-arounds.
For example, ASIS in Debian currently builds with GCC-10 from its last
AdaCore public release (2019), but this requires libgnat-util.

For now, ASIS must be removed from testing so that other Ada packages
can migrate to GCC-11.

Bug#1008978: bsdjson segmentation fault

[Эрик Шахов]

Package: bacula 
Version: 9.6.7-3 


Hi. 

Error message: bacula-sd: bsdjson.c:530-0 No Storage resource defined in /. 
Cannot continue. 05-апр 16:42 bacula-sd JobId 0: Error: bsdjson.c:530 No 
Storage resource defined in /. Cannot continue. bacula-sd: bsdjson.c:541-0 No 
Director resource defined in /. Cannot continue. 05-апр 16:42 bacula-sd JobId 
0: Error: bsdjson.c:541 No Director resource defined in /. Cannot continue. 
bacula-sd: bsdjson.c:546-0 No Device resource defined in /. Cannot continue. 
05-апр 16:42 bacula-sd JobId 0: Error: bsdjson.c:546 No Device resource defined 
in /. Cannot continue. 
Segmentation fault 

To reproduce the bug we just need to install bacula and type command 
"/usr/sbin/bsdjson /". This command will abort with "segmentation fault". In 
normal way it must finish without "Segmentation fault". 
System information: Linux debian 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 
(2022-03-07) x86_64 GNU/Linux 
libc-2.31.so 

CWE identifier for this bug: CWE-476 NULL Pointer Dereference 

Code fragment where bug appearance: 

I n some moments program bsdjson call function check_resources(bsdjson.c:521). 
In if(! me->messages ) ( file bsdjson . c : 551 ) and if(! 
me->working_directory) ( file bsdjson . c : 560 ) because of NULL Pointer 
Dereference appearance undefined program behavior. In this bug - «Segmentation 
fault» 

Way to fix this bug: 

Problem can be solved by correcting «if». For example: 

if( me && !me→messages) 

f( me && ! me->working_directory) 
Regards, 

Shahov Erik 

Bug#1008930: RFS: go-junit-report/1.0.0-1 -- Convert go test output to junit xml (program)

[Bastian Germann]

Control: tags -1 moreinfo

On Mon, 4 Apr 2022 10:32:31 -0300 "Gabriel M. Dutra"  
wrote:

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "go-junit-report":

* Package name : go-junit-report
Version : 1.0.0-1
Upstream Author : TODO
* URL : https://github.com/jstemmer/go-junit-report
* License : Expat
* Vcs : https://salsa.debian.org/go-team/packages/go-junit-report
Section : golang

The source builds the following binary packages:

go-junit-report - Convert go test output to junit xml (program)

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


https://mentors.debian.net/package/go-junit-report/

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

dget -x 
https://mentors.debian.net/debian/pool/main/g/go-junit-report/go-junit-report_1.0.0-1.dsc


Changes for the initial release:

go-junit-report (1.0.0-1) UNRELEASED; urgency=medium


Please address unstable or experimental with a new package upload.


.
* Initial release (Closes: TODO)


You have to file an ITP first and fill the TODO.

Please untag moreinfo from this bug when you are done.

Bug#1003936: w3m: Updated German message catalogue

[Tatsuya Kinoshita]

Control: tags -1 + patch pending

On 2022-01-18 at 12:03 +0100, Markus Hiereth wrote:
> with this message, you receive the German version of the latest message 
> catalogue
> [w3m_0.5.3+git20210102-6_de_2.po (text/plain, attachment)]

Merged in the Git repo.

Thanks,
--
Tatsuya Kinoshita


pgp4Q1YDcZfag.pgp
Description: PGP signature

Bug#1008976: Wordpress editor shows empty screen

[Katharina Drexel]

Package: wordpress
Version: 5.9.2+dfsg1-1
Severity: normal

Hello,

when editing a post with the actual wordpress version only a blank screen is 
shown.
For fixing that you have to copy the files

wp-includes/js/dist/blocks.js
wp-includes/js/dist/blocks.min.js

from the actual upstream version (tested under bullseye).

Kind Regards
Katharina
-- 

Bug#1008975: lm-sensors: resume from suspend will start fancontrol even if it's disabled

[Andreas Hasenack]

Package: lm-sensors
Version: 1:3.6.0-7
Severity: normal

Dear Maintainer,

the fix for bug #664141 introduced a system-sleep hook that restart
fancontrol. It does that unconditionally, though, so that even if the
user disabled the service (via systemctl disable fancontrol.service),
it will be started. I think that is undesired behavior, and applied
this patch in the ubuntu package, which I'm submitting for your
consideration:

diff --git a/debian/fancontrol-systemd-sleep b/debian/fancontrol-systemd-sleep
index ffbdd0c5..ad7d99ee 100644
--- a/debian/fancontrol-systemd-sleep
+++ b/debian/fancontrol-systemd-sleep
@@ -2,7 +2,9 @@

 case "$1" in
   post)
-/bin/systemctl restart fancontrol.service
+if /bin/systemctl --quiet is-active fancontrol.service; then
+  /bin/systemctl restart fancontrol.service
+fi
 exit 0
 ;;
 esac


With this patch, the following is the new behavior on resume:

Service is enabled and active --> is restarted
Service is disabled and active --> is restarted
Service is enabled and inactive --> is not restarted
Service is disabled and inactive --> is not restarted

Cheers!

Bug#1008974: nautilus-share: incorrect command line for samba 4.15

[Andreas Hasenack]

Package: nautilus-share
Version: 0.7.3-2
Severity: normal

Dear Maintainer,

nautilus-share uses the "net usershare" command with the "-l"
(lowercase L) parameter. Since samba 4.15.0[1], this has been removed
and now the long version, "--long", must be used instead.

Here is the patch we applied to Ubuntu:

Description: update net usershare command-line for samba 4.15.x
 Samba 4.15.x removed[1] the short "-l" option for net commands, requiring the
 "--long" alternative.
 .
 1. https://www.samba.org/samba/history/samba-4.15.0.html
Author: Andreas Hasenack 
Bug-Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1967245
Forwarded: no, upstream git repo is archived
Last-Update: 2022-04-04

--- a/src/shares.c
+++ b/src/shares.c
@@ -623,7 +623,7 @@
 return FALSE;

 argv[0] = "add";
-argv[1] = "-l";
+argv[1] = "--long";
 argv[2] = info->share_name;
 argv[3] = info->path;
 argv[4] = info->comment;





1. https://www.samba.org/samba/history/samba-4.15.0.html

Bug#1008925: pytorch-vision FTBFS with Python 3.10 due to X-Python3-Version: 3.9

[Diederik de Haas]

On Mon, 04 Apr 2022 12:32:32 +0300 Adrian Bunk  wrote:
> Source: pytorch-vision
> Version: 0.8.2-1
> Severity: serious
> Tags: ftbfs bookworm sid
> 
> https://buildd.debian.org/status/logs.php?pkg=pytorch-vision=0.8.2-1+b3
> 
> https://sources.debian.org/src/pytorch-vision/0.8.2-1/debian/control/#L28

https://github.com/pytorch/vision/pulls?q=is%3Apr+python+3.10+is%3Aclosed 
seems to indicate that an upgrade to upstream's 0.12 is needed to properly 
support python 3.10

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

Bug#1008973: linux-image-amd64: Very slow wireless with MEDIATEK 7961

[Xavier Chantry]

Package: linux-image-amd64
Version: 5.10.84-1
Severity: important
X-Debbugs-Cc: chantry.xav...@gmail.com

Dear Maintainer,

We have a problem with MEDIATEK 7961 wireless on Levono P14s with AMD
Ryzen.

With 5.10 kernel on debian stable the wireless just does not work, so we
installed kernel 5.16 from testing.

With kernel 5.16 the wireless is so slow that it's unusable, each
internet query takes several seconds. A simple ping to google.com varies
from 100ms to 3000ms.

With kernel 5.17 it's slighly better but the ping still goes up to
600ms.

With kernel 5.15 however, it works quite good, Internet is very usable,
ping varies from 3ms to 30ms.
(on the same network, the P14s with Intel wireless does better and is
always under 10ms).

It looks like big changes were made to the mt7921e driver in 5.16
according to Phoronix :
The Mediatek MT7921 WiFi driver has added support for 6GHz WiFi, active
state power management (ASPM), and other improvements.

And it looks like this caused a big regression with MEDIATEK 7961.

Besides the network performance problem on 5.16, suspend/resume is also
broken, while it works perfectly on 5.15.

-- System Information:
Debian Release: 11.2
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages linux-image-amd64 depends on:
ii  linux-image-5.10.0-10-amd64  5.10.84-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Bug#1008750: Workaround: Disable VGA on the motherboard

[Marko Mäkelä]

The problem appears to be that a built-in unaccelerated graphics adapter 
exists on the motherboard.


Adding file /etc/udev/rules.d/83-card0.rules
with the following contents allows GNOME to start on Wayland:

ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x1a03", ATTR{class}=="0x03", 
ATTR{remove}="1"

Some possibly relevant kernel startup messages (from dmesg) are as 
follows:


[0.596600] pci :0a:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=none,locks=none
[0.596600] pci :81:00.0: vgaarb: setting as boot VGA device
[0.596600] pci :81:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.596600] pci :0a:00.0: vgaarb: bridge control possible
[0.596600] pci :81:00.0: vgaarb: bridge control possible
[0.596600] vgaarb: loaded
...
[1.266286] efifb: probing for efifb
[1.266292] pmd_set_huge: Cannot satisfy [mem 0xe000-0xe020] with a h
uge-page mapping due to MTRR override.
[1.266304] efifb: framebuffer at 0xe000, using 8128k, total 8128k
[1.266306] efifb: mode is 1920x1080x32, linelength=7680, pages=1
[1.266307] efifb: scrolling: redraw
[1.266308] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[1.266434] Console: switching to colour frame buffer device 240x67
[1.270104] fb0: EFI VGA frame buffer device
...
[1.820564] checking generic (e000 7f) vs hw (c400 200)
[1.820589] ast :0a:00.0: enabling device ( -> 0003)
[1.820726] ast :0a:00.0: [drm] Using P2A bridge for configuration
[1.820729] ast :0a:00.0: [drm] AST 2400 detected
[1.820740] ast :0a:00.0: [drm] Analog VGA only
[1.820747] ast :0a:00.0: [drm] dram MCLK=408 Mhz type=6 bus_width=16
[1.821073] [drm] Initialized ast 0.1.0 20120228 for :0a:00.0 on minor 0
[1.825665] checking generic (e000 7f) vs hw (0 0)
[1.825787] ast :0a:00.0: [drm] fb1: astdrmfb frame buffer device
[1.900752] [drm] amdgpu kernel modesetting enabled.
[1.900933] amdgpu: CRAT table not found
[1.900936] amdgpu: Virtual CRAT table created for CPU
[1.900966] amdgpu: Topology: Add CPU node
[1.901234] checking generic (e000 7f) vs hw (e000 1000)
[1.901242] checking generic (e000 7f) vs hw (e000 1000)
[1.901245] fb0: switching to amdgpu from EFI VGA
[1.901428] Console: switching to colour dummy device 80x25
[1.901491] amdgpu :81:00.0: vgaarb: deactivate vga console

With best regards,

Marko

Bug#1008273: Should python-nemu be removed?

[Martina Ferrari]

severity 1008273 normal
reassign 1008273 ftp.debian.org
retitle 1008273 RM:  -- RoM; Abandoned
thx


Your package came up as a candidate for removal from Debian:


Yes, I should have done this years ago. I am upstream for it too, and I 
have not touched that code in almost 10 years. Please, remove it from 
Debian.


Thanks.

--
Martina Ferrari (Tina)

Bug#1008955: Bad subject, sorry

[Lupe Christoph]

> My recommendation is to use systemd-timesyncd if you want to use
> systemd-time-wait-sync (or disable the use systemd-time-wait-sync.service)

You seem to not have read more than the subject, where I made a
copy-and-paste-o. The entire *text* of the bug report is about
systemd-networkd-wait-online.

I can't correct the bad subject. If you can, please replace
systemd-time-wait-sync with systemd-networkd-wait-online.

Then, please read the body.
Thanks.

Bug#1008972: firmware-iwlwifi: iwlwifi reports errors while shutdown computer

[dasebastian]

Package: firmware-iwlwifi
Version: 20210315-3
Severity: normal
X-Debbugs-Cc: voiwap...@gmx.at

Dear Maintainer,

after updating my system to bullseye, I mostly always get a lot of errors when 
shuting down the computer (if I was logged in into a wireless network). Things 
like:

[ 536.451518] iwlwifi :03:00.0: Error sending REPLY_SCAN_ABORT_CMD: time 
out after 2000ms.
[ 536.451668] iwlwifi :03:00.0: Current CMD queue read_ptr 28 write_ptr 29
[ 536.699549] iwlwifi :03:00.0: Loaded firmware version: 18.168.6.1 
6000g2a-6.ucode

# lots of lines then like:
[ 536.699834] iwlwifi :03:00.0: 0x | interruptlink1

# with interruptlink2, time gp1, time gp2, wait_event...
followed by:
Start IWL Event Log Dump: nothing in log
Command REPLY_RXON failed: FW Error
Error clearing ASSOC_MSK on BSS (-5)

This goes over two screens and takes about 5-10 seconds, then computer shuts 
down.

I did not try any solutions, because it only affects the shutdown behavior.
 

-- 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-13-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.140

-- no debconf information

Bug#1008971: xfburn: on page https://packages.debian.org/stretch/xfburn, link "Homepage" is dead

[hcdoum...@free.fr]

Package: xfburn
Version: 0.6.2-1
Severity: minor

Dear Maintainer,

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


* What led up to the situation?
* 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: 11.3
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-13-amd64 (SMP w/2 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfburn depends on:
ii libburn4 1.5.2-1
ii libc6 2.31-13+deb11u3
ii libexo-2-0 4.16.0-1
ii libgdk-pixbuf2.0-0 2.40.2-2
ii libglib2.0-0 2.66.8-1
ii libgstreamer-plugins-base1.0-0 1.18.4-2
ii libgstreamer1.0-0 1.18.4-2.1
ii libgtk-3-0 3.24.24-4+deb11u2
ii libgudev-1.0-0 234-1
ii libisofs6 1.5.2-1
ii libxfce4ui-2-0 4.16.0-1
ii libxfce4util7 4.16.0-1

xfburn recommends no packages.

xfburn suggests no packages.

Bug#724959: mount of rootfs fails

[Mark Hindley]

Control: tags -1 unreproducible

David,

I know this was a very long time ago, for which apologies. But #677420/#724959
was mentioned in the discussion of #1008910 so I had a look.

On Mon, Sep 30, 2013 at 10:48:24AM +1000, David Burgess wrote:
> Package: initscripts
> Version: 2.88dsf-43
> 
> /lib/init/mount-functions.sh does not handle quoted LABEL= or UUID= names in
> fstab. mount -a (and findfs) works with quoted names in fstab.

I am unable to reproduce this behaviour and quoted names are parsed correctly.

I am wondering if it was a bug in the particular shell you (were?) using. I
notice the submitter of #677420 was using bash as /bin/sh.

Thanks.

Mark

Bug#1008970: ITP: pyimagetool -- Image Tool for multidimensional analysis

[Neil Williams]

Package: wnpp
Severity: wishlist
Owner: Neil Williams 
X-Debbugs-Cc: debian-de...@lists.debian.org, codeh...@debian.org

* Package name: pyimagetool
  Version : 1.0
  Upstream Author : Kyle Gordon 
* URL : https://github.com/kgord831/PyImageTool
* License : GPL3
  Programming Lang: Python
  Description : Image Tool for multidimensional analysis

 Python Image Tool can be used to visualise analysis of data in
 microscopy (STM, SSM, optics), ARPES, XRD, or other multidimensional
 datasets on regularly gridded coordinates.
 .
 This package installs the module for Python 3 and an
 example helper script to create a writeable data cache.

This package will be maintained within the Debian Science Team.

The module provides the support to plot the data using Qt
but each plot requires a custom script, based on the packaged helper,
to load the data and supporting parameters. No desktop file is
provided.

Bug#1008811: Won't start without python3-dbus (misses dependency)

[Ritesh Raj Sarraf]

Control: tag -1 pending

On Sat, 2022-04-02 at 00:55 +0200, Daniel Leidert wrote:
> Package: snapper-gui
> Version: 0git.960a94834f-3.1
> Severity: serious
> 
> snapper-gui doesn't start without python3-dbus:

Thank you for reporting this bug. It has been committed in the
packaging repository and will be part of the next upload.


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#1008969: jhove in non-free

[Mathieu Malaterre]

Source: jhove
Version: 1.20.1-5

It is not clear why jove is in non-free. Would it be possible to
migrate back to main and refer to `icc-profiles-free`. Or am I missing
something?

Thanks

Bug#1008968: jhove v1.25.38 is out

[Mathieu Malaterre]

Source: jhove

It would be super nice to have v1.25.38 in Debian.

Thanks for maintaining jhove.

-M

Bug#1008965: lazygal: Crashes with illegal chars in IPTC keywords

[Alexandre Rossi]

Hi,

> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 2: 
> invalid
> start byte
[...]
>   File "/usr/lib/python3/dist-packages/lazygal/metadata.py", line 406, in
> get_keywords
> values = self._metadata.get_tag_multiple(key)
> SystemError:  returned a result with an error set

Can you provide a minimal failing image so I can reproduce?

Thanks,

Alex

Bug#1008966: libopenmpi-dev: IO (and UCX) problems causing mpi4py test failures

[Drew Parsons]

Package: libopenmpi-dev
Version: 4.1.3-1
Severity: serious
Justification: debci failure (mpi4py)
Control: affects -1 src:mpi4py

mpi4py is failing IO tests with the new openmpi 4.1.3.

i386 has actually been failing test_io.TestIOSelf for some time, but
now the problem has expanded to amd64 and other arches.

The problem (exposed in mpi4py tests) has been reported at
https://github.com/mpi4py/mpi4py/issues/105
We checked that the same tests are passing with mpich, which I why I'm
filing this bug against openmpi rather than mpi4py

The mpi4py maintainer can reproduce the error (after building on
Fedora without ucx, which was causing other problems) using
OMPI_MCA_io=romio321.  He observes that the default OMPIO component
failed to load at runtime, so ROMIO is being used instead.

He provides a backtrace:

$ OMPI_MCA_io=romio321 valgrind -q python test/main.py -q -i test_io -k 
TestIOSelf.testIReadIWriteAll -v
[0@kw61149] Python 3.10.4 (/usr/bin/python)
[0@kw61149] numpy 1.21.5 (/usr/lib64/python3.10/site-packages/numpy)
[0@kw61149] MPI 3.1 (Open MPI 4.1.3)
[0@kw61149] mpi4py 4.0.0.dev0 
(/home/dalcinl/Devel/mpi4py/build/lib.linux-x86_64-3.10/mpi4py)
testIReadIWriteAll (test_io.TestIOSelf) ... ==3623039== Jump to the invalid 
address stated on the next line
==3623039==at 0x0: ???
==3623039==by 0x1DA8E8B3: mca_io_romio_dist_MPI_File_iwrite_all 
(iwrite_all.c:58)
==3623039==by 0x1DA8BAF5: mca_io_romio321_file_iwrite_all 
(io_romio321_file_write.c:204)
==3623039==by 0x1600D5D5: PMPI_File_iwrite_all (pfile_iwrite_all.c:83)
==3623039==by 0x15DBACA9: PyMPI_File_iwrite_all_c (largecnt.h:2377)
==3623039==by 0x15ECAA01: __pyx_pf_6mpi4py_3MPI_4File_62Iwrite_all 
(MPI.c:171765)
==3623039==by 0x15ECA843: __pyx_pw_6mpi4py_3MPI_4File_63Iwrite_all 
(MPI.c:171700)
==3623039==by 0x498A50F: method_vectorcall_VARARGS_KEYWORDS 
(descrobject.c:344)
==3623039==by 0x497CBA2: UnknownInlinedFun (abstract.h:114)
==3623039==by 0x497CBA2: UnknownInlinedFun (abstract.h:123)
==3623039==by 0x497CBA2: UnknownInlinedFun (ceval.c:5867)
==3623039==by 0x497CBA2: _PyEval_EvalFrameDefault (ceval.c:4198)
==3623039==by 0x497B5FF: UnknownInlinedFun (pycore_ceval.h:46)
==3623039==by 0x497B5FF: _PyEval_Vector (ceval.c:5065)
==3623039==by 0x49918F7: UnknownInlinedFun (call.c:342)
==3623039==by 0x49918F7: UnknownInlinedFun (abstract.h:114)
==3623039==by 0x49918F7: method_vectorcall (classobject.c:53)
==3623039==by 0x497C7C6: UnknownInlinedFun (abstract.h:114)
==3623039==by 0x497C7C6: UnknownInlinedFun (abstract.h:123)
==3623039==by 0x497C7C6: UnknownInlinedFun (ceval.c:5867)
==3623039==by 0x497C7C6: _PyEval_EvalFrameDefault (ceval.c:4213)
==3623039==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==3623039== 
[kw61149:3623039] *** Process received signal ***
[kw61149:3623039] Signal: Segmentation fault (11)
[kw61149:3623039] Signal code: Invalid permissions (2)
[kw61149:3623039] Failing at address: (nil)
[kw61149:3623039] [ 0] /lib64/libc.so.6(+0x42750)[0x4bff750]
[kw61149:3623039] *** End of error message ***
Segmentation fault (core dumped)





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

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

Versions of packages libopenmpi-dev depends on:
ii  gfortran [gfortran-mod-15] 4:11.2.0-2
ii  gfortran-11 [gfortran-mod-15]  11.2.0-19
ii  gfortran-9 [gfortran-mod-15]   9.4.0-5
ii  libevent-dev   2.1.12-stable-1
ii  libhwloc-dev   2.7.1-1
ii  libibverbs-dev 39.0-1+b1
ii  libjs-jquery   3.6.0+dfsg+~3.5.13-1
ii  libjs-jquery-ui1.13.1+dfsg-1
ii  libopenmpi34.1.3-1
ii  libpmix-dev4.1.2-2
ii  openmpi-bin4.1.3-1
ii  openmpi-common 4.1.3-1
ii  zlib1g-dev 1:1.2.11.dfsg-4

Versions of packages libopenmpi-dev recommends:
ii  libcoarrays-openmpi-dev  2.9.3-1

Versions of packages libopenmpi-dev suggests:
pn  openmpi-doc  

-- no debconf information

Bug#993716: Lowering severity

[Thomas Goirand]

Hi,

I have lowered the severity of this bug to allow the package to migrate 
back to testing.


The reasoning is that, yes, there's an important issue to fix, as 
upgrade is broken. However, having no bridgeutils in testing is more 
harmful than this bug.


Cheers,

Thomas Goirand (zigo)

Bug#1008222: bind unicast_src x.y.z.w failed 99 - Cannot assign requested address

[Arturo Borrero Gonzalez]

On 3/25/22 23:57, Vincent Bernat wrote:

  ❦ 25 March 2022 11:48 +01, Arturo Borrero Gonzalez:


I honestly don't know how this relates to the execution error itself.
Do you think the address assignment fails because some misconfigured
netmask?


Usually, on Linux, VIP are using /32 to avoid issues with source address
selection. Notably, when contacting a peer, the VIP could be selected
when using a /29, while this is not possible when using a /32.


I just tested your theory, used this in the config:

  virtual_ipaddress {
185.15.57.9/32 dev eno2.2107
208.80.153.190/32 dev eno2.2120
  }

Downgraded to the Bullseye version, but keepalived fails with the same 
error:


aborrero@cloudgw2001-dev:~ $ sudo /usr/sbin/keepalived -lD --dont-fork
Tue Apr  5 08:14:32 2022: Starting Keepalived v2.1.5 (07/13,2020)
Tue Apr  5 08:14:32 2022: WARNING - keepalived was build for newer Linux 
5.10.70, running on Linux 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 
(2022-03-07)
Tue Apr  5 08:14:32 2022: Command line: '/usr/sbin/keepalived' '-lD' 
'--dont-fork'

Tue Apr  5 08:14:32 2022: Opening file '/etc/keepalived/keepalived.conf'.
Tue Apr  5 08:14:32 2022: NOTICE: setting config option 
max_auto_priority should result in better keepalived performance

Tue Apr  5 08:14:32 2022: Starting VRRP child process, pid=1571242
Tue Apr  5 08:14:32 2022: Registering Kernel netlink reflector
Tue Apr  5 08:14:32 2022: Registering Kernel netlink command channel
Tue Apr  5 08:14:32 2022: Opening file '/etc/keepalived/keepalived.conf'.
Tue Apr  5 08:14:32 2022: (/etc/keepalived/keepalived.conf: Line 25) 
Warning - cannot track route 185.15.57.0/29 with no interface specified, 
not tracking
Tue Apr  5 08:14:32 2022: (/etc/keepalived/keepalived.conf: Line 26) 
Warning - cannot track route 172.16.128.0/24 with no interface 
specified, not tracking
Tue Apr  5 08:14:32 2022: Assigned address 208.80.153.188 for interface 
eno2.2120
Tue Apr  5 08:14:32 2022: Assigned address fe80::32e1:71ff:fe60:e97d for 
interface eno2.2120

Tue Apr  5 08:14:32 2022: Registering gratuitous ARP shared channel
Tue Apr  5 08:14:32 2022: (VRRP1) removing Virtual Routes
Tue Apr  5 08:14:32 2022: (VRRP1) removing VIPs.
Tue Apr  5 08:14:32 2022: bind unicast_src 208.80.153.188 failed 99 - 
Cannot assign requested address
Tue Apr  5 08:14:32 2022: (VRRP1): entering FAULT state (src address not 
configured)

Tue Apr  5 08:14:32 2022: (VRRP1) Entering FAULT STATE
Tue Apr  5 08:14:32 2022: (VRRP1) removing Virtual Routes
Tue Apr  5 08:14:32 2022: VRRP sockpool: [ifindex(  8), family(IPv4), 
proto(112), fd(-1,-1), unicast, address(208.80.153.188)]

^CTue Apr  5 08:14:36 2022: Stopping
Tue Apr  5 08:14:37 2022: Stopped - used 0.001718 user time, 0.00 
system time
Tue Apr  5 08:14:37 2022: CPU usage (self/children) user: 
0.006457/0.003166 system: 0.006457/0.00

Tue Apr  5 08:14:37 2022: Stopped Keepalived v2.1.5 (07/13,2020)

Bug#1008964: Acknowledgement (python3-pywatchman: capabilityCheck fails with Python 3.10 (PY_SSIZE_T_CLEAN macro must be defined for '#' formats))

[Frederic Peters]

In case it helps, here's the patch ready to be copied to
debian/patches/ (I tested it locally and it works).


Frederic
Description: fix Python deprecation warnings about PY_SSIZE_T_CLEAN
Origin: upstream, https://github.com/facebook/watchman/commit/6813a948fee72a15acf4120262d37c9c8dc3f16b

--- a/python/pywatchman/bser.c
+++ b/python/pywatchman/bser.c
@@ -28,6 +28,7 @@ OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 */
 
+#define PY_SSIZE_T_CLEAN
 #include 
 #include 
 #ifdef _MSC_VER
@@ -1026,7 +1027,7 @@ static int pdu_info_helper(
 int64_t* total_len_out) {
   const char* start = NULL;
   const char* data = NULL;
-  int datalen = 0;
+  Py_ssize_t datalen = 0;
   const char* end;
   int64_t expected_len;
   off_t position;
@@ -1075,7 +1076,7 @@ static PyObject* bser_pdu_len(PyObject* self, PyObject* args) {
 
 static PyObject* bser_loads(PyObject* self, PyObject* args, PyObject* kw) {
   const char* data = NULL;
-  int datalen = 0;
+  Py_ssize_t datalen = 0;
   const char* start;
   const char* end;
   int64_t expected_len;

Bug#1008965: lazygal: Crashes with illegal chars in IPTC keywords

[Björn]

Package: lazygal
Version: 0.10.5-1
Severity: normal
X-Debbugs-Cc: coronal...@yandex.com

Dear Maintainer,

   * What led up to the situation?

Starting lazygal with pictures having illegal (pre-UTF-8) characters in IPTC
keywords. The keyword "Bj�rn" leads to a crash.

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

Removing the keyword or changing it to UTF-8 "Björn" worked. But: I would like
to create a gallery with all pictures, even old ones, without changing all the
pictures.

   * What was the outcome of this action?

UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf6 in position 2: invalid
start byte

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/bin/lazygal", line 33, in 
sys.exit(load_entry_point('lazygal==0.10.5', 'console_scripts',
'lazygal')())
  File "/usr/lib/python3/dist-packages/lazygal/cmdline.py", line 292, in main
album.generate(progress=progress)
  File "/usr/lib/python3/dist-packages/lazygal/generators.py", line 943, in
generate
destgal.make()
  File "/usr/lib/python3/dist-packages/lazygal/generators.py", line 667, in
make
super().make(force)
  File "/usr/lib/python3/dist-packages/lazygal/make.py", line 120, in make
self.call_populate_deps()
  File "/usr/lib/python3/dist-packages/lazygal/make.py", line 43, in
call_populate_deps
self.populate_deps()
  File "/usr/lib/python3/dist-packages/lazygal/generators.py", line 341, in
populate_deps
media.load_metadata(self.pindex)
  File "/usr/lib/python3/dist-packages/lazygal/sourcetree.py", line 152, in
load_metadata
self.load_metadata_from_mediafile()
  File "/usr/lib/python3/dist-packages/lazygal/sourcetree.py", line 140, in
load_metadata_from_mediafile
self._parse_metadata(mdloader)
  File "/usr/lib/python3/dist-packages/lazygal/sourcetree.py", line 233, in
_parse_metadata
'keywords': list(mdloader.get_keywords()),
  File "/usr/lib/python3/dist-packages/lazygal/metadata.py", line 406, in
get_keywords
values = self._metadata.get_tag_multiple(key)
SystemError:  returned a result with an error set

   * What outcome did you expect instead?

Normal creating of gallery. With keyword "Bj�rn" or without (doesn't matter)



Thank you!



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

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

Versions of packages lazygal depends on:
ii  gir1.2-gexiv2-0.10  0.14.0-1
ii  libjs-jquery3.6.0+dfsg+~3.5.13-1
ii  python3 3.9.8-1
ii  python3-genshi  0.7.6-1
ii  python3-gi  3.42.0-3
ii  python3-pil 9.0.1-1

lazygal recommends no packages.

Versions of packages lazygal suggests:
ii  ffmpeg  7:4.4.1-3+b2

-- no debconf information

Bug#1008156: telegram-desktop: Crash when switch account

[Stefano Callegari]

Il Mon, Apr 04, 2022 at 10:03:03PM +0300, Nicholas Guriev scrisse:
> Control: tags -1 - upstream
> 
> On Пн, 2022-03-28 at 13:20 +0300, Nicholas Guriev wrote:
> > This will be fixed somehow in the upcoming upstream release, 3.6.2.
> 
> I was wrong and did incorrect test. In actual fact, the crash happens
> due to memory allocator from glibc that is in use by default.
> 
> Can you please check my workaround? Run the next commands in terminal:
> 
>sudo apt-get install libjemalloc2
>LD_PRELOAD=libjemalloc.so.2 telegram-desktop
> 

~  $ dpkg -l telegram-desktop
[...]
ii  telegram-desktop 3.6.0+ds-1 amd64 fast and secure messaging application

No crash...

~  $ dpkg -l telegram-desktop
[...]
ii  telegram-desktop 3.6.1+ds-2 amd64 fast and secure messaging application

Crash...

~ <-bash> # aptitude install libjemalloc2
libjemalloc2 è già installato e si trova alla versione richiesta (5.2.1-4)
[...]

Already installed.

I try...

~  $ LD_PRELOAD=libjemalloc.so.2 telegram-desktop

(telegram-desktop:33019): Telegram-WARNING **: 09:30:27.427: Application
has been built with foreign rlottie, animated emojis won't be colored to
the selected pack.

(telegram-desktop:33019): Telegram-WARNING **: 09:30:27.427: Application
was built without embedded fonts, this may lead to font issues. On
Debian-based systems, make sure you have the fonts-open-sans package
installed
error: : cannot open
error: : cannot open
error: : cannot open
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
qt.svg: Error while inflating gzip file: SVG format check failed
[...]

No crash!!!

But it has required a lot of time to connect to the account on open, then
it has switched in real time.

Ciao
-- 
Stefano Callegari
GnuPG Public Key Server: pgp.mit.edu

Bug#1008964: python3-pywatchman: capabilityCheck fails with Python 3.10 (PY_SSIZE_T_CLEAN macro must be defined for '#' formats)

[Frederic Peters]

Package: python3-pywatchman
Version: 4.9.0-6+b2
Severity: important

Hi,

With Python 3.10 now the default Python version pywatchman no longer works:

Python 3.10.4 (main, Apr  2 2022, 09:04:19) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pywatchman
>>> client = pywatchman.client(timeout=0.1)
>>> client.capabilityCheck()
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pywatchman/__init__.py", line 1071, in 
capabilityCheck
res = self.query('version', {
  File "/usr/lib/python3/dist-packages/pywatchman/__init__.py", line 1048, in 
query
self._connect()
  File "/usr/lib/python3/dist-packages/pywatchman/__init__.py", line 917, in 
_connect
self.sockpath = self._resolvesockname()
  File "/usr/lib/python3/dist-packages/pywatchman/__init__.py", line 904, in 
_resolvesockname
result = bser.loads(stdout)
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats

While it's still ok with 3.9:

Python 3.9.12 (main, Mar 24 2022, 13:02:21)
[GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pywatchman
>>> client = pywatchman.client(timeout=0.1)
>>> client.capabilityCheck()
{'capabilities': {}, 'version': '4.9.0'}



This had been reported upstream as 
https://github.com/facebook/watchman/issues/970
and there is a fix in
  
https://github.com/facebook/watchman/commit/6813a948fee72a15acf4120262d37c9c8dc3f16b

(but no new release)



Thanks,


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

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

Versions of packages python3-pywatchman depends on:
ii  libc6   2.33-7
ii  python3 3.10.4-1
ii  python3.10  3.10.4-3
ii  watchman4.9.0-6+b2

python3-pywatchman recommends no packages.

python3-pywatchman suggests no packages.

-- no debconf information

Bug#1008956: tex-common: Something in package "tex-common" causes dpkg to exit with exit code -1

[Hilmar Preuße]

Am 05.04.2022 um 00:13 teilte Ashleigh Moore mit:

Hi Ashleigh,


I noticed the error that dpkg reported: exit code -1, and the package
"tex-common". I saw that it made a error report with the name
"fmtutil.", but I thought that perhaps it was a fluke
brought on by the mammoth number of packages I had it installing.



If you have still one of these files, please provide it. Thanks!

Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#977780: Problem is not resolved up to this time yet, unfortunately...

[roman.ber...@aspose.com]

Надіслано з мого мобільного пристрою Huawei

Bug#999443: pulseaudio: Muted microphone is unmuted when resuming from sleep

[Igor Kovalenko]

On Mon, 04 Apr 2022 09:04:33 -0500 Ben Goodwin  wrote:
> Package: pulseaudio
> Version: 15.0+dfsg1-4
> Followup-For: Bug #999443
> X-Debbugs-Cc: vbgoodw...@gmail.com
>
> It seems that I was mistaken and this bug is not resolved in 15.0+dfsg1-4.
> The microphone seems to keep its muted status after a reboot but not
> afer waking from being suspended to memory.
>
>

You are running pipewire audio, not pulseaudio, see 'pactl info'

>> Server Name: PulseAudio (on PipeWire 0.3.48)

Do you have the same issue with pulseaudio?

Bug#1008962: O: crossguid -- C++ UUID library

[Bálint Réczey]

Package: wnpp
Severity: normal

Orphaning the package.

Thanks,
Balint