Bug#1054249: (no subject)
Can this solution be brought too bookworm, either through stable-updates (preferably) or otherwise backports? The current package is not useable.
Bug#1057074: This is gnutls-cli on my wsl2 box
laenenj@L241362:/mnt/c/Windows/System32$ time gnutls-cli elpa.gnu.org Processed 140 CA certificate(s). Resolving 'elpa.gnu.org:443'... Connecting to '209.51.188.89:443'... - Certificate type: X.509 - Got a certificate list of 3 certificates. - Certificate[0] info: - subject `CN=elpa.gnu.org', issuer `CN=R3,O=Let's Encrypt,C=US', serial 0x039d688ee4d536c2c5d180acd0b77dd534de, RSA key 2048 bits, signed using RSA-SHA256, activated `2023-11-21 11:08:15 UTC', expires `2024-02-19 11:08:14 UTC', pin-sha256="QcwJ9TVQmsXtBHYcKDWyfyNR3X5gWYDtlVNItux6Rhg=" Public Key ID: sha1:445b8bb7b09ad78854d5391cde68b9897a5a052c sha256:41cc09f535509ac5ed04761c2835b27f2351dd7e605980ed955348b6ec7a4618 Public Key PIN: pin-sha256:QcwJ9TVQmsXtBHYcKDWyfyNR3X5gWYDtlVNItux6Rhg= - Certificate[1] info: - subject `CN=R3,O=Let's Encrypt,C=US', issuer `CN=ISRG Root X1,O=Internet Security Research Group,C=US', serial 0x00912b084acf0c18a753f6d62e25a75f5a, RSA key 2048 bits, signed using RSA-SHA256, activated `2020-09-04 00:00:00 UTC', expires `2025-09-15 16:00:00 UTC', pin-sha256="jQJTbIh0grw0/1TkHSumWb+Fs0Ggogr621gT3PvPKG0=" - Certificate[2] info: - subject `CN=ISRG Root X1,O=Internet Security Research Group,C=US', issuer `CN=DST Root CA X3,O=Digital Signature Trust Co.', serial 0x4001772137d4e942b8ee76aa3c640ab7, RSA key 4096 bits, signed using RSA-SHA256, activated `2021-01-20 19:14:03 UTC', expires `2024-09-30 18:14:03 UTC', pin-sha256="C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=" - Status: The certificate is trusted. - Description: (TLS1.3-X.509)-(ECDHE-SECP256R1)-(RSA-PSS-RSAE-SHA256)-(AES-256-GCM) - Session ID: 8D:A7:2C:73:27:87:2D:12:1F:E3:C8:14:41:3F:12:CD:9B:3B:66:48:E4:C9:03:C4:09:D7:19:33:4B:17:AE:E4 - Options: - Handshake was completed - Simple Client Mode: - Peer has closed the GnuTLS connection real0m20.525s user0m0.041s sys 0m0.000s
Bug#1057074: I start to doubt if it's emacs, gnutls-cli is very slow on my debian box
gargle@msi:~$ time gnutls-cli elpa.gnu.org Processed 140 CA certificate(s). Resolving 'elpa.gnu.org:443'... Connecting to '2001:470:142::89:443'... Connecting to '209.51.188.89:443'... - Certificate type: X.509 - Got a certificate list of 3 certificates. - Certificate[0] info: - subject `CN=elpa.gnu.org', issuer `CN=R3,O=Let's Encrypt,C=US', serial 0x039d688ee4d536c2c5d180acd0b77dd534de, RSA key 2048 bits, signed using RSA-SHA256, activated `2023-11-21 11:08:15 UTC', expires `2024-02-19 11:08:14 UTC', pin-sha256="QcwJ9TVQmsXtBHYcKDWyfyNR3X5gWYDtlVNItux6Rhg=" Public Key ID: sha1:445b8bb7b09ad78854d5391cde68b9897a5a052c sha256:41cc09f535509ac5ed04761c2835b27f2351dd7e605980ed955348b6ec7a4618 Public Key PIN: pin-sha256:QcwJ9TVQmsXtBHYcKDWyfyNR3X5gWYDtlVNItux6Rhg= - Certificate[1] info: - subject `CN=R3,O=Let's Encrypt,C=US', issuer `CN=ISRG Root X1,O=Internet Security Research Group,C=US', serial 0x00912b084acf0c18a753f6d62e25a75f5a, RSA key 2048 bits, signed using RSA-SHA256, activated `2020-09-04 00:00:00 UTC', expires `2025-09-15 16:00:00 UTC', pin-sha256="jQJTbIh0grw0/1TkHSumWb+Fs0Ggogr621gT3PvPKG0=" - Certificate[2] info: - subject `CN=ISRG Root X1,O=Internet Security Research Group,C=US', issuer `CN=DST Root CA X3,O=Digital Signature Trust Co.', serial 0x4001772137d4e942b8ee76aa3c640ab7, RSA key 4096 bits, signed using RSA-SHA256, activated `2021-01-20 19:14:03 UTC', expires `2024-09-30 18:14:03 UTC', pin-sha256="C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=" - Status: The certificate is trusted. - Description: (TLS1.3-X.509)-(ECDHE-SECP256R1)-(RSA-PSS-RSAE-SHA256)-(AES-256-GCM) - Session ID: 1B:FA:A7:4C:81:3D:6B:3E:9C:2D:65:EB:5D:52:44:4B:E8:2E:58:C9:4C:67:DE:69:AB:4F:F7:2C:10:5C:03:C6 - Options: - Handshake was completed - Simple Client Mode: - Peer has closed the GnuTLS connection real2m34.806s user0m0.014s sys 0m0.009s on my wsl2 gnutls-cli doesn't go for ipv6. It immediately connects to '209.51.188.89:443'...
Bug#1057074: emacs: A package-refresh-contents or M-x mastodon 'hangs' my emacs
Package: emacs Version: 1:29.1+1-5 Severity: important X-Debbugs-Cc: johan.laenen+debianb...@gmail.com Dear Maintainer, I'm on trixie/sid and I noticed last week that whenever I'd do a package-refresh-contents or whenever I'd try to launch mastodon.el (M-x mastodon) my emacs would hang. The command package-refresh-contents only showed 'Contacting host: elpa.gnu.org:443' and didn't do much more. I had to ctlr-g to break out or wait a couple of minutes before emacs would say that the package refresh was done. The package mastodon.el is a different beast. After a wait I'd get 'Wrong type argument: stringp, nil'. Switching to ipv4 only made the problem disappear: root@msi:/home/gargle# /sbin/sysctl -w net.ipv6.conf.all.disable_ipv6=1net.ipv6.conf.all.disable_ipv6 = 1 root@msi:/home/gargle# /sbin/sysctl -w net.ipv6.conf.default.disable_ipv6=1net.ipv6.conf.default.disable_ipv6 = 1 I moved these two lines above in my /etc/sysctl.conf and double checked my /etc/network/interfaces. I had nothing extra about ipv6 in my configuration. This is what I had and what I still have: root@msi:/home/gargle/whoami# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto loiface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp I'm baffled because I never experienced this behaviour before. My company's laptop runs wsl2 with debian on windows 10 and doesn't show this problem. My setup at home used to work in september and october. On october the 22nd I posted a message on mastodon at floss.social from within emacs by means of mastodon.el. I don't actually know the exact date on which I started to get errors. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs depends on: ii emacs-gtk 1:29.1+1-5 emacs recommends no packages. emacs suggests no packages. -- no debconf information
Bug#1039601: /usr/share/openvswitch/scripts/ifupdown.sh: /usr/share/openvswitch/scripts/ifupdown.sh disregards current status for daemon on sysvinit systems
Package: openvswitch-switch Version: 3.1.0-2 Severity: important File: /usr/share/openvswitch/scripts/ifupdown.sh Tags: patch X-Debbugs-Cc: skin_tiic...@hotmail.com Dear Maintainer, Previously in bullseye this script checked if the service was already running and if not, starting it on sysvinit systems. This is no longer the case which can cause a deadlock situation when it tries to bring interfaces up. Bringing back the old logic fixes the problem as it wont try to start it if the service is already running. -- System Information: Debian Release: 12.0 Architecture: amd64 (x86_64) Versions of packages openvswitch-switch depends on: ii init-system-helpers 1.65.2 ii kmod 30+20221128-1 ii libbpf1 1:1.1.0-1 ii libc62.36-9 ii libcap-ng0 0.8.3-1+b3 ii libnuma1 2.0.16-1 ii libssl3 3.0.8-1 ii libunbound8 1.17.1-2 ii libxdp1 1.3.1-1 ii netbase 6.4 ii openvswitch-common 3.1.0-2 ii procps 2:4.0.3-1 ii python3 3.11.2-1+b1 ii python3-netifaces0.11.0-2+b1 ii python3-openvswitch 3.1.0-2 ii uuid-runtime 2.38.1-5+b1 openvswitch-switch recommends no packages. openvswitch-switch suggests no packages. -- no debconf information 38c38 < if service openvswitch-switch status > /dev/null 2>&1; then --- > if ! service openvswitch-switch status > /dev/null 2>&1; then
Bug#1033625: closed by Brian Potkin (Re: Bug#1033625:)
So this is a bug in cups-browsed? Am Do., 30. März 2023 um 19:23 Uhr schrieb Brian Potkin < claremont...@gmail.com>: > On Thu 30 Mar 2023 at 15:54:09 +0200, Johan Kröckel wrote: > > > Hi Brian, > > > > thanks for your help. But isn't it still a bug that cups is creating a > > printer(-queue) that not only does not work, but also when using it opens > > connections to the printer for hours? I think about the situation, that > you > > have many bookworm clients in the network, this could amount to a denial > of > > service. > > > > I deleted the not working Kyocera_ECOSYS_M5526cdw but cups keeps > recreating > > it when I connect to the corresponding network. > > The auto-creation of the queue (the one shown by 'lpstat -t' and that keeps > coming back after deletion) is done by cups-browsed, not by CUPS. Let's try > this: > > Purge cups-browsed with > > apt purge cups-browsed > > Then do > > rm rm /var/cache/cups/* > > (the files will be regenerated) and restart cups. > > systemctl restart cups > > 'lstsat -l -e' should show a printer name. Can it be used to print? > 'lpstat -t' > should not have implicitclass and should show the manually set up printer, > > Cheers, > > Brian. >
Bug#1033625: closed by Brian Potkin (Re: Bug#1033625:)
Hi Brian, thanks for your help. But isn't it still a bug that cups is creating a printer(-queue) that not only does not work, but also when using it opens connections to the printer for hours? I think about the situation, that you have many bookworm clients in the network, this could amount to a denial of service. I deleted the not working Kyocera_ECOSYS_M5526cdw but cups keeps recreating it when I connect to the corresponding network. Johan Am Do., 30. März 2023 um 14:12 Uhr schrieb Debian Bug Tracking System < ow...@bugs.debian.org>: > This is an automatic notification regarding your Bug report > which was filed against the cups package: > > #1033625: cups constantly without timeout connects to network printer, > does not print > > It has been closed by Brian Potkin . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Brian Potkin < > claremont...@gmail.com> by > replying to this email. > > > -- > 1033625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033625 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > -- Forwarded message -- > From: Brian Potkin > To: 1033625-d...@bugs.debian.org > Cc: > Bcc: > Date: Thu, 30 Mar 2023 13:10:53 +0100 > Subject: Re: Bug#1033625: > On Thu 30 Mar 2023 at 09:55:24 +0200, Johan Kröckel wrote: > > > Am Mi., 29. März 2023 um 13:23 Uhr schrieb Brian Potkin < > > claremont...@gmail.com>: > > [...[ > > > > A print queue can also be manually set up by > > > > > > lpadmin -p M5526cdw -v > > > "ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/" -E -m everywhere > > > > > > Test printing with > > > > > > lp -d M5526cdw /etc/nsswitch.conf > > > > > > > This worked. This works with a job pending in Kyocera_ECOSYS_M5526cdw as > > well. > > > > Printing from a different device works as well > > while Kyocera_ECOSYS_M5526cdw has a pending job and keeps an open > > connection to the printer. > > > > Cheers, > > > > > > Brian. > > > > > > > Brian, thank you. Debugging such a problem is fun as long as someone > guides > > you/me. > > You appear happy with the outcome, John, so I am closing the report. > > Cheers, > > Brian. > > > -- Forwarded message -- > From: "Johan Kröckel" > To: Debian Bug Tracking System > Cc: > Bcc: > Date: Tue, 28 Mar 2023 23:01:47 +0200 > Subject: cups constantly without timeout connects to network printer, does > not print > Package: cups > Version: 2.4.2-2 > Severity: important > X-Debbugs-Cc: johan.kroec...@gmail.com > > I am using a Kyocera Ecosys m5526cdw over the network. Printing stopped > working (worked with this version before). > > Now when I try to start a print job cups ends with a message "Der > Druckauftrag wurde nicht angenommen.". BUT: > > Now cups connects to the printer (LED on printer lights up as long as the > pc is on) but nothing is printed. When I reboot, the LED stops to blink as > long as the system is not completely booted, then the connection starts > again. > > After running cupsctl --debug-logging, error_log grows by around 30 > megabytes per hour. > > -- System Information: > Debian Release: 12.0 > APT prefers testing-security > APT policy: (500, 'testing-security'), (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.1.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 > 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.2-2 > ii cups-common2.4.2-2 > ii cups-core-drivers 2.4.2-2 > ii cups-daemon2.4.2-2 > ii cups-filters 1.28.17-2 > ii cups-ppdc 2.4.2-2 > ii cups-server-common 2.4.2-2 > ii debconf [debconf-2.0] 1.5.82 > ii ghostscript10.0.0~dfsg-9+b1 > ii libavahi-client3 0.8-9 > ii libavahi-common3 0.8-9 > ii libc6 2.36-8 > ii libcups2 2.4.2-2 > ii libgcc-s1 12.2.0-14 > ii libstdc++6 12.2.0-14 > ii libusb-1.0-0 2:1.0.26-1 > ii poppler-utils 22.12.0-2+b1 > ii procps 2:4.0.2-3 > > Versions of packages cups recommends: > ii avahi-daemon 0.8-9 > ii colord1.4.6-2.2 > > Versions of packages cups suggests: > pn cups-bsd > pn cups-pdf > pn foomatic-db-compressed-ppds | foomatic-db > pn smbclient > ii udev 252.6-1 > > -- debconf information: > cupsys/backend: lpd, socket, usb, snmp, dnssd > cupsys/raw-print: true >
Bug#1033625:
I found #883554 when googling "implicitclass cups". That's a difference between the two print queues: One is ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/ (works) and the other is implicitclass://Kyocera_ECOSYS_M5526cdw/ (the not printing but connecting one, btw never created or configured manually).
Bug#1033625:
Am Mi., 29. März 2023 um 13:23 Uhr schrieb Brian Potkin < claremont...@gmail.com>: > On Wed 29 Mar 2023 at 11:36:50 +0200, Johan Kröckel wrote: > > > root@stockholm:~# lpstat -l -e > > Kyocera_ECOSYS_M5526cdw network none lp -d M5526cdw /etc/nsswitch.conf > > ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/ > > Printiing should take place with > > lp -d Kyocera_ECOSYS_M5526cdw /etc/nsswitch.conf > > Does it? > No. Same problem. > > root@stockholm:~# driverless > > ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/ > > A print queue can also be manually set up by > > lpadmin -p M5526cdw -v > "ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/" -E -m everywhere > > Test printing with > > lp -d M5526cdw /etc/nsswitch.conf > This worked. This works with a job pending in Kyocera_ECOSYS_M5526cdw as well. Printing from a different device works as well while Kyocera_ECOSYS_M5526cdw has a pending job and keeps an open connection to the printer. Cheers, > > Brian. > Brian, thank you. Debugging such a problem is fun as long as someone guides you/me.
Bug#1033625:
root@stockholm:~# lpstat -l -e Kyocera_ECOSYS_M5526cdw network none ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/ root@stockholm:~# lpstat -t Zeitplandienst läuft keine systemvoreingestellten Ziele Gerät für Kyocera_ECOSYS_M5526cdw: implicitclass://Kyocera_ECOSYS_M5526cdw/ Kyocera_ECOSYS_M5526cdw akzeptiert Anfragen seit Mi 29 Mär 2023 11:33:55 CEST Drucker Kyocera_ECOSYS_M5526cdw druckt jetzt Kyocera_ECOSYS_M5526cdw-10. Aktiviert seit Mi 29 Mär 2023 11:33:55 CEST Sleeping... Kyocera_ECOSYS_M5526cdw-10 anonymous 1024 Di 28 Mär 2023 21:05:38 CEST Kyocera_ECOSYS_M5526cdw-11 anonymous 1024 Di 28 Mär 2023 21:08:34 CEST root@stockholm:~# avahi-browse -rt _ipp._tcp + wlp3s0 IPv6 Kyocera ECOSYS M5526cdw Internet Printer local + wlp3s0 IPv4 Kyocera ECOSYS M5526cdw Internet Printer local = wlp3s0 IPv4 Kyocera ECOSYS M5526cdw Internet Printer local hostname = [KM3D81DC.local] address = [192.168.178.5] port = [631] txt = ["TLS=1.2" "air=none" "mopria-certified=2.0" "rp=ipp/print" "priority=48" "rfo=ipp/faxout" "kind=document,envelope" "PaperMax=legal-A4" "URF=CP255,DM4,IFU0,IS19-20,OB1-10,PQ4,RS600,SRGB24,V1.4,W8" "UUID=4509a320-0062-00a6-0101-0025074fc6da" "Color=T" "Scan=T" "Fax=T" "Duplex=T" "adminurl=https://KM3D81DC.local/airprint; "note=" "usb_MDL=Kyocera ECOSYS M5526cdw (KPDL)" "usb_MFG=Kyocera" "qtotal=1" "ty=Kyocera ECOSYS M5526cdw" "product=(ECOSYS M5526cdw)" "pdl=image/pwg-raster,application/octet-stream,application/pdf,image/tiff,image/jpeg,image/urf,application/postscript,application/vnd.hp-PCL,application/vnd.hp-PCLXL,application/vnd.xpsdocument" "txtvers=1"] = wlp3s0 IPv6 Kyocera ECOSYS M5526cdw Internet Printer local hostname = [KM3D81DC.local] address = [192.168.178.5] port = [631] txt = ["TLS=1.2" "air=none" "mopria-certified=2.0" "rp=ipp/print" "priority=48" "rfo=ipp/faxout" "kind=document,envelope" "PaperMax=legal-A4" "URF=CP255,DM4,IFU0,IS19-20,OB1-10,PQ4,RS600,SRGB24,V1.4,W8" "UUID=4509a320-0062-00a6-0101-0025074fc6da" "Color=T" "Scan=T" "Fax=T" "Duplex=T" "adminurl=https://KM3D81DC.local/airprint; "note=" "usb_MDL=Kyocera ECOSYS M5526cdw (KPDL)" "usb_MFG=Kyocera" "qtotal=1" "ty=Kyocera ECOSYS M5526cdw" "product=(ECOSYS M5526cdw)" "pdl=image/pwg-raster,application/octet-stream,application/pdf,image/tiff,image/jpeg,image/urf,application/postscript,application/vnd.hp-PCL,application/vnd.hp-PCLXL,application/vnd.xpsdocument" "txtvers=1"] root@stockholm:~# avahi-browse -rt _uscan._tcp + wlp3s0 IPv6 Kyocera ECOSYS M5526cdw _uscan._tcp local + wlp3s0 IPv4 Kyocera ECOSYS M5526cdw _uscan._tcp local = wlp3s0 IPv6 Kyocera ECOSYS M5526cdw _uscan._tcp local hostname = [KM3D81DC.local] address = [192.168.178.5] port = [9095] txt = ["mopria-certified-scan=1.3" "usb_MFG=Kyocera" "duplex=T" "is=platen,adf" "cs=color,grayscale,binary" "UUID=4509a320-0062-00a6-0101-0025074fc6da" "pdl=application/pdf,image/jpeg" "note=" "ty=Kyocera ECOSYS M5526cdw" "rs=eSCL" "representation=https://KM3D81DC.local/printer-icon/machine_128.png; "adminurl=https://KM3D81DC.local/airprint; "vers=2.63" "txtvers=1"] = wlp3s0 IPv4 Kyocera ECOSYS M5526cdw _uscan._tcp local hostname = [KM3D81DC.local] address = [192.168.178.5] port = [9095] txt = ["mopria-certified-scan=1.3" "usb_MFG=Kyocera" "duplex=T" "is=platen,adf" "cs=color,grayscale,binary" "UUID=4509a320-0062-00a6-0101-0025074fc6da" "pdl=application/pdf,image/jpeg" "note=" "ty=Kyocera ECOSYS M5526cdw" "rs=eSCL" "representation=https://KM3D81DC.local/printer-icon/machine_128.png; "adminurl=https://KM3D81DC.local/airprint; "vers=2.63" "txtvers=1"] root@stockholm:~# driverless ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/ root@stockholm:~# lpoptions -p Kyocera_ECOSYS_M5526cdw device-uri=ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/ printer-info='Kyocera ECOSYS M5526cdw' printer-location printer-make-and-model='Kyocera Kyocera ECOSYS M5526cdw (KPDL)' printer-type=83890204
Bug#1033625: thousand lines from error_log
tail_-n1000_error_log Description: Binary data
Bug#1033625:
root@stockholm:~# lpstat -l -e Kyocera_ECOSYS_M5526cdw network none ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/ root@stockholm:~# lpstat -t Zeitplandienst läuft keine systemvoreingestellten Ziele Gerät für Kyocera_ECOSYS_M5526cdw: implicitclass://Kyocera_ECOSYS_M5526cdw/ Kyocera_ECOSYS_M5526cdw akzeptiert Anfragen seit Mi 29 Mär 2023 11:33:55 CEST Drucker Kyocera_ECOSYS_M5526cdw druckt jetzt Kyocera_ECOSYS_M5526cdw-10. Aktiviert seit Mi 29 Mär 2023 11:33:55 CEST Sleeping... Kyocera_ECOSYS_M5526cdw-10 anonymous 1024 Di 28 Mär 2023 21:05:38 CEST Kyocera_ECOSYS_M5526cdw-11 anonymous 1024 Di 28 Mär 2023 21:08:34 CEST root@stockholm:~# avahi-browse -rt _ipp._tcp + wlp3s0 IPv6 Kyocera ECOSYS M5526cdw Internet Printer local + wlp3s0 IPv4 Kyocera ECOSYS M5526cdw Internet Printer local = wlp3s0 IPv4 Kyocera ECOSYS M5526cdw Internet Printer local hostname = [KM3D81DC.local] address = [192.168.178.5] port = [631] txt = ["TLS=1.2" "air=none" "mopria-certified=2.0" "rp=ipp/print" "priority=48" "rfo=ipp/faxout" "kind=document,envelope" "PaperMax=legal-A4" "URF=CP255,DM4,IFU0,IS19-20,OB1-10,PQ4,RS600,SRGB24,V1.4,W8" "UUID=4509a320-0062-00a6-0101-0025074fc6da" "Color=T" "Scan=T" "Fax=T" "Duplex=T" "adminurl=https://KM3D81DC.local/airprint; "note=" "usb_MDL=Kyocera ECOSYS M5526cdw (KPDL)" "usb_MFG=Kyocera" "qtotal=1" "ty=Kyocera ECOSYS M5526cdw" "product=(ECOSYS M5526cdw)" "pdl=image/pwg-raster,application/octet-stream,application/pdf,image/tiff,image/jpeg,image/urf,application/postscript,application/vnd.hp-PCL,application/vnd.hp-PCLXL,application/vnd.xpsdocument" "txtvers=1"] = wlp3s0 IPv6 Kyocera ECOSYS M5526cdw Internet Printer local hostname = [KM3D81DC.local] address = [192.168.178.5] port = [631] txt = ["TLS=1.2" "air=none" "mopria-certified=2.0" "rp=ipp/print" "priority=48" "rfo=ipp/faxout" "kind=document,envelope" "PaperMax=legal-A4" "URF=CP255,DM4,IFU0,IS19-20,OB1-10,PQ4,RS600,SRGB24,V1.4,W8" "UUID=4509a320-0062-00a6-0101-0025074fc6da" "Color=T" "Scan=T" "Fax=T" "Duplex=T" "adminurl=https://KM3D81DC.local/airprint; "note=" "usb_MDL=Kyocera ECOSYS M5526cdw (KPDL)" "usb_MFG=Kyocera" "qtotal=1" "ty=Kyocera ECOSYS M5526cdw" "product=(ECOSYS M5526cdw)" "pdl=image/pwg-raster,application/octet-stream,application/pdf,image/tiff,image/jpeg,image/urf,application/postscript,application/vnd.hp-PCL,application/vnd.hp-PCLXL,application/vnd.xpsdocument" "txtvers=1"] root@stockholm:~# avahi-browse -rt _uscan._tcp + wlp3s0 IPv6 Kyocera ECOSYS M5526cdw _uscan._tcp local + wlp3s0 IPv4 Kyocera ECOSYS M5526cdw _uscan._tcp local = wlp3s0 IPv6 Kyocera ECOSYS M5526cdw _uscan._tcp local hostname = [KM3D81DC.local] address = [192.168.178.5] port = [9095] txt = ["mopria-certified-scan=1.3" "usb_MFG=Kyocera" "duplex=T" "is=platen,adf" "cs=color,grayscale,binary" "UUID=4509a320-0062-00a6-0101-0025074fc6da" "pdl=application/pdf,image/jpeg" "note=" "ty=Kyocera ECOSYS M5526cdw" "rs=eSCL" "representation= https://KM3D81DC.local/printer-icon/machine_128.png; "adminurl= https://KM3D81DC.local/airprint; "vers=2.63" "txtvers=1"] = wlp3s0 IPv4 Kyocera ECOSYS M5526cdw _uscan._tcp local hostname = [KM3D81DC.local] address = [192.168.178.5] port = [9095] txt = ["mopria-certified-scan=1.3" "usb_MFG=Kyocera" "duplex=T" "is=platen,adf" "cs=color,grayscale,binary" "UUID=4509a320-0062-00a6-0101-0025074fc6da" "pdl=application/pdf,image/jpeg" "note=" "ty=Kyocera ECOSYS M5526cdw" "rs=eSCL" "representation= https://KM3D81DC.local/printer-icon/machine_128.png; "adminurl= https://KM3D81DC.local/airprint; "vers=2.63" "txtvers=1"] root@stockholm:~# driverless ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/ root@stockholm:~# lpoptions -p Kyocera_ECOSYS_M5526cdw device-uri=ipps://Kyocera%20ECOSYS%20M5526cdw._ipps._tcp.local/ printer-info='Kyocera ECOSYS M5526cdw' printer-location printer-make-and-model='Kyocera Kyocera ECOSYS M5526cdw (KPDL)' printer-type=83890204
Bug#1033625: cups constantly without timeout connects to network printer, does not print
Package: cups Version: 2.4.2-2 Severity: important X-Debbugs-Cc: johan.kroec...@gmail.com I am using a Kyocera Ecosys m5526cdw over the network. Printing stopped working (worked with this version before). Now when I try to start a print job cups ends with a message "Der Druckauftrag wurde nicht angenommen.". BUT: Now cups connects to the printer (LED on printer lights up as long as the pc is on) but nothing is printed. When I reboot, the LED stops to blink as long as the system is not completely booted, then the connection starts again. After running cupsctl --debug-logging, error_log grows by around 30 megabytes per hour. -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.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 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.2-2 ii cups-common2.4.2-2 ii cups-core-drivers 2.4.2-2 ii cups-daemon2.4.2-2 ii cups-filters 1.28.17-2 ii cups-ppdc 2.4.2-2 ii cups-server-common 2.4.2-2 ii debconf [debconf-2.0] 1.5.82 ii ghostscript10.0.0~dfsg-9+b1 ii libavahi-client3 0.8-9 ii libavahi-common3 0.8-9 ii libc6 2.36-8 ii libcups2 2.4.2-2 ii libgcc-s1 12.2.0-14 ii libstdc++6 12.2.0-14 ii libusb-1.0-0 2:1.0.26-1 ii poppler-utils 22.12.0-2+b1 ii procps 2:4.0.2-3 Versions of packages cups recommends: ii avahi-daemon 0.8-9 ii colord1.4.6-2.2 Versions of packages cups suggests: pn cups-bsd pn cups-pdf pn foomatic-db-compressed-ppds | foomatic-db pn smbclient ii udev 252.6-1 -- debconf information: cupsys/backend: lpd, socket, usb, snmp, dnssd cupsys/raw-print: true
Bug#1011241: kodi: Unable to change timezone (Kodi only uses system’s timezone)
Hi Vasyl. Thank you very much for this super quick answer :) > cdatetime-std-chrono patches fix the issue where too narrow representation of > timepoints > made Kodi unusable if a media item referenced a date before 1902. This > patchset is not > yet merged upstream, but will be in 20.0~alpha2. > > Christian's deb-multimedia builds dont have most patches I added for Kodi > from Debian so > their users still experience the bug, to my knowledge. > Ok, thanks for the explanation. I don’t have media from that long ago, so I never faced this bug. > Let me quickly reproduce an issue and issue a test build for you. > Are you comfortable installing packages via "dpkg -i" ? I can run it in a test environment with no access to data, so if you have a patch you want me to try don’t hesitate. You can even send me a git diff output or a patch file and I can rebuild the package. -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#1009417: saga: FTBFS: configure: error: cannot import Python module "distutils".
I will check.
The mRMR issue has been addressed. I will target a new release (and change
the build system to cmake, as autotools will be deprecated next release).
On Tue, Apr 12, 2022 at 10:55 PM Sebastiaan Couwenberg
wrote:
> On 4/12/22 20:23, Lucas Nussbaum wrote:
> >> checking for python script directory (pythondir)...
> ${PYTHON_PREFIX}/lib/python3.10/site-packages
> >> checking for python extension module directory (pyexecdir)...
> ${PYTHON_EXEC_PREFIX}/lib/python3.10/site-packages
> >> checking for python3.10... (cached) /usr/bin/python3
> >> checking for a version of Python >= '2.1.0'... yes
> >> checking for the distutils Python package... no
> >> configure: error: cannot import Python module "distutils".
> >> Please check your Python installation. The error was:
> >> :1: DeprecationWarning: The distutils package is deprecated and
> slated for removal in Python 3.12. Use setuptools or check PEP 632 for
> potential alternatives
>
> Johan can you fix this (upstream)?
>
> And has the mRMR license issue been addressed upstream to unblock
> updating the package to 8.x?
>
> Kind Regards,
>
> Bas
>
> --
> GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
>
Bug#1006310: lsusb output
johan@stoltw8783:~$ lsusb -v -d 1bcf:28c4
Bus 003 Device 002: ID 1bcf:28c4 Sunplus Innovation Technology Inc.
Integrated_Webcam_HD
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.01
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x1bcf Sunplus Innovation Technology Inc.
idProduct 0x28c4
bcdDevice 86.16
iManufacturer 1 CN00XMGG8LG00187CAN4A04
iProduct 2 Integrated_Webcam_HD
iSerial 3 01.00.00
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x03f3
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 14 Video
bFunctionSubClass 3 Video Interface Collection
bFunctionProtocol 0
iFunction 4
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 14 Video
bInterfaceSubClass 1 Video Control
bInterfaceProtocol 1
iInterface 4
VideoControl Interface Descriptor:
bLength 13
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdUVC 1.50
wTotalLength 0x006f
dwClockFrequency 48.00MHz
bInCollection 1
baInterfaceNr( 0) 1
VideoControl Interface Descriptor:
bLength 18
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType 0x0201 Camera Sensor
bAssocTerminal 0
iTerminal 0
wObjectiveFocalLengthMin 0
wObjectiveFocalLengthMax 0
wOcularFocalLength 0
bControlSize 3
bmControls 0x003e
Auto-Exposure Mode
Auto-Exposure Priority
Exposure Time (Absolute)
Window
Region of Interest
VideoControl Interface Descriptor:
bLength 13
bDescriptorType 36
bDescriptorSubtype 5 (PROCESSING_UNIT)
bUnitID 2
bSourceID 1
wMaxMultiplier 16384
bControlSize 3
bmControls 0x177f
Brightness
Contrast
Hue
Saturation
Sharpness
Gamma
White Balance Temperature
Backlight Compensation
Gain
Power Line Frequency
White Balance Temperature, Auto
iProcessing 0
bmVideoStandards 0x00
VideoControl Interface Descriptor:
bLength 29
bDescriptorType 36
bDescriptorSubtype 6 (EXTENSION_UNIT)
bUnitID 3
guidExtensionCode {0fb885c3-68c2-4547-90f7-8f47579d95fc}
bNumControls 8
bNrInPins 1
baSourceID( 0) 2
bControlSize 4
bmControls( 0) 0xff
bmControls( 1) 0x00
bmControls( 2) 0x00
bmControls( 3) 0x00
iExtension 0
VideoControl Interface Descriptor:
bLength 29
bDescriptorType 36
bDescriptorSubtype 6 (EXTENSION_UNIT)
bUnitID 4
guidExtensionCode {63610682-5070-49ab-b8cc-b3855e8d221d}
bNumControls 22
bNrInPins 1
baSourceID( 0) 3
bControlSize 4
bmControls( 0) 0xff
bmControls( 1) 0xff
bmControls( 2) 0x71
bmControls( 3) 0x06
iExtension 0
VideoControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 5
wTerminalType 0x0101 USB Streaming
bAssocTerminal 0
bSourceID 4
iTerminal 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x87 EP 7 IN
bmAttributes 3
Transfer Type
Bug#1006310: Debian Bullesye webcam support
Package: libv4l-0 Version: 1.22.1-2 Severity: Normal Hi, I have a newly installed Dell Precision 7650, Debian 11.2 and can't get any picture on the webcam. I have tried both the Bullseye packages and from backports Bus 003 Device 002: ID 1bcf:28c4 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Is this hardware supported ? Linux stoltw8783 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux -- Johan Andersson | Infrastructure Engineering - Persistent Storage Team| King, Stockholm | +46721827568 | johan.anders...@king.com |
Bug#1002216: jpylyzer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
I just created a bugfix release that should fix this, details here: https://github.com/openpreserve/jpylyzer/issues/176#issuecomment-1009877080
Bug#1001015: "E: Removing essential system-critical packages is not permitted. This might break the system." for foreign-arch multiarch essential/protected packages
Package: apt
Version: 2.3.13
Severity: important
X-Debbugs-Cc: johan.laenen+debianb...@gmail.com
Dear Maintainer,
I removed steam from my system, a 64bit machine:
root@msi:/home/gargle# dpkg --print-architecture
amd64
Steam needed i386 stuff, so I added the architecture before doing apt-get
install steam. Some i386 packages were indeed installed. I purged them all but
three remain, and I cannot get rid of them:
root@msi:/home/gargle# dpkg --get-selections | grep i386 | awk '{print $1}'
gcc-11-base:i386
libc6:i386
libgcc-s1:i386
root@msi:/home/gargle# apt-get remove --purge gcc-11-base:i386 libgcc-s1:i386
libc6:i386
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
gcc-11-base:i386* libc6:i386* libgcc-s1:i386*
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
libgcc-s1:i386 gcc-11-base:i386 (due to libgcc-s1:i386) libc6:i386 (due to
libgcc-s1:i386)
0 upgraded, 0 newly installed, 3 to remove and 156 not upgraded.
After this operation, 12.9 MB disk space will be freed.
E: Removing essential system-critical packages is not permitted. This might
break the system.
-- Package-specific info:
-- apt-config dump --
APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::LastInstalledKernel "5.15.0-1-amd64";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit
0 ; apt-show-versions -i";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service &&
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call
--system --dest org.freedesktop.PackageKit --object-path
/org/freedesktop/PackageKit --timeout 4 --method
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo
> /dev/null";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "false";
APT::Compressor::zstd::Cost "60";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "200";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "300";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-6";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::lzma "";
Bug#996805: nemo: Freezes when opening a folder that contains a large GIF file
Hello,
I decided to take another shot at this and I still can't believe it, but I
actually ended up fixing it.
Hooking a debugger to Nemo and stopping it in the middle of the freeze shows
that it's hanging inside libgdk_pixbuf-2.0.so. More specifically, once Nemo
calls gdk_pixbuf_loader_write() inside get_pixbuf_for_content() (in
nemo-directory-async.c) the function takes a very long time to return or never
returns at all for very large GIFs. Most likely, this means there's a
regression inside libgdk_pixbuf-2.0.so, which also makes sense in the context
of my original report: the bug is present in Debian 11 and Arch (both use
version 2.42), but not in Debian 10 (which uses version 2.38) nor in Mint 20.1
(which uses version 2.40). The code of get_pixbuf_for_content() between Debian
and Mint's source packages is also the same, and doesn't change for Nemo 5.0.3
either, so the whole picture is congruent. I tried "forward-porting" Buster's
libgdk_pixbuf just for confirmation, but unfortunately that doesn't seem
compatible with the rest of the system.
When looking at get_pixbuf_for_content(), there's a comment mentioning the need
to call gdk_pixbuf_loader_write() with chunks of the file to process, however
Nemo's implementation doesn't actually do this and shoves the whole file in one
go at gdk_pixbuf_loader_write() which then seems to choke on it. Making slight
adjustments so that the file is actually served in chunks as the comment
mentions actually fixes the whole issue. I recompiled Nemo with such changes
and the fix seems to hold.
Nemo's original get_pixbuf_for_content() is pretty self-contained so it can be
extracted into a standalone program of just a handful of lines as a minimal
reproducible example. I did it and tried it both on Debian 11 and Mint 20.1 and
the behavior is as expected: it freezes on Debian but works on Mint. I also
tested the changes in this way to take time measurements for different chunk
sizes and compare performance between the fixed version and the original one on
Mint.
I'm attaching a patch for Nemo's get_pixbuf_for_content() as well as the
examples mentioned (which aren't very nice, but should be good enough to
illustrate). I hope this is useful. This is my first time reporting an issue on
and making a submission to an open source project, so I apologize if something
doesn't turn out to be tidy enough.
My only other question is whether there's any chance of seeing this properly
fixed for Bullseye in some way in the future.--- ../original/nemo-4.8.6/libnemo-private/nemo-directory-async.c 2021-03-05 08:57:48.0 -0500
+++ libnemo-private/nemo-directory-async.c 2021-10-21 22:27:11.0 -0400
@@ -3902,7 +3902,7 @@
gboolean res;
GdkPixbuf *pixbuf, *pixbuf2;
GdkPixbufLoader *loader;
- gsize chunk_len;
+ gsize chunk_len = 1;
pixbuf = NULL;
loader = gdk_pixbuf_loader_new ();
@@ -3912,12 +3912,20 @@
/* For some reason we have to write in chunks, or gdk-pixbuf fails */
res = TRUE;
- while (res && file_len > 0) {
+ while (res && file_len > chunk_len) {
+ res = gdk_pixbuf_loader_write (loader, (guchar *) file_contents, chunk_len, NULL);
+ file_contents += chunk_len;
+ file_len -= chunk_len;
+ }
+
+ if (res && file_len != 0)
+ {
chunk_len = file_len;
res = gdk_pixbuf_loader_write (loader, (guchar *) file_contents, chunk_len, NULL);
file_contents += chunk_len;
file_len -= chunk_len;
}
+
if (res) {
res = gdk_pixbuf_loader_close (loader, NULL);
}
//needs libgdk-pixbuf2.0-dev installed.
//Compile with g++ mre_original.cpp -L/usr/lib/x86_64-linux-gnu/ -lgdk_pixbuf-2.0 -lglib-2.0 -lgobject-2.0 -I/usr/include/gdk-pixbuf-2.0/gdk-pixbuf/ -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/glib-2.0/ -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -o original
#include
#include
#include "gdk-pixbuf.h"
#include
using namespace std;
static GdkPixbuf *
get_pixbuf_for_content (int file_len,
char *file_contents);
int main(int argc, char *argv[])
{
if(argc != 2)
{
printf("wrong number of arguments\n");
exit(123);
}
char *filePath=argv[1];
FILE *fp = fopen(filePath, "rb");
if(fp==nullptr)
{
printf("error openning file\n");
exit(123);
}
fseek(fp, 0, SEEK_END);
int size = ftell(fp);
fseek(fp, 0, SEEK_SET);
std::vector fileContents;
fileContents.resize(size);
char * ptr = fileContents.data();
int readQty = fread(ptr, 1, size, fp);
fclose(fp);
if(readQty != size)
{
printf("error reading file: read: %d, size: %d\n", readQty, size);
exit(123);
}
get_pixbuf_for_content(size, ptr);
return 0;
}
static GdkPixbuf *
get_pixbuf_for_content (int file_len,
char *file_contents)
{
gboolean res;
GdkPixbuf *pixbuf, *pixbuf2;
GdkPixbufLoader *loader;
gsize chunk_len;
pixbuf = NULL;
loader = gdk_pixbuf_loader_new ();
/* For some reason we have to write in chunks, or gdk-pixbuf fails */
res = TRUE;
while (res && file_len > 0) {
chunk_len = file_len;
res =
Bug#996805: nemo: Freezes when opening a folder that contains a large GIF file
Package: nemo Version: 4.8.6-2 Severity: normal X-Debbugs-Cc: jcdeb...@protonmail.ch Dear Maintainer, * What led up to the situation? After Upgrading to Debian 11, opening a folder that contained a big GIF file caused all open Nemo windows to freeze. Opening a single folder with a 10MB GIF causes every opened Nemo window to freeze for about 20 seconds and to use 100% of a processor core on a Ryzen 5900X system. This only happens when using Icon view for the folder in question and only when using the maximum zoom available. It does not happen in List view nor in Compact view nor at smaller zoom levels. It did not happen on Debian 10. The bigger the GIF file the more Nemo takes to unfreeze. I have a directory with a few much bigger GIF files in it and I cannot visit it on my system, while other folders with smaller GIFs take many seconds to load. * What exactly did you do (or not do) that was effective (or ineffective)? I tried a clean installation of Debian 11 on a virtual machine to rule out configuration issues with my system, and I was able to reproduce the issue on the VM as well. I also upgraded the VM to testing (which has Nemo 5.0.3), and it seems it is also affected by the issue. I looked for a solution online and found a Linux Mint bugtracker issue regarding slowdowns when icon captions are enabled, but disabling them did not change anything. It is worth noting however that it is coincidentally at the maximum zoom level that more captions show. There is additionally an issue on their bugtracker describing the same problem I am reporting, reported by an Arch user (see https://github.com/linuxmint/nemo/issues/2756), however it seems the Mint team was unable to reproduce it. I proceeded to make a VM with Linux Mint 20.1 and I could not reproduce the issue either despite the fact that Mint 20.1 ships with the same Nemo version as Debian 11 (Nemo 4.8.6), so it seems this might be an issue with other distributions. Disabling thumbnails effectively makes the issue disappear. Nemo uses gdk-pixbuf-thumbnailer to generate thumbnails for GIF files, but running the same command Nemo uses to create a thumbnail for a big GIF on the command line exits immediately with success. I attempted to configure ffmpegthumbnailer to be used for GIF files thumbnail generation and it didn't seem to have any effect on Nemo freezing either. Running nemo --debug on a folder with a large GIF file does not seem to provide any hints. Running strace on nemo in the same conditions shows nemo hangs in a loop calling mmap/mremap, however that's not very helpful. I'm out of ideas on how to debug further. Considering the ease of reproduction and that the logs don't seem to point to anything evident, I'm not including them in this report, but I can include them later on if necessary. * What was the outcome of this action? Nothing really worked. The only solution is to dodge the issue by disabling thumbnails or using other view styles or zoom levels. * What outcome did you expect instead? The folder with the large GIF file to open in a reasonable amount of time with no system effort. Test GIFs of different sizes can be generated with ease from any video with ffmpeg (e.g. ffmpeg -t 5 -i output.gif). Every one I tried caused the same issue. -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/2 CPU threads) 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 nemo depends on: ii cinnamon-desktop-data 4.8.1-2 ii desktop-file-utils 0.26-1 ii gsettings-desktop-schemas 3.38.0-2 ii gvfs 1.46.2-1 ii libatk1.0-02.36.0-2 ii libc6 2.31-13+deb11u2 ii libcairo-gobject2 1.16.0-5 ii libcairo2 1.16.0-5 ii libcinnamon-desktop4 4.8.1-2 ii libexempi8 2.5.2-1 ii libexif12 0.6.22-3 ii libgail-3-03.24.24-4 ii libgdk-pixbuf-2.0-02.42.2+dfsg-1 ii libglib2.0-0 2.66.8-1 ii libglib2.0-data2.66.8-1 ii libgtk-3-0 3.24.24-4 ii libnemo-extension1 4.8.6-2 ii libnotify4 0.7.9-3 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-01.46.2-3 ii libselinux13.1-3 ii libx11-6 2:1.7.2-1 ii libxapp1 2.0.7-1 ii libxml22.9.10+dfsg-6.7 ii nemo-data 4.8.6-2 ii shared-mime-info 2.0-1 Versions of packages nemo recommends: ii cinnamon-l10n4.8.3-1 ii gvfs-backends
Bug#996611: Acknowledgement (/usr/bin/firefox: when starting firefox after my latest dist-upgrade I get a warning about /usr/bin/which)
Dear maintainer, my bug report is a copy of #996455 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996455>. My excuses, I didn't see this when logging. This report may be closed. Greetings, Johan On Sat, 16 Oct 2021 at 07:33, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 996611: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996611. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > johan.laenen+debianb...@gmail.com > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Maintainers of Mozilla-related packages < > team+pkg-mozi...@tracker.debian.org> > > If you wish to submit further information on this problem, please > send it to 996...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 996611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996611 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#996611: /usr/bin/firefox: when starting firefox after my latest dist-upgrade I get a warning about /usr/bin/which
Package: firefox-esr Version: 91.2.0esr-1 Severity: minor File: /usr/bin/firefox X-Debbugs-Cc: johan.laenen+debianb...@gmail.com Dear Maintainer, when starting firefox from the command line I get a warning about /usr/bin/which: gargle@msi:~$ firefox & [1] 1288 gargle@msi:~$ /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead. firefox starts without a problem. I didn't expect this warning. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox-esr depends on: ii debianutils 5.5-1 ii fontconfig 2.13.1-4.2 ii libatk1.0-0 2.36.0-2 ii libc62.32-4 ii libcairo-gobject21.16.0-5 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.20-2 ii libdbus-glib-1-2 0.112-2 ii libevent-2.1-7 2.1.12-stable-1 ii libffi8 3.4.2-3 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.11.0+dfsg-1 ii libgcc-s111.2.0-9 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libglib2.0-0 2.70.0-1+b1 ii libgtk-3-0 3.24.30-3 ii libnspr4 2:4.32-1 ii libnss3 2:3.70-1 ii libpango-1.0-0 1.48.10+ds1-1 ii libstdc++6 11.2.0-9 ii libvpx6 1.10.0-2 ii libx11-6 2:1.7.2-2+b1 ii libx11-xcb1 2:1.7.2-2+b1 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.4-1 ii libxfixes3 1:5.0.3-2 ii libxrender1 1:0.9.10-1 ii procps 2:3.3.17-5 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages firefox-esr recommends: ii libavcodec58 7:4.4-6+b2 Versions of packages firefox-esr suggests: ii fonts-lmodern 2.004.5-6.1 pn fonts-stix | otf-stix ii libcanberra0 0.30-8 ii libgssapi-krb5-2 1.18.3-7 ii pulseaudio 15.0+dfsg1-2 -- no debconf information
Bug#993749: network-manager: Connecting/creating a WWAN connection fails with gnome shell js-error in journal
Package: network-manager Version: 1.30.0-2 Severity: important X-Debbugs-Cc: johan.kroec...@gmail.com When I click "connect" in the mobile broadband submenu the assistant for creating a new connection should open, but nothing happens and the journal shows: Sep 06 00:50:10 X gnome-shell[1507]: JS ERROR: Error: Argument string may not be null _packVariant@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:104:29 _init/this.Variant._new_internal@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:298:35 launchSettingsPanel/param<@resource:///org/gnome/shell/ui/status/network.js:88:31 launchSettingsPanel@resource:///org/gnome/shell/ui/status/network.js:88:22 _autoConnect@resource:///org/gnome/shell/ui/status/network.js:567:28 addAction/<@resource:///org/gnome/shell/ui/popupMenu.js:538:21 activate@resource:///org/gnome/shell/ui/popupMenu.js:191:14 vfunc_button_release_event@resource:///org/gnome/shell/ui/popupMenu.js:138:14 When I try to create the connection directly, the assistant fails at the end with: Sep 06 00:55:56 X gnome-control-c[3357]: value "((NMSettingSerialParity) 110)" of type 'NMSettingSerialParity' is invalid or out of range for property 'parity' of type 'NMSettingSerialParity' Sep 06 00:55:56 X NetworkManager[664]: [1630882556.8868] audit: op="connection-add-activate" pid=3357 uid=1000 result="fail" reason="Connection 'T-Mobile(Telekom) Vorgabe' is not available on device cdc-wdm0 because device is not available" Sep 06 00:55:56 X gnome-control-c[3357]: Failed to add new connection: (2) Connection 'T-Mobile(Telekom) Vorgabe' is not available on device cdc-wdm0 because device is not available Thanks -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager depends on: ii adduser 3.118 ii dbus 1.12.20-2 ii libaudit11:3.0-2 ii libbluetooth35.55-3.1 ii libc62.31-13 ii libcurl3-gnutls 7.74.0-1.3+b1 ii libglib2.0-0 2.66.8-1 ii libgnutls30 3.7.1-5 ii libjansson4 2.13.1-1.1 ii libmm-glib0 1.14.12-0.2 ii libndp0 1.6-1+b1 ii libnewt0.52 0.52.21-4+b3 ii libnm0 1.30.0-2 ii libpsl5 0.21.0-1.2 ii libreadline8 8.1-1 ii libselinux1 3.1-3 ii libsystemd0 247.3-6 ii libteamdctl0 1.31-1 ii libudev1 247.3-6 ii libuuid1 2.36.1-8 ii policykit-1 0.105-31 ii udev 247.3-6 ii wpasupplicant2:2.9.0-21 Versions of packages network-manager recommends: ii dnsmasq-base [dnsmasq-base] 2.85-1 ii iptables 1.8.7-1 ii libpam-systemd 247.3-6 ii modemmanager 1.14.12-0.2 ii ppp 2.4.9-1+1 ii wireless-regdb 2020.04.29-2 Versions of packages network-manager suggests: ii isc-dhcp-client 4.4.1-2.3 pn libteam-utils -- no debconf information
Bug#986257: RFS: age/1.0.0~rc1-2 -- simple, modern and secure encryption tool
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "age": * Package name: age Version : 1.0.0~rc1-2 Upstream Author : Filippo Valsorda * URL : https://github.com/FiloSottile/age * License : BSD-3-clause, Expat, ISC * Vcs : https://salsa.debian.org/go-team/packages/age Section : utils It builds those binary packages: age - simple, modern and secure encryption tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/age/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/age/age_1.0.0~rc1-2.dsc Changes since the last upload: age (1.0.0~rc1-2) unstable; urgency=medium . * Set main.Version at build time to ease debuging (Closes: #986144) Regards, -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#985028: RFS: age/1.0.0~rc1-1 -- simple, modern and secure encryption tool
Hey Christoph! Thanks for the upload. Regarding UNRELEASED vs unstable, to be honest I never now who’s role it is to update debian/changelog. As I am not a DM or DD, I can’t really upload to unstable myself so I always thought I had to put UNRELEASED here. -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#985028: RFS: age/1.0.0~rc1-1 -- simple, modern and secure encryption tool
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "age": * Package name: age Version : 1.0.0~rc1-1 Upstream Author : Filippo Valsorda * URL : https://github.com/FiloSottile/age * License : Expat, BSD-3-clause, ISC * Vcs : https://salsa.debian.org/go-team/packages/age Section : utils It builds those binary packages: age - simple, modern and secure encryption tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/age/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/age/age_1.0.0~rc1-1.dsc Changes since the last upload: age (1.0.0~rc1-1) UNRELEASED; urgency=medium . [ nicoo ] * d/rules: Do not build PIE binaries on architectures where go cannot (Closes: #981412) * d/control: Declare compliance with policy v4.5.1 * New upstream version 1.0.0~beta6 + New `-R` flag to specify a file with a list of recipients. + Armored encoding now up to 20× faster . [ Johan Fleury ] * New upstream version 1.0.0~rc1 (Closes: #981413) + age: when writing to an existing file, its content will be overwritten + age: new `-e`/`--encrypt` flag + age-keygen: new `-y` flag to convert identity file to recipient file Regards -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#981592: Compose key can not create Greek symbols
Hi,
I saw something similar so decided to share it here. Maybe it will help you.
I have this in my /usr/share/X11/xkb/symbols/us
key { [ grave, asciitilde,dead_grave, dead_tilde ]
};
key { [ 6,asciicircum, dead_circumflex, dead_caron ]
};
key { [ minus, underscore, dead_macron, degree ]
};
key { [ bracketleft, braceleft, guillemotleft, dead_doublegrave ]
};
key { [bracketright, braceright, guillemotright, dead_doubleacute
] };
key { [apostrophe, quotedbl,dead_acute, dead_diaeresis ]
};
key { [ comma, less, dead_cedilla, dead_ogonek ]
};
key { [ slash, question, questiondown, dead_stroke ]
};
key { [ backslash,bar,dead_greek,brokenbar ]
};
key { [ backslash,bar,dead_greek,brokenbar ]
};
(from https://www.choam.eu/altgr-intl/#weur)
Running setupconf gives me 8 warnings:
Mar 10 15:36:22 msi console-setup.sh[560]: WARNING: Unknown X keysym
"dead_greek"
Mar 10 15:36:22 msi console-setup.sh[560]: WARNING: Unknown X keysym
"dead_greek"
Mar 10 15:36:22 msi console-setup.sh[560]: WARNING: Unknown X keysym
"dead_greek"
Mar 10 15:36:22 msi console-setup.sh[560]: WARNING: Unknown X keysym
"dead_greek"
Mar 10 15:36:22 msi console-setup.sh[560]: WARNING: Unknown X keysym
"dead_greek"
Mar 10 15:36:22 msi console-setup.sh[560]: WARNING: Unknown X keysym
"dead_greek"
Mar 10 15:36:22 msi console-setup.sh[560]: WARNING: Unknown X keysym
"dead_greek"
Mar 10 15:36:22 msi console-setup.sh[560]: WARNING: Unknown X keysym
"dead_greek"
dead_grave, dead_circumflex, dead_tilde, dead_acute, dead_cedilla, and
dead_diaeresis work as intended on the console, the other dead keys spit
out the normal characters. In X all the dead keys work as intended.
Did you check your logs?
My system:
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages console-setup depends on:
ii console-setup-linux 1.200
ii debconf 1.5.74
ii keyboard-configuration 1.200
ii xkb-data2.29-2
console-setup recommends no packages.
Versions of packages console-setup suggests:
ii locales 2.31-9
ii lsb-base 11.1.0
Versions of packages keyboard-configuration depends on:
ii debconf 1.5.74
ii liblocale-gettext-perl 1.07-4+b1
Versions of packages console-setup-linux depends on:
ii init-system-helpers 1.60
ii initscripts 2.96-5
ii kbd 2.3.0-3
ii keyboard-configuration 1.200
console-setup-linux suggests no packages.
Versions of packages console-setup is related to:
pn console-common
pn console-data
pn console-tools
pn gnome-control-center
ii kbd 2.3.0-3
ii systemd 247.2-5
-- debconf information:
keyboard-configuration/store_defaults_in_debconf_db: true
console-setup/charmap47: UTF-8
console-setup/codesetcode: Lat15
console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic
languages
console-setup/fontface47: Fixed
console-setup/store_defaults_in_debconf_db: true
console-setup/fontsize: 8x16
console-setup/fontsize-fb47: 8x16
keyboard-configuration/optionscode: ctrl:nocaps
keyboard-configuration/altgr: The default for the keyboard layout
keyboard-configuration/ctrl_alt_bksp: false
keyboard-configuration/unsupported_options: true
console-setup/framebuffer_only:
keyboard-configuration/unsupported_layout: true
* keyboard-configuration/layout: English (US)
keyboard-configuration/unsupported_config_layout: true
keyboard-configuration/modelcode: pc105
keyboard-configuration/compose: No compose key
console-setup/guess_font:
keyboard-configuration/xkb-keymap: us
console-setup/use_system_font:
keyboard-configuration/switch: No temporary switch
keyboard-configuration/variantcode: altgr-weur
keyboard-configuration/toggle: No toggling
keyboard-configuration/layoutcode: us
console-setup/fontsize-text47: 8x16
debian-installer/console-setup-udeb/title:
keyboard-configuration/other:
* keyboard-configuration/unsupported_config_options: true
* keyboard-configuration/model: Generic 105-key PC (intl.)
* keyboard-configuration/variant: English (US) - English (intl., with AltGr
dead keys)
greetings,
Johan
Bug#982356: Testing Vagrant box shows unexpected IP address after first vagrant up
Package: cloud.debian.org
Version: 20210207.1
When I specify an additional interface using 'testing.vm.network
"private_network", name: "my_network", ip: "10.249.10.10", :mac =>
"1010"' and I perform "vagrant up", there are two interfaces on
the host named testing.
One interface has an IP address inside the 192.168.121.0/24 network.
The other interface has two IP addresses: the specified 10.249.10.10 IP
address and another IP address inside the 10.249.10.0/24 network.
This second IP address disappears after "vagrant reload".
I attached a Vagrantfile to this email.
One can type these commands to check that two addresses are indeed added
to interface ens6:
$ vagrant up
$ vagrant ssh testing
$ ip a show ens6
Some tools (such as openvpn) do not like that the second interface
(ens6) has two IP addresses.
I suggest that the DHCP provided IP address be removed once the IP
address specified in the Vagrantfile is setup.
I am using Debian Buster, kernel 5.9.0-5-amd64, libc6 2.28-10, vagrant
2.2.3 et libvirt 5.0.0-4+deb10u1.
Les données à caractère personnel recueillies et traitées dans le cadre de cet
échange, le sont à seule fin d’exécution d’une relation professionnelle et
s’opèrent dans cette seule finalité et pour la durée nécessaire à cette
relation. Si vous souhaitez faire usage de vos droits de consultation, de
rectification et de suppression de vos données, veuillez contacter
contact.r...@sgdsn.gouv.fr. Si vous avez reçu ce message par erreur, nous vous
remercions d’en informer l’expéditeur et de détruire le message. The personal
data collected and processed during this exchange aims solely at completing a
business relationship and is limited to the necessary duration of that
relationship. If you wish to use your rights of consultation, rectification and
deletion of your data, please contact: contact.r...@sgdsn.gouv.fr. If you have
received this message in error, we thank you for informing the sender and
destroying the message.
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.define "testing" do |testing|
testing.vm.box = "debian/testing64"
testing.vm.box_version = "20210124.1"
testing.vm.hostname = "testing"
testing.vm.network "private_network", name: "my_network", ip:
"10.249.10.10", :mac => "1010"
testing.vm.synced_folder ".", "/vagrant", type: "rsync", rsync__exclude:
".git/"
end
end
Bug#982125: (No Subject)
So I found out that this bug is actually from libblockdev: it has been reported upstream in libblockdev#453 [1] and fixed in libblockdev#415 [2] (released with 2.21-1). I’ve made a MR on Salsa [3]. [1] https://github.com/storaged-project/libblockdev/issues/453 [2] https://github.com/storaged-project/libblockdev/pull/415 [3] https://salsa.debian.org/utopia-team/libblockdev/-/merge_requests/2 -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#982125: lvm2-dbusd: lvremove fails with ValueError (from `options_to_cli_args`)
Package: lvm2-dbusd
Version: 2.03.02-3
Severity: important
Tags: upstream
Dear Maintainer,
While working on targetd (ITP #968297), I figured removing an LV through
lvm2-dbusd fails with (other operations like creating a new LV work as
expected):
```
lvmdbusd[30995]: 30995:30999 - Exception returned to client:
lvmdbusd[30995]: Traceback (most recent call last):
lvmdbusd[30995]: File "/usr/lib/python3/dist-packages/lvmdbusd/request.py",
line 72, in run_cmd
lvmdbusd[30995]: result = self.method(*self.arguments)
lvmdbusd[30995]: File "/usr/lib/python3/dist-packages/lvmdbusd/lv.py", line
459, in _remove
lvmdbusd[30995]: rc, out, err = cmdhandler.lv_remove(lv_name,
remove_options)
lvmdbusd[30995]: File
"/usr/lib/python3/dist-packages/lvmdbusd/cmdhandler.py", line 391, in lv_remove
lvmdbusd[30995]: cmd.extend(options_to_cli_args(remove_options))
lvmdbusd[30995]: File
"/usr/lib/python3/dist-packages/lvmdbusd/cmdhandler.py", line 214, in
options_to_cli_args
lvmdbusd[30995]: for k, v in list(dict(options).items()):
lvmdbusd[30995]: ValueError: dictionary update sequence element #0 has length
1; 2 is required
```
I’ve added a line before `cmdhandler.py:214` to print the content of `options`
and it appears to contain:
```
dbus.Struct((dbus.Dictionary({dbus.String('--yes'): dbus.String('',
variant_level=1)}, signature=dbus.Signature('sv'), variant_level=1),),
signature=None)
```
I have no easy way to test this, but I don’t think it is fixed in newer
versions present in testing/unstable as I didn’t found any change related to
that part of the code in upstreams’s git history.
-- System Information:
Debian Release: 10.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-14-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lvm2-dbusd depends on:
ii dbus1.12.20-0+deb10u1
ii lvm22.03.02-3
ii python3 3.7.3-1
ii python3-dbus1.2.8-3
ii python3-gi 3.30.4-1
ii python3-pyudev 0.21.0-1
lvm2-dbusd recommends no packages.
lvm2-dbusd suggests no packages.
-- no debconf information
--
Johan Fleury
signature.asc
Description: OpenPGP digital signature
Bug#981475: qemu-system-common: Upgrading the backports version of qemu-system-common removed qemu-system-x86
Package: qemu-system-common Version: 1:5.2+dfsg-3~bpo10+1 Severity: important Dear Maintainer, I did apt-get upgrade and noticed that qemu-system-common and qemu-system-x86 were not included in the normal upgrade. My Qemu x86/x86_64 VMs did not work after that either. I think it was due to some library or linking related errors. I had installed Qemu from the backports some time ago. So I did dist-upgrade, and it removed qemu-system-x86 while upgrading qemu- system-common. Any x86/x86_64 Qemu VM was of course unusable after this. I installed qemu-system-x86 manually from the backports, and it seems to work normally. Only this error is given when starting it, but it's not apparently serious: = qemu-system-x86_64: warning: dbind: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. = I attached the last console output of apt-get (truncated and translated to english, btw, I think it's not necessarily a good decision to localize system utilities). -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qemu-system-common depends on: ii libaio10.3.112-3 ii libc6 2.28-10 ii libcap-ng0 0.7.9-2 ii libgbm118.3.6-2+deb10u1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgnutls303.6.7-4+deb10u5 ii libnettle6 3.4.1-1 ii libpixman-1-0 0.36.0-1 ii libseccomp22.3.3-4 ii liburing1 0.7-3~bpo10+1 ii libvirglrenderer0 0.7.0-2 ii zlib1g 1:1.2.11.dfsg-1 qemu-system-common recommends no packages. qemu-system-common suggests no packages. -- no debconf information *** /home/usrr/qemubug1.txt $ sudo apt-get dist-upgrade ... The following packages were automatically installed and are no longer required: libbrlapi0.6 libcacard0 libcapstone3 libdaxctl1 libfdt1 libndctl6 libpmem1 libslirp0 libspice-server1 libusbredirparser1 libvdeplug2 libvirglrenderer0 libxencall1 libxendevicemodel1 libxenevtchn1 libxenforeignmemory1 libxengnttab1 libxenmisc4.11 libxenstore3.0 libxentoolcore1 libxentoollog1 qemu-system-common qemu-system-data seabios Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: qemu-system-x86 The following packages will be upgraded: qemu-system-common 1 to upgrade, 0 new, 1 to remove and 0 not upgraded. Need to download 1 646 kB. After this, 33,9 MB will be freed. ... Download:1 http://ftp.de.debian.org/debian buster-backports/main amd64 qemu- system-common amd64 1:5.2+dfsg-3~bpo10+1 [1 646 kB] ... Removing qemu-system-x86 (1:5.0-14~bpo10+1) ... (Reading database ... 359300 files and directories currently installed.) Preparing to unpack .../qemu-system-common_1%3a5.2+dfsg-3~bpo10+1_amd64.deb ... Unpacking qemu-system-common (1:5.2+dfsg-3~bpo10+1) over (1:5.0-14~bpo10+1) ... Setting up qemu-system-common (1:5.2+dfsg-3~bpo10+1) ... Processing triggers for man-db (2.8.5-2) ... $sudo apt-get install -t buster-backports qemu-system-x86 ... The following package was automatically installed and is no longer required: libcapstone3 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libcapstone4 libfdt1 Suggested packages: samba vde2 The following NEW packages will be installed: libcapstone4 qemu-system-x86 The following packages will be upgraded: libfdt1 ... Download:1 http://ftp.de.debian.org/debian buster-backports/main amd64 libcapstone4 amd64 4.0.2-3~bpo10+1 [559 kB] Download:2 http://ftp.de.debian.org/debian buster-backports/main amd64 libfdt1 amd64 1.6.0-1~bpo10+1 [21,1 kB] Download:3 http://ftp.de.debian.org/debian buster-backports/main amd64 qemu- system-x86 amd64 1:5.2+dfsg-3~bpo10+1 [8 143 kB] ... Selecting previously unselected package libcapstone4:amd64. (Reading database ... 359321 files and directories currently installed.) Preparing to unpack .../libcapstone4_4.0.2-3~bpo10+1_amd64.deb ... Unpacking libcapstone4:amd64 (4.0.2-3~bpo10+1) ... Preparing to unpack .../libfdt1_1.6.0-1~bpo10+1_amd64.deb ... Unpacking libfdt1:amd64 (1.6.0-1~bpo10+1) over (1.4.7-3) ... Selecting previously unselected package qemu-system-x86. Preparing to unpack .../qemu-system-x86_1%3a5.2+dfsg-3~bpo10+1_amd64.deb ... Unpacking qemu-system-x86 (1:5.2+dfsg-3~bpo10+1) ... Setting up libfdt1:amd64 (1.6.0-1~bpo10+1) ... Setting up libcapstone4:amd64 (4.0.2-3~bpo10+1) ... Setting up qemu-system-x86 (1:5.2+dfsg-3~bpo10+1) ...
Bug#981473: reportbug: "Other system information" box is very small in GUI
Package: reportbug Version: 7.5.3~deb10u1 Severity: wishlist Dear Maintainer, In the dialog where the bug report is written (in the reportbug GUI), there's the box "Other system information". It is very small even when the window is maximized and its size can't be changed. It would be useful to enable size adjust or just make it larger. -- Package-specific info: ** Environment settings: INTERFACE="gtk" ** /home/ussr/.reportbugrc: reportbug_version "7.1.7" mode standard ui gtk2 realname "johan" email "kurko2...@gmail.com" no-cc header "X-Debbugs-CC: kurko2...@gmail.com" smtphost reportbug.debian.org -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt1.8.2.2 ii python33.7.3-1 ii python3-reportbug 7.5.3~deb10u1 ii sensible-utils 0.0.12 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums pn dlocate pn emacs-bin-common ii file1:5.35-4+deb10u1 ii gnupg 2.2.12-1+deb10u1 pn postfix | exim4 | mail-transport-agent pn python3-urwid pn reportbug-gtk ii xdg-utils 1.1.3-1+deb10u1 Versions of packages python3-reportbug depends on: ii apt1.8.2.2 ii file 1:5.35-4+deb10u1 ii python33.7.3-1 ii python3-apt1.8.4.3 ii python3-debian 0.1.35 ii python3-debianbts 2.8.2 ii python3-requests 2.21.0-1 ii sensible-utils 0.0.12 python3-reportbug suggests no packages.
Bug#981472: reportbug: Package can't be changed except by restarting reportbug
Package: reportbug Version: 7.5.3~deb10u1 Severity: minor Dear Maintainer, For example, enter qemu-system-x86 into the package name field, then search for already submitted bugs. Now you notice that the bug is actually in qemu-system- common. Press the Back button until you arrive to the start, however, it's apparently not possible to change the chosen package name except by restarting reportbug. -- Package-specific info: ** Environment settings: INTERFACE="gtk" ** /home/user/.reportbugrc: reportbug_version "7.1.7" mode standard ui gtk2 realname "johan" email "kurko2...@gmail.com" no-cc header "X-Debbugs-CC: kurko2...@gmail.com" smtphost reportbug.debian.org -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages reportbug depends on: ii apt1.8.2.2 ii python33.7.3-1 ii python3-reportbug 7.5.3~deb10u1 ii sensible-utils 0.0.12 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail pn debconf-utils pn debsums pn dlocate pn emacs-bin-common ii file1:5.35-4+deb10u1 ii gnupg 2.2.12-1+deb10u1 pn postfix | exim4 | mail-transport-agent pn python3-urwid pn reportbug-gtk ii xdg-utils 1.1.3-1+deb10u1 Versions of packages python3-reportbug depends on: ii apt1.8.2.2 ii file 1:5.35-4+deb10u1 ii python33.7.3-1 ii python3-apt1.8.4.3 ii python3-debian 0.1.35 ii python3-debianbts 2.8.2 ii python3-requests 2.21.0-1 ii sensible-utils 0.0.12 python3-reportbug suggests no packages.
Bug#980261: RFS: jgmenu/4.3.0-1 [RFP] -- Simple X11 menu
GPL2 applies. > On 26 Jan 2021, at 22:27, Boyuan Yang wrote: > > X-Debbugs-CC: mat...@linuxmint.pl jgm...@gmail.com > > >> On Sat, 16 Jan 2021 21:38:16 +0100 =?UTF-8?Q?Mateusz_=c5=81ukasik?= >> wrote: >> Package: sponsorship-requests >> Severity: wishlist >> >> Dear mentors, >> >> I am looking for a sponsor for my package "jgmenu": >> >>* Package name: jgmenu >> Version : 4.3.0-1 >> Upstream Author : Johan Malm >>* URL : https://jgmenu.github.io/ >>* License : LGPL-2+, GPL-2+, Expat, LGPL-3+ >>* Vcs : https://github.com/mati75/jgmenu >> Section : x11 >> >> It builds those binary packages: >> >> jgmenu-xfce4-panel-applet - xfce4-panel applet for jgmenu >> jgmenu - Simple X11 menu >> >> To access further information about this package, please visit the > following URL: >> >> https://mentors.debian.net/package/jgmenu/ >> >> Alternatively, one can download the package with dget using this > command: >> >> dget -x > https://mentors.debian.net/debian/pool/main/j/jgmenu/jgmenu_4.3.0-1.dsc >> >> Changes for the initial release: >> >>jgmenu (4.3.0-1) unstable; urgency=medium >>. >> * Initial release. (Closes: #882210) > > > One major problem: debian/copyright in your work says that the whole > project is licensed under GPL-2+, however the LICENSE file from > upstream only gives GPLv2 license text. The README file also does not > mention that the whole project is licensed under GPLv2 **or later**. > > Could you please contact upstream to clarify the case? The best output > would be adding a "the whole project is licensed under GPLv2 or later" > sentense in the README file, which would make things clear to everyone. > > P.S. I took a look at upstream's debian/copyright file at > https://github.com/johanmalm/jgmenu/blob/master/debian/copyright , in > which the upstream only mentioned GPL-2, not GPL-2+. If upstream is > only willing to release the whole project under GPL-2-only, using GPL- > 2+ is wrong and must be fixed. > > -- > Thanks, > Boyuan Yang
Bug#981065: RFP: gede -- Graphical frontend to GDB
Package: wnpp Severity: wishlist Gede is a graphical frontend (GUI) to GDB written in C++ and using the Qt5 or Qt4 toolkit. Licensed according to the BSD license. Downloadable from http://gede.dexar.se. Files for creating a deb is included in the source.
Bug#980818: RFS: targetd/0.9.1-1 [ITP] -- remote configuration of a LIO-based storage appliance
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "targetd": * Package name: targetd Version : 0.9.1-1 Upstream Author : Tony Asleson * URL : https://github.com/open-iscsi/targetd * License : GPL-3.0+ * Vcs : https://salsa.debian.org/python-team/applications/targetd Section : net It builds those binary packages: targetd - remote configuration of a LIO-based storage appliance To access further information about this package, please visit the following URL: https://mentors.debian.net/package/targetd/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/t/targetd/targetd_0.9.1-1.dsc Changes for the initial release: targetd (0.9.1-1) UNRELEASED; urgency=medium . * Initial release (Closes: #968297). Special notes to the person that’ll review my package: * I’ve created the git repository at : https://salsa.debian.org/Arcaik/targetd * targetd won’t start if no password is set in the configuration, so I used debconf to ask the user for a password in the post install phase (falling back to generating a random one), but I’m not sure if I’m doing this correctly (I’m just running sed on the file). Regards. -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#968297: ITP: targetd -- remote configuration of a LIO-based storage appliance
retitle 968297 ITP: targetd -- remote configuration of a LIO-based storage appliance -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#977058: borgmatic FTBFS with pytest 6
This is probably fixed by upstream commit ea6cd53067[^1], but not yet released. I’ve pushed upstream version 1.5.12 to salsa, but I’m not sure what to do next. [^1]: https://projects.torsion.org/witten/borgmatic/commit/ea6cd53067435365a96786b006aec391714501c4 -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#847573: Fixed in testing
Fixed in testing but painfully broken in stable.
Bug#974768: handbrake: Saving custom presets in custom category is broken
Package: handbrake Version: 1.2.2+ds1-1 Severity: normal Creating a custom preset category in the GUI is not possible. Saving a new preset with the option "new category" enabled fails silently. Workaround: - Save a new preset in a default category like "General" - Close Handbrake - Open ~/.config/ghb/presets.json - There is a new second "General" category at the end of the file - Change the name to your prefered new custom categories name -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-12-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages handbrake depends on: ii libass9 1:0.14.0-2 ii libavcodec587:4.1.6-1~deb10u1 ii libavfilter77:4.1.6-1~deb10u1 ii libavformat58 7:4.1.6-1~deb10u1 ii libavutil56 7:4.1.6-1~deb10u1 ii libbluray2 1:1.1.0-1 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libdvdnav4 6.0.0-1 ii libdvdread4 6.0.1-1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-02.58.3-2+deb10u2 ii libgstreamer-plugins-base1.0-0 1.14.4-2 ii libgstreamer1.0-0 1.14.4-1 ii libgtk-3-0 3.24.5-1 ii libgudev-1.0-0 232-2 ii libjansson4 2.12-1 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libsamplerate0 0.1.9-2 ii libswresample3 7:4.1.6-1~deb10u1 ii libswscale5 7:4.1.6-1~deb10u1 ii libtheora0 1.1.1+dfsg.1-15 ii libvorbis0a 1.3.6-2 ii libvorbisenc2 1.3.6-2 ii libx264-155 2:0.155.2917+git0a84d98-2 ii libx265-165 2.9-4 ii libxml2 2.9.4+dfsg1-7+b3 Versions of packages handbrake recommends: ii gstreamer1.0-libav 1.15.0.1+git20180723+db823502-2 ii gstreamer1.0-pulseaudio 1.14.4-1 ii gstreamer1.0-x 1.14.4-2 handbrake suggests no packages. -- no debconf information
Bug#690945: hi
My greeting to you.I'm Nimia Johan ,i want to know if you have read my sent letter to you?.want to discuss something inportant with you and also kindly write to me to my Email for more discussion Best regards Nimia
Bug#966315: (Requesting sponsorship) Re: Bug#966315: ITP: age -- simple, modern and secure encryption tool
> Only thing I could find was this blog entry: > https://neilmadden.blog/2019/12/30/a-few-comments-on-age/ > > (After that I'm not really sure if age is ready for Debian…) > Filippo Valsorda replied to this post [^1] and while I’m not a security expert at all, I feel the main issue is not on age’s robustness, but more on what it should do or not do as a tool (e.g. providing sender authentication). > Are there other reviews on age? I’m not aware of any reviews/audit on age’s encryption. [^1]: https://groups.google.com/forum/#!msg/age-dev/r-gwwcN3L-0/EhEvUbG5AwAJ -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#969505: RFS: age/1.0.0~beta4-1 [ITP] -- simple, modern and secure encryption tool
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "age": * Package name: age Version : 1.0.0~beta4-1 Upstream Author : Filippo Valsorda * URL : https://github.com/FiloSottile/age * License : ISC, BSD-3-clause, Expat * Vcs : https://salsa.debian.org/go-team/packages/age Section : utils It builds those binary packages: age - simple, modern and secure encryption tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/age/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/a/age/age_1.0.0~beta4-1.dsc Changes for the initial release: age (1.0.0~beta4-1) UNRELEASED; urgency=medium . * Initial release (Closes: #966315). Regards, -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#969058: iptables in buster-backports requires netbase >= 6.0 which is not present in archive
>> this bug utterly hosed the systems i am working on (fortunately a dev >> network) >> > If in a rush, one could simply install netbase from testing. It should be a > simple operation. Or install a previous version that may still be in apt cache. > This costs thousand of €€€ (EURs) in engineering time. Would you volunteer to > do > all the work you are suggesting should be done? Or fund with money for other > folks to do so? > > Please, be mindful, Debian is a community project. People do work here mostly > on > a volunteer capacity. While I may understand your frustration, this kind of > yelling you are doing might destroy people's motivation in communities. Totally agree, and I wanted to thank you for the work you’re doing on backporting iptables, it’s appreciated and really helpful (for instance, without this I wouldn’t be able to run Kubernetes on Buster). >> This makes `iptables` un-upgradable on my system, and even worse, it >> lead to it being removed an I cannot install it anymore: >> > this is because the apt pin config you have for the package... The config > tells > apt to only install the package from buster-bpo, but that package is > uninstallable, therefore the deadlock. Am I doing something wrong here? I really need iptables to be installed from backports and this is the only way I found to do so (appart from running `apt install -t buster-backports iptables` by hand) -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#969058: iptables in buster-backports requires netbase >= 6.0 which is not present in archive
Package: iptables Version: 1.8.5-3~bpo10+1 Severity: grave Justification: renders package unusable Dear Maintainer, Commit d7ad2173[^1] was backported into the debian/buster-backports branch and the iptables package version 1.8.5-3~bpo10+1 was pushed to the buster-backports archive yesterday[^2], but netbase is not present in version >=6.0 in the archive. This makes `iptables` un-upgradable on my system, and even worse, it lead to it being removed an I cannot install it anymore: ``` Start-Date: 2020-08-26 19:32:52 Commandline: /usr/bin/apt-get --option=Dpkg::Options::=--force-confold --option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet dist-upgrade Upgrade: libip6tc2:amd64 (1.8.3-2~bpo10+1, 1.8.5-3~bpo10+1), libiptc0:amd64 (1.8.3-2~bpo10+1, 1.8.5-3~bpo10+1), libxtables12:amd64 (1.8.3-2~bpo10+1, 1.8.5-3~bpo10+1), libip4tc2:amd64 (1.8.3-2~bpo10+1, 1.8.5-3~bpo10+1) Remove: iptables:amd64 (1.8.3-2~bpo10+1), kubernetes-worker:amd64 (1.18.8-1), ufw:amd64 (0.36-1), docker-ce:amd64 (5:19.03.12~3-0~debian-buster) End-Date: 2020-08-26 19:32:56 ``` iptables is installed from buster-backports using the folowing preference configuration: ``` Package: iptables libiptc0 libnftnl11 libxtables12 Pin: release a=buster-backports Pin-Priority: 1001 ``` [^1]: https://salsa.debian.org/pkg-netfilter-team/pkg-iptables/-/commit/d7ad2173f0cd7d26d2ecf0b49d3708203973faf2 [^2]: https://salsa.debian.org/pkg-netfilter-team/pkg-iptables/-/commit/f9ad7966a634ec0700f81f19bfb03fdfa8a09cdd -- System Information: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-10-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages iptables depends on: ii libc62.28-10 ii libip4tc01.8.2-4 ii libip4tc21.8.5-3~bpo10+1 ii libip6tc01.8.2-4 ii libip6tc21.8.5-3~bpo10+1 ii libiptc0 1.8.5-3~bpo10+1 ii libmnl0 1.0.4-2 ii libnetfilter-conntrack3 1.0.7-1 ii libnfnetlink01.0.1-3+b1 ii libnftnl11 1.1.7-1~bpo10+1 ii libxtables12 1.8.5-3~bpo10+1 ii netbase 5.6 Versions of packages iptables recommends: pn nftables Versions of packages iptables suggests: pn firewalld ii kmod 26-1
Bug#968297: RFP: targetd -- remote configuration of a LIO-based storage appliance
Package: wnpp Severity: wishlist X-Debbugs-Cc: jfle...@arcaik.net, debian-pyt...@lists.debian.org * Package name: targetd Version : 0.8.12 Upstream Author : Tony Asleson * URL : https://github.com/open-iscsi/targetd/ * License : GPL-3.0-or-later Programming Lang: Python Description : remote configuration of a LIO-based storage appliance targetd turns Linux into a remotely-configurable storage appliance. It supports an HTTP/jsonrpc-2.0 interface to let a remote administrator allocate volumes from an LVM volume group, and export those volumes over iSCSI. This can be especially usefull in environment such as Kubernetes where storage is provisionned automatically.
Bug#968029: ITP: prometheus-exporter-exporter -- simple reverse proxy to other Prometheus exporters
Package: wnpp Severity: wishlist Owner: Johan Fleury X-Debbugs-Cc: debian-de...@lists.debian.org, jfle...@arcaik.net * Package name: prometheus-exporter-exporter Version : 0.4.0-1 Upstream Author : Tristan Colgate-McFarlane * URL : https://github.com/QubitProducts/exporter_exporter * License : Apache-2.0 Programming Lang: Golang Description : simple reverse proxy to other Prometheus exporters prometheus-exporter-exporter is intended as a single binary alternative to nginx/apache for use in environments where opening multiple TCP ports to all servers might be difficult (technically or politically).
Bug#966315: (Requesting sponsorship) Re: Bug#966315: ITP: age -- simple, modern and secure encryption tool
Hello. So, apart from the issue I reported in my previous message, I believe the package is ready to be included in Debian. If a kind member could help me get this “finalized” I’d be very happy :) -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#966315: RFP: age -- simple, modern and secure encryption tool with small explicit keys, no config options, and UNIX-style composability
retitle 966315 ITP: age -- simple, modern and secure encryption tool thanks I started working on this package and I put my changes on salsa[1]. I could use some help/review from the Golang team to solve these 3 errors reported by Lintian: * E: age: statically-linked-binary usr/bin/age-keygen * W: age: hardening-no-pie usr/bin/age * W: age: hardening-no-relro usr/bin/age I fixed this by overriding `dh_auto_build` in `d/rules`, but I’m not sure if that’s the correct way to do it: ``` override_dh_auto_build: dh_auto_build -O--builddirectory=_build -O--buildsystem=golang -- -buildmode=pie ``` [1] https://salsa.debian.org/Arcaik/age -- Johan Fleury signature.asc Description: OpenPGP digital signature
Bug#966315: RFP: age -- simple, modern and secure encryption tool with small explicit keys, no config options, and UNIX-style composability
Package: wnpp Severity: wishlist X-Debbugs-Cc: jfle...@arcaik.net * Package name: age Version : 1.0.0-beta4 Upstream Author : Filippo Valsorda * URL : https://github.com/FiloSottile/age * License : BSD-3-Clause Programming Lang: Golang Description : simple, modern and secure encryption tool with small explicit keys, no config options, and UNIX-style composability
Bug#965371: resolve: enable RES_TRUSTAD towards the 127.0.0.53 stub resolver
Package: systemd Version: 245.6-3 Severity: wishlist Tags: patch X-Debbugs-Cc: jfle...@arcaik.net Since glibc 2.31, the resolvers in /etc/resolve.conf are not trusted anymore and the AD flag is stripped from their responses. As systemd-resolved is listening on a loopback interface, the `trust-ad` option was added to its stub resolve.conf file by upstream commit a742f98[^1]. It would be great if this commit could be backported to systemd 245 in Sid, waiting for version 246 to be released by upstream. [^1]: https://github.com/systemd/systemd/commit/a742f9828ea73d9c2c9bafe701c10fe60f058012 -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.53-8 ii libapparmor1 2.13.4-3 ii libaudit11:2.8.5-3+b1 ii libblkid12.35.2-7 ii libc62.31-1 ii libcap2 1:2.36-1 ii libcrypt11:4.4.16-1 ii libcryptsetup12 2:2.3.3-1 ii libgcrypt20 1.8.6-2 ii libgnutls30 3.6.14-2+b1 ii libgpg-error01.38-2 ii libidn2-02.3.0-1 ii libip4tc21.8.5-2 ii libkmod2 27+20200310-2 ii liblz4-1 1.9.2-2 ii liblzma5 5.2.4-1+b1 ii libmount12.35.2-7 ii libpam0g 1.3.1-5 ii libpcre2-8-0 10.34-7 ii libseccomp2 2.4.3-1+b1 ii libselinux1 3.1-2 ii libsystemd0 245.6-3 ii mount2.35.2-7 ii systemd-timesyncd [time-daemon] 245.6-3 ii util-linux 2.35.2-7 Versions of packages systemd recommends: ii dbus 1.12.20-1 Versions of packages systemd suggests: ii policykit-10.105-28 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.137 ii libnss-systemd 245.6-3 ii libpam-systemd 245.6-3 ii udev 245.6-3 -- Configuration Files: /etc/systemd/resolved.conf changed [not included] -- no debconf information
Bug#960012: Info received ((No Subject))
I believe this is also the cause of issues with PrivateBin version 1.3 and higher. It is not possible to send or read a paste. Reading a paste will result in: ``` DOMException: "The operation failed for an operation-specific reason" privatebin.js:1240:25 decipher https://[PrivateBin Server]/js/privatebin.js?1.3.4:1240 ``` Version prior to 1.3 used JS libraries while newer version uses WebCrypto API and AES GCM. I suppose this is broken by the NSS 3.52 - Firefox 76 incompatibility. -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
Bug#960012: (No Subject)
merge 960012 959971 thanks signature.asc Description: OpenPGP digital signature
Bug#959971: jitsi: unable to hear or see other users in a room
Package: firefox Version: 76.0-2 Severity: important Hi. Since I upgraded to Firefox 76.0 on Debian Sid, I’m unable to hear or see other participants in a Jitsi Room (and they are unable to hear or see me). Other participants can hear each other perfectly fine. I’ve reproduced this behaviour on three different installation of Debian Sid and multiple Jitsi servers. I’ve also reproduced with my main Firefox profile as well as with a new, empty profile. I tested with some friends using Firefox 76.0 on Archlinux and they have no issue (apart that we can’t communicate together). I also tested with Jitsi on Android and with Chromium on Debian. None of these have issues. Regards. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox depends on: ii debianutils 4.9.1 ii fontconfig 2.13.1-4 ii libatk1.0-0 2.36.0-2 ii libc6 2.30-7 ii libcairo-gobject2 1.16.0-4 ii libcairo2 1.16.0-4 ii libdbus-1-3 1.12.16-2 ii libdbus-glib-1-20.110-5 ii libevent-2.1-7 2.1.11-stable-1 ii libffi7 3.3-4 ii libfontconfig1 2.13.1-4 ii libfreetype62.10.1-2 ii libgcc-s1 10-20200502-1 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-4 ii libglib2.0-02.64.2-1 ii libgtk-3-0 3.24.18-1 ii libnspr42:4.25-1 ii libnss3 2:3.52-1 ii libpango-1.0-0 1.44.7-4 ii libstdc++6 10-20200502-1 ii libvpx6 1.8.2-1 ii libx11-62:1.6.9-2+b1 ii libx11-xcb1 2:1.6.9-2+b1 ii libxcb-shm0 1.14-2 ii libxcb1 1.14-2 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext62:1.3.3-1+b2 ii libxfixes3 1:5.0.3-2 ii libxrender1 1:0.9.10-1 ii libxt6 1:1.1.5-1+b3 ii procps 2:3.3.16-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages firefox recommends: ii libavcodec58 7:4.2.2-1+b1 Versions of packages firefox suggests: pn fonts-lmodern pn fonts-stix | otf-stix ii libcanberra0 0.30-7 ii libgssapi-krb5-2 1.17-7 ii libgtk2.0-02.24.32-4 ii pulseaudio 13.0-5 -- no debconf information -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
Bug#958915: gnome-software: plugin appstream is disabled beacause /usr/share/appdata doesn’t exist
Package: gnome-software Version: 3.36.0-2 Severity: important Dear Maintainers, On a clean installation of Debian Sid with GNOME 3, I found myself unable to use `gnome-software` as Debian packages where not listed at all. It seems that gnome-software’s checks that `/usr/share/appdata` exists as a condition to enable the `appstream` plugin. At startup, gnome-software shows these logs: ``` 16:37:41:0068 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, desktop-menu-path, flatpak, hardcoded-blacklist, hardcoded-popular, modalias, packagekit-refine, rewrite-resource, odrs, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 16:37:41:0068 Gs disabled plugins: dpkg, dummy, repos, appstream ``` With option `--verbose` it also shows this log: ``` 16:34:31:0313 Gs disabling appstream as setup failed: Error opening directory ?/usr/share/appdata?: No such file or directory ``` I believe this check should either be removed or a package (either `gnome-software` or `appstream`) should create the `/usr/share/appdata`. --- -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-software depends on: ii appstream0.12.10-2 ii apt-config-icons 0.12.10-2 ii dconf-gsettings-backend [gsettings-backend] 0.36.0-1 ii gnome-software-common3.36.0-2 ii gsettings-desktop-schemas3.36.0-1 ii libappstream-glib8 0.7.17-1 ii libatk1.0-0 2.36.0-2 ii libc62.30-4 ii libcairo21.16.0-4 ii libfwupd21.3.9-4 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-4 ii libglib2.0-0 2.64.2-1 ii libgspell-1-21.8.3-1 ii libgtk-3-0 3.24.18-1 ii libgtk3-perl 0.037-1 ii libgudev-1.0-0 233-1 ii libjson-glib-1.0-0 1.4.4-2 ii libpackagekit-glib2-18 1.1.13-2+b1 ii libpolkit-gobject-1-00.105-26 ii libsoup2.4-1 2.70.0-1 ii libxmlb1 0.1.15-2 ii packagekit 1.1.13-2+b1 ii software-properties-gtk 0.96.20.2-2.1 Versions of packages gnome-software recommends: ii fwupd 1.3.9-4 Versions of packages gnome-software suggests: pn apt-config-icons-hidpi ii gnome-software-plugin-flatpak 3.36.0-2 pn gnome-software-plugin-snap -- no debconf information -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
Bug#958832: RFP: firmware-sof -- open source audio Digital Signal Processing (DSP) firmware infrastructure and SDK
Package: wnpp Severity: wishlist * Package name: firmware-sof Version : 1.4.2 Upstream Author : Multiple Authors * URL : https://www.sofproject.org/ https://thesofproject.github.io/ https://github.com/thesofproject/sof * License : BSD, ISC Programming Lang: C Description : open source audio Digital Signal Processing (DSP) firmware infrastructure and SDK --- I am the owner of a 7th generation Thinkpad X1 Carbon on which there are a lot of audio has a lot of problem (for instance on kernel 5.5, sound card is not even detected by alsa). Most of the online forums and wiki (the Arch Linux wiki for instance [1]) tell the users to install firmware files directly from the sofproject's Github repository to fix those issues. I believe it would be better if one could install theses firmware directly from the Debian repositories. [1] https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Carbon_(Gen_7)#Audio -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
Bug#955405: ruby-thor: superclass mismatch for class Command
Package: ruby-thor Version: 0.19.4-1 Severity: normal Dear Maintainer, When I update my rails project thor from `0.20.3` to `1.0.0` or `1.0.1` I cannot run tests anymore. It gives me this trackback: ``` Traceback (most recent call last): 82: from bin/rails:4:in `' 81: from ~/vendor/bundle/ruby/2.5.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `require' 80: from ~/vendor/bundle/ruby/2.5.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:291:in `load_dependency' 79: from ~/vendor/bundle/ruby/2.5.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `block in require' 78: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require' 77: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi' 76: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register' 75: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi' 74: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require' 73: from ~/vendor/bundle/ruby/2.5.0/gems/railties-6.0.2.2/lib/rails/commands.rb:18:in `' 72: from ~/vendor/bundle/ruby/2.5.0/gems/railties-6.0.2.2/lib/rails/command.rb:46:in `invoke' 71: from ~/vendor/bundle/ruby/2.5.0/gems/railties-6.0.2.2/lib/rails/command/base.rb:69:in `perform' 70: from /usr/lib/ruby/vendor_ruby/thor.rb:369:in `dispatch' 69: from /usr/lib/ruby/vendor_ruby/thor/invocation.rb:126:in `invoke_command' 68: from /usr/lib/ruby/vendor_ruby/thor/command.rb:27:in `run' 67: from ~/vendor/bundle/ruby/2.5.0/gems/railties-6.0.2.2/lib/rails/commands/test/test_command.rb:33:in `perform' 66: from ~/vendor/bundle/ruby/2.5.0/gems/railties-6.0.2.2/lib/rails/test_unit/runner.rb:39:in `run' 65: from ~/vendor/bundle/ruby/2.5.0/gems/railties-6.0.2.2/lib/rails/test_unit/runner.rb:50:in `load_tests' 64: from ~/vendor/bundle/ruby/2.5.0/gems/railties-6.0.2.2/lib/rails/test_unit/runner.rb:50:in `each' 63: from ~/vendor/bundle/ruby/2.5.0/gems/railties-6.0.2.2/lib/rails/test_unit/runner.rb:50:in `block in load_tests' 62: from ~/vendor/bundle/ruby/2.5.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `require' 61: from ~/vendor/bundle/ruby/2.5.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:291:in `load_dependency' 60: from ~/vendor/bundle/ruby/2.5.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `block in require' 59: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require' 58: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi' 57: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register' 56: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi' 55: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require' 54: from ~/test/controllers/fonts_controller_test.rb:1:in `' 53: from ~/vendor/bundle/ruby/2.5.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `require' 52: from ~/vendor/bundle/ruby/2.5.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:291:in `load_dependency' 51: from ~/vendor/bundle/ruby/2.5.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `block in require' 50: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require' 49: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi' 48: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register' 47: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi' 46: from ~/vendor/bundle/ruby/2.5.0/gems/bootsnap-1.4.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require' 45: from ~/test/test_helper.rb:4:in `' 44: from ~/vendor/bundle/ruby/2.5.0/gems/zeitwerk-2.3.0/lib/zeitwerk/kernel.rb:23:in
Bug#953176: cups-daemon: cupsd with socket-activation removes /run/cups/cups.sock on exit
Package: cups-daemon Version: 2.2.10-6+deb10u2 Severity: important Dear Maintainer, systemd creates /run/cups/cups.sock on boot and as soon as anything connects to it (by e.g. lpstat), cupsd -l starts as expected. There are no shared printers on the system and the web interface is not running, so cupsd will eventually exit. When it does, I find it will unlink /run/cups/cups.sock (seen by strace on the running cupsd process), which causes subsequent invocations of lpstat to fail with "Bad file descriptor". cupsd did not remove the socket in Stretch, but in Buster it does. -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cups-daemon depends on: ii adduser 3.118 ii bc1.07.1-2+b1 ii libavahi-client3 0.7-4+b1 ii libavahi-common3 0.7-4+b1 ii libc6 2.28-10 ii libcups2 2.2.10-6+deb10u2 ii libdbus-1-3 1.12.16-1 ii libgssapi-krb5-2 1.17-3 ii libpam0g 1.3.1-5 ii libpaper1 1.1.28 ii libsystemd0 241-7~deb10u3 ii lsb-base 10.2019051400 ii procps2:3.3.15-2 ii ssl-cert 1.0.39 Versions of packages cups-daemon recommends: ii avahi-daemon 0.7-4+b1 ii colord1.4.3-4 pn cups-browsed Versions of packages cups-daemon suggests: ii cups 2.2.10-6+deb10u2 ii cups-bsd 2.2.10-6+deb10u2 ii cups-client2.2.10-6+deb10u2 ii cups-common2.2.10-6+deb10u2 ii cups-filters [foomatic-filters]1.21.6-5 pn cups-pdf ii cups-ppdc 2.2.10-6+deb10u2 ii cups-server-common 2.2.10-6+deb10u2 pn foomatic-db-compressed-ppds | foomatic-db ii ghostscript9.27~dfsg-2+deb10u3 pn hplip ii poppler-utils 0.71.0-5 ii printer-driver-gutenprint 5.3.1-7 ii printer-driver-hpcups 3.18.12+dfsg0-2 pn smbclient ii udev 241-7~deb10u3 -- no debconf information
Bug#851639: ITP: alacritty -- A cross-platform, GPU-accelerated terminal emulator
Hi Félix. I’m not really into Rust nor Rust packaging in Debian, could you elaborate a bit more on why Debian requires Alacritty to be hosted on crates.io? According to the discussion in alacritty#357 [1], upstream can’t or won't publish to crates.io. It seems that there hasn't been any progress on this RFP/ITP since 2017, is there any way one can help (I couldn't find any repo on salsa)? [1] https://github.com/jwilm/alacritty/issues/357 -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
Bug#948346: xdm gets killed, but only on sunday, on the first startup (code=killed, signal=USR2)
Package: xdm Version: 1:1.1.11-3+b1 Severity: important Dear Maintainer, xdm gets killed on sundays at startup time. It only happens once on sunday. When I delete /var/lib/xdm.pid I can proceed with a xdm restart without any problem. This is what systemd (systemctl status and journalctl -u xdm.service) reports: ● xdm.service - X-Window Display Manager Loaded: loaded (/lib/systemd/system/xdm.service; indirect; vendor preset: enabled) Active: failed (Result: signal) since Sun 2020-01-05 08:30:37 CET; 1min 45s ago Process: 673 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/xdm" ] (code=exited, status=0/SUCCESS) Process: 676 ExecStart=/usr/bin/xdm -nodaemon (code=killed, signal=USR2) Main PID: 676 (code=killed, signal=USR2) Jan 05 08:30:31 msi systemd[1]: Starting X-Window Display Manager... Jan 05 08:30:31 msi systemd[1]: Started X-Window Display Manager. Jan 05 08:30:34 msi systemd[1]: xdm.service: Main process exited, code=killed, status=12/USR2 Jan 05 08:30:37 msi systemd[1]: xdm.service: Failed with result 'signal'. -- Logs begin at Sun 2020-01-05 08:30:25 CET, end at Sun 2020-01-05 08:31:56 CET. -- Jan 05 08:30:31 msi systemd[1]: Starting X-Window Display Manager... Jan 05 08:30:31 msi systemd[1]: Started X-Window Display Manager. Jan 05 08:30:34 msi systemd[1]: xdm.service: Main process exited, code=killed, status=12/USR2 Jan 05 08:30:37 msi systemd[1]: xdm.service: Failed with result 'signal'. I have no idea what causes the kill :( -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xdm depends on: ii cpp4:9.2.1-3.1 ii debconf [debconf-2.0] 1.5.73 ii libc6 2.29-3 ii libpam0g 1.3.1-5 ii libselinux13.0-1 ii libx11-6 2:1.6.8-1 ii libxau61:1.0.8-1+b2 ii libxaw72:1.0.13-1+b2 ii libxdmcp6 1:1.1.2-3 ii libxext6 2:1.3.3-1+b2 ii libxft22.3.2-2 ii libxinerama1 2:1.1.4-2 ii libxmu62:1.1.2-2+b3 ii libxpm41:3.5.12-1 ii libxrender11:0.9.10-1 ii libxt6 1:1.1.5-1+b3 ii lsb-base 11.1.0 ii procps 2:3.3.15-2+b1 ii x11-utils 7.7+4 ii x11-xserver-utils 7.7+8 xdm recommends no packages. xdm suggests no packages. -- Configuration Files: /etc/X11/xdm/Xresources changed: Xcursor.theme: whiteglass xlogin*login.translations: #override \ CtrlR: abort-display()\n\ F1: set-session-argument(failsafe) finish-field()\n\ Delete: delete-character()\n\ Left: move-backward-character()\n\ Right: move-forward-character()\n\ Home: move-to-begining()\n\ End: move-to-end()\n\ CtrlKP_Enter: set-session-argument(failsafe) finish-field()\n\ KP_Enter: set-session-argument() finish-field()\n\ CtrlReturn: set-session-argument(failsafe) finish-field()\n\ Return: set-session-argument() finish-field() xlogin*greeting: Welcome to CLIENTHOST xlogin*namePrompt: \040\040\040\040\040\040\040Login: xlogin*fail: Login incorrect or forbidden by policy xlogin*greetFont: -adobe-helvetica-bold-o-normal--24-240-75-75-p-138-iso8859-1 xlogin*font: -adobe-helvetica-medium-r-normal--18-180-75-75-p-98-iso8859-1 xlogin*promptFont: -adobe-helvetica-bold-r-normal--18-180-75-75-p-103-iso8859-1 xlogin*failFont: -adobe-helvetica-bold-r-normal--18-180-75-75-p-103-iso8859-1 xlogin*greetFace: Serif-24:bold:italic xlogin*face:Helvetica-18 xlogin*promptFace: Helvetica-18:bold xlogin*failFace:Helvetica-18:bold xlogin*greetFont: -adobe-helvetica-bold-o-normal--17-120-100-100-p-92-iso8859-1 xlogin*font: -adobe-helvetica-medium-r-normal--12-120-75-75-p-67-iso8859-1 xlogin*promptFont: -adobe-helvetica-bold-r-normal--12-120-75-75-p-70-iso8859-1 xlogin*failFont: -adobe-helvetica-bold-o-normal--14-140-75-75-p-82-iso8859-1 xlogin*greetFace: Serif-18:bold:italic xlogin*face:Helvetica-12 xlogin*promptFace: Helvetica-12:bold xlogin*failFace:Helvetica-14:bold xlogin*borderWidth: 1 xlogin*frameWidth: 5 xlogin*innerFramesWidth: 2 xlogin*shdColor: grey30 xlogin*hiColor: grey90 xlogin*background: grey !xlogin*foreground: darkgreen xlogin*greetColor: red3 xlogin*failColor: red *Foreground: black *Background: #f0 xlogin*borderWidth: 3 xlogin*frameWidth: 0 xlogin*innerFramesWidth: 1 xlogin*shdColor: black xlogin*hiColor: black xlogin*logoFileName: /usr/share/X11/xdm/pixmaps/debian.xpm xlogin*logoFileName: /usr/share/X11/xdm/pixmaps/debianbw.xpm
Bug#947349: qemu-system-gui: SDL GUI is missing?
Package: qemu-system-gui Version: 1:3.1+dfsg-8+deb10u3 Severity: wishlist Dear Maintainer, QEMU supports SDL GUI interface as well, in addition to GTK, but it seems that qemu-system-gui doesn't provide it. I've noticed that it sometimes works better than the GTK interface so it would be useful if Debian provided both interfaces. -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qemu-system-gui depends on: ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libepoxy0 1.5.3-0.1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-02.58.3-2+deb10u2 ii libgtk-3-0 3.24.5-1 ii libpulse0 12.2-4+deb10u1 ii libvte-2.91-0 0.54.2-2 ii libx11-62:1.6.7-1 qemu-system-gui recommends no packages. qemu-system-gui suggests no packages. -- no debconf information
Bug#946592: libreoffice-calc: [Wayland?] Insert/delete cells prompt doesn't always appear, Libreoffice freezes
Package: libreoffice-calc Version: 1:6.1.5-3+deb10u5 Followup-For: Bug #946592 Additional information: "Selecting" the invisible prompt using Alt+Tab, then using Alt+F4 seems to close it and Calc becomes responsive again. -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-calc depends on: ii coinor-libcbc3 2.9.9+repack1-1 ii coinor-libcoinmp1v5 1.8.3-2+b11 ii coinor-libcoinutils3v5 2.10.14+repack1-1 ii libatlas3-base [liblapack.so.3] 3.10.3-8 ii libblas3 [libblas.so.3] 3.8.0-2 ii libboost-filesystem1.67.01.67.0-13 ii libboost-iostreams1.67.0 1.67.0-13 ii libbz2-1.0 1.0.6-9.2~deb10u1 ii libc62.28-10 ii libetonyek-0.1-1 0.1.9-1 ii libgcc1 1:8.3.0-6 ii libicu63 63.1-6 ii liblapack3 [liblapack.so.3] 3.8.0-2 ii liblcms2-2 2.9-3 ii libmwaw-0.3-30.3.14-1 ii libodfgen-0.1-1 0.1.7-1 ii liborcus-0.14-0 0.14.1-6 ii libreoffice-base-core1:6.1.5-3+deb10u5 ii libreoffice-core 1:6.1.5-3+deb10u5 ii librevenge-0.0-0 0.0.4-6 ii libstaroffice-0.0-0 0.0.6-1 ii libstdc++6 8.3.0-6 ii libwps-0.4-4 0.4.10-1 ii libxml2 2.9.4+dfsg1-7+b3 ii lp-solve 5.5.0.15-4+b1 ii uno-libs36.1.5-3+deb10u5 ii ure 6.1.5-3+deb10u5 ii zlib1g 1:1.2.11.dfsg-1 libreoffice-calc recommends no packages. Versions of packages libreoffice-calc suggests: ii ocl-icd-libopencl1 2.2.12-2 Versions of packages libreoffice-core depends on: ii fontconfig2.13.1-2 ii fonts-opensymbol 2:102.10+LibO6.1.5-3+deb10u5 ii libboost-date-time1.67.0 1.67.0-13 ii libboost-locale1.67.0 1.67.0-13 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libclucene-contribs1v52.3.3.4+dfsg-1 ii libclucene-core1v52.3.3.4+dfsg-1 ii libcmis-0.5-5v5 0.5.2-1 ii libcups2 2.2.10-6+deb10u1 ii libcurl3-gnutls 7.64.0-4 ii libdbus-1-3 1.12.16-1 ii libdbus-glib-1-2 0.110-4 ii libdconf1 0.30.1-2 ii libeot0 0.01-5 ii libepoxy0 1.5.3-0.1 ii libexpat1 2.2.6-2+deb10u1 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig12.13.1-2 ii libfreetype6 2.9.1-3+deb10u1 ii libgcc1 1:8.3.0-6 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgpgmepp6 1.12.0-6 ii libgraphite2-31.3.13-7 ii libharfbuzz-icu0 2.3.1-1 ii libharfbuzz0b 2.3.1-1 ii libhunspell-1.7-0 1.7.0-2 ii libhyphen02.8.8-7 ii libice6 2:1.0.9-2 ii libicu63 63.1-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-22.9-3 ii libldap-2.4-2 2.4.47+dfsg-3+deb10u1 ii libmythes-1.2-0 2:1.2.4-3 ii libneon27-gnutls 0.30.2-3 ii libnspr4 2:4.20-1 ii libnss3 2:3.42.1-1+deb10u1 ii libnumbertext-1.0-0 1.0.5-1 ii libodfgen-0.1-1 0.1.7-1 ii liborcus-0.14-0 0.14.1-6 ii libpng16-16 1.6.36-6 ii libpoppler82 0.71.0-5 ii librdf0 1.0.17-1.1+b1 ii libreoffice-common1:6.1.5-3+deb10u5 ii librevenge-0.0-0 0.0.4-6 ii libsm62:1.2.3-1 ii libstdc++68.3.0-6 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.4-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libxmlsec11.2.27-2 ii libxmlsec1-nss1.2.27-2 ii libxrandr22:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.11.1.32-2.2~deb10u1 ii uno-libs3 6.1.5-3+deb10u5 ii ure 6.1.5-3+deb10u5 ii zlib1g1:1.2.11.dfsg-1 Versions of packages libreoffice-core recommends: ii libpaper-utils 1.1.28 -- no debconf information
Bug#946592: libreoffice-calc: [Wayland?] Insert/delete cells prompt doesn't always appear, Libreoffice freezes
Package: libreoffice-calc Version: 1:6.1.5-3+deb10u5 Severity: normal Dear Maintainer, This happens on KDE+Wayland, and I suspect that this might be a Wayland-related problem. Sometimes, when you choose some cells in Libreoffice Calc, then right click and choose "Insert..." or "Delete...", the popup that asks for insert/delete options (e.g. "shift cells up") does not appear, and this causes Calc to stop reacting to any user input. If you use Alt+Tab to cycle through open applications, you can see the "Insert (or Delete) cells" prompt there but you cannot select it. The only option to recover seems to be killing Libreoffice from console or via a process manager. -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libreoffice-calc depends on: ii coinor-libcbc3 2.9.9+repack1-1 ii coinor-libcoinmp1v5 1.8.3-2+b11 ii coinor-libcoinutils3v5 2.10.14+repack1-1 ii libatlas3-base [liblapack.so.3] 3.10.3-8 ii libblas3 [libblas.so.3] 3.8.0-2 ii libboost-filesystem1.67.01.67.0-13 ii libboost-iostreams1.67.0 1.67.0-13 ii libbz2-1.0 1.0.6-9.2~deb10u1 ii libc62.28-10 ii libetonyek-0.1-1 0.1.9-1 ii libgcc1 1:8.3.0-6 ii libicu63 63.1-6 ii liblapack3 [liblapack.so.3] 3.8.0-2 ii liblcms2-2 2.9-3 ii libmwaw-0.3-30.3.14-1 ii libodfgen-0.1-1 0.1.7-1 ii liborcus-0.14-0 0.14.1-6 ii libreoffice-base-core1:6.1.5-3+deb10u5 ii libreoffice-core 1:6.1.5-3+deb10u5 ii librevenge-0.0-0 0.0.4-6 ii libstaroffice-0.0-0 0.0.6-1 ii libstdc++6 8.3.0-6 ii libwps-0.4-4 0.4.10-1 ii libxml2 2.9.4+dfsg1-7+b3 ii lp-solve 5.5.0.15-4+b1 ii uno-libs36.1.5-3+deb10u5 ii ure 6.1.5-3+deb10u5 ii zlib1g 1:1.2.11.dfsg-1 libreoffice-calc recommends no packages. Versions of packages libreoffice-calc suggests: ii ocl-icd-libopencl1 2.2.12-2 Versions of packages libreoffice-core depends on: ii fontconfig2.13.1-2 ii fonts-opensymbol 2:102.10+LibO6.1.5-3+deb10u5 ii libboost-date-time1.67.0 1.67.0-13 ii libboost-locale1.67.0 1.67.0-13 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libclucene-contribs1v52.3.3.4+dfsg-1 ii libclucene-core1v52.3.3.4+dfsg-1 ii libcmis-0.5-5v5 0.5.2-1 ii libcups2 2.2.10-6+deb10u1 ii libcurl3-gnutls 7.64.0-4 ii libdbus-1-3 1.12.16-1 ii libdbus-glib-1-2 0.110-4 ii libdconf1 0.30.1-2 ii libeot0 0.01-5 ii libepoxy0 1.5.3-0.1 ii libexpat1 2.2.6-2+deb10u1 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig12.13.1-2 ii libfreetype6 2.9.1-3+deb10u1 ii libgcc1 1:8.3.0-6 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgpgmepp6 1.12.0-6 ii libgraphite2-31.3.13-7 ii libharfbuzz-icu0 2.3.1-1 ii libharfbuzz0b 2.3.1-1 ii libhunspell-1.7-0 1.7.0-2 ii libhyphen02.8.8-7 ii libice6 2:1.0.9-2 ii libicu63 63.1-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-22.9-3 ii libldap-2.4-2 2.4.47+dfsg-3+deb10u1 ii libmythes-1.2-0 2:1.2.4-3 ii libneon27-gnutls 0.30.2-3 ii libnspr4 2:4.20-1 ii libnss3 2:3.42.1-1+deb10u1 ii libnumbertext-1.0-0 1.0.5-1 ii libodfgen-0.1-1 0.1.7-1 ii liborcus-0.14-0 0.14.1-6 ii libpng16-16 1.6.36-6 ii libpoppler82 0.71.0-5 ii librdf0 1.0.17-1.1+b1 ii libreoffice-common1:6.1.5-3+deb10u5 ii librevenge-0.0-0 0.0.4-6 ii libsm62:1.2.3-1 ii libstdc++68.3.0-6 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.4-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libxmlsec11.2.27-2 ii libxmlsec1-nss1.2.27-2 ii libxrandr22:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.11.1.32-2.2~deb10u1 ii uno-libs3
Bug#945161: accountwizard: Broken dependencies (KLineEdit)
Package: accountwizard Version: 4:18.08.3-3 Severity: normal Dear Maintainer, The accountwizard tries to instantiate widgets that are not installed when I try to setup a Kolab client, so this seems to be a dependency issue. The output from the program is: $ accountwizard org.kde.knewstuff.core: Using a deprecated location for the knsrc file "accountwizard.knsrc" - please contact the author of the software which provides th "QFormBuilder was unable to create a widget of the class 'KLineEdit'." "Empty widget item in QFormLayout 'formLayout'." "QFormBuilder was unable to create a widget of the class 'KLineEdit'." "Empty widget item in QFormLayout 'formLayout'." "QFormBuilder was unable to create a custom widget of the class 'KPasswordLineEdit'; defaulting to base class 'QWidget'." Kross: "Error error=TypeError: Result of expression 'page.widget().nameEdit' [undefined] is not an object. lineno=27 trace=\n() at /usr/share/akona This means that I cannot enter the name, nor the password, due to the widgets not being properly instantiated. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8), LANGUAGE=en_US:en (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages accountwizard depends on: ii kio 5.62.1-2 ii libc6 2.29-3 ii libgcc1 1:9.2.1-19 ii libgpgmepp6 1.13.1-1 ii libkf5akonadicore5abi2 [libkf5akonadicore5-18.08] 4:18.08.3-11 ii libkf5akonadimime5 [libkf5akonadimime5-18.08] 4:18.08.3-3 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-18.08] 4:18.08.3-11 ii libkf5codecs5 5.62.0-1 ii libkf5configcore5 5.62.0-1 ii libkf5coreaddons5 5.62.0-1 ii libkf5crash5 5.62.0-1 ii libkf5dbusaddons5 5.62.0-1 ii libkf5i18n5 5.62.0-1 ii libkf5identitymanagement5 [libkf5identitymanagement5-18.08] 18.08.3-4 ii libkf5itemviews5 5.62.0-1 ii libkf5kcmutils5 5.62.0-1 ii libkf5kiocore55.62.1-2 ii libkf5krosscore5 5.62.0-1 ii libkf5ldap5abi1 [libkf5ldap5-18.08] 18.08.3-3 ii libkf5libkdepim5 [libkf5libkdepim5-18.08] 4:18.08.3-4 ii libkf5libkleo5 [libkf5libkleo5-18.08] 4:18.08.3-4 ii libkf5mailtransport5 [libkf5mailtransport5-18.08] 18.08.3-4 ii libkf5mailtransportakonadi5 [libkf5mailtransportakonadi5-18. 18.08.3-4 ii libkf5mime5abi1 [libkf5mime5-18.08] 18.08.3-3 ii libkf5newstuffcore5 5.62.0-1 ii libkf5notifications5 5.62.0-1 ii libkf5pimcommon5abi2 [libkf5pimcommon5-18.08] 4:18.08.3-4 ii libkf5wallet-bin 5.62.0-1 ii libkf5wallet5 5.62.0-1 ii libkf5widgetsaddons5 5.62.0-1 ii libkf5xmlgui5 5.62.0-1+b1 ii libqgpgme71.13.1-1 ii libqt5core5a 5.12.5+dfsg-2 ii libqt5dbus5 5.12.5+dfsg-2 ii libqt5gui55.12.5+dfsg-2 ii libqt5widgets55.12.5+dfsg-2 ii libqt5xml55.12.5+dfsg-2 ii libstdc++69.2.1-19 accountwizard recommends no packages. accountwizard suggests no packages.
Bug#944452: qemu-system-gui: Error 'GLSL ES 3.00 is not supported' when using -vga virtio and -display gtk,gl=on
Package: qemu-system-gui Version: 1:3.1+dfsg-8+deb10u2 Severity: normal Dear Maintainer, I tried to use virtio as the virtual GPU and I set OpenGL on for the GUI by using "-display gtk,gl=on". However, Qemu didn't start properly. Instead, it gave the error messages shown below. Using "-display sdl[,gl=on]" doesn't work at all. It says "Display 'sdl' is not available." qemu_gl_create_compile_shader: compile vertex error 0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES qemu_gl_create_compile_shader: compile fragment error 0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES qemu_gl_create_compile_shader: compile vertex error 0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES qemu_gl_create_compile_shader: compile fragment error 0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qemu-system-gui depends on: ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libepoxy0 1.5.3-0.1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-02.58.3-2+deb10u1 ii libgtk-3-0 3.24.5-1 ii libpulse0 12.2-4+deb10u1 ii libvte-2.91-0 0.54.2-2 ii libx11-62:1.6.7-1 qemu-system-gui recommends no packages. qemu-system-gui suggests no packages. -- no debconf information
Bug#944035: RFP: moar -- Easy text file viewer / pager similar to less
Package: wnpp Severity: wishlist * Package name: moar Version : 0.9.9 Upstream Author : Johan Walles * URL : https://github.com/walles/moar * License : BSD-2-Clause Programming Lang: Go Description : Easy text file viewer / pager similar to less Moar is a text file viewer / pager designed to be nice out of the box. Related features: * Syntax highlight source code by default if Highlight is installed. * Search is incremental / find-as-you-type just like in Chrome or Emacs * Search becomes case sensitive if you add any UPPER CASE characters to your search terms, just like in Emacs * Regexp search if your search string is a valid regexp * Displays ANSI color coded texts (like the output from git diff for example) * Displays man pages * Supports UTF-8 input and output * The position in the file is always shown Also, for compatibility reasons, moar uses the formats declared in these environment variables when viewing man pages: * LESS_TERMCAP_md: ANSI escape sequence for bold text * LESS_TERMCAP_us: ANSI escape sequence for underlined text
Bug#942068: openvpn-systemd-resolved: missing script for update-systemd-resolved
Yes this solved my warnings. Should this be done by the package? Just from a upgrade perspective for other users.
Bug#942068: openvpn-systemd-resolved: missing script for update-systemd-resolved
Hi Eugene, Thanks for the quick reply. I imported a ovpn file but not to my knowledge I configured the path. Also when I look in the network manager of the VPN tools I can't find anything related to this. But when I look at the file: /etc/openvpn/update-systemd-resolved.conf That was installed by package openvpn-systemd-resolved it contains the script path. Here is the output of the file that was installed: #/etc/openvpn/update-systemd-resolved.conf: script-security 2 setenv PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin up /etc/openvpn/scripts/update-systemd-resolved up-restart down /etc/openvpn/scripts/update-systemd-resolved down-pre Is this a package error or a configuration error of the file? Thanks, Johan -Oorspronkelijk bericht- Van: Eugene Zhukov Aan: Johan Smits , 942...@bugs.debian.org Onderwerp: Bug#942068: openvpn-systemd-resolved: missing script for update-systemd-resolved Datum: Thu, 10 Oct 2019 09:43:04 +0300 Thank you for the bug report, Johan. Could there be something with the configuration on your side? update-systemd-resolved is installed under /etc/openvpn not /etc/openvpn/scripts Thanks, Eugene
Bug#942068: openvpn-systemd-resolved: missing script for update-systemd-resolved
Package: openvpn-systemd-resolved Version: 1.3.0-3 Severity: normal Dear Maintainer, When I check the journal log I see a lot of errors. It seems like there is a file missing to start the VPN. But when I start the VPN all works normal (my vpn also uses the same public dns services) okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: Service RestartSec=5s expired, scheduling restart. okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: Scheduled restart job, restart counter is at 1207. okt 09 21:08:37 laptop systemd[1]: Stopped OpenVPN connection to update-systemd-resolved. okt 09 21:08:37 laptop systemd[1]: Starting OpenVPN connection to update-systemd-resolved... okt 09 21:08:37 laptop ovpn-update-systemd-resolved[20604]: Options error: --up script fails with '/etc/openvpn/scripts/update-systemd-resolved': No such file or directory (errno=2) okt 09 21:08:37 laptop ovpn-update-systemd-resolved[20604]: Options error: Please correct this error. okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE okt 09 21:08:37 laptop ovpn-update-systemd-resolved[20604]: Use --help for more information. okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: Failed with result 'exit-code'. okt 09 21:08:37 laptop systemd[1]: Failed to start OpenVPN connection to update-systemd-resolved. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openvpn-systemd-resolved depends on: ii libnss-resolve 242-7 ii openvpn 2.4.7-1 ii systemd 242-7 openvpn-systemd-resolved recommends no packages. openvpn-systemd-resolved suggests no packages. -- no debconf information
Bug#940849: tilix: Undefined symbol: _D4glib1c5types__T6ScopedTC3gio22ApplicationCommandLineQyZQBo6__dtorMFZv
Package: tilix Version: 1.8.9-1 Severity: important Dear Maintainer, Updating to the latest version of tilix it is not possible to start Tilix. `$ tilix: symbol lookup error: tilix: undefined symbol: _D4glib1c5types__T6ScopedTC3gio22ApplicationCommandLineQyZQBo6__dtorMFZ v` There is also a github issue: https://github.com/gnunn1/tilix/issues/1756 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tilix depends on: ii dconf-gsettings-backend [gsettings-backend] 0.34.0-1 ii libc62.29-1 ii libgcc1 1:9.2.1-8 ii libgtkd-3-0 3.8.5-1+b2 ii libphobos2-ldc-shared82 1:1.12.0-1+b1 ii libvted-3-0 3.8.5-1+b2 ii libx11-6 2:1.6.7-1 ii tilix-common 1.8.9-1 tilix recommends no packages. Versions of packages tilix suggests: pn python-nautilus -- no debconf information
Bug#936768: jpylyzer: Python2 removal in sid/bullseye
FWIW, the upstream jpylyzer source code (of which I'm the maintainer) is already fully compatible with Python 3 (and has been since the first jpylyzer release in 2011). If there are any Python 2 dependencies, they are only in the current packaging (which I think should be easy to fix, but I'm not that familiar with the package-specific code). Also, a new jpylyzer release is scheduled for late November. As this will be a 2.0 release with some breaking changes in the output format (relative to the 1.x releases), some users may want to stick to the 1.18 release for a while. Because of this I think it would be a good idea to fix the packaging for the current 1.18 release.
Bug#935726: kvirc: Crash on startup when Wayland is used
Package: kvirc Version: 4:5.0.0+dfsg-1 Severity: important Dear Maintainer, When starting KVirc on KDE desktop + Wayland, it crashes. This happens every time. The KDE crash reporter gave the following information. Application: KVIrc (kvirc), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9fc43435c0 (LWP 1303))] Thread 3 (Thread 0x7f9fc21c9700 (LWP 1306)): #0 0x7f9fcac2e819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f9fc85ad136 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9fc85ad25c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9fcb2dd87b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9fcb28b27b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9fcb0daec6 in QThread::exec() () from /usr/lib/x86_64-linux- gnu/libQt5Core.so.5 #6 0x7f9fcefed545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f9fcb0e4aa7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9fcfb82fa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #9 0x7f9fcac394cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f9fc433c700 (LWP 1305)): #0 0x7f9fcfb8900c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f9fcaf543bc in std::condition_variable::wait(std::unique_lock&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #2 0x7f9fce4ec542 in ?? () from /usr/lib/x86_64-linux- gnu/libQt5WebKit.so.5 #3 0x7f9fce4ec659 in ?? () from /usr/lib/x86_64-linux- gnu/libQt5WebKit.so.5 #4 0x7f9fcaf59b2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x7f9fcfb82fa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #6 0x7f9fcac394cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f9fc43435c0 (LWP 1303)): [KCrash Handler] #6 0x7f9fcf6d761c in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #7 0x7f9fcf6d7b1a in XInternAtom () from /usr/lib/x86_64-linux- gnu/libX11.so.6 #8 0x5611251cef0b in ?? () #9 0x5611251cf007 in ?? () #10 0x561124ff1f0f in ?? () #11 0x7f9fcab6409b in __libc_start_main () from /lib/x86_64-linux- gnu/libc.so.6 #12 0x56112500196a in _start () [Inferior 1 (process 1303) detached] -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kvirc depends on: ii kvirc-data4:5.0.0+dfsg-1 ii kvirc-modules 4:5.0.0+dfsg-1 ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libkf5configcore5 5.54.0-1+deb10u1 ii libkf5coreaddons5 5.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5notifications5 5.54.0-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5windowsystem5 5.54.0-1 ii libkf5xmlgui5 5.54.0-1 ii libkvilib54:5.0.0+dfsg-1 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus5 5.11.3+dfsg1-1 ii libqt5gui55.11.3+dfsg1-1 ii libqt5network55.11.3+dfsg1-1 ii libqt5webkit5 5.212.0~alpha2-21 ii libqt5widgets55.11.3+dfsg1-1 ii libqt5x11extras5 5.11.3-2 ii libssl1.1 1.1.1c-1 ii libstdc++68.3.0-6 ii libx11-6 2:1.6.7-1 ii zlib1g1:1.2.11.dfsg-1 kvirc recommends no packages. kvirc suggests no packages. -- no debconf information
Bug#934122: borgmatic: "validate-borgmatic-config" is not found
Hi Julian. This command was introduced in upstream version 1.3.3 of borgmatic which was released 3 months ago. Upstream released quite a few versions since I first packaged borgmatic. I'll try to package the latest release as soon as possible (maybe this week, but can't promise I'll have time). Thank you for reporting this.
Bug#933464: saga: Please rebuild against wxWidgets GTK 3 package
FYI. I've done some testing and didn't see any issues when using the wxWidgets GTK3 build.
Bug#933253: systemsettings: Crash when opening Keyboard and input devices -> Mouse if Wayland is used and no mouse is connected
Package: systemsettings Version: 4:5.14.5-1.1 Severity: normal Dear Maintainer, Opening Mouse settings under keyboard and input devices causes systemsettings5 to crash when Wayland is used and no mouse is connected (only laptop touchpad and trackpoint are used). The KDE crash report application gave the following information: Application: Järjestelmäasetukset (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc854a25cc0 (LWP 1029))] Thread 6 (Thread 0x7fc8377fe700 (LWP 1046)): [KCrash Handler] #6 0x7fc858915f6c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fc858911194 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fc858a48f73 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fc858a4fa0c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fc858a46b7c in QQmlDataBlob::tryDone() () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fc858a46dde in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () from /usr/lib/x86_64-linux- gnu/libQt5Qml.so.5 #12 0x7fc858a4753a in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7fc858a485e8 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7fc858a487ed in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7fc858ab7fb4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7fc858ab868a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7fc85a2664b1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fc85a26d950 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fc8598515a9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fc85985459b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fc8598a3233 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fc856fa5f2e in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fc856fa61c8 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fc856fa625c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7fc8598a2863 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7fc85985027b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fc85969fec6 in QThread::exec() () from /usr/lib/x86_64-linux- gnu/libQt5Core.so.5 #28 0x7fc858ab7c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7fc8596a9aa7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7fc857c43fa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #31 0x7fc85939b4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7fc8435ef700 (LWP 1034)): #0 0x7fc859390819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fc856fa6136 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc856fa625c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc8598a287b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc85985027b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc85969fec6 in QThread::exec() () from /usr/lib/x86_64-linux- gnu/libQt5Core.so.5 #6 0x7fc858ab7c65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fc8596a9aa7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc857c43fa3 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #9 0x7fc85939b4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7fc849dc6700 (LWP 1033)): #0 0x7fff8e5a1a21 in clock_gettime () #1 0x7fc8593a8ff6 in clock_gettime () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7fc8598a21a1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fc8598a09d9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc8598a0fd5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc8598a25fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc856fa5669 in g_main_context_prepare () from /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0 #7 0x7fc856fa606b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fc856fa625c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fc8598a287b in
Bug#818366: synaptic: fails to start under Wayland
Package: synaptic Version: 0.84.6 Followup-For: Bug #818366 Dear Maintainer, I can confirm this on Buster. If Synaptic is started from KDE applications menu when using Wayland, it does not ask for root privileges but starts without privileges instead. It is not very useful in that state. If I try to start Synaptic from the console by issuing "sudo synaptic", it doesn't start at all. It gives this error message: " No protocol specified Unable to init server: Yhdistäminen ei onnistunut:Yhteys torjuttu Failed to initialize GTK. Probably you're running Synaptic on Wayland with root permission. Please restart your session without Wayland, or run Synaptic without root permission " -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages synaptic depends on: ii hicolor-icon-theme 0.17-2 ii libapt-inst2.0 1.8.2 ii libapt-pkg5.01.8.2 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libept1.5.0 1.1+nmu3+b1 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2 ii libgnutls30 3.6.7-4 ii libgtk-3-0 3.24.5-1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpcre2-8-0 10.32-5 ii libstdc++6 8.3.0-6 ii libvte-2.91-00.54.2-2 ii libx11-6 2:1.6.7-1 ii libxapian30 1.4.11-1 ii policykit-1 0.105-25 ii zenity 3.30.0-2 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages synaptic recommends: ii libgtk2-perl 2:1.24992-1+b2 ii xdg-utils 1.1.3-1 Versions of packages synaptic suggests: pn apt-xapian-index pn deborphan pn dwww pn menu pn software-properties-gtk ii tasksel 3.53 -- no debconf information
Bug#932389: gnome-sound-recorder crashes when trying to play back a recording
Package: gnome-sound-recorder Version: 3.28.2-1 Severity: important Crashes with: ** (org.gnome.SoundRecorder:12342): CRITICAL **: 19:04:35.810: g_object_info_get_n_fields: assertion 'info != NULL' failed ** Gjs:ERROR:gi/object.cpp:481:bool ObjectInstance::field_getter_impl(JSContext*, JS::HandleObject, JS::HandleString, JS::MutableHandleValue): assertion failed: (field) Playing back a recording is not possible. Pretty embarrassing for a program which has two functions and a default workflow which involves these two functions... -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-sound-recorder depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii gir1.2-gdkpixbuf-2.0 2.38.1+dfsg-1 ii gir1.2-glib-2.0 1.58.3-2 ii gir1.2-gst-plugins-base-1.0 1.14.4-2 ii gir1.2-gstreamer-1.0 1.14.4-1 ii gir1.2-gtk-3.0 3.24.5-1 ii gir1.2-pango-1.0 1.42.4-6 ii gjs 1.54.3-1 ii gstreamer1.0-plugins-base1.14.4-2 ii gstreamer1.0-plugins-good1.14.4-1 ii gstreamer1.0-pulseaudio 1.14.4-1 gnome-sound-recorder recommends no packages. gnome-sound-recorder suggests no packages. -- no debconf information
Bug#932372: libsdl1.2-dev is not multiarch-compatible?
Package: libsdl1.2-dev Version: 1.2.15+dfsg2-4 Severity: normal Dear Maintainer, I tried to install libsdl1.2-dev:i386 on a 64-bit system in order to compile 32-bit versions of some software, but it would require removing these packages libcaca-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-net1.2-dev libsdl- sound1.2-dev libsdl1.2-dev and this is obviously not desirable. So unless I'm doing something wrong, libsdl1.2-dev seems to be multiarch-incompatible. -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libsdl1.2-dev depends on: ii libasound2-dev 1.1.8-1 ii libcaca-dev0.99.beta19-2.1 ii libglu1-mesa-dev [libglu-dev] 9.0.0-2.1+b3 ii libpulse-dev 12.2-4 ii libsdl1.2debian1.2.15+dfsg2-4 ii libx11-dev 2:1.6.7-1 ii libxext-dev2:1.3.3-1+b2 libsdl1.2-dev recommends no packages. libsdl1.2-dev suggests no packages. -- no debconf information
Bug#899377: xfce4-notifyd doesn't autostart with xfce session
Package: xfce4-notifyd Version: 0.4.3-1 Followup-For: Bug #899377 Dear Maintainer, I can confirm this on Buster. Also, I think the severity of this bug is more than normal because this causes major problems to many important desktop features such as NetworkManager and volume control. A workaround was provided on Xfce forums - add this command to the automatically started programs in the Session & Startup settings manager: systemctl --user start xfce4-notifyd -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages xfce4-notifyd depends on: ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libdbus-1-3 1.12.16-1 ii libdbus-glib-1-2 0.110-4 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2 ii libgtk-3-0 3.24.5-1 ii libnotify4 0.7.7-4 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libx11-6 2:1.6.7-1 ii libxfce4panel-2.0-4 4.12.2-1 ii libxfce4ui-2-0 4.12.1-3 ii libxfce4util74.12.1-3 ii libxfconf-0-24.12.1-1 Versions of packages xfce4-notifyd recommends: ii libnotify-bin 0.7.7-4 xfce4-notifyd suggests no packages. -- no debconf information
Bug#919102: reportbug: crash if fails to contact debian server
Package: reportbug
Version: 7.5.2
Followup-For: Bug #919102
Dear Maintainer,
I can confirm this with version 7.5.2. If there's no network connection,
reportbug will crash as described. I noticed this after upgrading to buster.
Crash information below.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in
_conn_request
conn.connect()
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 998, in
connect
address_info = socket.getaddrinfo(host, port, 0, socket.SOCK_STREAM)
File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Tilapäinen virhe nimenselvityksessä
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line 1049, in
sync_pre_operation
http_proxy=http_proxy, archived=archived, source=source)
File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 1069, in
get_reports
bugs = debianbts.get_bugs(pkg_filter, package)
File "/usr/lib/python3/dist-packages/debianbts/debianbts.py", line 401, in
get_bugs
reply = soap_client.call('get_bugs', method_el)
File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line 256, in
call
self.xml_response = self.send(method, self.xml_request)
File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line 318, in
send
location, http_method, body=xml, headers=headers)
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in
request
(response, content) = self._request(conn, authority, uri, request_uri,
method, body, headers, redirections, cachekey)
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in
_request
(response, content) = self._conn_request(conn, request_uri, method, body,
headers)
File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1193, in
_conn_request
raise ServerNotFoundError("Unable to find the server at %s" % conn.host)
httplib2.ServerNotFoundError: Unable to find the server at bugs.debian.org
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2285, in
main()
File "/usr/bin/reportbug", line 1115, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 1728, in user_interface
latest_first=self.options.latest_first)
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line 1763, in
func
args, kwargs = op.sync_pre_operation(*args, **kwargs)
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line 1051, in
sync_pre_operation
error_dialog("Unable to connect to %s BTS." % sysinfo['name'])
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line 137, in
error_dialog
_assert_context(ui_context)
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk_ui.py", line 92, in
_assert_context
(_describe_context(really), _describe_context(expected)))
AssertionError: Function should be called in
but was called in
-- Package-specific info:
** Environment settings:
INTERFACE="gtk"
** /home/username/.reportbugrc:
reportbug_version "7.1.7"
mode standard
ui gtk2
realname ***
email *
no-cc
header "X-Debbugs-CC: *"
smtphost reportbug.debian.org
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8),
LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages reportbug depends on:
ii apt1.8.2
ii python33.7.3-1
ii python3-reportbug 7.5.2
ii sensible-utils 0.0.12
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail
pn debconf-utils
pn debsums
pn dlocate
pn emacs24-bin-common | emacs25-bin-common
ii file 1:5.35-4
ii gnupg2.2.12-1
pn postfix | exim4 | mail-transport-agent
pn python3-urwid
pn reportbug-gtk
ii xdg-utils1.1.3-1
Versions of packages python3-reportbug depends on:
ii apt1.8.2
ii file 1:5.35-4
ii python33.7.3-1
ii python3-apt1.8.4
ii python3-debian 0.1.35
ii python3-debianbts 2.8.2
ii python3-requests 2.21.0-1
python3-reportbug suggests no packages.
Bug#931811: nut-client update returned error, required configuration change
Package: nut-client Version: 2.7.4-8 Severity: minor Dear Maintainer, When upgrading the system from Stretch to Buster, the final stage of updating nut-client failed. The output is shown below. As a workaround, I set MINSUPPLIES = 0 in /etc/nut/upsmon.conf which solved the problem. After upgrade, upsmon (nut-monitor.service) was enabled and running even though I had explicitly disabled it when I originally installed nut. Setting up nut-client (2.7.4-8) ... Job for nut-monitor.service failed because the control process exited with error code. See "systemctl status nut-monitor.service" and "journalctl -xe" for details. invoke-rc.d: initscript nut-client, action "restart" failed. ● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-07-09 23:05:52 EEST; 9ms ago Process: 6207 ExecStart=/sbin/upsmon (code=exited, status=1/FAILURE) july 09 23:05:52 hostname upsmon[6207]: fopen /var/run/nut/upsmon.pid: No such file or directory july 09 23:05:52 hostname upsmon[6207]: Using power down flag file /etc/killpower july 09 23:05:52 hostname upsmon[6207]: Network UPS Tools upsmon 2.7.4 july 09 23:05:52 hostname upsmon[6207]: Fatal error: insufficient power configured! july 09 23:05:52 hostname upsmon[6207]: Sum of power values: 0 july 09 23:05:52 hostname upsmon[6207]: Minimum value (MINSUPPLIES): 1 july 09 23:05:52 hostname upsmon[6207]: Edit your upsmon.conf and change the values. july 09 23:05:52 hostname systemd[1]: nut-monitor.service: Control process exited, code=exited, status=1/FAILURE july 09 23:05:52 hostname systemd[1]: nut-monitor.service: Failed with result 'exit-code'. july 09 23:05:52 hostname systemd[1]: Failed to start Network UPS Tools - power device monitor and shutdown controller. dpkg: error processing package nut-client (--configure): installed nut-client package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of nut: nut depends on nut-client; however: Package nut-client is not configured yet. dpkg: error processing package nut (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of nut-server: nut-server depends on nut-client (= 2.7.4-8); however: Package nut-client is not configured yet. dpkg: error processing package nut-server (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: nut-client nut nut-server E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nut-client depends on: ii adduser3.118 ii libc6 2.28-10 ii libupsclient4 2.7.4-8 ii lsb-base 10.2019051400 Versions of packages nut-client recommends: ii bash-completion 1:2.8-6 Versions of packages nut-client suggests: pn nut-monitor -- Configuration Files: /etc/nut/nut.conf [Errno 13] Lupa evätty: '/etc/nut/nut.conf' /etc/nut/upsmon.conf [Errno 13] Lupa evätty: '/etc/nut/upsmon.conf' /etc/nut/upssched.conf [Errno 13] Lupa evätty: '/etc/nut/upssched.conf' -- no debconf information
Bug#924575: systemd-networkd doesn't process IPv6 RA properly
> On 15 Mar 2019, at 08:37, Johan Wassberg wrote: > >> (would be great if you cant test this version and report back) > > Will see what we can accomplish in the lab! systemd(-networkd) 241-1~bpo9+1 from stretch-backports seems to work better. The expiration is now present in the output from `ip -6 r` and the route is discarded when the timer runs out: ``` 2001:dead:5:1219::/64 dev ens33 proto ra metric 1024 expires 2591574sec pref medium fe80::/64 dev ens33 proto kernel metric 256 pref medium default via fe80::209:fff:fe09:5 dev ens33 proto ra metric 1024 expires 1374sec mtu 1500 pref medium ``` But both the new version of systemd-networkd and the default network service "networking" (not sure of the official name is) will add more then one default route if the router advertise this. Is this a feature or a bug? It is not possible to and another default route via `ip -6 route`: ``` # ip -6 route add default via default via fe80::dead:beef:dead:beef dev ens33 RTNETLINK answers: File exists ``` Still curious, is systemd-networkd in stretch-backports considered stable? -- jocar signature.asc Description: Message signed with OpenPGP
Bug#924575: systemd-networkd doesn't process IPv6 RA properly
Thanks for a fast reply! > On 14 Mar 2019, at 15:31, Michael Biebl wrote: > > Hi > > Am 14.03.19 um 15:16 schrieb Johan Wassberg: >> Package: systemd >> Version: 232-25+deb9u9 >> Severity: important >> >> Dear Maintainer, >> this issue is a bit outside my confort zone but I still want to try to >> report this bug. >> >> It is probably the same as Launchpad#1800836[0] and according to that >> ticket the issue fixed in a new version of systemd. But for all of us >> that are stuck with Stretch for some years to come it would be great if >> someone could look in to the issue and backport the fix. > > networkd in stretch I would cosider a tech-preview. > It will probably work for simple cases, but is known to have limitations. > If you want to rely on networkd for more complex setups in stretch, Wish we known this back in Xenial when we for some reason I can't remember decided to switch to networkd… > I > would actually recommend that you use the backport of v241 that we > provide via stretch-backports. Is version 241 of networkd considered stable or is it still a tech-preview? > (would be great if you cant test this version and report back) Will see what we can accomplish in the lab! -- jocar signature.asc Description: Message signed with OpenPGP
Bug#924575: systemd-networkd doesn't process IPv6 RA properly
Package: systemd Version: 232-25+deb9u9 Severity: important Dear Maintainer, this issue is a bit outside my confort zone but I still want to try to report this bug. It is probably the same as Launchpad#1800836[0] and according to that ticket the issue fixed in a new version of systemd. But for all of us that are stuck with Stretch for some years to come it would be great if someone could look in to the issue and backport the fix. The problem seems to be that systemd-networkd doesn't expire or take note of the RA Default Lifetime. In older OSes (or Stretch without systemd-networkd) you could see the expiration of the default route: ``` $ ip -6 r 2001:6b0:5:1568::/64 dev ens192 proto kernel metric 256 expires 2591756sec pref medium fe80::/64 dev ens192 proto kernel metric 256 pref medium default via fe80::209:fff:fe09:5 dev ens192 proto ra metric 1024 expires 1556sec pref medium ``` but with systemd-networkd that information is lost: ``` ip -6 r 2001:6b0:5:1219::/64 dev ens33 proto ra metric 1024 pref medium fe80::/64 dev ens33 proto kernel metric 256 pref medium default via fe80::209:fff:fe09:5 dev ens33 proto ra metric 1024 mtu 1500 pref medium ``` My quess is that this is not an display issue since we can reproduce the same behavior as in Launchpad#1800836[0]: Multiple default routes after a firewall failover. Multiple default routes causes strange connection errors. After failover with systemd-networkd: ``` ip -6 r 2001:6b0:5:1219::/64 dev ens33 proto ra metric 1024 pref medium fe80::/64 dev ens33 proto kernel metric 256 pref medium default via fe80::209:fff:fe09:5 dev ens33 proto ra metric 1024 mtu 1500 pref medium default via fe80::724c:a5ff:fe58:42a2 dev ens33 proto ra metric 1024 mtu 1500 pref medium ``` After failover without systemd-networkd: ``` ip -6 r 2001:6b0:5:1568::/64 dev ens192 proto kernel metric 256 expires 2591536sec pref medium fe80::/64 dev ens192 proto kernel metric 256 pref medium default via fe80::209:fff:fe09:5 dev ens192 proto ra metric 1024 expires 1336sec pref medium ``` Let me know if there is any other information I can provide to help out. [0] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800836 -- Package-specific info: -- System Information: Debian Release: 9.8 APT prefers stretch-updates-test APT policy: (500, 'stretch-updates-test'), (500, 'stretch-security-test'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.115 ii libacl1 2.2.52-3+b1 ii libapparmor12.11.0-3+deb9u2 ii libaudit1 1:2.6.7-2 ii libblkid1 2.29.2-1+deb9u1 ii libc6 2.24-11+deb9u4 ii libcap2 1:2.25-1 ii libcryptsetup4 2:1.7.3-4 ii libgcrypt20 1.7.6-2+deb9u3 ii libgpg-error0 1.26-2 ii libidn111.33-1 ii libip4tc0 1.6.0+snapshot20161117-6 ii libkmod223-2 ii liblz4-10.0~r131-2+b1 ii liblzma55.2.2-1.2+b1 ii libmount1 2.29.2-1+deb9u1 ii libpam0g1.1.8-3.6 ii libseccomp2 2.3.1-2.1+deb9u1 ii libselinux1 2.6-3+b3 ii libsystemd0 232-25+deb9u9 ii mount 2.29.2-1+deb9u1 ii procps 2:3.3.12-3+deb9u1 ii util-linux 2.29.2-1+deb9u1 Versions of packages systemd recommends: ii dbus1.10.26-0+deb9u1 ii libpam-systemd 232-25+deb9u9 Versions of packages systemd suggests: pn policykit-1 pn systemd-container pn systemd-ui Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.130 ii udev 232-25+deb9u9 -- no debconf information
Bug#922141: freeipa-client: additional info : --no-ntp option works
Hello All, as was suggested ( by Timo I think ) using the --no-ntp option fixed this for me some time ago now. I had no further problems with the laptops enrolled as freeipa-client. Further updates in Debian Buster caused no issues. Greetings, J -- Deze e-mail en alle documenten die ermee verzonden zijn, kunnen vertrouwelijke informatie en/of persoonsgegevens bevatten en zijn enkel bestemd voor gebruik door de beoogde en aangeduide bestemmeling(en). Verspreiding of bekendmaking van de inhoud, alsook enige verwerking van de persoonsgegevens die deze e-mail mogelijk bevat, is enkel toegelaten indien overeengekomen met de afzender. Indien u deze e-mail per vergissing ontvangen heeft, gelieve ons dan onmiddellijk te contacteren en deze e-mail en bijhorende bestanden te verwijderen.
Bug#657730: Confirmed in 3.39.1+dfsg-2 (buster)
'/usr/lib/calibre/html5lib/treebuilders/etree_lxml.pyc' rimosso '/usr/lib/calibre/html5lib/treebuilders/__init__.pyc' rimosso removed directory '/usr/lib/calibre/html5lib/treebuilders' '/usr/lib/calibre/html5lib/tokenizer.pyc' rimosso '/usr/lib/calibre/html5lib/utils.pyc' rimosso '/usr/lib/calibre/html5lib/serializer/htmlserializer.pyc' rimosso '/usr/lib/calibre/html5lib/serializer/__init__.pyc' rimosso removed directory '/usr/lib/calibre/html5lib/serializer' '/usr/lib/calibre/html5lib/ihatexml.pyc' rimosso '/usr/lib/calibre/html5lib/treewalkers/__init__.pyc' rimosso removed directory '/usr/lib/calibre/html5lib/treewalkers' '/usr/lib/calibre/html5lib/__init__.pyc' rimosso '/usr/lib/calibre/html5lib/trie/_base.pyc' rimosso '/usr/lib/calibre/html5lib/trie/datrie.pyc' rimosso '/usr/lib/calibre/html5lib/trie/__init__.pyc' rimosso '/usr/lib/calibre/html5lib/trie/py.pyc' rimosso removed directory '/usr/lib/calibre/html5lib/trie' '/usr/lib/calibre/html5lib/inputstream.pyc' rimosso '/usr/lib/calibre/html5lib/html5parser.pyc' rimosso removed directory '/usr/lib/calibre/html5lib' removed directory '/usr/lib/calibre' After: apt autoremove --purge (purged fonts-mathjax* libchm1* libjs-coffeescript* libjs-mathjax* libjs-sphinxdoc* libpodofo0.9.6* libqt5designer5* libqt5help5* libtidy5deb1* optipng* python-apsw* python-cherrypy3* python-css-parser* python-cssselect* python-cssutils* python-dnspython* python-feedparser* python-html5-parser* python-markdown* python-mechanize* python-msgpack* python-netifaces* python-pygments* python-pyqt5* python-pyqt5.qtsvg* python-pyqt5.qtwebkit* python-regex* python-repoze.lru* python-routes* python-utidylib* python-webob* python-yaml*) apt install calibre (were installed calibre calibre-bin and the same package listed above) Now calibre runs fine. -- Cura ut valeas Johan Haggi postridie Kalendas Martias MMDCCLXXII ab Urbe condita signature.asc Description: PGP signature
Bug#923236: plaso: requires pyparsing >= 2.3.0
Package: plaso Version: 20190131-1 Severity: important Dear Maintainer, Trying to run log2timeline from plaso-20190131-1 fails with the following error: [FAILURE] pyparsing version: 2.2.0 is too old, 2.3.0 or later required. But 2.2.0 is the latest available in Buster: python-pyparsing/testing,now 2.2.0+dfsg1-2 all [installed,automatic] alternative to creating and executing simple grammars - Python 2.7 This is due to this upstream commit: https://github.com/log2timeline/plaso/commit/441e4c718d6d5eae4d4ac490dac107842a15e337 which changed the required version from >= 2.0.3 to >= 2.3.0. That change was committed on January 18, and is thus included in releases of Plaso >= 20190131. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-17134-Microsoft Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages plaso depends on: ii python 2.7.15-4 ii python-artifacts 20190113-1 ii python-biplist 1.0.3-1 ii python-certifi 2018.8.24-1 ii python-chardet 3.0.4-3 ii python-crypto2.6.1-9+b1 ii python-dateutil 2.7.3-3 ii python-dfdatetime20190116-1 ii python-dfvfs 20190128-1 ii python-dfwinreg 20190122-1 ii python-dtfabric 20181128-1 ii python-efilter 1.5-2 ii python-elasticsearch 5.4.0-1 ii python-fsapfs20190210-1 ii python-future0.16.0-1 ii python-hachoir-core 1.3.3-4 ii python-hachoir-metadata 1.3.3-2 ii python-hachoir-parser1.3.4-2 ii python-idna 2.6-1 ii python-libbde20190102-1 ii python-libesedb 20181229-3 ii python-libevt20181227-1 ii python-libevtx 20181227-1 ii python-libewf20140804-1 ii python-libfsntfs 20190104-1 ii python-libfvde 20190104-1 ii python-libfwnt 20181227-1 ii python-libfwsi 20181227-1 ii python-liblnk20181227-1 ii python-libmsiecf 20181227-1 ii python-libolecf 20181231-1 ii python-libqcow 20181227-1 ii python-libregf 20181231-1 ii python-libscca 20181227-1 ii python-libsigscan20190103-1 ii python-libsmdev 20181227-1 ii python-libsmraw 20181227-1 ii python-libvhdi 20181227-1 ii python-libvmdk 20181227-1 ii python-libvshadow20190127-1 ii python-libvslvm 20181227-1 ii python-lz4 1.1.0+dfsg-1 ii python-lzma 0.5.3-4 ii python-pefile2018.8.8-1 ii python-psutil5.5.0-1 ii python-pyparsing 2.2.0+dfsg1-2 ii python-requests 2.20.0-2 ii python-six 1.12.0-1 ii python-tsk 20190121-2 ii python-tz2018.9-1 ii python-urllib3 1.24.1-1 ii python-xlsxwriter1.1.2-0.1 ii python-yaml 3.13-2 ii python-yara 3.8.0-1 ii python-zmq 17.1.2-2 plaso recommends no packages. plaso suggests no packages. -- no debconf information
Bug#922141: freeipa-client: additional info
Hello All, additional info: server is ipa-server.x86_64 4.2.0-15.0.1.el7.centos.19 I never had this EM connecting Centos of Ubuntu clients to this server. I reinstalled freeipa-client and updated the test-laptop, and I'm trying to test this further. At the moment I'm gettting another EM: root@jvermeulen:/var/log/apt# ipa-client-install This program will set up FreeIPA client. Version 4.7.2 WARNING: conflicting time synchronization service 'ntp' will be disabled in favor of chronyd Discovery was successful! Client hostname: *** Realm: * DNS Domain: * IPA Server: ** BaseDN: *** Continue to configure the system with these values? [no]: yes Synchronizing time Configuration of chrony was changed by installer. CalledProcessError(Command ['/bin/systemctl', 'restart', 'chronyd.service'] returned non-zero exit status 5: 'Failed to restart chronyd.service: Unit chronyd.service not found.\n') The ipa-client-install command failed. See /var/log/ipaclient-install.log for more information So ipa-client seems to look for chronyd, while on this test system I seem to have to use chrony root@jvermeulen:/var/log/apt# systemctl status chronyd Unit chronyd.service could not be found. root@jvermeulen:/var/log/apt# systemctl status chrony ● chrony.service - chrony, an NTP client/server Loaded: loaded (/lib/systemd/system/chrony.service; disabled; vendor preset: enabled) Active: active (running) since Wed 2019-02-13 17:00:55 CET; 1min 40s ago Docs: man:chronyd(8) man:chronyc(1) man:chrony.conf(5) Main PID: 1760 (chronyd) Tasks: 1 (limit: 4915) Memory: 1.4M CGroup: /system.slice/chrony.service └─1760 /usr/sbin/chronyd Maybe I have to make another bug report for this other EM I get today. I have removed chrony and installed and enabled ntp, I stil get WARNING: conflicting time synchronization service 'ntp' will be disabled in favor of chronyd and end result is the same. Greetings, J -- Johan Vermeulen IT-medewerker Caw De Kempen johan.vermeu...@cawdekempen.be <mailto:johan.vermeu...@cawdekempen.be> 0479.82.01.41 -- Deze e-mail en alle documenten die ermee verzonden zijn, kunnen vertrouwelijke informatie en/of persoonsgegevens bevatten en zijn enkel bestemd voor gebruik door de beoogde en aangeduide bestemmeling(en). Verspreiding of bekendmaking van de inhoud, alsook enige verwerking van de persoonsgegevens die deze e-mail mogelijk bevat, is enkel toegelaten indien overeengekomen met de afzender. Indien u deze e-mail per vergissing ontvangen heeft, gelieve ons dan onmiddellijk te contacteren en deze e-mail en bijhorende bestanden te verwijderen.
Bug#921953: apacheds: Further analysis
Hi. Looked at it a bit more and found the following things. ApacheDS have moved it's configuration to a dynamic schema based setup, like OpenLDAP. As part of the startup it tries to migrate the config.ldif to a folder based setup in ou=config. Since the user it runs as doesn't have write permission for /etc/apacheds it fails and then gives up starting. Additionally, once the permission issue is sorted the current systemd unit checks for the existance of the config.ldif file which will be renamed as part of the migration so it will not start the server. The patch below fixes both but I'm not sure if services are supposed to write in /etc. -- diff -ur apache-directory-server-2.0.0~M15/debian/apacheds.postinst apache-directory-server-2.0.0~M15-mod/debian/apacheds.postinst --- apache-directory-server-2.0.0~M15/debian/apacheds.postinst 2015-07-01 22:22:10.0 +0200 +++ apache-directory-server-2.0.0~M15-mod/debian/apacheds.postinst 2019-02-10 21:07:19.687924216 +0100 @@ -32,7 +32,9 @@ # Fix directory permissions chown -R $APACHEDS_USER:$APACHEDS_GROUP /var/log/apacheds || true chown -R $APACHEDS_USER:$APACHEDS_GROUP /var/lib/apacheds || true +chown $APACHEDS_USER:$APACHEDS_GROUP /etc/apacheds chown $APACHEDS_USER:$APACHEDS_GROUP /etc/apacheds/* +chmod 640 /etc/apacheds chmod 640 /etc/apacheds/* ;; diff -ur apache-directory-server-2.0.0~M15/debian/apacheds.service apache-directory-server-2.0.0~M15-mod/debian/apacheds.service --- apache-directory-server-2.0.0~M15/debian/apacheds.service 2015-07-01 22:22:10.0 +0200 +++ apache-directory-server-2.0.0~M15-mod/debian/apacheds.service 2019-02-10 21:04:28.228844408 +0100 @@ -1,7 +1,8 @@ [Unit] Description=Apache Directory Server After=network.target -ConditionPathExists=/etc/apacheds/config.ldif +ConditionPathExists=|/etc/apacheds/config.ldif +ConditionPathIsDirectory=|/etc/apacheds/ou=config [Service] Type=simple Regards, Johan
Bug#921953: apacheds: Apacheds fails to start after clean installation
Package: apacheds Version: 2.0.0~M24-2 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Fresh installation of buster using default options, then tried to install apacheds. * What exactly did you do (or not do) that was effective (or ineffective)? apt-get install apacheds * What was the outcome of this action? Feb 10 14:35:14 testdap2 systemd[1]: Started Apache Directory Server. Feb 10 14:35:17 testdap2 sh[46942]: [2019-35-10T14:35:17.017+] ERROR [org.apache.directory.server.UberjarMain] - Failed to start the service. Feb 10 14:35:17 testdap2 sh[46942]: org.apache.directory.api.ldap.model.exception.LdapOperationException: /usr/share/apacheds/instances/default/conf/ou=config.ldif (Permission denied) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.core.partition.ldif.LdifPartition.addEntry(LdifPartition.java:790) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.core.partition.ldif.LdifPartition.add(LdifPartition.java:263) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.config.ConfigPartitionInitializer.initConfigPartition(ConfigPartitionInitializer.java:181) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.ApacheDsService.initConfigPartition(ApacheDsService.java:335) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:187) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:153) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.start(UberjarMain.java:151) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.main(UberjarMain.java:77) Feb 10 14:35:17 testdap2 sh[46942]: Caused by: java.io.FileNotFoundException: /usr/share/apacheds/instances/default/conf/ou=config.ldif (Permission denied) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileOutputStream.open0(Native Method) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileOutputStream.(FileOutputStream.java:237) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileOutputStream.(FileOutputStream.java:187) Feb 10 14:35:17 testdap2 sh[46942]: at java.base/java.io.FileWriter.(FileWriter.java:96) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.core.partition.ldif.LdifPartition.addEntry(LdifPartition.java:784) Feb 10 14:35:17 testdap2 sh[46942]: ... 7 more Feb 10 14:35:17 testdap2 systemd-journald[10273]: Forwarding to syslog missed 7 messages. Feb 10 14:35:17 testdap2 sh[46942]: [2019-35-10T14:35:17.017+] ERROR [org.apache.directory.server.UberjarMain] - Failed to start the service. Feb 10 14:35:17 testdap2 sh[46942]: java.lang.NullPointerException Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.ApacheDsService.stop(ApacheDsService.java:635) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.stop(UberjarMain.java:219) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.start(UberjarMain.java:158) Feb 10 14:35:17 testdap2 sh[46942]: at org.apache.directory.server.UberjarMain.main(UberjarMain.java:77) Feb 10 14:35:17 testdap2 systemd[1]: apacheds.service: Main process exited, code=exited, status=1/FAILURE Feb 10 14:35:17 testdap2 systemd[1]: apacheds.service: Failed with result 'exit-code'. * What outcome did you expect instead? A running apacheds instance. I also looked for a README.Debian in the /usr/share/doc/apacheds folder for any other instructions, but no such file. Regards, Johan -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.15.18-10-pve (SMP w/24 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apacheds depends on: ii adduser 3.118 ii default-jre-headless [java7-runtime-headless] 2:1.11-71 ii libapacheds-java 2.0.0~M24-2 ii openjdk-11-jre-headless [java7-runtime-headless] 11.0.2+9-3 apacheds recommends no packages. apacheds suggests no packages. -- Configuration Files: /etc/apacheds/config.ldif [Errno 13] Permission denied: '/etc/apacheds/config.ldif' /etc/apacheds/log4j.properties [Errno 13] Permission denied: '/etc/apacheds/log4j.properties' -- no debconf information
Bug#915306: px: Should Recommend lsof, not depend on
Package: px Version: 1.0.13-1 Severity: normal Hi! px can actually operate without "lsof", so it should recommend "lsof" rather than depending on it. This would also enable installation of px on Debian/Hurd and Debian/kFreeBSD where lsof is not available. Regards /Johan -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.125-linuxkit (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: unable to detect Versions of packages px depends on: ii lsof 4.89+dfsg-0.1 ii procps 2:3.3.15-2 ii python33.7.1-2 ii python3-dateutil 2.7.3-1 ii python3-docopt 0.6.2-2 ii python3-pkg-resources 40.5.0-1 px recommends no packages. px suggests no packages. -- no debconf information
Bug#880393: libsasl2-modules-gssapi-heimdal seems built against MIT - Buster?
Hi again! Will the patch from Helmut be included in Buster and make this library useful again? -- jocar
Bug#909314: Short reply
Hi there Shirish, I get where you're coming from and what you say is not without merit. I do however want to clarify that I don't it completely removed, and in relation to that two related things. Firstly: I'm not a package maintainer, but I suspect that stuff like this might have been handled in the past. In which case my suggestion will depend entirely on that. But hypothetically: there are a lot of sites youtube-dl can be used for. So how long can that list be? Is 5 sites, or more, a liability or an asset? Arguments like that can devolve into absurdities, there are a finite amount of sites, but there _is_ a lot of them. I obviously hint at the former, but really. With regard to Debian packaging I'm a user and it is from that perspective I view it. Secondly: Without being contrarian for the sake of being contrarian I'd say that the inverse is true when you say: "...would have made sense if it was a GUI program but it's a CLI program." I'd argue that it's easier to browse a long list in a "GUI format" and not the other way around. Or in a worst case scenario: just as cumbersome. What I think is not Policy. Neither does it become praxis just by a mere uttering, and rightfully. So I look forward to nothing. Best regard, Johan. pgpygrKFVdK8c.pgp Description: OpenPGP digital signature
Bug#910581: confirmed
I cab confirm this bug. Exact same situation here. I could also fix it by downgrading libkf5kontactinterface5 to 17.12.3-1. -- Johan Spee "Eve Ryth in Gisgon na Beal Right"
Bug#910683: RFS: borgmatic/1.2.7-1 [ITP]
Le 10/10/2018 à 14:59, Andrej Shadura a écrit : > Thanks. I’ve done some changes too, you can find them at: > > https://salsa.debian.org/debian/borgmatic/ > Thank you so much! I see you uploaded the package to ftp-master so I removed the one on mentors.debian.net. > It seems to me you have slightly misunderstood the purpose of branches > or how they’re used. I think this document may be helpful: > > https://dep-team.pages.debian.net/deps/dep14/ > Thank you for the info. I actually didn't know how to work with branches in a Debian repository and couldn't find any references. I'll keep this in mind for my future contributions. -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
Bug#910683: RFS: borgmatic/1.2.7-1 [ITP]
Hi Andrej. Just to let you know, I commit some small changes in my borgmatic respository regarding what you did on pykwalify. I added a configuration file for gbp and removed "explicit dependencies" in debian/control (to let dh_python manage them). I also renamed the master branch to debian/master and the upstream/1.2.7 branch to upstream/latest (I imported the full upstream history up to the 1.2.7 tag). Please let me know if something else is missing. Regards. -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
Bug#910677: closing RFS: pykwalify/1.7.0-1 [ITP]
Le 09/10/2018 à 17:29, Andrej Shadura a écrit :> Nothing really: I’m a member of it :) > I’ve uploaded the package and pushed it to > https://salsa.debian.org/python-team/modules/pykwalify, please have a > look at my changes. > That looks good to me. Thank you for your help and for having been so quick. On Tue, 09 Oct 2018 22:20:42 + Bart Martens wrote: > Please remove the package from mentors or mark it "needs sponsor = no". > I removed it. Thank you. -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
Bug#910677: Subject: RFS: pykwalify/1.7.0-1 [ITP]
Le 09/10/2018 à 16:12, Andrej Shadura a écrit : > I’m just thinking, Johan, how do you feel about putting this package under a > maintenance of the Python team with you as an uploader? On one hand, you > won’t ‘own’ the package, but on the other hand others could upload fixes if > your package becomes RC-buggy, for example. > I'm totally fine with that. To be honest, I'm quite new at creating official Debian packages and I'm not really familiar with how uploads to the Debian repository work. I would be very happy if my work could be backed by the Python team. What should I do to have it accepted by the Python team? -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
Bug#910683: RFS: borgmatic/1.2.7-1 [ITP]
Correction (sorry, I just copy-pasted too quickly): * Package name: borgmatic Version : 1.2.7-1 Upstream Author : Dan Helfman (witten) * URL : http://www.example.org/ * License : GPLv3 Section : utils -- Johan Fleury PGP Key ID : 0x5D404386805E56E6 signature.asc Description: OpenPGP digital signature
