Bug#1063900: gstreamer1.0-plugins-good: missing Breaks+Replaces: gstreamer1.0-plugins-ugly (<< 1.23)
On Wed, 14 Feb 2024 14:58:16 +0100 Andreas Beckmann wrote: Package: gstreamer1.0-plugins-good Version: 1.23.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, [...] Current version in sid are the following ones: $ apt policy gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-plugins-good: Table de version : 1.24.2-1 500 500 https://deb.debian.org/debian unstable/main amd64 Packages gstreamer1.0-plugins-ugly: Table de version : 1.24.2-1+b1 500 500 https://deb.debian.org/debian unstable/main amd64 Packages The following files are in conflict: /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrwbdec.so /usr/share/gstreamer-1.0/presets/GstAmrnbEnc.prs Files mentioned here in the bug report are not present in gstreamer1.0-plugins-ugly:1.24.2-1+b1 anymore. Can you confirm I am not wrong and update the bug report accordingly ? cheers, Regards, Andreas -- Jean-Marc (*) /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrnb.so /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstamrwbdec.so /usr/share/gstreamer-1.0/presets/GstAmrnbEnc.prs OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1063808: simple-scan: Unable to load items from the cursor theme adwaita-icon-theme
Package: simple-scan Version: 44.0-1 Severity: normal X-Debbugs-Cc: jean-m...@6jf.be Dear Maintainer, Since adwaita-icon-theme upgraded to 46~beta-1, I get issues when cropping a scanned document. The mouse cursor does not change when trying to grap the crop-region-selector to resize it. Logs from simple-scan: $ LANG=C simple-scan Gdk-Message: 17:42:28.355: Unable to load bottom_side from the cursor theme Gdk-Message: 17:42:28.370: Unable to load hand1 from the cursor theme Gdk-Message: 17:42:28.969: Unable to load bottom_side from the cursor theme Gdk-Message: 17:42:29.021: Unable to load arrow from the cursor theme Gdk-Message: 17:42:29.224: Unable to load bottom_left_corner from the cursor theme Gdk-Message: 17:42:29.593: Unable to load left_side from the cursor theme Gdk-Message: 17:42:29.719: Unable to load bottom_left_corner from the cursor theme Gdk-Message: 17:42:30.253: Unable to load bottom_side from the cursor theme Gdk-Message: 17:42:30.271: Unable to load hand1 from the cursor theme Gdk-Message: 17:42:35.285: Unable to load bottom_side from the cursor theme Gdk-Message: 17:42:35.398: Unable to load arrow from the cursor theme Gdk-Message: 17:42:36.161: Unable to load bottom_side from the cursor theme Gdk-Message: 17:42:36.507: Unable to load bottom_right_corner from the cursor theme Gdk-Message: 17:42:42.130: Unable to load arrow from the cursor theme Gdk-Message: 17:43:51.187: Unable to load hand1 from the cursor theme Gdk-Message: 17:43:51.283: Unable to load top_side from the cursor theme Gdk-Message: 17:43:51.312: Unable to load arrow from the cursor theme Regards, Jean-Marc -- Package-specific info: -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages simple-scan depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.10-4 ii dbus-x11 [dbus-session-bus] 1.14.10-4 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b1 ii libc6 2.37-15 ii libcairo2 1.18.0-1+b1 ii libcolord21.4.6-5 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b1 ii libglib2.0-0 2.78.3-2 ii libgtk-3-03.24.41-1 ii libgusb2 0.4.8-1 ii libhandy-1-0 1.8.3-1 ii libpackagekit-glib2-181.2.8-1+b1 ii libsane1 1.2.1-7+b1 ii libwebp7 1.3.2-0.3 ii libwebpmux3 1.3.2-0.3 ii xdg-utils 1.1.3-4.1 ii zlib1g1:1.3.dfsg-3+b1 simple-scan recommends no packages. simple-scan suggests no packages. -- no debconf information
Bug#1063640: Processed: Re: Bug#1063640: adwaita-icon-theme: cursor theme not found
hi Jeremy,
Le 12/02/24 à 13:21, Debian Bug Tracking System a écrit :
Processing control commands:
found -1 45.3-2
Bug #1063640 {Done: Jeremy Bícha } [src:mutter]
adwaita-icon-theme: cursor theme not found
Marked as found in versions mutter/45.3-2 and reopened.
fixed -1 44.8-3
Bug #1063640 [src:mutter] adwaita-icon-theme: cursor theme not found
Marked as fixed in versions mutter/44.8-3.
I think it is not fully fixed in mutter 44.8-3.
$ LANG=C apt policy mutter
mutter:
Installed: 44.8-3
I got problems running the simple-scan application and trying to crop
the scanned document. The mouse cursor does not change when trying to
grap the crop-region-selector to resize it.
$ LANG=C simple-scan
Gdk-Message: 17:42:28.355: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:28.370: Unable to load hand1 from the cursor theme
Gdk-Message: 17:42:28.969: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:29.021: Unable to load arrow from the cursor theme
Gdk-Message: 17:42:29.224: Unable to load bottom_left_corner from the
cursor theme
Gdk-Message: 17:42:29.593: Unable to load left_side from the cursor theme
Gdk-Message: 17:42:29.719: Unable to load bottom_left_corner from the
cursor theme
Gdk-Message: 17:42:30.253: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:30.271: Unable to load hand1 from the cursor theme
Gdk-Message: 17:42:35.285: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:35.398: Unable to load arrow from the cursor theme
Gdk-Message: 17:42:36.161: Unable to load bottom_side from the cursor theme
Gdk-Message: 17:42:36.507: Unable to load bottom_right_corner from the
cursor theme
Gdk-Message: 17:42:42.130: Unable to load arrow from the cursor theme
Gdk-Message: 17:43:51.187: Unable to load hand1 from the cursor theme
Gdk-Message: 17:43:51.283: Unable to load top_side from the cursor theme
Gdk-Message: 17:43:51.312: Unable to load arrow from the cursor theme
Regards,
--
Jean-Marc
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1063640: adwaita-icon-theme: cursor theme not found
Hi Guy, On Mon, 12 Feb 2024 09:45:26 +0200 Guy Rutenberg wrote: Package: mutter Version: 44.8-3 Followup-For: Bug #1063640 X-Debbugs-Cc: guyrutenb...@gmail.com Dear Maintainer, I just experienced the same bug using mutter 44.8-3 and adwaita-icon-them 46~beta-1. Reverting back to adwaita-icon-theme 45.0-2 resolved the issue. Did you upgrade your theme inside a running gnome session ? Because in this case, you first need to log out/log in to really use mutter 44.8-3. Meaning you will get this issue until you re-start a new session. Guy -- Jean-Marc OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058887: linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor
Hi Salvatore, Le 6/01/24 à 17:31, Salvatore Bonaccorso a écrit : Hi Jean-Marc, On Sat, Jan 06, 2024 at 03:01:10PM +0100, Salvatore Bonaccorso wrote: Hi The issue should be fixed with https://git.kernel.org/linus/400f6ebbc175286576c7f7fddf3c347d09d12310 . Can you check that commit on top of the most current version in unstable to confirm? Let me be a bit more specific: This is about testing the attached patch with help of https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4 to build a kernel image with the patch applied, to confirm if it fixes the issue. Though I'm almost sure that this is the same issue. I built a kernel image with the patch applied and it solves the issue. Thank you so much for your help. And it pushes me back in compiling kernel allowing to compare the current way of working with old ones. Incredible progress making kernel building "child's play". Building a kernel with the patch applied in 2 commands ... Hats off to you all. Regards, Salvatore Regards, -- Jean-Marc OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058887: issue also impacts Debian stable
The Debian stable having the issue runs linux-image-6.1.0-17 (6.1.69-1). -- Jean-Marc OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058887: issue also impacts Debian stable
Control: severity 1058887 serious thanks It also impact Debian stable. I just installed Debian bookworm on a laptop and it gets the same issue. Switching off the wi-fi hangs and impacts other softwares and the poweroff. Raising the severity to serious. -- Jean-Marc OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058887: issue persists with kernel 6.6.8
Upgrading linux kernel to 6.6.9-1 does not solve the issue. -- Jean-Marc
Bug#1058887: issue persists with kernel 6.6.8
After today's upgrade bringing linux-image-6.6.8 to sid, issue persists. Switching off my iwlwifi device makes nmcli unusable. It also blocks firefox. And "sudo any-command" hangs, impossible to break it. Powering off/rebooting the system is also impossible. -- Jean-Marc
Bug#1058887: downgrading firmware-iwlwifi does not help
I also downgraded firmware-iwlwifi from 20230625-2 to 20230210-5 but it does not help. Switching off iwlwifi device hangs and blocks the system making it impossible to power off. -- Jean-Marc OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058887: linux-image-6.5.0-5-amd64: impossible to switch off iwlwifi adaptor
Package: src:linux Version: 6.5.13-1 Severity: normal Dear Maintainer, When I try to switch off my Wi-Fi adaptor, it just blocks/hangs and never goes down. Trying to get info in cli also blocks: $ env LANG=C nmcli Warning: nmcli (1.44.2) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. Even reboot/power-down hangs and the only way to recover is a hard-power down. I added at the end of this report some info from syslog (tail -f /var/log/syslog) I ran at the moment I swithced off my Wi-Fi. Last info, I tried with the previous kernel linux-image-6.5.0-4-amd64 (6.5.10-1) and it works like a charm. Regards, Jean-Marc -- Package-specific info: ** Version: Linux version 6.5.0-5-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 13.2.0-7) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC Debian 6.5.13-1 (2023-11-29) ** Command line: BOOT_IMAGE=/vmlinuz-6.5.0-5-amd64 root=/dev/mapper/gandalf--vg-root ro quiet ** Tainted: W (512) * kernel issued warning ** Kernel log: [ 15.121367] hid-alps 0018:044E:120B.0001: input,hidraw0: I2C HID v1.00 Mouse [DLL07A0:01 044E:120B] on i2c-DLL07A0:01 [ 15.160195] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 [ 15.160285] thermal thermal_zone7: failed to read out thermal zone (-61) [ 15.167411] iwlwifi :02:00.0: reporting RF_KILL (radio disabled) [ 15.224743] EXT4-fs (nvme0n1p2): mounting ext2 file system using the ext4 subsystem [ 15.23] iwlwifi :02:00.0: base HW address: 00:28:f8:e3:43:f6, OTP minor version: 0x0 [ 15.235653] EXT4-fs (nvme0n1p2): mounted filesystem 24d75cff-3492-44c9-bb3b-b3cc1a47ff56 r/w without journal. Quota mode: none. [ 15.244767] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [ 15.247297] EXT4-fs (dm-3): mounted filesystem 16ae5ebd-3b09-4b5a-a492-54848826a72c r/w with ordered data mode. Quota mode: none. [ 15.254994] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3246: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 15.254999] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 15.255002] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 15.255004] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 15.255005] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 15.255007] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [ 15.255009] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [ 15.255010] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 15.256746] iwlwifi :02:00.0 wlp2s0: renamed from wlan0 [ 15.295867] usb 1-5: New USB device found, idVendor=0bda, idProduct=5650, bcdDevice=60.06 [ 15.295871] usb 1-5: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 15.295873] usb 1-5: Product: Integrated Webcam_HD [ 15.295874] usb 1-5: Manufacturer: CN0K49W17248773OA6KAA00 [ 15.295876] usb 1-5: SerialNumber: 200901010001 [ 15.322123] input: HDA Digital PCBeep as /devices/pci:00/:00:1f.3/sound/card0/input12 [ 15.38] input: HDA Intel PCH Headphone Mic as /devices/pci:00/:00:1f.3/sound/card0/input13 [ 15.322338] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input14 [ 15.322437] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input15 [ 15.322533] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input16 [ 15.390559] audit: type=1400 audit(1702826732.654:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=655 comm="apparmor_parser" [ 15.393865] audit: type=1400 audit(1702826732.654:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="system_tor" pid=658 comm="apparmor_parser" [ 15.401016] audit: type=1400 audit(1702826732.662:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=656 comm="apparmor_parser" [ 15.401021] audit: type=1400 audit(1702826732.662:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=656 comm="apparmor_parser" [ 15.404165] audit: type=1400 audit(1702826732.666:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="torbrowser_tor" pid=675 comm="apparmor_parser" [ 15.406822] audit: type=1400 audit(1702826732.670:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=657 comm="apparmor_parser" [ 15.406827] audit: type=1400 audit
Bug#1057535: python3-fonttools: upgrading package gave a SyntaxWarning: invalid escape sequence '\_'
Package: python3-fonttools Version: 4.38.0-1+b2 Severity: normal X-Debbugs-Cc: jean-m...@6jf.be Dear Maintainer, Upgrading the package today in my debian sid from 4.38.0-1+b1 to 4.38.0-1+b2 gave a warning message: Paramétrage de python3-fonttools (4.38.0-1+b2) ... /usr/lib/python3/dist-packages/fontTools/cffLib/specializer.py:40: SyntaxWarning: invalid escape sequence '\_' """Takes a T2CharString program list and returns list of commands. I guess this is not really important. But, please, take a look at it. Regards, JM -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-fonttools depends on: ii libc6 2.37-13 ii python33.11.6-1 ii python3-all3.11.6-1 ii python3-brotli 1.1.0-2+b1 ii python3-fs 2.4.16-2 ii python3-lxml 4.9.3-1+b1 ii python3-lz44.0.2+dfsg-1+b3 ii python3-pkg-resources 68.1.2-2 ii python3-scipy 1.10.1-6 ii python3-sympy 1.12-6 ii python3-ufolib20.16.0+dfsg1-1 ii python3-unicodedata2 15.1.0+ds-1+b1 ii unicode-data 15.1.0-1 python3-fonttools recommends no packages. python3-fonttools suggests no packages. -- no debconf information
Bug#1053345: [debian bookworm] brcmfmac mmc2:0001:1: firmware: failed to load brcm/brcmfmac4330-sdio.cubietech,cubietruck-plus.bin (-2)
ls 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 02:01:23:c9:ff:40 brd ff:ff:ff:ff:ff:ff altname end0 3: usb0: mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 96:c0:0e:9d:d2:46 brd ff:ff:ff:ff:ff:ff 5: wlan0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 94:a1:a2:e4:35:27 brd ff:ff:ff:ff:ff:ff root@Cubietruck-Plus:~# root@Cubietruck-Plus:~# iwconfig wlan0 wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on root@Cubietruck-Plus:~# It seems that all is ok (!), even with the error (!) Thank in advance to install this patch in bookworm and perhaps also on trixie firmware package. Regards -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1031363: librnp0 from experimental breaks thunderbird openpgp feature
Hi Eric, On Wed, 15 Feb 2023 18:59:23 +0100 Eric Valette wrote: > Package: librnp0 > Version: 0.17.0~git20220428-1 > Severity: serious > Justification: makes unrelated software on the system > > Thre is no dependency and the packages installs but thunderbird do not manage to dlopen the dddl and it breaks opengpg. > > Downgrading to unstable version fixes the problem. > Can you confirm you are still facing this issue with the last version of thunderbird ? And, please, update this bug report accordingly. Thank you so much. Regards, --- Jean-Marc OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1049398: u-boot-sunxi: missing dependency
Package: u-boot-sunxi Version: 2023.01+dfsg-2 Severity: important Dear Maintainers, Is seems that on package u-boot-sunxi, one internal tool must use another tools defined and installed by Debian package u-boot-tools. But because package u-boot-tools is not defined in dependencies on u-boot-sunxi, then not possible to end the job. Test 1 : before any action... -- root@hn-cubietruck-120:~# cat /etc/debian_version 12.1 root@hn-cubietruck-120:~# dpkg -l |grep u-boot root@hn-cubietruck-120:~# Test 2 : Install package u-boot-sunxi -- root@hn-cubietruck-120:~# apt install u-boot-sunxi . Dépaquetage de u-boot-sunxi:armhf (2023.01+dfsg-2) ... Paramétrage de u-boot-sunxi:armhf (2023.01+dfsg-2) ... root@hn-cubietruck-120:~# Test 3 : Install u-boot-sunxi root@hn-cubietruck-120:~# TARGET=/usr/lib/u-boot/Cubietruck /usr/bin/u-boot-install-sunxi /dev/mmcblk1 /usr/bin/u-boot-install-sunxi: mkimage: command not found. Please install u-boot-tools. root@hn-cubietruck-120:~# root@hn-cubietruck-120:~# echo $? 1 Test 4 : Install u-boot-tools - root@hn-cubietruck-120:~# apt install -y u-boot-tools .. Dépaquetage de u-boot-tools (2023.01+dfsg-2) ... Paramétrage de libubootenv0.1:armhf (0.3.2-1) ... Paramétrage de u-boot-tools (2023.01+dfsg-2) ... Paramétrage de libubootenv-tool (0.3.2-1) ... root@hn-cubietruck-120:~# Test 5: reinstall now u-boot root@hn-cubietruck-120:~# TATARGET=/usr/lib/u-boot/Cubietruck /usr/bin/u-boot-install-sunxi /dev/mmcblk1 Thank in advance to change dependencies into u-boot-sunxi package Best regards -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1042484: util-linux-locales: /usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5
Trying to solve the failed upgrade, I pinned util-linux-locales to version 2.38.1-6 and ran "apt --fix-broken install". This removed the package util-linux-locales 2.38.1-6. Re-installing package util-linux-locales 2.38.1-6, I noticed there is a conflict between it and manpages-fr package: $ env LANG=C apt depends manpages-fr manpages-fr Breaks: manpages-fr-dev (<< 4.11) Breaks: (<= 20151231) Breaks: tree (<< 2.1.0-1) **Breaks: util-linux-locales (<< 2.39.1-3)** Breaks: xz-utils (<< 5.2.7) So, re-installing util-linux-locales 2.38.1-6 removed package manpages-fr. Current situation for sid/unstable users with manpages-fr package installed: . pin util-linux-locales to version 2.38.1-6 = removing manpages-fr. . try to upgrade to but upgrade failed. -- Jean-Marc OpenPGP_signature Description: OpenPGP digital signature
Bug#1042484: util-linux-locales: /usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5
Package: util-linux-locales Version: 2.39.1-3 Severity: serious Justification: 6 X-Debbugs-Cc: jean-m...@6jf.be Dear Maintainer, Upgrading util-linux-locales from 2.38.1-6 to 2.39.1-3 failed and returned this error message: Preparing to unpack .../util-linux-locales_2.39.1-3_all.deb ... Unpacking util-linux-locales (2.39.1-3) over (2.38.1-6) ... dpkg: error processing archive /var/cache/apt/archives/util-linux-locales_2.39.1-3_all.deb (--unpack): trying to overwrite '/usr/share/man/fr/man1/lastb.1.gz', which is also in package manpages-fr 4.19.0-5 Errors were encountered while processing: /var/cache/apt/archives/util-linux-locales_2.39.1-3_all.deb Please, fix this problem. Thank you so much. Regards, Jean-Marc -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages util-linux-locales depends on: ii util-linux 2.39.1-3 util-linux-locales recommends no packages. util-linux-locales suggests no packages. -- no debconf information
Bug#1041437: [debian bookworm] [kernel 6.1.0-9-rt-armmp] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Package:linux-image-6.1.0-9-rt-armm Version: 6.1.0-9-rt-armmp Severity: serious Dear developer, On Debian bookworm, target nanopir1, please find following issue [ 3991.659348] secondary_start_kernel from 0x40301ec0 [ 3991.659348] secondary_start_kernel from 0x40301ec0 [ 3991.659348] secondary_start_kernel from 0x40301ec0 [ 3991.878735] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [ 3991.878763] CPU: 3 PID: 1 Comm: systemd Tainted: G C L 6.1.0-9-rt-armmp #1 Debian 6.1.27-1 [ 3991.878777] Hardware name: Allwinner sun8i Family [ 3991.878796] unwind_backtrace from show_stack+0x18/0x1c [ 3991.878839] show_stack from dump_stack_lvl+0x40/0x4c [ 3991.878867] dump_stack_lvl from panic+0x114/0x37c [ 3991.878892] panic from make_task_dead+0x0/0x184 [ 3992.631427] CPU1: stopping [ 3992.631448] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G C L 6.1.0-9-rt-armmp #1 Debian 6.1.27-1 [ 3992.631462] Hardware name: Allwinner sun8i Family [ 3992.631474] unwind_backtrace from show_stack+0x18/0x1c [ 3992.631504] show_stack from dump_stack_lvl+0x40/0x4c [ 3992.631527] dump_stack_lvl from do_handle_IPI+0x36c/0x3d8 [ 3992.631552] do_handle_IPI from ipi_handler+0x20/0x28 [ 3992.631573] ipi_handler from handle_percpu_devid_irq+0xac/0x278 [ 3992.631600] handle_percpu_devid_irq from generic_handle_domain_irq+0x30/0x40 [ 3992.631620] generic_handle_domain_irq from gic_handle_irq+0x90/0xb0 [ 3992.631639] gic_handle_irq from generic_handle_arch_irq+0x58/0x78 [ 3992.631659] generic_handle_arch_irq from call_with_stack+0x18/0x20 [ 3992.631688] call_with_stack from __irq_svc+0x98/0xdc [ 3992.631708] Exception stack(0xf0875f68 to 0xf0875fb0) [ 3992.631721] 5f60: 0001 c1064990 0067b901 c0321080 c158d340 0001 [ 3992.631732] 5f80: c140f89c c140f8fc 4020406a 410fc075 03126e98 f0875fb8 [ 3992.631740] 5fa0: c030a750 c030a754 60070013 [ 3992.631746] __irq_svc from arch_cpu_idle+0x40/0x44 [ 3992.631762] arch_cpu_idle from default_idle_call+0x48/0x8c [ 3992.631782] default_idle_call from do_idle+0xbc/0x12c [ 3992.631804] do_idle from cpu_startup_entry+0x20/0x24 [ 3992.631824] cpu_startup_entry from secondary_start_kernel+0x134/0x154 [ 3992.631847] secondary_start_kernel from 0x40301ec0 [ 3992.631921] CPU0: stopping [ 3992.631931] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C L 6.1.0-9-rt-armmp #1 Debian 6.1.27-1 [ 3992.631942] Hardware name: Allwinner sun8i Family [ 3992.631948] unwind_backtrace from show_stack+0x18/0x1c [ 3992.631969] show_stack from dump_stack_lvl+0x40/0x4c [ 3992.631989] dump_stack_lvl from do_handle_IPI+0x36c/0x3d8 [ 3992.632012] do_handle_IPI from ipi_handler+0x20/0x28 [ 3992.632034] ipi_handler from handle_percpu_devid_irq+0xac/0x278 [ 3992.632056] handle_percpu_devid_irq from generic_handle_domain_irq+0x30/0x40 [ 3992.632074] generic_handle_domain_irq from gic_handle_irq+0x90/0xb0 [ 3992.632090] gic_handle_irq from generic_handle_arch_irq+0x58/0x78 [ 3992.632110] generic_handle_arch_irq from __irq_svc+0x88/0xdc [ 3992.632128] Exception stack(0xc1401f10 to 0xc1401f58) [ 3992.632138] 1f00: c1064990 00999581 c0321080 [ 3992.632148] 1f20: c158d340 c140f89c c140f8fc c9fff9f7 [ 3992.632158] 1f40: 03126e98 c1401f60 c030a750 c030a754 60030013 [ 3992.632164] __irq_svc from arch_cpu_idle+0x40/0x44 [ 3992.632179] arch_cpu_idle from default_idle_call+0x48/0x8c [ 3992.632195] default_idle_call from do_idle+0xbc/0x12c [ 3992.632215] do_idle from cpu_startup_entry+0x20/0x24 [ 3992.632234] cpu_startup_entry from rest_init+0xd8/0xdc [ 3992.632257] rest_init from arch_post_acpi_subsys_init+0x0/0x18 [ 3992.632290] CPU2: stopping [ 3992.632299] CPU: 2 PID: 240 Comm: systemd-journal Tainted: G C L 6.1.0-9-rt-armmp #1 Debian 6.1.27-1 Best regards -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1041436: [debian bookworm] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.bin (-2)
ff:ff:ff:ff root@nanopi-r1:~# Applying this command can do the correct job... ln -s /lib/firmware/brcm/brcmfmac43430-sdio.AP6212.txt /lib/firmware/brcm/brcmfmac43430-sdio.txt Then... root@nanopi-r1:~# modprobe brcmfmac debug=1 [ 2557.347535] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 2557.356664] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.bin (-2) [ 2557.356767] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.bin (-2) [ 2557.356779] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.bin failed with error -2 [ 2557.365197] usbcore: registered new interface driver brcmfmac [ 2557.406398] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43430-sdio.bin [ 2557.415787] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.txt (-2) [ 2557.415924] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.txt (-2) [ 2557.416237] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43430-sdio.txt [ 2557.416524] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.clm_blob (-2) [ 2557.416627] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.clm_blob (-2) [ 2557.469152] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43430-sdio.clm_blob [ 2557.671497] brcmfmac_wcc: brcmf_wcc_attach: executing [ 2557.736205] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766 The bad news is of courre the same error, but ... root@nanopi-r1:~# ip link ls 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 02:81:9f:b8:31:a7 brd ff:ff:ff:ff:ff:ff altname end0 3: eth1: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether a2:a8:a0:49:74:4b brd ff:ff:ff:ff:ff:ff 5: wlan0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 12:81:9f:b8:31:a7 brd ff:ff:ff:ff:ff:ff root@nanopi-r1:~# root@nanopi-r1:~# iwconfig wlan0 wlan0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on It seems that all is ok (!), even with the error (!) Thank in advance to install this patch in bookworm and trixie firmware package. Regards Cordialement -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1040654: [vmdb2] option --exclude from debootstrap
Package: vmdb2 Version: 0.27+really.0.26-1 Severity: wishlist Dear developer, I have a dream(!) When i use debootstrap, i always use --include AND --exclude options so that Debian make the right choice of package installed into rootfs. Could you please implement in vmdb2 option --exclude from debootstrap ? Thanks in advance Cordialement -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1003959: always true on recent vmdb2 package
Hello, I confirm the same issue on vmdb2 recent : ii vmdb2 0.27+really.0.26-1 all creator of disk images with Debian installed Is there one solution ? Thanks in advance for you help Cordialement -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1037215: [ifupdown] not possible to force -ddd option on wpasupplicant (debug option)
Source: ifupdown Version: Severity: n0.8.36 ormal Dear Debian team, I am using ifupdown package on Debian 11.7 with one wifi interface(if-sta0) in STA mode with sysvinit (no systemd). As a result, of course, i am also using supplicant daemon supplied by wpasupplicant Debian package. In order to search complex issue when usging multiple AP targets, i would to use debug feature as defined in wpasupplicant documentation. ~$ zgrep debug /usr/share/doc/wpasupplicant/README.modes.gz In order to debug connection, association and authentication problems, increase the verbosity level of wpa_supplicant to log debug output by adding the wpa-debug-level option to /etc/network/interfaces like in wpa-debug-level 3 My current configuration for this interface (if-sta0) (file /etc/network/interfaces) is ... . # interface 2.1/17 (if-sta0) (physical):02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59), WLAN interface on motherboard in STA mode allow-autoif-sta0 iface if-sta0 inet dhcp wpa-group CCMP TKIP wpa-pairwiseCCMP TKIP wpa-proto WPA RSN wpa-key-mgmtWPA-PSK wpa-auth-algOPEN wpa-debug-level 3# either 1,2 or 3 wpa-driver wext,nl80211 wpa-iface if-sta0 wpa-ap-scan 1 wpa-scan-ssid 1 wpa-logfile /var/log/wpa_supplicant.log wpa-psk "test-debian" wpa-ssid"hn-tplink-re450-275-2.4Ghz" wpa-ctrl_interface /var/run/wpa_supplicant wpa-conf/etc/wpa_supplicant/wpa_supplicant.if-sta0.conf . After following command sudo ifdown if-sta0;sleep 1;sudo ifup -v if-sta0 The interface shut down, then wpasupplicant is correctly launched, then association is done, and final dhcp is also done, so that no error occurs, perfect (!) Debian ifup/ifdown launch daemon with following parameters... ansible@hn-asusgl752-400:~$ ps auxww |grep supplic ansible 15775 0.0 0.0 5500 892 pts/1S+ 14:25 0:00 tail -f /var/log/wpa_supplicant.log root 20123 0.1 0.0 11776 3524 ?Ss 22:23 0:00 /sbin/wpa_supplicant -B -P /run/wpa_supplicant.if-sta0.pid -i if-sta0 -D wext,nl80211 -f /var/log/wpa_supplicant.log -c /etc/wpa_supplicant/wpa_supplicant.if-sta0.conf ansible 20326 0.0 0.0 6228 1048 pts/18 S+ 22:23 0:00 grep supplic As you can see, it seems that option "-ddd" is not computed by Debian infrastructure when reading "wpa-debug-level 3" into /etc/network/interfaces, it is therefore not possible to debug this daemon. Thanks to give me one method to force debug daemon mode. Please give me a method to force debug daemon mode. Please note that I tried the following line in the interface definition, but without any hit ? pre-up /usr/sbin/wpa_supplicant -B -D nl80211,wext -i if-sta0 -c /etc/wpa_supplicant/wpa_supplicant.if-sta0.conf -f /var/log/wpa_supplicant/wpa_supplicant.log -t -dd Best regards -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1035022: unpaper: undefined symbol: vaSyncBuffer
Package: unpaper Version: 7.0.0-0.1 Severity: important Dear Maintainer, * What led up to the situation? Launching the application from command line gives an error. Unable to start it. * What exactly did you do (or not do) that was effective (or ineffective)? Simply entered "unpaper" in the command line. * What was the outcome of this action? The following error message: unpaper: symbol lookup error: /lib/x86_64-linux-gnu/libavcodec.so.59: undefined symbol: vaSyncBuffer * What outcome did you expect instead? Anything but what I got. As an example, the version being printed in the output. -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing'), (100, 'bookworm-fasttrack'), (100, 'bookworm-backports-staging') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-7-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unpaper depends on: ii libavcodec59 10:5.1.3-dmo3 ii libavformat59 10:5.1.3-dmo3 ii libavutil5710:5.1.3-dmo3 ii libc6 2.36-9 unpaper recommends no packages. unpaper suggests no packages. -- no debconf information
Bug#1034301: [thunderbird on armhf & amd64] not the same release on Debian bullseye 11.6 ?
.debian.org/debian bullseye-updates InRelease Réception de :8 http://ftp.de.debian.org/debian bullseye/main Translation-fr [2 433 kB] Réception de :9 http://ftp.de.debian.org/debian buster/main Translation-fr [2 478 kB] 4 960 ko réceptionnés en 2s (2 313 ko/s) Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Tous les paquets sont à jour. Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Calcul de la mise à jour... Fait 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour. ansible@hn-asusgl752-400:~$ ansible@vn-bullseye-armhf-260:~$ sudo apt update && sudo apt upgrade -y Get:1 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB] Hit:2 http://ftp.de.debian.org/debian bullseye-backports InRelease Hit:3 http://ftp.de.debian.org/debian bullseye InRelease Hit:4 http://ftp.de.debian.org/debian buster InRelease Hit:5 http://ftp.de.debian.org/debian bullseye-updates InRelease Fetched 48.4 kB in 3s (15.7 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ansible@vn-bullseye-armhf-260:~$ test 06: apt-cache policy thunderbird ansible@hn-asusgl752-400:~$ apt-cache policy thunderbird thunderbird: Installé : 1:102.9.0-1~deb11u1 Candidat : 1:102.9.0-1~deb11u1 Table de version : *** 1:102.9.0-1~deb11u1 500 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages 100 /var/lib/dpkg/status 1:91.13.0-1~deb11u1 500 500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages 1:91.12.0-1~deb10u1 90 90 http://ftp.de.debian.org/debian buster/main amd64 Packages ansible@hn-asusgl752-400:~$ ansible@vn-bullseye-armhf-260:~$ apt-cache policy thunderbird thunderbird: Installed: 1:78.8.0-1~deb10u1 Candidate: 1:78.8.0-1~deb10u1 Version table: *** 1:78.8.0-1~deb10u1 100 90 http://ftp.de.debian.org/debian buster/main armhf Packages 100 /var/lib/dpkg/status ansible@vn-bullseye-armhf-260:~$ Conclusions: Why thunderbird is whith one oldrelease on target vn-bullseye-armhf-260 ?. I expect to have the same release than on target hn-asusgl752-400 ? Thanks in advance for your help Cordialement -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1032254: [Debian Bookworm] : dpkg: error processing archive /var/cache/apt/archives/usrmerge_35_all.deb (--unpack):
On 02/03/2023 16:16, Marco d'Itri wrote: On Mar 02, Jean-Marc LACROIX wrote: I am trying to install (via debootstrap) one rootfs in one secured LXC container. My current problem is due to the package usrmerge which is not instalable. Is the usr-is-merged package installed? Is /lib a symlink? /usr is a standalone filesystem, this requires using an initramfs. This failure mode is correct, even if not much helpful for a container, but usrmerge should not have been installed in the first place. Hi Marco, No, the package usr-is-merged is not installed, because ansible@vn-bookworm-arm64-130:~$ dpkg -l |grep merge ii libregexp-assemble-perl 0.38-2 all Perl module to merge several regular expressions ansible@vn-bookworm-arm64-130:~$ apt-cache search usr-is-merged usr-is-merged - Transitional package to assert a merged-/usr system usrmerge - convertir le système dans un schéma de répertoires fusionnés dans /usr ansible@vn-bookworm-arm64-130:~$ sudo apt install usr-is-merged Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Les NOUVEAUX paquets suivants seront installés : usr-is-merged 0 mis à jour, 1 nouvellement installés, 0 à enlever et 8 non mis à jour. Il est nécessaire de prendre 4 832 o dans les archives. Après cette opération, 11,3 ko d'espace disque supplémentaires seront utilisés. Réception de :1 http://ftp.de.debian.org/debian bookworm/main arm64 usr-is-merged all 35 [4 832 B] 4 832 o réceptionnés en 0s (19,4 ko/s) debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78, <> line 1.) debconf: falling back to frontend: Readline Sélection du paquet usr-is-merged précédemment désélectionné. (Lecture de la base de données... 59832 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../usr-is-merged_35_all.deb ... Dépaquetage de usr-is-merged (35) ... Paramétrage de usr-is-merged (35) ... ansible@vn-bookworm-arm64-130:~$ Now, it is installed ansible@vn-bookworm-arm64-130:~$ dpkg -l |grep merge ii libregexp-assemble-perl 0.38-2 all Perl module to merge several regular expressions ii usr-is-merged 35 all Transitional package to assert a merged-/usr system ansible@vn-bookworm-arm64-130:~$ Then i try to install usrmerge now, but without sucess ansible@vn-bookworm-arm64-130:~$ LC_ALL=C sudo apt install usrmerge Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: usrmerge 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 0 B/12.5 kB of archives. After this operation, 38.9 kB of additional disk space will be used. debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78, <> line 1.) debconf: falling back to frontend: Readline (Reading database ... 59835 files and directories currently installed.) Preparing to unpack .../archives/usrmerge_35_all.deb ... /usr is a standalone filesystem, this requires using an initramfs. dpkg: error processing archive /var/cache/apt/archives/usrmerge_35_all.deb (--unpack): new usrmerge package pre-installation script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/usrmerge_35_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ansible@vn-bookworm-arm64-130:~$ ansible@vn-bookworm-arm64-130:~$ ls -altr / total 38 drwxr-xr-x 2 root root 1024 3 sept. 14:10 boot drwx-- 2 root root 12288 24 nov. 11:04 lost+found lrwxrwxrwx 1 root root 8 24 nov. 11:31 sbin -> usr/sbin lrwxrwxrwx 1 root root 7 24 nov. 11:31 lib -> usr/lib drwxr-xr-x 2 root root 1024 24 nov. 11:31 debootstrap lrwxrwxrwx 1 root root 7 24 nov. 11:31 bin -> usr/bin drwxr-xr-x 12 root root 1024 24 nov. 11:31 var drwxr-xr-x 2 root root 1024 24 nov. 11:31 srv drwxr-xr-x 2 root root 1024 24 nov. 11:31 opt drwxr-xr-x 2 root root 1024 24 nov. 11:31 mnt drwxr-xr-x 2 root root 1024 24 nov. 11:31 media drwxr-xr-x 12 root root 4096 24 nov. 11:31 usr drwxr-xr-x 6 root root 1024 24 nov. 18:33 home drwxr-xr-x 20 root root 1024 24 nov. 19:48 .. drwxr-xr-x 20 root root 1024 24 nov. 19:48 . drwx-- 4 root root 1024 11 déc. 23:41 root dr-xr-xr-x 385 root root 0 2 mars 13:29 proc dr-xr-xr-x 13 root root 0 2 mars 13:29 sys drwxr-xr-x 13 root root 680 2 mars 13:29 dev drwxr-xr-x 77 root root 7168 2 mars 13:42 etc drwxr-xr-x 2 root root 0 2 mars 13:42 nfs-home drwxrwxrwt 5 root root 3072 2 mars 17:09 tmp drwxr-xr-x 15 root root 6
Bug#1032254: [Debian Bookworm] : dpkg: error processing archive /var/cache/apt/archives/usrmerge_35_all.deb (--unpack):
On 02/03/2023 14:25, Luca Boccassi wrote: On Thu, 2 Mar 2023 at 12:30, Jean-Marc LACROIX wrote: On 02/03/2023 13:13, Luca Boccassi wrote: Control: tags -1 moreinfo On Thu, 2 Mar 2023 13:00:00 +0100 Jean-Marc LACROIX wrote: Source: usrmerge Version: 35 Severity: normal Dear Debian team, I am trying to install (via debootstrap) one rootfs in one secured LXC container. My current problem is due to the package usrmerge which is not instalable.boowor The target is based on one rock64 board. Which debootstrap version did you use to create the rootfs? debootstrap used is running on hypervisor based on one Debian Bullseye 11.6 release. Deboostrap is launched with --variant=minbase option on http://deb.debian.org/debian and of course with booworm parameter What's the version? debootstrap --version Hi Luca, On hypervisor (arm64 Debian 11.5 bullseye target), the current release fir debootstrap pacae is ansible@hn-rock64-130:~$ sudo debootstrap --version debootstrap 1.0.128+nmu2 ansible@hn-rock64-130:~$ Cordialement -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1032254: [Debian Bookworm] : dpkg: error processing archive /var/cache/apt/archives/usrmerge_35_all.deb (--unpack):
On 02/03/2023 13:13, Luca Boccassi wrote: Control: tags -1 moreinfo On Thu, 2 Mar 2023 13:00:00 +0100 Jean-Marc LACROIX wrote: Source: usrmerge Version: 35 Severity: normal Dear Debian team, I am trying to install (via debootstrap) one rootfs in one secured LXC container. My current problem is due to the package usrmerge which is not instalable.boowor The target is based on one rock64 board. Which debootstrap version did you use to create the rootfs? debootstrap used is running on hypervisor based on one Debian Bullseye 11.6 release. Deboostrap is launched with --variant=minbase option on http://deb.debian.org/debian and of course with booworm parameter Cordialement -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1032254: [Debian Bookworm] : dpkg: error processing archive /var/cache/apt/archives/usrmerge_35_all.deb (--unpack):
rned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/usrmerge_35_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@vn-bookworm-arm64-130:~# Thans in advance for your help Cordialement -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1030308: simple-scan - debug messages
Hi, Please find attached the log messages I got reproducing the problem. First part is starting simple-scan, setting the source to "All Pages From Feeder" and closing it. Second part is re-opening simple-scan, trying to scan and getting the error message, then changing back to "Single Page", trying again and always getting the same message "Failed to scan - Document feeder empty". I hope this help. Regards, -- Jean-Marc simple-scan-debug.log.gz Description: application/gzip OpenPGP_signature Description: OpenPGP digital signature
Bug#1030308: simple-scan does not take sources' prefs into account
Package: simple-scan Version: 42.5-2 Severity: normal X-Debbugs-Cc: jean-m...@6jf.be Dear Maintainer, When I start simple-scan with "All Pages From Feeder" as source (i.e. when this was the source during my last scan session) and if I want to change to use "Single Page", I always got the message "Failed to scan - Document feeder empty". It is like simple-scan does not take into account the fact I changed the source but keep the last option from start. I can very easily reproduce it. Start simple-scan, change the source to "All Pages From Feeder" in the dropdown list at the right-hand side of the "Scan" button and close simple-scan. Start simple-scan again, it should start with the option "All Pages From Feeder" as source. Change this option choosing "Single Page" and try to scan a document clicking on the button "Scan". You should get the message "Failed to scan - Document feeder empty". Workaround is to select "Single Page" option, close simple-scan and re-start it. Hope it will help. Regards, Jean-Marc P.S. Thank you so much creating this program I use a lot ! -- Package-specific info: -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages simple-scan depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.4-1 ii dbus-x11 [dbus-session-bus] 1.14.4-1 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii libc6 2.36-8 ii libcairo2 1.16.0-7 ii libcolord21.4.6-2.1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.5-1 ii libgtk-3-03.24.36-2 ii libgusb2 0.3.10-1 ii libhandy-1-0 1.8.1-1 ii libpackagekit-glib2-181.2.6-2 ii libsane1 1.1.1-6+b2 ii libwebp7 1.2.4-0.1 ii libwebpmux3 1.2.4-0.1 ii xdg-utils 1.1.3-4.1 ii zlib1g1:1.2.13.dfsg-1 simple-scan recommends no packages. simple-scan suggests no packages. -- no debconf information
Bug#1026113: packagekit automatically upgraded debian sid
Package: packagekit Version: 1.2.6-1 Severity: normal X-Debbugs-Cc: jean-m...@6jf.be Dear Maintainer, Today, packagekit automatically upgraded my system during boot/startup. -- Boot 5df5ad4016c2467181758c46374040a1 -- dec 14 20:17:13 g systemd[1]: Starting PackageKit Daemon... dec 14 20:17:13 g PackageKit[792]: daemon start dec 14 20:17:13 g systemd[1]: Started PackageKit Daemon. dec 14 20:17:13 g PackageKit[792]: uid 0 is trying to obtain org.freedesktop.packagekit.package-install-untrusted auth (only_trusted:0) dec 14 20:17:13 g PackageKit[792]: new update-packages transaction /224745_eaabcdba scheduled from uid 0 dec 14 20:17:13 g PackageKit[792]: uid 0 obtained auth for org.freedesktop.packagekit.package-install-untrusted [...] dec 14 20:19:51 g PackageKit[792]: in /224745_eaabcdba for update-packages package endeavour-common;43.0-1;all;debian-unstable-main was installing for uid 0 dec 14 20:19:51 g PackageKit[792]: in /224745_eaabcdba for update-packages package endeavour;43.0-1;amd64;debian-unstable-main was installing for uid 0 dec 14 20:19:51 g PackageKit[792]: in /224745_eaabcdba for update-packages package firefox-l10n-fr;108.0-1;all;debian-unstable-main was installing for uid 0 dec 14 20:19:51 g PackageKit[792]: in /224745_eaabcdba for update-packages package firefox;108.0-1;amd64;debian-unstable-main was installing for uid 0 [...] It caused an upgrade of firefox to 108 version, version affected by bugs. I guess as it works in a non-interactive mode, it does not use apt-listbugs. As I am using a Debian sid Gnome 43 system, I though I can prevent this using gnome-software options but the one to upgrade automatically was already set to off. I tried to find some doc without success to understand how to prevent this. To avoid such action in future, I masked the packagekit.service. In my humble opinion, no auto upgrade should happen in a sid/unstable system. And I open this bugreport to notify this hoping you can explain what triggerred such upgrades and fix the problem in disabling auto-upgrades. Regards, Jean-Marc -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages packagekit depends on: ii init-system-helpers 1.65.2 ii libappstream4 0.15.5-1 ii libapt-pkg6.0 2.5.4 ii libc6 2.36-6 ii libgcc-s1 12.2.0-10 ii libglib2.0-02.74.3-1 ii libglib2.0-bin 2.74.3-1 ii libgstreamer1.0-0 1.20.4-1 ii libpackagekit-glib2-18 1.2.6-1 ii libpolkit-gobject-1-0 122-1 ii libsqlite3-03.40.0-1 ii libstdc++6 12.2.0-10 ii libsystemd0 252.3-2 ii polkitd 122-1 Versions of packages packagekit recommends: ii packagekit-tools 1.2.6-1 ii systemd 252.3-2 Versions of packages packagekit suggests: ii appstream 0.15.5-1 -- no debconf information
Bug#1024270: python3-ptable: installing python3-ptable gives messages "SyntaxWarning: "is" with a literal."
Package: python3-ptable Version: 0.9.2-4 Severity: normal X-Debbugs-Cc: jean-m...@6jf.be Dear Maintainer, Installing python3-ptable package gives this SyntaxWarning messages: Paramétrage de python3-ptable (0.9.2-4) ... /usr/lib/python3/dist-packages/prettytable/prettytable.py:421: SyntaxWarning: "is" with a literal. Did you mean "=="? elif val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:441: SyntaxWarning: "is" with a literal. Did you mean "=="? elif val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:459: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:476: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:674: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:691: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:421: SyntaxWarning: "is" with a literal. Did you mean "=="? elif val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:441: SyntaxWarning: "is" with a literal. Did you mean "=="? elif val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:459: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:476: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:674: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is None or (isinstance(val, dict) and len(val) is 0): /usr/lib/python3/dist-packages/prettytable/prettytable.py:691: SyntaxWarning: "is" with a literal. Did you mean "=="? if val is None or (isinstance(val, dict) and len(val) is 0): Regards, Jean-Marc -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-ptable depends on: ii python3 3.10.6-3 python3-ptable recommends no packages. python3-ptable suggests no packages. -- no debconf information
Bug#1023244: gajim does not start : libsoup-ERROR
Package: gajim Version: 1.5.2-1 Severity: important Dear Maintainer, gajim does not start anymore. It just crashes producing this error message: $ gajim (org.gajim.Gajim:104000): libsoup-ERROR **: 00:06:55.825: libsoup2 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported. I got the same with other programs (i.e. dino-im). Regards, Jean-Marc -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gajim depends on: ii desktop-file-utils 0.26-1 ii gir1.2-gst-plugins-base-1.0 1.20.3-2 ii gir1.2-gtk-3.0 3.24.34-3 ii gir1.2-gtksource-4 4.8.3-1 ii python3 3.10.6-1 ii python3-cairo1.20.1-4 ii python3-css-parser 1.0.8-1 ii python3-gi 3.42.2-2 ii python3-gi-cairo 3.42.2-2 ii python3-idna 3.3-1 ii python3-keyring 23.9.3-1 ii python3-nbxmpp 3.2.4-1 ii python3-openssl 21.0.0-1 ii python3-packaging21.3-1.1 ii python3-pil 9.2.0-1.1 ii python3-precis-i18n 1.0.4-2 Versions of packages gajim recommends: ii alsa-utils 1.2.7-1 ii aspell-en [aspell-dictionary]2018.04.16-0-1 ii aspell-fr [aspell-dictionary]0.50-3-8.1 ii aspell-nl [aspell-dictionary]1:2.20.19-2 ii ca-certificates 20211016 ii dbus 1.14.4-1 ii fonts-noto-color-emoji 2.038-1 ii gajim-omemo 2.8.15-1 ii gajim-openpgp1.4.9-1 ii gir1.2-farstream-0.2 0.2.9-1 ii gir1.2-geoclue-2.0 2.6.0-2 ii gir1.2-gsound-1.01.0.3-2 ii gir1.2-gspell-1 1.12.0-1 ii gir1.2-gstreamer-1.0 1.20.3-1 ii gir1.2-gupnpigd-1.0 1.2.0-3 ii gir1.2-secret-1 0.20.5-3 ii gnome-shell [notification-daemon]43.0-2 ii gstreamer1.0-plugins-ugly1.20.3-1 ii notification-daemon 3.20.0-4+b1 ii pulseaudio-utils 16.1+dfsg1-2+b1 ii python3-dbus 1.3.2-1 ii python3-sentry-sdk 1.9.10-1 ii xfce4-notifyd [notification-daemon] 0.6.4-1 Versions of packages gajim suggests: ii libxss1 1:1.2.3-1 ii nautilus-sendto 3.8.6-4 -- no debconf information
Bug#1021403: [parted] /usr/sbin/parted: invalid token: swap
Le 07/10/2022 à 18:29, Colin Watson a écrit : Control: severity -1 normal Control: fixed -1 3.5-1 On Fri, Oct 07, 2022 at 05:29:14PM +0200, Jean-Marc LACROIX wrote: Severity: critical "makes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package" A difficulty with using the CLI, or even a missing feature in the CLI, doesn't fall into any of these categories. According documentation available in man it seems possible to create one partition of type "swap" by using "set" option on command line. After many tests done with Linux "parted" command and Ansible module "parted", it seems that it is not possible to set one logical partition as a swap partition with the flag option available into parted tool. My disk uses for test has following partitions... ansible@thinkpad-410:~$ sudo fdisk -l /dev/sda Disque /dev/sda : 931,51 GiB, 1000204886016 octets, 1953525168 secteurs Modèle de disque : HGST HTS721010A9 Unités : secteur de 1 × 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 4096 octets taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets Type d'étiquette de disque : dos Identifiant de disque : 0x483880d2 Périphérique AmorçageDébutFin Secteurs Taille Id Type /dev/sda1*2048 48828415 48826368 23,3G 83 Linux /dev/sda2 48830462 1953523711 1904693250 908,2G 5 Étendue /dev/sda5 48830464 68360191 19529728 9,3G 8e LVM Linux /dev/sda6 68362240 703610871998848 976M 82 partition d'échange Linux / Solaris This says that it's already a swap partition, so I'm not sure why you need to set it as one. Can you explain further? Yes, Ansible is one tool which is able to manage idempotence feature. Idempotence is originally a concept from Mathematics. As defined by Wikipedia, idempotence is the property of certain operations in mathematics and computer science whereby they can be applied multiple times without changing the result beyond the initial application. Therefore, the designer should define only one variable (for example) to indicate that /dev/sda6is a logical partition located on an extended partition with type swap. This therefore constitutes an element of choice (the specification) which must be considered as non-modifiable and therefore inviolable (!). Of course, if we modify the specification, then the partition will have to change state. On the first run, of course, because there is nothing on the disk, then Ansible detect this feature and then force a command (parted) to create the partition with swap type. But on the second pass (and later pass), because this partition is already set to the exact type chosen by designer, then no action is done (!) (On an MBR partition table like this, all that setting the "swap" flag does is set the partition type to 0x82.) /dev/sda7 70363136 742666233903488 1,9G 8e LVM Linux /dev/sda8 74268672 279068671 20480 97,7G 8e LVM Linux and when i try to set one partition with swap, then ... ansible@thinkpad-410:~$ sudo /usr/sbin/parted -s -m -a optimal /dev/sda -- unit KiB set 6 swap on /usr/sbin/parted: invalid token: swap I have also tried, but without success... ansible@thinkpad-410:~$ sudo /usr/sbin/parted -s -m -a optimal /dev/sda -- unit KiB set 6 swap on set 6 lvm off /usr/sbin/parted: invalid token: swap This was fixed in parted 3.4.64. From the NEWS file: Add use of the swap partition flag to msdos disk labeled disks. But since it's already of the correct type, maybe you can just skip that bit on older versions of parted? (Or, if your automation is building the entire system from scratch, then another option might be to use GPT instead of MBR.) Dear Colin, First of all, many thanks for the quickly answer and of course for the good news for this bug available in Debian Bookworm Release. Please find some trace to verify behaviour with your new package ansible@thinkpad-410:~$ apt-cache policy parted parted: Installé : 3.4-1 Candidat : 3.4-1 Table de version : 3.5-2 80 80 http://ftp.de.debian.org/debian bookworm/main amd64 Packages *** 3.4-1 500 500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status 3.2-25 90 90 http://ftp.de.debian.org/debian oldstable/main amd64 Packages ansible@thinkpad-410:~$ cat /etc/debian_version 11.5 ansible@thinkpad-410:~$ dpk -l |grep -v ii -bash: dpk : commande introuvable ansible@thinkpad-410:~$ dpkg -l |grep -v ii Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom
Bug#1021403: [parted] /usr/sbin/parted: invalid token: swap
Package: parted Version: 3.4-1 Severity: critical Dear maintainers, According documentation available in man it seems possible to create one partition of type "swap" by using "set" option on command line. After many tests done with Linux "parted" command and Ansible module "parted", it seems that it is not possible to set one logical partition as a swap partition with the flag option available into parted tool. My disk uses for test has following partitions... ansible@thinkpad-410:~$ sudo fdisk -l /dev/sda Disque /dev/sda : 931,51 GiB, 1000204886016 octets, 1953525168 secteurs Modèle de disque : HGST HTS721010A9 Unités : secteur de 1 × 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 4096 octets taille d'E/S (minimale / optimale) : 4096 octets / 4096 octets Type d'étiquette de disque : dos Identifiant de disque : 0x483880d2 Périphérique AmorçageDébutFin Secteurs Taille Id Type /dev/sda1*2048 48828415 48826368 23,3G 83 Linux /dev/sda2 48830462 1953523711 1904693250 908,2G 5 Étendue /dev/sda5 48830464 68360191 19529728 9,3G 8e LVM Linux /dev/sda6 68362240 703610871998848 976M 82 partition d'échange Linux / Solaris /dev/sda7 70363136 742666233903488 1,9G 8e LVM Linux /dev/sda8 74268672 279068671 20480 97,7G 8e LVM Linux and when i try to set one partition with swap, then ... ansible@thinkpad-410:~$ sudo /usr/sbin/parted -s -m -a optimal /dev/sda -- unit KiB set 6 swap on /usr/sbin/parted: invalid token: swap I have also tried, but without success... ansible@thinkpad-410:~$ sudo /usr/sbin/parted -s -m -a optimal /dev/sda -- unit KiB set 6 swap on set 6 lvm off /usr/sbin/parted: invalid token: swap Of course, it is possible to use fdisk , but my challenge is to use only some Ansible modules (if possible !) Thanks in advance for your help -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1016488: openvpn: OpenVPN client prevents shutdown process.
Package: openvpn Version: 2.6.0~git20220518+dco-3 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? When openVPN client is connecter and tyring to shutdown the computer using init 0 command. * What exactly did you do (or not do) that was effective (or ineffective)? Waiting 90s gets the client killed. However, client should not be hanging. Issue is that network is down and client can't reconnect (expected) * What was the outcome of this action? * What outcome did you expect instead? Client should exit quickly instead of waiting for timeout and get killed. Here is an extract of the journalctl: sep 07 04:39:11 t460s NetworkManager[9152]: [1631003951.8511] device (wlp4s0): no secrets: No ag> sep 07 04:39:11 t460s NetworkManager[9152]: [1631003951.8522] device (wlp4s0): Activation: faile> sep 07 04:39:15 t460s ovpn-client[8902]: write UDP: Network is unreachable (code=101) sep 07 04:39:15 t460s ovpn-client[8902]: Network unreachable, restarting sep 07 04:39:15 t460s ovpn-client[8902]: SIGUSR1[soft,network-unreachable] received, process restarting sep 07 04:39:15 t460s ovpn-client[8902]: Restart pause, 300 second(s) sep 07 04:40:38 t460s systemd[1]: session-2.scope: Stopping timed out. Killing. -- System Information: Debian Release: 11.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable'), (100, 'bullseye- fasttrack'), (100, 'bullseye-backports-staging') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-16-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openvpn depends on: ii debconf [debconf-2.0] 1.5.77 ii libc6 2.31-13+deb11u3 ii liblz4-1 1.9.3-2 ii liblzo2-2 2.10-2 ii libnl-3-2003.4.0-1+b1 ii libnl-genl-3-200 3.4.0-1+b1 ii libpam0g 1.4.0-9+deb11u1 ii libpkcs11-helper1 1.27-1 pn libssl3 ii libsystemd0247.3-7 ii lsb-base 11.1.0 ii systemd247.3-7 Versions of packages openvpn recommends: ii easy-rsa 3.0.8-1 Versions of packages openvpn suggests: ii openssl 1.1.1n-0+deb11u3 pn openvpn-dco-dkms pn openvpn-systemd-resolved ii resolvconf1.87 -- debconf information:
Bug#1014284: [kernel 5.18.5-1] [arm64 on Rock64 SBC]
rq not found [7.725695] rk_gmac-dwmac ff54.ethernet: IRQ eth_lpi not found [7.726374] rk_gmac-dwmac ff54.ethernet: force_sf_dma_mode is ignored if force_thresh_dma_mode is set. [7.727348] rk_gmac-dwmac ff54.ethernet: PTP uses main clock [7.728039] rk_gmac-dwmac ff54.ethernet: phy regulator is not available yet, deferred probing [7.733519] dwmmc_rockchip ff50.mmc: IDMAC supports 32-bit address mode. [7.734230] dwmmc_rockchip ff50.mmc: Using internal DMA controller. [7.734853] dwmmc_rockchip ff50.mmc: Version ID is 270a [7.735489] dwmmc_rockchip ff50.mmc: DW MMC controller at irq 39,32 bit host data width,256 deep fifo [7.735865] dwmmc_rockchip ff52.mmc: IDMAC supports 32-bit address mode. [7.736367] rk_gmac-dwmac ff54.ethernet: IRQ eth_wake_irq not found [7.737051] dwmmc_rockchip ff52.mmc: Using internal DMA controller. [7.737638] rk_gmac-dwmac ff54.ethernet: IRQ eth_lpi not found [7.738227] dwmmc_rockchip ff52.mmc: Version ID is 270a [7.739317] dwmmc_rockchip ff52.mmc: DW MMC controller at irq 40,32 bit host data width,256 deep fifo [7.740225] rk_gmac-dwmac ff54.ethernet: force_sf_dma_mode is ignored if force_thresh_dma_mode is set. [7.742033] rk_gmac-dwmac ff54.ethernet: PTP uses main clock [7.743327] rk_gmac-dwmac ff54.ethernet: phy regulator is not available yet, deferred probing [7.777307] rk808-regulator rk808-regulator: there is no dvs0 gpio [7.778604] rk808-regulator rk808-regulator: there is no dvs1 gpio On previous message[ref 2] , it seems Ethernet port is correctly detected with correct parameters because ... ansible@hn-rock64-130:~$ sudo mii-tool --verbose if-prod if-prod: negotiated 1000baseT-FD flow-control, link ok product info: vendor 00:e0:4c or 00:07:32, model 17 rev 6 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control link partner: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control As a result, it is not very clear for me why there is one warning message ([ref 2]) ? Any ideas or suggestions will be appreciated (!) Cordialement -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1004566: wesnoth-1.16-data: '/usr/share/icons/HighContrast/scalable/apps/wesnoth-icon.svg', which is also in package wesnoth-1.14-data 1:1.14.17-2
Package: wesnoth-1.16-data Version: 1:1.16.1-1 Severity: grave Tags: a11y Justification: renders package unusable Dear Maintainer, During the upgrade from wesnoth-1.14 to wesnoth-1.16 in sid, I got the following message: Unpacking wesnoth-1.16-data (1:1.16.1-1) ... dpkg: error processing archive /var/cache/apt/archives/wesnoth-1.16-data_1%3a1.16.1-1_all.deb (--unpack): trying to overwrite '/usr/share/icons/HighContrast/scalable/apps/wesnoth-icon.svg', which is also in package wesnoth-1.14-data 1:1.14.17-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) It broke the upgrade in the middle. I guess it will be solved in first removing wesnoth-1.14* packages and running an 'apt --fix-broken install'. Regards, Jean-Marc -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wesnoth-1.16-data depends on: ii fonts-adf-oldania 0.20190904-2 ii fonts-dejavu-core 2.37-2 ii fonts-dejavu-extra2.37-2 ii fonts-droid-fallback 1:6.0.1r16-1.1 ii fonts-lato2.0-2.1 wesnoth-1.16-data recommends no packages. Versions of packages wesnoth-1.16-data suggests: iu wesnoth-1.16-music 1:1.16.1-1
Bug#959125: xdg-desktop-portal-gtk: does not provide implementations for org.freedesktop.impl.portal.{ScreenCast,RemoteDesktop}
hi Pedro, On Wed, 29 Apr 2020 18:48:53 +0100 Simon McVittie wrote: Control: block -1 by 954022 On Wed, 29 Apr 2020 at 17:13:08 +0100, Pedro Ângelo wrote: > looking upstream, there's an issue reported about xdg-desktop-portal-gtk not > instantiating the ScreenCast and RemoteDesktop interfaces on Ubuntu It needs a newer version of pipewire (see #954022). > it seems to never return from the call to `createSession` The error behaviour when not everything needed is available is also not great (it should fail cleanly with an error rather than waiting forever). I'm not sure whether that's an xdg-desktop-portal or xdg-desktop-portal-gtk bug. smcv Simon said it needed a new pipewire version mentioning this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954022 This is fixed since 5/9/20. Can you check if the bug persists ? And close the bug if it is okay ? Regards, -- Jean-Marc OpenPGP_signature Description: OpenPGP digital signature
Bug#998087: arm64+virtio: "No device for installation media was detected" error
Package: debian-installer Severity: normal Tags: d-i X-Debbugs-Cc: jmran...@hotmail.com Dear Maintainer, Environment: - physical hardware is a Mac with an M1 processor, running MacOS - VM provided by QEMU-6.1.0 + patches for that processor, hidden in the hombrew installer for QEMU - using qemu-system-aarch64 - so arm64 VM on an arm64 physical CPU - reproduced with both debian-11.1.0-arm64-netinst.iso and today's debian-testing-arm64-netinst.iso - the ISO is made visible inside QEMU via its "-cdrom" command-line argument, which makes it visible under /dev/vda in Debian's installer - for simplification, no other virtual hard disk exist - Debian's normal "non-graphical, non-expert" install mode is used Error: - At installation step 4 (Detect and mount installation media), the installer fails to detect the ISO, and states "No device for installation media was detected". Solution: - to "Load drivers from removable media?", answer no - to "Manually select a module and device for installation media, answer yes - to "Module needed for accessing the installation media", select "none" - enter "/dev/vda" (or "/dev/vda1") as the device file to use - installation media is now detected, and installation continues. Would it make sense to add the various /dev/vd? to the list of locations already automatically probed? Thanks.
Bug#763192: closed by Salvatore Bonaccorso (Re: Bug#763192: [LXC] [nfsd] kernel crash when running nfs-kernel-server in one LXC Container)
/home
/dev/mapper/vg_vm_nfs_260-lv_var_log19423579682100217
45% /var/log
/dev/mapper/vg_vm_nfs_260-lv_var_lib12678611643105682
10% /var/lib
/dev/mapper/vg_vm_nfs_260-lv_var_cache 37260768377280474
20% /var/cache
/dev/mapper/vg_vm_nfs_260-lv_var_lib_apt721392 155928513000
24% /var/lib/apt
/dev/mapper/vg_vm_nfs_260-lv_nfs_home 59600812 18687568 37855992
34% /srv
tmpfs 196624 56196568
1% /run
tmpfs 51200 5120
0% /run/lock
tmpfs 393240 40393200
1% /dev/shm
ansible@vm-nfs-260:~$
ansible@vm-nfs-260:~$ cat /etc/debian_version
10.9
ansible@vm-nfs-260:~$ pstree -anp
init,1
|-rpcbind,662 -w -h vm-nfs-260-service
|-rpc.statd,671 --state-directory-path /var/lib/nfs --port 32766
--outgoing-port 32765 --name vm-nfs-260-service
|-rpc.idmapd,680
|-rpc.mountd,742 --state-directory-path /var/lib/nfs --manage-gids
--port 32767 --num-threads=6
| |-rpc.mountd,745 --state-directory-path /var/lib/nfs
--manage-gids --port 32767 --num-threads=6
| |-rpc.mountd,746 --state-directory-path /var/lib/nfs
--manage-gids --port 32767 --num-threads=6
| |-rpc.mountd,747 --state-directory-path /var/lib/nfs
--manage-gids --port 32767 --num-threads=6
| |-rpc.mountd,748 --state-directory-path /var/lib/nfs
--manage-gids --port 32767 --num-threads=6
| |-rpc.mountd,749 --state-directory-path /var/lib/nfs
--manage-gids --port 32767 --num-threads=6
| `-rpc.mountd,750 --state-directory-path /var/lib/nfs
--manage-gids --port 32767 --num-threads=6
|-syslog-ng,764
| `-syslog-ng,765 -p /var/run/syslog-ng.pid --no-caps
|-cron,788
|-monit,804 -c /etc/monit/monitrc
| |-{monit},9259
| |-{monit},9260
| `-(verify_rpc_stat,10086)
|-getty,808 115200 console
`-sshd,32294
`-sshd,10079
`-sshd,10081
`-bash,10082
`-pstree,10107 -anp
ansible@vm-nfs-260:~$
Only ssh, monit, syslog are running with one sysvinit init
( no systemd !)
ansible@vm-nfs-260:~$ ip route ls
default via 192.168.24.254 dev et-user
192.168.22.0/24 dev et-serv proto kernel scope link src 192.168.22.136
192.168.24.0/24 dev et-user proto kernel scope link src 192.168.24.136
192.168.25.0/24 dev et-admi proto kernel scope link src 192.168.25.136
ansible@vm-nfs-260:~$
Of course, all configuration files are 100% compatible with Debian Buster.
ansible@vm-nfs-260:~$ cat /etc/default/nfs-kernel-server |grep -v "#"
|grep -v ^$
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--state-directory-path /var/lib/nfs --manage-gids --port
32767 --num-threads=6"
NEED_SVCGSSD="no"
ansible@vm-nfs-260:~$
ansible@vm-nfs-260:~$ cat /etc/exports |grep -v "#" |grep -v ^$
/srv/nfs/home
localhost(rw,secure_locks,insecure,no_subtree_check,no_all_squash,async,no_root_squash)
/srv/nfs/home
192.168.22.0/24(rw,secure_locks,insecure,no_subtree_check,no_all_squash,async,root_squash)
-
Step 3: nfs clien side
---
For client side, i am running nfs client on amd64, armhf and arm64
architecture, either on one real physical target, either on one
LXC container.
For example, following configuration is done on one LXC arm64 bullseye
arm64 target
jean-marc@vm-bullseye-arm64-280:~$ df
Sys. de fichiers
blocs de 1K Utilisé Disponible Uti% Monté sur
/dev/mapper/vg_vm_bullseye_arm64_280-lv_rootfs
11886710847 99133 10% /
none
4920492 0% /dev
udev
180652401806524 0% /dev/dri
/dev/mapper/vg_vm_bullseye_arm64_280-lv_usr
5981956 44397361218636 79% /usr
/dev/mapper/vg_vm_bullseye_arm64_280-lv_var
206112 5011 186151 3% /var
/dev/mapper/vg_vm_bullseye_arm64_280-lv_tmp
138697 1554 126822 2% /tmp
/dev/mapper/vg_vm_bullseye_arm64_280-lv_home
118867 3256 106724 3% /home
/dev/mapper/vg_vm_bullseye_arm64_280-lv_var_log
19423566707 113192 38% /var/log
/dev/mapper/vg_vm_bullseye_arm64_280-lv_var_lib
12678648031 69294 41% /var/lib
/dev/mapper/vg_vm_bullseye_arm64_280-lv_var_cache
991512 196272 727656 22% /var/cache
/dev/mapper/vg_vm_bullseye_arm64_280-lv_var_lib_apt
721392 279148 389780 42% /var/lib/apt
tmpfs
390880 736 390144 1% /run
tmpfs
51200 5120 0% /run/lock
tmpfs
781760 16 781744 1% /dev/shm
tmpfs
3908800 390880 0% /run/user/1
vm-nfs-260-service.sub-dns-lapiteau.TLD.jml:/srv/nfs/home/jean-marc
59600896 18687616 37856000 34% /nfs-home/jean-marc
jean-marc@vm-bullseye-arm64-280:~$ uname -a
Linux vm-bullseye-arm64-280 5.10.0-0.bpo.5-arm64 #1 SMP Debian
5.10.24-1~bpo10+1 (2021-03-29) aarch64 GNU/Linux
jean-marc@vm-bullseye-arm64-280:~$ cat /etc/debian_version
bullseye/sid
jean-marc@vm-bullseye-arm64-280:~$
-
best regards
---
Bug#983808: fancontrol: pwmconfig should validate permissions before reading.
Package: fancontrol Version: 1:3.6.0-7 Severity: important X-Debbugs-Cc: jean-m...@spaggiari.org When running pwmconfig on a Dell Precision 5530, it fails to read /sys/class/hwmon/hwmon6/pwm1_enable. Indeed, this file is write only (--w---). Therefore the script it throwing an error: Found the following PWM controls: hwmon6/pwm1 current value: 128 cat: hwmon6/pwm1_enable: Permission non accordée cat: hwmon6/pwm1_enable: Permission non accordée /usr/sbin/pwmconfig: ligne 164 : [: : nombre entier attendu comme expression cat: hwmon6/pwm1_enable: Permission non accordée /usr/sbin/pwmconfig: ligne 187 : [: : nombre entier attendu comme expression cat: hwmon6/pwm1_enable: Permission non accordée /usr/sbin/pwmconfig: ligne 195 : [: : nombre entier attendu comme expression hwmon6/pwm1 stuck to 128 Manual control mode not supported, skipping hwmon6/pwm1. hwmon6/pwm2 current value: 128 Giving the fans some time to reach full speed... Found the following fan sensors: hwmon6/fan1_input current speed: 5126 RPM hwmon6/fan2_input current speed: 5086 RPM The resulting /etc/fancontrol file is almost empty: # cat /etc/fancontrol # Configuration file generated by pwmconfig, changes will be lost INTERVAL=10 DEVPATH= DEVNAME= FCTEMPS= FCFANS= MINTEMP= MAXTEMP= MINSTART= MINSTOP= And then the service fails to restart: mar 01 16:50:45 precision5530 systemd[1]: Starting Cleanup of Temporary Directories... ░░ Subject: L'unité (unit) systemd-tmpfiles-clean.service a commencé à démarrer ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ L'unité (unit) systemd-tmpfiles-clean.service a commencé à démarrer. mar 01 16:50:45 precision5530 su[2434]: (to root) jmspaggi on pts/0 mar 01 16:50:45 precision5530 su[2434]: pam_unix(su:session): session opened for user root(uid=0) by (uid=0) mar 01 16:50:45 precision5530 systemd[1]: systemd-tmpfiles-clean.service: Succeeded. ░░ Subject: Unit succeeded ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state. mar 01 16:50:45 precision5530 systemd[1]: Finished Cleanup of Temporary Directories. ░░ Subject: L'unité (unit) systemd-tmpfiles-clean.service a terminé son démarrage ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ L'unité (unit) systemd-tmpfiles-clean.service a terminé son démarrage, avec le résultat done. mar 01 16:54:25 precision5530 wpa_supplicant[776]: wlp59s0: CTRL-EVENT-SIGNAL- CHANGE above=1 signal=-49 noise=-96 txrate=175500 mar 01 16:58:10 precision5530 systemd[1]: Starting fan speed regulator... ░░ Subject: L'unité (unit) fancontrol.service a commencé à démarrer ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ L'unité (unit) fancontrol.service a commencé à démarrer. mar 01 16:58:10 precision5530 fancontrol[2697]: Loading configuration from /etc/fancontrol ... mar 01 16:58:10 precision5530 fancontrol[2697]: Some mandatory settings missing, please check your config file! mar 01 16:58:10 precision5530 systemd[1]: fancontrol.service: Control process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ An ExecStartPre= process belonging to unit fancontrol.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. mar 01 16:58:10 precision5530 systemd[1]: fancontrol.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ The unit fancontrol.service has entered the 'failed' state with result 'exit-code'. mar 01 16:58:10 precision5530 systemd[1]: Failed to start fan speed regulator. ░░ Subject: L'unité (unit) fancontrol.service a échoué ░░ Defined-By: systemd ░░ Support: https://www.debian.org/support ░░ ░░ L'unité (unit) fancontrol.service a échoué, avec le résultat failed. Before trying to read the file, the script should check for the permissions, and if not allowed, should take the right decision. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE=fr_CA:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fancontrol depends on: ii init-system-helpers 1.60 ii lsb-base 11.1.0 fancontrol recommends no packages. fancontrol suggests no packages.
Bug#972245: openjdk-11-jre-headless: WARNING: tempfile is deprecated; consider using mktemp instead.
Package: openjdk-11-jre-headless Version: 11.0.10+9-1 Followup-For: Bug #972245 Dear Maintainer, Still getting the warning about tempfile in today's upgrade. $ dpkg-query --control-show openjdk-11-jre-headless postinst | grep tempfile log=$(tempfile) log=$(tempfile) Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openjdk-11-jre-headless depends on: ii ca-certificates-java 20190909 ii java-common 0.72 ii libasound21.2.4-1.1 ii libc6 2.31-9 ii libcups2 2.3.3op1-7 ii libfontconfig12.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgcc-s1 10.2.1-6 ii libharfbuzz0b 2.7.4-1 ii libjpeg62-turbo 1:2.0.5-2 ii liblcms2-22.12~rc1-2 ii libnss3 2:3.60-1 ii libpcsclite1 1.9.0-1 ii libstdc++610.2.1-6 ii libx11-6 2:1.7.0-2 ii libxext6 2:1.3.3-1.1 ii libxi62:1.7.10-1 ii libxrender1 1:0.9.10-1 ii libxtst6 2:1.2.3-1 ii util-linux2.36.1-6 ii zlib1g1:1.2.11.dfsg-2 openjdk-11-jre-headless recommends no packages. Versions of packages openjdk-11-jre-headless suggests: ii fonts-dejavu-extra 2.37-2 pn fonts-indic pn fonts-ipafont-gothic pn fonts-ipafont-mincho pn fonts-wqy-microhei | fonts-wqy-zenhei ii libnss-mdns0.14.1-2 -- no debconf information
Bug#663255: Nous avons mis à jour notre webmail zimbra pour mieux vous servir.
Nous avons mis à jour notre webmail zimbra pour mieux vous servir. Pour profiter de ce service et continuer à utiliser votre compte zimbra, il vous est demandé de vérifier votre compte.Cliquez ici et vérifiez votre compte.
Bug#976640: git: git - trying to install git failed due to unmet dependencies
This was due to a system setting. Correcting the problem allowed me to install git without problem. Sorry for that. I'll close this bug report. Regards, -- Jean-Marc OpenPGP_signature Description: OpenPGP digital signature
Bug#976640: git: git - trying to install git failed due to unmet dependencies
Package: git Version: 1:2.28.0-1 Severity: normal File: git Dear Maintainer, Trying to install git on my Debian testing system failed due to unmet dependencies. git seems to strictly depend on git-man git-man >> 1:2.28.0 but testing only contains 2.29.2-1 which leads to an impossible installation. Example : $ env LANG=C sudo apt install git Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: git : Depends: git-man (< 1:2.28.0-.) but 1:2.29.2-1 is to be installed E: Unable to correct problems, you have held broken packages. $ env LANG=C apt policy git-man git-man: Installed: (none) Candidate: 1:2.29.2-1 Version table: 1:2.29.2+next.20201030-1 1 1 https://mirror.as35701.net/debian experimental/main amd64 Packages 1:2.29.2-1 990 990 https://mirror.as35701.net/debian testing/main amd64 Packages 500 https://mirror.as35701.net/debian unstable/main amd64 Packages Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages git depends on: pn git-man ii libc62.31-5 ii libcurl3-gnutls 7.72.0-1 pn liberror-perl ii libexpat12.2.10-1 ii libpcre2-8-0 10.34-7 ii perl 5.32.0-5 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages git recommends: ii ca-certificates 20200601 ii less 551-2 ii openssh-client [ssh-client] 1:8.4p1-3 ii patch2.7.6-6 Versions of packages git suggests: ii gettext-base 0.19.8.1-10 pn git-cvs pn git-daemon-run | git-daemon-sysvinit pn git-doc pn git-el pn git-email pn git-gui pn git-mediawiki pn git-svn pn gitk pn gitweb
Bug#973883: [apt-cacher-ng] bad exit code (=0) instead (<>0) if Check permissions of /var/log/apt-cacher-ng
Package: apt-cacher-ng
Version: 3.2.1-1
Severity: grave
Dear maintainers,
It seems there is one bad exit code issue (=0) when trying to start
démon if internal check is bad. (/etc/init.d/apt-cacher-ng start)
ansible@srv-apt-cache-400:~$ dpkg -l |grep apt-cache
ii apt-cacher-ng 3.2.1-1 amd64
caching proxy server for software repositories
ansible@srv-apt-cache-400:~$ uname -a
Linux srv-apt-cache-400 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1
(2020-10-18) x86_64 GNU/Linux
ansible@srv-apt-cache-400:~$ cat /etc/debian_version
10.6
ansible@srv-apt-cache-400:~$ pstree -anp
init,1
|-sshd,682
| |-sshd,717
| | `-sshd,719
| `-sshd,11014
| `-sshd,11016
| `-bash,11017
| `-pstree,11964 -anp
|-getty,696 38400 tty2
|-getty,697 38400 tty3
|-getty,698 38400 tty4
|-monit,7389 -c /etc/monit/monitrc
| |-{monit},7390
| |-{monit},7913
| `-(bash,11655)
|-syslog-ng,9901
| `-syslog-ng,9902 -p /var/run/syslog-ng.pid --no-caps
`-cron,17286
ansible@srv-apt-cache-400:~$ sudo /etc/init.d/apt-cacher-ng start
[] Starting apt-cacher-ng: apt-cacher-ngProblem creating log files.
Check permissions of the log directory, //var/log/apt-cacher-ng
failed!
ansible@srv-apt-cache-400:~$ echo $?
0
ansible@srv-apt-cache-400:~$
And, of course, this is true, because ...
ansible@srv-apt-cache-400:~$ sudo ls -altr /var/log/apt-cacher-ng
total 2
drwx-- 2 root root 1024 Nov 6 14:34 .
drwxr-xr-x 8 root root 1024 Nov 6 14:52 ..
Thanks in advance to correct this issue. In my use case, because i am
using Ansible to make deployment, it is then not possible to detect this
bug (because exit code = 0) in one automatic way
Best regards
Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»
Bug already reported 2 times: initramfs-tools: update-initramfs should not store temporary files on /boot https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929424 pigz: abort: write error on (No space left on device) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960181 The 2 bugs are all marked as DONE. In the second bug #960181, when marking it as DONE on Sun, 10 May 2020, Ben Hutchings reported this comment : « There may be a bug here, in that the /boot partition was too small. That has been fixed in the installer, but unfortunately we don't have a general way to grow the partition on installed systems. ». No way to check if there is a way to avoid this in the 2 scripts mkinitramfs and update-initramfs ? Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpekgKDlgIMh.pgp Description: PGP signature
Bug#970355: syslog-ng : segfault at 0 ip 00007fa46a2bf7b2 sp 00007ffed353fb30 error 6 in libsyslog-ng-3.19.so.0.0.0[7fa46a2a9000+5a000]
Package: syslog-ng Version: 3.19.1-5 Severity: grave Dear maintainers, On amd64, i have following error ==> /var/log/syslog-ng/current_logs/BY_FACILITY.kern.notice.log <== 2020-09-15T08:25:53+02:00 s_dev_kernel_kmsg@asus-190 kernel: 6,35313,87037029084,-;syslog-ng[10311]: segfault at 0 ip 7fa46a2bf7b2 sp 7ffed353fb30 error 6 in libsyslog-ng-3.19.so.0.0.0[7fa46a2a9000+5a000] 2020-09-15T08:25:53+02:00 s_dev_kernel_kmsg@asus-190 kernel: 6,35314,87037029092,-;Code: e8 c3 9b fe ff 4c 89 e7 e8 eb dc fe ff 48 89 c7 e8 23 ca fe ff e9 15 ff ff ff 66 0f 1f 44 00 00 48 8b 83 f0 00 00 00 48 89 df 00 00 00 00 00 48 83 c4 08 5b 5d 41 5c 41 5d e9 b9 fc ff ff 66 About the curent configuration, there is no disc full... ansible@asus-190:~$ df Sys. de fichiers blocs de 1K Utilisé Disponible Uti% Monté sur udev 6015136 06015136 0% /dev tmpfs 1213460 29241210536 1% /run /dev/mapper/vg_debian-lv_rootfs_crypt 927000134336 728360 16% / /dev/mapper/vg_debian-lv_usr 7511832 57149601434140 80% /usr tmpfs5120 4 5116 1% /run/lock tmpfs 2426900 571242369776 3% /dev/shm /dev/mapper/vg_debian-lv_boot 463826193086 242273 45% /boot /dev/sda2 98304 39534 58770 41% /boot2/efi /dev/sdb1 191551 5199 186352 3% /boot/efi /dev/sdb5 2817056 1688848 965392 64% /debian_rescue /dev/mapper/vg_debian-lv_home80388420 741911722894992 97% /home /dev/mapper/vg_debian-lv_tmp 943128 82076 795928 10% /tmp /dev/mapper/vg_debian-lv_var 860591 7183 808724 1% /var /dev/mapper/vg_debian-lv_var_cache 863632140484 667980 18% /var/cache /dev/mapper/vg_debian-lv_var_lib 959909 69128 842002 8% /var/lib /dev/mapper/vg_debian-lv_var_lib_apt 1057092431004 563584 44% /var/lib/apt /dev/mapper/vg_debian-lv_var_log 560120225992 293132 44% /var/log cgroup6067296 06067296 0% /sys/fs/cgroup /dev/sde3 862818100 120357724 698561908 15% /mnt/backup ansible@asus-190:~$ My syslog configuration is in attached file Thanks in advance for your help Jean-Marc syslog-ng-debian-buster-10.5-bug-segfault.tar.gz Description: application/gzip
Bug#970337: fonts-open-sans: warning when purging the package
Apparently, there are already other bugs related to similar problems. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898522 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920928 These 3 have references to each other. This one has not : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909541 And this bug is being worked on: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040 Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpZHxB5UhTcJ.pgp Description: PGP signature
Bug#970337: fonts-open-sans: warning when purging the package
Package: fonts-open-sans Version: 1.11-1 Severity: normal Dear Maintainer, apt mentioned fonts-open-sans was automatically installed but not needed anymore. I then ran an apt autoremove --purge. During the purge, I got a warning because dpkg was not able to remove the directory /usr/share/fonts/truetype/open-sans, this directory being not empty. Indeed, it still contained one file named .uuid: $ ls -la /usr/share/fonts/truetype/open-sans total 12 drwxr-xr-x 2 root root 4096 sep 14 21:30 . drwxr-xr-x 21 root root 4096 jui 12 22:14 .. -rw-r--r-- 1 root root 36 fév 13 2020 .uuid Maybe something to manage in one of the control files. Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#970140: gramps: Python3.8 SyntaxWarning: "is not" with a literal.
Followed up upstream: https://gramps-project.org/bugs/view.php?id=11641 Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpB6jufWn8Ea.pgp Description: PGP signature
Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles
I removed the 3 packages : sudo apt purge webext-noscript webext-privacy-badger webext-ublock-origin-firefox I then installed the 3 extensions from the Firefox add-ons repo. And everything works fine. So, most probably, FF80 checks add-ons and removes/disables old ones. I Cc this to webext maintainers. Maybe they are not aware of this problem. Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpvmfi2MLoVI.pgp Description: PGP signature
Bug#970140: gramps: Python3.8 SyntaxWarning: "is not" with a literal. in exportvcalendar.py:205 during installation
Package: gramps Version: 5.1.3-1 Severity: normal Dear Maintainer, Since Python3.8, "is" and "is not" checks produce SyntaxWarning when used with certains type of literals. See release notes: https://docs.python.org/3.8/whatsnew/3.8.html#changes-in-python-behavior "The compiler now produces a SyntaxWarning when identity checks (is and is not) are used with certain types of literals (e.g. strings, numbers). These can often work by accident in CPython, but are not guaranteed by the language spec. The warning advises users to use equality tests (== and !=) instead." Please, replace "is not" with "!=" in /usr/lib/python3/dist-packages/gramps/plugins/export/exportvcalendar.py - line 205. Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gramps depends on: ii gir1.2-gtk-3.03.24.22-1 ii librsvg2-22.48.8+dfsg-1 ii python3 3.8.2-3 ii python3-bsddb36.2.7-1.1+b1 ii python3-gi3.36.1-1 ii python3-gi-cairo 3.36.1-1 ii xdg-utils 1.1.3-2 Versions of packages gramps recommends: ii gir1.2-geocodeglib-1.0 3.26.2-2 ii gir1.2-gexiv2-0.10 0.12.1-1 ii gir1.2-osmgpsmap-1.01.1.0-7 ii graphviz2.42.2-4 ii python3-icu 2.5-1 Versions of packages gramps suggests: ii fonts-freefont-ttf20120503-10 ii gir1.2-goocanvas-2.0 2.0.4-1 ii gir1.2-gtkspell3-3.0 3.0.10-1 ii python3-numpy 1:1.19.1-1 ii python3-pil 7.2.0-1 pn rcs -- no debconf information
Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies:
Julien, Indeed, it is not possible to install this package, because I put a rule of no installation in the APT preference file following dark stories of Nvidia drivers ... Afterdeleting the /etc/apt/preferences.d/preferences_debian_v_10_buster_no_driver_nouveau_but_driver_nvidia.pref file, everything is OK: ansible@vm-buster-amd64-190:~$ dpkg -l |grep xbase-client ii xbase-clients1:7.7+19 all miscellaneous X clients - metapackage ansible@vm-buster-amd64-190:~$ cat /etc/debian_version 10.5 ansible@vm-buster-amd64-190:~$ Sorry for the inconvenience, please close this bug Le 09/09/2020 à 11:07, Jean-Marc LACROIX a écrit : Le 09/09/2020 à 10:53, Julien Cristau a écrit : Control: tag -1 moreinfo unreproducible On Wed, Sep 09, 2020 at 10:23:53AM +0200, Jean-Marc LACROIX wrote: Package: xbase-clients Version: 3.2-2 That is not the version of xbase-clients in any Debian release as far as I can tell. Severity: grave Dear maintainers, It seems there is a dependancy issue (?) when trying to install xbase-clients Debian buster 10.5 package. The installation in done on one LXC container running with sysvinit, and without droping any Posix 1003.2 capabilities. ansible@vm-buster-amd64-190:~$ sudo apt install xbase-clients [...] xbase-clients : Depends: x11-utils but it is not going to be installed [...] ansible@vm-buster-amd64-190:~$ sudo apt install libglx-mesa0 [...] libglx-mesa0 : Depends: libgl1-mesa-dri but it is not going to be installed E: Unable to correct problems, you have held broken packages. ansible@vm-buster-amd64-190:~$ sudo apt install libglx-mesa-dri Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package libglx-mesa-dri The above said libgl1-mesa-dri, not libglx-mesa-dri. Cheers, Julien Julien, Sorry for my bad copy/paste (!) ansible@vm-buster-amd64-190:~$ apt-cache policy libglx-mesa-dri N: Unable to locate package libglx-mesa-dri ansible@vm-buster-amd64-190:~$ deborphan ansible@vm-buster-amd64-190:~$ apt-cache policy xbase-clients xbase-clients: Installed: (none) Candidate: 1:7.7+19 Version table: 1:7.7+19 500 500 http://ftp.de.debian.org/debian buster/main amd64 Packages 90 http://ftp.de.debian.org/debian stretch/main amd64 Packages ansible@vm-buster-amd64-190:~$ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: (none) Candidate: 18.3.6-2+deb10u1 Version table: 18.3.6-2+deb10u1 500 500 http://ftp.de.debian.org/debian buster/main amd64 Packages 13.0.6-1+b2 90 90 http://ftp.de.debian.org/debian stretch/main amd64 Packages ansible@vm-buster-amd64-190:~$ sudo apt install -y libgl1-mesa-dri Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libdrm-nouveau2 (>= 2.4.66) but it is not installable E: Unable to correct problems, you have held broken packages. ansible@vm-buster-amd64-190:~$ Best regards -- Cordialement -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr-- -
Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies:
Le 09/09/2020 à 10:53, Julien Cristau a écrit : Control: tag -1 moreinfo unreproducible On Wed, Sep 09, 2020 at 10:23:53AM +0200, Jean-Marc LACROIX wrote: Package: xbase-clients Version: 3.2-2 That is not the version of xbase-clients in any Debian release as far as I can tell. Severity: grave Dear maintainers, It seems there is a dependancy issue (?) when trying to install xbase-clients Debian buster 10.5 package. The installation in done on one LXC container running with sysvinit, and without droping any Posix 1003.2 capabilities. ansible@vm-buster-amd64-190:~$ sudo apt install xbase-clients [...] xbase-clients : Depends: x11-utils but it is not going to be installed [...] ansible@vm-buster-amd64-190:~$ sudo apt install libglx-mesa0 [...] libglx-mesa0 : Depends: libgl1-mesa-dri but it is not going to be installed E: Unable to correct problems, you have held broken packages. ansible@vm-buster-amd64-190:~$ sudo apt install libglx-mesa-dri Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package libglx-mesa-dri The above said libgl1-mesa-dri, not libglx-mesa-dri. Cheers, Julien Julien, Sorry for my bad copy/paste (!) ansible@vm-buster-amd64-190:~$ apt-cache policy libglx-mesa-dri N: Unable to locate package libglx-mesa-dri ansible@vm-buster-amd64-190:~$ deborphan ansible@vm-buster-amd64-190:~$ apt-cache policy xbase-clients xbase-clients: Installed: (none) Candidate: 1:7.7+19 Version table: 1:7.7+19 500 500 http://ftp.de.debian.org/debian buster/main amd64 Packages 90 http://ftp.de.debian.org/debian stretch/main amd64 Packages ansible@vm-buster-amd64-190:~$ apt-cache policy libgl1-mesa-dri libgl1-mesa-dri: Installed: (none) Candidate: 18.3.6-2+deb10u1 Version table: 18.3.6-2+deb10u1 500 500 http://ftp.de.debian.org/debian buster/main amd64 Packages 13.0.6-1+b2 90 90 http://ftp.de.debian.org/debian stretch/main amd64 Packages ansible@vm-buster-amd64-190:~$ sudo apt install -y libgl1-mesa-dri Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libdrm-nouveau2 (>= 2.4.66) but it is not installable E: Unable to correct problems, you have held broken packages. ansible@vm-buster-amd64-190:~$ Best regards
Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies:
ge: * Pin: release o=Debian,l=Debian,n=buster-update Pin-Priority: 500 Package: * Pin: release o=Debian,l=Debian,n=buster Pin-Priority: 500 Package: * Pin: release o=Debian,l=Debian,n=buster-backports Pin-Priority: 100 Package: * Pin: release o=Debian,l=Debian,n=stretch Pin-Priority: 90 Package: * Pin: release o=Debian,l=Debian,n=bullseye Pin-Priority: 80 Package: * Pin: release o=Debian,l=Debian,n=sid Pin-Priority: 70 Package: * Pin: release o=Debian,l=Debian,n=experimental Pin-Priority: 60 Package: dhcpcd5 Pin: release * Pin-Priority: -1 Package: libdrm-nouveau2 Pin: release * Pin-Priority: -1 Package: xserver-xorg-video-nouveau Pin: release * Pin-Priority: -1 Package: elogind Pin: release * Pin-Priority: -1 Package: systemd Pin: release * Pin-Priority: -1 ansible@vm-buster-amd64-190:~$ deborphan ansible@vm-buster-amd64-190:~$ ansible@vm-buster-amd64-190:~$ df Filesystem1K-blocksUsed Available Use% Mounted on /dev/mapper/vg_vm_buster_amd64_190-lv_rootfs 1188673746 106234 4% / none492 0 492 0% /dev /dev/mapper/vg_vm_buster_amd64_190-lv_usr 5981956 1432032 4226340 26% /usr /dev/mapper/vg_vm_buster_amd64_190-lv_var2061122546 188616 2% /var /dev/mapper/vg_vm_buster_amd64_190-lv_tmp1386971555 126821 2% /tmp /dev/mapper/vg_vm_buster_amd64_190-lv_home 1188671586 108394 2% /home /dev/mapper/vg_vm_buster_amd64_190-lv_var_log194235 20889 159010 12% /var/log /dev/mapper/vg_vm_buster_amd64_190-lv_var_lib126786 27093 90232 24% /var/lib /dev/mapper/vg_vm_buster_amd64_190-lv_var_cache 991512 102452 821476 12% /var/cache /dev/mapper/vg_vm_buster_amd64_190-lv_var_lib_apt 1108144 277092 756712 27% /var/lib/apt tmpfs 12134601464 1211996 1% /run tmpfs 5120 0 5120 0% /run/lock tmpfs 2816840 24 2816816 1% /dev/shm ansible@vm-buster-amd64-190:~$ ansible@asus-190:~ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.7.0-2-amd64 root=UUID=11e74815-f8fa-4913-bf10-3267c6c59138 ro log_buf_len=1M fsck.mode=force fsck.repair=yes pcie_aspm=off add.acpi=off ipv6.disable=1 loglevel=7 apparmor=0 selinux=0 cgroup_enable=memory Best regards Jean-Marc
Bug#969174: Fixed here [was Re: Bug#969174: firefox: FF80 seems to have
broken all add-ons on existing profiles] Message-Id: <20200904132941.cacb8887fd7ab7f486ccc...@6jf.be> In-Reply-To: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 04 Sep 2020 01:33:53 +0200 Christoph Anton Mitterer wrote: > On Thu, 2020-09-03 at 22:43 +0200, Ra=C3=BAl S=C3=A1nchez Siles wrote: > > Fortunately 80.0.1-1 came around and this bug has been somehow > > fixed or not exposed. This is what I can tell so far. Let me know if > > I can provide any more helpful information. >=20 > yes... that seems to fix it... Not on my system. I though it was fixed because just after the upgrade to FF 80.0.1-1, the extensions re-appeared. But at the second start, they were gone again. It is a bit the same behavior that with FF80.0.1. If you disable+re-enable the extensions, they are back. But they disappear after briefly appearing once you re-start FF. > Cheers, > Chris. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpRC1DJ2d8Hb.pgp Description: PGP signature
Bug#969174: firefox: FF80 seems to have broken all add-ons on existing profiles
On Fri, 28 Aug 2020 17:18:44 +0200 Christoph Anton Mitterer wrote: > Package: firefox > Version: 80.0-1 > Severity: normal > > > Hi. > > It seems that with FF80 all addons are broken in existing profiles. They're > shown > in the add-ons list, but e.g. their icons aren’t in the menu. > > E.g. ublock origin, noscript also don't seem to work... so it's not just a > display > issue. > > Cheers, > Chris I am facing the same issue. Add-ons installed, shown as active in the add-ons' menu but not appearing in the FF bar as they were with FF79. One remark nevertheless : if I open the page about:support and click on the button "Refresh Firefox..." and then re-start Firefox, I got the icon of the add-ons I installed through Debian packages meaning noScript, privacy Badger and uBlock Origin in the FF bar. Chris, can you try this ? But after browsing the web and re-starting FF, they disappeared again. Chris, Mike, did you install add-ons from Debian or directly from FF repository ? Maybe the current versions are not compatible with FF80. My installed packages: Packages Version =-= firefox 80.0-1 webext-noscript 10.1.9.6-2 webext-privacy-badger 2020.7.21-1 webext-ublock-origin 1.28.0+dfsg-1 Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt https://6jf.be/keys/ED0B8558.txt pgpu5zBlp8Xi7.pgp Description: PGP signature
Bug#963548: Same issue
Facing the same issue as the others here. Let me know whatever information you need and I will be happy to share it. @t460s:~$ chromium --disable-extensions [15182:15182:0709/070125.715925:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [15144:15201:0709/070141.969650:ERROR:database.cc(1632)] Passwords sqlite error 2067, errno 0: UNIQUE constraint failed: logins.origin_url, logins.username_element, logins.username_value, logins.password_element, logins.signon_realm, sql: INSERT INTO logins (origin_url, action_url, username_element, username_value, password_element, password_value, submit_element, signon_realm, preferred, date_created, blacklisted_by_user, scheme, password_type, times_used, form_data, date_synced, display_name, icon_url, federation_url, skip_zero_click, generation_upload_status, possible_username_pairs, id, date_last_used) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) libpng warning: iCCP: known incorrect sRGB profile Received signal 11 SEGV_MAPERR 7f013c130c67 #0 0x56170c781469 (/usr/lib/chromium/chromium+0x51f9468) #1 0x56170c6df193 (/usr/lib/chromium/chromium+0x5157192) #2 0x56170c780ff1 (/usr/lib/chromium/chromium+0x51f8ff0) #3 0x7f946ce40730 (/usr/lib/x86_64-linux-gnu/libpthread-2.28.so+0x1272f) #4 0x7f9466d2cd48 (/usr/lib/x86_64-linux-gnu/libc-2.28.so+0x7fd47) #5 0x7f9466d2fa58 (/usr/lib/x86_64-linux-gnu/libc-2.28.so+0x82a57) #6 0x7f9466d3156a __libc_malloc #7 0x56170c798bee operator new() #8 0x7f9466fa63cd std::__cxx11::basic_string<>::reserve() #9 0x7f9466f9a845 std::__cxx11::basic_stringbuf<>::overflow() #10 0x7f9466fa49cb std::basic_streambuf<>::xsputn() #11 0x7f9466f95b34 std::__ostream_insert<>() #12 0x56170c7817b9 (/usr/lib/chromium/chromium+0x51f97b8) #13 0x56170c781844 (/usr/lib/chromium/chromium+0x51f9843) #14 0x56170c6f19d2 (/usr/lib/chromium/chromium+0x51699d1) #15 0x56170c6f3b1e (/usr/lib/chromium/chromium+0x516bb1d) #16 0x56170ae5c62a (/usr/lib/chromium/chromium+0x38d4629) #17 0x56170ae5c67e (/usr/lib/chromium/chromium+0x38d467d) #18 0x56170a50298f (/usr/lib/chromium/chromium+0x2f7a98e) #19 0x56170ae16559 (/usr/lib/chromium/chromium+0x388e558) #20 0x56170ae1679e (/usr/lib/chromium/chromium+0x388e79d) #21 0x56170ae5fe67 (/usr/lib/chromium/chromium+0x38d7e66) #22 0x56170ae8bac2 (/usr/lib/chromium/chromium+0x3903ac1) #23 0x56170ae8bd7e (/usr/lib/chromium/chromium+0x3903d7d) #24 0x56170ae5c63f (/usr/lib/chromium/chromium+0x38d463e) #25 0x56170ae5c67e (/usr/lib/chromium/chromium+0x38d467d) #26 0x56170a50298f (/usr/lib/chromium/chromium+0x2f7a98e) #27 0x56170a7b9f53 (/usr/lib/chromium/chromium+0x3231f52) #28 0x56170aae4e22 (/usr/lib/chromium/chromium+0x355ce21) #29 0x56170c8b4aff (/usr/lib/chromium/chromium+0x532cafe) #30 0x56170c8bb274 (/usr/lib/chromium/chromium+0x5333273) #31 0x56170c8b916d (/usr/lib/chromium/chromium+0x533116c) #32 0x56170c8b7e2c (/usr/lib/chromium/chromium+0x532fe2b) #33 0x56170c8b0913 (/usr/lib/chromium/chromium+0x5328912) #34 0x56170c8cc77b (/usr/lib/chromium/chromium+0x534477a) #35 0x56170c8cca41 (/usr/lib/chromium/chromium+0x5344a40) #36 0x56170c8cc040 (/usr/lib/chromium/chromium+0x534403f) #37 0x56170a7a2e26 (/usr/lib/chromium/chromium+0x321ae25) #38 0x56170a7a294c (/usr/lib/chromium/chromium+0x321a94b) #39 0x56170a79ed51 (/usr/lib/chromium/chromium+0x3216d50) #40 0x56170a79561b (/usr/lib/chromium/chromium+0x320d61a) #41 0x56170a787f1b (/usr/lib/chromium/chromium+0x31fff1a) #42 0x56170a787c03 (/usr/lib/chromium/chromium+0x31ffc02) #43 0x56170a7a69a6 (/usr/lib/chromium/chromium+0x321e9a5) #44 0x56170c79e28a (/usr/lib/chromium/chromium+0x5216289) #45 0x7f946b2579ba (/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6.0.2+0x229b9) #46 0x7f946b258537 event_base_loop #47 0x56170c79e510 (/usr/lib/chromium/chromium+0x521650f) #48 0x56170c73dc05 (/usr/lib/chromium/chromium+0x51b5c04) #49 0x56170c715a1d (/usr/lib/chromium/chromium+0x518da1c) #50 0x56170aa80d93 (/usr/lib/chromium/chromium+0x34f8d92) #51 0x56170c7543f7 (/usr/lib/chromium/chromium+0x51cc3f6) #52 0x56170c7910ce (/usr/lib/chromium/chromium+0x52090cd) #53 0x7f946ce35fa3 start_thread #54 0x7f9466da64cf clone r8: 0024 r9: 7f943c30 r10: 0020 r11: 7f943c80 r12: 7f943c80 r13: 0021 r14: 7f943c20 r15: 0081 di: 7f943c20 si: 0021 bp: 7f013c130c5f bx: dx: 0020 ax: 7f013c130c5f cx: 7f943c125cd0 sp: 7f94577faa00 ip: 7f9466d2cd48 efl: 00010206 cgf: 002b0033 erf: 0004 trp: 000e msk: cr2: 7f013c130c67 [end of stack trace] Calling _exit(1). Core file will not be generated.
Bug#956885: gnome: gdm fails to start up after bullseye upgrade
On Thu, 16 Apr 2020 11:30:01 -0500 "Julio C. Ortega" wrote: > I can confirm also that downgrading gir1.2-gnomedesktop-3.0 to 3.34.2-2 > solved the problem. You can also force the next version of gnome-shell from unstable. sudo apt install gnome-shell/unstable mutter/unstable gnome-shell-extensions/unstable Include gnome-shell-extensions in your upgrade to avoid problems with missing dependencies. And give it a try with the option --simulate before to be sure it won't break something. > Julio C. Ortega Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpoNNqPZcVvR.pgp Description: PGP signature
Bug#956910: Bug fixes with packages from unstable
Install the next version of gnome-shell from unstable: sudo apt install gnome-shell/unstable mutter/unstable gnome-shell-extensions/unstable Include gnome-shell-extensions in your upgrade to avoid problems with missing dependencies. And give it a try with the option --simulate before to be sure it won't break something. Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpgFTeNEF7SN.pgp Description: PGP signature
Bug#956885: gnome: gdm fails to start up after bullseye upgrade
On Thu, 16 Apr 2020 11:30:01 -0500 "Julio C. Ortega" wrote: > I can confirm also that downgrading gir1.2-gnomedesktop-3.0 to 3.34.2-2 > solved the problem. You can also force the next version of gnome-shell from unstable. sudo apt install gnome-shell/unstable mutter/unstable gnome-shell-extensions/unstable Include gnome-shell-extensions in your upgrade to avoid problems with missing dependencies. And give it a try with the option --simulate before to be sure it won't break something. > Julio C. Ortega Jean-Marc
Bug#953832: ImportError: /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block
Hi Faidon, Do you need some help ? Do you think reporting this upstream can help ? Also, I am not really used to report bug or help in bug triage. So, tell me if I am doing something wrong. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgp4u_NAgJZM2.pgp Description: PGP signature
Bug#952811: [apt-cacher-ng] 500 Bad redirection (path)
Hello, Thanks for your reply. Please, find in attached file my configuration. Best regards Jean-Marc Le 3/6/20 à 7:45 AM, Eduard Bloch a écrit : Control: tags 952811 +moreinfo Hallo, * Jean-Marc LACROIX [Sat, Feb 29 2020, 05:25:53PM]: Package: apt-cacher-ng Version: 3.2-2 Severity: grave That's hardly grave because not clearly reproducible. But I have seen this 502 in development a couple of times, appeared and disappeared without trace. Please share your config, i.e. all *.conf and *.backend files. Best regards, Eduard. -- Wo man am meisten drauf erpicht, grad das bekommt man meistens nicht. -- Wilhelm Busch config_apt_cacher_ng_debian_buster_10.3_arch_armhf.tar.gz Description: application/gzip
Bug#952811: [apt-cacher-ng] 500 Bad redirection (path)
Package: apt-cacher-ng Version: 3.2-2 Severity: grave Dear maintainers, It seems there is a cache or DNS issue (?) sometimes when trying to access from my internal local network to public Internet. My clients targets are either armhf, either arm64 or amd64 running Debian Buster 10.3 Apt-cacher-ng is running on armhf target With following file : /etc/apt/apt.conf.d/apt_conf_proxy_http_https ansible@pinebook:~$ grep -i Acqui /etc/apt/apt.conf.d/apt_conf_proxy_http_https Acquire::http::proxy "http://srv-apt-cacher-110-service:3142;; Acquire::https::proxy "http://srv-apt-cacher-110-service:3142;; ansible@pinebook:~$ grep -iR ^Deb /etc/apt/ /etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb http://ftp.debian.org/debian/ buster main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb http://ftp.fr.debian.org/debian buster-updates main contrib non-free /etc/apt/sources.list.d/armbian_apt_v_10_buster.list:deb http://apt.armbian.com buster main buster-utils buster-desktop /etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb http://ftp.debian.org/debian/ stretch main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb http://security.debian.org buster/updates main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb http://ftp.fr.debian.org/debian buster-backports main contrib non-free test 1: The issue ... - ansible@pinebook:~$ sudo apt update Hit:1 http://ftp.fr.debian.org/debian buster-backports InRelease Err:2 http://apt.armbian.com buster InRelease 500 Bad redirection (path) [IP: 192.168.54.79 3142] Hit:3 http://ftp.debian.org/debian buster InRelease Hit:4 http://security.debian.org buster/updates InRelease Hit:5 http://ftp.fr.debian.org/debian buster-updates InRelease Ign:6 http://ftp.debian.org/debian stretch InRelease Hit:7 http://ftp.debian.org/debian stretch Release Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. W: Failed to fetch http://apt.armbian.com/dists/buster/InRelease 500 Bad redirection (path) [IP: 192.168.54.79 3142] W: Some index files failed to download. They have been ignored, or old ones used instead. ansible@pinebook:~$ ansible@pinebook:~$ host 192.168.54.79 79.54.168.192.in-addr.arpa domain name pointer srv-apt-cacher-110-service.noip.jml. test 2: no more issue (!) - ansible@pinebook:~$ sudo sed -i -e 's/Acquire/#Acquire/g' /etc/apt/apt.conf.d/apt_conf_proxy_http_https ansible@pinebook:~$ sudo apt update Hit:1 http://ftp.fr.debian.org/debian buster-backports InRelease Hit:2 http://ftp.fr.debian.org/debian buster-updates InRelease Hit:3 http://ftp.debian.org/debian buster InRelease Ign:4 http://ftp.debian.org/debian stretch InRelease Hit:5 http://security.debian.org buster/updates InRelease Hit:6 http://ftp.debian.org/debian stretch Release Hit:7 https://apt.armbian.com buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. ansible@pinebook:~$ Thanks in advance for your help Best regards
Bug#951479: [files list file for package 'base-passwd' is missing final newline] [debian buster 10.3]
Hi, Le 2/17/20 à 2:27 PM, Guillem Jover a écrit : Hi! On Mon, 2020-02-17 at 13:48:30 +0100, Jean-Marc LACROIX wrote: Le 2/17/20 à 12:18 PM, Simon Richter a écrit : On Mon, Feb 17, 2020 at 10:31:25AM +0100, Jean-Marc LACROIX wrote: dpkg: unrecoverable fatal error, aborting: files list file for package 'base-passwd' is missing final newline E: Sub-process /usr/bin/dpkg returned an error code (2) That file is generated by dpkg on installation, so it's not the package's fault. The "final newline" check is a safety check to see that the file name is complete, guarding against write errors. You need to reinstall the base-passwd package, possibly after deleting /var/lib/dpkg/info/base-passwd.list, and I'd also run a file system check for good measure, because that state should only happen on write errors (although I remember it also sometimes happened when /var was full, but IIRC that got fixed). I'm very doubtful this would be a dpkg problem (but you never know). This looks like "hardware"/emulation (memory, disk, etc) or filesystem related, perhaps due to a damaged fsys due to a system crash or similar. Please find the test results root@vm-ssh-190-factory:~# ls -altr /var/lib/dpkg/info/base-passwd.list -rw-r--r-- 1 root root 1120 Feb 12 18:33 /var/lib/dpkg/info/base-passwd.list root@vm-ssh-190-factory:~# mv /var/lib/dpkg/info/base-passwd.list /var/lib/dpkg/info/base-passwd.list.orig Could you attach the old base-passwd.list file? yes, in attached file. root@srv-firewall-190-factory:~# ls /var/lib/dpkg/info/base-files.* -altr -rwxr-xr-x 1 root root 3110 Feb 1 17:09 /var/lib/dpkg/info/base-files.postinst -rw-r--r-- 1 root root 1897 Feb 1 17:09 /var/lib/dpkg/info/base-files.md5sums -rw-r--r-- 1 root root 114 Feb 1 17:09 /var/lib/dpkg/info/base-files.conffiles -rw-r--r-- 1 root root 1784 Feb 12 18:26 /var/lib/dpkg/info/base-files.list.orig.20714 -rw-r--r-- 1 root root 1784 Feb 17 13:53 /var/lib/dpkg/info/base-files.list Please note also that after second installation, result is the same ... root@srv-firewall-190-factory:~# diff /var/lib/dpkg/info/base-files.list /var/lib/dpkg/info/base-files.list.orig.20714 Binary files /var/lib/dpkg/info/base-files.list and /var/lib/dpkg/info/base-files.list.orig.20714 differ About the /var , my disc organisation is root@vm-ssh-190-factory:~# df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg_vm_ssh_190-lv_rootfs 117M 31M 78M 29% / none 492K 0 492K 0% /dev /dev/mapper/vg_vm_ssh_190-lv_usr 685M 471M 165M 75% /usr /dev/mapper/vg_vm_ssh_190-lv_var 66M 1.3M 60M 3% /var /dev/mapper/vg_vm_ssh_190-lv_tmp 66M 1.3M 60M 3% /tmp /dev/mapper/vg_vm_ssh_190-lv_home 27M 779K 24M 4% /home /dev/mapper/vg_vm_ssh_190-lv_var_log 190M 14M 163M 8% /var/log /dev/mapper/vg_vm_ssh_190-lv_var_lib 124M 7.5M 108M 7% /var/lib /dev/mapper/vg_vm_ssh_190-lv_var_cache461M 226M 207M 53% /var/cache /dev/mapper/vg_vm_ssh_190-lv_var_lib_apt 618M 263M 311M 46% /var/lib/apt tmpfs 1.2G 28K 1.2G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 2.7G 0 2.7G 0% /dev/shm What's the filesystem type on /var/lib? Also the used size there seems suspiciously very tiny? Or perhaps you've got very few packages installed I guess. All FS mount point are ext4 on LVM2 on SSD disc root@srv-firewall-190-factory:~# mount /dev/mapper/vg_srv_firewall_190-lv_rootfs on / type ext4 (rw,noatime,nodiratime,discard,commit=600) none on /dev type tmpfs (rw,relatime,size=492k,mode=755) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) /dev/mapper/vg_srv_firewall_190-lv_usr on /usr type ext4 (rw,noatime,nodiratime,discard,commit=600) /dev/mapper/vg_srv_firewall_190-lv_var on /var type ext4 (rw,noatime,nodiratime,discard,commit=600) /dev/mapper/vg_srv_firewall_190-lv_tmp on /tmp type ext4 (rw,noatime,nodiratime,discard,commit=600) /dev/mapper/vg_srv_firewall_190-lv_home on /home type ext4 (rw,noatime,nodiratime,discard,commit=600) /dev/mapper/vg_srv_firewall_190-lv_var_log on /var/log type ext4 (rw,noatime,nodiratime,discard,commit=600) /dev/mapper/vg_srv_firewall_190-lv_var_lib on /var/lib type ext4 (rw,noatime,nodiratime,discard,commit=600) /dev/mapper/vg_srv_firewall_190-lv_var_cache on /var/cache type ext4 (rw,noatime,nodiratime,discard,commit=600) /dev/mapper/vg_srv_firewall_190-lv_var_lib_apt on /var/lib/apt type ext4 (rw,noatime,nodiratime,discard,commit=600) devpts on /dev/console type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666,max=10) devpts on /dev/ptmx type devpts (rw,nosuid,n
Bug#951479: [files list file for package 'base-passwd' is missing final newline] [debian buster 10.3]
+deb10u1_all.deb ... Unpacking gnupg (2.2.12-1+deb10u1) ... Selecting previously unselected package libapt-inst2.0:amd64. Preparing to unpack .../14-libapt-inst2.0_1.8.2_amd64.deb ... Unpacking libapt-inst2.0:amd64 (1.8.2) ... Selecting previously unselected package python-apt-common. Preparing to unpack .../15-python-apt-common_1.8.4.1_all.deb ... Unpacking python-apt-common (1.8.4.1) ... Selecting previously unselected package python-apt. Preparing to unpack .../16-python-apt_1.8.4.1_amd64.deb ... Unpacking python-apt (1.8.4.1) ... Setting up libksba8:amd64 (1.3.5-2) ... Setting up libnpth0:amd64 (1.6-1) ... Setting up libassuan0:amd64 (2.5.2-1) ... Setting up libapt-inst2.0:amd64 (1.8.2) ... Setting up gnupg-l10n (2.2.12-1+deb10u1) ... Setting up python-apt-common (1.8.4.1) ... Setting up gpgconf (2.2.12-1+deb10u1) ... Setting up gpg (2.2.12-1+deb10u1) ... Setting up gnupg-utils (2.2.12-1+deb10u1) ... Setting up pinentry-curses (1.1.0-2) ... Setting up gpg-agent (2.2.12-1+deb10u1) ... Setting up gpgsm (2.2.12-1+deb10u1) ... Setting up dirmngr (2.2.12-1+deb10u1) ... Setting up gpg-wks-server (2.2.12-1+deb10u1) ... Setting up gpg-wks-client (2.2.12-1+deb10u1) ... Setting up gnupg (2.2.12-1+deb10u1) ... Setting up python-apt (1.8.4.1) ... Processing triggers for libc-bin (2.28-10) ... root@vm-ssh-190-factory:~# About the /var , my disc organisation is root@vm-ssh-190-factory:~# df -h FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg_vm_ssh_190-lv_rootfs 117M 31M 78M 29% / none 492K 0 492K 0% /dev /dev/mapper/vg_vm_ssh_190-lv_usr 685M 471M 165M 75% /usr /dev/mapper/vg_vm_ssh_190-lv_var 66M 1.3M 60M 3% /var /dev/mapper/vg_vm_ssh_190-lv_tmp 66M 1.3M 60M 3% /tmp /dev/mapper/vg_vm_ssh_190-lv_home 27M 779K 24M 4% /home /dev/mapper/vg_vm_ssh_190-lv_var_log 190M 14M 163M 8% /var/log /dev/mapper/vg_vm_ssh_190-lv_var_lib 124M 7.5M 108M 7% /var/lib /dev/mapper/vg_vm_ssh_190-lv_var_cache461M 226M 207M 53% /var/cache /dev/mapper/vg_vm_ssh_190-lv_var_lib_apt 618M 263M 311M 46% /var/lib/apt tmpfs 1.2G 28K 1.2G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 2.7G 0 2.7G 0% /dev/shm that's why i don't think this is the root cause of the problem Could you give more information, on the nature of this bug, because I must now make sure that all my equipment park which is managed under Ansible is installed correctly. From Debian's point of view, there is no more bug (good news!), From my point of view, I have to find a technical solution that works in 100% of cases ... Le 2/17/20 à 12:18 PM, Simon Richter a écrit : Hi, On Mon, Feb 17, 2020 at 10:31:25AM +0100, Jean-Marc LACROIX wrote: dpkg: unrecoverable fatal error, aborting: files list file for package 'base-passwd' is missing final newline E: Sub-process /usr/bin/dpkg returned an error code (2) That file is generated by dpkg on installation, so it's not the package's fault. The "final newline" check is a safety check to see that the file name is complete, guarding against write errors. You need to reinstall the base-passwd package, possibly after deleting /var/lib/dpkg/info/base-passwd.list, and I'd also run a file system check for good measure, because that state should only happen on write errors (although I remember it also sometimes happened when /var was full, but IIRC that got fixed). Simon
Bug#951479: [files list file for package 'base-passwd' is missing final newline] [debian buster 10.3]
Package: python-apt Version: 1.8.4.1 Dear maintainers, It seems there is a dependency issue (?) when installing python-apt as indicated in following trace. On previous Debian buster (10.2), this issue does not exist. root@vm-ssh-190-factory:~# cat /etc/debian_version 10.3 root@vm-ssh-190-factory:~# grep -iR deb /etc/apt/sources* |grep -v "#" /etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb http://security.debian.org buster/updates main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb http://ftp.fr.debian.org/debian buster-backports main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb http://ftp.fr.debian.org/debian buster-updates main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb http://ftp.debian.org/debian/ stretch main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb http://ftp.debian.org/debian/ buster main contrib non-free root@vm-ssh-190-factory:~# grep -R P /etc/apt/preferences* |grep -v "#" /etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Package: systemd /etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Pin: release * /etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Package: elogind /etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Pin: release * /etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Package: dhcpcd5 /etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Pin: release * /etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster/updates /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 920 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster-update /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 910 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 900 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster-backports /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=stretch /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 400 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=testing /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=unstable /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1 root@vm-ssh-190-factory:~# apt update && apt upgrade Hit:1 http://ftp.fr.debian.org/debian buster-backports InRelease Hit:2 http://ftp.debian.org/debian buster InRelease Hit:4 http://ftp.fr.debian.org/debian buster-updates InRelease Ign:5 http://ftp.debian.org/debian stretch InRelease Hit:3 http://security-cdn.debian.org buster/updates InRelease Hit:6 http://ftp.debian.org/debian stretch Release Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@vm-ssh-190-factory:~# root@vm-ssh-190-factory:~# dpkg -l |grep -v ii Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--=== root@vm-ssh-190-factory:~# root@vm-ssh-190-factory:~# uname -a Linux vm-ssh-190-factory 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux
Bug#950707: closed by Sergey B Kirpichev (reply to skirpic...@gmail.com) (Re: [monit] Depends: libcrypt1 (>= 1:4.1.0) but it is not going to be installed)
Dear Sergey, It seems that on Debian 10.3, monit is now available without any issue...because ansible@srv-mmonit-110:~$ dpkg -l |grep monit ansible@srv-mmonit-110:~$ cat /etc/debian_version 10.3 I have taken into account your recommendation regarding the backports package. Now, my preferences are : ansible@srv-mmonit-110:~$ grep P /etc/apt/preferences.d/preferences_debian_v_10_buster.pref |grep -v "#" Package: * Pin: release o=Debian,l=Debian,n=buster/updates Pin-Priority: 920 Package: * Pin: release o=Debian,l=Debian,n=buster-update Pin-Priority: 910 Package: * Pin: release o=Debian,l=Debian,n=buster Pin-Priority: 900 Package: * Pin: release o=Debian,l=Debian,n=buster-backports Pin-Priority: 905 Package: * Pin: release o=Debian,l=Debian,n=stretch Pin-Priority: 400 Package: * Pin: release o=Debian,l=Debian,n=testing Pin-Priority: -1 Package: * Pin: release o=Debian,l=Debian,n=unstable Pin-Priority: -1 Package: udev Pin: release o=Debian,l=Debian,n=* Pin-Priority: -1 and when i install monit ansible@srv-mmonit-110:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ansible@srv-mmonit-110:~$ deborphan ansible@srv-mmonit-110:~$ sudo apt install monit Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: exim4 | postfix | mail-transport-agent The following NEW packages will be installed: monit 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 296 kB of archives. After this operation, 762 kB of additional disk space will be used. Get:1 http://ftp.debian.org/debian stretch/main armhf monit armhf 1:5.20.0-6+deb9u1 [296 kB] Fetched 296 kB in 0s (9105 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package monit. (Reading database ... 20938 files and directories currently installed.) Preparing to unpack .../monit_1%3a5.20.0-6+deb9u1_armhf.deb ... Unpacking monit (1:5.20.0-6+deb9u1) ... Setting up monit (1:5.20.0-6+deb9u1) ... [ ok ] Starting daemon monitor: monit. ansible@srv-mmonit-110:~$ I don't understand why i install the stretch release, (because pining!), but for my point of view, the problem is solved ! Regards Le 2/5/20 à 2:09 PM, Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report which was filed against the monit package: #950707: [monit] Depends: libcrypt1 (>= 1:4.1.0) but it is not going to be installed It has been closed by Sergey B Kirpichev (reply to skirpic...@gmail.com). 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 Sergey B Kirpichev (reply to skirpic...@gmail.com) by replying to this email.
Bug#950707: [monit] Depends: libcrypt1 (>= 1:4.1.0) but it is not going to be installed
Package: monit Version: 1:5.20.0-6 Severity: grave Dear maintainers, Many thanks for the packaging of this application on Debian Gnu/Linux. It seems there is one dependancy change (?) on recent monit Buster 10.2. As a result, it is not more possible to install monit Debian package on Buster 10.2 release. My configuration is ansible@srv-nfs-110:~$ cat /etc/debian_version 10.2 ansible@srv-nfs-110:~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux 10 (buster) Release:10 Codename: buster ansible@srv-nfs-110:~$ uname -a Linux srv-nfs-110 4.14.150-odroidxu4 #1 SMP PREEMPT Mon Oct 28 07:56:57 CET 2019 armv7l GNU/Linux ansible@srv-nfs-110:~$ grep deb /etc/apt/sources.list.d/* |grep -v "#" /etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb http://ftp.fr.debian.org/debian buster-backports main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb http://ftp.debian.org/debian/ buster main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_next.list:deb http://ftp.debian.org/debian/ bullseye main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb http://ftp.debian.org/debian/ stretch main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb http://security.debian.org buster/updates main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb http://ftp.fr.debian.org/debian buster-updates main contrib non-free ansible@srv-nfs-110:~$ grep P /etc/apt/preferences.d/preferences_debian_v_10_buster* |grep -v "#" /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster-update /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 901 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 900 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=buster-backports /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=stretch /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: 400 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=testing /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: * /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=unstable /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Package: udev /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin: release o=Debian,l=Debian,n=* /etc/apt/preferences.d/preferences_debian_v_10_buster.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Package: dhcpcd5 /etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Pin: release * /etc/apt/preferences.d/preferences_debian_v_10_buster_no_dhcpcd5.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Package: elogind /etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Pin: release * /etc/apt/preferences.d/preferences_debian_v_10_buster_no_elogind.pref:Pin-Priority: -1 /etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Package: systemd /etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Pin: release * /etc/apt/preferences.d/preferences_debian_v_10_buster_no_systemd.pref:Pin-Priority: -1 ansible@srv-nfs-110:~$ ansible@srv-nfs-110:~$ deborphan ansible@srv-nfs-110:~$ dpkg -l |grep -v ii Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===--=== The issue ! ansible@srv-nfs-110:~$ sudo apt install monit Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable
Bug#950333: [apt-cacher-ng] disc full
Package: apt-cacher-ng Version: 3.2-2 Severity: important Dear maintainers, Many thanks for the packaging of this application (). Two questions about this application. After reading the documentation and many blogs on Internet, it seems not possible to set maximum size to the parameter : "CacheDir:" in configuration file. As a result, of course, after some times, this directory can be full. Of course it is possible to mount this directory to one dedicated disc mount point, but the issue is always the same, it depends of disc size (!). My dream is to specify one limit (!) in this parameter, with potential associated policy (optional) to manage automatically old files when disc is full for example. Q1: Is it possible ? Q2: Furthermore, it seems that when disc is full, then all clients can not download files when launching apt update/upgrade with following error : "Failed to update apt cache", perhaps due to [HTTP error, code: 503] in /var/log/apt-cacher-ng/apt-cacher.log ? Thanks in advance for your answers
Bug#949221: python3-enchant: Warning during the package installation: SyntaxWarning: "is" with a literal. Did you mean "=="?
Package: python3-enchant Version: 2.0.0-1 Severity: normal Dear Maintainer, Yesterday, during a full-upgrade, my Debian system automatically installed python3-enchant (2.0.0-1). During the package installation, I got a warning message: /usr/lib/python3/dist-packages/enchant/checker/CmdLineChecker.py:163: SyntaxWarning: "is" with a literal. Did you mean "=="? if index is 0: It seems with the last python 3 versions, this syntax starts to get warned about this being consider as a minor bug. Please, can you take this in charge ? Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-enchant depends on: ii libenchant1c2a 1.6.0-11.3 ii python3 3.7.5-3 python3-enchant recommends no packages. python3-enchant suggests no packages. -- no debconf information
Bug#901965: hid2hci.patch
Hi bluez maintainers, A person got in touch with debian-user-french people asking for help because she was facing the issue described in this bug report. I wonder if there is any progress on finding a solution ? For info, this problem is also mentionned in the bug report #889110 ([1]) (closed by Michael Biebl on 9 Feb 2018). And in the RedHat Bug 1563554 ([2]) suggesting a workaround by just adding in front of the line containing in the file /lib/udev/rules.d/97-hid2hci.rules. Can you, please, advice what is the best solution to, at least, mitigate the risk of being hit by this bug ? Specifying the ACTION like described in the RH bugreport or using the driver usbhid like in the Тут Root's proposed patch. And about further investigations, unfortunately, I cannot reproduce the bug and, then, I am not able to investigate further to know if it is really a driver or kernel bug. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt [1] https://bugs.debian.org/889110 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1563554 pgpMRzCyEtr6N.pgp Description: PGP signature
Bug#942050: gnome-shell: gnome shell does not take the org.gnome.desktop.peripherals.keyboard numlock-state into account
This problem seems to be solved in the last gnome-shell version (3.34.1+git20191024-1). You can close this bug report. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpuXLTRrWFC5.pgp Description: PGP signature
Bug#942272: gnome-shell: numlock state is reversed
Hi EdiD, I got numlock state problems too with this gnome-shell version. Mine were no similar to yours but seem to disappear with the last gnome-shell version (3.34.1+git20191024-1). Can you check if your problems still persist ? And confirm it in this bug report ? Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpTkKpcYvSeA.pgp Description: PGP signature
Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.
Wed, 23 Oct 2019 16:40:37 + wrote : Hi Mario, > Internal Use - Confidential > > In 1.3.2-5 the service is disabled by default (and also this issue should be > fixed). Okay. So, the bug can be closed, I guess. Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpwpc8u5Cvgq.pgp Description: PGP signature
Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.
Package: fwupd Version: 1.3.2-2 Severity: normal Dear Maintainer, On my PC, fwupd-refresh.service failed to start. $ systemctl status fwupd-refresh.service ● fwupd-refresh.service - Refresh fwupd metadata and update motd Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2019-10-23 16:06:35 CEST; 2h 13min ago Docs: man:fwupdmgr(1) Process: 4608 ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=0/SUCCESS) Process: 4624 ExecStart=/usr/bin/fwupdmgr get-updates --log 85-fwupd (code=exited, status=1/FAILURE) Main PID: 4624 (code=exited, status=1/FAILURE) oct 23 16:06:35 svrname systemd[1]: Starting Refresh fwupd metadata and update motd... oct 23 16:06:35 svrname fwupdmgr[4608]: Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz oct 23 16:06:35 svrname fwupdmgr[4608]: Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc oct 23 16:06:35 svrname systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE oct 23 16:06:35 svrname systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. oct 23 16:06:35 svrname systemd[1]: Failed to start Refresh fwupd metadata and update motd. That's the service definition: $ systemctl cat fwupd-refresh.service # /lib/systemd/system/fwupd-refresh.service [Unit] Description=Refresh fwupd metadata and update motd Documentation=man:fwupdmgr(1) After=network.target network-online.target systemd-networkd.service NetworkManager.service connman.service [Service] Type=oneshot RuntimeDirectory=motd.d CacheDirectory=fwupdmgr RuntimeDirectoryPreserve=yes StandardError=null ExecStart=/usr/bin/fwupdmgr refresh ExecStart=/usr/bin/fwupdmgr get-updates --log 85-fwupd DynamicUser=yes RestrictAddressFamilies=AF_NETLINK AF_UNIX AF_INET AF_INET6 SystemCallFilter=~@mount ProtectKernelModules=yes ProtectControlGroups=yes RestrictRealtime=yes And about the runtime directory: $ ls -ld /run/motd.d lrwxrwxrwx 1 root root 14 oct 23 16:06 /run/motd.d -> private/motd.d $ ls -ld /run/private/ drwx-- 3 root root 60 oct 23 16:06 /run/private/ $ sudo ls -ld /run/private/motd.d drwxr-xr-x 2 62803 62803 40 oct 23 16:06 /run/private/motd.d $ sudo ls -l /run/private/motd.d total 0 Kind Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fwupd depends on: ii libarchive13 3.4.0-1 ii libc6 2.29-2 ii libefiboot137-2 ii libefivar1 37-2 ii libelf10.176-1.1 ii libfwupd2 1.3.2-2 ii libgcab-1.0-0 1.3-1 ii libglib2.0-0 2.62.1-1 ii libgnutls303.6.9-5 ii libgpg-error0 1.36-7 ii libgpgme11 1.13.1-1 ii libgudev-1.0-0 233-1 ii libgusb2 0.3.0-1 ii libjson-glib-1.0-0 1.4.4-2 ii libpolkit-gobject-1-0 0.105-26 ii libsmbios-c2 2.4.1-1 ii libsoup2.4-1 2.68.2-1 ii libsqlite3-0 3.30.1-1 ii libtss2-esys0 2.1.0-4+b1 ii libxmlb1 0.1.13-1 ii shared-mime-info 1.10-1 Versions of packages fwupd recommends: ii bolt 0.8-4 ii fwupd-amd64-signed [fwupd-signed] 1.3.2+2 ii python33.7.5-1 fwupd suggests no packages. -- no debconf information
Bug#942234: gdm3: the button «Shutdown» does not work anymore
Package: gdm3 Version: 3.34.0-2 Severity: normal Dear Maintainer, Since the last upgrade to GDM 3.34, the shutdown button does not work anymore. If I click on it, I get the popup window with the three buttons (Cancel, Reboot, Shutdown) but clicking on Reboot or Shutdown just close this popup window and does nothing more. Looking in /var/log/daemon.log, I found this message each time I use the GDM Shutdown option: Oct 12 20:43:19 machineName gnome-session-binary[11980]: WARNING: Shutdown failed: GDBus.Error:org.freedesktop.DBus.Error.InteractiveAuthorizationRequired: Interactive authentication required. Moreover, I also notice this in the systemctl status gdm.service output: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Sat 2019-10-12 15:00:24 CEST; 6h ago Process: 1008 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1020 (gdm3) Tasks: 3 (limit: 4915) Memory: 11.2M CGroup: /system.slice/gdm.service └─1020 /usr/sbin/gdm3 oct 12 20:29:01 machineName gdm3[1020]: Child process -9036 was already dead. oct 12 20:42:28 machineName gdm-launch-environment][11942]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) oct 12 20:43:09 machineName gdm-password][12188]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type oct 12 20:43:25 machineName gdm-password][12196]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type oct 12 20:43:31 machineName gdm-password][12196]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type oct 12 20:43:31 machineName gdm-password][12196]: gkr-pam: unable to locate daemon control file oct 12 20:43:31 machineName gdm-password][12196]: pam_unix(gdm-password:session): session opened for user jim by (uid=0) oct 12 20:43:34 machineName gdm3[1020]: Child process -11964 was already dead. oct 12 21:05:27 machineName gdm-launch-environment][14042]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) oct 12 21:05:44 machineName gdm3[1020]: Child process -14060 was already dead. Maybe something missing since the last upgrade from 3.30. Maybe it is because of the file /etc/securetty. It was in the package login since Buster but it is not present in this package in Bullseye anymore. Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdm3 depends on: ii accountsservice 0.6.45-2 ii adduser 3.118 ii dconf-cli 0.34.0-1 ii dconf-gsettings-backend 0.34.0-1 ii debconf [debconf-2.0] 1.5.73 ii gir1.2-gdm-1.03.34.0-2 ii gnome-session [x-session-manager] 3.34.1-1 ii gnome-session-bin 3.34.1-1 ii gnome-settings-daemon 3.34.0-3 ii gnome-shell 3.34.0-2 ii gnome-terminal [x-terminal-emulator] 3.34.0-1 ii gsettings-desktop-schemas 3.34.0-2 ii libaccountsservice0 0.6.45-2 ii libaudit1 1:2.8.5-2 ii libc6 2.29-2 ii libcanberra-gtk3-00.30-7 ii libcanberra0 0.30-7 ii libgdk-pixbuf2.0-02.38.2+dfsg-1 ii libgdm1 3.34.0-2 ii libglib2.0-0 2.62.1-1 ii libglib2.0-bin2.62.1-1 ii libgtk-3-03.24.12-1 ii libkeyutils1 1.6-6 ii libpam-modules1.3.1-5 ii libpam-runtime1.3.1-5 ii libpam-systemd242-7 ii libpam0g 1.3.1-5 ii librsvg2-common 2.44.14-1 ii libselinux1 2.9-2+b2 ii libsystemd0 242-7 ii libwrap0 7.6.q-28 ii libx11-6 2:1.6.8-1 ii libxau6 1:1.0.8-1+b2 ii libxcb1 1.13.1-2 ii libxdmcp6 1:1.1.2-3 ii lsb-base 11.1.0 ii mutter [x-window-manager] 3.34.0-4 ii policykit-1 0.105-26 ii procps2:3.3.15-2+b1 ii
Bug#942050: gnome-shell: gnome shell does not take the org.gnome.desktop.peripherals.keyboard numlock-state into account
On Wed, 09 Oct 2019 17:40:15 +0200 Jean-Marc wrote: > Package: gnome-shell > Version: 3.34.0-2 > Severity: normal > > Dear Maintainer, I would like to re-phrase : > Since the last upgrade from gnome-shell 3.30 to 3.34, the gnome-shell does > not take the gsettings org.gnome.desktop.peripherals.keyboard numlock-state > into account and always start with org.gnome.desktop.peripherals.keyboard > numlock-state set to false. I should have written : [...] and always start as if the value org.gnome.desktop.peripherals.keyboard numlock-state is set to false. It means, to be as clear as possible I can start with numlock-state set to true but the numpad will not render numbers. Hitting the numlock key changes the value of this setting and the behavior of the shell. Right now, the numlock-state value is false and the numpad returns numbers. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgphxaKb1AFVn.pgp Description: PGP signature
Bug#942071: [debian Buster] [armhf & arm64] [xarchiver] Depends: libgtk-3-0 (>= 3.0.0) but it is not going to be installed
Package: xarchiver Version: 1:0.5.4.14-1 Severity: grave Dear maintainers, It seems there is a dependency issue when installing xarchiver as indicated in following trace. My target is either armhf, either arm64 Debian Buster 10.1 My test conditions are ... ansible@vm-buster-armhf-110:~$ cat /etc/debian_version 10.1 ansible@vm-buster-armhf-110:~$ uname -a Linux vm-buster-armhf-110 4.14.141-odroidxu4 #12 SMP PREEMPT Wed Oct 2 00:24:32 CEST 2019 armv7l GNU/Linux ansible@vm-buster-armhf-110:~$ dpkg -l |grep -v ii Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--===--=== ansible@vm-buster-armhf-110:~$ deborphan ansible@vm-buster-armhf-110:~$ ansible@vm-buster-armhf-110:~$ grep deb /etc/apt/sources.list.d/* |grep -v "#" /etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb http://ftp.fr.debian.org/debian buster-backports main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb http://ftp.debian.org/debian/ buster main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb http://ftp.debian.org/debian/ stretch main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb http://security.debian.org buster/updates main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb http://ftp.fr.debian.org/debian buster-updates main contrib non-free ansible@vm-buster-armhf-110:~$ cat /etc/apt/preferences.d/preferences_* |grep -v "#" |grep -v "^$" Package: * Pin: release o=Debian,l=Debian,n=buster-update Pin-Priority: 901 Package: * Pin: release o=Debian,l=Debian,n=buster Pin-Priority: 900 Package: * Pin: release o=Debian,l=Debian,n=buster-backports Pin-Priority: -1 Package: * Pin: release o=Debian,l=Debian,n=stretch Pin-Priority: 400 Package: * Pin: release o=Debian,l=Debian,n=testing Pin-Priority: -1 Package: * Pin: release o=Debian,l=Debian,n=unstable Pin-Priority: -1 Package: udev Pin: release o=Debian,l=Debian,n=* Pin-Priority: -1 Package: dhcpcd5 Pin: release * Pin-Priority: -1 Package: systemd Pin: release * Pin-Priority: -1 ansible@vm-buster-armhf-110:~$ sudo apt update && sudo apt upgrade Hit:1 http://ftp.fr.debian.org/debian buster-backports InRelease Hit:2 http://ftp.fr.debian.org/debian buster-updates InRelease Hit:3 http://security.debian.org buster/updates InRelease Hit:4 http://ftp.debian.org/debian buster InRelease Ign:5 http://ftp.debian.org/debian stretch InRelease Hit:6 http://ftp.debian.org/debian stretch Release Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ansible@vm-buster-armhf-110:~$ ansible@vm-buster-armhf-110:~$ sudo apt install xarchiver Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xarchiver : Depends: libgtk-3-0 (>= 3.0.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ansible@vm-buster-armhf-110:~$ Please note that on target arm64, result is the same ansible@vm-buster-arm64-130:~$ sudo apt install xarchiver Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xarchiver : Depends: libgtk-3-0 (>= 3.0.0) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ansible@vm-buster-arm64-130:~$ uname -a Linux vm-buster-arm64-130 4.4.182-rockchip64 #1 SMP Fri Jun 28 17:34:00 CEST 2019 aarch64 GNU/Linux ansible@vm-buster-arm64-130:~$ Because my package pining is always available with the n-1 release (stretch), (Thanks to Debian preferences !), the proposed workaround for the moment is : sudo apt -t stretch install xarchiver Thanks in advance for your help... Best regards
Bug#942050: gnome-shell: gnome shell does not take the org.gnome.desktop.peripherals.keyboard numlock-state into account
Package: gnome-shell Version: 3.34.0-2 Severity: normal Dear Maintainer, Since the last upgrade from gnome-shell 3.30 to 3.34, the gnome-shell does not take the gsettings org.gnome.desktop.peripherals.keyboard numlock-state into account and always start with org.gnome.desktop.peripherals.keyboard numlock-state set to false. I set "org.gnome.desktop.peripherals.keyboard remember-numlock-state true" on my system. to keep the numlock-state to the same value reboot after reboot, session after session. So, when GDM starts, it remembers the last numlock-state. With gnome-shell 3.30, it was the same. Now, with gnome-shell 3.34, it always start with numlock-state set to false leading to strange behaviors. For example, if I leave the session with numlock on, when I re-open a new session, gsettings show this: $ gsettings list-recursively | grep keyboard.*numlock org.gnome.desktop.peripherals.keyboard remember-numlock-state true org.gnome.desktop.peripherals.keyboard numlock-state true and my numlock key on my keyboard is set to on too (with the led swtiched to on) but when I type on the numpad, I do not get numbers. I have to type on numlock key, swithing the led off to get my numpad working as it was on. For example, now, that's my setting: $ gsettings list-recursively | grep keyboard.*numlock org.gnome.desktop.peripherals.keyboard remember-numlock-state true org.gnome.desktop.peripherals.keyboard numlock-state false and the numpad with the led off gives numbers. I hope I am clear in my explanations. Regards, Jean-Marc -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.34.0-1 ii evolution-data-server3.34.0-3 ii gir1.2-accountsservice-1.0 0.6.45-2 ii gir1.2-atspi-2.0 2.34.0-3 ii gir1.2-freedesktop 1.62.0-2 ii gir1.2-gcr-3 3.33.4-2 ii gir1.2-gdesktopenums-3.0 3.34.0-2 ii gir1.2-gdm-1.0 3.34.0-2 ii gir1.2-geoclue-2.0 2.5.5-1 ii gir1.2-glib-2.0 1.62.0-2 ii gir1.2-gnomebluetooth-1.03.34.0-1 ii gir1.2-gnomedesktop-3.0 3.34.0-2 ii gir1.2-gtk-3.0 3.24.12-1 ii gir1.2-gweather-3.0 3.28.3-2 ii gir1.2-ibus-1.0 1.5.19-4+b1 ii gir1.2-mutter-5 3.34.0-4 ii gir1.2-nm-1.01.20.2-1 ii gir1.2-nma-1.0 1.8.22-2 ii gir1.2-pango-1.0 1.42.4-7 ii gir1.2-polkit-1.00.105-26 ii gir1.2-rsvg-2.0 2.44.14-1 ii gir1.2-soup-2.4 2.68.1-2 ii gir1.2-upowerglib-1.00.99.11-1 ii gjs 1.58.0-2 ii gnome-backgrounds3.34.0-1 ii gnome-settings-daemon3.34.0-3 ii gnome-shell-common 3.34.0-2 ii gsettings-desktop-schemas3.34.0-2 ii libatk-bridge2.0-0 2.34.0-3 ii libatk1.0-0 2.34.0-1 ii libc62.29-2 ii libcairo21.16.0-4 ii libcroco30.6.13-1 ii libecal-2.0-13.34.0-3 ii libedataserver-1.2-243.34.0-3 ii libgcr-base-3-1 3.33.4-2 ii libgdk-pixbuf2.0-0 2.38.2+dfsg-1 ii libgirepository-1.0-11.62.0-2 ii libgjs0g 1.58.0-2 ii libgles2 1.1.0-1+b1 ii libglib2.0-0 2.62.0-3 ii libglib2.0-bin 2.62.0-3 ii libgnome-autoar-0-0 0.2.3-2 ii libgstreamer1.0-01.16.1-1 ii libgtk-3-0 3.24.12-1 ii libical3 3.0.5-2 ii libjson-glib-1.0-0 1.4.4-2 ii libmutter-5-03.34.0-4 ii libnm0 1.20.2-1 ii libpango-1.0-0 1.42.4-7 ii libpangocairo-1.0-0
Bug#941908: gnome: unable to start gnome-shell, cursor only with no login
On Mon, 07 Oct 2019 14:26:28 -0500 william l-k wrote: > Thank you for your suggestions. I'll give it try and report back. gnome-shell 3.34 released to testing yesterday solving a similar issue (see https://bugs.debian.org/941782). Can you check if the problem you reported is also solved now after full-upgrading to the last testing version ? And in case it is, confirm it here ? Thank you for reporting this issue. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpOdldjbfrN_.pgp Description: PGP signature
Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed
Hi team,
It seems that now all is ok, because sysvinit is correctly installed on
Debian 10.1
ansible@pinebook:~$ dpkg -l |grep sysvini
ii sysvinit-core 2.93-8
arm64System-V-like init utilities
ii sysvinit-utils 2.93-8
arm64System-V-like utilities
ansible@pinebook:~$ cat /etc/debian_version
10.1
ansible@pinebook:~$ dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion
Architecture Description
+++-===-==--===
ansible@pinebook:~$ pstree -anp
init,1
|-systemd-udevd,540
|-syslog-ng,2611
| `-syslog-ng,2612 -p /var/run/syslog-ng.pid --no-caps
|-cron,2690
|-dbus-daemon,2724 --system
|-elogind-daemon,2748
|-lightdm,2776
| |-{lightdm},2794
| |-{lightdm},2802
| |-Xorg,6815 :0 -seat seat0 -auth /var/run/lightdm/root/:0
-nolisten tcp vt7 -novtswitch
| | |-{Xorg},6821
| | |-{Xorg},6822
| | |-{Xorg},6823
| | |-{Xorg},6824
| | `-{Xorg},6829
| |-lightdm,6834 --session-child 17 20
| | |-{lightdm},6835
| | |-{lightdm},6836
| | `-lightdm-gtk-gre,6837
| | |-{lightdm-gtk-gre},6838
| | |-{lightdm-gtk-gre},6839
| | |-{lightdm-gtk-gre},6840
| | |-{lightdm-gtk-gre},6841
| | |-{lightdm-gtk-gre},6842
| | `-{lightdm-gtk-gre},6866
| `-lightdm,6867 --session-child 13 20
|-sshd,2881
| |-sshd,3493
| | `-sshd,3495
| | `-bash,3496
| `-sshd,6517
| `-sshd,6519
| `-bash,6520
| `-pstree,7009 -anp
ansible@pinebook:~$ dpkg -l |grep libsoup2
ii libsoup2.4-1:arm64 2.64.2-2
arm64HTTP library implementation in C
-- Shared library
So for my point of vue, my proposal is to close this bug ...
Thanks for your help
Best regards
Le 10/09/2019 à 13:35, Dmitry Bogatov a écrit :
[2019-09-08 17:53] Jean-Marc LACROIX
> Please:
>
> * Try installing something else, like `tor'. I expect you will get
> similar error (`tor' depends on libsystemd0, sigh)
ansible@pinebook:~$ sudo apt install tor
[...]
Okay, tor installs fine with your apt-pinning. My guess was wrong.
ansible@pinebook:~$ dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion
Architecture Description
+++-===---===
ansible@pinebook:~$ dpkg -l |grep systemd
ii dbus-user-session
1.12.16-1arm64simple interprocess messaging
system (systemd --user integration)
ii libpam-systemd:arm64241-5
arm64system and service manager - PAM module
ii libsystemd0:arm64 241-5
arm64systemd utility library
ii syslog-ng-mod-journal 3.19.1-5
arm64Enhanced system logging daemon
(systemd journal plugin)
ii systemd 241-5
arm64system and service manager
ii systemd-sysv241-5
arm64system and service manager - SysV links
Okay, on this stage you have systemd as pid1 implementation.
[...]
Now, according Debian doc, i try to install sysvinit
Which exactly doc? I guess it needs to be adjusted.
ansible@pinebook:~$ sudo apt install sysvinit sysvinit-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package sysvinit is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
sysvinit-core:armhf systemd-sysv:armhf sysvinit-core systemd-sysv
E: Package 'sysvinit' has no installation candidate
It seems on Debian 10.1, there is now one new package name ?
[...]
There were no package renaming at least last year.
ansible@pinebook
Bug#941913: [Debian Buster 10.1] [arm64] [python-dev] The following packages have unmet dependencies:
Package: python-dev Version: 2.7.16-1 Severity: grave Dear maintainers, It seems there is a dependency issue when installing python-dev as indicated in following trace. My target is one arm64 Pinebook Debian buster 10.1 My test conditions are ... ansible@pinebook:~$ uname -a Linux pinebook 5.3.3-sunxi64 #5.98.191007 SMP Mon Oct 7 02:47:01 CEST 2019 aarch64 GNU/Linux ansible@pinebook:~$ cat /etc/debian_version 10.1 ansible@pinebook:~$ grep deb /etc/apt/sources.list.d/* |grep -v "#" /etc/apt/sources.list.d/armbian_apt_v_10_buster.list:deb http://apt.armbian.com buster main buster-utils buster-desktop /etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb http://ftp.fr.debian.org/debian buster-backports main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb http://ftp.debian.org/debian/ buster main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb http://ftp.debian.org/debian/ stretch main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb http://security.debian.org buster/updates main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb http://ftp.fr.debian.org/debian buster-updates main contrib non-free ansible@pinebook:~$ cat /etc/apt/preferences.d/preferences_* |grep -v "#" |grep -v "^$" Package: hostapd Pin: origin "apt.armbian.com" Pin-Priority: -1 Package: * Pin: origin "apt.armbian.com" Pin-Priority: 500 Package: * Pin: release o=Debian,l=Debian,n=buster-update Pin-Priority: 901 Package: * Pin: release o=Debian,l=Debian,n=buster Pin-Priority: 900 Package: * Pin: release o=Debian,l=Debian,n=buster-backports Pin-Priority: -1 Package: * Pin: release o=Debian,l=Debian,n=stretch Pin-Priority: 400 Package: * Pin: release o=Debian,l=Debian,n=testing Pin-Priority: -1 Package: * Pin: release o=Debian,l=Debian,n=unstable Pin-Priority: -1 Package: dhcpcd5 Pin: release * Pin-Priority: -1 Package: systemd Pin: release * Pin-Priority: -1 ansible@pinebook:~$ deborphan ansible@pinebook:~$ ansible@pinebook:~$ dpkg -l |grep -v ii Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-==--=== ansible@pinebook:~$ pstree -anp init,1 |-cron,2398 |-sshd,2532 | `-sshd,2760 | `-sshd,2762 | `-bash,2763 | `-pstree,1015 -anp |-login,2590 -- |-getty,2591 38400 tty2 |-getty,2592 38400 tty3 |-getty,2593 38400 tty4 |-getty,2594 115200 ttyS0 |-dbus-daemon,3962 --system |-systemd-udevd,10415 `-syslog-ng,28841 `-syslog-ng,28842 -p /var/run/syslog-ng.pid --no-caps ansible@pinebook:~$ sudo apt install python-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python-dev : Depends: libpython-dev (= 2.7.16-1) but it is not going to be installed Depends: python2.7-dev (>= 2.7.16-1~) but it is not going to be installed Depends: python2-dev (= 2.7.16-1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Thanks in advance for your help Best regards
Bug#941782: gir1.2-gnomedesktop-3.0 3.34.0-2 breaks gnome-shell
On Sat, 5 Oct 2019 15:33:34 -0700 Mike Miller wrote: > Package: gir1.2-gnomedesktop-3.0 > Version: 3.34.0-2 > Followup-For: Bug #941782 > > Affected by this today, gnome-shell is completely non-functional with > the version of gir1.2-gnomedesktop-3.0 now in testing. Confirm that > installing the stable version of the package (3.30.2.1-2) restores it. and to restore/install the stable version of the package gir1.2-gnomedesktop-3.0 1/ add the stable to your source.list 2/ sudo apt update 3/ sudo apt install gir1.2-gnomedesktop-3.0=3.30.2.1-2 4/ sudo apt-mark hold gir1.2-gnomedesktop-3.0 Do not forget to mark it unhold once the bug will be fixed. > -- > mike I add this info to this bug because a lot of people asked for a solution on the #debian-next channel since yesterday. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpNkAmYYTk86.pgp Description: PGP signature
Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed
uired (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== Now, according Debian doc, i try to install sysvinit ansible@pinebook:~$ sudo apt install sysvinit sysvinit-utils Reading package lists... Done Building dependency tree Reading state information... Done Package sysvinit is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: sysvinit-core:armhf systemd-sysv:armhf sysvinit-core systemd-sysv E: Package 'sysvinit' has no installation candidate It seems on Debian 10.1, there is now one new package name ? ansible@pinebook:~$ cat /etc/apt/sources.list.d/debian_apt_v_10_buster_* |grep -v "#" |grep -v "^$" deb http://ftp.fr.debian.org/debian buster-backports main contrib non-free deb http://ftp.debian.org/debian/ buster main contrib non-free deb http://ftp.debian.org/debian/ stretch main contrib non-free deb http://security.debian.org buster/updates main contrib non-free deb http://ftp.fr.debian.org/debian buster-updates main contrib non-free ansible@pinebook:~$ apt-cache search sysvinit git-daemon-sysvinit - fast, scalable, distributed revision control system (git-daemon service) live-config-sysvinit - Live System Configuration Components (sysvinit backend) sysvinit-core - System-V-like init utilities sysvinit-utils - System-V-like utilities ansible@pinebook:~$ sudo apt install sysvinit-core sysvinit-utils Reading package lists... Done Building dependency tree Reading state information... Done sysvinit-utils is already the newest version (2.93-8). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: dconf-service : Depends: default-dbus-session-bus or dbus-session-bus libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Le 01/09/2019 à 15:23, Dmitry Bogatov a écrit : control: tags -1 +moreinfo [2019-08-30 16:44] Jean-Marc LACROIX Package: sysvinit Version: 2.93-8 Severity: grave Dear maintainers, It seems there is a dependency issue when installing sysvinit-core as indicated in following trace [...] Package: *systemd* Pin: release * Pin-Priority: -1 I think problem is here. *systemd* matches `libsystemd0`, and given that even apt depends on `libsystemd0`, you are unlikely to solve any dependency. Please: * Try installing something else, like `tor'. I expect you will get similar error (`tor' depends on libsystemd0, sigh) * Replace `*systemd*' with `systemd' (without wildcard) in your apt-pinnings and try installing sysvinit-core again.
Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed
Package: sysvinit Version: 2.93-8 Severity: grave Dear maintainers, It seems there is a dependency issue when installing sysvinit-core as indicated in following trace ansible@pinebook:~$ LC_ALL=C LANG=C LANGUAGE=C sudo apt install sysvinit-core Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: dconf-service : Depends: default-dbus-session-bus or dbus-session-bus libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. My configuration is : ansible@pinebook:~$ cat /etc/debian_version 10.0 ansible@pinebook:~$ uname -a Linux pinebook 5.2.5-sunxi64 #5.92 SMP Fri Aug 2 07:51:38 CEST 2019 aarch64 GNU/Linux ansible@pinebook:~$ grep deb /etc/apt/sources.list.d/* |grep -v "#" /etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb http://ftp.fr.debian.org/debian buster-backports main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb http://ftp.debian.org/debian/ buster main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb http://ftp.debian.org/debian/ stretch main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb http://security.debian.org buster/updates main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb http://ftp.fr.debian.org/debian buster-updates main contrib non-free ansible@pinebook:~$ cat /etc/apt/preferences.d/preferences_debian_v_10_buster* |grep -v "#" |grep -v "^$" Package: dhcpcd5 Pin: release * Pin-Priority: -1 Package: *systemd* Pin: release * Pin-Priority: -1 Package: * Pin: release o=Debian,l=Debian,n=buster-update Pin-Priority: 901 Package: * Pin: release o=Debian,l=Debian,n=buster Pin-Priority: 900 Package: * Pin: release o=Debian,l=Debian,n=buster-backports Pin-Priority: -1 Package: * Pin: release o=Debian,l=Debian,n=stretch Pin-Priority: 400 Package: * Pin: release o=Debian,l=Debian,n=testing Pin-Priority: -1 Package: * Pin: release o=Debian,l=Debian,n=unstable Pin-Priority: -1 ansible@pinebook:~$ dpkg -l |grep -v ii Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais) ||/ Nom Version Architecture Description +++-===---=== Thanks in advance for your help Best regards
Bug#905720: acme-tiny: Please follow upstream versioning instead of date-based versions
On Sat, 6 Apr 2019 14:28:22 +0100 Samuel Henrique wrote: > Control: tags -1 patch > > Fix available on https://salsa.debian.org/samueloph/acme-tiny > > Discussion about the epoch bump: > https://lists.debian.org/debian-devel/2019/04/msg00052.html > > -- > Samuel Henrique Hi Samuel, I have a question about bugs 905720 and 924393. For both, you said there is a fix ([0]) and you mentionned the discution on debian-devel list ([1]) related the first epoch for acme-tiny. My question: do you think bug 905720 should be merged into bug 924393 ? I looked at them but (maybe I am wrong) I did not see any merge indication. Secondary question : what is blocking the fix ? You dropped this mail in April, the 6th. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt [0] https://salsa.debian.org/samueloph/acme-tiny [1] https://lists.debian.org/debian-devel/2019/04/msg00052.html pgpD5M7o4pjHS.pgp Description: PGP signature
Bug#894569: [Letsencrypt-devel] Bug#894569: acme-tiny: compatibility issues
On Thu, 5 Apr 2018 22:23:43 +0300 sergio wrote: > On 03/04/18 20:30, Sebastien Badia wrote: > > > The actual version in Debian stable (stretch) is 20160801-3+deb9u1. > > Could you please, tell us more about your problem ? > > Unfortunately I can't reproduce it more! But a week ago I had to > download the latest version from github (that successfully works) as > 20160801-3+deb9u1 produced some python Traceback. May be it were some > letsencrypt issues? > > > -- > sergio Hi Sergio, Any information to add to this bug report ? Can you reproduce it ? In case you cannot reproduce the issue, can this bug be closed ? Thanks in advance. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpBMNwuU5m2C.pgp Description: PGP signature
Bug#927800: [Debian Stretch 9.8] lm-sensors : Depends: libsensors4 (>= 1:3.1.1) but it is not going to be installed
Aurelien, Many thanks for your support...and of course your good idea (!) ansible@srv-owncloud-100:~$ sudo apt remove --purge lm-sensors libsensors* Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'libsensors4-dev' for glob 'libsensors*' Note, selecting 'libsensors-dev' for glob 'libsensors*' Note, selecting 'libsensors-config' for glob 'libsensors*' Note, selecting 'libsensors-applet-plugin0' for glob 'libsensors*' Note, selecting 'libsensors4' for glob 'libsensors*' Note, selecting 'libsensors5' for glob 'libsensors*' Note, selecting 'libsensors-applet-plugin-dev' for glob 'libsensors*' Package 'libsensors4' is not installed, so not removed Package 'libsensors4-dev' is not installed, so not removed Package 'libsensors-applet-plugin-dev' is not installed, so not removed Package 'libsensors-applet-plugin0' is not installed, so not removed The following packages will be REMOVED: ffmpeg* libavdevice58* libgl1* libgl1-mesa-dri* libglx-mesa0* libglx0* libsensors-config* libsensors5* lm-sensors* 0 upgraded, 0 newly installed, 9 to remove and 1 not upgraded. After this operation, 153 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 36267 files and directories currently installed.) Removing ffmpeg (7:4.1.1-1) ... Removing libavdevice58:amd64 (7:4.1.1-1) ... Removing libgl1:amd64 (1.1.0-1) ... Removing libglx0:amd64 (1.1.0-1) ... Removing libglx-mesa0:amd64 (18.3.4-2) ... Removing libgl1-mesa-dri:amd64 (18.3.4-2) ... Removing lm-sensors (1:3.5.0-3) ... Removing libsensors5:amd64 (1:3.5.0-3) ... Removing libsensors-config (1:3.5.0-3) ... Processing triggers for libc-bin (2.28-8) ... (Reading database ... 36137 files and directories currently installed.) Purging configuration files for libsensors-config (1:3.5.0-3) ... Purging configuration files for lm-sensors (1:3.5.0-3) ... Purging configuration files for ffmpeg (7:4.1.1-1) ... You can close this bug, it was a problem of dependencies with other packages for an unknown reason, because for my point of view, none stretch-backports can be installed according to my preferences. Regards Le 23/04/2019 à 16:27, Aurelien Jarno a écrit : On 2019-04-23 15:55, Jean-Marc LACROIX wrote: When i launch following command ... ansible@srv-owncloud-100:~$ sudo apt install lm-sensors Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: lm-sensors : Depends: libsensors4 (>= 1:3.1.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. I believe libsensors4 can't be installed as libsensors5 from Buster is already installed on your system, probably as a dependency of another package. You can't install both at the same time. It is installable without issue on a pure Stretch system. But it is possible to install Buster release without any others errors ansible@srv-owncloud-100:~$ sudo apt -t buster install lm-sensors Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: fancontrol read-edid i2c-tools The following NEW packages will be installed: lm-sensors 0 upgraded, 1 newly installed, 0 to remove and 225 not upgraded. Need to get 114 kB of archives. After this operation, 412 kB of additional disk space will be used. Get:1 http://ftp.debian.org/debian buster/main amd64 lm-sensors amd64 1:3.5.0-3 [114 kB] Fetched 114 kB in 0s (451 kB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package lm-sensors. (Reading database ... 36231 files and directories currently installed.) Preparing to unpack .../lm-sensors_1%3a3.5.0-3_amd64.deb ... Unpacking lm-sensors (1:3.5.0-3) ... Setting up lm-sensors (1:3.5.0-3) ... ansible@srv-owncloud-100:~$ This actually confirms the issue. lm-sensors 1:3.5.0-3 requires libsensors5. As it doesn't get installed, it means that you already have it installed on your system. Therefore you should try to remove libsensors5 and all the depending packages. Then you should be able to install lm-sensors and libsensors4 from Stretch.
Bug#927800: [Debian Stretch 9.8] lm-sensors : Depends: libsensors4 (>= 1:3.1.1) but it is not going to be installed
Package: lm-sensors Version: 1:3.4.0-4 Dear maintainer, I'm trying to install thelm-sensors package on a running LXC container on Debian Stretch V9.8, (arch = amd64) It seems that my environment is ok, as shown in the rest of my configuration ansible@srv-owncloud-100:~$ ip route ls default via 192.168.56.49 dev et-user-test 192.168.54.0/24 dev et-serv-test proto kernel scope link src 192.168.54.54 192.168.56.0/24 dev et-user-test proto kernel scope link src 192.168.56.54 192.168.57.0/24 dev et-admi-test proto kernel scope link src 192.168.57.54 192.168.59.0/24 dev et-wifi-test proto kernel scope link src 192.168.59.54 ansible@srv-owncloud-100:~$ pstree -anp init,1 |-dhclient,595 -4 -v -pf /run/dhclient.et-admi-test.pid -lf /var/lib/dhcp/dhclient.et-admi-test.leases -I -df /var/lib/dhcp/dhclient6.et-admi-test.leases... |-dhclient,677 -4 -v -pf /run/dhclient.et-serv-test.pid -lf /var/lib/dhcp/dhclient.et-serv-test.leases -I -df /var/lib/dhcp/dhclient6.et-serv-test.leases... |-dhclient,769 -4 -v -pf /run/dhclient.et-user-test.pid -lf /var/lib/dhcp/dhclient.et-user-test.leases -I -df /var/lib/dhcp/dhclient6.et-user-test.leases... |-dhclient,856 -4 -v -pf /run/dhclient.et-wifi-test.pid -lf /var/lib/dhcp/dhclient.et-wifi-test.leases -I -df /var/lib/dhcp/dhclient6.et-wifi-test.leases... |-sshd,980 | `-sshd,13815 | `-sshd,13821 | `-bash,13822 | `-pstree,14793 -anp |-getty,995 38400 tty1 |-getty,996 38400 tty2 |-getty,997 38400 tty3 `-getty,998 38400 tty4 ansible@srv-owncloud-100:~$ cat /etc/debian_version 9.8 ansible@srv-owncloud-100:~$ sudo apt update && sudo apt upgrade Ign:1 http://ftp.debian.org/debian stretch InRelease Hit:2 http://ftp.debian.org/debian buster InRelease Ign:4 http://ftp.debian.org/debian jessie InRelease Hit:5 http://ftp.debian.org/debian stretch Release Hit:6 http://ftp.debian.org/debian jessie Release Ign:3 https://attic.owncloud.com/org/download/repositories/production/Debian_9.0 InRelease Hit:8 http://download.owncloud.org/download/repositories/production/Debian_9.0 Release Hit:11 http://ftp.fr.debian.org/debian stretch-backports InRelease Hit:12 http://ftp.fr.debian.org/debian stretch-updates InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. ansible@srv-owncloud-100:~$ dpkg -l |grep -v ii Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-==--=== ansible@srv-owncloud-100:~$ ls -altr /etc/apt/sources.list.d/debian_apt_v_9_stretch_* -rw-r--r-- 1 root root 957 Apr 22 19:47 /etc/apt/sources.list.d/debian_apt_v_9_stretch_previous.list -rw-r--r-- 1 root root 838 Apr 22 19:47 /etc/apt/sources.list.d/debian_apt_v_9_stretch_current.list -rw-r--r-- 1 root root 849 Apr 22 19:47 /etc/apt/sources.list.d/debian_apt_v_9_stretch_updates.list -rw-r--r-- 1 root root 782 Apr 22 19:47 /etc/apt/sources.list.d/debian_apt_v_9_stretch_update_security.list -rw-r--r-- 1 root root 918 Apr 22 19:47 /etc/apt/sources.list.d/debian_apt_v_9_stretch_next.list -rw-r--r-- 1 root root 847 Apr 22 19:47 /etc/apt/sources.list.d/debian_apt_v_9_stretch_backports.list -rw-r--r-- 1 root root 952 Apr 22 19:47 /etc/apt/sources.list.d/debian_apt_v_9_stretch_owncloud.list ansible@srv-owncloud-100:~$ cat /etc/apt/sources.list.d/*list |grep -v "#" deb http://ftp.fr.debian.org/debian/ stretch-backports main contrib non-free deb http://ftp.debian.org/debian/ stretch main contrib non-free deb http://ftp.debian.org/debian/ buster main contrib non-free deb http://download.owncloud.org/download/repositories/production/Debian_9.0/ / deb http://ftp.debian.org/debian/ jessie main contrib non-free deb http://ftp.fr.debian.org/debian/ stretch-updates main contrib non-free About the pining capabilities ansible@srv-owncloud-100:~$ ls -altr /etc/apt/preferences.d/preferences_debian_v_9_stretch* -rw-r--r-- 1 root root 1052 Apr 22 19:47 /etc/apt/preferences.d/preferences_debian_v_9_stretch_no_systemd.pref -rw-r--r-- 1 root root 2493 Apr 22 19:48 /etc/apt/preferences.d/preferences_debian_v_9_stretch.pref -rw-r--r-- 1 root root 1161 Apr 22 19:48 /etc/apt/preferences.d/preferences_debian_v_9_stretch_no_dhcpcd5.pref ansible@srv-owncloud-100:~$ cat /etc/apt/preferences.d/preferences_debian_v_9_stretch* |grep -v "#" Package: * Pin: release a=stretch-update Pin-Priority: 901 Package: * Pin: release a=stretch Pin-Priority: 900
Bug#924666: invoke-rc.d: syntax error: unknown option "--skip-systemd-native"
Hi, According to previous tests, due to a serious bug in the post-installation scripts, it is no longer possible to reinstall or remove any type of package. The system is then definitely unusable. Thanks in advance to apply following patch To reproduce : step 1: no hostapd on the system ansible@srv-authenticator-100:~$ dpkg -l |grep hostapd ansible@srv-authenticator-100:~$ step 2: install buster release ansible@srv-authenticator-100:~$ sudo apt -t buster install hostapd Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: hostapd 0 upgraded, 1 newly installed, 0 to remove and 303 not upgraded. Need to get 0 B/777 kB of archives. After this operation, 2081 kB of additional disk space will be used. Selecting previously unselected package hostapd. (Reading database ... 23028 files and directories currently installed.) Preparing to unpack .../hostapd_2%3a2.7+git20190128+0c1e29f-2_amd64.deb ... Unpacking hostapd (2:2.7+git20190128+0c1e29f-2) ... Setting up hostapd (2:2.7+git20190128+0c1e29f-2) ... invoke-rc.d: syntax error: unknown option "--skip-systemd-native" dpkg: error processing package hostapd (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for man-db (2.7.6.1-2) ... Errors were encountered while processing: hostapd E: Sub-process /usr/bin/dpkg returned an error code (1) ansible@srv-authenticator-100:~$ step 3: As system is broken, be sure to verify that system is unusable ansible@srv-authenticator-100:~$ sudo dpkg --purge --force-all hostapd (Reading database ... 23054 files and directories currently installed.) Removing hostapd (2:2.7+git20190128+0c1e29f-2) ... invoke-rc.d: syntax error: unknown option "--skip-systemd-native" dpkg: error processing package hostapd (--purge): subprocess installed pre-removal script returned error exit status 1 invoke-rc.d: syntax error: unknown option "--skip-systemd-native" dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: hostapd ansible@srv-authenticator-100:~$ step 4: search invalid parameter ansible@srv-authenticator-100:~$ egrep -e '-skip-systemd-native' /var/lib/dpkg/info/hostapd.* /var/lib/dpkg/info/hostapd.postinst:invoke-rc.d --skip-systemd-native hostapd $_dh_action || exit 1 /var/lib/dpkg/info/hostapd.prerm: invoke-rc.d --skip-systemd-native hostapd stop || exit 1 step 5 : patch Debian scripts . sudo sed -i -e 's/--skip-systemd-native//g' /var/lib/dpkg/info/hostapd.* step 6 : As system is broken, be sure to verify that system is usable now ansible@srv-authenticator-100:~$ sudo apt remove --purge hostapd -y Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: hostapd* 0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded. 1 not fully installed or removed. After this operation, 2081 kB disk space will be freed. (Reading database ... 23054 files and directories currently installed.) Removing hostapd (2:2.7+git20190128+0c1e29f-2) ... /etc/init.d/hostapd: 30: /etc/init.d/hostapd: log_action_msg: not found Processing triggers for man-db (2.7.6.1-2) ... (Reading database ... 23032 files and directories currently installed.) Purging configuration files for hostapd (2:2.7+git20190128+0c1e29f-2) ... dpkg: warning: while removing hostapd, directory '/etc/hostapd' not empty so not removed ansible@srv-authenticator-100:~$ Many thanks To William Bonnet for his support on Debian systems Best regards
Bug#924666: [hostapd] [buster on stretch] invoke-rc.d: syntax error: unknown option "--skip-systemd-native"
Hi, I am trying to install on Debian buster hostapd release on stretch target This job was ok in december 2018, but now, it seems there is one regression in the package, because : ansible@srv-authenticator-100:~$ sudo apt install -t buster hostapd Reading package lists... Done Building dependency tree Reading state information... Done hostapd is already the newest version (2:2.7+git20190128+0c1e29f-2). 0 upgraded, 0 newly installed, 0 to remove and 303 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up hostapd (2:2.7+git20190128+0c1e29f-2) ... invoke-rc.d: syntax error: unknown option "--skip-systemd-native" dpkg: error processing package hostapd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: hostapd E: Sub-process /usr/bin/dpkg returned an error code (1) ansible@srv-authenticator-100:~$ My environment is : ansible@srv-authenticator-100:~$ pstree -an init |-logsave -s /var/log/fsck/checkfs fsck -M -A -a |-dhclient -4 -v -pf /run/dhclient.eth-admin.pid -lf /var/lib/dhcp/dhclient.eth-admin.leases -I -df /var/lib/dhcp/dhclient6.eth-admin.leases eth-admin |-dhclient -4 -v -pf /run/dhclient.eth-srv.pid -lf /var/lib/dhcp/dhclient.eth-srv.leases -I -df /var/lib/dhcp/dhclient6.eth-srv.leases eth-srv |-dhclient -4 -v -pf /run/dhclient.eth-user.pid -lf /var/lib/dhcp/dhclient.eth-user.leases -I -df /var/lib/dhcp/dhclient6.eth-user.leases eth-user |-dhclient -4 -v -pf /run/dhclient.eth-wifi.pid -lf /var/lib/dhcp/dhclient.eth-wifi.leases -I -df /var/lib/dhcp/dhclient6.eth-wifi.leases eth-wifi |-syslog-ng | `-syslog-ng -p /var/run/syslog-ng.pid --no-caps |-cron |-sshd | `-sshd | `-sshd | `-bash | `-pstree -an |-getty 115200 console |-getty 38400 tty2 |-getty 38400 tty3 `-getty 38400 tty4 Thanks in advance for your help
Bug#924666: [hostapd] [buster] not possible to start and to uninstall : /etc/init.d/hostapd: 30: /etc/init.d/hostapd: log_action_msg: not found
Package: hostapd Version: 2:2.7+git20190128+0c1e29f-2 Dear maintaniers, On Debian Buster, it seems not possible to uninstall hostapd package afterinstallation. Furthermore, i can not launch daemon. My current configuration before installing hostapd is : (with sysvinit, not systemd !) ansible@vm-buster-x86-amd64-100:~$ pstree -anp init,1 |-dhclient,603 -4 -v -i -pf /run/dhclient.eth-admin.pid -lf /var/lib/dhcp/dhclient.eth-admin.leases -I -df... |-dhclient,685 -4 -v -i -pf /run/dhclient.eth-srv.pid -lf /var/lib/dhcp/dhclient.eth-srv.leases -I -df ... |-dhclient,768 -4 -v -i -pf /run/dhclient.eth-user.pid -lf /var/lib/dhcp/dhclient.eth-user.leases -I -df ... |-cron,1197 |-dbus-daemon,1206 --system |-getty,1476 115200 console |-getty,1477 38400 tty2 |-getty,1478 38400 tty3 |-getty,1479 38400 tty4 |-syslog-ng,12916 | `-(syslog-ng,13835) |-syslog-ng,12939 | `-syslog-ng,12940 -p /var/run/syslog-ng.pid --no-caps `-sshd,16299 `-sshd,10843 `-sshd,10849 `-bash,10850 `-pstree,13836 -anp ansible@vm-buster-x86-amd64-100:~$ cat /etc/debian_version buster/sid ansible@vm-buster-x86-amd64-100:~$ cat /etc/apt/sources.list.d/debian_apt_v_10_buster_* |grep -v "#" deb http://ftp.debian.org/debian/ buster main contrib non-free deb http://ftp.debian.org/debian/ sid main contrib non-free deb http://ftp.debian.org/debian/ stretch main contrib non-free deb http://ftp.debian.org/debian/ unstable main contrib non-free ansible@vm-buster-x86-amd64-100:~$ cat /etc/apt/preferences.d/preferences_debian_v_10_buster* |grep -v "#" Package: * Pin: release a=buster Pin-Priority: 900 Package: * Pin: release a=stretch Pin-Priority: 400 Package: * Pin-Priority: -1 Package: * Pin: release a=unstable Pin-Priority: -1 Package: dhcpcd5 Pin: release * Pin-Priority: -1 Package: *systemd* Pin: release * Pin-Priority: -1 ansible@vm-buster-x86-amd64-100:~$ sudo apt update && sudo apt upgrade ansible@vm-buster-x86-amd64-100:~$ dpkg -l |grep -v ii Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ansible@vm-buster-x86-amd64-100:~$ sudo apt install hostapd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnl-route-3-200 The following NEW packages will be installed: hostapd libnl-route-3-200 0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded. Need to get 939 kB of archives. After this operation, 2637 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ftp.debian.org/debian buster/main amd64 libnl-route-3-200 amd64 3.4.0-1 [162 kB] Get:2 http://ftp.debian.org/debian buster/main amd64 hostapd amd64 2:2.7+git20190128+0c1e29f-2 [777 kB] Fetched 939 kB in 1s (1280 kB/s) Selecting previously unselected package libnl-route-3-200:amd64. (Reading database ... 130986 files and directories currently installed.) Preparing to unpack .../libnl-route-3-200_3.4.0-1_amd64.deb ... Unpacking libnl-route-3-200:amd64 (3.4.0-1) ... Selecting previously unselected package hostapd. Preparing to unpack .../hostapd_2%3a2.7+git20190128+0c1e29f-2_amd64.deb ... Unpacking hostapd (2:2.7+git20190128+0c1e29f-2) ... Setting up libnl-route-3-200:amd64 (3.4.0-1) ... Setting up hostapd (2:2.7+git20190128+0c1e29f-2) ... /etc/init.d/hostapd: 30: /etc/init.d/hostapd: log_action_msg: not found Processing triggers for man-db (2.8.5-2) ... Processing triggers for libc-bin (2.28-8) ... ansible@vm-buster-x86-amd64-100:~$ Which is very fine But... ansible@vm-buster-x86-amd64-100:~$ sudo apt remove --purge hostapd Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libnl-route-3-200 Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: hostapd* 0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded. After this operation, 2081 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 131018 files and directories currently installed.) Removing hostapd (2:2.7+git20190128+0c1e29f-2) ... /etc/init.d/hostapd: 30: /etc/init.d/hostapd: log_action_msg: not found Processing triggers for man-db (2.8.5-2) ... (Reading database ... 130996 files and directories currently installed.) Purging configuration files for hostapd (2:2.7+git20190128+0c1e29f-2) ... ansible@vm-buster-x86-amd64-100:~$ Please note following error : /etc/init.d/hostapd: 30:
Bug#921945: sylpheed: Sylpheed uses the wrong application for opening pdf files
Thu, 7 Mar 2019 10:15:39 +0100 Ricardo Mones écrivait : > control: forwarded -1 https://sylpheed.sraoss.jp/redmine/issues/312 > control: severity -1 wishlist > > Hi Jean-Marc, Hi Ricardo, > On Sun, Feb 10, 2019 at 01:57:28PM +0100, Jean-Marc wrote: > > Package: sylpheed > > Version: 3.7.0-4 > > Severity: normal > > > > Dear Maintainer, > > > > Sylpheed does not take into account the XDG default application the > > desktop environment should use for opening files of a specific > > MIME/Filetype. > > > > Example: . when I tried to open a PDF file, Sylpheed uses gimp to open > > the file. > > > > Gimp is the first application in the > > /usr/share/applications/mimeinfo.cache entry defining which > > application(s) can read/open/associate with pdf files. > > > > $ grep application/pdf /usr/share/applications/mimeinfo.cache > > application/pdf=gimp.desktop;inkscape.desktop;org.gnome.Evince.desktop;libreoffice-draw.desktop; > > > > It should use my desktop's default application from Debian Gnome > > default spec in /usr/share/applications/gnome-mimeapps.list to open > > PDF files. > > AFAIK Sylpheed is not a GNOME application, is just a GTK+2 application. I am speaking about taking into account the Cross-Desktop Group (XDG) spec. I had mentionned the file containing the Debian default values for my desktop as example. It has nothing to do with Gnome in particular. See https://www.freedesktop.org/ for more info. . Association between MIME types and applications https://specifications.freedesktop.org/mime-apps-spec/latest/ or in this one-page: https://specifications.freedesktop.org/mime-apps-spec/mime-apps-spec-1.0.1.html > Anyway I'm forwarding this upstream, just in case they may consider > worth to implement it for a better user experience. Thank you. > thanks for reporting, > -- > Ricardo Mones Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpR9g_iS3NCv.pgp Description: PGP signature
Bug#923298: chromium: file overlap with chromium-sandbox without Conficts and/or Replaces
On Tue, 26 Feb 2019 08:39:22 -0500 Michael Gilbert wrote: > control: tag -1 pending > > This may not be common knowledge, but mixed suites have always been a > supported configuration. This is a legitimate bug. I have a fix > queued for the next -security upload. > > Best wishes, > Mike > > Hi Mike, Can you specify in which version this will be fixed ? I can see version 72.0.3626.121-1 in unstable but changelog does not mention this bug. Thank you. Regards, Jean-Marc https://6jf.be/keys/ED863AD1.txt pgp8jnrOQ_s54.pgp Description: PGP signature
Bug#923298: chromium: file overlap with chromium-sandbox without Conficts and/or Replaces
On Tue, 26 Feb 2019 08:39:22 -0500 Michael Gilbert wrote: > control: tag -1 pending > > This may not be common knowledge, but mixed suites have always been a > supported configuration. This is a legitimate bug. I have a fix > queued for the next -security upload. > > Best wishes, > Mike > > Hi Mike, Can you specify in which version this will be fixed ? I can see version 72.0.3626.121-1 in unstable but changelog does not mention this bug. Thank you. Regards, Jean-Marc
Bug#922547: linux-image-4.9.0-8-armmp: Failed to boot after upgrading to linux-image-4.9.0-8-armmp version 4.9.144-3
Package: src:linux Version: 4.9.130-2 Severity: normal Dear Maintainer, Today, I upgraded my Debian stable. This upgrade included a Linux image upgrade from 4.9.130-2 to 4.9.144-3. The ugrade went well but left my cubieboard unbootable. I tried to create a rescue SD disk using the firmware + partition images I found here: https://get.debian.org/debian/dists/stable/main/installer-armhf/current/images/netboot/SD-card-images/ But I got the same: an unbootable rescue disk. I finally need to boot on my backup SD disk apt-marking the package linux-image-4.9.0-8-armmp as hold. Jean-Marc -- Package-specific info: ** Version: Linux version 4.9.0-8-armmp (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.130-2 (2018-10-27) ** Command line: console=ttyS0,115200 quiet ** Not tainted ** Kernel log: [8.973619] Registered IR keymap rc-empty [8.974088] input: sunxi-ir as /devices/platform/soc@01c0/1c21800.ir/rc/rc0/input0 [8.974114] rc rc0: sunxi-ir as /devices/platform/soc@01c0/1c21800.ir/rc/rc0 [9.008281] sunxi-ir 1c21800.ir: initialized sunXi IR driver [9.086910] lirc_dev: IR Remote Control driver registered, major 242 [9.094194] rc rc0: lirc_dev: driver ir-lirc-codec (sunxi-ir) registered at minor = 0 [9.094209] IR LIRC bridge handler initialized [9.197604] input: axp20x-pek as /devices/platform/soc@01c0/1c2ac00.i2c/i2c-0/0-0034/axp20x-pek/input/input1 [9.293592] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok [9.417609] Adding 1000444k swap on /dev/mmcblk0p2. Priority:-1 extents:1 across:1000444k SSFS [ 11.391116] random: crng init done [ 11.391132] random: 7 urandom warning(s) missed due to ratelimiting [ 13.618733] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [ 13.850605] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 14.024784] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [ 14.157500] systemd-journald[193]: Received request to flush runtime journal from PID 1 [ 14.408922] EXT4-fs (mmcblk0p1): mounting ext2 file system using the ext4 subsystem [ 14.419429] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null) [ 15.810981] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.950694] sun4i-emac 1c0b000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 16.950732] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 31.099975] tun: Universal TUN/TAP device driver, 1.6 [ 31.099986] tun: (C) 1999-2004 Max Krasnyansky [ 121.770373] rc rc0: IR event FIFO is full! [ 121.774487] rc rc0: IR event FIFO is full! [ 121.778581] rc rc0: IR event FIFO is full! [ 121.782674] rc rc0: IR event FIFO is full! [ 121.786771] rc rc0: IR event FIFO is full! [ 121.790864] rc rc0: IR event FIFO is full! [ 121.794956] rc rc0: IR event FIFO is full! [ 121.799049] rc rc0: IR event FIFO is full! [ 121.803141] rc rc0: IR event FIFO is full! [ 121.807233] rc rc0: IR event FIFO is full! [ 121.811325] rc rc0: IR event FIFO is full! [ 121.815418] rc rc0: IR event FIFO is full! [ 121.819540] rc rc0: IR event FIFO is full! [ 121.823633] rc rc0: IR event FIFO is full! [ 121.827726] rc rc0: IR event FIFO is full! [ 121.831818] rc rc0: IR event FIFO is full! [ 121.835910] rc rc0: IR event FIFO is full! [ 121.840002] rc rc0: IR event FIFO is full! [ 121.844095] rc rc0: IR event FIFO is full! [ 121.848187] rc rc0: IR event FIFO is full! [ 121.852279] rc rc0: IR event FIFO is full! [ 121.856375] rc rc0: IR event FIFO is full! [ 121.860468] rc rc0: IR event FIFO is full! [ 121.864562] rc rc0: IR event FIFO is full! [ 307.911134] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. [ 406.240378] systemd: 42 output lines suppressed due to ratelimiting [ 859.482624] rc rc0: IR event FIFO is full! [ 859.495934] rc rc0: IR event FIFO is full! [ 879.822042] rc rc0: IR event FIFO is full! [ 879.826157] rc rc0: IR event FIFO is full! [ 879.830265] rc rc0: IR event FIFO is full! [ 879.834358] rc rc0: IR event FIFO is full! [ 879.838449] rc rc0: IR event FIFO is full! [ 879.842540] rc rc0: IR event FIFO is full! [ 879.846632] rc rc0: IR event FIFO is full! [ 879.850725] rc rc0: IR event FIFO is full! [ 879.854818] rc rc0: IR event FIFO is full! [ 879.858910] rc rc0: IR event FIFO is full! [ 879.863002] rc rc0: IR event FIFO is full! [ 879.867112] rc rc0: IR event FIFO is full! [ 879.871206] rc rc0: IR event FIFO is full! [ 879.875299] rc rc0: IR event FIFO is full! [ 879.879391] rc rc0: IR event FIFO is full! [ 879.883483] rc rc0: IR event FIFO is full! [ 879.887576] rc rc0: IR event FIFO is full! [ 879.891667] rc rc0: IR event FIFO is full! [ 879.895759] rc rc0: IR event FIFO is full! [ 879.
Bug#921736: minissdpd: Script in d/minissdpd.config uses /sbin/ifconfig, but package does not depend on net-tools
On Fri, 08 Feb 2019 17:57:04 +0100 Tim Dengel wrote: > Package: minissdpd > Version: 1.5.20180223-5 > Severity: important > > Dear Maintainer, > > the script in debian/minissdpd.config uses /sbin/ifconfig, but the package > does not depend on net-tools, causing the script to fail on upgrades if > net-tools is not installed. > Is it possible to increase the bug severity to serious ? Increasing it to serious allows apt-listbugs to list it in case of upgrade. Jean-Marc https://6jf.be/keys/ED863AD1.txt pgpjmWPf2mjFL.pgp Description: PGP signature
