August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219879] New: [TRACKERBUG] Remove EOL OpenSSL 1.1.1 and OpenSSL 1.0.0
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1219879 Bug ID: 1219879 Summary: [TRACKERBUG] Remove EOL OpenSSL 1.1.1 and OpenSSL 1.0.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: otto.hollmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug collects the challenges and packages that need to be adapted before removing OpenSSL 1.1.1 and OpenSSL 1.0.0 OpenSSL 1.1.1 (package openssl1_1) is EOL since 11th September 2023. OpenSSL 1.0.0 (package openssl1_0_0) is EOL since 31th December 2019. Therefore, it makes sense to get rid of them and we are going to remove them from Factory in the near future. Unfortunately some packages still rely/depend on these old OpenSSL versions. If we would like to keep these packages, they must be adapted to use OpenSSL 3. Currently these packages are usually hardcoded to use specific openssl package, e.g.: > BuildRequires: libopenssl-1_1-devel The preferred way is to use our meta package > BuildRequires: libopenssl or > BuildRequires: libopenssl-devel that will always pull respective packages with the default OpenSSL version (at the moment libopenssl3 or libopenssl-3-devel). Migration guide can be found here: https://www.openssl.org/docs/man3.0/man7/migration_guide.html List of packages that are using old OpenSSL: dd_rescue EternalTerminal fdo-client libredfish libzrtpcpp python -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1228610] New: Mail Makefile error finding alias directory
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228610 Bug ID: 1228610 Summary: Mail Makefile error finding alias directory Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: marc(a)marcchamberlin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The macro shell script for ALIAS_FILE is searching for a file. Instead it should be searching for a directory. Change the ALIAS_FILE environment variable in /etc/mail/Makefile from ALIAS_FILE = $(shell find $(ETC)aliases.d/ -type f) to ALIAS_FILE = $(shell find $(ETC)aliases.d/ -type d) Recommend changing the name of this environment variable to ALIAS_DIR to avoid confusion. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1221183] New: Upgrade problems with clang-cpp
by bugzilla_noreply＠suse.com 17 Nov '24

17 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221183 Bug ID: 1221183 Summary: Upgrade problems with clang-cpp Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: franz.sirl-obs(a)lauterbach.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Hi, during a "zypper --releasever=15.6 dup" upgrade from a fully up-to-date 15.5 installation I got the following messages: Checking for file conflicts: ...................................................................................................................................................................[error] Detected 4 file conflicts: File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from install of clang13-13.0.1-bp156.7.42.x86_64 (Main Repository) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang11-11.0.1-150300.3.6.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang15-15.0.7-150500.4.4.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang7-7.0.1-150100.3.22.2.x86_64 (@System) File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no): yes Even though this is mostly harmless, it disturbs the upgrade experience and probably can be easily fixed by backporting the clang-cpp/update-alternatives change from clang17 to the other clang versions that are part of Leap. regards, Franz -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1228824] New: libbotan 2 > 3 switch breaks dependencies?
by bugzilla_noreply＠suse.com 17 Nov '24

17 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228824 Bug ID: 1228824 Summary: libbotan 2 > 3 switch breaks dependencies? Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: t.rother(a)netzwissen.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- After the latest tumbleweed update I had problems with starting keepassxc LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20240801 Codename: n/a - current keepassxc 2.7.9 requires libbotan-2-19.x and crashes without it on startup. - only botan 3.x is available in the tumbleweed repos - this affects both the classic rpm and the flathub package Current workaround: install libbotan 2.x manually from leap 15 and have both packages in parallel: S | Name | Summary | Type ---+----------------+-----------------------------+-------- i+ | libbotan-2-19 | A C++ Crypto Library | package i+ | libbotan-3-5 | A C++ Crypto Library | package With this setup at least the flathub package works normal: KeePassXC org.keepassxc.KeePassXC 2.7.9 stable system Note: severity "major" as the password manager is a critical application for most users -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1229061] New: Laptop that will only run Plasma/Wayland, not Plasma X11
by bugzilla_noreply＠suse.com 16 Nov '24

16 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1229061 Bug ID: 1229061 Summary: Laptop that will only run Plasma/Wayland, not Plasma X11 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: 64bit OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: marc(a)marcchamberlin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876623 --> https://bugzilla.suse.com/attachment.cgi?id=876623&action=edit xsession-errors file When I try to use the Plasma/X11 desktop, after a reboot I reach the KDE login screen OK. If I choose to log in with the Plasma/X11 desktop, after entering my login name and password, the screen just goes blank for a moment, then cycles back and re-brings up the login/password screen again. Apparently the Plasma/X11 version of the desktop is not accepting my login credentials for some reason. However, if I choose to brings up the Plasma/Wayland desktop, my login credentials work just fine and the desktop comes up OK. I have attached a copy of my .xsession-errors file hoping that might offer a clue. (Guess I can only add one attachment at a time) will add results of doing a hw-probe -all in a follow on post. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1215403] New: SDDM default display-manager cannot login to X11 desktop
by bugzilla_noreply＠suse.com 16 Nov '24

16 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215403 Bug ID: 1215403 Summary: SDDM default display-manager cannot login to X11 desktop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ajbudge(a)errichel.co.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With TW as OS and KDE desktop, when running SDDM as default-displaymanager after boot login will only work with Plasma (Wayland) desktop. Selecting X11 and logging in goes dark and then after a few seconds returns to login screen. journal gives me:- Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: Starting X11 session: "" "/usr/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\"" Sep 16 09:22:04 HP-Z640-1 sddm[1851]: Session started false Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: [PAM] Closing session Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: [PAM] Ended. Sep 16 09:22:04 HP-Z640-1 sddm[1851]: Auth: sddm-helper exited with 2 and there is nothing in /etc/sddm.conf.d> or /.local/share/sddm> cat xorg-session.log (nothing here) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1213139] New: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213139 Bug ID: 1213139 Summary: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3412937/modules/cons oletest_setup/steps/52 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Randomly (currently every ~4th run), the test fails because systemd-vconsole-setup fails to complete. The kernel spits out an allocation failure: [ 519.853569] systemd-vconsol: vmalloc error: size 0, page order 9, failed to allocate pages, mode:0xcc2(GFP_KERNEL|__GFP_HIGHMEM), nodemask=(null),cpuset=/,mems_allowed=0 [ 519.854619] CPU: 0 PID: 11361 Comm: systemd-vconsol Not tainted 6.3.9-1-default #1 openSUSE Tumbleweed 4b767630dbc263131e96e89ef291fd4fd2951892 [ 519.855385] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 519.855860] Call Trace: [ 519.856047] <TASK> [ 519.856208] dump_stack_lvl+0x47/0x60 [ 519.856455] warn_alloc+0x13a/0x1b0 [ 519.856693] ? __alloc_pages+0x32d/0x350 [ 519.857009] __vmalloc_node_range+0x631/0x8b0 [ 519.857343] ? con_font_op+0x193/0x430 [ 519.857593] kvmalloc_node+0xa6/0xd0 [ 519.857857] ? con_font_op+0x193/0x430 [ 519.858105] con_font_op+0x193/0x430 [ 519.858346] ? __pfx_bpf_lsm_capable+0x10/0x10 [ 519.858631] ? security_capable+0x44/0x70 [ 519.858891] vt_ioctl+0x834/0x1380 [ 519.859126] tty_ioctl+0x4b1/0x870 [ 519.859355] __x64_sys_ioctl+0x94/0xd0 [ 519.859601] do_syscall_64+0x60/0x90 [ 519.859871] ? exc_page_fault+0x6e/0x150 [ 519.860129] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 519.860447] RIP: 0033:0x7f1144d0c2cf [ 519.860710] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 519.861757] RSP: 002b:00007ffe520b5af0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 519.862201] RAX: ffffffffffffffda RBX: 00007ffe520b5c10 RCX: 00007f1144d0c2cf [ 519.862843] RDX: 00007ffe520b5bf0 RSI: 0000000000004b72 RDI: 0000000000000003 [ 519.863463] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000001 [ 519.864093] R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000000008 [ 519.864705] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 [ 519.865317] </TASK> [ 519.865681] Mem-Info: [ 519.866038] active_anon:34752 inactive_anon:94983 isolated_anon:0 active_file:120769 inactive_file:114642 isolated_file:0 unevictable:3088 dirty:1160 writeback:0 slab_reclaimable:23978 slab_unreclaimable:21653 mapped:30383 shmem:4200 pagetables:3497 sec_pagetables:0 bounce:0 kernel_misc_reclaimable:0 free:66953 free_pcp:198 free_cma:0 [ 519.881932] Node 0 active_anon:139008kB inactive_anon:379932kB active_file:483076kB inactive_file:458568kB unevictable:12352kB isolated(anon):0kB isolated(file):0kB mapped:121532kB dirty:4640kB writeback:0kB shmem:16800kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 61440kB writeback_tmp:0kB kernel_stack:8040kB pagetables:13988kB sec_pagetables:0kB all_unreclaimable? no [ 519.893364] Node 0 DMA free:8220kB boost:0kB min:328kB low:408kB high:488kB reserved_highatomic:0KB active_anon:32kB inactive_anon:1908kB active_file:1564kB inactive_file:2136kB unevictable:0kB writepending:0kB present:15000kB managed:14364kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [ 519.903019] lowmem_reserve[]: 0 1889 1889 1889 1889 [ 519.905153] Node 0 DMA32 free:259592kB boost:0kB min:44724kB low:55904kB high:67084kB reserved_highatomic:16384KB active_anon:138976kB inactive_anon:378024kB active_file:481512kB inactive_file:456432kB unevictable:12352kB writepending:4640kB present:2076960kB managed:1966804kB mlocked:16kB bounce:0kB free_pcp:792kB local_pcp:792kB free_cma:0kB [ 519.915738] lowmem_reserve[]: 0 0 0 0 0 [ 519.917815] Node 0 DMA: 31*4kB (UME) 13*8kB (UME) 10*16kB (UM) 21*32kB (UME) 20*64kB (UM) 10*128kB (UME) 2*256kB (UE) 2*512kB (UE) 1*1024kB (E) 1*2048kB (E) 0*4096kB = 8228kB [ 519.920264] Node 0 DMA32: 20402*4kB (UMEH) 7366*8kB (UMEH) 2957*16kB (UMEH) 1109*32kB (UMEH) 359*64kB (UMEH) 66*128kB (UMEH) 11*256kB (MH) 4*512kB (MH) 0*1024kB 0*2048kB 0*4096kB = 259624kB [ 519.922145] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [ 519.923229] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [ 519.924415] 262294 total pagecache pages [ 519.925139] 22685 pages in swap cache [ 519.925777] Free swap = 1663652kB [ 519.926439] Total swap = 2097148kB [ 519.927082] 522990 pages RAM [ 519.927676] 0 pages HighMem/MovableOnly [ 519.928332] 27698 pages reserved [ 519.929181] 0 pages cma reserved [ 519.929828] 0 pages hwpoisoned If the system was actually out of RAM, I'd expect it to fail earlier in random places already. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-upgrade_Leap_15.2_cryptlvm@uefi fails in [consoletest_setup](https://openqa.opensuse.org/tests/3412937/modules/consol… ## Test suite description Upgrade scenario with cryptlvm for Leap 15.2 Set QEMUVGA=virtio due to bsc#1210555 ## Reproducible Fails since (at least) Build [20230401](https://openqa.opensuse.org/tests/3205451) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212937] New: Kernel panic when booting up tumbleweed 20230629
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1212937 Bug ID: 1212937 Summary: Kernel panic when booting up tumbleweed 20230629 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867932 --> https://bugzilla.suse.com/attachment.cgi?id=867932&action=edit screenshot When I booted my tw system today, I ran into a kernel panic. Kernel: Linux 6.3.9-1-default Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad T14s Gen 2a The issue happened once and after a reboot I was able to boot up fine. The standby issue with the laptop hanging up on resume and eventually rebooting automatically is back again and sadly reproducible always. Not sure if that could be related. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1228728] New: system marked as tainted: unmerged-bin
by bugzilla_noreply＠suse.com 14 Nov '24

