Processed: reopening 689962, tagging 689962, severity of 689962 is wishlist, forcibly merging 689962 989153
Processing commands for cont...@bugs.debian.org:
> reopen 689962
Bug #689962 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-3.2.0-4-amd64: Compile with CONFIG_VIRTIO_CONSOLE=y
Bug reopened
Ignoring request to alter fixed versions of bug #689962 to the same values
previously set
> tags 689962 - moreinfo
Bug #689962 [src:linux] linux-image-3.2.0-4-amd64: Compile with
CONFIG_VIRTIO_CONSOLE=y
Removed tag(s) moreinfo.
> severity 689962 wishlist
Bug #689962 [src:linux] linux-image-3.2.0-4-amd64: Compile with
CONFIG_VIRTIO_CONSOLE=y
Ignoring request to change severity of Bug 689962 to the same value.
> forcemerge 689962 989153
Bug #689962 [src:linux] linux-image-3.2.0-4-amd64: Compile with
CONFIG_VIRTIO_CONSOLE=y
Bug #689962 [src:linux] linux-image-3.2.0-4-amd64: Compile with
CONFIG_VIRTIO_CONSOLE=y
Marked as found in versions linux/5.10.38-1.
Bug #989153 [src:linux] linux-image-amd64: Pleset set CONFIG_VIRTIO_CONSOLE=y
to boot with virtio console
Marked as found in versions linux/3.2.30-1.
Merged 689962 989153
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
689962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689962
989153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 689962
Processing commands for cont...@bugs.debian.org:
> unarchive 689962
Bug #689962 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-3.2.0-4-amd64: Compile with CONFIG_VIRTIO_CONSOLE=y
Unarchived Bug 689962
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
689962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 989152 in 5.10.38-1
Processing commands for cont...@bugs.debian.org: > found 989152 5.10.38-1 Bug #989152 [src:linux] linux: Mouse wheel support is broken after resume Marked as found in versions linux/5.10.38-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 989152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 989153 to src:linux, severity of 989153 is wishlist
Processing commands for cont...@bugs.debian.org: > reassign 989153 src:linux 5.10.38-1 Bug #989153 [linux-image-amd64] linux-image-amd64: Pleset set CONFIG_VIRTIO_CONSOLE=y to boot with virtio console Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/5.10.38+1. Ignoring request to alter fixed versions of bug #989153 to the same values previously set Bug #989153 [src:linux] linux-image-amd64: Pleset set CONFIG_VIRTIO_CONSOLE=y to boot with virtio console Marked as found in versions linux/5.10.38-1. > severity 989153 wishlist Bug #989153 [src:linux] linux-image-amd64: Pleset set CONFIG_VIRTIO_CONSOLE=y to boot with virtio console Severity set to 'wishlist' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 989153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
klibc_2.0.8-6.1_source.changes ACCEPTED into unstable
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Thu, 27 May 2021 00:12:10 +0200
Source: klibc
Architecture: source
Version: 2.0.8-6.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Thorsten Glaser
Closes: 943425
Changes:
klibc (2.0.8-6.1) unstable; urgency=medium
.
* Non-maintainer upload.
* {set,long}jmp [s390x]: save/restore the correct FPU registers
(f8‥f15 not f1/f3/f5/f7) (Closes: #943425)
Checksums-Sha1:
8f6d258158fe0e99bc25df3ae74e0fdd6e757b7a 2155 klibc_2.0.8-6.1.dsc
7c8d56187e99acee5c4b279ac320a2b8ab241376 25128 klibc_2.0.8-6.1.debian.tar.xz
Checksums-Sha256:
962fa58feba82f33095b2b990b2692c73bf39e18da954cae35e58e20cdc007a8 2155
klibc_2.0.8-6.1.dsc
8de7dde6d6c192f0f2a7a3c7a14181618f21e6fa5a6e7011ee1d0db057ee6a4a 25128
klibc_2.0.8-6.1.debian.tar.xz
Files:
d9b64d57ddc0b4dc1b4f0b6767286c74 2155 libs optional klibc_2.0.8-6.1.dsc
2f1894721d61245d1864f9e751782370 25128 libs optional
klibc_2.0.8-6.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８ ☕☂☄
iQIcBAEBCQAGBQJgrslWAAoJEHa1NLLpkAfgH64QAIOGObjrl1fuw+m+/B6UbBvm
4cly8oI399hX+zjPvxFFPcq0MQS8Ggb9Z9Q3zpT+YHkSqJPs1kIBr0DNq/dXMexY
NiEp6KiKClk2tNfI1xmbISX60AecaXG/k40DiqvOkk28Oxh78u6Kip1OEp3ABY60
Le1XfgC7zbA477kmHJlwchoOJx3THVBcPcqERzc4UDHv+BnhvTC1kfSwc6EZjP/2
dIti6PumphrZUEcFIXDc5hOO48Qn4cuK32MlV3QpiBSPOJrr1rLRBXgxwl4o7kGD
p+CR0NEPq6nVzysoluBMUEltV9+kRJLq0fMaESE8KhvKWK1ZmhZzpSWYQiMKP4pU
1oP7SXfnt4UY7NVOHfxONLOsAPyLop+//uMNRDwoL9ko8t66zWdG5agZWmmgIP50
FZw9esh+vhqpH2eLaIrTn3ZBRpUh1GPHHw9jBuGsKEb6qmkt2R5NJZy4EXH5HI5u
a/5ryfEWvbuwq2/QBbBrurItuS6A9LCmszB3BYdbgDvhq4sl/+ODw7vTYeo8NkGm
kIX6MPOwlt/M4z4XR2uzivDhXMc5bXzubGcHUPfiO7R8r61bfTU7uSJDZaWKd56V
d+MqnPV7Y7QA6pReALDKgkn8wczuU7nvYksqUVkDEWVuRm5SR1KEMNqLY9BED9u7
bG1rgv11xgcHdwSmYk7q
=svUl
-END PGP SIGNATURE-
Thank you for your contribution to Debian.
Processing of klibc_2.0.8-6.1_source.changes
klibc_2.0.8-6.1_source.changes uploaded successfully to localhost along with the files: klibc_2.0.8-6.1.dsc klibc_2.0.8-6.1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#943425: klibc: debdiff for NMU 2.0.8-6.1
Hi Ben, maks,
please find attached the debdiff fixing this release-critical bug.
I’ve uploaded to DELAYED/0 per devref.
Please integrate this into the next maintainer upload.
I’ve only added the patch for the wrong registers being saved,
not the one fixing sig{set,long}jmp because, apparently, klibc
documents its standard violation for these two functions, so
that’s best dealt with upstream. I’ll upload mksh using the
regular {set,long}jmp functions instead where signals are to
not be saved once klibc is built on all architectures.
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2diff -Nru klibc-2.0.8/debian/changelog klibc-2.0.8/debian/changelog
--- klibc-2.0.8/debian/changelog2021-04-30 03:05:23.0 +0200
+++ klibc-2.0.8/debian/changelog2021-05-27 00:12:10.0 +0200
@@ -1,3 +1,11 @@
+klibc (2.0.8-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * {set,long}jmp [s390x]: save/restore the correct FPU registers
+(f8‥f15 not f1/f3/f5/f7) (Closes: #943425)
+
+ -- Thorsten Glaser Thu, 27 May 2021 00:12:10 +0200
+
klibc (2.0.8-6) unstable; urgency=medium
* Upload to unstable
diff -Nru
klibc-2.0.8/debian/patches/0041-klibc-set-long-jmp-s390x-save-restore-the-correct-re.patch
klibc-2.0.8/debian/patches/0041-klibc-set-long-jmp-s390x-save-restore-the-correct-re.patch
---
klibc-2.0.8/debian/patches/0041-klibc-set-long-jmp-s390x-save-restore-the-correct-re.patch
1970-01-01 01:00:00.0 +0100
+++
klibc-2.0.8/debian/patches/0041-klibc-set-long-jmp-s390x-save-restore-the-correct-re.patch
2021-05-27 00:11:57.0 +0200
@@ -0,0 +1,57 @@
+Description: {set,long}jmp [s390x]: save/restore the correct registers
+ The s390x ABI actually has FPU registers f8‥f15, not f1/f3/f5/f7,
+ to be saved. (Closes: Debian #943425)
+Author: mirabilos
+Forwarded: https://lists.zytor.com/archives/klibc/2021-May/004620.html
+
+--- a/usr/include/arch/s390/klibc/archsetjmp.h
b/usr/include/arch/s390/klibc/archsetjmp.h
+@@ -16,7 +16,7 @@ struct __jmp_buf {
+
+ struct __jmp_buf {
+ uint64_t __gregs[10]; /* general registers r6-r15 */
+- uint64_t __fpregs[4]; /* fp registers f1, f3, f5, f7 */
++ uint64_t __fpregs[8]; /* fp registers f8-f15 */
+ };
+
+ #endif /* __s390x__ */
+--- a/usr/klibc/arch/s390/setjmp.S
b/usr/klibc/arch/s390/setjmp.S
+@@ -38,10 +38,14 @@ longjmp:
+
+ setjmp:
+ stmg%r6,%r15,0(%r2) # save all general registers
+- std %f1,80(%r2) # save fp registers f4 and f6
+- std %f3,88(%r2)
+- std %f5,96(%r2)
+- std %f7,104(%r2)
++ std %f8,80(%r2) # save fp registers f8 to f15
++ std %f9,88(%r2)
++ std %f10,96(%r2)
++ std %f11,104(%r2)
++ std %f12,112(%r2)
++ std %f13,120(%r2)
++ std %f14,128(%r2)
++ std %f15,136(%r2)
+ lghi%r2,0 # return 0
+ br %r14
+
+@@ -54,10 +58,14 @@ setjmp:
+ longjmp:
+ lgr %r1,%r2 # jmp_buf
+ lgr %r2,%r3 # return value
+- ld %f7,104(%r1)# restore all saved registers
+- ld %f5,96(%r1)
+- ld %f3,88(%r1)
+- ld %f1,80(%r1)
++ ld %f15,136(%r1) # restore all saved registers
++ ld %f14,128(%r1)
++ ld %f13,120(%r1)
++ ld %f12,112(%r1)
++ ld %f11,104(%r1)
++ ld %f10,96(%r1)
++ ld %f9,88(%r1)
++ ld %f8,80(%r1)
+ lmg %r6,%r15,0(%r1)
+ br %r14# return to restored address
+
diff -Nru klibc-2.0.8/debian/patches/series klibc-2.0.8/debian/patches/series
--- klibc-2.0.8/debian/patches/series 2021-04-30 02:38:31.0 +0200
+++ klibc-2.0.8/debian/patches/series 2021-05-27 00:09:21.0 +0200
@@ -10,3 +10,4 @@
0037-klibc-calloc-Fail-if-multiplication-overflows.patch
0039-klibc-cpio-Fix-possible-integer-overflow-on-32-bit-s.patch
0040-klibc-cpio-Fix-possible-crash-on-64-bit-systems.patch
+0041-klibc-set-long-jmp-s390x-save-restore-the-correct-re.patch
Bug#943425: marked as done (klibc: [s390x] setjmp/longjmp do not save/restore all registers in use)
Your message dated Wed, 26 May 2021 22:33:32 +
with message-id
and subject line Bug#943425: fixed in klibc 2.0.8-6.1
has caused the Debian Bug report #943425,
regarding klibc: [s390x] setjmp/longjmp do not save/restore all registers in use
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
943425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libklibc-dev
Version: 2.0.7-1
When building mksh against klibc on s390x, one testcase positively fails:
FAIL ../../check.t:funsub-2
Description:
You can now reliably use local and return in funsubs
(not exit though)
unexpected exit status 11 (signal 11), expected 0
unexpected stdout - got too little output
wanted:
1:ya x2,2,0.
2:ya x2,1,0.
3:ya,1,3.
got:
1:ya x2,2,0.
2:ya x2,1,0.
I’ll need to track this down later, filing the bug to remember.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
**
Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.
Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.
**
--- End Message ---
--- Begin Message ---
Source: klibc
Source-Version: 2.0.8-6.1
Done: Thorsten Glaser
We believe that the bug you reported is fixed in the latest version of
klibc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 943...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thorsten Glaser (supplier of updated klibc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Format: 1.8
Date: Thu, 27 May 2021 00:12:10 +0200
Source: klibc
Architecture: source
Version: 2.0.8-6.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Thorsten Glaser
Closes: 943425
Changes:
klibc (2.0.8-6.1) unstable; urgency=medium
.
* Non-maintainer upload.
* {set,long}jmp [s390x]: save/restore the correct FPU registers
(f8‥f15 not f1/f3/f5/f7) (Closes: #943425)
Checksums-Sha1:
8f6d258158fe0e99bc25df3ae74e0fdd6e757b7a 2155 klibc_2.0.8-6.1.dsc
7c8d56187e99acee5c4b279ac320a2b8ab241376 25128 klibc_2.0.8-6.1.debian.tar.xz
Checksums-Sha256:
962fa58feba82f33095b2b990b2692c73bf39e18da954cae35e58e20cdc007a8 2155
klibc_2.0.8-6.1.dsc
8de7dde6d6c192f0f2a7a3c7a14181618f21e6fa5a6e7011ee1d0db057ee6a4a 25128
klibc_2.0.8-6.1.debian.tar.xz
Files:
d9b64d57ddc0b4dc1b4f0b6767286c74 2155 libs optional klibc_2.0.8-6.1.dsc
2f1894721d61245d1864f9e751782370 25128 libs optional
klibc_2.0.8-6.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (MirBSD)
Comment: ☃ ЦΤℱ—８ ☕☂☄
iQIcBAEBCQAGBQJgrslWAAoJEHa1NLLpkAfgH64QAIOGObjrl1fuw+m+/B6UbBvm
4cly8oI399hX+zjPvxFFPcq0MQS8Ggb9Z9Q3zpT+YHkSqJPs1kIBr0DNq/dXMexY
NiEp6KiKClk2tNfI1xmbISX60AecaXG/k40DiqvOkk28Oxh78u6Kip1OEp3ABY60
Le1XfgC7zbA477kmHJlwchoOJx3THVBcPcqERzc4UDHv+BnhvTC1kfSwc6EZjP/2
dIti6PumphrZUEcFIXDc5hOO48Qn4cuK32MlV3QpiBSPOJrr1rLRBXgxwl4o7kGD
p+CR0NEPq6nVzysoluBMUEltV9+kRJLq0fMaESE8KhvKWK1ZmhZzpSWYQiMKP4pU
1oP7SXfnt4UY7NVOHfxONLOsAPyLop+//uMNRDwoL9ko8t66zWdG5agZWmmgIP50
FZw9esh+vhqpH2eLaIrTn3ZBRpUh1GPHHw9jBuGsKEb6qmkt2R5NJZy4EXH5HI5u
a/5ryfEWvbuwq2/QBbBrurItuS6A9LCmszB3BYdbgDvhq4sl/+ODw7vTYeo8NkGm
kIX6MPOwlt/M4z4XR2uzivDhXMc5bXzubGcHUPfiO7R8r61bfTU7uSJDZaWKd56V
d+MqnPV7Y7QA6pReALDKgkn8wczuU7nvYksqUVkDEWVuRm5SR1KEMNqLY9BED9u7
bG1rgv11xgcHdwSmYk7q
=svUl
-END PGP SIGNATURE End Message ---
Bug#989153: linux-image-amd64: Pleset set CONFIG_VIRTIO_CONSOLE=y to boot with virtio console
Package: linux-image-amd64 Version: 5.10.38-1 Severity: normal Dear Maintainer, Please compile virtio serial as built-in (CONFIG_VIRTIO_CONSOLE=y) to be able to boot with serial=hvc0
linux-signed-i386_5.10.38+1_source.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 20 May 2021 07:47:35 +0200 Source: linux-signed-i386 Architecture: source Version: 5.10.38+1 Distribution: sid Urgency: medium Maintainer: Debian Kernel Team Changed-By: Salvatore Bonaccorso Changes: linux-signed-i386 (5.10.38+1) unstable; urgency=medium . * Sign kernel from linux 5.10.38-1 . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.29 - [armhf] bus: ti-sysc: Fix warning on unbind if reset is not deasserted - [x86] platform/x86: intel-hid: Support Lenovo ThinkPad X1 Tablet Gen 2 - [amd64] bpf, x86: Use kvmalloc_array instead kmalloc_array in bpf_jit_comp - net/mlx5e: Enforce minimum value check for ICOSQ size - mISDN: fix crash in fritzpci - mac80211: Check crypto_aead_encrypt for errors - mac80211: choose first enabled channel for monitor - [arm64] drm/msm/dsi_pll_7nm: Fix variable usage for pll_lockdet_rate - [arm64] drm/msm/adreno: a5xx_power: Don't apply A540 lm_setup to other GPUs - [arm64] drm/msm: Ratelimit invalid-fence message - netfilter: conntrack: Fix gre tunneling over ipv6 - netfilter: nftables: skip hook overlap logic if flowtable is stale - [x86] platform/x86: thinkpad_acpi: Allow the FnLock LED to change state - [arm64] drm/msm/disp/dpu1: icc path needs to be set before dpu runtime resume - block: clear GD_NEED_PART_SCAN later in bdev_disk_changed - [x86] platform/x86: intel_pmc_core: Ignore GBE LTR on Tiger Lake platforms - [arm64] ptp_qoriq: fix overflow in ptp_qoriq_adjfine() u64 calcalation - scsi: target: pscsi: Clean up after failure in pscsi_map_sg() - [ia64] mca: allocate early mca with GFP_ATOMIC - [ia64] fix format strings for err_inject - cifs: revalidate mapping when we open files for SMB1 POSIX - cifs: Silently ignore unknown oplock break handle - io_uring: fix timeout cancel return code - math: Export mul_u64_u64_div_u64 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.30 - ALSA: aloop: Fix initialization of controls - ALSA: hda/realtek: Fix speaker amp setup on Acer Aspire E1 - ALSA: hda/conexant: Apply quirk for another HP ZBook G5 model - [x86] ASoC: intel: atom: Stop advertising non working S24LE support - nfc: fix refcount leak in llcp_sock_bind() (CVE-2020-25670) - nfc: fix refcount leak in llcp_sock_connect() (CVE-2020-25671) - nfc: fix memory leak in llcp_sock_connect() (CVE-2020-25672) - nfc: Avoid endless loops caused by repeated llcp_sock_connect() - selinux: make nslot handling in avtab more robust - selinux: fix cond_list corruption when changing booleans - selinux: fix race between old and new sidtab - xen/evtchn: Change irq_info lock to raw_spinlock_t - net: ipv6: check for validity before dereferencing cfg->fc_nlinfo.nlh - [x86] drm/i915: Fix invalid access to ACPI _DSM objects - [amd64] IB/hfi1: Fix probe time panic when AIP is enabled with a buggy BIOS - LOOKUP_MOUNTPOINT: we are cleaning "jumped" flag too late - [ia64] fix user_stack_pointer() for ptrace() - ocfs2: fix deadlock between setattr and dio_end_io_write - fs: direct-io: fix missing sdio->boundary - ethtool: fix incorrect datatype in set_eee ops - of: property: fw_devlink: do not link ".*,nr-gpios" - [armhf] dts: turris-omnia: configure LED[2]/INTn pin as interrupt pin - batman-adv: initialize "struct batadv_tvlv_tt_vlan_data"->reserved field - ice: Continue probe on link/PHY errors - ice: Increase control queue timeout - ice: prevent ice_open and ice_stop during reset - ice: fix memory allocation call - ice: remove DCBNL_DEVRESET bit from PF state - ice: Fix for dereference of NULL pointer - ice: Use port number instead of PF ID for WoL - ice: Cleanup fltr list in case of allocation issues - iwlwifi: pcie: properly set LTR workarounds on 22000 devices - ice: fix memory leak of aRFS after resuming from suspend - net: hso: fix null-ptr-deref during tty device unregistration - bpf: Enforce that struct_ops programs be GPL-only - bpf: link: Refuse non-O_RDWR flags in BPF_OBJ_GET - ethernet/netronome/nfp: Fix a use after free in nfp_bpf_ctrl_msg_rx - bpf: Refcount task stack in bpf_get_task_stack - bpf, sockmap: Fix sk->prot unhash op reset - bpf, sockmap: Fix incorrect fwd_alloc accounting - net: ensure mac header is set in virtio_net_hdr_to_skb() - i40e: Fix sparse warning: missing error code 'err' - i40e: Fix sparse error: 'vsi->netdev' could be null - i40e: Fix sparse error: uninitialized symbol 'ring' - i40e: Fix sparse errors in i40e_txrx.c - net: sched: sch_teql: fix null-pointer dereference - net: sched: fix action overwrite reference counting - nl80211:
Bug#989152: linux: Mouse wheel support is broken after resume
Source: linux Version: Mouse wheel behaviour is broken after resume Severity: normal Dear Maintainer, I've remarked that on a specific laptop the mouse wheel function is not restored after resume. This is a regression that has been introduced between Buster and Bullseye, and only occurs on one of my hosts. Laptop model : Dell Latitude e6540 Mouse model : Microsoft Intellimouse 4500 Desktop environment : KDE Steps to reproduce : DO : boot the computer and open KDE DO : open whatever application with a scrollbar and use the mouse scroll wheel EXPECT : the scrolling works. DO : suspend the computer to RAM for 5 minutes DO : resume your activity DO : open whatever application with a scrollbar and use the mouse scroll wheel EXPECT : the scrolling works. ACTUAL : the scrolling does not work. Workaround : unplug and plug the mouse, or use a tool like resetmsmice (it would be great to include it in the archive : https://github.com/paulrichards321/resetmsmice ) -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
Bug#889817: linux: kernel does not always provide a heap [alpha arm64 mips64el ppc64el ppc64 s390x sparc64]
Hi Aurelien,
On Wed, May 26, 2021 at 06:09:45PM +0200, Aurelien Jarno wrote:
> control: fixed 889817 5.2.6-1
> control: fixed 889817 4.19.87-1
>
> Hi Salvatore,
>
> On 2021-05-24 08:31, Salvatore Bonaccorso wrote:
> > Source: linux
> > Source-Version: 5.10.38-1
> >
> > Hi,
> >
> > On Wed, Feb 07, 2018 at 12:37:44PM +0100, Aurelien Jarno wrote:
> > > Source: linux
> > > Version: 4.14.13-1
> > > Severity: normal
> > > Tags: upstream
> > >
> > > When ASLR is enabled (which is the default), the Linux kernel on at
> > > least alpha, arm64, mips64el, ppc64el, ppc64, s390x and sparc64 might
> > > not provide a heap to the program. This is the case for example when
> > > the program is run through the program interpreter ld.so. This happens
> > > with different probability depending on the architecture. This causes
> > > issues with GLIBC tunables support, which needs to be able to reserve
> > > a few hundred bytes of memory through brk. This is reproducible with
> > > at least kernel 4.9 and 4.15, and it's likely that the issue has always
> > > been there.
> > >
> > > The following script, based on one from James Cowgill, shows the issue:
> > >
> > > #!/bin/bash
> > > export LC_ALL=C
> > >
> > > interp=$(readelf --headers /bin/cat | grep 'Requesting program
> > > interpreter' | sed -e 's/.*: //' -e 's/]//')
> > >
> > > for i in {1..1}
> > > do
> > > OUT=$($interp /bin/cat /proc/self/maps)
> > > if [[ $OUT != *heap* ]]
> > > then
> > > echo -n F
> > > echo "$OUT"
> > > else
> > > echo -n .
> > > fi
> > > done
> > >
> > > A workaround is to set /proc/sys/kernel/randomize_va_space to 1.
> >
> > As discussed on IRC, I was not able to trigger this behaviour with
> > 4.19.181-1 on amdahl (arm64), zelenka (s390x) or plummer (ppc64el). So
> > guess the issue has been fixed in meanwhile somewhere.
> >
> > Not sure it is worth trying to bisect and finding the fixing
> > commit(s).
>
> I have found that the problem has been fixed in that upstream commit:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbdc6076d2e5d07db44e74c11b01a3e27ab90b32
>
> This commit went into kernel 5.2, and was later backported in kernel
> 4.19.75.
>
> > But for now closing with all recent versions in supported branches.
>
> This mail should update the version in the BTS to the corresponding
> Debian version.
Very nice, thanks a lot for digging deeper into it to find the fixing
commit!
Regards,
Salvatore
Bug#989143: initramfs-tools: doesn’t actually compress with zstd
Package: initramfs-tools Version: 0.140 Severity: normal Hey. Just noted by coincidence, that even though I have set: COMPRESS=zstd and zstd is installed and even runs (seen in e.g. top utility) when running update-initramfs -u the files are in the end nevertheless plain cpio: file /boot/initrd.img-5.10.0-7-amd64 /boot/initrd.img-5.10.0-7-amd64: ASCII cpio archive (SVR4 with no CRC) Cheers, Chris. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 24M May 14 13:47 /boot/initrd.img-5.10.0-6-amd64 -rw-r--r-- 1 root root 24M May 26 19:21 /boot/initrd.img-5.10.0-7-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-5.10.0-7-amd64 root=/dev/mapper/system ro rootflags=subvol=root random.trust_cpu=off luks.crypttab=no -- /proc/filesystems btrfs fuseblk -- /etc/initramfs-tools/modules usb-storage xhci-hcd xhci-pci ehci-hcd ehci-pci uhci-hcd btrfs -- /etc/initramfs-tools/initramfs.conf MODULES=dep BUSYBOX=auto KEYMAP=n COMPRESS=zstd DEVICE= NFSROOT=auto RUNSIZE=10% FSTYPE=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] unused devices: -- /sys/block dm-0 loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 sda /usr/share/initramfs-tools/hooks: btrfs cryptgnupg cryptgnupg-sc cryptkeyctl cryptopensc cryptpassdev cryptroot cryptroot-unlock dmsetup fsck fuse intel_microcode keymap klibc-utils kmod lvm2 mdadm nbd ntfs_3g reiserfsprogs resume thermal thin-provisioning-tools udev v86d xfs zz-busybox -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages initramfs-tools depends on: ii initramfs-tools-core 0.140 ii linux-base4.6 initramfs-tools recommends no packages. Versions of packages initramfs-tools suggests: ii bash-completion 1:2.11-2 -- no debconf information
Processed: Re: Bug#889817: linux: kernel does not always provide a heap [alpha arm64 mips64el ppc64el ppc64 s390x sparc64]
Processing control commands:
> fixed 889817 5.2.6-1
Bug #889817 {Done: Salvatore Bonaccorso } [src:linux] linux:
kernel does not always provide a heap [alpha arm64 mips64el ppc64el ppc64 s390x
sparc64]
Marked as fixed in versions linux/5.2.6-1.
> fixed 889817 4.19.87-1
Bug #889817 {Done: Salvatore Bonaccorso } [src:linux] linux:
kernel does not always provide a heap [alpha arm64 mips64el ppc64el ppc64 s390x
sparc64]
Marked as fixed in versions linux/4.19.87-1.
--
889817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#889817: linux: kernel does not always provide a heap [alpha arm64 mips64el ppc64el ppc64 s390x sparc64]
control: fixed 889817 5.2.6-1
control: fixed 889817 4.19.87-1
Hi Salvatore,
On 2021-05-24 08:31, Salvatore Bonaccorso wrote:
> Source: linux
> Source-Version: 5.10.38-1
>
> Hi,
>
> On Wed, Feb 07, 2018 at 12:37:44PM +0100, Aurelien Jarno wrote:
> > Source: linux
> > Version: 4.14.13-1
> > Severity: normal
> > Tags: upstream
> >
> > When ASLR is enabled (which is the default), the Linux kernel on at
> > least alpha, arm64, mips64el, ppc64el, ppc64, s390x and sparc64 might
> > not provide a heap to the program. This is the case for example when
> > the program is run through the program interpreter ld.so. This happens
> > with different probability depending on the architecture. This causes
> > issues with GLIBC tunables support, which needs to be able to reserve
> > a few hundred bytes of memory through brk. This is reproducible with
> > at least kernel 4.9 and 4.15, and it's likely that the issue has always
> > been there.
> >
> > The following script, based on one from James Cowgill, shows the issue:
> >
> > #!/bin/bash
> > export LC_ALL=C
> >
> > interp=$(readelf --headers /bin/cat | grep 'Requesting program interpreter'
> > | sed -e 's/.*: //' -e 's/]//')
> >
> > for i in {1..1}
> > do
> > OUT=$($interp /bin/cat /proc/self/maps)
> > if [[ $OUT != *heap* ]]
> > then
> > echo -n F
> > echo "$OUT"
> > else
> > echo -n .
> > fi
> > done
> >
> > A workaround is to set /proc/sys/kernel/randomize_va_space to 1.
>
> As discussed on IRC, I was not able to trigger this behaviour with
> 4.19.181-1 on amdahl (arm64), zelenka (s390x) or plummer (ppc64el). So
> guess the issue has been fixed in meanwhile somewhere.
>
> Not sure it is worth trying to bisect and finding the fixing
> commit(s).
I have found that the problem has been fixed in that upstream commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bbdc6076d2e5d07db44e74c11b01a3e27ab90b32
This commit went into kernel 5.2, and was later backported in kernel
4.19.75.
> But for now closing with all recent versions in supported branches.
This mail should update the version in the BTS to the corresponding
Debian version.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
Processed: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c
Processing control commands: > retitle -1 Apple keyboard: Scan code event (EV_MSC) not generated when the > EV_KEY event is generated by hid-apple.c Bug #757356 [src:linux] Scan code event not generated for some keys of the Apple keyboard: those in applespi_fn_codes Changed Bug title to 'Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c' from 'Scan code event not generated for some keys of the Apple keyboard: those in applespi_fn_codes'. > tags -1 patch Bug #757356 [src:linux] Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c Added tag(s) patch. -- 757356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#757356: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c
Control: retitle -1 Apple keyboard: Scan code event (EV_MSC) not generated when
the EV_KEY event is generated by hid-apple.c
Control: tags -1 patch
On 2021-05-26 10:39:11 +0200, Vincent Lefevre wrote:
> And the cursor keys. Actually, all the keys corresponding to
>
> static const struct applespi_key_translation applespi_fn_codes[] = {
> { KEY_BACKSPACE, KEY_DELETE },
> { KEY_ENTER,KEY_INSERT },
> { KEY_F1, KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY },
> { KEY_F2, KEY_BRIGHTNESSUP, APPLE_FLAG_FKEY },
> { KEY_F3, KEY_SCALE, APPLE_FLAG_FKEY },
> { KEY_F4, KEY_DASHBOARD, APPLE_FLAG_FKEY },
> { KEY_F5, KEY_KBDILLUMDOWN, APPLE_FLAG_FKEY },
> { KEY_F6, KEY_KBDILLUMUP, APPLE_FLAG_FKEY },
> { KEY_F7, KEY_PREVIOUSSONG, APPLE_FLAG_FKEY },
> { KEY_F8, KEY_PLAYPAUSE, APPLE_FLAG_FKEY },
> { KEY_F9, KEY_NEXTSONG, APPLE_FLAG_FKEY },
> { KEY_F10, KEY_MUTE, APPLE_FLAG_FKEY },
> { KEY_F11, KEY_VOLUMEDOWN, APPLE_FLAG_FKEY },
> { KEY_F12, KEY_VOLUMEUP, APPLE_FLAG_FKEY },
> { KEY_RIGHT,KEY_END },
> { KEY_LEFT, KEY_HOME },
> { KEY_DOWN, KEY_PAGEDOWN },
> { KEY_UP, KEY_PAGEUP },
> { }
> };
>
> in drivers/input/keyboard/applespi.c.
>
> Just in case, in /etc/modprobe.d/hid_apple.conf, I have
>
> options hid_apple fnmode=2
> options hid_apple iso_layout=0
But since I'm using hid_apple, I should have taken
drivers/hid/hid-apple.c, which has the same kind of code:
static const struct apple_key_translation apple_fn_keys[] = {
{ KEY_BACKSPACE, KEY_DELETE },
{ KEY_ENTER,KEY_INSERT },
{ KEY_F1, KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY },
{ KEY_F2, KEY_BRIGHTNESSUP, APPLE_FLAG_FKEY },
{ KEY_F3, KEY_SCALE, APPLE_FLAG_FKEY },
{ KEY_F4, KEY_DASHBOARD, APPLE_FLAG_FKEY },
{ KEY_F5, KEY_KBDILLUMDOWN, APPLE_FLAG_FKEY },
{ KEY_F6, KEY_KBDILLUMUP, APPLE_FLAG_FKEY },
{ KEY_F7, KEY_PREVIOUSSONG, APPLE_FLAG_FKEY },
{ KEY_F8, KEY_PLAYPAUSE, APPLE_FLAG_FKEY },
{ KEY_F9, KEY_NEXTSONG, APPLE_FLAG_FKEY },
{ KEY_F10, KEY_MUTE, APPLE_FLAG_FKEY },
{ KEY_F11, KEY_VOLUMEDOWN, APPLE_FLAG_FKEY },
{ KEY_F12, KEY_VOLUMEUP, APPLE_FLAG_FKEY },
{ KEY_UP, KEY_PAGEUP },
{ KEY_DOWN, KEY_PAGEDOWN },
{ KEY_LEFT, KEY_HOME },
{ KEY_RIGHT,KEY_END },
{ }
};
In the conditions from hidinput_apple_event(), the only ones that
should match according to my settings are
if (usage->code == fn_keycode) {
and
if (fnmode) {
and these are the keys (when trans is true, for fnmode) for which I do
not get a scan code event. Said otherwise, if hidinput_apple_event()
returns 1, I do not get a scan code event. There are input_event()
calls, but I suppose that they will just generate an EV_KEY event,
and EV_MSC is the one that is missing.
Note: in hid-apple.c, apple_event() calls hidinput_apple_event(), and
one has
static struct hid_driver apple_driver = {
[...]
.event = apple_event,
[...]
};
module_hid_driver(apple_driver);
I forgot that there was
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356#35
from Daniel Lin, with a patch, in 2017. I've looked at this patch
(but have not tried it), and it adds an additional EV_MSC event
when hidinput_apple_event() has to generate an EV_KEY event. So
I confirm that should solve this issue and I'm adding the patch
tag (I don't know whether the patch needs an update, though).
--
Vincent Lefèvre - Web:
Processed: Scan code event not generated for some keys of the Apple keyboard: those in applespi_fn_codes
Processing control commands: > retitle -1 Scan code event not generated for some keys of the Apple keyboard: > those in applespi_fn_codes Bug #757356 [src:linux] Scan code event not generated for some keys of the Apple keyboard Changed Bug title to 'Scan code event not generated for some keys of the Apple keyboard: those in applespi_fn_codes' from 'Scan code event not generated for some keys of the Apple keyboard'. -- 757356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#757356: Scan code event not generated for some keys of the Apple keyboard: those in applespi_fn_codes
Control: retitle -1 Scan code event not generated for some keys of the Apple
keyboard: those in applespi_fn_codes
On 2021-05-26 09:52:16 +0200, Vincent Lefevre wrote:
> No MSC_SCAN line for F1 to F12.
[...]
> Same issue for the Enter and Backspace keys:
[...]
And the cursor keys. Actually, all the keys corresponding to
static const struct applespi_key_translation applespi_fn_codes[] = {
{ KEY_BACKSPACE, KEY_DELETE },
{ KEY_ENTER,KEY_INSERT },
{ KEY_F1, KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY },
{ KEY_F2, KEY_BRIGHTNESSUP, APPLE_FLAG_FKEY },
{ KEY_F3, KEY_SCALE, APPLE_FLAG_FKEY },
{ KEY_F4, KEY_DASHBOARD, APPLE_FLAG_FKEY },
{ KEY_F5, KEY_KBDILLUMDOWN, APPLE_FLAG_FKEY },
{ KEY_F6, KEY_KBDILLUMUP, APPLE_FLAG_FKEY },
{ KEY_F7, KEY_PREVIOUSSONG, APPLE_FLAG_FKEY },
{ KEY_F8, KEY_PLAYPAUSE, APPLE_FLAG_FKEY },
{ KEY_F9, KEY_NEXTSONG, APPLE_FLAG_FKEY },
{ KEY_F10, KEY_MUTE, APPLE_FLAG_FKEY },
{ KEY_F11, KEY_VOLUMEDOWN, APPLE_FLAG_FKEY },
{ KEY_F12, KEY_VOLUMEUP, APPLE_FLAG_FKEY },
{ KEY_RIGHT,KEY_END },
{ KEY_LEFT, KEY_HOME },
{ KEY_DOWN, KEY_PAGEDOWN },
{ KEY_UP, KEY_PAGEUP },
{ }
};
in drivers/input/keyboard/applespi.c.
Just in case, in /etc/modprobe.d/hid_apple.conf, I have
options hid_apple fnmode=2
options hid_apple iso_layout=0
--
Vincent Lefèvre - Web:
Processed: Scan codes still not generated for F1 to F12, Enter and Backspace
Processing control commands:
> reopen -1
Bug #757356 {Done: j...@debian.org} [src:linux] Scan code event not generated
for some keys of the Apple keyboard
Bug reopened
Ignoring request to alter fixed versions of bug #757356 to the same values
previously set
> found -1 5.10.38-1
Bug #757356 [src:linux] Scan code event not generated for some keys of the
Apple keyboard
Marked as found in versions linux/5.10.38-1.
--
757356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#757356: Scan codes still not generated for F1 to F12, Enter and Backspace
Control: reopen -1 Control: found -1 5.10.38-1 On 2021-04-28 18:39:44 +0200, j...@debian.org wrote: > This bug was filed for a very old kernel. If you can reproduce it with > - the current version in unstable/testing > - the latest kernel from buster.backports > please reopen the bug, see https://www.debian.org/Bugs/server-control Bug still reproducible with linux-image-5.10.0-7-amd64 5.10.38-1. # evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: AT Translated Set 2 keyboard /dev/input/event1: Video Bus /dev/input/event2: PS/2 Generic Mouse /dev/input/event3: Apple, Inc Apple Keyboard /dev/input/event4: Apple, Inc Apple Keyboard /dev/input/event5: PixArt USB Optical Mouse [...] Select the device event number [0-24]: 3 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x5ac product 0x221 version 0x111 Input device name: "Apple, Inc Apple Keyboard" [...] Testing ... (interrupt to exit) Event: time 1622014586.354418, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0 Event: time 1622014586.354418, -- SYN_REPORT Event: time 1622014588.314431, type 1 (EV_KEY), code 59 (KEY_F1), value 1 Event: time 1622014588.314431, -- SYN_REPORT éEvent: time 1622014588.402405, type 1 (EV_KEY), code 59 (KEY_F1), value 0 Event: time 1622014588.402405, -- SYN_REPORT Event: time 1622014591.010396, type 1 (EV_KEY), code 60 (KEY_F2), value 1 Event: time 1622014591.010396, -- SYN_REPORT èEvent: time 1622014591.130400, type 1 (EV_KEY), code 60 (KEY_F2), value 0 Event: time 1622014591.130400, -- SYN_REPORT Event: time 1622014593.266402, type 1 (EV_KEY), code 61 (KEY_F3), value 1 Event: time 1622014593.266402, -- SYN_REPORT êEvent: time 1622014593.418425, type 1 (EV_KEY), code 61 (KEY_F3), value 0 Event: time 1622014593.418425, -- SYN_REPORT Event: time 1622014594.258377, type 1 (EV_KEY), code 62 (KEY_F4), value 1 Event: time 1622014594.258377, -- SYN_REPORT ëEvent: time 1622014594.410386, type 1 (EV_KEY), code 62 (KEY_F4), value 0 Event: time 1622014594.410386, -- SYN_REPORT Event: time 1622014595.186424, type 1 (EV_KEY), code 63 (KEY_F5), value 1 Event: time 1622014595.186424, -- SYN_REPORT âEvent: time 1622014595.306297, type 1 (EV_KEY), code 63 (KEY_F5), value 0 Event: time 1622014595.306297, -- SYN_REPORT Event: time 1622014595.898361, type 1 (EV_KEY), code 64 (KEY_F6), value 1 Event: time 1622014595.898361, -- SYN_REPORT îEvent: time 1622014596.018362, type 1 (EV_KEY), code 64 (KEY_F6), value 0 Event: time 1622014596.018362, -- SYN_REPORT Event: time 1622014596.546417, type 1 (EV_KEY), code 65 (KEY_F7), value 1 Event: time 1622014596.546417, -- SYN_REPORT ôEvent: time 1622014596.666411, type 1 (EV_KEY), code 65 (KEY_F7), value 0 Event: time 1622014596.666411, -- SYN_REPORT Event: time 1622014597.130399, type 1 (EV_KEY), code 66 (KEY_F8), value 1 Event: time 1622014597.130399, -- SYN_REPORT ûEvent: time 1622014597.234394, type 1 (EV_KEY), code 66 (KEY_F8), value 0 Event: time 1622014597.234394, -- SYN_REPORT Event: time 1622014597.714254, type 1 (EV_KEY), code 67 (KEY_F9), value 1 Event: time 1622014597.714254, -- SYN_REPORT àEvent: time 1622014597.842254, type 1 (EV_KEY), code 67 (KEY_F9), value 0 Event: time 1622014597.842254, -- SYN_REPORT Event: time 1622014598.354389, type 1 (EV_KEY), code 68 (KEY_F10), value 1 Event: time 1622014598.354389, -- SYN_REPORT ùEvent: time 1622014598.458419, type 1 (EV_KEY), code 68 (KEY_F10), value 0 Event: time 1622014598.458419, -- SYN_REPORT Event: time 1622014598.962403, type 1 (EV_KEY), code 87 (KEY_F11), value 1 Event: time 1622014598.962403, -- SYN_REPORT ïEvent: time 1622014599.058405, type 1 (EV_KEY), code 87 (KEY_F11), value 0 Event: time 1622014599.058405, -- SYN_REPORT Event: time 1622014599.826412, type 1 (EV_KEY), code 88 (KEY_F12), value 1 Event: time 1622014599.826412, -- SYN_REPORT çEvent: time 1622014599.938401, type 1 (EV_KEY), code 88 (KEY_F12), value 0 Event: time 1622014599.938401, -- SYN_REPORT Event: time 1622014601.242407, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70068 Event: time 1622014601.242407, type 1 (EV_KEY), code 110 (KEY_INSERT), value 1 Event: time 1622014601.242407, -- SYN_REPORT ^[[2~Event: time 1622014601.378309, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70068 Event: time 1622014601.378309, type 1 (EV_KEY), code 110
