From rana at asapmktg.com Tue Jul 2 18:37:15 2024 From: rana at asapmktg.com (Admin support) Date: Tue, 02 Jul 2024 17:37:15 +0000 (UTC) Subject: ATTENTION Message-ID: <0214202407371775F8BC2A8F-A2783453CE@asapmktg.com> ? ? Dear Microsoft User We are writing to inform you that we have implemented new security measures to protect our email users' accounts from increasing cyber threats. we require all users to update their email account now to ensure uninterrupted access to their email.. Kindly take a minute to complete our email verification below ? ? Verify Now https://u28432017.ct.sendgrid.net/ls/click?upn=u001.fHqzhQ7Cz8k60d8hivFGuQb8W7J7lgD6IHVw-2FjMpHVZmFio126gq0-2BUm9bdH8Gz3NKk4_SAv8Nf0aBhqls3OwPd5OEZGe2ba25FOhb7oQrBFn0SRZeaokfQ-2BHfdoC9oZNyBBn8C8Iv91zlyyR3kG5MtzrWq0AWRbEgtpSb9Agi5WooPkcodS-2Fm-2B-2F1i7aFsQWwpGJ2GpwReIqXxAJHb7hEQRYQl72wSLHjMCtihC4kQfKWqlw09nhzlkQAljKthoJVIYzTor-2BcCSz5aZk20mgeaDwtmnEXLAtEz6W9HNXuykdWw9QqHAa5KMZoJ7gbyCazTaw4 ? Important Notice Account disconnection will take place today 12:00 Midnight if issue not resolved Microsoft respects your privacy. Read our privacy policy for more ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From owner at bugs.debian.org Wed Jul 3 11:51:04 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 03 Jul 2024 10:51:04 +0000 Subject: Processed: Re: Bug#1010893: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. References: <87tth6eov2.fsf@tauware.de> Message-ID: Processing control commands: > reassign -1 init-system-helpers Bug #1010893 [docker.io] Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. Bug reassigned from package 'docker.io' to 'init-system-helpers'. No longer marked as found in versions docker.io/20.10.14+dfsg1-1. Ignoring request to alter fixed versions of bug #1010893 to the same values previously set -- 1010893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010893 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From debian-reportbug at plan9.de Mon Jul 1 02:42:58 2024 From: debian-reportbug at plan9.de (Marc Lehmann) Date: Mon, 01 Jul 2024 03:42:58 +0200 Subject: Bug#1074564: initramfs-tools: fails to include config udevd config files Message-ID: <171979817843.30531.524001251562099424.reportbug@cerebro.laendle> Package: initramfs-tools Version: 0.142 Severity: normal Dear Maintainer, initramfs-tools packages andf uses systemd-udevd in the initramfs, but does not package the required .link files. Specifically, files and overrides from /etc are all missing, causing udevs to apply the hardcoded defaults when naming interfaces and applying other settings. * What exactly did you do (or not do) that was effective (or ineffective)? I have .link files and .link.d override directories in /etc/systemd/network. The generated initramfs contains the link files from /usr/lib/systemd/network/, but not the ones from etc., causing interfaces to be named wrongly. * What was the outcome of this action? E.g. when I have a /etc/systemd/network/99-default.link.d/50-namepolicy.conf file with: [Link] NamePolicy=keep kernel then some interfaces have the correct name and others don't after boot, depending on which drivers have been loaded. * What outcome did you expect instead? The system configuration should be respected and not overriden by hardcoded defaults in the initramfs. -- Package-specific info: -- initramfs sizes -rw------- 1 root root 50M Jun 9 11:10 /boot/initrd.img-6.1.0-20-amd64 -rw------- 1 root root 50M Jun 11 09:31 /boot/initrd.img-6.1.0-21-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-6.1.0-21-amd64 root=/dev/mapper/cryptroot ro rootflags=subvol=rootfs mitigations=off pcie_aspm.policy=powersupersave root=/dev/mapper/cryptroot relatime zswap.enabled=0 modprobe.blacklist=nouveau,nvidiafb ip=10.0.0.1::10.0.0.5:255.255.255.240:::off rd.luks=0 libata.allow_tpm=1 vsyscall=xonly nvidia-drm.modeset=1 raid0.default_layout=1 syscall.x32=y intel_iommu=on iommu=pt workqueue.power_efficient=1 cpu0_hotplug irqaffinity=16-23 i915.fastboot=1 i915.modeset=1 preempt=voluntary split_lock_detect=off -- /proc/filesystems f2fs ext3 ext2 ext4 btrfs vfat xfs fuseblk -- lsmod Module Size Used by tls 135168 0 nvidia_uvm 4669440 0 snd_seq_dummy 16384 0 snd_hrtimer 16384 1 snd_seq 90112 7 snd_seq_dummy rpcsec_gss_krb5 36864 0 nfsv4 1052672 1 dns_resolver 16384 1 nfsv4 nfs 516096 4 nfsv4 fscache 376832 1 nfs netfs 57344 1 fscache vboxnetadp 28672 0 vboxnetflt 32768 0 vboxdrv 602112 2 vboxnetadp,vboxnetflt cmac 16384 3 algif_hash 16384 1 algif_skcipher 16384 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 28672 2 z3fold 32768 1 wacom 135168 0 nvme_fabrics 32768 0 bridge 311296 0 stp 16384 1 bridge llc 16384 2 bridge,stp tcp_bbr 20480 77 sch_fq 20480 1 cuse 16384 3 binfmt_misc 24576 1 nls_ascii 16384 1 nls_cp437 20480 1 x86_pkg_temp_thermal 20480 0 intel_powerclamp 20480 0 coretemp 20480 0 snd_sof_pci_intel_tgl 16384 0 snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_tgl soundwire_intel 49152 1 snd_sof_intel_hda_common soundwire_generic_allocation 16384 1 soundwire_intel soundwire_cadence 40960 1 soundwire_intel snd_sof_intel_hda 20480 1 snd_sof_intel_hda_common snd_sof_pci 24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common snd_sof 274432 2 snd_sof_pci,snd_sof_intel_hda_common snd_sof_utils 20480 1 snd_sof snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common kvm_intel 380928 0 snd_hda_ext_core 40960 2 snd_sof_intel_hda_common,snd_soc_hdac_hda snd_soc_acpi_intel_match 81920 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common iwlmvm 385024 0 snd_soc_core 352256 4 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda snd_compress 28672 1 snd_soc_core kvm 1142784 1 kvm_intel i915 3055616 2 snd_intel_dspcfg 36864 2 snd_sof,snd_sof_intel_hda_common uvcvideo 131072 0 snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg btusb 69632 0 irqbypass 16384 1 kvm mac80211 1175552 1 iwlmvm nvidia_modeset 1363968 6 btrtl 28672 1 btusb videobuf2_vmalloc 20480 1 uvcvideo btbcm 24576 1 btusb videobuf2_memops 20480 1 videobuf2_vmalloc rapl 20480 0 libarc4 16384 1 mac80211 snd_hda_codec 184320 2 snd_soc_hdac_hda,snd_sof_intel_hda snd_usb_audio 376832 5 drm_buddy 20480 1 i915 btintel 45056 1 btusb videobuf2_v4l2 36864 1 uvcvideo btmtk 16384 1 btusb videobuf2_common 73728 4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops drm_display_helper 184320 1 i915 snd_hda_core 122880 5 snd_hda_ext_core,snd_hda_codec,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda snd_usbmidi_lib 45056 1 snd_usb_audio iwlwifi 360448 1 iwlmvm bluetooth 958464 29 btrtl,btmtk,btintel,btbcm,bnep,btusb cec 61440 2 drm_display_helper,i915 snd_hwdep 16384 2 snd_usb_audio,snd_hda_codec processor_thermal_device_pci 16384 0 videodev 294912 3 videobuf2_v4l2,uvcvideo,videobuf2_common mei_hdcp 24576 0 soundwire_bus 102400 3 soundwire_intel,soundwire_generic_allocation,soundwire_cadence snd_rawmidi 53248 1 snd_usbmidi_lib processor_thermal_device 20480 1 processor_thermal_device_pci rc_core 69632 1 cec pmt_telemetry 16384 0 processor_thermal_rfim 16384 1 processor_thermal_device snd_seq_device 16384 2 snd_seq,snd_rawmidi intel_rapl_msr 20480 0 intel_cstate 20480 0 processor_thermal_mbox 16384 2 processor_thermal_rfim,processor_thermal_device pmt_class 16384 1 pmt_telemetry snd_pcm 159744 9 snd_usb_audio,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_compress,snd_soc_core,snd_sof_utils,snd_hda_core ttm 94208 1 i915 mc 77824 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common iTCO_wdt 16384 0 cfg80211 1142784 3 iwlmvm,iwlwifi,mac80211 snd_timer 49152 3 snd_seq,snd_hrtimer,snd_pcm processor_thermal_rapl 20480 1 processor_thermal_device intel_pmc_bxt 16384 1 iTCO_wdt mei_me 53248 1 drm_kms_helper 208896 2 drm_display_helper,i915 snd 126976 24 snd_seq,snd_seq_device,snd_hwdep,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_sof,snd_timer,snd_compress,snd_soc_core,snd_pcm,snd_rawmidi intel_rapl_common 32768 2 intel_rapl_msr,processor_thermal_rapl iTCO_vendor_support 16384 1 iTCO_wdt ecdh_generic 16384 2 bluetooth int3400_thermal 20480 0 joydev 28672 0 ecc 40960 1 ecdh_generic intel_uncore 217088 0 mei 159744 3 mei_hdcp,mei_me soundcore 16384 1 snd watchdog 45056 1 iTCO_wdt intel_pmc_core 53248 0 i2c_algo_bit 16384 1 i915 intel_vsec 20480 0 serial_multi_instantiate 20480 0 mxm_wmi 16384 0 wmi_bmof 16384 0 rfkill 36864 5 iwlmvm,bluetooth,cfg80211 int340x_thermal_zone 20480 1 processor_thermal_device acpi_thermal_rel 16384 1 int3400_thermal pcspkr 16384 0 acpi_pad 184320 0 acpi_tad 20480 0 button 24576 0 bfq 94208 10 evdev 28672 12 sg 40960 0 nvidia 54517760 92 nvidia_uvm,nvidia_modeset jitterentropy_rng 16384 1 drbg 45056 1 ansi_cprng 16384 0 seqiv 16384 12 esp4 24576 12 xfrm_user 53248 0 xfrm_algo 16384 2 esp4,xfrm_user i2c_dev 24576 0 nfsd 708608 5 nct6683 28672 0 parport_pc 40960 0 auth_rpcgss 159744 2 nfsd,rpcsec_gss_krb5 ppdev 24576 0 nfs_acl 16384 1 nfsd lockd 131072 2 nfsd,nfs lp 20480 0 grace 16384 2 nfsd,lockd parport 73728 3 parport_pc,lp,ppdev drm 614400 8 drm_kms_helper,drm_display_helper,nvidia,drm_buddy,i915,ttm loop 32768 0 fuse 176128 2 cuse efi_pstore 16384 0 configfs 57344 1 sunrpc 692224 26 nfsd,nfsv4,auth_rpcgss,lockd,rpcsec_gss_krb5,nfs_acl,nfs ip_tables 36864 0 x_tables 61440 1 ip_tables autofs4 53248 10 efivarfs 24576 1 raid10 65536 0 raid1 53248 0 multipath 20480 0 linear 20480 0 ohci_hcd 61440 0 uhci_hcd 57344 0 ehci_hcd 102400 0 xfs 1945600 0 vfat 24576 1 fat 90112 1 vfat btrfs 1789952 5 blake2b_generic 20480 0 ext4 983040 2 crc16 16384 2 bluetooth,ext4 mbcache 16384 1 ext4 jbd2 167936 1 ext4 f2fs 802816 0 crc32_generic 16384 0 lz4hc_compress 24576 1 f2fs zstd_compress 294912 2 f2fs,btrfs lz4 16384 56 lz4_compress 24576 2 lz4,f2fs xts 16384 0 ecb 16384 0 dm_crypt 61440 7 dm_cache_smq 28672 2 dm_cache 73728 3 dm_cache_smq dm_persistent_data 106496 1 dm_cache dm_bio_prison 20480 1 dm_cache dm_bufio 40960 1 dm_persistent_data raid456 180224 0 async_raid6_recov 24576 1 raid456 async_memcpy 20480 2 raid456,async_raid6_recov async_pq 20480 2 raid456,async_raid6_recov async_xor 20480 3 async_pq,raid456,async_raid6_recov ses 20480 0 async_tx 20480 5 async_pq,async_memcpy,async_xor,raid456,async_raid6_recov enclosure 20480 1 ses xor 24576 2 async_xor,btrfs scsi_transport_sas 49152 1 ses raid6_pq 122880 4 async_pq,btrfs,raid456,async_raid6_recov libcrc32c 16384 4 dm_persistent_data,btrfs,xfs,raid456 crc32c_generic 16384 0 e1000e 315392 0 raid0 24576 1 md_mod 192512 7 raid1,raid10,raid0,linear,raid456,multipath hid_generic 16384 0 uas 32768 5 usbhid 65536 1 wacom usb_storage 81920 2 uas hid 159744 3 wacom,usbhid,hid_generic dm_mod 184320 50 dm_crypt,dm_cache,dm_bufio crc32_pclmul 16384 0 crc32c_intel 24576 9 ghash_clmulni_intel 16384 0 sha512_ssse3 49152 1 sha512_generic 16384 1 sha512_ssse3 sd_mod 65536 9 sha256_ssse3 32768 1 sha1_ssse3 32768 0 nvme 53248 2 xhci_pci 24576 0 nvme_core 163840 11 nvme,nvme_fabrics xhci_hcd 315392 1 xhci_pci t10_pi 16384 2 sd_mod,nvme_core ahci 49152 1 crc64_rocksoft_generic 16384 1 libahci 49152 1 ahci megaraid_sas 180224 1 crc64_rocksoft 20480 1 t10_pi crc_t10dif 20480 1 t10_pi libata 401408 2 libahci,ahci aesni_intel 393216 42 usbcore 348160 12 xhci_hcd,ohci_hcd,snd_usb_audio,usbhid,snd_usbmidi_lib,usb_storage,uvcvideo,ehci_hcd,btusb,xhci_pci,uas,uhci_hcd crct10dif_generic 16384 0 scsi_mod 286720 8 ses,scsi_transport_sas,sd_mod,usb_storage,uas,megaraid_sas,libata,sg crypto_simd 16384 1 aesni_intel cryptd 28672 22 crypto_simd,ghash_clmulni_intel igc 163840 0 crct10dif_pclmul 16384 1 i2c_i801 36864 0 crc64 20480 2 crc64_rocksoft,crc64_rocksoft_generic i2c_smbus 20480 1 i2c_i801 usb_common 16384 6 xhci_hcd,ohci_hcd,usbcore,uvcvideo,ehci_hcd,uhci_hcd scsi_common 16384 5 scsi_mod,usb_storage,uas,libata,sg crct10dif_common 16384 3 crct10dif_generic,crc_t10dif,crct10dif_pclmul fan 20480 0 video 65536 2 i915,nvidia_modeset wmi 36864 3 video,wmi_bmof,mxm_wmi pinctrl_alderlake 36864 0 -- /etc/initramfs-tools/modules e1000e raid456 dm-cache-smq dm-crypt xts lz4 f2fs ext3 ext4 btrfs vfat xfs usb_common usbcore xhci_hcd uhci_hcd ehci_hcd ohci_hcd usbkbd hid hid_generic usbhid hid_generic megaraid_sas -- /etc/kernel-img.conf # Kernel Image management overrides # See kernel-img.cnf(5) for details do_symlinks = No -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=auto KEYMAP=n COMPRESS=zstd DEVICE= NFSROOT=auto RUNSIZE=10% FSTYPE=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /etc/crypttab # cryptroot /dev/vg_cerebro/root /boot initramfs,luks,keyscript=decrypt_keyctl,discard cryptrootext /dev/disk/by-partlabel/EXTRA_SLASH_FOR_GGUF_DOWNLOADS /boot initramfs,luks,keyscript=decrypt_keyctl,discard cryptlocalvol /dev/vg_cerebro/localvol /boot initramfs,luks,keyscript=decrypt_keyctl #cryptswap /dev/vg_cerebro/swap /dev/urandom swap,cipher=aes-xts-plain64,size=256 # cryptlocalvolx /dev/vg_cerebro/localvolx /boot initramfs,luks,keyscript=decrypt_keyctl #cryptoldroot /dev/vg_oldroot/oldroot /boot initramfs,luks,keyscript=decrypt_keyctl -- /proc/mdstat Personalities : [raid0] [raid6] [raid5] [raid4] [linear] [multipath] [raid1] [raid10] md5 : active raid0 sdc1[4] sdd1[0] sdg1[2] sdf1[1] 15627554816 blocks super 1.2 1024k chunks unused devices: -- mkinitramfs hooks /etc/initramfs-tools/hooks/: schmorp-dm-modules schmorp-dropbearkeys schmorp-e2fsck /usr/share/initramfs-tools/hooks: btrfs cryptgnupg cryptgnupg-sc cryptkeyctl cryptopensc cryptpassdev cryptroot cryptroot-unlock dmsetup dropbear fsck fuse intel_microcode iscsi keymap klibc-utils kmod lvm2 mdadm nbd nbd-client ntfs_3g reiserfsprogs resume thermal thin-provisioning-tools udev xfs zz-busybox zz_nvidia-blacklists-nouveau -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'oldstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 6.1.0-21-amd64 (SMP w/28 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages initramfs-tools depends on: ii initramfs-tools-core 0.142 ii linux-base 4.9 initramfs-tools recommends no packages. Versions of packages initramfs-tools suggests: ii bash-completion 1:2.11-6 -- no debconf information From smcv at debian.org Wed Jul 3 20:02:58 2024 From: smcv at debian.org (Simon McVittie) Date: Wed, 3 Jul 2024 20:02:58 +0100 Subject: Bug#1074789: systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser) In-Reply-To: References: <868af0ba-b4b8-42b6-816c-90723826d034@debian.org> Message-ID: Control: reassign -1 systemd Control: retitle -1 systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser) Control: affects -1 + polkitd On Wed, 03 Jul 2024 at 19:25:15 +0200, Michael Biebl wrote: > Am 03.07.24 um 17:15 schrieb Lionel ?lie Mamane: > > $ ls -al /run/systemd/userdb/io.systemd.DynamicUser > > srw-rw-rw- 1 root root 0 24 mai 17:36 /run/systemd/userdb/io.systemd.DynamicUser > > > > $ sudo lsof /run/systemd/userdb/io.systemd.DynamicUser > > lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc > > Output information may be incomplete. > > systemd should be listening on this socket > > At this point, I think it's a systemd issue. I think it's fairly clear, at least, that this *isn't* a polkitd issue: its postinst is just using systemd-sysusers in an obvious way, so this (whatever the underlying issue is here) is going to affect increasingly many packages as they adopt systemd-sysusers as their way to create their required system users. smcv From owner at bugs.debian.org Wed Jul 3 20:03:07 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 03 Jul 2024 19:03:07 +0000 Subject: Processed: reassign 1074564 to udev References: <1720033162-1873-bts-benh@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > reassign 1074564 udev Bug #1074564 [initramfs-tools] initramfs-tools: fails to include config udevd config files Bug reassigned from package 'initramfs-tools' to 'udev'. No longer marked as found in versions initramfs-tools/0.142. Ignoring request to alter fixed versions of bug #1074564 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1074564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074564 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From owner at bugs.debian.org Wed Jul 3 20:06:05 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 03 Jul 2024 19:06:05 +0000 Subject: Processed: Re: Bug#1074789: systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser) References: Message-ID: Processing control commands: > reassign -1 systemd Bug #1074789 [polkitd] fails to configure (postinst) in absence of systemd-userdbd Bug reassigned from package 'polkitd' to 'systemd'. No longer marked as found in versions policykit-1/122-3. Ignoring request to alter fixed versions of bug #1074789 to the same values previously set > retitle -1 systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser) Bug #1074789 [systemd] fails to configure (postinst) in absence of systemd-userdbd Changed Bug title to 'systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser)' from 'fails to configure (postinst) in absence of systemd-userdbd'. > affects -1 + polkitd Bug #1074789 [systemd] systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser) Added indication that 1074789 affects polkitd -- 1074789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074789 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From lionel at mamane.lu Wed Jul 3 20:18:49 2024 From: lionel at mamane.lu (Lionel =?iso-8859-1?Q?=C9lie?= Mamane) Date: Wed, 3 Jul 2024 21:18:49 +0200 Subject: systemd-sysusers and userdb/io.systemd.DynamicUser socket [was: Bug#1074789: polkitd: postinst configure first install fails due to systemd-sysusers not working] In-Reply-To: References: <868af0ba-b4b8-42b6-816c-90723826d034@debian.org> Message-ID: Dear systemd maintainers, The polkitd postinst script invokes systemd-sysusers, and relies on it being functional, under the sole condition that this binary is present; in Debian this is equivalent to the systemd package being installed since /bin/systemd-sysusers is in that package. Is this a correct assumption or is there an additional condition for systemd-sysusers to be functional that the polkitd postinst script should be checking before invocation? I hit a scenario where it doesn't work, and makes the installation (configure phase) of polkitd fail, due to the necessary user not being created. I traced that back to systemd-sysusers trying to connect to /run/systemd/userdb/io.systemd.DynamicUser On all my Debian machines, that socket exists but nobody is listening on it. A polkitd maintainer argues that systemd should be listening on it, and on his machine it does. The stdout/stderr of the invocation looks like: $ sudo systemd-sysusers polkitd.conf Failed to check if group polkitd already exists: Connection refused but the return value is 0, which would indicate success. But the user that should be created is not created. At least this seems to be a bug in systemd-sysusers; according to usual interface, and as documented in its man page, if it failed to perform its job, it should return non-zero. What is your take on this? You can see the history of the discussion in bug #1074789 https://bugs.debian.org/1074789 systemd version 252.26-1~deb12u2 on amd64, and systemd-userdbd is not installed. Thanks in advance, -- Lionel Mamane From lionel at mamane.lu Wed Jul 3 20:18:49 2024 From: lionel at mamane.lu (Lionel =?UTF-8?Q?=C3=89lie?= Mamane) Date: Wed, 3 Jul 2024 21:18:49 +0200 Subject: Bug#1074789: systemd-sysusers and userdb/io.systemd.DynamicUser socket [was: Bug#1074789: polkitd: postinst configure first install fails due to systemd-sysusers not working] In-Reply-To: References: <868af0ba-b4b8-42b6-816c-90723826d034@debian.org> Message-ID: Dear systemd maintainers, The polkitd postinst script invokes systemd-sysusers, and relies on it being functional, under the sole condition that this binary is present; in Debian this is equivalent to the systemd package being installed since /bin/systemd-sysusers is in that package. Is this a correct assumption or is there an additional condition for systemd-sysusers to be functional that the polkitd postinst script should be checking before invocation? I hit a scenario where it doesn't work, and makes the installation (configure phase) of polkitd fail, due to the necessary user not being created. I traced that back to systemd-sysusers trying to connect to /run/systemd/userdb/io.systemd.DynamicUser On all my Debian machines, that socket exists but nobody is listening on it. A polkitd maintainer argues that systemd should be listening on it, and on his machine it does. The stdout/stderr of the invocation looks like: $ sudo systemd-sysusers polkitd.conf Failed to check if group polkitd already exists: Connection refused but the return value is 0, which would indicate success. But the user that should be created is not created. At least this seems to be a bug in systemd-sysusers; according to usual interface, and as documented in its man page, if it failed to perform its job, it should return non-zero. What is your take on this? You can see the history of the discussion in bug #1074789 https://bugs.debian.org/1074789 systemd version 252.26-1~deb12u2 on amd64, and systemd-userdbd is not installed. Thanks in advance, -- Lionel Mamane From biebl at debian.org Wed Jul 3 20:26:36 2024 From: biebl at debian.org (Michael Biebl) Date: Wed, 3 Jul 2024 21:26:36 +0200 Subject: Bug#1074789: [Pkg-utopia-maintainers] Bug#1074789: polkitd: setup uses non-failsafe manner of checking whether user/group exists In-Reply-To: References: <868af0ba-b4b8-42b6-816c-90723826d034@debian.org> Message-ID: Am 03.07.24 um 21:00 schrieb Lionel ?lie Mamane: > On Wed, Jul 03, 2024 at 07:25:15PM +0200, Michael Biebl wrote: > >>>>> connect(5, {sa_family=AF_UNIX, sun_path="/run/systemd/userdb/io.systemd.DynamicUser"}, 45) = -1 ECONNREFUSED (Connection refused) > >> systemd should be listening on this socket > > Well, on no less than four different Debian machines, it does not. > >> $ sudo lsof /run/systemd/userdb/io.systemd.DynamicUser >> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> systemd 1 root 28u unix 0x0000000073ac41e2 0t0 8696 >> /run/systemd/userdb/io.systemd.DynamicUser type=STREAM (LISTEN) > > Isn't that on a machine where systemd-userdb is installed maybe? The > installation of that package triggers the systemd binary to listen? No, systemd-userdb is not installed and as you can see from the above output it's actually systemd which listens on that socket. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From bluca at debian.org Wed Jul 3 22:58:33 2024 From: bluca at debian.org (Luca Boccassi) Date: Wed, 03 Jul 2024 22:58:33 +0100 Subject: Bug#1074789: [Pkg-utopia-maintainers] Bug#1074789: polkitd: setup uses non-failsafe manner of checking whether user/group exists In-Reply-To: References: <868af0ba-b4b8-42b6-816c-90723826d034@debian.org> Message-ID: On Wed, 3 Jul 2024 21:26:36 +0200 Michael Biebl wrote: > Am 03.07.24 um 21:00 schrieb Lionel ?lie Mamane: > > On Wed, Jul 03, 2024 at 07:25:15PM +0200, Michael Biebl wrote: > > > >>>>> connect(5, {sa_family=AF_UNIX, sun_path="/run/systemd/userdb/io.systemd.DynamicUser"}, 45) = -1 ECONNREFUSED (Connection refused) > > > >> systemd should be listening on this socket > > > > Well, on no less than four different Debian machines, it does not. > > > >> $ sudo lsof /run/systemd/userdb/io.systemd.DynamicUser > >> COMMAND PID USER?? FD?? TYPE???????????? DEVICE SIZE/OFF NODE NAME > >> systemd?? 1 root?? 28u? unix 0x0000000073ac41e2????? 0t0 8696 > >> /run/systemd/userdb/io.systemd.DynamicUser type=STREAM (LISTEN) > > > > Isn't that on a machine where systemd-userdb is installed maybe? The > > installation of that package triggers the systemd binary to listen? > > No, systemd-userdb is not installed and as you can see from the above > output it's actually systemd which listens on that socket. I can reproduce it by mounting a tmpfs on /run/systemd/userdb/ _and_ creating an empty io.systemd.DynamicUser file on it. Maybe it should not abort like that, however, if you have the directory in /run/ _and_ the socket file exists _but_ nothing is listening on it, then your machine is broken in some way. If the directory/socket are missing they are just skipped gracefully. -- Kind regards, Luca Boccassi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From bluca at debian.org Wed Jul 3 23:10:30 2024 From: bluca at debian.org (Luca Boccassi) Date: Wed, 03 Jul 2024 23:10:30 +0100 Subject: Bug#1074789: [Pkg-utopia-maintainers] Bug#1074789: polkitd: setup uses non-failsafe manner of checking whether user/group exists In-Reply-To: References: <868af0ba-b4b8-42b6-816c-90723826d034@debian.org> Message-ID: On Wed, 03 Jul 2024 22:58:33 +0100 Luca Boccassi wrote: > On Wed, 3 Jul 2024 21:26:36 +0200 Michael Biebl > wrote: > > Am 03.07.24 um 21:00 schrieb Lionel ?lie Mamane: > > > On Wed, Jul 03, 2024 at 07:25:15PM +0200, Michael Biebl wrote: > > > > > >>>>> connect(5, {sa_family=AF_UNIX, > sun_path="/run/systemd/userdb/io.systemd.DynamicUser"}, 45) = -1 > ECONNREFUSED (Connection refused) > > > > > >> systemd should be listening on this socket > > > > > > Well, on no less than four different Debian machines, it does not. > > > > > >> $ sudo lsof /run/systemd/userdb/io.systemd.DynamicUser > > >> COMMAND PID USER?? FD?? TYPE???????????? DEVICE SIZE/OFF NODE NAME > > >> systemd?? 1 root?? 28u? unix 0x0000000073ac41e2????? 0t0 8696 > > >> /run/systemd/userdb/io.systemd.DynamicUser type=STREAM (LISTEN) > > > > > > Isn't that on a machine where systemd-userdb is installed maybe? > The > > > installation of that package triggers the systemd binary to listen? > > > > No, systemd-userdb is not installed and as you can see from the above > > output it's actually systemd which listens on that socket. > > I can reproduce it by mounting a tmpfs on /run/systemd/userdb/ _and_ > creating an empty io.systemd.DynamicUser file on it. Maybe it should > not abort like that, however, if you have the directory in /run/ _and_ > the socket file exists _but_ nothing is listening on it, then your > machine is broken in some way. If the directory/socket are missing they > are just skipped gracefully. I'm not sure what's the alternative here - if consulting NSS fails for some local reasons because the machine is broken/misconfigured, I am not sure if it should just ignore it and continue it. If NSS is configured and is supposed to work, but doesn't for some temporary/local reason, you might end up creating a duplicated user/group, and I am not really sure that's better than bailing out without touching anything. -- Kind regards, Luca Boccassi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From owner at bugs.debian.org Wed Jul 3 23:42:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 03 Jul 2024 22:42:03 +0000 Subject: Processed: Bug#1074564 marked as pending in systemd References: <6685d3168a593_bcb70fdc1837b@godard.mail> <171979817843.30531.524001251562099424.reportbug@cerebro.laendle> Message-ID: Processing control commands: > tag -1 pending Bug #1074564 [udev] initramfs-tools: fails to include config udevd config files Added tag(s) pending. -- 1074564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074564 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From bluca at debian.org Thu Jul 4 11:47:20 2024 From: bluca at debian.org (Luca Boccassi) Date: Thu, 04 Jul 2024 11:47:20 +0100 Subject: Bug#1074789: [Pkg-utopia-maintainers] Bug#1074789: polkitd: setup uses non-failsafe manner of checking whether user/group exists In-Reply-To: References: <868af0ba-b4b8-42b6-816c-90723826d034@debian.org> Message-ID: On Wed, 03 Jul 2024 23:10:30 +0100 Luca Boccassi wrote: > On Wed, 03 Jul 2024 22:58:33 +0100 Luca Boccassi > wrote: > > On Wed, 3 Jul 2024 21:26:36 +0200 Michael Biebl > > wrote: > > > Am 03.07.24 um 21:00 schrieb Lionel ?lie Mamane: > > > > On Wed, Jul 03, 2024 at 07:25:15PM +0200, Michael Biebl wrote: > > > > > > > >>>>> connect(5, {sa_family=AF_UNIX, > > sun_path="/run/systemd/userdb/io.systemd.DynamicUser"}, 45) = -1 > > ECONNREFUSED (Connection refused) > > > > > > > >> systemd should be listening on this socket > > > > > > > > Well, on no less than four different Debian machines, it does > not. > > > > > > > >> $ sudo lsof /run/systemd/userdb/io.systemd.DynamicUser > > > >> COMMAND PID USER?? FD?? TYPE???????????? DEVICE SIZE/OFF NODE > NAME > > > >> systemd?? 1 root?? 28u? unix 0x0000000073ac41e2????? 0t0 8696 > > > >> /run/systemd/userdb/io.systemd.DynamicUser type=STREAM (LISTEN) > > > > > > > > Isn't that on a machine where systemd-userdb is installed maybe? > > The > > > > installation of that package triggers the systemd binary to > listen? > > > > > > No, systemd-userdb is not installed and as you can see from the > above > > > output it's actually systemd which listens on that socket. > > > > I can reproduce it by mounting a tmpfs on /run/systemd/userdb/ _and_ > > creating an empty io.systemd.DynamicUser file on it. Maybe it should > > not abort like that, however, if you have the directory in /run/ > _and_ > > the socket file exists _but_ nothing is listening on it, then your > > machine is broken in some way. If the directory/socket are missing > they > > are just skipped gracefully. > > I'm not sure what's the alternative here - if consulting NSS fails for > some local reasons because the machine is broken/misconfigured, I am > not sure if it should just ignore it and continue it. If NSS is > configured and is supposed to work, but doesn't for some > temporary/local reason, you might end up creating a duplicated > user/group, and I am not really sure that's better than bailing out > without touching anything. Consensus seems to be that in this bad situation it's slightly better to complain loudly and continue, so the next point release will contain a fix to this effect. You should still figure out how you ended up with a dead af_unix socket in the first place, as that's a sign of something seriously wrong on that machine. -- Kind regards, Luca Boccassi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From frederic at juliana-multimedia.com Fri Jul 5 11:26:09 2024 From: frederic at juliana-multimedia.com (=?UTF-8?Q?Fr=C3=A9d=C3=A9ric?= MASSOT) Date: Fri, 5 Jul 2024 12:26:09 +0200 Subject: Bug#1074789: Use SYSTEMD_NSS_DYNAMIC_BYPASS=1 ? References: Message-ID: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> Hi, I had the same problem installing the tuned and tuned-utils packages: Param?trage de polkitd (122-3) ... Failed to check if group polkitd already exists: Connection refused id: ??polkitd???: utilisateur inexistant chown: utilisateur incorrect: ??polkitd:root?? dpkg: erreur de traitement du paquet polkitd (--configure)?: le sous-processus paquet polkitd script post-installation install? a renvoy? un ?tat de sortie d'erreur 1 dpkg: des probl?mes de d?pendances emp?chent la configuration de tuned?: tuned d?pend de polkitd; cependant : Le paquet polkitd n'est pas encore configur?. I found this bug report: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716 I was able to complete the installation with: # SYSTEMD_NSS_DYNAMIC_BYPASS=1 apt-get install tuned tuned-utils Regards. -- ============================================== | FR?D?RIC MASSOT | | https://www.juliana-multimedia.com | | mailto:frederic at juliana-multimedia.com | | +33.(0)2.97.54.77.94 +33.(0)6.67.19.95.69 | ===========================Debian=GNU/Linux=== From ftpmaster at ftp-master.debian.org Fri Jul 5 22:35:10 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Fri, 05 Jul 2024 21:35:10 +0000 Subject: Processing of systemd_256.2-1_source.changes Message-ID: systemd_256.2-1_source.changes uploaded successfully to localhost along with the files: systemd_256.2-1.dsc systemd_256.2.orig.tar.gz systemd_256.2-1.debian.tar.xz systemd_256.2-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) From ftpmaster at ftp-master.debian.org Fri Jul 5 23:05:31 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Fri, 05 Jul 2024 22:05:31 +0000 Subject: systemd_256.2-1_source.changes ACCEPTED into unstable Message-ID: Thank you for your contribution to Debian. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 05 Jul 2024 19:15:59 +0100 Source: systemd Architecture: source Version: 256.2-1 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Luca Boccassi Closes: 1027773 1074564 1074789 Changes: systemd (256.2-1) unstable; urgency=medium . * d/not-installed: fix shutdown.standalone path * autopkgtest: skip qemu tests on arm64 * Add recommends on linux-sysctl-defaults. This package contains the default sysctl settings, and is maintained by the kernel team. This is not available in Ubuntu so keep it as a recommends for now, to avoid breaking the upstream CI. (Closes: #1027773) * initramfs-tools: copy network drop-ins too (Closes: #1074564) * d/e/checkout-upstream: fix shellcheck warnings * d/e/checkout-upstream: do not fail if rebase fails * d/e/checkout-upstream: switch packaging branch on upstream stable PRs. * New upstream version 256.2 (Closes: #1074789) * Install run0 zsh completion file Checksums-Sha1: f277f039941f6dd558c9ac9e6cc13ed90225b242 8094 systemd_256.2-1.dsc 937b54d419807a041573f72ecb7bdd1b09def615 15648609 systemd_256.2.orig.tar.gz d5a3f2fecb28014fce130a492ea453599849153a 170896 systemd_256.2-1.debian.tar.xz fe6bf55c17574d095270c933161b85b70ed3e4e5 13114 systemd_256.2-1_source.buildinfo Checksums-Sha256: d87947d5a0dbdd931d2f4b2e85524c948bdf65605428554c6b1770c5634fef21 8094 systemd_256.2-1.dsc 81ed336d36e48b1f31b876540f437755f33c7c389ba6e8efb8d3512129f0096d 15648609 systemd_256.2.orig.tar.gz 96fa89e483c062f8ed506ac5f032066dd92edf66c3219f1ba72699bd4c6e92d9 170896 systemd_256.2-1.debian.tar.xz 6a505fd310e3d9043d2d59fbeeb6eb7f4045e908731ea12191de18ea1b73ba83 13114 systemd_256.2-1_source.buildinfo Files: d3ff96c2e1746eba71459123b65cc0a2 8094 admin optional systemd_256.2-1.dsc 65e746dd4746dca7a2776a44d9cab9ae 15648609 admin optional systemd_256.2.orig.tar.gz cd21e4dcdce562e0d23f9593561f37ee 170896 admin optional systemd_256.2-1.debian.tar.xz 7a0f230b0077640326a7fb39eded1104 13114 admin optional systemd_256.2-1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmaIZLARHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB465Q//aKCoba7jjHy8Lni6JotBqKsfdDq6UqWM EiLc/Emaoe5nXI2S8EqYwZCeeYg+R45Fnx0sNxnh9y7c4N9a+KsuaiGKSRh0OXQT llKUFIY8LzvR5tFSGJXnZygjfMOPTrkWEmMzUFqg9Gd6j1eIZ/dxouN5ZOBu+bbu 2Y0LTZw5vWd4LhOQ2a4J/MeyzZrnxdlJbfG8iitIPDBd/EBqIoP9FsI9KcUX9IFU 1xH7QTaasCkojhR9vIlPvP5UF6zszlxN2ROEMcoOxsgAnB2OghF1EXM3ZAtSn9H1 rtY1UJUJsLtbBS7Qi9Wd9fUAWPOm/oZ0057QgSL1Kz0OZDJl7C8Cegy4jN6Pizv/ x7LS/zR6qAEl8DIwmmxA/0HpyM7/6KNkqbnjn/jirgUYLit/kMkAGdV938J5BqS7 lr3XQyNZXhjIpksrmMlR2SYM0vyXNpVEai9ouRDP40qq6NpYlnOHr/IgK2j02cJY uF/V8fCeiB053HvlLwaaHqlADa0GPF1+sN2p+SL/FLd7i5O6IBJGEXawpZf6EQGY UzD1UnRxoRmtVOlTgRMWlz7eqiYt23ZNq/Upn06WGKGhBefqoV22Q3XzCVuUUSZZ KmLKcJfq28lxPJ/J2lm7PdqWOYRuItVRLhVMtWU4wwdeqL688odmhAQs2i/41EGz Phj+Dp9blMc= =EsRJ -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From owner at bugs.debian.org Fri Jul 5 23:09:04 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 05 Jul 2024 22:09:04 +0000 Subject: Bug#1027773: marked as done (Please set sysctl net.ipv4.ping_group_range by default) References: <164824489682.154846.6780885459813319094.reportbug@x230> Message-ID: Your message dated Fri, 05 Jul 2024 22:05:32 +0000 with message-id and subject line Bug#1027773: fixed in systemd 256.2-1 has caused the Debian Bug report #1027773, regarding Please set sysctl net.ipv4.ping_group_range by default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 1027773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027773 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Petr Vorel Subject: iputils-ping: Move from capabilities to ICMP socket Date: Fri, 25 Mar 2022 22:48:16 +0100 Size: 4012 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#1027773: fixed in systemd 256.2-1 Date: Fri, 05 Jul 2024 22:05:32 +0000 Size: 7675 URL: From owner at bugs.debian.org Fri Jul 5 23:09:06 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 05 Jul 2024 22:09:06 +0000 Subject: Bug#1074564: marked as done (initramfs-tools: fails to include config udevd config files) References: <171979817843.30531.524001251562099424.reportbug@cerebro.laendle> Message-ID: Your message dated Fri, 05 Jul 2024 22:05:32 +0000 with message-id and subject line Bug#1074564: fixed in systemd 256.2-1 has caused the Debian Bug report #1074564, regarding initramfs-tools: fails to include config udevd config files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 1074564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074564 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Marc Lehmann Subject: initramfs-tools: fails to include config udevd config files Date: Mon, 01 Jul 2024 03:42:58 +0200 Size: 18103 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#1074564: fixed in systemd 256.2-1 Date: Fri, 05 Jul 2024 22:05:32 +0000 Size: 7698 URL: From owner at bugs.debian.org Fri Jul 5 23:09:08 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 05 Jul 2024 22:09:08 +0000 Subject: Bug#1074789: marked as done (systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser)) References: Message-ID: Your message dated Fri, 05 Jul 2024 22:05:32 +0000 with message-id and subject line Bug#1074789: fixed in systemd 256.2-1 has caused the Debian Bug report #1074789, regarding systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 1074789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074789 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Lionel Elie Mamane Subject: polkitd: setup uses non-failsafe manner of checking whether user/group exists Date: Wed, 3 Jul 2024 11:17:48 +0200 Size: 4781 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#1074789: fixed in systemd 256.2-1 Date: Fri, 05 Jul 2024 22:05:32 +0000 Size: 7697 URL: From wesley at schwengle.net Sat Jul 6 22:58:17 2024 From: wesley at schwengle.net (Wesley Schwengle) Date: Sat, 06 Jul 2024 17:58:17 -0400 Subject: Bug#1075882: systemd + crypttab not working after 256-2 Message-ID: <172030309777.3063.6441143336205122502.reportbug@sputnik-odin.opperschaap.net> Package: systemd Version: 256.2-1 Severity: important X-Debbugs-Cc: wesley at schwengle.net Dear Maintainer, Today after an upgrade of systemd my machine was unable to reboot because it failed to read /etc/crypttab. In /etc/crypttab I have a second disk which is encrypted (which is my /home). My fstab entry for /home could not be mounted, resulting in a timeout. I did see a recommendation for a package that wasn't going to be installed: systemd-cryptsetup. Initially I didn't think much of it, because several other systemd-X packages are not always needed have a working system. But reading the changelog of 256-2 from experimental showed that it was indeed a required dependency (for those who have a crypttab). I realize I have a "special" setup to not install recommends by default and I have an obligation to read changelogs, but I think this change might warrant more information to the end user as disk encryption is much more common nowadays. Also, going forward users from bookworm to trixie might want to see this in the release notes. I think a mention in NEWS.Debian is in order. I was able to fix the issue by install systemd-cryptsetup. Many thanks, Wesley -- Package-specific info: -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.7-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii libacl1 2.3.2-2 ii libapparmor1 3.1.7-1 ii libaudit1 1:3.1.2-4 ii libblkid1 2.40.1-9 ii libc6 2.38-14 ii libcap2 1:2.66-5 ii libmount1 2.40.1-9 ii libpam0g 1.5.3-7 ii libseccomp2 2.5.5-1 ii libselinux1 3.5-2+b2 ii libssl3t64 3.2.2-1 ii libsystemd-shared 256.2-1 ii libsystemd0 256.2-1 ii mount 2.40.1-9 Versions of packages systemd recommends: ii dbus [default-dbus-system-bus] 1.14.10-4+b1 ii libzstd1 1.5.6+dfsg-1 pn linux-sysctl-defaults ii openntpd [time-daemon] 1:6.2p3-4.2+b2 ii systemd-cryptsetup 256.2-1 Versions of packages systemd suggests: ii libcryptsetup12 2:2.7.2-2 ii libgcrypt20 1.10.3-3 ii libidn2-0 2.3.7-2 ii liblz4-1 1.9.4-2 ii liblzma5 5.6.2-2 pn libtss2-rc0t64 ii libtss2-tcti-device0t64 [libtss2-tcti-device0] 4.1.3-1 ii polkitd 124-3 pn systemd-boot pn systemd-container pn systemd-homed pn systemd-repart ii systemd-resolved 256.2-1 pn systemd-userdbd Versions of packages systemd is related to: ii dbus-user-session 1.14.10-4+b1 pn dracut ii initramfs-tools 0.142 ii libnss-systemd 256.2-1 ii libpam-systemd 256.2-1 ii udev 256.2-1 -- debconf-show failed From bluca at debian.org Sat Jul 6 23:06:54 2024 From: bluca at debian.org (Luca Boccassi) Date: Sat, 06 Jul 2024 23:06:54 +0100 Subject: Bug#1075882: systemd + crypttab not working after 256-2 In-Reply-To: <172030309777.3063.6441143336205122502.reportbug@sputnik-odin.opperschaap.net> References: <172030309777.3063.6441143336205122502.reportbug@sputnik-odin.opperschaap.net> <172030309777.3063.6441143336205122502.reportbug@sputnik-odin.opperschaap.net> Message-ID: <044fef2b2e0008cae39ac0cfbe86d2b1b771413f.camel@debian.org> Control: tags -1 wontfix Control: close -1 On Sat, 06 Jul 2024 17:58:17 -0400 Wesley Schwengle wrote: > Package: systemd > Version: 256.2-1 > Severity: important > X-Debbugs-Cc: wesley at schwengle.net > > Dear Maintainer, > > Today after an upgrade of systemd my machine was unable to reboot because it > failed to read /etc/crypttab. > > In /etc/crypttab I have a second disk which is encrypted (which is my /home). > My fstab entry for /home could not be mounted, resulting in a timeout. > > I did see a recommendation for a package that wasn't going to be installed: > systemd-cryptsetup. Recommends are installed by default intentionally, if you choose to turn that default off, you need to make sure you install every you need for optional features manually, there's just no way around it. -- Kind regards, Luca Boccassi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From owner at bugs.debian.org Sat Jul 6 23:09:08 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 06 Jul 2024 22:09:08 +0000 Subject: Processed: Re: systemd + crypttab not working after 256-2 References: <044fef2b2e0008cae39ac0cfbe86d2b1b771413f.camel@debian.org> <172030309777.3063.6441143336205122502.reportbug@sputnik-odin.opperschaap.net> Message-ID: Processing control commands: > tags -1 wontfix Bug #1075882 [systemd] systemd + crypttab not working after 256-2 Added tag(s) wontfix. > close -1 Bug #1075882 [systemd] systemd + crypttab not working after 256-2 Marked Bug as done -- 1075882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075882 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From bluca at debian.org Sun Jul 7 14:28:53 2024 From: bluca at debian.org (Luca Boccassi) Date: Sun, 07 Jul 2024 14:28:53 +0100 Subject: Bug#1075898: bookworm-pu: package systemd/252.28-1~deb12u1 Message-ID: <0ac99d0727bdd5ad4e686bca09ebf695672a5c5e.camel@debian.org> Package: release.debian.org Severity: normal Tags: bookworm User: release.debian.org at packages.debian.org Usertags: pu X-Debbugs-Cc: pkg-systemd-maintainers at lists.alioth.debian.org Dear Release Team, We would like to upload the latest stable point release of systemd 252 to bookworm-p-u. Stable release branches are maintained upstream with the intention of providing bug fixes only and no compatibility breakages, and with automated non-trivial CI jobs that also cover Debian and Ubuntu. I have already uploaded to p-u. There are no packaging changes. Debdiff attached. The list of commits included can be seen at: https://github.com/systemd/systemd-stable/compare/v252.27...v252.28 -- Kind regards, Luca Boccassi -------------- next part -------------- A non-text attachment was scrubbed... Name: debdiff Type: text/x-patch Size: 30690 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From ftpmaster at ftp-master.debian.org Sun Jul 7 14:38:36 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Sun, 07 Jul 2024 13:38:36 +0000 Subject: Processing of systemd_252.28-1~deb12u1_source.changes Message-ID: systemd_252.28-1~deb12u1_source.changes uploaded successfully to localhost along with the files: systemd_252.28-1~deb12u1.dsc systemd_252.28.orig.tar.gz systemd_252.28-1~deb12u1.debian.tar.xz systemd_252.28-1~deb12u1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) From ftpmaster at ftp-master.debian.org Sun Jul 7 14:50:34 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Sun, 07 Jul 2024 13:50:34 +0000 Subject: systemd_252.28-1~deb12u1_source.changes ACCEPTED into proposed-updates->stable-new Message-ID: Thank you for your contribution to Debian. Mapping bookworm to stable. Mapping stable to proposed-updates. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 07 Jul 2024 11:56:20 +0100 Source: systemd Architecture: source Version: 252.28-1~deb12u1 Distribution: bookworm Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Luca Boccassi Closes: 1074789 Changes: systemd (252.28-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.28 (Closes: #1074789) Checksums-Sha1: d812fc736a74345df9f74eeacf3363a8ef3354cd 6618 systemd_252.28-1~deb12u1.dsc 5290fe695685c4208da6d80ef1296f66ec378d30 12128602 systemd_252.28.orig.tar.gz da7c2236860b02504ebd0394dd605e0b51464b2a 171232 systemd_252.28-1~deb12u1.debian.tar.xz 885eb88c7b4af471c0eb27f2a9cb4f158ab7cf98 11795 systemd_252.28-1~deb12u1_source.buildinfo Checksums-Sha256: 0567c404fc64cfe1b4cc72f998fa74ef197e5367d4741a5737ee0b138d4bcb42 6618 systemd_252.28-1~deb12u1.dsc 7427fcf27f10ef9bae21d71c491c575e190353b471dd5d12b9dabfa4169b589b 12128602 systemd_252.28.orig.tar.gz 3d9979f2318a53500d5b93e4bc13b25d8e656b86c4d530b24a2d374d4cb42c63 171232 systemd_252.28-1~deb12u1.debian.tar.xz 87029242c5daa185d2a676e3027c6a8379e634d64e81486ae71864e2bc1a5fbd 11795 systemd_252.28-1~deb12u1_source.buildinfo Files: 6ee87452641470c4fcecee73678d4de3 6618 admin optional systemd_252.28-1~deb12u1.dsc d9fd683d175858a76522fc40c5bc8303 12128602 admin optional systemd_252.28.orig.tar.gz 5e0fdf94fa3f463f828fdafc6b7c720b 171232 admin optional systemd_252.28-1~deb12u1.debian.tar.xz 2b41f88e54582bbc512e3a7bbcfc5c63 11795 admin optional systemd_252.28-1~deb12u1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmaKl28RHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB5BrQ/+POttGQnwjWlr6krwG5RyOSP40svW6ieq Ne9gXLwkqgQz8fn7t9v+TevtcQGiFotTTilGksCYf3uC8sK/1d4aHmcUok88eLX5 TJH2r1ZvyzjFp1mYMU+yHtIpiBGwl9T+quX3DGwL0jQkzq7Bo06U+vN4a7yM5UdE X1vgpjFccgH9/xYbWuFNevdj9ZI1gCNsbjY691k1ALzt9oAqw1X3enFSdUccC+Rv u34KJzRSUglLeATE//+P3RJPyBaaGjphN/BVS1gE972E04GjIc9TkQbYFgem7OrD +JI2NA5hMSAcjqulScpK79nnNbIuC09Cxy70TlMcHfORepxQxHaO8BhWERH8XNVC nKayRzjxqE+VkEXIFraRjWxxvw1EL+q19eNn3a3SLUHBz/vRd/P+pICKaFlGF8oI 2Gr5okYEoCqC2ox9z9WL1Hjz/NbXmdC0Kw/ttx8Ea2Fomqb2fi8DkKM6gWyVIk5Y 9FVF1feQKiZtdmzvPuVs9gjCYqFtNmoF8j+jObc2QJBETX6V8RDvsq9FodbZJcsr D92vq8NpVckEAkq7FexQNDz3xU+HKHqLgrhFq1M/0ifKdoVLSMCiJfzkoJomQUsV 41Xg8ACimd3m9nJxSEAMxMAl85cPORcyWkutnM2AfV1gehk7TSYtNFrMhSKtlmcm 5qXGd8Nx6fg= =tmXt -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From noreply at release.debian.org Mon Jul 8 05:39:14 2024 From: noreply at release.debian.org (Debian testing watch) Date: Mon, 08 Jul 2024 04:39:14 +0000 Subject: systemd 256.2-1 MIGRATED to testing Message-ID: FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 256.1-2 Current version: 256.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. From ftpmaster at ftp-master.debian.org Mon Jul 8 12:08:15 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Mon, 08 Jul 2024 11:08:15 +0000 Subject: Processing of systemd_254.15-1~bpo12+1_source.changes Message-ID: systemd_254.15-1~bpo12+1_source.changes uploaded successfully to localhost along with the files: systemd_254.15-1~bpo12+1.dsc systemd_254.15.orig.tar.gz systemd_254.15-1~bpo12+1.debian.tar.xz systemd_254.15-1~bpo12+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) From ftpmaster at ftp-master.debian.org Mon Jul 8 12:40:04 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Mon, 08 Jul 2024 11:40:04 +0000 Subject: systemd_254.15-1~bpo12+1_source.changes ACCEPTED into stable-backports Message-ID: Thank you for your contribution to Debian. Mapping bookworm-backports to stable-backports. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Mon, 08 Jul 2024 10:19:49 +0100 Source: systemd Architecture: source Version: 254.15-1~bpo12+1 Distribution: bookworm-backports Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Luca Boccassi Changes: systemd (254.15-1~bpo12+1) bookworm-backports; urgency=medium . * New upstream stable version 254.15 Checksums-Sha1: a313874fb083d2c03be2ef051e3ee9c51a2f4904 6929 systemd_254.15-1~bpo12+1.dsc bfc3e5fa36aa587361cc89b225688159ed225ced 14537162 systemd_254.15.orig.tar.gz 60990a2d9f38216a3147ac98e2174ae78857bdc7 155976 systemd_254.15-1~bpo12+1.debian.tar.xz f557282088cd847dcd9f9fe87d2d210c8825ab2d 12504 systemd_254.15-1~bpo12+1_source.buildinfo Checksums-Sha256: dec65040b47299930ebd8d3c1daf0d861b42f07922d658a117c57ce272d3d929 6929 systemd_254.15-1~bpo12+1.dsc 9ad1ba6612357bb1c3f7963fd81112b52e9e3717289e869748615b3c781bdd98 14537162 systemd_254.15.orig.tar.gz 5fdf503da4cd09dc59c93476be12fa88a6f97818b90494a9e4eda4f1f913c915 155976 systemd_254.15-1~bpo12+1.debian.tar.xz b0229ba2a058d86e786a2dab2459a8bad0ff6dcb7127551304252ba4da8f7e2a 12504 systemd_254.15-1~bpo12+1_source.buildinfo Files: 0638be89376da8dc08af8e14b4c39670 6929 admin optional systemd_254.15-1~bpo12+1.dsc b314b23e01cd900df358b50ac83fd6fa 14537162 admin optional systemd_254.15.orig.tar.gz ac325c9990f60bf9af24e9dfadbfe4bf 155976 admin optional systemd_254.15-1~bpo12+1.debian.tar.xz a9f7ece2e53b9264eaa54f7be54dffcf 12504 admin optional systemd_254.15-1~bpo12+1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmaLxc4RHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB72OBAAjKtWT4qLR02q7AbpdxcIEBVuqvTu/VNi 1I8ktxUaT+T21fkQoQbC6qnPEDzTxCHDx9+S5KaB575EmMRjairc0V+S8SW/GFQo OCSLw5HihwRVkt7SyTdtkPR7EwrCr1Am1O4hizKP45gMH33oEZm5kAipOKAMl5HY B8sX0j1j7jSaYLdQ3uPpL9Vd3/Buq2bE22amh+NaKW4XDmZoOZMqpz8YfH0P2RDQ 8Tgazr6HaRyshzf+4HToIxw39viOw8ekULUIxjAIw68FzFgQi5ygsTazegs3b6oi L2F8qpjOX+CJNkqgfWKvmQfIqNmDi9YU4G2sYSQXEPrI3VphQrwNQsarJraoOGgT m2B/5IrMsfbpOZ4LEhaK2xoDtlH6aQ8npcgTQ60Qr2JI8iGwXy+X0vacc8bOEVMn pfz7dBDYVsVdyrGnnOwY0uY8QaOmj7+65ePSAVCRqA2zBsRbGWkr8sDZ0G2P8oRu zBUPWi7kAFjvyfmSp/YXg3Tenfc2MtBkNv8e2mj1c+x1nk4yUeIX2sJMnViBfedB SPH+fbX6u317uWbBkvCa1dq3B8ZZxx4R2aSgi7L0ndiN+jp8J54JGKlNIKikAucz HZJZfC6iJ2nYMnDajfcd9DMhoNYqSCmpzAac+Tr46cfQqcFWOkMLunBpZlyZjhRc I0z12pLoTVM= =FOPP -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From vincent at vinc17.net Tue Jul 9 08:53:17 2024 From: vincent at vinc17.net (Vincent Lefevre) Date: Tue, 9 Jul 2024 09:53:17 +0200 Subject: Bug#1072505: systemd: /usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path "/run/lock", ignoring. In-Reply-To: <901f144f9f1a8bd7fe24b2e3534acd74968a0bf0.camel@debian.org> References: <171738685573.345174.8783429761985098405.reportbug@trefle.academ.org> <171738685573.345174.8783429761985098405.reportbug@trefle.academ.org> <901f144f9f1a8bd7fe24b2e3534acd74968a0bf0.camel@debian.org> <171738685573.345174.8783429761985098405.reportbug@trefle.academ.org> Message-ID: <20240709075317.GA83161@cventin.lip.ens-lyon.fr> On 2024-06-03 10:27:08 +0100, Luca Boccassi wrote: > On Mon, 03 Jun 2024 10:54:15 +0700 "Damir R. Islamov" > wrote: > > Every time the systemd package is being configured, > > it return a warnung > > /usr/lib/tmpfiles.d/legacy.conf:13: Duplicate line for path > "/run/lock", ignoring. > > It's expected and harmless, just ignore it as the message says Then, why outputting such a useless message??? This message has no interest for the end user. Worse, the user may wonder whether there is something wrong. For a few weeks, there have been 5 bug reports + all the users (including me) who had to do a search on the web for this message. Moreover, the word "ignoring" as written in the message is misleading. As I understand it, it means that *systemd* ignores the duplicate line, not that the user should ignore the message (which would be rather stupid: if some information related to something expected and harmless is to be ignored, then do not provide such information in the first place). And the fact that systemd ignores the duplicate line does not mean that there isn't an issue somewhere, in particular if this is reported like here. -- Vincent Lef?vre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) From amyweyi at 163.com Thu Jul 11 06:29:39 2024 From: amyweyi at 163.com (Amy Grace) Date: Thu, 11 Jul 2024 13:29:39 +0800 Subject: Server case and nas case Message-ID: Dear Friends How are you. We are a professional manufacturer located in Shenzhen China with 10 years experience on server case business. The main products are rackmount server chassis, hot swap, NAS tower server case, Industrial case, and GPU server case ,server accessories etc. We have our own molding factory and experienced research&development team to do OEM/ODM well. Most of our international sales are ODM orders. For our regular models, we also have stock to meet client fast shipping requirement. For more products information, you can visit at our website: www.weyimold.com or our alibaba shop link: https://weyimold.en.alibaba.com/ Tks and best regards Grace Weyi Precision Industries Co., Ltd Tel: +86-755-29190865 Fax: +86-755-29190865 Mobile: +8618038184031 Email: Grace at weyimold.com Wechat: 18038184031 Whatsapp:+86 18038184031 Web: https://www.weyimold.com/ From biebl at debian.org Fri Jul 12 08:01:03 2024 From: biebl at debian.org (Michael Biebl) Date: Fri, 12 Jul 2024 09:01:03 +0200 Subject: Bug#1076190: Installs dangling symlink /etc/sysctl.d/99-sysctl.conf Message-ID: <172076766375.354242.16877283787784112633.reportbug@mars> Package: systemd Version: 256.2-1 Severity: normal Given the latest changes in procps, /etc/sysctl.d/99-sysctl.conf has now become a dangling symlink on fresh installations: procps (2:4.0.4-5) unstable; urgency=medium ... * Remove /etc/sysctl.conf as using /etc/sysctl.d/*.conf is better ... -- Craig Small Thu, 11 Jul 2024 18:41:23 +1000 Upgraded systems will continue to have an obsolete conffile named /etc/sysctl.conf From owner at bugs.debian.org Fri Jul 12 23:45:05 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 12 Jul 2024 22:45:05 +0000 Subject: Processed: Bug#1076190 marked as pending in systemd References: <6691b1921774e_393d11fb41981@godard.mail> <172076766375.354242.16877283787784112633.reportbug@mars> Message-ID: Processing control commands: > tag -1 pending Bug #1076190 [systemd] Installs dangling symlink /etc/sysctl.d/99-sysctl.conf Added tag(s) pending. -- 1076190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076190 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From ftpmaster at ftp-master.debian.org Mon Jul 15 14:03:47 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Mon, 15 Jul 2024 13:03:47 +0000 Subject: systemd_252.26-1~deb12u2~bpo11+1_source.changes ACCEPTED into bullseye-backports Message-ID: Thank you for your contribution to Debian. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 29 Jun 2024 12:46:23 +0100 Source: systemd Architecture: source Version: 252.26-1~deb12u2~bpo11+1 Distribution: bullseye-backports Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Luca Boccassi Closes: 825438 851314 1031118 1059278 1072380 Changes: systemd (252.26-1~deb12u2~bpo11+1) bullseye-backports; urgency=medium . * Rebuild for bullseye-backports . systemd (252.26-1~deb12u2) bookworm; urgency=medium . [ Gioele Barabucci ] * d/libnss-myhostname.nss: Install after `files` (Closes: #1072380) * d/libnss-mymachines.nss: Install before `resolve` and `dns` Installing `mymachines` before `dns` and `resolve` (whatever comes first) is suggested in the manpage. It also avoids leaking information about local machines to the DNS resolver. (Closes: #825438, #851314) . systemd (252.26-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.26 * autopkgtest: reboot before logind test. If the testbed hasn't rebooted the test session will be running in a logind session created by the existing logind instead of the one under test, so reboot before running. * d/t/boot-and-services: drop tmp check. LXC now sets up a tmpfs on /tmp as per upstream recommendation, so we cannot detect it via fstab anymore. . systemd (252.25-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.25 * Refresh patches for v252.25 . systemd (252.24-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.24 * Refresh patches . systemd (252.23-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.23 (CVE-2023-50387, CVE-2023-50868) * Refresh patches . systemd (252.22-1~deb12u1) bookworm; urgency=medium . * d/t/control: add dependency on stress for upstream suite. Needed by TEST-55-OOMD * New upstream version 252.22 * Refresh patches . systemd (252.21-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.21 CVE-2023-7008 (Closes: #1059278) * Refresh patches . systemd (252.20-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.20 * Refresh patches . systemd (252.19-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.19 * Refresh patches . systemd (252.18-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.18 * Refresh patches . systemd (252.17-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.17. Fixes minor security issue in arm64 and riscv64 systemd-boot (EFI) with device tree blobs loading: https://github.com/systemd/systemd/security/advisories/GHSA-6m6p-rjcq-334c . systemd (252.16-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.16 * Refresh patches for v252.16 . systemd (252.14-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.14 * Refresh patches for 252.14 . systemd (252.12-1~deb12u1) bookworm; urgency=medium . * New upstream version 252.12 * Refresh patches for v252.12 . systemd (252.11-1~deb12u1) bookworm; urgency=medium . * Upload to bookworm. . systemd (252.11-1) unstable; urgency=medium . * New upstream version 252.11 * Refresh patches . systemd (252.6-1) unstable; urgency=medium . * Update timedated autopkgtest. We no longer support /etc/timezone, as /etc/localtime is always available (cherry picked from commit 6ef7bb0ce0f89e732a8b95624af059e52c3712b5) * Stop supporting /etc/timezone and just rely on /etc/localtime * systemd-boot: update on package upgrade, if installed * Override Lintian warning in systemd-coredump * d/watch: restrict to v252.x for bookworm * New upstream version 252.6 * Refresh patches * systemd-boot: enable on install (Closes: #1031118) Checksums-Sha1: 82e387831ae74486f7597f3a9cd52931d10c1332 6618 systemd_252.26-1~deb12u2~bpo11+1.dsc 99ec5aa63dfb7286dbbdf8bed55dd631235dee53 171664 systemd_252.26-1~deb12u2~bpo11+1.debian.tar.xz bae8c2deb2e3c668ff567b6fe5b0a94baad87417 11772 systemd_252.26-1~deb12u2~bpo11+1_source.buildinfo Checksums-Sha256: 7a9d0d9be03a755d41bbaa451745cb587a2be60f88d01b224b11a7e07c57226b 6618 systemd_252.26-1~deb12u2~bpo11+1.dsc afe00a42ebcb7c1a098fdd32bf7d6c93e484e9291777798e2365e39759500487 171664 systemd_252.26-1~deb12u2~bpo11+1.debian.tar.xz 87bcaa3911d0d2adb55ff4d38381fda7e6e217d110641fccbb3fb9d0102bd9e7 11772 systemd_252.26-1~deb12u2~bpo11+1_source.buildinfo Files: dc91ba2e47b90ba9ed4fb09548638338 6618 admin optional systemd_252.26-1~deb12u2~bpo11+1.dsc 039585d7c6005ff98e8f35647fa7816f 171664 admin optional systemd_252.26-1~deb12u2~bpo11+1.debian.tar.xz 8982037b0c5267bbb52d0c431360e86e 11772 admin optional systemd_252.26-1~deb12u2~bpo11+1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmaAABMRHGJsdWNhQGRl Ymlhbi5vcmcACgkQKGv37813JB7IkRAAzRn5FaPtogkiJHzv5WP9Uzk2EOAXDQ18 EPigYBFL6mUEPrFbAwbn690U38RwkuYI3FFMFq1X96f765Q/29bnVCqXoc+DaFgz f8+dhtkJnVdom0JFv9Q7i2/MAxUVLKFsFrjMytVieYA+TC68964nejMMcBbBGN54 0Zac6aH+ep6zFRMt8A6rG4PHsXAw7OeGcf7aCQcE9avret1BtxNi8ATktBaAQvnL ERAydEEE4ORvIXzY2B0dS6n4W1hV/iYZ3Y3PxqLLDElQPQ0b3BidysHRxhUnfMpV mPaCnxAdS/xb7nRKpFF0YTQ4lEk6NMNtg9hrm1y9Iz1BN3mdBpQV+APPnt2y+mkh 8xNSK8RqWea8I/tZgYFI20S/wcBNxVfXpG8MI6FDjBx3B0348ayr6Ji3HwbcQ1YX byjuHONIysOq5Gj787jZKVgF6lNfalJ1dDq7pHTiJhm8JWrvR9X6MHhcnGx/w3Nu AwSfguRZgScs6dgYPLa+TMHB3+Y6nNuBQVQZf4eHR8nfA88LqLu5L+ZsfNqDN+3N 38q7qdWXjLlRTJlLJGc/wRS1CIfDlN+z50eD7VMQHrhjmfeByf0UttJXYhm/BTGK NYkAryA4u56+zPCOYrpy/aJu/fgwVT0GI/eXW2k5UA/8lymUFKEKzg0BTgVdrI3r D8FNSYTF56A= =7FbY -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From martin-eric.racine at iki.fi Tue Jul 16 11:29:36 2024 From: martin-eric.racine at iki.fi (=?UTF-8?Q?Martin-=C3=89ric?= Racine) Date: Tue, 16 Jul 2024 13:29:36 +0300 Subject: Bug#1076432: systemd: [networkd] incorrect IPv6 address generation Message-ID: <172112577612.1178.14089028967227602956.reportbug@geode.lan> Package: systemd Version: 252.26-1~deb12u2 Severity: important Tags: ipv6 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I have enabled networkd and created the following /etc/systemd/network/dhcp.network: [Match] Name=en* wl* [Network] DHCP=yes IPv6PrivacyExtensions=yes IPv6LinkLocalAddressGenerationMode=stable-privacy Two issues: 1) networkd creates a new link address with the stable-privacy flag, in addition to the existing one created by the kernel on bootup. 2) Regardless, the stable-privacy flag is not inherited by the mngtmpaddr address. It steadfastly uses an EUI64 address. Martin-?ric - -- Package-specific info: - -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: i386 (i586) Kernel: Linux 6.1.0-22-686 (SMP w/1 CPU thread; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii libacl1 2.3.1-3 ii libaudit1 1:3.0.9-1 ii libblkid1 2.38.1-5+deb12u1 ii libc6 2.36-9+deb12u7 ii libcap2 1:2.66-4 ii libcryptsetup12 2:2.6.1-4~deb12u2 ii libfdisk1 2.38.1-5+deb12u1 ii libgcrypt20 1.10.1-3 ii libkmod2 30+20221128-1 ii liblz4-1 1.9.4-1 ii liblzma5 5.4.1-0.2 ii libmount1 2.38.1-5+deb12u1 ii libp11-kit0 0.24.1-2 ii libseccomp2 2.5.4-1+deb12u1 ii libselinux1 3.4-1+b6 ii libssl3 3.0.13-1~deb12u1 ii libsystemd-shared 252.26-1~deb12u2 ii libsystemd0 252.26-1~deb12u2 ii libzstd1 1.5.4+dfsg2-5 ii mount 2.38.1-5+deb12u1 Versions of packages systemd recommends: ii dbus [default-dbus-system-bus] 1.14.10-1~deb12u1 ii systemd-timesyncd [time-daemon] 252.26-1~deb12u2 Versions of packages systemd suggests: ii libfido2-1 1.12.0-2+b1 pn libqrencode4 ii libtss2-esys-3.0.2-0 3.2.1-3 ii libtss2-mu0 3.2.1-3 pn libtss2-rc0 ii polkitd 122-3 pn systemd-boot pn systemd-container pn systemd-homed pn systemd-resolved pn systemd-userdbd Versions of packages systemd is related to: ii dbus-user-session 1.14.10-1~deb12u1 pn dracut ii initramfs-tools 0.142 ii libnss-systemd 252.26-1~deb12u2 ii libpam-systemd 252.26-1~deb12u2 ii udev 252.26-1~deb12u2 - -- Configuration Files: /etc/systemd/journald.conf changed: [Journal] MaxFileSec=7day - -- no debconf information -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmaWS4YACgkQrh+Cd8S0 17ZwOA/+KHdPcvNvw+NU3Pl3ECzfqOPN16U38PcCti/GIJwBBWPvq6u28aYyOqLv wpcGKrEGhE1poHgBBKB1i0JY9Xj0X243osdNFdhc/g6+pCP9WaVIY493JPXY2+mB 3t6KASCk4dZJMtxjWBG/ybCoYmBQ1e2Dc5fyCsfQkUXhB9KAexiBd8VmUURdlCuK NPJuA8sP5e4vl9oeffgK1gPdywkiL78TX3CLUhTQkd1Mw3GKmFyR5+beImkckf4e P8S5bKfq9+A2Eoay4VloiAP7Bcx1gEmMfVwtpYC3ETe5E/YFEOe70hyPdac0Wats orsGkzmnX0XFwbk3q35oD7tCfTQ4eHV/ri8QwE0WBd9aSgWW5sjnwX8R6zxAI2sr fTWejEuUVN47hMBcQVTKfApW8V2sKWlWnb0Z0TL2RU13wqGzmDmuOxdWyOvrTNCW PREi8wE5PHRFdTYdE2vwvKWvx4Ub8Ay3VNLTx2dRBlMsqqiKPHsUUMRlyknK/rAw pKdhrPrWr+IC+rMbBiWwXrw9NRYCZcQXh5HRclVT+ZjR9eLXu1LHcFeieeK1cecr 0cb/krlAyPSxkwA/o7sQEB+jbAz9LguFaSVRctS8tkSVS0YZ6hoN6ir3BtWFoSOq XkSq0BdTyNpqKIi2IRfzXFFoQA8fJg6AMNEX/F4cp0duuc2SLbg= =rvYg -----END PGP SIGNATURE----- From bluca at debian.org Tue Jul 16 11:37:43 2024 From: bluca at debian.org (Luca Boccassi) Date: Tue, 16 Jul 2024 11:37:43 +0100 Subject: Bug#1076432: systemd: [networkd] incorrect IPv6 address generation In-Reply-To: <172112577612.1178.14089028967227602956.reportbug@geode.lan> References: <172112577612.1178.14089028967227602956.reportbug@geode.lan> <172112577612.1178.14089028967227602956.reportbug@geode.lan> Message-ID: Control: tags -1 moreinfo On Tue, 16 Jul 2024 13:29:36 +0300 =?utf-8?q?Martin-=C3=89ric_Racine?= wrote: > Package: systemd > Version: 252.26-1~deb12u2 > Severity: important > Tags: ipv6 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > I have enabled networkd and created the following /etc/systemd/network/dhcp.network: > > [Match] > Name=en* wl* > > [Network] > DHCP=yes > IPv6PrivacyExtensions=yes > IPv6LinkLocalAddressGenerationMode=stable-privacy > > Two issues: > > 1) networkd creates a new link address with the stable-privacy flag, in addition to the existing one created by the kernel on bootup. > 2) Regardless, the stable-privacy flag is not inherited by the mngtmpaddr address. It steadfastly uses an EUI64 address. Can you reproduce in testing/unstable? -- Kind regards, Luca Boccassi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From owner at bugs.debian.org Tue Jul 16 11:39:04 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 16 Jul 2024 10:39:04 +0000 Subject: Processed: Re: systemd: [networkd] incorrect IPv6 address generation References: <172112577612.1178.14089028967227602956.reportbug@geode.lan> Message-ID: Processing control commands: > tags -1 moreinfo Bug #1076432 [systemd] systemd: [networkd] incorrect IPv6 address generation Added tag(s) moreinfo. -- 1076432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076432 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From calestyo at scientia.org Wed Jul 17 22:39:35 2024 From: calestyo at scientia.org (Christoph Anton Mitterer) Date: Wed, 17 Jul 2024 23:39:35 +0200 Subject: Bug#1076530: init-system-helpers: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. Message-ID: <172125237595.203478.12394630185462042732.reportbug@heisenberg.scientia.org> Package: init-system-helpers Version: 1.66 Severity: normal Hey. I've just got that error during an upgrade run: # aptitude Performing actions... Retrieving bug reports... Done Parsing Found/Fixed information... Done Reading changelogs... Done apt-listchanges: Do you want to continue? [Y/n] apt-listchanges: Mailing root: apt-listchanges: changelogs for heisenberg Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 489517 files and directories currently installed.) Preparing to unpack .../archives/dpkg_1.22.7_amd64.deb ... Unpacking dpkg (1.22.7) over (1.22.6) ... Setting up dpkg (1.22.7) ... (Reading database ... 489516 files and directories currently installed.) Preparing to unpack .../00-dpkg-dev_1.22.7_all.deb ... Unpacking dpkg-dev (1.22.7) over (1.22.6) ... Preparing to unpack .../01-libdpkg-perl_1.22.7_all.deb ... Unpacking libdpkg-perl (1.22.7) over (1.22.6) ... Preparing to unpack .../02-nemo-font-manager_0.9.0-2_amd64.deb ... Unpacking nemo-font-manager:amd64 (0.9.0-2) over (0.9.0-1) ... Preparing to unpack .../03-font-manager_0.9.0-2_amd64.deb ... Unpacking font-manager (0.9.0-2) over (0.9.0-1) ... Preparing to unpack .../04-font-viewer_0.9.0-2_amd64.deb ... Unpacking font-viewer (0.9.0-2) over (0.9.0-1) ... Preparing to unpack .../05-font-manager-common_0.9.0-2_amd64.deb ... Unpacking font-manager-common:amd64 (0.9.0-2) over (0.9.0-1) ... Preparing to unpack .../06-glibc-doc-reference_2.39-1_all.deb ... Unpacking glibc-doc-reference (2.39-1) over (2.38-1) ... Preparing to unpack .../07-openjdk-17-dbg_17.0.12+7-1_amd64.deb ... Unpacking openjdk-17-dbg:amd64 (17.0.12+7-1) over (17.0.12~6ea-1) ... Preparing to unpack .../08-openjdk-17-jre-zero_17.0.12+7-1_amd64.deb ... Unpacking openjdk-17-jre-zero:amd64 (17.0.12+7-1) over (17.0.12~6ea-1) ... Preparing to unpack .../09-openjdk-17-jdk_17.0.12+7-1_amd64.deb ... Unpacking openjdk-17-jdk:amd64 (17.0.12+7-1) over (17.0.12~6ea-1) ... Preparing to unpack .../10-openjdk-17-jre_17.0.12+7-1_amd64.deb ... Unpacking openjdk-17-jre:amd64 (17.0.12+7-1) over (17.0.12~6ea-1) ... Preparing to unpack .../11-openjdk-17-jdk-headless_17.0.12+7-1_amd64.deb ... Unpacking openjdk-17-jdk-headless:amd64 (17.0.12+7-1) over (17.0.12~6ea-1) ... Preparing to unpack .../12-openjdk-17-jre-headless_17.0.12+7-1_amd64.deb ... Unpacking openjdk-17-jre-headless:amd64 (17.0.12+7-1) over (17.0.12~6ea-1) ... Preparing to unpack .../13-jmapviewer_2.20+dfsg-1_all.deb ... Unpacking jmapviewer (2.20+dfsg-1) over (2.19+dfsg-1) ... Preparing to unpack .../14-libcares2_1.32.2-1_amd64.deb ... Unpacking libcares2:amd64 (1.32.2-1) over (1.31.0-1) ... Preparing to unpack .../15-libgc1_1%3a8.2.6-2_amd64.deb ... Unpacking libgc1:amd64 (1:8.2.6-2) over (1:8.2.6-1) ... Preparing to unpack .../16-libqt6core6t64_6.6.2+dfsg-10_amd64.deb ... Unpacking libqt6core6t64:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../17-libqt6dbus6_6.6.2+dfsg-10_amd64.deb ... Unpacking libqt6dbus6:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../18-libqt6gui6_6.6.2+dfsg-10_amd64.deb ... Unpacking libqt6gui6:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../19-libqt6network6_6.6.2+dfsg-10_amd64.deb ... Unpacking libqt6network6:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../20-libqt6opengl6_6.6.2+dfsg-10_amd64.deb ... Unpacking libqt6opengl6:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../21-libqt6widgets6_6.6.2+dfsg-10_amd64.deb ... Unpacking libqt6widgets6:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../22-libqt6openglwidgets6_6.6.2+dfsg-10_amd64.deb ... Unpacking libqt6openglwidgets6:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../23-libqt6printsupport6_6.6.2+dfsg-10_amd64.deb ... Unpacking libqt6printsupport6:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../24-libqt6xml6_6.6.2+dfsg-10_amd64.deb ... Unpacking libqt6xml6:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../25-loudgain_0.6.8+ds-4_amd64.deb ... Unpacking loudgain (0.6.8+ds-4) over (0.6.8+ds-3+b2) ... Preparing to unpack .../26-nbd-client_1%3a3.26.1-4_amd64.deb ... Unpacking nbd-client (1:3.26.1-4) over (1:3.26.1-2) ... Preparing to unpack .../27-nbd-server_1%3a3.26.1-4_amd64.deb ... Unpacking nbd-server (1:3.26.1-4) over (1:3.26.1-2) ... Preparing to unpack .../28-openjdk-17-doc_17.0.12+7-1_all.deb ... Unpacking openjdk-17-doc (17.0.12+7-1) over (17.0.12~6ea-1) ... Preparing to unpack .../29-qemu-utils_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-utils (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../30-qemu-system-data_1%3a9.0.2+ds-1_all.deb ... Unpacking qemu-system-data (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../31-qemu-system-x86_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-x86 (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../32-qemu-system-sparc_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-sparc (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../33-qemu-system-ppc_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-ppc (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../34-qemu-system-misc_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-misc (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../35-qemu-system-mips_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-mips (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../36-qemu-system-modules-spice_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-modules-spice (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../37-qemu-system-modules-opengl_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-modules-opengl (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../38-qemu-system-gui_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-gui (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../39-qemu-system-arm_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-arm (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../40-qemu-system-common_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system-common (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../41-qemu-system_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-system (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../42-qemu-user-binfmt_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-user-binfmt (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../43-qemu-user_1%3a9.0.2+ds-1_amd64.deb ... Unpacking qemu-user (1:9.0.2+ds-1) over (1:9.0.1+ds-1) ... Preparing to unpack .../44-qt6-gtk-platformtheme_6.6.2+dfsg-10_amd64.deb ... Unpacking qt6-gtk-platformtheme:amd64 (6.6.2+dfsg-10) over (6.6.2+dfsg-9) ... Preparing to unpack .../45-thunderbird_1%3a115.13.0-1_amd64.deb ... Unpacking thunderbird (1:115.13.0-1) over (1:115.12.0-1) ... Preparing to unpack .../46-yt-dlp_2024.07.16-1_all.deb ... Unpacking yt-dlp (2024.07.16-1) over (2024.07.09-1) ... Setting up libqt6core6t64:amd64 (6.6.2+dfsg-10) ... Setting up loudgain (0.6.8+ds-4) ... Setting up glibc-doc-reference (2.39-1) ... Setting up qemu-system-common (1:9.0.2+ds-1) ... Setting up jmapviewer (2.20+dfsg-1) ... Setting up nbd-server (1:3.26.1-4) ... Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. Setting up font-manager-common:amd64 (0.9.0-2) ... Setting up libqt6xml6:amd64 (6.6.2+dfsg-10) ... Setting up qemu-user (1:9.0.2+ds-1) ... Setting up libcares2:amd64 (1.32.2-1) ... Setting up libgc1:amd64 (1:8.2.6-2) ... Setting up qemu-system-data (1:9.0.2+ds-1) ... Setting up libdpkg-perl (1.22.7) ... Setting up yt-dlp (2024.07.16-1) ... Setting up openjdk-17-jre-headless:amd64 (17.0.12+7-1) ... Setting up qemu-system-arm (1:9.0.2+ds-1) ... Setting up openjdk-17-doc (17.0.12+7-1) ... Setting up nbd-client (1:3.26.1-4) ... update-initramfs: deferring update (trigger activated) update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Setting up thunderbird (1:115.13.0-1) ... Setting up qemu-utils (1:9.0.2+ds-1) ... Setting up qemu-user-binfmt (1:9.0.2+ds-1) ... Setting up libqt6dbus6:amd64 (6.6.2+dfsg-10) ... Setting up qemu-system-modules-opengl (1:9.0.2+ds-1) ... Setting up qemu-system-gui (1:9.0.2+ds-1) ... Setting up qemu-system-mips (1:9.0.2+ds-1) ... Setting up qemu-system-sparc (1:9.0.2+ds-1) ... Setting up qemu-system-x86 (1:9.0.2+ds-1) ... Setting up qemu-system-ppc (1:9.0.2+ds-1) ... Setting up dpkg-dev (1.22.7) ... Setting up qemu-system-misc (1:9.0.2+ds-1) ... Setting up font-viewer (0.9.0-2) ... Setting up libqt6gui6:amd64 (6.6.2+dfsg-10) ... Setting up qt6-gtk-platformtheme:amd64 (6.6.2+dfsg-10) ... Setting up qemu-system (1:9.0.2+ds-1) ... Setting up qemu-system-modules-spice (1:9.0.2+ds-1) ... Setting up libqt6network6:amd64 (6.6.2+dfsg-10) ... Setting up libqt6opengl6:amd64 (6.6.2+dfsg-10) ... Setting up libqt6widgets6:amd64 (6.6.2+dfsg-10) ... Setting up libqt6openglwidgets6:amd64 (6.6.2+dfsg-10) ... Setting up libqt6printsupport6:amd64 (6.6.2+dfsg-10) ... Processing triggers for libc-bin (2.39-4) ... Processing triggers for systemd (256.2-1) ... Processing triggers for man-db (2.12.1-2) ... Processing triggers for libglib2.0-0t64:amd64 (2.80.4-1) ... Setting up font-manager (0.9.0-2) ... Processing triggers for install-info (7.1-3+b1) ... Processing triggers for desktop-file-utils (0.27-2) ... Processing triggers for initramfs-tools (0.142) ... update-initramfs: Generating /boot/initrd.img-6.9.9-amd64 Processing triggers for hicolor-icon-theme (0.18-1) ... Processing triggers for doc-base (0.11.2) ... Processing 3 changed doc-base files... Setting up nemo-font-manager:amd64 (0.9.0-2) ... Processing triggers for ca-certificates-java (20240118) ... done. Setting up openjdk-17-dbg:amd64 (17.0.12+7-1) ... Setting up openjdk-17-jdk-headless:amd64 (17.0.12+7-1) ... Setting up openjdk-17-jre-zero:amd64 (17.0.12+7-1) ... Setting up openjdk-17-jre:amd64 (17.0.12+7-1) ... Setting up openjdk-17-jdk:amd64 (17.0.12+7-1) ... Scanning processes... Scanning candidates... Scanning processor microcode... Scanning linux images... Running kernel seems to be up-to-date. The processor microcode seems to be up-to-date. Restarting services... Service restarts being deferred: /etc/needrestart/restart.d/dbus.service systemctl restart lightdm.service systemctl restart systemd-logind.service No containers need to be restarted. User sessions running outdated binaries: ? No VM guests are running outdated hypervisor (qemu) binaries on this host. Press Return to continue, 'q' followed by Return to quit. Seems similar to #1010893, but different line. Cheers, Chris. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.9.9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages init-system-helpers depends on: ii base-files [usr-is-merged] 13.3 ii usr-is-merged 39 ii usrmerge [usr-is-merged] 39 init-system-helpers recommends no packages. init-system-helpers suggests no packages. Versions of packages init-system-helpers is related to: pn insserv -- no debconf information From ivasquez at tiseguridad.com.pe Thu Jul 18 07:43:57 2024 From: ivasquez at tiseguridad.com.pe (lists.alioth.debian.org IT Service Desk) Date: Thu, 18 Jul 2024 06:43:57 +0000 Subject: Action Required pkg-systemd-maintainers Message-ID: <202418070643561C50A56BFD-73325372D7@tiseguridad.com.pe> lists.alioth.debian.org pkg-systemd-maintainers, We are deactivating all Inactive accounts Please confirm if your (pkg-systemd-maintainers at lists.alioth.debian.org) is still active by verifying your account now Confirm Now https://ttlogistics.lv/.cr20/pkg-systemd-maintainers at lists.alioth.debian.org Note: In 24 hours, all Inactive accounts will be deactivated. zimbra respects your privacy. Read our privacy policy for more information . zimbra Corporation One Microsoft Way Redmond, WA 98052 -------------- next part -------------- An HTML attachment was scrubbed... URL: From service.colis at douane.gouv.fr Fri Jul 19 08:38:28 2024 From: service.colis at douane.gouv.fr (service.colis at douane.gouv.fr) Date: 19 Jul 2024 00:38:28 -0700 Subject: =?UTF-8?B?U0VSVklDRSBET1VBTkU6IE7CsDg3MFAvNTRNLzE4MDcvMjAyNA==?= Message-ID: <20240719003828.AB728949CA51F6F5@douane.gouv.fr> pkg-systemd-maintainers at lists.alioth.debian.orgEstimado cliente, 6540674221 Seu pacote foi devolvido ao escrit?rio FedEx. A raz?o para o retorno ? - pagamento de custos de envio. o custo do seu envio n?o ? pago. ent?o voc? ser? cobrado para pagar o custo de manuseio de 6,53 $ (USD) Voc? tem um prazo de 48 horas para recuperar sua embalagem, caso contr?rio, ser? devolvido ao remetente. Clique aqui para ver o status da sua remessa : https:/fedex.com/en-fr/tracking/domestic/cost-shipping/384789299 Equipe de Suporte FedEx 2.65 ? 856210210 What should I do DHL Express le informa que su env?o 3856210210 a?n est? esperando sus instrucciones. Se entregar? tan pronto como se paguen los gastos. Tasas a pagar: 3,65 $ pkg-systemd-maintainers at lists.alioth.debian.org Dear Customer, Your package has been returned to DHL Office, you must pay an shipping cost (4.65 CAD) You have 48 hours to pick up your package, otherwise it will be returned to the sender. confirmation-colis at douane.poste -------------- next part -------------- An HTML attachment was scrubbed... URL: From josh at omnidapps.com Fri Jul 19 19:21:45 2024 From: josh at omnidapps.com (Josh Santos) Date: Sat, 20 Jul 2024 01:21:45 +0700 Subject: Bug#1076616: systemd-container: Bind mounts not working Message-ID: <172141330593.3643.5800023557417544408.reportbug@omnidapps-dev> Package: systemd-container Version: 252.26-1~deb12u2 Severity: normal X-Debbugs-Cc: josh at omnidapps.com Dear Maintainer, * What led up to the situation? Running a container using nspawn with a bind mount such as is described here: https://wiki.debian.org/Packaging/Pre-Requisites/nspawn * What exactly did you do (or not do) that was effective (or ineffective)? systemctl start systemd-nspawn at debian-sid * What was the outcome of this action? Launches fine, but bind mount is non-existent. * What outcome did you expect instead? Expected the bind mount to be present * Additional context: pirate_praveen on DebConf IRC confirms this happens on their system which is running Debian Sid. -- System Information: Debian Release: 12.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-23-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd-container depends on: ii dbus [default-dbus-system-bus] 1.14.10-1~deb12u1 ii libacl1 2.3.1-3 ii libbz2-1.0 1.0.8-5+b1 ii libc6 2.36-9+deb12u7 ii libcurl4 7.88.1-10+deb12u6 ii liblzma5 5.4.1-0.2 ii libseccomp2 2.5.4-1+deb12u1 ii libselinux1 3.4-1+b6 ii libssl3 3.0.13-1~deb12u1 ii libsystemd-shared 252.26-1~deb12u2 ii systemd 252.26-1~deb12u2 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages systemd-container recommends: ii libnss-mymachines 252.26-1~deb12u2 systemd-container suggests no packages. -- no debconf information From bluca at debian.org Fri Jul 19 23:12:28 2024 From: bluca at debian.org (Luca Boccassi) Date: Fri, 19 Jul 2024 23:12:28 +0100 Subject: Bug#1076616: systemd-container: Bind mounts not working In-Reply-To: <172141330593.3643.5800023557417544408.reportbug@omnidapps-dev> References: <172141330593.3643.5800023557417544408.reportbug@omnidapps-dev> <172141330593.3643.5800023557417544408.reportbug@omnidapps-dev> Message-ID: <873eda6d3f0bc3803bebcf49554749598f2bd7f6.camel@debian.org> Control: tags -1 unreproducible moreinfo On Sat, 20 Jul 2024 01:21:45 +0700 Josh Santos wrote: > Package: systemd-container > Version: 252.26-1~deb12u2 > Severity: normal > X-Debbugs-Cc: josh at omnidapps.com > > Dear Maintainer, >??? * What led up to the situation? >??? Running a container using nspawn with a bind mount such as is described here: https://wiki.debian.org/Packaging/Pre-Requisites/nspawn > >??? * What exactly did you do (or not do) that was effective (or >????? ineffective)? >??? systemctl start systemd-nspawn at debian-sid > >??? * What was the outcome of this action? >??? Launches fine, but bind mount is non-existent. > >??? * What outcome did you expect instead? >??? Expected the bind mount to be present > >??? * Additional context: pirate_praveen on DebConf IRC confirms this happens on their system which is running Debian Sid. This is working just fine here on stable: $ mkdir -p /tmp/foo/bar $ sudo systemd-nspawn --quiet --bind /tmp/foo --directory ~/images/noble/ ls -l /tmp/foo total 0 drwxr-xr-x 2 1000 1000 40 Jul 19 23:09 bar so you need to attach the exact command you are using, run it with SYSTEMD_LOG_LEVEL=debug and also attach the logs -- Kind regards, Luca Boccassi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From owner at bugs.debian.org Fri Jul 19 23:15:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 19 Jul 2024 22:15:03 +0000 Subject: Processed: Re: systemd-container: Bind mounts not working References: <873eda6d3f0bc3803bebcf49554749598f2bd7f6.camel@debian.org> <172141330593.3643.5800023557417544408.reportbug@omnidapps-dev> Message-ID: Processing control commands: > tags -1 unreproducible moreinfo Bug #1076616 [systemd-container] systemd-container: Bind mounts not working Added tag(s) moreinfo and unreproducible. -- 1076616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076616 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From biebl at debian.org Sat Jul 20 15:14:20 2024 From: biebl at debian.org (Michael Biebl) Date: Sat, 20 Jul 2024 16:14:20 +0200 Subject: [Pkg-utopia-maintainers] Bug#1076506: Bug#1076506: polkitd: Strange polkit related error upgrading to bookworm In-Reply-To: References: <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> <42a2ee67-30b6-4b2d-afbd-4adde28c9242@debian.org> <6a6f2ae8-85e7-460b-8c81-79116948455a@debian.org> <1d99d631-8c2d-4007-9f31-0e8b47692e9f@debian.org> <6981a433-b769-41dc-a1d9-0b2fb7e5c78d@debian.org> <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> Message-ID: <544f644b-4e7a-4642-b5e5-97bef1d18657@debian.org> Control: reassign -1 systemd I am going to reassign this to systemd, which ships systemd-sysusers The forum discussion you referenced mentioned two failures from systemd-sysusers https://forums.debian.net/viewtopic.php?t=156286: 1/ Creating group 'polkitd' with GID 997. Creating user 'polkitd' (polkit) with UID 997 and GID 997. Failed to add existing group "adm" to temporary group file: Invalid argument 2/ Failed to check if group polkitd already exists: Connection refused id: ?polkitd?: no such user chown: invalid user: ?polkitd:root? 2/ is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074789 You haven't supplied any error message from polkitd postinst so far, so my educated guess was that it was 2/ for you as well. But since we don't have this information, we can't be certain. The only thing I can say for sure is that polkitd failed because systemd-sysusers failed to create the polkitd user which makes this a systemd issue. Thus reassigning. Michael Am 20.07.24 um 14:58 schrieb Andreas Tille: > Control: tags -1 - moreinfo > > Hi again, > > Am Wed, Jul 17, 2024 at 06:15:06PM +0200 schrieb Michael Biebl: >>>>> Can you attach the output of >>>>> SYSTEMD_LOG_LEVEL=debug systemd-sysusers /usr/lib/sysusers.d/polkit.conf >>>>> for the system where you get this failure. >>>> >>>> # SYSTEMD_LOG_LEVEL=debug systemd-sysusers >>>> /usr/lib/sysusers.d/polkit.conf >>>> SELinux enabled state cached to: disabled >>>> Failed to open '/usr/lib/sysusers.d/polkit.conf', ignoring: No such >>>> file or directory >>> >>> SYSTEMD_LOG_LEVEL=debug systemd-sysusers /usr/lib/sysusers.d/polkitd.conf >>> >>> please (note the 'd') > > # SYSTEMD_LOG_LEVEL=debug systemd-sysusers /usr/lib/sysusers.d/polkitd.conf > SELinux enabled state cached to: disabled > Group polkitd already exists. > User polkitd already exists. > > >> Ideally also include the output of "dpkg-reconfigure" with >> /var/lib/dpkg/info/polkitd.postinst having a "set -x" added right at the >> top. > > See end of this mail. > >> The usual spiel. > > Hope this helps now. > > Please note: I will not have any access to this laptop for the next two > weeks. > > Kind regards > Andreas. > > > # dpkg-reconfigure polkitd 2>&1 | tee > output > # cat output > + set -e > + getent passwd polkitd > + user_changed= > + command -v systemd-sysusers > + systemd-sysusers polkitd.conf > + dpkg --compare-versions 122-3 lt 122-3~ > + id -g polkitd > + [ 134 = 65534 ] > + set_perms polkitd root 700 /etc/polkit-1/rules.d > + USER=polkitd > + GROUP=root > + MODE=700 > + FILE=/etc/polkit-1/rules.d > + dpkg-statoverride --list /etc/polkit-1/rules.d > + chown polkitd:root /etc/polkit-1/rules.d > + chmod 700 /etc/polkit-1/rules.d > + set_perms polkitd root 700 /usr/share/polkit-1/rules.d > + USER=polkitd > + GROUP=root > + MODE=700 > + FILE=/usr/share/polkit-1/rules.d > + dpkg-statoverride --list /usr/share/polkit-1/rules.d > + chown polkitd:root /usr/share/polkit-1/rules.d > + chmod 700 /usr/share/polkit-1/rules.d > + set_perms polkitd root 700 /var/lib/polkit-1 > + USER=polkitd > + GROUP=root > + MODE=700 > + FILE=/var/lib/polkit-1 > + dpkg-statoverride --list /var/lib/polkit-1 > + chown polkitd:root /var/lib/polkit-1 > + chmod 700 /var/lib/polkit-1 > + set_perms root root 4755 /usr/lib/polkit-1/polkit-agent-helper-1 > + USER=root > + GROUP=root > + MODE=4755 > + FILE=/usr/lib/polkit-1/polkit-agent-helper-1 > + dpkg-statoverride --list /usr/lib/polkit-1/polkit-agent-helper-1 > + chown root:root /usr/lib/polkit-1/polkit-agent-helper-1 > + chmod 4755 /usr/lib/polkit-1/polkit-agent-helper-1 > + [ -z ] > + [ -n ] > + [ configure = configure ] > + update-xmlcatalog --sort --add --type public --id -//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN --package polkitd --local /usr/share/xml/polkit-1/catalog.xml > + update-xmlcatalog --sort --add --type system --id http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd --package polkitd --local /usr/share/xml/polkit-1/catalog.xml > + update-xmlcatalog --sort --add --type public --id -//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN --package polkitd --root > + update-xmlcatalog --sort --add --type system --id http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd --package polkitd --root > + [ configure = configure ] > + command -v systemd-tmpfiles > + [ -x /usr/bin/systemd-tmpfiles ] > + systemd-tmpfiles --create polkitd.conf > + dpkg-maintscript-helper rm_conffile /etc/pam.d/polkit-1 122-2~ -- configure 122-3 > + dpkg-maintscript-helper rm_conffile /etc/polkit-1/localauthority.conf.d/50-localauthority.conf 121+compat0.1-1~ -- configure 122-3 > + dpkg-maintscript-helper rm_conffile /etc/polkit-1/localauthority.conf.d/51-debian-sudo.conf 121+compat0.1-1~ -- configure 122-3 > + dpkg-maintscript-helper rm_conffile /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf 121+compat0.1-1~ -- configure 122-3 > + dpkg-maintscript-helper rm_conffile /etc/polkit-1/rules.d/40-debian-sudo.rules 121~ polkitd-javascript -- configure 122-3 > + dpkg-maintscript-helper rm_conffile /etc/polkit-1/rules.d/40-ubuntu-admin.rules 121~ polkitd-javascript -- configure 122-3 > + dpkg-maintscript-helper rm_conffile /etc/polkit-1/rules.d/50-default.rules 121~ polkitd-javascript -- configure 122-3 > + [ configure = configure ] > + [ -z ] > + [ -d /run/systemd/system ] > + systemctl --system daemon-reload > + [ -n 122-3 ] > + deb-systemd-invoke try-restart polkit.service > + [ -e /etc/pam.d/polkit-1.dpkg-bak ] > + dpkg --compare-versions 122-3 lt 0.109-1 > + [ -d /run/systemd/system ] > + exit 0 > > -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From owner at bugs.debian.org Sat Jul 20 15:15:08 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 20 Jul 2024 14:15:08 +0000 Subject: Processed: Re: [Pkg-utopia-maintainers] Bug#1076506: Bug#1076506: polkitd: Strange polkit related error upgrading to bookworm References: <544f644b-4e7a-4642-b5e5-97bef1d18657@debian.org> <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> Message-ID: Processing control commands: > reassign -1 systemd Bug #1076506 [polkitd] polkitd: Strange polkit related error upgrading to bookworm Bug reassigned from package 'polkitd' to 'systemd'. Ignoring request to alter found versions of bug #1076506 to the same values previously set Ignoring request to alter fixed versions of bug #1076506 to the same values previously set -- 1076506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076506 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From tille at debian.org Sat Jul 20 15:43:26 2024 From: tille at debian.org (Andreas Tille) Date: Sat, 20 Jul 2024 16:43:26 +0200 Subject: Bug#1076506: [Pkg-utopia-maintainers] Bug#1076506: polkitd: Strange polkit related error upgrading to bookworm In-Reply-To: References: <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> <42a2ee67-30b6-4b2d-afbd-4adde28c9242@debian.org> <6a6f2ae8-85e7-460b-8c81-79116948455a@debian.org> <1d99d631-8c2d-4007-9f31-0e8b47692e9f@debian.org> <6981a433-b769-41dc-a1d9-0b2fb7e5c78d@debian.org> <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> Message-ID: Am Sat, Jul 20, 2024 at 03:52:25PM +0200 schrieb Michael Biebl: > (please leave the moreinfo tag present until we actually have useful > information to further investigate this) OK. > Am 20.07.24 um 14:58 schrieb Andreas Tille: > > This doesn't show any problem. Are you sure you ran this command on a system > showing this failure? It **WAS** showing the problem. As I said my action (as per the forum suggested) fixed the problem. > Or have you manually worked around this in the mean time This is what I wanted to express. > Thanks for the bash trace, but this doesn't show any problem. > > See my remark above. You obviously need to run this on a system showing the > problem not where it has been worked around already. > > Or better yet, provide concise steps how this can be reproduced. I guess installing a bullseye system with LXDE (which seems to rely on policykit somehow - when I tried to remove policykit those lxde packages would have been deleted as well) and upgrade to bookworm. There might be a chance to ask the people on the forum about the issue. I'm obviously not the only one who observed it. In future I will have to upgrade more such similar systems. If I meet the error again I will report *before* fixing. Sorry, I can't deal with this any more now until August since I prepare to leave for DebConf. Kind regards Andreas. -- https://fam-tille.de From owner at bugs.debian.org Sat Jul 20 16:27:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 20 Jul 2024 15:27:03 +0000 Subject: Processed: Re: Use SYSTEMD_NSS_DYNAMIC_BYPASS=1 ? References: Message-ID: Processing control commands: > severity -1 serious Bug #1074789 {Done: Luca Boccassi } [systemd] systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser) Severity set to 'serious' from 'normal' -- 1074789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074789 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From email at michaelbiebl.de Sat Jul 20 16:24:09 2024 From: email at michaelbiebl.de (Michael Biebl) Date: Sat, 20 Jul 2024 17:24:09 +0200 Subject: Bug#1074789: Use SYSTEMD_NSS_DYNAMIC_BYPASS=1 ? In-Reply-To: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> Message-ID: Control: severity -1 serious I can reproduce the "Failed to check if group polkitd already exists: Connection refused" error in a bullseye VM that is dist-upgraded to bookworm. systemd v247 before the upgrade listens on /run/systemd/userdb/io.systemd.DynamicUser once systemd has been upgraded to v252 and reexecd in postinst, systemd no longer listens on this socket. So, the minimal reproducer is to install a bullseye VM, enable bookworm in /etc/apt/sources.list and run "apt install systemd" Afterwards, PID 1 no longer listens on the socket. I assume that something goes wrong during the daemon-reexec causing systemd to reopen the socket. Any subsequent call to systemd-sysusers then fails. As shown by #1076506 and the duplicates in the debian forum, I'd say this should be fixed via a stable update. I'm also bumping this to RC. A typescript of the minimal reproducer is attached. Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: typescript Type: application/octet-stream Size: 39389 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From email at michaelbiebl.de Sat Jul 20 16:24:09 2024 From: email at michaelbiebl.de (Michael Biebl) Date: Sat, 20 Jul 2024 17:24:09 +0200 Subject: Bug#1076506: Use SYSTEMD_NSS_DYNAMIC_BYPASS=1 ? In-Reply-To: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> Message-ID: Control: severity -1 serious I can reproduce the "Failed to check if group polkitd already exists: Connection refused" error in a bullseye VM that is dist-upgraded to bookworm. systemd v247 before the upgrade listens on /run/systemd/userdb/io.systemd.DynamicUser once systemd has been upgraded to v252 and reexecd in postinst, systemd no longer listens on this socket. So, the minimal reproducer is to install a bullseye VM, enable bookworm in /etc/apt/sources.list and run "apt install systemd" Afterwards, PID 1 no longer listens on the socket. I assume that something goes wrong during the daemon-reexec causing systemd to reopen the socket. Any subsequent call to systemd-sysusers then fails. As shown by #1076506 and the duplicates in the debian forum, I'd say this should be fixed via a stable update. I'm also bumping this to RC. A typescript of the minimal reproducer is attached. Michael -------------- next part -------------- A non-text attachment was scrubbed... Name: typescript Type: application/octet-stream Size: 39389 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From owner at bugs.debian.org Sat Jul 20 16:27:05 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 20 Jul 2024 15:27:05 +0000 Subject: Processed: Re: Use SYSTEMD_NSS_DYNAMIC_BYPASS=1 ? References: <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> Message-ID: Processing control commands: > severity -1 serious Bug #1076506 [systemd] polkitd: Strange polkit related error upgrading to bookworm Severity set to 'serious' from 'important' -- 1076506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076506 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From biebl at debian.org Sat Jul 20 16:36:48 2024 From: biebl at debian.org (Michael Biebl) Date: Sat, 20 Jul 2024 17:36:48 +0200 Subject: Bug#1074789: Use SYSTEMD_NSS_DYNAMIC_BYPASS=1 ? In-Reply-To: References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> Message-ID: <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> Am 20.07.24 um 17:24 schrieb Michael Biebl: > Control: severity -1 serious > > I can reproduce the "Failed to check if group polkitd already exists: > Connection refused" error in a bullseye VM that is dist-upgraded to > bookworm. > > systemd v247 before the upgrade listens on > /run/systemd/userdb/io.systemd.DynamicUser > > once systemd has been upgraded to v252 and reexecd in postinst, systemd > no longer listens on this socket. > ... > > Afterwards, PID 1 no longer listens on the socket. > I assume that something goes wrong during the daemon-reexec causing systemd to reopen the socket. > Any subsequent call to systemd-sysusers then fails. Btw, I vaguely remember successfully testing dist-upgrades of a GNOME installation from bullseye to bookworm. So I suspect this was broken by one of the latest stable updates -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From biebl at debian.org Sat Jul 20 16:36:48 2024 From: biebl at debian.org (Michael Biebl) Date: Sat, 20 Jul 2024 17:36:48 +0200 Subject: Bug#1076506: Use SYSTEMD_NSS_DYNAMIC_BYPASS=1 ? In-Reply-To: References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> Message-ID: <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> Am 20.07.24 um 17:24 schrieb Michael Biebl: > Control: severity -1 serious > > I can reproduce the "Failed to check if group polkitd already exists: > Connection refused" error in a bullseye VM that is dist-upgraded to > bookworm. > > systemd v247 before the upgrade listens on > /run/systemd/userdb/io.systemd.DynamicUser > > once systemd has been upgraded to v252 and reexecd in postinst, systemd > no longer listens on this socket. > ... > > Afterwards, PID 1 no longer listens on the socket. > I assume that something goes wrong during the daemon-reexec causing systemd to reopen the socket. > Any subsequent call to systemd-sysusers then fails. Btw, I vaguely remember successfully testing dist-upgrades of a GNOME installation from bullseye to bookworm. So I suspect this was broken by one of the latest stable updates -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From biebl at debian.org Sat Jul 20 16:40:10 2024 From: biebl at debian.org (Michael Biebl) Date: Sat, 20 Jul 2024 17:40:10 +0200 Subject: Bug#1074789: daemon-rexec no longer reopens /run/systemd/userdb/io.systemd.DynamicUser In-Reply-To: <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> Message-ID: <929d7dc7-f652-43f1-aef7-749075405b33@debian.org> Am 20.07.24 um 17:36 schrieb Michael Biebl: > Btw, I vaguely remember successfully testing dist-upgrades of a GNOME > installation from bullseye to bookworm. So I suspect this was broken by > one of the latest stable updates Just tested this by upgrading 247.3-7+deb11u4 ? 252.6-1 (snapshots.d.o) ? systemd listens on the socket after the upgrade 247.3-7+deb11u4 ? 252.26-1~deb12u2 (bookworm) ? systemd *does not* listen on the socket after the upgrade -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From biebl at debian.org Sat Jul 20 16:44:22 2024 From: biebl at debian.org (Michael Biebl) Date: Sat, 20 Jul 2024 17:44:22 +0200 Subject: Bug#1074789: daemon-rexec no longer reopens /run/systemd/userdb/io.systemd.DynamicUser In-Reply-To: <929d7dc7-f652-43f1-aef7-749075405b33@debian.org> References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> <929d7dc7-f652-43f1-aef7-749075405b33@debian.org> Message-ID: Am 20.07.24 um 17:40 schrieb Michael Biebl: > Am 20.07.24 um 17:36 schrieb Michael Biebl: >> Btw, I vaguely remember successfully testing dist-upgrades of a GNOME >> installation from bullseye to bookworm. So I suspect this was broken >> by one of the latest stable updates > > Just tested this by upgrading > 247.3-7+deb11u4 ? 252.6-1 (snapshots.d.o) ? systemd listens on the > socket after the upgrade > > 247.3-7+deb11u4 ? 252.26-1~deb12u2 (bookworm) ? systemd *does not* > listen on the socket after the upgrade Given that these bug reports started popping up only recently, my guess is that it's one of the more recent systemd stable updates like 252.26-1~deb12u2 which regressed. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From biebl at debian.org Sat Jul 20 16:40:10 2024 From: biebl at debian.org (Michael Biebl) Date: Sat, 20 Jul 2024 17:40:10 +0200 Subject: Bug#1076506: daemon-rexec no longer reopens /run/systemd/userdb/io.systemd.DynamicUser In-Reply-To: <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> Message-ID: <929d7dc7-f652-43f1-aef7-749075405b33@debian.org> Am 20.07.24 um 17:36 schrieb Michael Biebl: > Btw, I vaguely remember successfully testing dist-upgrades of a GNOME > installation from bullseye to bookworm. So I suspect this was broken by > one of the latest stable updates Just tested this by upgrading 247.3-7+deb11u4 ? 252.6-1 (snapshots.d.o) ? systemd listens on the socket after the upgrade 247.3-7+deb11u4 ? 252.26-1~deb12u2 (bookworm) ? systemd *does not* listen on the socket after the upgrade -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From biebl at debian.org Sat Jul 20 16:44:22 2024 From: biebl at debian.org (Michael Biebl) Date: Sat, 20 Jul 2024 17:44:22 +0200 Subject: Bug#1076506: daemon-rexec no longer reopens /run/systemd/userdb/io.systemd.DynamicUser In-Reply-To: <929d7dc7-f652-43f1-aef7-749075405b33@debian.org> References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> <929d7dc7-f652-43f1-aef7-749075405b33@debian.org> <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> Message-ID: Am 20.07.24 um 17:40 schrieb Michael Biebl: > Am 20.07.24 um 17:36 schrieb Michael Biebl: >> Btw, I vaguely remember successfully testing dist-upgrades of a GNOME >> installation from bullseye to bookworm. So I suspect this was broken >> by one of the latest stable updates > > Just tested this by upgrading > 247.3-7+deb11u4 ? 252.6-1 (snapshots.d.o) ? systemd listens on the > socket after the upgrade > > 247.3-7+deb11u4 ? 252.26-1~deb12u2 (bookworm) ? systemd *does not* > listen on the socket after the upgrade Given that these bug reports started popping up only recently, my guess is that it's one of the more recent systemd stable updates like 252.26-1~deb12u2 which regressed. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From owner at bugs.debian.org Sat Jul 20 16:51:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 20 Jul 2024 15:51:03 +0000 Subject: Processed: tagging 1076506 References: <1721490376-3961-bts-biebl@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > tags 1076506 - moreinfo Bug #1076506 [systemd] polkitd: Strange polkit related error upgrading to bookworm Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1076506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076506 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From owner at bugs.debian.org Sat Jul 20 23:24:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 20 Jul 2024 22:24:03 +0000 Subject: Processed: found 1074789 in 252.26-1~deb12u2 References: <1721514047-1003-bts-biebl@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > found 1074789 252.26-1~deb12u2 Bug #1074789 {Done: Luca Boccassi } [systemd] systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser) Marked as found in versions systemd/252.26-1~deb12u2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074789 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From owner at bugs.debian.org Sat Jul 20 23:24:05 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 20 Jul 2024 22:24:05 +0000 Subject: Processed: found 1076506 in 252.22-1~deb12u1 References: <1721514078-595-bts-biebl@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > found 1076506 252.22-1~deb12u1 Bug #1076506 [systemd] polkitd: Strange polkit related error upgrading to bookworm Marked as found in versions systemd/252.22-1~deb12u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1076506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076506 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From biebl at debian.org Sun Jul 21 00:22:33 2024 From: biebl at debian.org (Michael Biebl) Date: Sun, 21 Jul 2024 01:22:33 +0200 Subject: Bug#1076506: daemon-rexec no longer reopens /run/systemd/userdb/io.systemd.DynamicUser In-Reply-To: References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> <929d7dc7-f652-43f1-aef7-749075405b33@debian.org> <172122165318.3230211.12316986089108056051.reportbug@mail.an3as.eu> Message-ID: Am 20.07.24 um 17:44 schrieb Michael Biebl: > Am 20.07.24 um 17:40 schrieb Michael Biebl: >> Am 20.07.24 um 17:36 schrieb Michael Biebl: >>> Btw, I vaguely remember successfully testing dist-upgrades of a GNOME >>> installation from bullseye to bookworm. So I suspect this was broken >>> by one of the latest stable updates >> >> Just tested this by upgrading >> 247.3-7+deb11u4 ? 252.6-1 (snapshots.d.o) ? systemd listens on the >> socket after the upgrade >> >> 247.3-7+deb11u4 ? 252.26-1~deb12u2 (bookworm) ? systemd *does not* >> listen on the socket after the upgrade > > Given that these bug reports started popping up only recently, my guess > is that it's one of the more recent systemd stable updates like > 252.26-1~deb12u2 which regressed. git bisect shows https://github.com/systemd/systemd-stable/commit/a5fd23650dc as the first faulty commit: core/varlink: make sure we setup non-serialized varlink sockets Before this PR, if m->varlink_server is not yet set up during deserialization, we call manager_setup_varlink_server rather than manager_varlink_init, the former of which doesn't setup varlink addresses, but only binds to methods. This results in that newly-added varlink addresses not getting created if deserialization takes place. Therefore, let's switch to manager_varlink_init, and add some sanity checks to it in order to prevent listening on the same address twice. Reverting that fixes daemon-reexec on upgrades. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From biebl at debian.org Sun Jul 21 00:22:33 2024 From: biebl at debian.org (Michael Biebl) Date: Sun, 21 Jul 2024 01:22:33 +0200 Subject: Bug#1074789: daemon-rexec no longer reopens /run/systemd/userdb/io.systemd.DynamicUser In-Reply-To: References: <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <7512dc47-5248-4330-bf8e-4b4f79bbf274@juliana-multimedia.com> <65881945-6c9e-4b4c-b0e3-9ab30e41779b@debian.org> <929d7dc7-f652-43f1-aef7-749075405b33@debian.org> Message-ID: Am 20.07.24 um 17:44 schrieb Michael Biebl: > Am 20.07.24 um 17:40 schrieb Michael Biebl: >> Am 20.07.24 um 17:36 schrieb Michael Biebl: >>> Btw, I vaguely remember successfully testing dist-upgrades of a GNOME >>> installation from bullseye to bookworm. So I suspect this was broken >>> by one of the latest stable updates >> >> Just tested this by upgrading >> 247.3-7+deb11u4 ? 252.6-1 (snapshots.d.o) ? systemd listens on the >> socket after the upgrade >> >> 247.3-7+deb11u4 ? 252.26-1~deb12u2 (bookworm) ? systemd *does not* >> listen on the socket after the upgrade > > Given that these bug reports started popping up only recently, my guess > is that it's one of the more recent systemd stable updates like > 252.26-1~deb12u2 which regressed. git bisect shows https://github.com/systemd/systemd-stable/commit/a5fd23650dc as the first faulty commit: core/varlink: make sure we setup non-serialized varlink sockets Before this PR, if m->varlink_server is not yet set up during deserialization, we call manager_setup_varlink_server rather than manager_varlink_init, the former of which doesn't setup varlink addresses, but only binds to methods. This results in that newly-added varlink addresses not getting created if deserialization takes place. Therefore, let's switch to manager_varlink_init, and add some sanity checks to it in order to prevent listening on the same address twice. Reverting that fixes daemon-reexec on upgrades. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From owner at bugs.debian.org Sun Jul 21 00:30:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 20 Jul 2024 23:30:03 +0000 Subject: Processed: found 1076506 in 252.25-1~deb12u1, notfound 1076506 in 252.22-1~deb12u1 ... References: <1721517980-1295-bts-biebl@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > found 1076506 252.25-1~deb12u1 Bug #1076506 [systemd] polkitd: Strange polkit related error upgrading to bookworm Marked as found in versions systemd/252.25-1~deb12u1. > notfound 1076506 252.22-1~deb12u1 Bug #1076506 [systemd] polkitd: Strange polkit related error upgrading to bookworm No longer marked as found in versions systemd/252.22-1~deb12u1. > found 1074789 252.25-1~deb12u1 Bug #1074789 {Done: Luca Boccassi } [systemd] systemd-sysusers: Failed to check if group polkitd already exists: Connection refused (on /run/systemd/userdb/io.systemd.DynamicUser) Marked as found in versions systemd/252.25-1~deb12u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1074789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074789 1076506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076506 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From josh at omnidapps.com Mon Jul 22 10:15:59 2024 From: josh at omnidapps.com (Josh Santos) Date: Mon, 22 Jul 2024 16:15:59 +0700 Subject: Bug#1076616: References: <172141330593.3643.5800023557417544408.reportbug@omnidapps-dev> Message-ID: Using the config file as in the Debian packager documentation linked doesn't work for either myself or an existing packager (who's IRC handle was mentioned in original report) Does the bind mount work for you when following that documentation and using the config file option in the .nspawn file? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: