Bug#1053750: linux-image-6.1.0-13-amd64: "Hardware Error" during shutdown that is not a hardware problem
Hi again, the error log in my previous message comes from this directory: /var/lib/systemd/pstore/7285820828300/ Each time the system reboots, a new directory is created, and 3 files are created in it. For the sake of completeness, here are the 3 files. Thanks, -- Laurent.dmesg-erst-7285820828300607490: Panic#1 Part2 <5>[1.135130] integrity: Loaded X.509 cert 'VMware, Inc.: VMware Secure Boot Signing: 04597f3e1ffb240bba0ff0f05d5eb05f3e15f6d7' <6>[1.136689] ima: No TPM chip found, activating TPM-bypass! <6>[1.136694] ima: Allocated hash algorithm: sha256 <6>[1.136721] ima: No architecture policies found <6>[1.136760] evm: Initialising EVM extended attributes: <6>[1.136762] evm: security.selinux <6>[1.136766] evm: security.SMACK64 (disabled) <6>[1.136769] evm: security.SMACK64EXEC (disabled) <6>[1.136772] evm: security.SMACK64TRANSMUTE (disabled) <6>[1.136775] evm: security.SMACK64MMAP (disabled) <6>[1.136778] evm: security.apparmor <6>[1.136781] evm: security.ima <6>[1.136783] evm: security.capability <6>[1.136786] evm: HMAC attrs: 0x1 <6>[1.244727] Freeing unused decrypted memory: 2036K <6>[1.246191] Freeing unused kernel image (initmem) memory: 2772K <6>[1.254388] Write protecting the kernel read-only data: 26624k <6>[1.256215] Freeing unused kernel image (text/rodata gap) memory: 2040K <6>[1.256858] Freeing unused kernel image (rodata/data gap) memory: 1108K <6>[1.316031] x86/mm: Checked W+X mappings: passed, no W+X pages found. <6>[1.316033] x86/mm: Checking user space page tables <6>[1.362096] x86/mm: Checked W+X mappings: passed, no W+X pages found. <6>[1.362100] Run /init as init process <7>[1.362101] with arguments: <7>[1.362103] /init <7>[1.362104] with environment: <7>[1.362105] HOME=/ <7>[1.362105] TERM=linux <7>[1.362106] BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 <5>[1.646867] lpc_ich :00:1f.0: I/O space for ACPI uninitialized <4>[1.646872] lpc_ich :00:1f.0: No MFD cells added <6>[1.650428] dca service started, version 1.12.1 <6>[1.650969] ACPI: bus type USB registered <6>[1.652413] usbcore: registered new interface driver usbfs <6>[1.652730] usbcore: registered new interface driver hub <6>[1.653398] usbcore: registered new device driver usb <5>[1.653422] SCSI subsystem initialized <4>[1.663161] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found <6>[1.668407] megasas: 07.719.03.00-rc1 <6>[1.669160] i801_smbus :00:1f.4: SPD Write Disable is set <6>[1.669200] i801_smbus :00:1f.4: SMBus using PCI interrupt <6>[1.669238] pci :00:1f.1: [8086:a1a0] type 00 class 0x058000 <6>[1.669277] pci :00:1f.1: reg 0x10: [mem 0xfd00-0xfdff 64bit] <6>[1.673812] pci :00:1f.1: Adding to iommu group 70 <6>[1.674001] pci :00:1f.1: Removing from iommu group 70 <7>[1.676560] libata version 3.00 loaded. <7>[1.695181] megaraid_sas :17:00.0: BAR:0x1 BAR's base_addr(phys):0xab10 mapped virt_addr:0xd4ff0abc <6>[1.695187] megaraid_sas :17:00.0: FW now in Ready state <6>[1.695190] megaraid_sas :17:00.0: 63 bit DMA mask and 32 bit consistent mask <6>[1.695835] megaraid_sas :17:00.0: firmware supports msix : (96) <6>[1.696438] megaraid_sas :17:00.0: requested/available msix 11/11 poll_queue 0 <6>[1.696540] megaraid_sas :17:00.0: current msix/online cpus : (11/10) <6>[1.696541] megaraid_sas :17:00.0: RDPQ mode : (disabled) <6>[1.696544] megaraid_sas :17:00.0: Current firmware supports maximum commands: 928 LDIO threshold: 0 <6>[1.701165] megaraid_sas :17:00.0: Performance mode :Latency (latency index = 1) <6>[1.701167] megaraid_sas :17:00.0: FW supports sync cache : No <6>[1.701170] megaraid_sas :17:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x4009 <6>[1.706081] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver <6>[1.706083] ixgbe: Copyright (c) 1999-2016 Intel Corporation. <6>[1.707314] tg3 :04:00.0 eth0: Tigon3 [partno(BCM95720) rev 572] (PCI Express) MAC address d0:94:66:77:ea:61 <6>[1.707319] tg3 :04:00.0 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) <6>[1.707322] tg3 :04:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] <6>[1.707324] tg3 :04:00.0 eth0: dma_rwctrl[0001] dma_mask[64-bit] <6>[1.707994] i2c i2c-0: 4/16 memory slots populated (from DMI) <4>[1.707996] i2c i2c-0: Systems with more than 4 memory slots not supported yet, not instantiating SPD <6>[1.719799] xhci_hcd :00:14.0: xHCI Host Controller <6>[1.719806] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 <6>[1.720945] xhci_hcd :00:14.0: hcc params 0x200077c1 hci version 0x100 quirks
Bug#1053750: linux-image-6.1.0-13-amd64: "Hardware Error" during shutdown that is not a hardware problem
Package: src:linux
Version: 6.1.55-1
Severity: normal
Dear Maintainer,
each time this system is rebooted, during shutdown, the kernel outputs the
following error message.
The kernel thinks it encountered a "Hardware Error", but the error is most
probably not a hardware error, because I also see it on another identical machine (Dell
PowerEdge R540).
I have seen this error since this system has been upgraded to Debian 12 and
with all Debian 6.1.x kernels.
Previously the system ran Debian 11 with 5.10.x kernels (and previously Debian
10) and I never saw this error.
[...]
<30>[109240.369926] systemd-shutdown[1]: All filesystems, swaps, loop devices,
MD devices and DM devices detached.
<2>[109240.369935] watchdog: watchdog0: watchdog did not stop!
<30>[109240.417270] systemd-shutdown[1]: Syncing filesystems and block devices.
<30>[109240.418636] systemd-shutdown[1]: Rebooting.
<6>[109240.418705] kvm: exiting hardware virtualization
<6>[109240.437954] megaraid_sas :17:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
<6>[109240.513486] ACPI: PM: Preparing to enter system sleep state S5
<0>[109244.971342] {1}[Hardware Error]: Hardware error from APEI Generic
Hardware Error Source: 5
<0>[109244.971345] {1}[Hardware Error]: event severity: fatal
<0>[109244.971346] {1}[Hardware Error]: Error 0, type: fatal
<0>[109244.971348] {1}[Hardware Error]: section_type: PCIe error
<0>[109244.971349] {1}[Hardware Error]: port_type: 0, PCIe end point
<0>[109244.971350] {1}[Hardware Error]: version: 3.0
<0>[109244.971351] {1}[Hardware Error]: command: 0x0002, status: 0x0010
<0>[109244.971352] {1}[Hardware Error]: device_id: :01:00.1
<0>[109244.971354] {1}[Hardware Error]: slot: 6
<0>[109244.971354] {1}[Hardware Error]: secondary_bus: 0x00
<0>[109244.971355] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x1563
<0>[109244.971356] {1}[Hardware Error]: class_code: 02
<0>[109244.971357] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x00018000
<0>[109244.971358] {1}[Hardware Error]: aer_uncor_severity: 0x000ef010
<0>[109244.971359] {1}[Hardware Error]: TLP Header: 4001 010f
90028090
<0>[109244.971362] Kernel panic - not syncing: Fatal hardware error!
<4>[109244.971364] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-13-amd64 #1
Debian 6.1.55-1
<4>[109244.971367] Hardware name: Dell Inc. PowerEdge R540/0PRWNC, BIOS 2.19.1
06/12/2023
<4>[109244.971368] Call Trace:
<4>[109244.971370]
<4>[109244.971372] dump_stack_lvl+0x44/0x5c
<4>[109244.971379] panic+0x118/0x2ed
<4>[109244.971386] __ghes_panic.cold+0x21/0x21
<4>[109244.971391] ghes_notify_nmi+0x1db/0x370
<4>[109244.971398] nmi_handle+0x5a/0x120
<4>[109244.971403] ? mwait_idle_with_hints.constprop.0+0x48/0x90
<4>[109244.971409] default_do_nmi+0x69/0x170
<4>[109244.971411] exc_nmi+0x13c/0x170
<4>[109244.971414] end_repeat_nmi+0x16/0x67
<4>[109244.971419] RIP: 0010:mwait_idle_with_hints.constprop.0+0x48/0x90
<4>[109244.971423] Code: 48 89 d1 65 48 8b 04 25 c0 fb 01 00 0f 01 c8 48 8b 00 a8 08
75 14 66 90 0f 00 2d df 09 b1 00 b9 01 00 00 00 48 89 f8 0f 01 c9 <65> 48 8b 04 25 c0
fb 01 00 f0 80 60 02 df f0 83 44 24 fc 00 48 8b
<4>[109244.971425] RSP: 0018:92003e18 EFLAGS: 0046
<4>[109244.971427] RAX: 0020 RBX: c608bf234950 RCX:
0001
<4>[109244.971429] RDX: RSI: 9219ee00 RDI:
0020
<4>[109244.971431] RBP: 0003 R08: 0002 R09:
3a518aaa
<4>[109244.971432] R10: 0014 R11: 431a R12:
9219ee00
<4>[109244.971433] R13: 9219ee00 R14: 0003 R15:
<4>[109244.971438] ? mwait_idle_with_hints.constprop.0+0x48/0x90
<4>[109244.971442] ? mwait_idle_with_hints.constprop.0+0x48/0x90
<4>[109244.971445]
<4>[109244.971445]
<4>[109244.971446] intel_idle_ibrs+0x7e/0x90
<4>[109244.971450] cpuidle_enter_state+0x89/0x420
<4>[109244.971457] cpuidle_enter+0x29/0x40
<4>[109244.971460] do_idle+0x20c/0x2b0
<4>[109244.971466] cpu_startup_entry+0x19/0x20
<4>[109244.971469] rest_init+0xcb/0xd0
<4>[109244.971472] arch_call_rest_init+0xa/0x14
<4>[109244.971478] start_kernel+0x6fe/0x727
<4>[109244.971482] secondary_startup_64_no_verify+0xe5/0xeb
<4>[109244.971490]
<0>[109244.971504] Kernel Offset: 0xf60 from 0x8100 (relocation
range: 0x8000-0xbfff)
-- Package-specific info:
** Version:
Linux version 6.1.0-13-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP
PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64
root=UUID=d4026c7c-61cc-435f-81c5-76194e22454e ro quiet net.ifnames=0
** Not tainted
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: Dell Inc.
product_name:
Bug#1034718: linux-image-6.1.0-7-amd64: error during shutdown
Package: src:linux
Version: 6.1.20-2
Severity: normal
Dear Maintainer,
each time I shutdown this system (a Debian 11 system with the bookworm kernel),
the Linux kernel outputs the following error message.
This error could have been unnoticed, but:
- it triggers an alarm in the iDRAC controller
- it is logged by systemd in /var/lib/systemd/pstore/
This error does not occur with Debian kernels from the 5.10 branch in bullseye.
Linux writes that this is a "harware error", but I see the exact same error on
2 different physical servers. Therefore it is very unlikely that the hardware is
deffective.
<0>[ 115.232774] {1}[Hardware Error]: Hardware error from APEI Generic
Hardware Error Source: 5
<0>[ 115.232776] {1}[Hardware Error]: event severity: fatal
<0>[ 115.232778] {1}[Hardware Error]: Error 0, type: fatal
<0>[ 115.232779] {1}[Hardware Error]: section_type: PCIe error
<0>[ 115.232780] {1}[Hardware Error]: port_type: 0, PCIe end point
<0>[ 115.232781] {1}[Hardware Error]: version: 3.0
<0>[ 115.232782] {1}[Hardware Error]: command: 0x0002, status: 0x0010
<0>[ 115.232783] {1}[Hardware Error]: device_id: :01:00.1
<0>[ 115.232785] {1}[Hardware Error]: slot: 6
<0>[ 115.232785] {1}[Hardware Error]: secondary_bus: 0x00
<0>[ 115.232786] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x1563
<0>[ 115.232787] {1}[Hardware Error]: class_code: 02
<0>[ 115.232788] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x00018000
<0>[ 115.232789] {1}[Hardware Error]: aer_uncor_severity: 0x000ef010
<0>[ 115.232790] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
<0>[ 115.232793] Kernel panic - not syncing: Fatal hardware error!
<4>[ 115.232795] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.1.0-7-amd64 #1
Debian 6.1.20-2
<4>[ 115.232798] Hardware name: Dell Inc. PowerEdge R540/0PRWNC, BIOS 2.17.1
11/17/2022
<4>[ 115.232799] Call Trace:
<4>[ 115.232801]
<4>[ 115.232804] dump_stack_lvl+0x44/0x5c
<4>[ 115.232812] panic+0x118/0x2ed
<4>[ 115.232820] __ghes_panic.cold+0x21/0x21
<4>[ 115.232826] ghes_notify_nmi+0x1db/0x370
<4>[ 115.232832] nmi_handle+0x5a/0x120
<4>[ 115.232836] ? mwait_idle_with_hints.constprop.0+0x48/0x90
<4>[ 115.232841] default_do_nmi+0x69/0x170
<4>[ 115.232844] exc_nmi+0x13c/0x170
<4>[ 115.232847] end_repeat_nmi+0x16/0x67
<4>[ 115.232850] RIP: 0010:mwait_idle_with_hints.constprop.0+0x48/0x90
<4>[ 115.232853] Code: 48 89 d1 65 48 8b 04 25 c0 fb 01 00 0f 01 c8 48 8b 00 a8 08
75 14 66 90 0f 00 2d 2f 50 b1 00 b9 01 00 00 00 48 89 f8 0f 01 c9 <65> 48 8b 04 25 c0
fb 01 00 f0 80 60 02 df f0 83 44 24 fc 00 48 8b
<4>[ 115.232855] RSP: 0018:ae803e18 EFLAGS: 0046
<4>[ 115.232857] RAX: 0020 RBX: bf363f234950 RCX:
0001
<4>[ 115.232859] RDX: RSI: ae99ea20 RDI:
0020
<4>[ 115.232860] RBP: 0003 R08: 0002 R09:
3a518aaa
<4>[ 115.232862] R10: 0018 R11: 8bf6 R12:
ae99ea20
<4>[ 115.232863] R13: ae99ea20 R14: 0003 R15:
<4>[ 115.232867] ? mwait_idle_with_hints.constprop.0+0x48/0x90
<4>[ 115.232871] ? mwait_idle_with_hints.constprop.0+0x48/0x90
<4>[ 115.232873]
<4>[ 115.232874]
<4>[ 115.232875] intel_idle_ibrs+0x7e/0x90
<4>[ 115.232879] cpuidle_enter_state+0x89/0x420
<4>[ 115.232883] cpuidle_enter+0x29/0x40
<4>[ 115.232885] do_idle+0x20c/0x2b0
<4>[ 115.232890] cpu_startup_entry+0x19/0x20
<4>[ 115.232893] rest_init+0xcb/0xd0
<4>[ 115.232897] arch_call_rest_init+0xa/0x14
<4>[ 115.232902] start_kernel+0x6fe/0x727
<4>[ 115.232905] secondary_startup_64_no_verify+0xe5/0xeb
<4>[ 115.232912]
<0>[ 115.232970] Kernel Offset: 0x2bc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
-- Package-specific info:
** Version:
Linux version 6.1.0-7-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP
PREEMPT_DYNAMIC Debian 6.1.20-2 (2023-04-08)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-7-amd64
root=UUID=d4026c7c-61cc-435f-81c5-76194e22454e ro quiet
** Not tainted
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: Dell Inc.
product_name: PowerEdge R540
product_version:
chassis_vendor: Dell Inc.
chassis_version:
bios_vendor: Dell Inc.
bios_version: 2.17.1
board_vendor: Dell Inc.
board_name: 0PRWNC
board_version: A07
** Loaded modules:
intel_rapl_msr
intel_rapl_common
intel_uncore_frequency
intel_uncore_frequency_common
isst_if_common
skx_edac
nfit
libnvdimm
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
nls_ascii
nls_cp437
vfat
fat
kvm
irqbypass
ghash_clmulni_intel
sha512_ssse3
sha512_generic
aesni_intel
ipmi_ssif
mgag200
crypto_simd
cryptd
rapl
intel_cstate
mei_me
sg
drm_shmem_helper
iTCO_wdt
dell_smbios
mei
Bug#1029138: linux-image-6.1.0-1-amd64: refcount_t: underflow; use-after-free in nfsd on a NFS server
On 1/18/23 16:46, Salvatore Bonaccorso wrote: Would it be possible to test 6.1.7, which contains related nfs changes with the nfsd filecache? Yes, of course, as soon as it is available as a Debian package... Regards, -- Laurent.
Bug#1028604: gpxviewer: homepage seems to be wrong
Package: gpxviewer Version: 1.1.0-5 Severity: normal Dear Maintainer, according to the package metadata the homepage of the project is as follows: $ dpkg -s gpxviewer [...] Version: 1.1.0-5 [...] Homepage: https://github.com/andrewgee/gpxviewer However, on this page, I only see tags up to version 0.5.3, whereas the package version is more recent. Cheers, -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gpxviewer depends on: ii gir1.2-osmgpsmap-1.0 1.2.0-2 ii librsvg2-common 2.54.5+dfsg-1 ii python3 3.11.1-1 ii python3-cairo 1.20.1-5 ii python3-gi3.42.2-3 ii python3-gi-cairo 3.42.2-3 ii python3-gpxpy 1.5.0-1 ii python3-matplotlib3.6.2-4 gpxviewer recommends no packages. gpxviewer suggests no packages. -- no debconf information -- Laurent.
Bug#1008681: linux-image-5.16.0-5-amd64: WARNING: CPU: 1 PID: 1061 at fs/nfsd/nfs4state.c:5891 nfs4_preprocess_stateid_op+0x600/0x690 [nfsd]
On 12/5/22 18:26, Diederik de Haas wrote: Do you know what the faulty and fixed 5.10 version were/are? The problem was not really in the kernel, but in rpc.svcgssd that has trouble with large Kerberos credentials. The only problem with 5.10 kernels is that they only display warnings about hung rpc.svcgssd processes, instead of this warning message displayed by more recent kernels: ./net/sunrpc/auth_gss/svcauth_gss.c: "RPCSEC/GSS credential too large - please use gssproxy\n"); Cheers, -- Laurent.
Bug#1008681: linux-image-5.16.0-5-amd64: WARNING: CPU: 1 PID: 1061 at fs/nfsd/nfs4state.c:5891 nfs4_preprocess_stateid_op+0x600/0x690 [nfsd]
On 12/5/22 17:34, Diederik de Haas wrote: btw: What's the reason for not using a 5.10 kernel on a Stable system? (Not that I mind, just curious) Thanks for your interest :>. I had a NFS problem with the 5.10 kernel and tested a more recent kernel to see if this problem had been fixed. (For the sake of completeness, the problem was running rpc.svcgssd instead of gssproxy). What's the current status wrt this issue? Since then, I went back to using a 5.10 kernel, where this issue does not show up. I will test again when Debian chooses the kernel branch that will be used for Debian 12... Thanks again, -- Laurent.
Bug#995877: linux-image-5.14.0-2-amd64: "pagealloc: memory corruption" during SCSI initialization
Package: src:linux Version: 5.14.9-2 Severity: important Dear Maintainer, I boot this system with the page_poison=1 kernel option and during boot, and more precisely during SCSI initialization (for external USB disks), I get this scary error dump: [3.350394] pagealloc: memory corruption [3.350420] (ptrval): 00 00 00 04 00 80 83 b0 [3.350447] CPU: 0 PID: 161 Comm: kworker/u4:5 Not tainted 5.14.0-2-amd64 #1 Debian 5.14.9-2 [3.350450] Hardware name: Dell Inc. OptiPlex 7010/0KRC95, BIOS A29 06/28/2018 [3.350451] Workqueue: events_unbound async_run_entry_fn [3.350457] Call Trace: [3.350461] dump_stack_lvl+0x46/0x5a [3.350465] __kernel_unpoison_pages.cold+0x49/0x85 [3.350470] get_page_from_freelist+0xc61/0xe50 [3.350474] ? chacha_block_generic+0x6f/0xb0 [3.350476] __alloc_pages+0x178/0x310 [3.350479] allocate_slab+0x87/0x490 [3.350482] ___slab_alloc+0x3eb/0x570 [3.350485] ? scsi_mq_init_request+0x2e/0xe0 [scsi_mod] [3.350497] ? scsi_mq_init_request+0x2e/0xe0 [scsi_mod] [3.350505] __slab_alloc+0x1c/0x40 [3.350507] kmem_cache_alloc_node+0x39c/0x3e0 [3.350510] scsi_mq_init_request+0x2e/0xe0 [scsi_mod] [3.350518] blk_mq_alloc_rqs+0x20e/0x2a0 [3.350522] blk_mq_init_sched+0xa9/0x350 [3.350524] elevator_init_mq+0x125/0x160 [3.350527] __device_add_disk+0x19e/0x2f0 [3.350530] sd_probe+0x2f0/0x4a0 [sd_mod] [3.350533] really_probe+0x1f5/0x3f0 [3.350537] __driver_probe_device+0xfe/0x180 [3.350539] driver_probe_device+0x1e/0x90 [3.350541] __device_attach_driver+0x72/0xe0 [3.350543] ? driver_allows_async_probing+0x50/0x50 [3.350545] ? driver_allows_async_probing+0x50/0x50 [3.350547] bus_for_each_drv+0x7e/0xc0 [3.350549] __device_attach_async_helper+0x9f/0xe0 [3.350551] async_run_entry_fn+0x30/0x130 [3.350554] process_one_work+0x1ec/0x390 [3.350556] worker_thread+0x53/0x3e0 [3.350558] ? process_one_work+0x390/0x390 [3.350559] kthread+0x127/0x150 [3.350562] ? set_kthread_struct+0x40/0x40 [3.350565] ret_from_fork+0x22/0x30 [3.350572] page:(ptrval) refcount:1 mapcount:0 mapping: index:0x0 pfn:0x1165a0 [3.350574] flags: 0x17c000(node=0|zone=2|lastcpupid=0x1f) [3.350577] raw: 0017c000 dead0100 dead0122 [3.350579] raw: 0001 [3.350579] page dumped because: pagealloc: corrupted page details Note that this error does not always occur. Sometimes the machine boots with no error message. I also attached a full dmesg output. Thanks ! -- Package-specific info: ** Version: Linux version 5.14.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.3.0-11) 10.3.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 5.14.9-2 (2021-10-03) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2-amd64 root=UUID=c27a1c2e-4689-49ec-ab55-bba0dae046dc ro vsyscall=none security=apparmor page_poison=1 quiet ** Tainted: S (4) * SMP kernel oops on an officially SMP incapable processor ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Dell Inc. product_name: OptiPlex 7010 product_version: 01 chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A29 board_vendor: Dell Inc. board_name: 0KRC95 board_version: A02 ** Loaded modules: crypto_simd xts cts ecb tun mei_hdcp mei_wdt cpufreq_conservative cpufreq_userspace cpufreq_ondemand cpufreq_powersave intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm ledtrig_audio rfkill snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec irqbypass rapl snd_hda_core intel_cstate snd_hwdep intel_uncore dell_wmi snd_pcm_oss sparse_keymap serio_raw pcspkr snd_mixer_oss dell_smbios dcdbas dell_wmi_descriptor iTCO_wdt snd_pcm intel_pmc_bxt at24 wmi_bmof sg iTCO_vendor_support snd_timer watchdog snd mei_me soundcore mei evdev msr drbd lru_cache i2c_dev binfmt_misc squashfs loop dm_crypt fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 hid_generic usbhid hid btrfs blake2b_generic zstd_compress uas usb_storage raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod dm_mirror dm_region_hash dm_log dm_mod sd_mod t10_pi crc_t10dif crct10dif_generic i915 crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ahci libahci libata i2c_algo_bit ttm drm_kms_helper cec ghash_clmulni_intel xhci_pci rc_core cryptd xhci_hcd psmouse i2c_i801 i2c_smbus scsi_mod lpc_ich ehci_pci drm ehci_hcd e1000e usbcore usb_common ptp pps_core wmi video button ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200
Bug#995628: qemu-system-data: desktop file is incomplete, remove it?
Package: qemu-system-data Version: 1:6.1+dfsg-6 Severity: normal Dear Maintainer, when I start a KDE program I see the following error messages: kf.service.services: The desktop entry file "/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line kf.service.sycoca: Invalid Service : "/usr/share/applications/qemu.desktop" The qemu.desktop file lacks a shell command, indeed. In fact I do not see what command could be added there. Qemu needs at least some options to do something useful. The best solution would perhaps be to remove the qemu.desktop completely. -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-1-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information -- Laurent.
Bug#995109: linux-image-5.14.0-1-amd64: kernel WARNING caused by samba nmbd (and related to Tomoyo)
On 27/09/2021 21.40, Salvatore Bonaccorso wrote: I believe this is fixed by https://salsa.debian.org/kernel-team/linux/-/commit/b7f5082c34ea43622ebd9cd42f5fdd7b5ed49761 pending for the next upload. Thanks a lot for the quick fix! -- Laurent.
Bug#995109: linux-image-5.14.0-1-amd64: kernel WARNING caused by samba nmbd (and related to Tomoyo)
Hi, since the backtrace contains functions from Tomoyo, I tried to disable Tomoyo with ccsecurity=off on the kernel command line but it does not help. Any other suggestion ? Thanks, -- Laurent.
Bug#995109: linux-image-5.14.0-1-amd64: kernel WARNING caused by samba nmbd (and related to Tomoyo)
Package: src:linux Version: 5.14.6-2 Severity: important Dear Maintainer, on a system that is used as a Samba server, the kernel logs are spammed by WARNINGs such as this one: Sep 26 07:42:40 hostname kernel: [ cut here ] Sep 26 07:42:40 hostname kernel: Buffer overflow detected (8 < 192)! Sep 26 07:42:40 hostname kernel: WARNING: CPU: 1 PID: 561 at include/linux/thread_info.h:200 ethtool_rxnfc_copy_to_user+0x2b/0xb0 Sep 26 07:42:40 hostname kernel: Modules linked in: ipmi_ssif intel_rapl_msr intel_rapl_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp quota_v2 quota_tree coretemp nls_ascii nls_cp437 vfat fat ghash_clmulni_intel m> Sep 26 07:42:40 hostname kernel: CPU: 1 PID: 561 Comm: nmbd Not tainted 5.14.0-1-amd64 #1 Debian 5.14.6-2 Sep 26 07:42:40 hostname kernel: Hardware name: Dell Inc. PowerEdge R540/0NJK2F, BIOS 2.12.2 07/09/2021 Sep 26 07:42:40 hostname kernel: RIP: 0010:ethtool_rxnfc_copy_to_user+0x2b/0xb0 Sep 26 07:42:40 hostname kernel: Code: 1f 44 00 00 41 55 65 48 8b 04 25 c0 7b 01 00 41 54 55 53 f6 40 10 02 75 23 be 08 00 00 00 48 c7 c7 28 16 30 a7 e8 64 4c 14 00 <0f> 0b 41 bc f2 ff ff ff 5b 44 89 e0 5d 41 5c 41 5d c3 48 89 fb 49 Sep 26 07:42:40 hostname kernel: RSP: 0018:ab4680cefbf8 EFLAGS: 00010282 Sep 26 07:42:40 hostname kernel: RAX: RBX: c06204e0 RCX: 94bfe009 Sep 26 07:42:40 hostname kernel: RDX: ffd8 RSI: 0027 RDI: 94bfe0098880 Sep 26 07:42:40 hostname kernel: RBP: 94b8d11c R08: R09: ab4680cefa20 Sep 26 07:42:40 hostname kernel: R10: ab4680cefa18 R11: a78d3588 R12: Sep 26 07:42:40 hostname kernel: R13: 7fff9b14aa20 R14: R15: ab4680cefc28 Sep 26 07:42:40 hostname kernel: FS: 7f59e1dcfa40() GS:94bfe008() knlGS: Sep 26 07:42:40 hostname kernel: CS: 0010 DS: ES: CR0: 80050033 Sep 26 07:42:40 hostname kernel: CR2: 557f575974d8 CR3: 000109a38002 CR4: 007706e0 Sep 26 07:42:40 hostname kernel: DR0: DR1: DR2: Sep 26 07:42:40 hostname kernel: DR3: DR6: fffe0ff0 DR7: 0400 Sep 26 07:42:40 hostname kernel: PKRU: 5554 Sep 26 07:42:40 hostname kernel: Call Trace: Sep 26 07:42:40 hostname kernel: ethtool_get_rxnfc+0xcb/0x1b0 Sep 26 07:42:40 hostname kernel: dev_ethtool+0xb4b/0x28f0 Sep 26 07:42:40 hostname kernel: ? sk_prot_alloc+0x30/0x120 Sep 26 07:42:40 hostname kernel: ? tomoyo_init_request_info+0x8f/0xb0 Sep 26 07:42:40 hostname kernel: ? tomoyo_path_number_perm+0x66/0x1d0 Sep 26 07:42:40 hostname kernel: dev_ioctl+0x156/0x480 Sep 26 07:42:40 hostname kernel: sock_do_ioctl+0x9b/0x130 Sep 26 07:42:40 hostname kernel: sock_ioctl+0x23a/0x320 Sep 26 07:42:40 hostname kernel: __x64_sys_ioctl+0x83/0xb0 Sep 26 07:42:40 hostname kernel: do_syscall_64+0x3b/0xc0 Sep 26 07:42:40 hostname kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Sep 26 07:42:40 hostname kernel: RIP: 0033:0x7f59e573bcc7 Sep 26 07:42:40 hostname kernel: Code: 00 00 00 48 8b 05 c9 91 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 99 91 0c 00 f7 d8 64 89 01 48 Sep 26 07:42:40 hostname kernel: RSP: 002b:7fff9b14a9b8 EFLAGS: 0246 ORIG_RAX: 0010 Sep 26 07:42:40 hostname kernel: RAX: ffda RBX: 557f575950f0 RCX: 7f59e573bcc7 Sep 26 07:42:40 hostname kernel: RDX: 7fff9b14a9f0 RSI: 8946 RDI: 000f Sep 26 07:42:40 hostname kernel: RBP: 000f R08: R09: 003166307331706e Sep 26 07:42:40 hostname kernel: R10: 000d R11: 0246 R12: 557f575952a0 Sep 26 07:42:40 hostname kernel: R13: 7fff9b14a9f0 R14: 557f575970d0 R15: 557f57597174 Sep 26 07:42:40 hostname kernel: ---[ end trace 387ad7d8b4db28d7 ]--- Sep 26 07:42:40 hostname kernel: [ cut here ] -- Package-specific info: ** Version: Linux version 5.14.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.3.0-10) 10.3.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 5.14.6-2 (2021-09-19) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1-amd64 root=UUID=3d817555-5d7c-4e8e-8a65-c80a673dc806 ro ccsecurity=off quiet ** Tainted: W (512) * kernel issued warning ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Dell Inc. product_name: PowerEdge R540 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: 2.12.2 board_vendor: Dell Inc. board_name: 0NJK2F board_version: A02 ** Loaded modules: dm_mod cpuid cts rpcsec_gss_krb5 ipmi_ssif intel_rapl_msr intel_rapl_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp quota_v2
Bug#985463: debian-installer: kernel complains about /boot partition in LVM install (ext2 filesystem being mounted at /boot supports timestamps until 2038)
On 3/18/21 9:08 PM, Charles Curley wrote:
How much memory does the computer have?
It is a VM with 1GB of RAM.
On my FIT-PCs, using the same
installer (but with firmware), I see that debian installer (d-i) goes
to ext2 rather than ext4. They have 228Mi of physical memory. On my IBM
R51, with 1.2Gi of physical memory, I do not see this; I get ext4.
It is strange that the choice of FS depends on the amount of RAM. Did you use
LVM on both systems?
[...] and I don't know how to check the size of my inodes.
You can see it with tune2fs, for instance:
# tune2fs -l /dev/sda1
[...]
Inode size: 256
But my work-around is to upgrade from ext2 to ext4, like so:
tune2fs -O extent,huge_file,flex_bg,dir_nlink,extra_isize,has_journal\
${dev}
I think that changing inode sizes can only be done by recreating the FS.
N.b.: Apparently on an upgrade like this, we can't do metadata_csum or
64bit.
32->64 bits can be done, but that's another story...
I don't know if it will solve your problem, but you are welcome to try
Thanks, but what I usually do is to get rid of the /boot partition. However
that leaves a small unused disk space at the beginning of the disk.
--
Laurent.
Bug#985463: debian-installer: kernel complains about /boot partition in LVM install (ext2 filesystem being mounted at /boot supports timestamps until 2038)
On 3/18/21 7:51 PM, Ben Hutchings wrote: I think that the installer uses ext2 for /boot because some boot loaders only support(ed) ext2 and not its successor filesystem formats. But I think that's an historical problem for most release architectures. If that is true, then an even simpler solution would be to get rid of the separate /boot partition and have the /boot directory in the root filesystem. Thanks for looking at this bug ! -- Laurent.
Bug#985463: debian-installer: kernel complains about /boot partition in LVM install (ext2 filesystem being mounted at /boot supports timestamps until 2038)
Package: debian-installer Severity: normal Dear Maintainers, I did a test installation using debian-testing-amd64-netinst.iso from 2021-03-15 (Debian bullseye/11), chose the LVM option, and noticed that once the system is installed and boots, the kernel complains with this message: ext2 filesystem being mounted at /boot supports timestamps until 2038 (0x7fff) This is not fatal, but is ugly and most people would prefer a system without this message. The problem comes from the fact that the boot partition is created as ext2 with 128 bytes inodes. One fix would be to create the /boot filesystem as ext4 with 256 bytes inodes. The same problem exists in the Debian buster installer and will show up when buster systems are upgraded to a 5.10 kernel. Thanks for your work! -- Laurent.
Bug#983441: libxapp1: generates an obsolete conffile
Package: libxapp1
Version: 2.0.6-2
Severity: normal
Dear Maintainer,
here is the problem:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
[...]
/etc/xdg/autostart/xapp-sn-watcher.desktop a9fa3be7aaf46761adcdb856c63c125f
obsolete
Simply installing libxapp1 on a system is sufficient to create this problem (no
upgrade scenario is necessary).
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-3-rt-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE n>
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libxapp1 depends on:
ii libc62.31-9
ii libcairo-gobject21.16.0-5
ii libcairo21.16.0-5
ii libdbusmenu-gtk3-4 18.10.20180917~bzr492+repack1-2
ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii libglib2.0-0 2.67.4-1
ii libgnomekbd8 3.26.1-1
ii libgtk-3-0 3.24.25-1
ii libx11-6 2:1.7.0-2
ii xapps-common 2.0.6-2
libxapp1 recommends no packages.
libxapp1 suggests no packages.
-- no debconf information
--
Laurent.
Bug#946262: dochelp: Fatal error: out of memory
On 1/23/21 9:07 PM, Mehdi Dogguy wrote: Thanks for the bugreport and sorry for not replying earlier! No problem! I wasn't able to reproduce this bug. Thanks for trying! FWIW, I've just uploaded dochelp 0.1.8 with a couple of bugfixes (none is related to memory management though). Can you maybe test it and report back if you still have the issue? I cannot reproduce the bug any longer. Difficult to say if it comes from dochelp's update or other changes on the system. Anyway, I am going to close this bug... Thanks again, -- Laurent.
Bug#979880: kodi: FTBFS because of mount_getexports_timeout and struct hdr_output_metadata
On 1/12/21 1:02 PM, Vasyl Gello wrote: This is probably a regression due to ABI change in libnfs. Let me check if upstream has a fix for it. Thanks a lot for looking at this bug! Do you use NFS shares with Kodi in your HTPC setup? Not at all. I am just trying to rebuild kodi before doing a backport for older systems... Thanks again, -- Laurent.
Bug#979880: kodi: FTBFS because of mount_getexports_timeout and struct hdr_output_metadata
Package: kodi
Version: 2:19.0~beta2+dfsg1-5
Severity: important
Dear Maintainer,
in fact there are 2 compilation errors. Note that my system has dev packages
from experimental, but libnfs-dev and libdrm-dev are from sid:
Package: libnfs-dev
Version: 4.0.0-1
Package: libdrm-dev
Version: 2.4.103-2
Here are the errors:
$ apt -b source kodi
[...]
Performing C++ SOURCE FILE Test NFS_MOUNT_GETEXPORTS_TIMEOUT failed with the
following output:
Change Dir:
/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/gmake cmTC_74802/fast && gmake[2]: Entering
directory
'/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/gmake -f CMakeFiles/cmTC_74802.dir/build.make
CMakeFiles/cmTC_74802.dir/build
gmake[3]: Entering directory
'/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_74802.dir/src.cxx.o
/usr/bin/c++ -g -ffile-prefix-map=/home/bonnaudl/kodi-19.0~beta2+dfsg1=.
-fstack-protector-strong -Wformat -Werror=format-security -O3 -Wdate-time
-D_FORTIFY_SOURCE=2 -D_XBMC -gsplit-dwarf -Wall -DNFS_MOUNT_GETEXPORTS_TIMEOUT -o
CMakeFiles/cmTC_74802.dir/src.cxx.o -c
"/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx"
/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:
In function ‘int main()’:
/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:6:8:
error: ‘mount_getexports_timeout’ was not declared in this scope; did you mean
‘mount_getexports_async’?
6 |mount_getexports_timeout(NULL, 0);
|^~~~
|mount_getexports_async
gmake[3]: *** [CMakeFiles/cmTC_74802.dir/build.make:85:
CMakeFiles/cmTC_74802.dir/src.cxx.o] Error 1
gmake[3]: Leaving directory
'/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
gmake[2]: *** [Makefile:140: cmTC_74802/fast] Error 2
gmake[2]: Leaving directory
'/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Source file was:
#include
int main()
{
mount_getexports_timeout(NULL, 0);
}
Performing C SOURCE FILE Test LIBDRM_HAS_HDR_OUTPUT_METADATA failed with the
following output:
Change Dir:
/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/gmake cmTC_b3181/fast && gmake[2]: Entering
directory
'/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/gmake -f CMakeFiles/cmTC_b3181.dir/build.make
CMakeFiles/cmTC_b3181.dir/build
gmake[3]: Entering directory
'/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_b3181.dir/src.c.o
/usr/bin/cc -I/usr/include/libdrm -g
-ffile-prefix-map=/home/bonnaudl/kodi-19.0~beta2+dfsg1=. -fstack-protector-strong
-Wformat -Werror=format-security -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -D_XBMC
-gsplit-dwarf -Wall -DLIBDRM_HAS_HDR_OUTPUT_METADATA -o CMakeFiles/cmTC_b3181.dir/src.c.o
-c
"/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c"
/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:
In function ‘main’:
/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:5:55:
error: storage size of ‘test’ isn’t known
5 |struct hdr_output_metadata test;
| ^~~~
/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:5:55:
warning: unused variable ‘test’ [-Wunused-variable]
gmake[3]: *** [CMakeFiles/cmTC_b3181.dir/build.make:85:
CMakeFiles/cmTC_b3181.dir/src.c.o] Error 1
gmake[3]: Leaving directory
'/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
gmake[2]: *** [Makefile:140: cmTC_b3181/fast] Error 2
gmake[2]: Leaving directory
'/home/bonnaudl/kodi-19.0~beta2+dfsg1/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Source file was:
#include
int main()
{
struct hdr_output_metadata test;
return test.metadata_type;
}
dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DVERBOSE=1 -DUSE_LTO=2
-DCMAKE_BUILD_TYPE=RelWithDebInfo -DENABLE_AIRTUNES=ON -DENABLE_ALSA=ON -DENABLE_AVAHI=ON
-DENABLE_BLURAY=ON -DENABLE_CEC=ON -DENABLE_DBUS=ON -DENABLE_DVDCSS=OFF
Bug#979791: pipewire: started automatically with root SSH connections
Hi, here is more information with error messages from pipewire in the logs: # journalctl | grep pipewire Jan 11 11:58:45 hosname dbus-daemon[589]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.10' (uid=0 pid=4725 comm="/usr/bin/pipewire") Jan 11 11:58:45 hostname pipewire[4725]: [W][02106.193605][module-protocol-native.c:386 client_new()] server 0x562aaca38db0: no peersec: Protocol not available Jan 11 11:58:45 hostname pipewire[4725]: [W][02106.193693][module-protocol-native.c:386 client_new()] server 0x562aaca38db0: no peersec: Protocol not available Jan 11 11:58:45 hostname pipewire[4740]: [E][02106.499213][core.c:71 core_event_error()] core 0x55d1d020eee0: proxy 0x55d1d0256ad0 id:4: bound:-1 seq:4 res:-2 (No such file or directory) msg:"can't create device: No such file or directory" Jan 11 11:58:45 hostname pipewire[4740]: [E][02106.499242][media-session.c:1971 core_error()] error id:4 seq:4 res:-2 (No such file or directory): can't create device: No such file or directory Jan 11 11:58:54 hostname pipewire[4740]: [E][02115.045683][core.c:71 core_event_error()] core 0x55d1d01fbeb0: proxy 0x55d1d01fbeb0 id:0: bound:-1 seq:20 res:-32 (Broken pipe) msg:"connection error" Jan 11 11:58:54 hostname systemd[4694]: pipewire.service: Succeeded. Jan 11 11:58:54 hostname systemd[4694]: pipewire.socket: Succeeded. -- Laurent.
Bug#979791: pipewire: started automatically with root SSH connections
Package: pipewire Version: 0.3.15-1 Severity: normal Dear Maintainer, * What led up to the situation? I log in with SSH to the root account of a system where pipewire is installed. * What was the outcome of this action? A pipewire process is started automatically by systemd: # systemd-cgls Control group /: -.slice ├─user.slice │ └─user-0.slice [...] │ └─user@0.service … │ ├─app.slice │ │ ├─pipewire.service │ │ │ ├─9730 /usr/bin/pipewire │ │ │ └─9739 /usr/bin/pipewire-media-session * What outcome did you expect instead? No pipewire process since it does not seem to be useful for this use case and it might increase the attack surface of the system. I do not know if this problem is better fixed in pipewire or systemd... -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE n> Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pipewire depends on: ii init-system-helpers 1.60 ii libpipewire-0.3-modules 0.3.15-1 ii pipewire-bin 0.3.15-1 pipewire recommends no packages. pipewire suggests no packages. -- no debconf information -- Laurent.
Bug#978006: extra-cmake-modules: please change the section of the package
Package: extra-cmake-modules Version: 5.77.0-2 Severity: normal Dear Maintainer, when I run "deborphan" on my system, the extra-cmake-modules package is always listed as an "orphaned" library. This comes from the fact that this package is in the "libs" section and no other package depends on it: $ dpkg -s extra-cmake-modules [...] Section: libs How about changing the section from "libs" to "devel"? (the cmake package belongs to the devel section) -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-trunk-rt-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled extra-cmake-modules depends on no packages. extra-cmake-modules recommends no packages. Versions of packages extra-cmake-modules suggests: ii qt5-qmake5.15.2+dfsg-2 ii qtbase5-dev 5.15.2+dfsg-2 -- no debconf information -- Laurent.
Bug#976321: plocate: generates an obsolete conffile
Package: plocate
Version: 1.1.0-2
Severity: normal
Dear Maintainer,
here is a sequence of commands to demonstrate the problem:
- We start with a system with neither mlocate nor plocate and check that the
system is free of obsolete conffiles
# apt purge plocate mlocate
# dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
[nothing]
- Let's install mlocate and check our system
# apt install mlocate
# dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
[still nothing]
- Let's install plocate and check our system again
# apt install plocate
# dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
/etc/updatedb.conf 4e27fc332ba845aa2f5374afd3d0e90d obsolete
My expectation here would be to install both mlocate and plocate and have no
obsolete conffile on the system.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages plocate depends on:
ii libc6 2.31-5
ii libgcc-s1 10.2.0-19
ii libstdc++6 10.2.0-19
ii liburing1 0.7-2
ii libzstd11.4.5+dfsg-4
plocate recommends no packages.
plocate suggests no packages.
-- no debconf information
--
Laurent.
Bug#973829: closed by Debian FTP Masters (reply to Yves-Alexis Perez ) (Bug#973829: fixed in xfwm4 4.15.3-1)
On 11/5/20 10:39 PM, Debian Bug Tracking System wrote: #973829: xfwm4: tracker complains about xfce-workspaces-settings.desktop It has been closed by Debian FTP Masters (reply to Yves-Alexis Perez ). xfwm4 (4.15.3-1) experimental; urgency=medium . * New upstream version 4.15.3 - Fix empty keyword lines in /u/s/a/xfce4-workspaces-settings.desktop. Closes: #973829 Thank you for the fix! -- Laurent.
Bug#973829: xfwm4: tracker complains about xfce-workspaces-settings.desktop
Hi, I confirm that removing the blank line fixes the problem. Thanks, -- Laurent.
Bug#973829: xfwm4: tracker complains about xfce-workspaces-settings.desktop
Package: xfwm4 Version: 4.15.2-1 Severity: normal Dear Maintainer, here is an error message I see in the logs of my system: # journalctl | grep tracker | grep xfce Nov 05 19:10:20 hostname tracker-extract[2240]: Could not load desktop file 'file:///usr/share/applications/xfce-workspaces-settings.desktop': Key file contains line “ ” which is not a key-value pair, group, or comment It probably comes from the empty line between those 2 lines: Keywords[uk]=[...] Keywords[zh_CN]=[...] -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE n> Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Laurent.
Bug#924303: [Pkg-fonts-devel] Bug#924303: Bug#924303: fonts-noto-core: creates an obsolete config file
On 10/29/20 6:10 PM, Jonas Smedegaard wrote: Did you have fonts-noto-core 20181227-1 installed, or installed and then removed, or installed and then purged, when you ran that command? I don't remember exactly. However I tried to reproduce the problem on a recent system both with fonts-noto-core 20181227-1 and 20201027-3 and could not reproduce the problem. Therefore I consider it to be fixed. You can close this bug if you wish or I can do it if you prefer. Thanks for checking this issue! -- Laurent.
Bug#924303: [Pkg-fonts-devel] Bug#924303: fonts-noto-core: creates an obsolete config file
On 10/29/20 4:30 PM, Jonas Smedegaard wrote: Please elaborate: What_is_ the issue? It is my understanding that packages should not create obsolete conffiles. That's what I understood when reading this: https://raphaelhertzog.com/2010/10/07/the-right-way-to-remove-an-obsolete-conffile-in-a-debian-package/ Thanks, -- Laurent.
Bug#972831: tar: produces incorrect TAR+zstd archive when creating archive remotely
On 10/24/20 6:22 PM, Bdale Garbee wrote: I took a quick look and the problem is with the use of localhost: in the filename, Thanks for checking! In fact the problem also exists for remote hosts. it appears to be unrelated to the compression algorithm chosen. With xz I can create correct archives on remote hosts. -- Laurent.
Bug#972831: tar: produces incorrect TAR+zstd archive when creating archive remotely
Package: tar Version: 1.30+dfsg-7 Severity: important Dear Maintainer, here is a a short list of commands that demonstrate the problem (it needs a SSH server): $ mkdir foo $ tar --zstd -cvf localhost:foo.tar.zst foo $ zstd -t foo.tar.zst foo.tar.zst : 0 MB... zstd: foo.tar.zst: unsupported format $ tar --zstd -tvf foo.tar.zst zstd: /*stdin*\: unsupported format drwxr-xr-x bonnaudl/bonnaudl 0 2020-10-24 17:41 foo/ tar: Child returned status 1 tar: Error is not recoverable: exiting now The same thing without SSH (creating the archive on a local filesystem) works well. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tar depends on: ii libacl1 2.2.53-8 ii libc62.31-4 ii libselinux1 3.1-2+b1 tar recommends no packages. Versions of packages tar suggests: ii bzip21.0.8-4 ii ncompress4.2.4.6-3 pn tar-doc pn tar-scripts ii xz-utils 5.2.4-1+b1 -- no debconf information -- Laurent.
Bug#971655: apt: does not upgrade my system whereas apt-get does
Package: apt Version: 2.1.10 Severity: normal Dear Maintainer, * What led up to the situation? I am trying to perform an upgrade on a sid system. * What exactly did you do (or not do) that was effective (or ineffective)? # apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: golang-github-cpuguy83-go-md2man-v2-dev : Conflicts: golang-github-cpuguy83-go-md2man-dev but 1.0.10+ds-1 is to be installed golang-github-russross-blackfriday-v2-dev : Conflicts: golang-github-russross-blackfriday-dev but 1.5.2+git20200218.41c5fcc-1 is to be installed E: Broken packages * What was the outcome of this action? apt displays an error message and does not upgrade the system. * What outcome did you expect instead? apt-get has a much more useful behaviour: it keep the problematic package back and upgrades other packages that do not have a problem: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: dh-python golang-github-spf13-cobra-dev libpython2-stdlib python2 python2-minimal The following packages will be upgraded: beast2-mcmc beast2-mcmc-doc beast2-mcmc-examples chemtool fakeroot fonts-sil-gentiumplus-compact ganglia-modules-linux ganglia-monitor gcc-snapshot gir1.2-vips-8.0 gnucash gnucash-common libceres-dev libceres1 libfakeroot libfile-listing-perl libganglia1 libigraph-dev libigraph1 libnb-absolutelayout-java libsdl2-2.0-0 libsdl2-dev libsfcgal1 libsphere-dev libsphere0d libsrt-doc libsrt-openssl-dev libsrt1-gnutls libsrt1-openssl libvips-dev libvips-doc libvips-tools libvips42 mc mc-data minitube python-astroquery-doc python-biopython-doc python3-biopython python3-git python3-gnucash python3-pcbasic-doc python3-radicale python3-virtualenv radicale scummvm scummvm-data whois 48 upgraded, 0 newly installed, 0 to remove and 5 not upgraded. Need to get 0 B/842 MB of archives. After this operation, 2,647 MB of additional disk space will be used. Do you want to continue? [Y/n] *** End of the template - remove these template lines *** -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "true"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-.*-5\.8\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-.*-5\.9\.0-rc4-amd64$"; APT::NeverAutoRemove:: "^linux-.*-5\.9\.0-rc6-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-.*-5\.8\.0-2-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-.*-5\.9\.0-rc4-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-.*-5\.9\.0-rc6-amd64$"; APT::NeverAutoRemove:: "^gnumach-.*-5\.8\.0-2-amd64$"; APT::NeverAutoRemove:: "^gnumach-.*-5\.9\.0-rc4-amd64$"; APT::NeverAutoRemove:: "^gnumach-.*-5\.9\.0-rc6-amd64$"; APT::NeverAutoRemove:: "^.*-modules-5\.8\.0-2-amd64$"; APT::NeverAutoRemove:: "^.*-modules-5\.9\.0-rc4-amd64$"; APT::NeverAutoRemove:: "^.*-modules-5\.9\.0-rc6-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-5\.8\.0-2-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-5\.9\.0-rc4-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-5\.9\.0-rc6-amd64$"; APT::NeverAutoRemove:: "^postgresql.*-12"; APT::NeverAutoRemove:: "^postgresql.*-13"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "contrib/metapackages"; APT::Never-MarkAuto-Sections:: "non-free/metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Move-Autobit-Sections:: "contrib/oldlibs"; APT::Move-Autobit-Sections:: "non-free/oldlibs"; APT::Move-Autobit-Sections:: "restricted/oldlibs"; APT::Move-Autobit-Sections:: "universe/oldlibs"; APT::Move-Autobit-Sections:: "multiverse/oldlibs"; APT::Update ""; APT::Update::Pre-Invoke ""; APT::Update::Pre-Invoke:: "if [ -x /usr/bin/daptup ];
Bug#969409: sendfile: weekly cron job should use mktemp instead of tempfile
Package: sendfile Version: 2.1b.20080616-6 Severity: normal Dear Maintainer, each week I receive an e-mail with the following content: /etc/cron.weekly/sendfile: WARNING: tempfile is deprecated; consider using mktemp instead. Could you please update /etc/cron.weekly/sendfile to use mktemp instead of tempfile? -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-trunk-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sendfile depends on: ii libc6 2.31-3 ii libdpkg-perl 1.20.5 ii libreadline8 8.1~alpha1-1 ii openbsd-inetd [inet-superserver] 0.20160825-5 ii perl 5.30.3-4 ii update-inetd 4.50 -- Laurent.
Bug#969257: plasma-discover: org.kde.discover.notifier.desktop causes kernel logs pollution
Package: plasma-discover Version: 5.19.4-1 Severity: normal Dear Maintainer, I see the following error message in the kernel logs on my system: [ 1794.049495] systemd-xdg-autostart-generator[3071]: Configuration file /etc/xdg/autostart/org.kde.discover.notifier.desktop is marked executable. Please remove executable permission bits. Proceeding anyway. This file has executable permissions indeed: -rwxr-xr-x 1 root root 1110 Aug 30 08:55 /etc/xdg/autostart/org.kde.discover.notifier.desktop and is the only one in this directory. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-trunk-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Laurent.
Bug#969255: kmix: kmix_autostart.desktop causes kernel logs pollution
Package: kmix Version: 4:20.08.0-1 Severity: normal Dear Maintainer, I see the following error message in the kernel logs on my system: [ 1794.033071] systemd-xdg-autostart-generator[3071]: /etc/xdg/autostart/kmix_autostart.desktop:6: Unknown key name 'MimeType' in section 'Desktop Entry', ignoring. The kmix_autostart.desktop file contains this line: MimeType= which looks like it contains no useful information. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-trunk-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Laurent.
Bug#969080: orthanc: error in systemd unit file
Package: orthanc Version: 1.7.3+dfsg-1 Severity: normal Dear Maintainer, the systemd unit file shipped in orthanc: /lib/systemd/system/orthanc.service contains the following line: Documentation=man orthanc(8) https://book.orthanc-server.com/index.html which according to systemd is incorrect: # journalctl |grep orthanc [...] /lib/systemd/system/orthanc.service:3: Invalid URL, ignoring: man /lib/systemd/system/orthanc.service:3: Invalid URL, ignoring: orthanc(8) -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) -- Laurent.
Bug#965384: repsnapper: syntax error in desktop file; causes flwm postinst failure
Package: repsnapper Version: 2.5a5-2+b1 Severity: normal Dear Maintainer, here is the problem: Setting up flwm (1.02+git2015.10.03+7dbb30-7) ... Exec key for 'repsnapper' contains '%F', '%U' or '%D' at the wrong place dpkg: error processing package flwm (--configure): -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Laurent.
Bug#964368: deepin-icon-theme: gtk-update-icon-cache: The generated cache was invalid.
Package: deepin-icon-theme Version: 2020.06.30-1 Severity: normal Dear Maintainer, here is the problem: # apt install deepin-icon-theme [...] Unpacking deepin-icon-theme (2020.06.30-1) ... Setting up deepin-icon-theme (2020.06.30-1) ... gtk-update-icon-cache: The generated cache was invalid. WARNING: icon cache generation failed for /usr/share/icons/bloom-classic -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages deepin-icon-theme depends on: ii papirus-icon-theme 20200702-1 deepin-icon-theme recommends no packages. deepin-icon-theme suggests no packages. -- no debconf information -- Laurent.
Bug#963049: pki-base: syntax error in /usr/share/pki/scripts/config
Package: pki-base Version: 10.9.0~a2-2 Severity: serious Dear Maintainer, here is the problem: # source /usr/share/pki/scripts/config -bash: break: only meaningful in a `for', `while', or `until' loop -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pki-base depends on: ii python3-pki-base 10.9.0~a2-2 pki-base recommends no packages. pki-base suggests no packages. -- no debconf information -- Laurent.
Bug#963048: pki-base: postinst failure because of incorrect use of --silent option of pki-upgrade
Package: pki-base Version: 10.9.0~a2-2 Severity: serious Dear Maintainer, here is the problem: Setting up pki-base (10.9.0~a2-2) ... dpkg: error processing package pki-base (--configure): installed pki-base package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: pki-base The problem comes from the postinst script that tries to execute this command: # pki-upgrade --silent [...] ERROR: option --silent not recognized Usage: pki-upgrade [OPTIONS] --status Show upgrade status only. Do not perform upgrade. --revert Revert the last version. --validate Validate upgrade status. -X Show advanced options. -v, --verbose Run in verbose mode. --debugRun in debug mode. -h, --help Show this help message. Removing the --silent option fixes the problem. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pki-base depends on: ii python3-pki-base 10.9.0~a2-2 pki-base recommends no packages. pki-base suggests no packages. -- no debconf information -- Laurent.
Bug#962901: deepin-icon-theme: postinst failure in update-alternatives
Package: deepin-icon-theme Version: 2020.06.11-1 Severity: serious Dear Maintainer, here is the problem: Setting up deepin-icon-theme (2020.06.11-1) ... update-alternatives: error: alternative path /usr/share/icons/deepin/cursor.theme doesn't exist dpkg: error processing package deepin-icon-theme (--configure): installed deepin-icon-theme package post-installation script subprocess returned error exit status 2 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages deepin-icon-theme depends on: ii papirus-icon-theme 20200602-1 deepin-icon-theme recommends no packages. deepin-icon-theme suggests no packages. -- no debconf information -- Laurent.
Bug#962706: python3-uflash-doc: typo in dpendencies
Package: python3-uflash-doc Version: 1.2.4+dfsg-1 Severity: normal Dear Maintainer, here is the problem: $ dpkg -s python3-uflash-doc [...] Suggests: -browser ---^ there is an extra w here. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-uflash-doc depends on: ii libjs-sphinxdoc 3.1.0-1 python3-uflash-doc recommends no packages. Versions of packages python3-uflash-doc suggests: pn -browser -- no debconf information -- Laurent.
Bug#961540: python3-pip: FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/pip/_vendor/vendor.txt'
Package: python3-pip Version: 20.1.1-1 Severity: normal Dear Maintainer, running "pip3 debug" ends with a FileNotFoundError exception: $ pip3 debug WARNING: This command is only meant for debugging. Do not use this with automation for parsing and getting these details, since the output and options of this command may change without notice. pip version: pip 20.1.1 from /usr/lib/python3/dist-packages/pip (python 3.8) sys.version: 3.8.3 (default, May 14 2020, 11:03:12) [GCC 9.3.0] sys.executable: /usr/bin/python3 sys.getdefaultencoding: utf-8 sys.getfilesystemencoding: utf-8 locale.getpreferredencoding: UTF-8 sys.platform: linux sys.implementation: name: cpython 'cert' config value: Not specified REQUESTS_CA_BUNDLE: None CURL_CA_BUNDLE: None pip._vendor.certifi.where(): /etc/ssl/certs/ca-certificates.crt pip._vendor.DEBUNDLED: True vendored library versions: ERROR: Exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 188, in _main status = self.run(options, args) File "/usr/lib/python3/dist-packages/pip/_internal/commands/debug.py", line 233, in run show_vendor_versions() File "/usr/lib/python3/dist-packages/pip/_internal/commands/debug.py", line 132, in show_vendor_versions vendor_txt_versions = create_vendor_txt_map() File "/usr/lib/python3/dist-packages/pip/_internal/commands/debug.py", line 58, in create_vendor_txt_map with open(vendor_txt_path) as f: FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/pip/_vendor/vendor.txt' -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-pip depends on: ii ca-certificates 20190110 ii python-pip-whl 20.1.1-1 ii python3 3.8.2-3 ii python3-distutils 3.8.3-2 ii python3-setuptools 46.1.3-1 ii python3-wheel 0.34.2-1 Versions of packages python3-pip recommends: ii build-essential 12.8 ii python3-dev 3.8.2-3 python3-pip suggests no packages. -- no debconf information -- Laurent.
Bug#958396: python3-pip: ModuleNotFoundError: No module named 'pip._vendor.certifi'
Package: python3-pip
Version: 20.0.2-5
Severity: normal
Dear Maintainer,
* What led up to the situation?
I was trying all pip3 subcommands.
* What exactly did you do (or not do) that was effective (or
ineffective)?
$ pip3 debug
Traceback (most recent call last):
File "/usr/bin/pip3", line 11, in
load_entry_point('pip==20.0.2', 'console_scripts', 'pip3')()
File "/usr/lib/python3/dist-packages/pip/_internal/cli/main.py", line 73, in
main
command = create_command(cmd_name, isolated=("--isolated" in cmd_args))
File "/usr/lib/python3/dist-packages/pip/_internal/commands/__init__.py",
line 96, in create_command
module = importlib.import_module(module_path)
File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/pip/_internal/commands/debug.py", line
11, in
from pip._vendor.certifi import where
ModuleNotFoundError: No module named 'pip._vendor.certifi'
* What was the outcome of this action?
Python exception.
* What outcome did you expect instead?
No exception.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.5.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-pip depends on:
ii ca-certificates 20190110
ii python-pip-whl 20.0.2-5
ii python3 3.8.2-3
ii python3-distutils 3.8.2-2
ii python3-setuptools 45.2.0-1
ii python3-wheel 0.34.2-1
Versions of packages python3-pip recommends:
ii build-essential 12.8
ii python3-dev 3.8.2-3
python3-pip suggests no packages.
-- no debconf information
--
Laurent.
Bug#951054: powertop: FTBFS, problem with aclocal: error: too many loops
On 4/11/20 9:56 AM, Kan-Ru Chen wrote: > I can not reproduce the FTBFS issue on my local machine or pbuilder. There is > also no > failure reported on buildd network. Thanks for checking! > Perhaps there is something local to your environment causing the problem? Indeed. My system has many packages from experimental, especially libc6 2.31. -- Laurent.
Bug#878082: python3-pip: TypeError
Hi, thank you for this new package version and attempt to fix this bug! Unfortunately I am still getting an exception on my system: Package: python3-pip Version: 20.0.2-2 # pip3 list --outdated WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of pip. Please see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue. To avoid this problem you can invoke Python with '-m pip' instead of running pip directly. ERROR: Exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 186, in _main status = self.run(options, args) File "/usr/lib/python3/dist-packages/pip/_internal/commands/list.py", line 158, in run packages = self.get_outdated(packages, options) File "/usr/lib/python3/dist-packages/pip/_internal/commands/list.py", line 165, in get_outdated return [ File "/usr/lib/python3/dist-packages/pip/_internal/commands/list.py", line 167, in if dist.latest_version > dist.parsed_version TypeError: '>' not supported between instances of 'Version' and 'Version' or # python3 -m pip list --outdated ERROR: Exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 186, in _main status = self.run(options, args) File "/usr/lib/python3/dist-packages/pip/_internal/commands/list.py", line 158, in run packages = self.get_outdated(packages, options) File "/usr/lib/python3/dist-packages/pip/_internal/commands/list.py", line 165, in get_outdated return [ File "/usr/lib/python3/dist-packages/pip/_internal/commands/list.py", line 167, in if dist.latest_version > dist.parsed_version TypeError: '>' not supported between instances of 'Version' and 'Version' -- Laurent.
Bug#954242: qgis-providers: postinst failure: free(): invalid pointer
Package: qgis-providers Version: 3.10.3+dfsg-1+b1 Severity: serious Dear Maintainer, here is the problem: Setting up qgis-providers (3.10.3+dfsg-1+b1) ... free(): invalid pointer Aborted (core dumped) dpkg: error processing package qgis-providers (--configure): installed qgis-providers package post-installation script subprocess returned error exit status 134 Note that my system has glibc 2.31 from experimental and the following environment variables are set: MALLOC_PERTURB_=117 MALLOC_CHECK_=3 Running "valgrind /usr/lib/qgis/crssync" finds many memory errors, and the first one is: ==34194== Invalid free() / delete / delete[] / realloc() ==34194==at 0x4838EAB: operator delete(void*) (vg_replace_malloc.c:586) ==34194==by 0x76643D5: __cxa_finalize (cxa_finalize.c:83) ==34194==by 0xEC8FF62: ??? (in /usr/lib/x86_64-linux-gnu/libproj.so.15.3.1) ==34194==by 0x400FF92: _dl_fini (dl-fini.c:138) ==34194==by 0x7663DD6: __run_exit_handlers (exit.c:108) ==34194==by 0x7663F89: exit (exit.c:139) ==34194==by 0x764CCF1: (below main) (libc-start.c:342) ==34194== Address 0x1796f740 is 0 bytes inside a block of size 17 free'd ==34194==at 0x4838EAB: operator delete(void*) (vg_replace_malloc.c:586) ==34194==by 0x76643D5: __cxa_finalize (cxa_finalize.c:83) ==34194==by 0x7B12702: ??? (in /usr/lib/x86_64-linux-gnu/libproj.so.19.0.0) ==34194==by 0x400FF92: _dl_fini (dl-fini.c:138) ==34194==by 0x7663DD6: __run_exit_handlers (exit.c:108) ==34194==by 0x7663F89: exit (exit.c:139) ==34194==by 0x764CCF1: (below main) (libc-start.c:342) ==34194== Block was alloc'd at ==34194==at 0x4837DEF: operator new(unsigned long) (vg_replace_malloc.c:344) ==34194==by 0x7B0E91F: ??? (in /usr/lib/x86_64-linux-gnu/libproj.so.19.0.0) ==34194==by 0x7B11A2C: ??? (in /usr/lib/x86_64-linux-gnu/libproj.so.19.0.0) ==34194==by 0x400FC09: call_init.part.0 (dl-init.c:72) ==34194==by 0x400FD08: call_init (dl-init.c:30) ==34194==by 0x400FD08: _dl_init (dl-init.c:119) ==34194==by 0x40010C9: ??? (in /usr/lib/x86_64-linux-gnu/ld-2.31.so) -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qgis-providers depends on: ii dpkg 1.20.0 ii libc6 2.31-0experimental0 ii libexpat1 2.2.9-1 ii libgcc-s1 10-20200312-2 ii libgdal26 3.0.4+dfsg-1+b1 ii libhdf5-103 1.10.4+repack-11 ii libnetcdf15 1:4.7.3-1 ii libpq512.2-1+b1 ii libqca-qt5-2 2.2.1-2 ii libqca-qt5-2-plugins 2.2.1-2 ii libqgis-core3.10.33.10.3+dfsg-1+b1 ii libqgis-gui3.10.3 3.10.3+dfsg-1+b1 ii libqscintilla2-qt5-15 2.11.2+dfsg-6 ii libqt5core5a [qtbase-abi-5-12-5] 5.12.5+dfsg-9 ii libqt5gui55.12.5+dfsg-9 ii libqt5network55.12.5+dfsg-9 ii libqt5sql55.12.5+dfsg-9 ii libqt5sql5-sqlite 5.12.5+dfsg-9 ii libqt5webkit5 5.212.0~alpha4-1 ii libqt5widgets55.12.5+dfsg-9 ii libqt5xml55.12.5+dfsg-9 ii libspatialite75.0.0~beta0-1~exp4 ii libsqlite3-0 3.31.1-4 ii libstdc++610-20200312-2 ii libxml2 2.9.10+dfsg-4 ii qgis-providers-common 3.10.3+dfsg-1 qgis-providers recommends no packages. qgis-providers suggests no packages. -- no debconf information -- Laurent.
Bug#953551: apt: trouble with "singular" packages from experimental
Package: apt Version: 2.0.0 Severity: normal Dear Maintainer, * What led up to the situation? Those packages are installed on my system: ii libsingular4m1:amd64 1:4.1.1-p2+ds-4+b1 amd64Computer Algebra System for Polynomial Computations -- library package ii singular 1:4.1.2-p1+ds-2+b1 amd64Computer Algebra System for Polynomial Computations ii singular-data 1:4.1.1-p2+ds-4 all Computer Algebra System for Polynomial Computations -- shared data ii singular-doc1:4.1.2-p1+ds-2 all Computer Algebra System for Polynomial Computations -- user documentation ii singular-modules:amd64 1:4.1.1-p2+ds-4+b1 amd64Computer Algebra System for Polynomial Computations -- module package ii singular-ui 1:4.1.1-p2+ds-4+b1 amd64Computer Algebra System for Polynomial Computations -- console user interface and I am trying to update packages that are in experimental. * What was the outcome of this action? # apt -t experimental upgrade [...] The following packages have unmet dependencies: libsingular4m1 : Breaks: libsingular E: Broken packages * What outcome did you expect instead? At least a list of packages that cannot be updated because of dependencies problems (this is expected in experimental). apt-get does it nicely: # apt-get -t experimental upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: chef-zero default-jdk default-jdk-doc default-jdk-headless default-jre default-jre-headless [...] And apt should also upgrade packages that require additional dependencies (which apt-get does not upgrade). -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "true"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$"; APT::NeverAutoRemove:: "^linux-.*-5\.4\.0-3-amd64$"; APT::NeverAutoRemove:: "^linux-.*-5\.4\.0-3-rt-amd64$"; APT::NeverAutoRemove:: "^linux-.*-5\.4\.0-4-amd64$"; APT::NeverAutoRemove:: "^linux-.*-5\.4\.0-4-rt-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-.*-5\.4\.0-3-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-.*-5\.4\.0-3-rt-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-.*-5\.4\.0-4-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-.*-5\.4\.0-4-rt-amd64$"; APT::NeverAutoRemove:: "^gnumach-.*-5\.4\.0-3-amd64$"; APT::NeverAutoRemove:: "^gnumach-.*-5\.4\.0-3-rt-amd64$"; APT::NeverAutoRemove:: "^gnumach-.*-5\.4\.0-4-amd64$"; APT::NeverAutoRemove:: "^gnumach-.*-5\.4\.0-4-rt-amd64$"; APT::NeverAutoRemove:: "^.*-modules-5\.4\.0-3-amd64$"; APT::NeverAutoRemove:: "^.*-modules-5\.4\.0-3-rt-amd64$"; APT::NeverAutoRemove:: "^.*-modules-5\.4\.0-4-amd64$"; APT::NeverAutoRemove:: "^.*-modules-5\.4\.0-4-rt-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-5\.4\.0-3-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-5\.4\.0-3-rt-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-5\.4\.0-4-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-5\.4\.0-4-rt-amd64$"; APT::NeverAutoRemove:: "^postgresql-"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-.*"; APT::VersionedKernelPackages:: "kfreebsd-.*"; APT::VersionedKernelPackages:: "gnumach-.*"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "contrib/metapackages"; APT::Never-MarkAuto-Sections:: "non-free/metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Move-Autobit-Sections ""; APT::Move-Autobit-Sections:: "oldlibs"; APT::Move-Autobit-Sections:: "contrib/oldlibs"; APT::Move-Autobit-Sections:: "non-free/oldlibs"; APT::Move-Autobit-Sections::
Bug#951054: powertop: FTBFS, problem with aclocal: error: too many loops
Package: powertop
Version: 2.11-1
Severity: serious
Dear Maintainer,
here is the problem:
$ apt -b source powertop
Reading package lists... Done
NOTICE: 'powertop' packaging is maintained in the 'Git' version control system
at:
https://salsa.debian.org/debian/powertop.git
Please use:
git clone https://salsa.debian.org/debian/powertop.git
to retrieve the latest (possibly unreleased) updates to the package.
Skipping already downloaded file 'powertop_2.11-1.dsc'
Skipping already downloaded file 'powertop_2.11.orig.tar.gz'
Skipping already downloaded file 'powertop_2.11-1.debian.tar.xz'
Need to get 0 B of source archives.
Skipping unpack of already unpacked source in powertop-2.11
dpkg-buildpackage: info: source package powertop
dpkg-buildpackage: info: source version 2.11-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Kan-Ru Chen (陳侃如)
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
debian/rules clean
dh clean
dh_clean
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
Copying file m4/codeset.m4
Copying file m4/fcntl-o.m4
Copying file m4/glibc2.m4
Copying file m4/glibc21.m4
Copying file m4/intdiv0.m4
Copying file m4/intl.m4
Copying file m4/intldir.m4
Copying file m4/intmax.m4
Copying file m4/inttypes-pri.m4
Copying file m4/inttypes_h.m4
Copying file m4/lcmessage.m4
Copying file m4/lock.m4
Copying file m4/longlong.m4
Copying file m4/printf-posix.m4
Copying file m4/size_max.m4
Copying file m4/stdint_h.m4
Copying file m4/threadlib.m4
Copying file m4/uintmax_t.m4
Copying file m4/visibility.m4
Copying file m4/wchar_t.m4
Copying file m4/wint_t.m4
Copying file m4/xsize.m4
Copying file po/Makevars.template
aclocal: installing 'm4/ax_cxx_compile_stdcxx.m4' from
'/usr/share/aclocal/ax_cxx_compile_stdcxx.m4'
aclocal: overwriting 'm4/ax_cxx_compile_stdcxx_11.m4' with
'/usr/share/aclocal/ax_cxx_compile_stdcxx_11.m4'
aclocal: overwriting 'm4/ax_pthread.m4' with '/usr/share/aclocal/ax_pthread.m4'
aclocal: installing 'm4/ax_require_defined.m4' from
'/usr/share/aclocal/ax_require_defined.m4'
aclocal: error: too many loops
aclocal: Please contact .
at /usr/share/automake-1.16/Automake/Channels.pm line 662.
Automake::Channels::msg("automake", "", "too many loops") called at
/usr/share/automake-1.16/Automake/ChannelDefs.pm line 212
Automake::ChannelDefs::prog_error("too many loops") called at
/usr/bin/aclocal line 1195
autoreconf: aclocal failed with exit status: 255
dh_autoreconf: error: autoreconf -f -i returned exit code 1
make: *** [debian/rules:6: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
E: Build command 'cd powertop-2.11 && dpkg-buildpackage -b -uc' failed.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages powertop depends on:
ii libc62.30-0experimental2
ii libgcc-s1 [libgcc1] 10-20200204-1
ii libgcc1 1:10-20200204-1
ii libncursesw6 6.1+20191019-1
ii libnl-3-200 3.4.0-1+b1
ii libnl-genl-3-200 3.4.0-1+b1
ii libpci3 1:3.6.4-1
ii libstdc++6 10-20200204-1
ii libtinfo66.1+20191019-1
powertop recommends no packages.
Versions of packages powertop suggests:
ii cpufrequtils 008-1.1
pn laptop-mode-tools
-- no debconf information
--
Laurent.
Bug#946262: dochelp: Fatal error: out of memory
Hi again,
here is some debugging info:
# strace dochelp update
[...]
openat(AT_FDCWD, "/usr/share/doc/lilypond/html/Documentation",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0
getdents64(3, /* 312 entries */, 32768) = 8256
getdents64(3, /* 0 entries */, 32768) = 0
close(3)= 0
lstat("/usr/share/doc/lintian/lintian.rst.gz", {st_mode=S_IFREG|0644,
st_size=13340, ...}) = 0
mmap(NULL, 1964723146752, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = -1 ENOMEM (Cannot allocate memory)
brk(0x57cf5391a000) = 0x5605e0f1a000
mmap(NULL, 1964723277824, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = -1 ENOMEM (Cannot allocate memory)
write(2, "Fatal error: ", 13Fatal error: ) = 13
write(2, "out of memory", 13out of memory) = 13
write(2, "\n", 1
) = 1
exit_group(2) = ?
+++ exited with 2 +++
--
Laurent.
Bug#946262: dochelp: Fatal error: out of memory
Package: dochelp Version: 0.1.7+b1 Severity: important Dear Maintainer, here is the problem: # apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up dochelp (0.1.7+b1) ... E: /usr/share/doc-base/scalapack-slug: Field "format" is not allowed in section Document E: /usr/share/doc-base/scalapack-pblasqref: Field "format" is not allowed in section Document E: /usr/share/doc-base/scalapack-scalapackqref: Field "format" is not allowed in section Document E: /usr/share/doc-base/scalapack-faq: Field "format" is not allowed in section Document Fatal error: out of memory dpkg: error processing package dochelp (--configure): installed dochelp package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: dochelp It can be reproduced with this command: # dochelp update E: /usr/share/doc-base/scalapack-slug: Field "format" is not allowed in section Document E: /usr/share/doc-base/scalapack-pblasqref: Field "format" is not allowed in section Document E: /usr/share/doc-base/scalapack-scalapackqref: Field "format" is not allowed in section Document E: /usr/share/doc-base/scalapack-faq: Field "format" is not allowed in section Document Fatal error: out of memory This system has 4GB of RAM and 1GB of swap. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dochelp depends on: ii libc6 2.29-4 ii libjs-jquery 3.3.1~dfsg-3 ii libpcre3 2:8.39-12+b1 dochelp recommends no packages. dochelp suggests no packages. -- no debconf information -- Laurent.
Bug#946160: hwloc: please round PCIe link values
On 04/12/2019 16.15, Brice Goglin wrote: > PCIe links (since Gen3) are encoded 128 data rate over 130 signal rate. > That's why you get 3.93 (truncated to 3.9). We decided to keep that > value exact in hwloc because the data/signal rate is different among > PCIe generations. We could round it up to 4 in the lstopo output, but I > am not sure where to start (PCIe Gen4 16x is 31.5GB/s instead of 32 and > Gen5 will be 63 instead of 64, those are harder to round up). Thanks for the detailed explanation! How about displaying the PCIe generation and number of links? -- Laurent.
Bug#946160: hwloc: please round PCIe link values
Package: hwloc Version: 2.1.0+dfsg-2 Severity: normal Dear Maintainer, my system has a NVMe SSD. It is displayed correctly in lstopo. However the PCIe link has a value of "3.9" (see attached file) whereas it should probably be "4.0". -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAG> Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages hwloc depends on: ii libc6 2.29-4 ii libcairo2 1.16.0-4 ii libhwloc15 2.1.0+dfsg-2 ii libtinfo6 6.1+20191019-1 ii libx11-62:1.6.8-1 hwloc recommends no packages. hwloc suggests no packages. -- no debconf information -- Laurent. lstopo.pdf Description: Adobe PDF document
Bug#941902: akonadi-server: syntax errors in apparmor profiles
Package: akonadi-server Version: 4:18.08.3-9 Severity: normal Dear Maintainer, during boot akonadi-server causes the apparmor.service to fail: # systemctl status apparmor.service ● apparmor.service - Load AppArmor profiles Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-10-07 13:14:57 CEST; 1h 43min ago Docs: man:apparmor(7) https://gitlab.com/apparmor/apparmor/wikis/home/ Main PID: 394 (code=exited, status=1/FAILURE) CPU: 432ms Oct 07 13:14:55 irancy.iut2.upmf-grenoble.fr apparmor.systemd[394]: Restarting AppArmor Oct 07 13:14:55 irancy.iut2.upmf-grenoble.fr apparmor.systemd[394]: Reloading AppArmor profiles Oct 07 13:14:55 irancy.iut2.upmf-grenoble.fr apparmor.systemd[394]: AppArmor parser error for /etc/apparmor.d in /etc/apparmor.d/postgresql_akonadi at line 25: syntax error, unexpected $end, expecting TOK_ID or TOK_MODE or TOK_SET_VAR Oct 07 13:14:55 irancy.iut2.upmf-grenoble.fr apparmor.systemd[394]: AppArmor parser error for /etc/apparmor.d in /etc/apparmor.d/mysqld_akonadi at line 36: syntax error, unexpected $end, expecting TOK_ID or TOK_MODE or TOK_SET_VAR Oct 07 13:14:56 irancy.iut2.upmf-grenoble.fr apparmor.systemd[394]: AppArmor parser error for /etc/apparmor.d/mysqld_akonadi in /etc/apparmor.d/mysqld_akonadi at line 36: syntax error, unexpected $end, expecting TOK_ID or TOK_MODE or TO> Oct 07 13:14:56 irancy.iut2.upmf-grenoble.fr apparmor.systemd[394]: AppArmor parser error for /etc/apparmor.d/postgresql_akonadi in /etc/apparmor.d/postgresql_akonadi at line 25: syntax error, unexpected $end, expecting TOK_ID or TOK_MO> Oct 07 13:14:57 irancy.iut2.upmf-grenoble.fr apparmor.systemd[394]: Error: At least one profile failed to load Oct 07 13:14:57 irancy.iut2.upmf-grenoble.fr systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE Oct 07 13:14:57 irancy.iut2.upmf-grenoble.fr systemd[1]: apparmor.service: Failed with result 'exit-code'. Oct 07 13:14:57 irancy.iut2.upmf-grenoble.fr systemd[1]: Failed to start Load AppArmor profiles. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages akonadi-server depends on: ii akonadi-backend-mysql4:18.08.3-9 ii akonadi-backend-postgresql 4:18.08.3-9 ii akonadi-backend-sqlite 4:18.08.3-8 ii libc62.29-2 ii libgcc1 1:9.2.1-8 ii libkf5akonadiprivate5abi2 [libkf5akonadiprivate5-18.08] 4:18.08.3-9 ii libkf5akonadiwidgets5abi1 [libkf5akonadiwidgets5-18.08] 4:18.08.3-9 ii libkf5configcore55.62.0-1 ii libkf5coreaddons55.62.0-1 ii libkf5crash5 5.62.0-1 ii libkf5i18n5 5.62.0-1 ii libqt5core5a 5.11.3+dfsg1-4 ii libqt5dbus5 5.11.3+dfsg1-4 ii libqt5gui5 5.11.3+dfsg1-4 ii libqt5network5 5.11.3+dfsg1-4 ii libqt5sql5 5.11.3+dfsg1-4 ii libqt5widgets5 5.11.3+dfsg1-4 ii libqt5xml5 5.11.3+dfsg1-4 ii libstdc++6 9.2.1-8 akonadi-server recommends no packages. -- Laurent Bonnaud. https://iut2.univ-grenoble-alpes.fr/formations/les-departements-de-l-iut2/informatique-info--149104.kjsp
Bug#941494: udev: 73-special-net-names.rules: Invalid value in rule for ibmveth devices
Package: udev
Version: 243-2
Severity: normal
Dear Maintainer,
here is an error message I see in the journal:
Oct 01 09:32:00 host systemd-udevd[403]:
/usr/lib/udev/rules.d/73-special-net-names.rules:14 Invalid value "/bin/sh -ec
'D=${DEVPATH#*/vio/}; D=${D/*}; D=${D#}; D=${D#0}; D=${D#0}; D=${D#0};
D=${D#0}; echo ${D:-0}'" for PROGRAM (char 16: invalid substitution type),
ignoring, but please fix it.
-- Package-specific info:
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.2.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages udev depends on:
ii adduser 3.118
ii dpkg 1.19.7
ii libacl1 2.2.53-5
ii libblkid1 2.34-0.1
ii libc6 2.29-2
ii libkmod2 26-3
ii libselinux1 2.9-2+b2
ii libudev1 243-2
ii systemd-sysv 243-2
ii util-linux2.34-0.1
udev recommends no packages.
udev suggests no packages.
Versions of packages udev is related to:
ii systemd 243-2
--
Laurent.
Bug#764658: gdm3: cannot see all session choices on smaller screens
Hi, I reported this issue here: https://gitlab.gnome.org/GNOME/gdm/issues/513 -- Laurent.
Bug#931390: xfce4-places-plugin: manpage in wrong section
On 7/8/19 6:24 PM, Yves-Alexis Perez wrote: > Indeed, thanks for the report. I've updated the manpage, that'll be part of > the next upload. Thank you for the fix! -- Laurent.
Bug#931390: xfce4-places-plugin: manpage in wrong section
Package: xfce4-places-plugin Version: 1.7.0-4 Severity: normal Dear Maintainer, this manpage: /usr/share/man/man2/xfce4-popup-places.22.gz is in section 22, which is most certainly a mistake. -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_> Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Laurent.
Bug#929076: kded5: many KDE processes have rwx memory mappings
Package: kded5 Version: 5.54.0-1 Severity: important Dear Maintainer, As a defense against machine code injection attacks made possible by buffer overflow bugs, most Linux distributions have worked over the years to remove as many rwx memory mappings as possible in processes. I checked this on several of my systems and unfortunately I found that many KDE processes do have rwx memory mappings. I chose to report this bug against the kded package because it is one of the most fundamental affected KDE process I found. However, the problem seems to be more general in KDE. I apologize in advance for not finding a better software package to report this problem. STEPS TO REPRODUCE 1. Log in Plasma 2. Run the following command: $ grep rwx /proc/$(pidof kded5)/maps OBSERVED RESULT $ grep rwx /proc/$(pidof kded5)/maps 7f68d7c2a000-7f68d7c3a000 rwxp 00:00 0 EXPECTED RESULT No output -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en> Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kded5 depends on: ii libc6 2.28-10 ii libkf5configcore5 5.54.0-1 ii libkf5coreaddons5 5.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons5 5.54.0-1 ii libkf5service-bin 5.54.0-1 ii libkf5service5 5.54.0-1 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5dbus55.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5widgets5 5.11.3+dfsg1-1 ii libstdc++6 9.1.0-2 kded5 recommends no packages. kded5 suggests no packages. -- no debconf information -- Laurent.
Bug#898060: RPC request reserved xxx but used yyy
Hi, the bug is still present in the latest 4.19 kernel available in Debian: # uname -a Linux erebus4 4.19.0-5-amd64 #1 SMP Debian 4.19.37-1 (2019-05-05) x86_64 GNU/Linux # dmesg [...] [17385.914817] RPC request reserved 228 but used 368 [24814.736955] RPC request reserved 228 but used 368 [97283.415615] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97283.416551] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97283.417521] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97283.418558] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97283.419541] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97283.420521] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97283.421271] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97283.422016] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97283.422656] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97283.423274] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.071038] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.072058] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.073045] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.073815] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.074802] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.075794] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.076782] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.077718] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.078649] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97396.079348] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [97770.036765] RPC request reserved 228 but used 368 [100858.023851] NFSD: client 192.168.141.128 testing state ID with incorrect client ID [100858.024369] NFSD: client 192.168.141.128 testing state ID with incorrect client ID [100858.024777] NFSD: client 192.168.141.128 testing state ID with incorrect client ID [100858.025286] NFSD: client 192.168.141.128 testing state ID with incorrect client ID [100858.025710] NFSD: client 192.168.141.128 testing state ID with incorrect client ID [100858.026219] NFSD: client 192.168.141.128 testing state ID with incorrect client ID [100858.026616] NFSD: client 192.168.141.128 testing state ID with incorrect client ID [100858.027012] NFSD: client 192.168.141.128 testing state ID with incorrect client ID [100858.027431] NFSD: client 192.168.141.128 testing state ID with incorrect client ID [103561.153046] RPC request reserved 228 but used 368 [95.799434] RPC request reserved 228 but used 368 [111251.062518] RPC request reserved 228 but used 368 [114211.124136] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [114211.125137] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [114211.126096] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [114211.127125] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [114211.127814] NFSD: client 192.168.141.107 testing state ID with incorrect client ID [116046.893332] RPC request reserved 228 but used 368 [121936.238050] RPC request reserved 228 but used 368 [128631.646068] RPC request reserved 228 but used 368 -- Laurent.
Bug#856393: lxcfs: error message from the kernel: cgroup: new mount options do not match the existing superblock, will be ignored
On 12/9/18 10:08 PM, Pierre-Elliott Bécue wrote: > I'm sorry nobody gave you any feedback on your bug. No problem, and sorry to answer after such a long time :>. > I've made an upload of lxc 3 in unstable. Could you run some tests with it > and tell me if you get the same issue? Yes. With this package version: Package: lxcfs Version: 3.0.3-2 the kernel still outputs: [2008277.482552] new mount options do not match the existing superblock, will be ignored Thanks, -- Laurent.
Bug#890343: The Debian kernel could use the fq_codel network queuing algorithm by default
Hi, this "bug" still exists in the latest 4.19 kernel in Debian: # uname -a Linux irancy 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux # ip addr [...] 2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 -- Laurent.
Bug#898060: RPC request reserved 84 but used 272
Hi, the bug is still present in the latest 4.19 kernel available in Debian: # uname -a Linux erebus4 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux # dmesg | grep RPC [3.742768] systemd[1]: Listening on RPCbind Server Activation Socket. [3.775310] RPC: Registered named UNIX socket transport module. [3.775311] RPC: Registered udp transport module. [3.775311] RPC: Registered tcp transport module. [3.775312] RPC: Registered tcp NFSv4.1 backchannel transport module. [17262.934669] RPC request reserved 228 but used 368 [17358.306369] RPC request reserved 228 but used 368 [24740.484446] RPC request reserved 148 but used 368 [24741.704647] RPC request reserved 228 but used 368 [26146.799347] RPC request reserved 228 but used 368 [28062.750494] RPC request reserved 228 but used 368 [35307.284580] RPC request reserved 228 but used 368 [35312.033280] RPC request reserved 228 but used 368 [38588.762063] RPC request reserved 228 but used 368 [49064.144596] RPC request reserved 228 but used 468 [103915.176964] RPC request reserved 228 but used 420 [...] -- Laurent.
Bug#925954: uwsgi-emperor: duplicate entry in /etc/logrotate.d/ causes logrotate.service to enter a failed state
Subject: uwsgi-emperor: duplicate
Package: uwsgi-emperor
Version: 2.0.18-1
Severity: important
Dear Maintainer,
here is the problem:
# systemctl status logrotate.service
● logrotate.service - Rotate log files
Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor
preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-03-29 00:00:00 CET; 10h ago
Docs: man:logrotate(8)
man:logrotate.conf(5)
Main PID: 956296 (code=exited, status=1/FAILURE)
Mar 29 00:00:00 irancy.iut2.upmf-grenoble.fr systemd[1]: Starting Rotate log
files...
Mar 29 00:00:00 irancy.iut2.upmf-grenoble.fr logrotate[956296]: error:
uwsgi-emperor:1 duplicate log entry for /var/log/uwsgi/emperor.log
Mar 29 00:00:00 irancy.iut2.upmf-grenoble.fr logrotate[956296]: error: found
error in file uwsgi-emperor, skipping
Mar 29 00:00:00 irancy.iut2.upmf-grenoble.fr systemd[1]: logrotate.service:
Main process exited, code=exited, status=1/FAILURE
Mar 29 00:00:00 irancy.iut2.upmf-grenoble.fr systemd[1]: logrotate.service:
Failed with result 'exit-code'.
Mar 29 00:00:00 irancy.iut2.upmf-grenoble.fr systemd[1]: Failed to start Rotate
log files.
And indeed, the /var/log/uwsgi/emperor.log file is covered by 2 rules in
/etc/logrotate.d/ :
# grep -r uwsgi /etc/logrotate.d/
/etc/logrotate.d/uwsgi:"/var/log/uwsgi/*.log" "/var/log/uwsgi/app/*.log" {
/etc/logrotate.d/uwsgi-emperor:"/var/log/uwsgi/emperor.log" {
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages uwsgi-emperor depends on:
ii uwsgi-core 2.0.18-1
uwsgi-emperor recommends no packages.
uwsgi-emperor suggests no packages.
-- no debconf information
--
Laurent.
Bug#925160: request for performance test in your environment
On 3/24/19 2:06 PM, Osamu Aoki wrote: > FYI: I have uploaded 0.41-1 which is essentially code clean up with > lintian warning removal actions such as adding autopkgtest data. > So use this 0.41-1, please. Thanks a lot! > I will be curious how these affects performance. SSH connections are now almost instantaneous on my system. > When you report, please tell us you use SSD or HDD for /usr/lib/*. My system has a SSD. > Also give us idea how many directories we are talking by including > > $ ls -1 /usr/lib /usr/lib/x86_64-linux-gnu|wc -l 18279 Thanks again, -- Laurent.
Bug#925160: systemd: user session slow to start (11 seconds)
On 20/03/2019 19.39, Michael Biebl wrote: > Another info that might help give a clue is setting > LogLevel=debug in /etc/systemd/user.conf, reboot, log in, then attach > the output of journalctl --user -b Thanks, it allowed me to find the cause of the problem: Mar 21 13:41:49 hostname sshd[237915]: Accepted publickey for root from 193.55.51.152 port 41646 ssh2: RSA SHA256:wmFQ70BsRjT4uCWua2ddnbfFv7kiMecLHVNtZMw0KMk Mar 21 13:41:49 hostname sshd[237915]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 21 13:41:49 hostname systemd-logind[743]: New session 4844 of user root. Mar 21 13:41:49 hostname systemd[1]: Starting User Manager for UID 0... Mar 21 13:41:49 hostname systemd[237918]: pam_unix(systemd-user:session): session opened for user root by (uid=0) Mar 21 13:41:49 hostname systemd[237918]: Found container virtualization none. Mar 21 13:41:49 hostname systemd[237918]: systemd 241 running in user mode for user 0/root. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELF Mar 21 13:41:49 hostname systemd[237918]: RLIMIT_MEMLOCK is already as high or higher than we need it, not bumping. Mar 21 13:41:49 hostname systemd[237918]: Found cgroup2 on /sys/fs/cgroup/unified, unified hierarchy for systemd controller Mar 21 13:41:49 hostname systemd[237918]: Unified cgroup hierarchy is located at /sys/fs/cgroup/unified/user.slice/user-0.slice/user@0.service. Controllers are on legacy hierarchies. Mar 21 13:41:49 hostname systemd[237918]: Got EBADF when using BPF_F_ALLOW_MULTI, which indicates it is supported. Yay! Mar 21 13:41:49 hostname systemd[237918]: Controller 'cpu' supported: yes Mar 21 13:41:49 hostname systemd[237918]: Controller 'cpuacct' supported: yes Mar 21 13:41:49 hostname systemd[237918]: Controller 'io' supported: no Mar 21 13:41:49 hostname systemd[237918]: Controller 'blkio' supported: yes Mar 21 13:41:49 hostname systemd[237918]: Controller 'memory' supported: yes Mar 21 13:41:49 hostname systemd[237918]: Controller 'devices' supported: yes Mar 21 13:41:49 hostname systemd[237918]: Controller 'pids' supported: yes Mar 21 13:41:49 hostname systemd[237918]: Controller 'bpf-firewall' supported: yes Mar 21 13:41:49 hostname systemd[237918]: Controller 'bpf-devices' supported: yes Mar 21 13:41:49 hostname systemd[237918]: Set up TFD_TIMER_CANCEL_ON_SET timerfd. Mar 21 13:41:49 hostname systemd[237918]: Serializing user-environment-generators to memfd. Mar 21 13:41:49 hostname systemd[237918]: Successfully forked off '(sd-executor)' as PID 237922. Mar 21 13:41:49 hostname systemd[237922]: Serializing 30-systemd-environment-d-generator to memfd. Mar 21 13:41:49 hostname systemd[237922]: Successfully forked off '(direxec)' as PID 237923. Mar 21 13:41:49 hostname systemd[237922]: /usr/lib/systemd/user-environment-generators/30-systemd-environment-d-generator succeeded. Mar 21 13:41:49 hostname systemd[237922]: Serializing 60-flatpak to memfd. Mar 21 13:41:49 hostname systemd[237922]: Successfully forked off '(direxec)' as PID 237924. Mar 21 13:41:49 hostname systemd[237922]: /usr/lib/systemd/user-environment-generators/60-flatpak succeeded. Mar 21 13:41:49 hostname systemd[237922]: Serializing 70-im-config to memfd. Mar 21 13:41:49 hostname systemd[237922]: Successfully forked off '(direxec)' as PID 237927. Mar 21 13:42:02 hostname systemd[237922]: /usr/lib/systemd/user-environment-generators/70-im-config succeeded. Therefore the problem is in /usr/lib/systemd/user-environment-generators/70-im-config. Moving this file away solves the problem :>. Should I reassign this bug to the im-config package ? Thanks again, -- Laurent.
Bug#925160: systemd: user session slow to start (11 seconds)
On 3/20/19 7:24 PM, Michael Biebl wrote: >> Do you have any (user) generators which might take a long time? > Typical places to check: > > /usr/lib/systemd/user-environment-generators/ > /usr/lib/systemd/user-generators/ Here is what I have in this system: # ls -l /usr/lib/systemd/user-environment-generators/ /usr/lib/systemd/user-generators/ /usr/lib/systemd/user-environment-generators/: total 28 -rwxr-xr-x 1 root root 14320 Mar 15 18:33 30-systemd-environment-d-generator -rwxr-xr-x 1 root root 472 Feb 11 17:17 60-flatpak -rwxr-xr-x 1 root root 287 Mar 8 18:09 70-im-config -rwxr-xr-x 1 root root 309 Mar 2 17:49 90gpg-agent /usr/lib/systemd/user-generators/: total 0 > and the equivalent locations in /etc and ~/.config/systemd This directory does not exist in my homedirs. Thanks, -- Laurent.
Bug#925160: systemd: user session slow to start (11 seconds)
On 3/20/19 5:52 PM, Michael Biebl wrote: > Is this problem reproducible if you login locally? Yes. When I log in from a local VT, just after typing the password: - I see the contents of /etc/motd - I wait for 11 seconds - then I see the shell prompt Thanks, -- Laurent.
Bug#925160: systemd: user session slow to start (11 seconds)
On 3/20/19 5:47 PM, Michael Prokop wrote: > What do you mean with "Further connections are fast", ssh-ing into > the system as the same user ? Exactly. > (do you use ssh with ControlMaster?) I do not use ControlMaster. > Is connecting via `ssh -o ControlPath=none ...` also slow? Using the "-o ControlPath=none" option is also slow. Thanks, -- Laurent.
Bug#925160: systemd: user session slow to start (11 seconds)
On 3/20/19 5:47 PM, Michael Prokop wrote: > Just a quick shot, are you sure your reverse DNS is OK? Yes. > If you set `UseDNS no` in /etc/ssh/sshd_config, is the SSH login faster? Setting "UseDNS no" does not solve the problem. Thanks, -- Laurent.
Bug#925160: systemd: user session slow to start (11 seconds)
On 3/20/19 5:52 PM, Michael Biebl wrote: > Is this problem reproducible if you login locally? Sorry, I will have to wait until tomorrow to have physical access to this system... Thanks, -- Laurent.
Bug#925160: systemd: user session slow to start (11 seconds)
Package: systemd Version: 241-2 Severity: important Dear Maintainer, on this system, an initial ssh connection needs 11 seconds to complete (as root or any other user). Further connections are fast. This is not a slow boot problem because it occurs even when the machine has been booted for days. It comes from a slow start of the user's session as can be seen in this log: Mar 20 15:06:27 hostname sshd[172771]: Accepted publickey for root from 193.55.51.153 port 53702 ssh2: RSA SHA256:wmFQ70BsRjT4uCWua2ddnbfFv7kiMecLHVNtZMw0KMk Mar 20 15:06:27 hostname sshd[172771]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 20 15:06:27 hostname systemd-logind[743]: New session 3373 of user root. Mar 20 15:06:27 hostname systemd[1]: Starting User Manager for UID 0... Mar 20 15:06:27 hostname systemd[172774]: pam_unix(systemd-user:session): session opened for user root by (uid=0) [11 seconds gap] Mar 20 15:06:38 hostname systemd[172774]: Listening on GnuPG network certificate management daemon. Mar 20 15:06:38 hostname systemd[172774]: Reached target Timers. Mar 20 15:06:38 hostname systemd[172774]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 20 15:06:38 hostname systemd[172774]: Reached target Paths. Mar 20 15:06:38 hostname systemd[172774]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 20 15:06:38 hostname systemd[172774]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 20 15:06:38 hostname systemd[172774]: Listening on Multimedia System. Mar 20 15:06:38 hostname systemd[172774]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 20 15:06:38 hostname systemd[172774]: Condition check resulted in Sound System being skipped. Mar 20 15:06:38 hostname systemd[172774]: Starting D-Bus User Message Bus Socket. Mar 20 15:06:38 hostname systemd[172774]: Listening on D-Bus User Message Bus Socket. Mar 20 15:06:38 hostname systemd[172774]: Reached target Sockets. Mar 20 15:06:38 hostname systemd[172774]: Reached target Basic System. Mar 20 15:06:38 hostname systemd[172774]: Reached target Default. Mar 20 15:06:38 hostname systemd[172774]: Startup finished in 11.151s. Mar 20 15:06:38 hostname systemd[1]: Started User Manager for UID 0. Mar 20 15:06:38 hostname systemd[1]: Started Session 3373 of user root. The problem can also be seen here: # systemd-analyze --user Startup finished in 11.151s (userspace) default.target reached after 11.151s in userspace # systemd-analyze --user blame 7ms dbus.socket # systemd-analyze --user critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. default.target @11.151s └─basic.target @11.150s └─sockets.target @11.150s └─dbus.socket @11.143s +7ms └─run-user-0.mount @11.137s └─-.mount @11.137s └─-.slice @11.137s In a further e-mail I will send the output of this command: # systemd-analyze --user dump -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US. UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.53-4 ii libapparmor1 2.13.2-9 ii libaudit11:2.8.4-2 ii libblkid12.33.1-0.1 ii libc62.28-8 ii libcap2 1:2.25-2 ii libcryptsetup12 2:2.1.0-2 ii libgcrypt20 1.8.4-5 ii libgnutls30 3.6.6-3 ii libgpg-error01.36-1 ii libidn11 1.33-2.2 ii libip4tc01.8.2-4 ii libkmod2 26-1 ii liblz4-1 1.8.3-1 ii liblzma5 5.2.4-1 ii libmount12.33.1-0.1 ii libpam0g 1.3.1-5 ii libseccomp2 2.3.3-4 ii libselinux1 2.9-1 ii libsystemd0 241-2 ii mount2.33.1-0.1 ii util-linux 2.33.1-0.1 Versions of packages systemd recommends: ii dbus1.13.8-1 ii libpam-systemd 241-2 Versions of packages systemd suggests: ii policykit-10.115-3 ii systemd-container 241-2 Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.133 ii udev 241-2 -- no debconf information -- Laurent.
Bug#920177: linux-image-amd64-rt: BUG while removing the sunrpc module
Hi, the bug is still there in this package version: Source: linux-signed-amd64 (4.19.28+2) Version: 4.19.28-2 [ 311.093489] RPC: Unregistered named UNIX socket transport module. [ 311.093493] RPC: Unregistered udp transport module. [ 311.093494] RPC: Unregistered tcp transport module. [ 311.093494] RPC: Unregistered tcp NFSv4.1 backchannel transport module. [ 311.093546] = [ 311.093548] BUG rpc_inode_cache (Not tainted): Objects remaining in rpc_inode_cache on __kmem_cache_shutdown() [ 311.093548] - [ 311.093549] Disabling lock debugging due to kernel taint [ 311.093551] INFO: Slab 0xf538f3cb objects=18 used=13 fp=0x36f8e292 flags=0x17fffc08100 [ 311.093554] CPU: 0 PID: 2939 Comm: rmmod Tainted: GB 4.19.0-4-rt-amd64 #1 Debian 4.19.28-2 [ 311.093555] Hardware name: Dell Inc. OptiPlex 7010/0KRC95, BIOS A29 06/28/2018 [ 311.093555] Call Trace: [ 311.093564] dump_stack+0x5c/0x80 [ 311.093568] slab_err+0xb0/0xd4 [ 311.093572] ? cpumask_next+0x16/0x20 [ 311.093574] ? flush_all+0x66/0x100 [ 311.093576] __kmem_cache_shutdown.cold.103+0x1c/0x26 [ 311.093581] shutdown_cache+0x15/0x1c0 [ 311.093583] kmem_cache_destroy+0x216/0x240 [ 311.093603] unregister_rpc_pipefs+0x16/0x30 [sunrpc] [ 311.093617] cleanup_sunrpc+0x1e/0x39 [sunrpc] [ 311.093620] __x64_sys_delete_module+0x190/0x2c0 [ 311.093623] do_syscall_64+0x53/0x100 [ 311.093626] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 311.093628] RIP: 0033:0x7f4dd72d8137 [ 311.093630] Code: 73 01 c3 48 8b 0d 59 0d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 29 0d 0c 00 f7 d8 64 89 01 48 [ 311.093631] RSP: 002b:7ffce99a5c78 EFLAGS: 0206 ORIG_RAX: 00b0 [ 311.093633] RAX: ffda RBX: 557deefcf220 RCX: 7f4dd72d8137 [ 311.093634] RDX: 000a RSI: 0800 RDI: 557deefcf288 [ 311.093634] RBP: R08: 7ffce99a4bf1 R09: [ 311.093635] R10: 7f4dd7349ae0 R11: 0206 R12: 7ffce99a5ea0 [ 311.093636] R13: 7ffce99a6c31 R14: 557deefce010 R15: 557deefcf220 [ 311.093638] kmem_cache_destroy rpc_inode_cache: Slab cache still has objects [ 311.099909] CPU: 0 PID: 2939 Comm: rmmod Tainted: GB 4.19.0-4-rt-amd64 #1 Debian 4.19.28-2 [ 311.099910] Hardware name: Dell Inc. OptiPlex 7010/0KRC95, BIOS A29 06/28/2018 [ 311.099910] Call Trace: [ 311.099915] dump_stack+0x5c/0x80 [ 311.099919] kmem_cache_destroy+0x233/0x240 [ 311.099937] unregister_rpc_pipefs+0x16/0x30 [sunrpc] [ 311.099950] cleanup_sunrpc+0x1e/0x39 [sunrpc] [ 311.099952] __x64_sys_delete_module+0x190/0x2c0 [ 311.099957] do_syscall_64+0x53/0x100 [ 311.099959] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 311.099961] RIP: 0033:0x7f4dd72d8137 [ 311.099963] Code: 73 01 c3 48 8b 0d 59 0d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 29 0d 0c 00 f7 d8 64 89 01 48 [ 311.099964] RSP: 002b:7ffce99a5c78 EFLAGS: 0206 ORIG_RAX: 00b0 [ 311.099965] RAX: ffda RBX: 557deefcf220 RCX: 7f4dd72d8137 [ 311.099966] RDX: 000a RSI: 0800 RDI: 557deefcf288 [ 311.099967] RBP: R08: 7ffce99a4bf1 R09: [ 311.099967] R10: 7f4dd7349ae0 R11: 0206 R12: 7ffce99a5ea0 [ 311.099968] R13: 7ffce99a6c31 R14: 557deefce010 R15: 557deefcf220 -- Laurent.
Bug#924303: fonts-noto-core: creates an obsolete config file
Package: fonts-noto-core
Version: 20181227-1
Severity: normal
Dear Maintainer,
here is the problem:
$ dpkg-query -W -f='${Conffiles}\n' | grep obsolete$
/etc/fonts/conf.avail/30-droid-noto.conf a34074694dce0a5ccc5844ec0a1315ea
obsolete
-- Package-specific info:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---=
ii fontconfig 2.13.1-2 amd64generic font configuration
library - support binaries
ii libfreetype6:amd64 2.9.1-3 amd64FreeType 2 font engine, shared
library files
ii libxft2:amd64 2.3.2-2 amd64FreeType-based font drawing
library for X
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- Configuration Files:
/etc/fonts/conf.avail/30-droid-noto.conf [Errno 2] No such file or directory:
'/etc/fonts/conf.avail/30-droid-noto.conf'
-- no debconf information
--
Laurent.
Bug#898060: RPC request reserved 84 but used 180
Hi, I tested the latest kernel from sid on a Debian stretch NFS server and I am still seeing those errors: # uname -a Linux xxx 4.19.0-3-amd64 #1 SMP Debian 4.19.20-1 (2019-02-11) x86_64 GNU/Linux # dmesg | grep RPC [3.771107] RPC: Registered named UNIX socket transport module. [3.771107] RPC: Registered udp transport module. [3.771108] RPC: Registered tcp transport module. [3.771108] RPC: Registered tcp NFSv4.1 backchannel transport module. [10935.178313] RPC request reserved 228 but used 420 [17600.583217] RPC request reserved 228 but used 368 [22343.748585] RPC request reserved 228 but used 368 [24651.947073] RPC request reserved 228 but used 368 [24701.408918] RPC request reserved 228 but used 368 [37470.043890] RPC request reserved 228 but used 368 [104256.308825] RPC request reserved 228 but used 368 [107048.398632] RPC request reserved 228 but used 368 [108543.686081] RPC request reserved 228 but used 368 [210531.371532] RPC request reserved 148 but used 468 [362822.294773] RPC request reserved 228 but used 368 [370389.005118] RPC request reserved 228 but used 368 [387965.206640] RPC request reserved 228 but used 368 [388109.336304] RPC request reserved 228 but used 368 [388329.055197] RPC request reserved 228 but used 368 [388453.648963] RPC request reserved 228 but used 368 [388568.098433] RPC request reserved 228 but used 368 [388619.549655] RPC request reserved 228 but used 368 [391940.696269] RPC request reserved 228 but used 368 -- Laurent.
Bug#920177: linux-image-4.19.0-2-rt-amd64-unsigned: BUG while removing the sunrpc module
Subject: linux-image-4.19.0-2-rt-amd64-unsigned: BUG Package: src:linux Version: 4.19.16-1 Severity: normal Dear Maintainer, I was trying to remove the sunrpc module from the kernel and got the following BUG and backtrace. Note that the kernel is tainted because of this previous error that is unrelated: [1.514708] button: module verification failed: signature and/or required key missing - tainting kernel [ 204.858131] RPC: Unregistered named UNIX socket transport module. [ 204.858134] RPC: Unregistered udp transport module. [ 204.858136] RPC: Unregistered tcp transport module. [ 204.858137] RPC: Unregistered tcp NFSv4.1 backchannel transport module. [ 204.859248] = [ 204.859251] BUG rpc_inode_cache (Tainted: GE): Objects remaining in rpc_inode_cache on __kmem_cache_shutdown() [ 204.859251] - [ 204.859252] Disabling lock debugging due to kernel taint [ 204.859255] INFO: Slab 0x006c197c objects=18 used=13 fp=0xa584567e flags=0x17fffc08100 [ 204.859259] CPU: 0 PID: 3633 Comm: rmmod Tainted: GB E 4.19.0-2-rt-amd64 #1 Debian 4.19.16-1 [ 204.859260] Hardware name: Dell Inc. OptiPlex 7010/0KRC95, BIOS A29 06/28/2018 [ 204.859261] Call Trace: [ 204.859269] dump_stack+0x5c/0x80 [ 204.859273] slab_err+0xb0/0xd4 [ 204.859277] ? cpumask_next+0x16/0x20 [ 204.859279] ? flush_all+0x66/0x100 [ 204.859282] __kmem_cache_shutdown.cold.103+0x1c/0x26 [ 204.859287] shutdown_cache+0x15/0x1c0 [ 204.859290] kmem_cache_destroy+0x216/0x240 [ 204.859316] unregister_rpc_pipefs+0x16/0x30 [sunrpc] [ 204.859334] cleanup_sunrpc+0x1e/0x39 [sunrpc] [ 204.859337] __x64_sys_delete_module+0x190/0x2c0 [ 204.859341] do_syscall_64+0x53/0x100 [ 204.859346] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 204.859349] RIP: 0033:0x7f43fb8a00f7 [ 204.859351] Code: 73 01 c3 48 8b 0d 99 0d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 69 0d 0c 00 f7 d8 64 89 01 48 [ 204.859354] RSP: 002b:7ffc4236d208 EFLAGS: 0206 ORIG_RAX: 00b0 [ 204.859356] RAX: ffda RBX: 55a14f7eb220 RCX: 7f43fb8a00f7 [ 204.859357] RDX: 000a RSI: 0800 RDI: 55a14f7eb288 [ 204.859358] RBP: R08: 7ffc4236c181 R09: [ 204.859359] R10: 7f43fb911ae0 R11: 0206 R12: 7ffc4236d430 [ 204.859360] R13: 7ffc4236ec4b R14: 55a14f7ea010 R15: 55a14f7eb220 [ 204.859363] kmem_cache_destroy rpc_inode_cache: Slab cache still has objects [ 204.859621] CPU: 0 PID: 3633 Comm: rmmod Tainted: GB E 4.19.0-2-rt-amd64 #1 Debian 4.19.16-1 [ 204.859622] Hardware name: Dell Inc. OptiPlex 7010/0KRC95, BIOS A29 06/28/2018 [ 204.859623] Call Trace: [ 204.859626] dump_stack+0x5c/0x80 [ 204.859629] kmem_cache_destroy+0x233/0x240 [ 204.859647] unregister_rpc_pipefs+0x16/0x30 [sunrpc] [ 204.859664] cleanup_sunrpc+0x1e/0x39 [sunrpc] [ 204.859666] __x64_sys_delete_module+0x190/0x2c0 [ 204.859670] do_syscall_64+0x53/0x100 [ 204.859673] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 204.859675] RIP: 0033:0x7f43fb8a00f7 [ 204.859677] Code: 73 01 c3 48 8b 0d 99 0d 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 69 0d 0c 00 f7 d8 64 89 01 48 [ 204.859678] RSP: 002b:7ffc4236d208 EFLAGS: 0206 ORIG_RAX: 00b0 [ 204.859679] RAX: ffda RBX: 55a14f7eb220 RCX: 7f43fb8a00f7 [ 204.859680] RDX: 000a RSI: 0800 RDI: 55a14f7eb288 [ 204.859681] RBP: R08: 7ffc4236c181 R09: [ 204.859682] R10: 7f43fb911ae0 R11: 0206 R12: 7ffc4236d430 [ 204.859683] R13: 7ffc4236ec4b R14: 55a14f7ea010 R15: 55a14f7eb220 -- Package-specific info: ** Version: Linux version 4.19.0-2-rt-amd64 (debian-ker...@lists.debian.org) (gcc version 8.2.0 (Debian 8.2.0-14)) #1 SMP PREEMPT RT Debian 4.19.16-1 (2019-01-17) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-2-rt-amd64 root=UUID=c27a1c2e-4689-49ec-ab55-bba0dae046dc ro vsyscall=none security=apparmor intel_iommu=on quiet ** Tainted: BE (8224) * System has hit bad_page. * Unsigned module has been loaded. ** Model information sys_vendor: Dell Inc. product_name: OptiPlex 7010 product_version: 01 chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A29 board_vendor: Dell Inc. board_name: 0KRC95 board_version: A02 ** Loaded modules: cpufreq_conservative(E) cpufreq_userspace(E) cpufreq_powersave(E) intel_rapl(E) intel_powerclamp(E) coretemp(E)
Bug#288373: matchbox-panel: KDE complains about mb-* desktop files
Hi,
after all these years, this bug still exists:
$ desktop-file-validate /usr/share/applications/mb-applet-battery.desktop
/usr/share/applications/mb-applet-battery.desktop: error: value "PanelApp" for
key "Type" in group "Desktop Entry" is not a registered type value
("Application", "Link" and "Directory")
/usr/share/applications/mb-applet-battery.desktop: error: (will be fatal in the
future): value "miniapm.png" for key "Icon" in group "Desktop Entry" is an icon
name with an extension, but there should be no extension as described in the
Icon Theme Specification if the value is not an absolute path
/usr/share/applications/mb-applet-battery.desktop: error: value
"Panel;Utility;MB" for key "Categories" in group "Desktop Entry" contains an
unregistered value "Panel"; values extending the format should start with "X-"
/usr/share/applications/mb-applet-battery.desktop: error: value
"Panel;Utility;MB" for key "Categories" in group "Desktop Entry" contains an
unregistered value "MB"; values extending the format should start with "X-"
And the upstream bug tracker does not seem to be working :<.
--
Laurent.
Bug#910363: spice-vdagent: tmpfiles.d/spice-vdagentd.conf uses /var/run instead of /run
Package: spice-vdagent Version: 0.17.0-1 Severity: normal Dear Maintainer, here is the problem: # apt install spice-vdagent [...] Setting up spice-vdagent (0.17.0-1) ... [...] [/usr/lib/tmpfiles.d/spice-vdagentd.conf:2] Line references path below legacy directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; please update the tmpfiles.d/ drop-in file accordingly. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages spice-vdagent depends on: ii init-system-helpers 1.54 ii libasound2 1.1.6-1 ii libc62.27-6 ii libdbus-1-3 1.13.6-1 ii libglib2.0-0 2.58.1-2 ii libpciaccess00.14-1 ii libsystemd0 239-10 ii libx11-6 2:1.6.6-1 ii libxfixes3 1:5.0.3-1 ii libxinerama1 2:1.1.4-1 ii libxrandr2 2:1.5.1-1 spice-vdagent recommends no packages. spice-vdagent suggests no packages. -- no debconf information -- Laurent.
Bug#910362: fail2ban: tmpfiles.d/fail2ban-tmpfiles.conf uses /var/run instead of /run
Package: fail2ban Version: 0.10.2-2.1 Severity: normal Dear Maintainer, here is the problem: # apt install fail2ban [...] Setting up fail2ban (0.10.2-2.1) ... [fail2ban-tmpfiles.conf:1] Line references path below legacy directory /var/run/, updating /var/run/fail2ban → /run/fail2ban; please update the tmpfiles.d/ drop-in file accordingly. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Laurent.
Bug#901533: mesa: please build
Source: mesa Severity: wishlist Dear Maintainer, the Mesa source package contains this file: ./mesa-18.1.1/src/intel/tools/intel_sanitize_gpu.c but it is not built during the Debian binary packages creation. Could you please build it? It would be very helpful to debug Mesa issues, such as: https://bugs.freedesktop.org/show_bug.cgi?id=106859 -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Laurent.
Bug#899974: dhelp: ruby warnings: parentheses after method name is interpreted as an argument list, not a decomposed argument
Package: dhelp Version: 0.6.25 Severity: normal Dear Maintainer, here is the problem: $ /usr/sbin/dhelp_parse /usr/lib/ruby/vendor_ruby/debian.rb:223: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:224: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:227: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:230: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:233: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:236: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:348: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:557: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:577: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:578: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:743: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:753: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:763: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:772: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:799: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:1004: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument Usage: dhelp_parse [-a | -d]... [DOCBASE_FILE]... or: dhelp_parse [-r | -i] Add/remove doc-base documents to/from Debian Online Help database or index them fully or incrementally. [...] -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dhelp depends on: ii doc-base0.10.8 ii ghostscript 9.22~dfsg-2.1 ii libcgi-pm-perl 4.38-1 ii libdata-page-perl 2.02-1 ii libhtml-parser-perl 3.72-3+b2 ii liblocale-gettext-perl 1.07-3+b3 ii libtemplate-perl2.27-1 ii liburi-perl 1.74-1 ii perl5.26.2-5 ii poppler-utils 0.64.0-1 ii ruby1:2.5.1 ii ruby-debian 0.3.9+b8 ii ruby-gettext3.2.9-1 ii swish++ 6.1.5-5 ii ucf 3.0038 dhelp recommends no packages. -- Laurent.
Bug#899972: bind9: apparmor profile includes local profile but does not provide it
Package: bind9 Version: 1:9.11.3+dfsg-1 Severity: normal Dear Maintainer, here is the problem: # aa-logprof Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. ERROR: Include file /etc/apparmor.d/local/usr.sbin.named not found [fatal error: aa-logprof stops here] This is caused by /etc/apparmor.d/usr.sbin.named that contains this line: #include but the /etc/apparmor.d/local/usr.sbin.named file does not exist. Could bind9 please provide this file in its package? An empty file is enough. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Laurent.
Bug#889715: libopenmpi-dev: problem in alternatives handling
On 02/06/2018 01:55 PM, Alastair McKinstry wrote: > This appears to be a downgrade from experimental 3.0.1*. I confirm that I had experimental packages that I later downgraded. Thanks for looking at this and for the fix! -- Laurent.
Bug#895201: trousers: syntax error in init script
Package: trousers Version: 0.3.14+fixed1-1 Severity: important Dear Maintainer, here is the problem: # apt install tpm-tools [...] Apr 08 12:33:44 xeelee trousers[12046]: * Starting Trusted Computing daemon tcsd Apr 08 12:33:44 xeelee trousers[12046]: /etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator The problem comes from the fact that on this system, there are 2 /dev/tmp* devices: # ls -l /dev/tpm* crw--- 1 tss tss 10, 224 Apr 8 12:33 /dev/tpm0 crw--- 1 root root 253, 65536 Apr 8 11:17 /dev/tpmrm0 BTW, see bug #787244. Perhaps a solution would be to replace if [ ! -e /dev/tpm* ] with if [ ! -e /dev/tpm? ] -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages trousers depends on: ii adduser3.117 ii libc6 2.27-3 ii libssl1.1 1.1.1~~pre4-1 ii lsb-base 9.20170808 trousers recommends no packages. trousers suggests no packages. -- Configuration Files: /etc/tcsd.conf [Errno 13] Permission denied: '/etc/tcsd.conf' -- no debconf information -- Laurent.
Bug#855105: xserver-xorg-core: numerous deleted DRM mmaped objects in Xorg server memory mappings
Not a bug according to upstream. Closing... -- Laurent.
Bug#855105: xserver-xorg-core: numerous deleted DRM mmaped objects in Xorg server memory mappings
> I confirm that on another test system with an AMD GPU I do not observe the > deleted mappings. With the more recent Xorg/mesa version now in sid the deleted objects have a different name: # grep i915 /proc/$(pidof Xorg)/maps 7f4c2793-7f4c27935000 rw-s 00:16 1011645/i915 (deleted) 7f4c27935000-7f4c2793a000 rw-s 00:16 1003904/i915 (deleted) 7f4c2793a000-7f4c2793e000 rw-s 00:16 1018009/i915 (deleted) 7f4c2793e000-7f4c2794e000 rw-s 00:16 1003894/i915 (deleted) 7f4c2794e000-7f4c27953000 rw-s 00:16 1003372/i915 (deleted) 7f4c27953000-7f4c27958000 rw-s 00:16 1016242/i915 (deleted) 7f4c27958000-7f4c2795c000 rw-s 00:16 1017939/i915 (deleted) 7f4c2795c000-7f4c2796c000 rw-s 00:16 1003866/i915 (deleted) 7f4c2796c000-7f4c27971000 rw-s 00:16 1016240/i915 (deleted) 7f4c27b86000-7f4c27b8a000 rw-s 00:16 1017996/i915 (deleted) 7f4c27b8a000-7f4c27b8f000 rw-s 00:16 1016238/i915 (deleted) 7f4c27b8f000-7f4c27b93000 rw-s 00:16 1017505/i915 (deleted) 7f4c27b93000-7f4c27c13000 rw-s 00:16 972018 /i915 (deleted) 7f4c2d468000-7f4c2d46c000 rw-s 00:16 1016411/i915 (deleted) 7f4c2d46c000-7f4c2d471000 rw-s 00:16 972003 /i915 (deleted) 7f4c2d59f000-7f4c2d5a7000 rw-s 00:16 972019 /i915 (deleted) 7f4c2d5e9000-7f4c2d5ed000 rw-s 00:16 1018025/i915 (deleted) It makes it obvious that the problem is specific to Intel GPUs. -- Laurent.
Bug#891208: xserver-xorg-core: write and execute memory regions
Package: xserver-xorg-core Version: 2:1.19.6-1 Severity: normal Dear Maintainer, the Xorg process runs with one memory zone that has both write and execute permissions: # grep rwxp /proc/$(pidof Xorg)/maps 7f4c2d5e8000-7f4c2d5e9000 rwxp 00:00 0 I see this in my 2 test systems, one with Intel GPU, the other with radeon GPU. This is a problem because in case of a bug in the server, it might be use to inject code into its process. The same problem does exist neither in Debian 9, nor in Ubuntu 17.10, nor in Ubuntu 18.04, nor in Fedora 27. It seems specific to Debian sid. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xserver-xorg-core depends on: ii keyboard-configuration 1.178 ii libaudit1 1:2.8.2-1 ii libbsd0 0.8.7-1 ii libc6 2.27-0experimental0 ii libdbus-1-3 1.13.0-1 ii libdrm2 2.4.90-1 ii libegl1 1.0.0-2 ii libegl1-mesa18.0.0~rc4-1 ii libepoxy0 1.4.3-1 ii libgbm1 18.0.0~rc4-1 ii libgcrypt20 1.8.2-1 ii libgl1 1.0.0-2 ii libpciaccess0 0.13.4-1+b2 ii libpixman-1-0 0.34.0-2 ii libselinux1 2.7-2+b1 ii libsystemd0 237-3 ii libudev1237-3 ii libxau6 1:1.0.8-1+b2 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.1-4 ii libxshmfence1 1.2-1+b2 ii udev237-3 ii xserver-common 2:1.19.6-1 Versions of packages xserver-xorg-core recommends: ii libgl1-mesa-dri 18.0.0~rc4-1 ii libpam-systemd 237-3 Versions of packages xserver-xorg-core suggests: ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 -- no debconf information -- Laurent.
Bug#890343: systemd: Debian could use the fq_codel network queuing algorithm by default
On 2/13/18 6:29 PM, Felipe Sateler wrote: > Changelog has this by Marco d'Itri: > >> * Do not install sysctl.d/50-default.conf because the systemd package >>should not change kernel policies, at least until it will become >>the only supported init system. Thanks for pointing this out! I did not find it with "grep codel". > And it makes sense: why would some users get this but others don't? Indeed. I will therefore reassign this bug to the kernel... Thanks again, -- Laurent.
Bug#890343: systemd: Debian could use the fq_codel network queuing algorithm by default
Package: systemd Version: 237-2 Severity: normal Dear Maintainer, by default Debian uses the pfifo_fast network queuing algorithm: # tc -s qdisc show [...] qdisc pfifo_fast 0: dev eth0 root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 Sent 413728102 bytes 475015 pkt (dropped 0, overlimits 0 requeues 785) backlog 0b 0p requeues 785 The systemd source package contains this file: ./systemd-237/sysctl.d/50-default.conf:net.core.default_qdisc = fq_codel whose purpose is to set the default queuing algorithm to fq_codel. According to the NEWS file, this is a better alternative: * The default sysctl.d/ snippets will now set: net.core.default_qdisc = fq_codel This selects Fair Queuing Controlled Delay as the default queuing discipline for network interfaces. fq_codel helps fight the network bufferbloat problem. It is believed to be a good default with no tuning required for most workloads. Downstream distributions may override this choice. On 10Gbit servers that do not do forwarding, "fq" may perform better. Systems without a good clocksource should use "pfifo_fast". However the 50-default.conf file is not in the Debian binary package. Is this intentional or an omission? Could it be possible to enable fq_codel by default? -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.117 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.12-2 ii libaudit11:2.8.2-1 ii libblkid12.31.1-0.1 ii libc62.27-0experimental0 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.1-1 ii libgcrypt20 1.8.2-1 ii libgpg-error01.27-6 ii libidn11 1.33-2.1 ii libip4tc01.6.2-1 ii libkmod2 25-1 ii liblz4-1 0.0~r131-2+b1 ii liblzma5 5.2.2-1.3 ii libmount12.31.1-0.1 ii libpam0g 1.1.8-3.7 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.7-2+b1 ii libsystemd0 237-2 ii mount2.31.1-0.1 ii procps 2:3.3.12-4 ii util-linux 2.31.1-0.1 Versions of packages systemd recommends: ii dbus1.13.0-1 ii libpam-systemd 237-2 Versions of packages systemd suggests: ii policykit-10.113-6 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.130 ii udev 237-2 -- Laurent.
Bug#889900: policykit-1: write and execute memory regions
Package: policykit-1 Version: 0.113-6 Severity: normal Tags: security Dear Maintainer, the polkitd process runs with several memory zones with both write and execute permissions: # grep rwxp /proc/$(pidof polkitd)/maps 7f2638828000-7f2638838000 rwxp 00:00 0 7f263884f000-7f263885f000 rwxp 00:00 0 7f263888-7f26388a rwxp 00:00 0 This is a problem because in case of a bug in polkitd, it might be use to inject code into the process. The same problem does exist neither in Debian 9, nor in Ubuntu 17.10 nor in Fedora 27. It seems specific to Debian experimental. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages policykit-1 depends on: ii adduser3.117 ii dbus 1.12.2-1 ii libc6 2.27-0experimental0 ii libexpat1 2.2.5-3 ii libglib2.0-0 2.55.1-1 ii libmozjs185-1.01.8.5-1.0.0+dfsg-7 ii libnspr4 2:4.18-1 ii libpam-systemd 237-1 ii libpam0g 1.1.8-3.7 ii libpolkit-agent-1-00.113-6 ii libpolkit-gobject-1-0 0.113-6 ii libsystemd0237-1 policykit-1 recommends no packages. policykit-1 suggests no packages. -- Configuration Files: /etc/polkit-1/rules.d/40-debian-sudo.rules [Errno 13] Permission denied: '/etc/polkit-1/rules.d/40-debian-sudo.rules' /etc/polkit-1/rules.d/50-default.rules [Errno 13] Permission denied: '/etc/polkit-1/rules.d/50-default.rules' -- no debconf information -- Laurent.
Bug#889715: libopenmpi-dev: problem in alternatives handling
Package: libopenmpi-dev Version: 2.1.1-8 Severity: important Dear Maintainer, here is the problem: Setting up libopenmpi-dev (2.1.1-8) ... update-alternatives: error: alternative link /usr/lib/x86_64-linux-gnu/libmpi.so is already managed by mpi-x86_64-linux-gnu dpkg: error processing package libopenmpi-dev (--configure): installed libopenmpi-dev package post-installation script subprocess returned error exit status 2 dpkg: dependency problems prevent configuration of mpi-default-dev: mpi-default-dev depends on libopenmpi-dev; however: Package libopenmpi-dev is not configured yet. dpkg: error processing package mpi-default-dev (--configure): -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libopenmpi-dev depends on: ii libc6 2.27-0experimental0 ii libhwloc-dev2.0.0~rc2-2 ii libhwloc5 1.11.9-1 ii libibverbs-dev 16.1-2 ii libopenmpi2 2.1.1-8 ii openmpi-common 2.1.1-8 libopenmpi-dev recommends no packages. Versions of packages libopenmpi-dev suggests: pn openmpi-doc -- no debconf information -- Laurent.
Bug#889713: ruby-soap4r: problem with apt-listbugs: warning: constant ::Fixnum is deprecated
Package: ruby-soap4r Version: 2.0.5-3 Severity: normal Dear Maintainer, here is the problem: Retrieving bug reports... 0% /usr/lib/ruby/vendor_ruby/soap/mapping/encodedregistry.rb:150: warning: constant ::Fixnum is deprecated /usr/lib/ruby/vendor_ruby/soap/mapping/encodedregistry.rb:216: warning: constant ::Fixnum is deprecated Retrieving bug reports... Done -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-soap4r depends on: ii ruby 1:2.5~1000grau ruby-soap4r recommends no packages. ruby-soap4r suggests no packages. -- no debconf information -- Laurent.
Bug#889655: libbeansbinding-java-doc: extraneous doc-base file
Package: libbeansbinding-java-doc Version: 1.2.1-3 Severity: normal Dear Maintainer, after each package installation, I see the following error message: Processing 1 removed doc-base file, 4 added doc-base files... Error while merging /usr/share/doc-base/libbeansbinding-java-doc with /usr/share/doc-base/libbeansbinding-java-doc-javadoc: format html already defined. This comes from the fact that /usr/share/doc-base/libbeansbinding-java-doc and /usr/share/doc-base/libbeansbinding-java-doc-javadoc contain almost the same content and point to the same HTML files. One of those 2 files should probably be removed. $ cat /usr/share/doc-base/libbeansbinding-java-doc Document: libbeansbinding-java-doc Title: Beans Binding (JSR 295) API Author: Sun Microsystems, Inc. Abstract: This is the API documentation for Beans Binding (JSR 295). Section: Programming/Java Format: HTML Index: /usr/share/doc/libbeansbinding-java-doc/api/index.html Files: /usr/share/doc/libbeansbinding-java-doc/api/*.html $ cat /usr/share/doc-base/libbeansbinding-java-doc-javadoc Document: libbeansbinding-java-doc Title: API JavaDoc for libbeansbinding-java-doc Author: The authors of libbeansbinding-java-doc Abstract: This is the API JavaDoc for libbeansbinding-java-doc Section: Programming/Java Format: HTML Index: /usr/share/doc/libbeansbinding-java-doc/api Files: /usr/share/doc/libbeansbinding-java-doc/api/*.html -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information -- Laurent.
Bug#889651: ruby-debian: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument
Package: ruby-debian Version: 0.3.9+b7 Severity: normal Dear Maintainer, after most package installations, I see the following error messages: Processing 1 removed doc-base file, 4 added doc-base files... /usr/lib/ruby/vendor_ruby/debian.rb:223: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:224: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:227: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:230: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:233: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:236: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:348: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:557: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:577: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:578: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:743: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:753: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:763: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:772: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:799: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument /usr/lib/ruby/vendor_ruby/debian.rb:1004: warning: parentheses after method name is interpreted as an argument list, not a decomposed argument -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-debian depends on: ii libapt-pkg5.0 1.6~alpha7 ii libc6 2.27-0experimental0 ii libgcc11:8-20180130-1 ii libgmp10 2:6.1.2+dfsg-2 ii libruby2.3 2.3.6-2 ii libruby2.5 2.5.0-4 ii libstdc++6 8-20180130-1 ii ruby 1:2.5~1000grau ruby-debian recommends no packages. ruby-debian suggests no packages. -- no debconf information -- Laurent.
Bug#889650: libsvnclientadapter-java-doc: extraneous doc-base file
Package: libsvnclientadapter-java-doc Version: 1.10.12-1 Severity: normal Dear Maintainer, after each package installation, I see the following error message: Processing 1 removed doc-base file, 4 added doc-base files... Error while merging /usr/share/doc-base/libsvnclientadapter-java-doc with /usr/share/doc-base/libsvnclientadapter-java-doc-javadoc: format html already defined. This comes from the fact that /usr/share/doc-base/libsvnclientadapter-java-doc and /usr/share/doc-base/libsvnclientadapter-java-doc-javadoc contain almost the same content and point to the same HTML files. One of those 2 files should probably be removed. $ cat /usr/share/doc-base/libsvnclientadapter-java-doc Document: libsvnclientadapter-java-doc Title: SVNClientAdapter API Author: svnClientAdapter project and others. Abstract: This is the API documentation for SVNClientAdapter. Section: Programming/Java Format: HTML Index: /usr/share/doc/libsvnclientadapter-java-doc/api/index.html Files: /usr/share/doc/libsvnclientadapter-java-doc/api/*.html $ cat /usr/share/doc-base/libsvnclientadapter-java-doc-javadoc Document: libsvnclientadapter-java-doc Title: API JavaDoc for libsvnclientadapter-java-doc Author: The authors of libsvnclientadapter-java-doc Abstract: This is the API JavaDoc for libsvnclientadapter-java-doc Section: Programming/Java Format: HTML Index: /usr/share/doc/libsvnclientadapter-java-doc/api Files: /usr/share/doc/libsvnclientadapter-java-doc/api/*.html -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information -- Laurent.
Bug#875637: iipimage-server: Wrong configuration file /etc/apache2/mods-available/iipsrv.conf
Hi, this bug is still there: Package: iipimage-server Version: 1.0-2 apache2_reload: apache2: Syntax error on line 147 of /etc/apache2/apache2.conf: Syntax error on line 20 of /etc/apache2/mods-enabled/iipsrv.conf: Expected but saw -- Laurent.
Bug#878082: python3-pip: TypeError: unorderable types: Version() > SetuptoolsVersion()
Package: python3-pip Version: 9.0.1-2 Severity: normal Dear Maintainer, here is the problem: $ pip3 list --outdated DEPRECATION: The default format will switch to columns in the future. You can use --format=(legacy|columns) (or define a format=(legacy|columns) in your pip.conf under the [list] section) to disable this warning. Exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 215, in main status = self.run(options, args) File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 157, in run packages = self.get_outdated(packages, options) File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 168, in get_outdated dist for dist in self.iter_packages_latest_infos(packages, options) File "/usr/lib/python3/dist-packages/pip/commands/list.py", line 169, in if dist.latest_version > dist.parsed_version TypeError: unorderable types: Version() > SetuptoolsVersion() According to comments in this bug report: https://github.com/pypa/pip/issues/3057 the problem comes from Debian modifications to pip. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-pip depends on: ii ca-certificates 20170717 ii python-pip-whl 9.0.1-2 ii python3 3.5.3-3 Versions of packages python3-pip recommends: ii build-essential 12.4 ii python3-dev 3.5.3-3 ii python3-setuptools 36.2.7-2 ii python3-wheel 0.29.0-2 python3-pip suggests no packages. -- no debconf information -- Laurent.
Bug#875468: gssproxy: ordering cycle during boot
Package: gssproxy Version: 0.7.0-2 Severity: important Dear Maintainer, here is an error message I see on my system during boot: sept. 11 16:27:48 hostname systemd[1]: gssproxy.service: Found ordering cycle on gssproxy.service/start sept. 11 16:27:48 hostname systemd[1]: gssproxy.service: Found dependency on remote-fs.target/start sept. 11 16:27:48 hostname systemd[1]: gssproxy.service: Found dependency on remote-fs-pre.target/start sept. 11 16:27:48 hostname systemd[1]: gssproxy.service: Found dependency on nfs-client.target/start sept. 11 16:27:48 hostname systemd[1]: gssproxy.service: Found dependency on rpc-svcgssd.service/start sept. 11 16:27:48 hostname systemd[1]: gssproxy.service: Found dependency on gssproxy.service/start sept. 11 16:27:48 hostname systemd[1]: gssproxy.service: Breaking ordering cycle by deleting job remote-fs.target/start sept. 11 16:27:48 hostname systemd[1]: remote-fs.target: Job remote-fs.target/start deleted to break ordering cycle starting with gssproxy.service/start -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gssproxy depends on: ii libc6 2.25-0experimental3 ii libgssapi-krb5-2 1.15.1-2 ii libgssrpc41.15.1-2 ii libini-config50.6.0-1 ii libk5crypto3 1.15.1-2 ii libkrb5-3 1.15.1-2 ii libpopt0 1.16-10+b2 ii libref-array1 0.6.0-1 ii libselinux1 2.7~rc2-1 ii libverto1 0.2.4-2.1 gssproxy recommends no packages. gssproxy suggests no packages. -- no debconf information -- Laurent.
Bug#857081: linux-image-rt-amd64-unsigned: NOHZ: local_softirq_pending 80
Hi, this bug is still there in kernel 4.11.6 : $ uname -a Linux irancy.iut2.upmf-grenoble.fr 4.11.0-1-rt-amd64 #1 SMP PREEMPT RT Debian 4.11.6-1 (2017-06-19) x86_64 GNU/Linux $ dmesg [...] [690935.587688] NOHZ: local_softirq_pending 80 When this error occurred the system was accessing a btrfs filesystem on a USB disk. Might the problem be in btrfs? -- Laurent.
Bug#865285: sntp: Cannot open KoD db file /var/db/ntp-kod: No such file or directory
Package: sntp Version: 1:4.2.8p10+dfsg-4 Severity: normal Dear Maintainer, here is the problem: # sntp pool.ntp.org sntp 4.2.8p10@1.3728-o (1) kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or directory 2017-06-20 11:05:44.073428 (-0100) +0.006359 +/- 0.025993 pool.ntp.org 62.210.211.218 s2 no-leap -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-rt-amd64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages sntp depends on: ii libc6 2.24-12 ii libopts25 1:5.18.12-3 ii libssl1.1 1.1.0f-3 sntp recommends no packages. sntp suggests no packages. -- no debconf information -- Laurent.
Bug#857081: linux-image-4.9.0-2-rt-amd64-unsigned: NOHZ: local_softirq_pending 80
Hi, this bug is still there in kernel 4.9.30 : $ uname -a Linux irancy.iut2.upmf-grenoble.fr 4.9.0-3-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.30-1 (2017-06-04) x86_64 GNU/Linux $ dmesg [...] [187203.776023] NOHZ: local_softirq_pending 80 -- Laurent.