14 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228728 Bug ID: 1228728 Summary: system marked as tainted: unmerged-bin Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- ``` State: running Units: 444 loaded (incl. loaded aliases) Jobs: 0 queued Failed: 0 units Since: Thu 2024-08-01 00:58:42 UTC; 8h ago systemd: 256.4+suse.6.g5bba1ebe17 Tainted: unmerged-bin ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1229552] New: Traceback at ../net/netfilter/nf_tables_api.c:2050 nf_tables_chain_destroy
by bugzilla_noreply＠suse.com 14 Nov '24

14 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1229552 Bug ID: 1229552 Summary: Traceback at ../net/netfilter/nf_tables_api.c:2050 nf_tables_chain_destroy Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876865 --> https://bugzilla.suse.com/attachment.cgi?id=876865&action=edit asgard2.i.o.o journal after boot Hi, installing updates including kernel-default-5.14.21-150500.55.65.1 on one of our openSUSE firewall VMs today, lots of this is printed during boot: ``` Aug 21 09:47:25 asgard2 kernel: WARNING: CPU: 2 PID: 5509 at ../net/netfilter/nf_tables_api.c:2050 nf_tables_chain_destroy+0x12a/0x150 [nf_tables] Aug 21 09:47:25 asgard2 kernel: Modules linked in: tun nf_nat nf_conntrack_netlink nf_tables nfnetlink wireguard libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel curve25519_x86_64 libcurve25519_generic libchacha dm_mod af_packet 8021q garp mrp stp llc iscsi_ibft iscsi_boot_sysfs rfkill nls_iso8859_1 nls_cp437 vfat fat iTCO_wdt intel_pmc_bxt iTCO_vendor_support intel_rapl_msr intel_rapl_common virtio_net virtio_balloon i2c_i801 net_failover pcspkr failover lpc_ich i2c_smbus mfd_core button joydev fuse configfs dmi_sysfs ip_tables x_tables crc32_pclmul ghash_clmulni_intel sha512_ssse3 ahci libahci sha256_ssse3 sha1_ssse3 libata sd_mod xhci_pci xhci_pci_renesas t10_pi crc64_rocksoft_generic xhci_hcd crc64_rocksoft sg crc64 usbcore aesni_intel crypto_simd cryptd scsi_mod virtio_blk serio_raw btrfs blake2b_generic xor raid6_pq nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c crc32c_intel efivarfs qemu_fw_cfg virtio_rng Aug 21 09:47:25 asgard2 kernel: Supported: Yes Aug 21 09:47:25 asgard2 kernel: CPU: 2 PID: 5509 Comm: nft Tainted: G W 6.4.0-150600.23.17-default #1 SLE15-SP6 5eff937aa9559314e63d74eec60fba157a5dbfd6 Aug 21 09:47:25 asgard2 kernel: Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022 Aug 21 09:47:25 asgard2 kernel: RIP: 0010:nf_tables_chain_destroy+0x12a/0x150 [nf_tables] Aug 21 09:47:25 asgard2 kernel: Code: 5f e9 2a ab 42 d3 48 8b 7b 58 e8 21 ab 42 d3 48 8b 7b 68 e8 18 ab 42 d3 48 89 df 5b 5d 41 5c 41 5d 41 5e 41 5f e9 06 ab 42 d3 <0f> 0b 5b 5d 41 5c 41 5d 41 5e 41 5f e9 85 91 d6 d3 0f 0b e9 05 ff Aug 21 09:47:25 asgard2 kernel: RSP: 0018:ffffa7fd8046b788 EFLAGS: 00010202 Aug 21 09:47:25 asgard2 kernel: RAX: 0000000000000001 RBX: ffff8bf6e8c89000 RCX: 0000000080150010 Aug 21 09:47:25 asgard2 kernel: RDX: ffff8bf72442f850 RSI: 0000000000000001 RDI: ffff8bf72442f868 Aug 21 09:47:25 asgard2 kernel: RBP: ffff8bf641f9a310 R08: 0000000000000001 R09: 0000000000000000 Aug 21 09:47:25 asgard2 kernel: R10: ffff8bf72442fb00 R11: 0000000000000372 R12: dead000000000122 Aug 21 09:47:25 asgard2 kernel: R13: dead000000000100 R14: ffff8bf72442ff00 R15: ffff8bf72442ff00 Aug 21 09:47:25 asgard2 kernel: FS: 00007f5c7ee8d740(0000) GS:ffff8bf728300000(0000) knlGS:0000000000000000 Aug 21 09:47:25 asgard2 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Aug 21 09:47:25 asgard2 kernel: CR2: 000055f5de2fbf14 CR3: 000000018f6b2000 CR4: 0000000000350ee0 Aug 21 09:47:25 asgard2 kernel: Call Trace: Aug 21 09:47:25 asgard2 kernel: <TASK> Aug 21 09:47:25 asgard2 kernel: ? __warn+0x7d/0x140 Aug 21 09:47:25 asgard2 kernel: ? nf_tables_chain_destroy+0x12a/0x150 [nf_tables 33ac467d326e5f0a925b542f8b6b5777507be3ab] Aug 21 09:47:25 asgard2 kernel: ? report_bug+0xfb/0x1e0 Aug 21 09:47:25 asgard2 kernel: ? handle_bug+0x44/0x80 Aug 21 09:47:25 asgard2 kernel: ? exc_invalid_op+0x13/0x60 Aug 21 09:47:25 asgard2 kernel: ? asm_exc_invalid_op+0x16/0x20 Aug 21 09:47:25 asgard2 kernel: ? nf_tables_chain_destroy+0x12a/0x150 [nf_tables 33ac467d326e5f0a925b542f8b6b5777507be3ab] Aug 21 09:47:25 asgard2 kernel: __nf_tables_abort+0x5c4/0xb00 [nf_tables 33ac467d326e5f0a925b542f8b6b5777507be3ab] Aug 21 09:47:25 asgard2 kernel: nf_tables_abort+0x5c/0x1a0 [nf_tables 33ac467d326e5f0a925b542f8b6b5777507be3ab] Aug 21 09:47:25 asgard2 kernel: nfnetlink_rcv_batch+0x368/0x640 [nfnetlink 464c7ee5607c7e250b1543054c6c85719c9ba7a6] Aug 21 09:47:25 asgard2 kernel: ? __vmalloc_node_range+0x40d/0x860 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: nfnetlink_rcv+0x121/0x140 [nfnetlink 464c7ee5607c7e250b1543054c6c85719c9ba7a6] Aug 21 09:47:25 asgard2 kernel: netlink_unicast+0x1c7/0x290 Aug 21 09:47:25 asgard2 kernel: netlink_sendmsg+0x31c/0x460 Aug 21 09:47:25 asgard2 kernel: sock_sendmsg+0x92/0xa0 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ____sys_sendmsg+0x207/0x2a0 Aug 21 09:47:25 asgard2 kernel: ___sys_sendmsg+0x88/0xd0 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? sk_getsockopt+0x1d1/0x10e0 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? sk_getsockopt+0x1d1/0x10e0 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? security_capable+0x38/0x60 Aug 21 09:47:25 asgard2 kernel: ? __sys_sendmsg+0x5e/0xa0 Aug 21 09:47:25 asgard2 kernel: __sys_sendmsg+0x5e/0xa0 Aug 21 09:47:25 asgard2 kernel: ? __sys_setsockopt+0xff/0x1b0 Aug 21 09:47:25 asgard2 kernel: do_syscall_64+0x5b/0x80 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? syscall_exit_to_user_mode+0x1e/0x40 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? do_syscall_64+0x67/0x80 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? syscall_exit_to_user_mode+0x1e/0x40 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? do_syscall_64+0x67/0x80 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? do_user_addr_fault+0x446/0x890 Aug 21 09:47:25 asgard2 kernel: ? srso_return_thunk+0x5/0x5f Aug 21 09:47:25 asgard2 kernel: ? exc_page_fault+0x69/0x150 Aug 21 09:47:25 asgard2 kernel: entry_SYSCALL_64_after_hwframe+0x7c/0xe6 Aug 21 09:47:25 asgard2 kernel: RIP: 0033:0x7f5c7e9313c0 Aug 21 09:47:25 asgard2 kernel: Code: 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 80 3d 69 c6 0d 00 00 74 17 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 48 83 ec 28 89 54 Aug 21 09:47:25 asgard2 kernel: RSP: 002b:00007ffe95184ec8 EFLAGS: 00000202 ORIG_RAX: 000000000000002e Aug 21 09:47:25 asgard2 kernel: RAX: ffffffffffffffda RBX: 00007ffe951960e0 RCX: 00007f5c7e9313c0 Aug 21 09:47:25 asgard2 kernel: RDX: 0000000000000000 RSI: 00007ffe95195f90 RDI: 0000000000000003 Aug 21 09:47:25 asgard2 kernel: RBP: 00007ffe95196090 R08: 0000000000000004 R09: 0000000000000002 Aug 21 09:47:25 asgard2 kernel: R10: 00007f5c7e80c840 R11: 0000000000000202 R12: 0000000000040000 Aug 21 09:47:25 asgard2 kernel: R13: 00000000000e0800 R14: 00007ffe95184f00 R15: 0000000000000003 Aug 21 09:47:25 asgard2 kernel: </TASK> Aug 21 09:47:25 asgard2 kernel: ---[ end trace 0000000000000000 ]--- ``` Full journal (which includes the kernel log) is attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 4