January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1217402] New: AUDIT-FIND: Updating server configuration as root while parsing untrusted data
by bugzilla_noreply＠suse.com 14 Feb '24

14 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1217402 Bug ID: 1217402 Summary: AUDIT-FIND: Updating server configuration as root while parsing untrusted data Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: fstrba(a)suse.com Reporter: jsegitz(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the new tomcat10 packages I stumbled across: 687 %post webapps 688 %{serverxmltool} add-context.xslt docBase=%{tomcatappdir}/ROOT path=/ 689 %{serverxmltool} add-context.xslt docBase=%{tomcatappdir}/sample path=/sample 690 %{serverxmltool} add-context.xslt docBase=%{tomcatappdir}/examples path=/examples This translates to e.g. /usr/libexec/tomcat/serverxml-tool.sh add-context.xslt docBase=/usr/share/tomcat/tomcat-webapps/ROOT path=/ serverxml-tool.sh invokes java with serverxmltool.jar to update /etc/tomcat/server.xml. All of this runs as root and parses XML. I didn't find a security issue with this (but also just spend a couple of minutes on this), but it's a bigger risk than necessary. Apart from overwriting the config file root privileges are not needed. Especially the java call should not run as root, xml operations are notoriously dangerous. runuser is a good tool for this. You can do the XML parsing as the tomcat user and then if necessary overwrite the tomcat config with an update file. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219222] New: Disable CONFIG_USELIB
by bugzilla_noreply＠suse.com 13 Feb '24

13 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219222 Bug ID: 1219222 Summary: Disable CONFIG_USELIB Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jack(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- uselib(2) system call is generally deprecated and was last needed with libc5. Recently there were also issues with this syscall and path-based LSMs [1] so from security POV it makes sense to disable CONFIG_USELIB if we don't need it. [1] https://lore.kernel.org/all/20240124192228.work.788-kees@kernel.org -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1218459] New: rpm scriptlets left over after snasphot updates
by bugzilla_noreply＠suse.com 13 Feb '24

13 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218459 Bug ID: 1218459 Summary: rpm scriptlets left over after snasphot updates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: d_werner(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I noticed on 2 Tumbleweed systems that since middle of October 2023 rpm scriptlets remain in the /var/tmp directory. For one of the systems the oldest files are related to the update from snapshot 20231012 to snapshot 20231013 on Oct. 15: $ ll -rt /var/tmp/rpm-tmp.* |head -rw------- 1 root root 177 15. Okt 14:07 /var/tmp/rpm-tmp.xEtA52 -rw------- 1 root root 479 15. Okt 14:07 /var/tmp/rpm-tmp.EXLxob -rw------- 1 root root 311 15. Okt 14:07 /var/tmp/rpm-tmp.bjfewF -rw------- 1 root root 648 15. Okt 14:07 /var/tmp/rpm-tmp.ZDYSLb -rw------- 1 root root 179 15. Okt 14:07 /var/tmp/rpm-tmp.BYmaWt -rw------- 1 root root 176 15. Okt 14:07 /var/tmp/rpm-tmp.aXzaBF -rw------- 1 root root 311 17. Okt 16:38 /var/tmp/rpm-tmp.eX0BsI -rw------- 1 root root 638 18. Okt 19:02 /var/tmp/rpm-tmp.F05Leb -rw------- 1 root root 311 18. Okt 19:02 /var/tmp/rpm-tmp.rxs60L -rw------- 1 root root 546 18. Okt 19:02 /var/tmp/rpm-tmp.nnvrQo and new files were created also with the update from snapshot 20231225 to snapshot 20231226 on Dec. 28: $ ll -rt /var/tmp/rpm-tmp.* |tail -rw------- 1 root root 311 22. Dez 19:32 /var/tmp/rpm-tmp.WVqG89 -rw------- 1 root root 1694 22. Dez 19:32 /var/tmp/rpm-tmp.1hF4yH -rw------- 1 root root 166 22. Dez 19:33 /var/tmp/rpm-tmp.eJdGQd -rw------- 1 root root 162 23. Dez 17:30 /var/tmp/rpm-tmp.ZsqgtG -rw------- 1 root root 177 23. Dez 17:30 /var/tmp/rpm-tmp.pPVWkF -rw------- 1 root root 311 23. Dez 17:30 /var/tmp/rpm-tmp.M8ojbB -rw------- 1 root root 311 26. Dez 20:16 /var/tmp/rpm-tmp.SLRu25 -rw------- 1 root root 166 28. Dez 06:08 /var/tmp/rpm-tmp.fYFPnC -rw------- 1 root root 311 28. Dez 06:09 /var/tmp/rpm-tmp.V99rNu -rw------- 1 root root 253 28. Dez 06:09 /var/tmp/rpm-tmp.Kn51G9 I do not find a tmpfiles.d configuration which would cause removal of files in /var/tmp owned by root reaching a certain age, therefore I suspect this started with snapshot 20231013. Currently the directory contains 236 such files on this system: $ ll /var/tmp/rpm-tmp.* |wc -l 236 Seems the files are created during the posttrans step of the snapshot update with zypper dup: stat rpm-tmp.bjfewF File: rpm-tmp.bjfewF Size: 311 Blocks: 8 IO Block: 4096 regular file Device: 254,1 Inode: 662121 Links: 1 Access: (0600/-rw-------) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2023-12-30 18:38:13.806666658 +0100 Modify: 2023-10-15 14:07:33.799999952 +0200 Change: 2023-10-15 14:07:33.799999952 +0200 Birth: 2023-10-15 14:07:33.796666619 +0200 fits to /var/log/zypp/history entry: # 2023-10-15 14:07:33 %posttrans(grub2-x86_64-efi-2.12~rc1-5.1.noarch) script output: # ++ cat /run/fde-tpm-helper/update # ++ uniq The number of files created during snapshot updates varies, probably depending on the updated packages and the related posttrans scriptlets. Content of the files generated on Oct 15: # cat $(ll -rt rpm-tmp.* |grep 'Oct 15' |awk '{print $9}') set -x # Migration to /usr/etc, restore just created .rpmsave for i in logrotate.d/zypp-history.lr; do test -f /etc/${i}.rpmsave && mv -v /etc/${i}.rpmsave /etc/${i} ||: done set -x if test -x /sbin/update-bootloader; then if test -f /run/update-bootloader/reinit; then rm -f -- /run/update-bootloader/reinit /run/update-bootloader/refresh if test -x /usr/libexec/grub2-instdev-fixup.pl; then /usr/libexec/grub2-instdev-fixup.pl || : fi /sbin/update-bootloader --reinit || : elif test -f /run/update-bootloader/refresh; then rm -f /run/update-bootloader/refresh /sbin/update-bootloader --refresh || : fi fi set -x # Launch the issue-generator: we have a new config file in /usr/lib/issue.d that needs to be represented if [ -x /usr/sbin/issue-generator ]; then if [ -x /usr/bin/systemd-tmpfiles ]; then /usr/bin/systemd-tmpfiles --create issue-generator.conf || : fi /usr/sbin/issue-generator || : fi set -x if test -x /sbin/update-bootloader; then if test -f /run/update-bootloader/reinit; then rm -f -- /run/update-bootloader/reinit /run/update-bootloader/refresh if test -x /usr/libexec/grub2-instdev-fixup.pl; then /usr/libexec/grub2-instdev-fixup.pl || : fi /sbin/update-bootloader --reinit || : elif test -f /run/update-bootloader/refresh; then rm -f /run/update-bootloader/refresh /sbin/update-bootloader --refresh || : fi fi if test -f /run/fde-tpm-helper/update; then /usr/libexec/fde/fde-tpm-helper "`cat /run/fde-tpm-helper/update | uniq`" || : rm -f /run/fde-tpm-helper/update fi set -x # Migration to /usr/etc, restore just created .rpmsave for i in logrotate.d/samba pam.d/samba; do test -f /etc/${i}.rpmsave && mv -v /etc/${i}.rpmsave /etc/${i} ||: doneset -x # Migration to /usr/etc, restore just created .rpmsave for i in logrotate.d/samba-winbind ; do test -f /etc/${i}.rpmsave && mv -v /etc/${i}.rpmsave /etc/${i} ||: done -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219388] New: VUL-0: CVE-2024-23840: eksctl: goreleaser: goreleaser release --debug shows secrets
by bugzilla_noreply＠suse.com 10 Feb '24

10 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219388 Bug ID: 1219388 Summary: VUL-0: CVE-2024-23840: eksctl: goreleaser: goreleaser release --debug shows secrets Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/392568/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: opensuse_buildservice(a)ojkastl.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: thomas.leroy(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. `goreleaser release --debug` log shows secret values used in the in the custom publisher. This vulnerability is fixed in 1.24.0. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-23840 https://github.com/goreleaser/goreleaser/commit/d5b6a533ca1dc3366983d5d31ee… https://github.com/goreleaser/goreleaser/security/advisories/GHSA-h3q2-8whx… https://www.cve.org/CVERecord?id=CVE-2024-23840 https://bugzilla.redhat.com/show_bug.cgi?id=2262014 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219307] New: mathomatic requires python2
by bugzilla_noreply＠suse.com 09 Feb '24

09 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219307 Bug ID: 1219307 Summary: mathomatic requires python2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- mathomatic has a requires on /usr/bin/python, aka python2 There are a bunch of scripts in this package: mathomatic-16.0.5> grep /usr/bin/python . -r ./primes/matho-mult:#!/usr/bin/python ./primes/primorial:#!/usr/bin/python ./primes/matho-sum:#!/usr/bin/python ./examples/factorial:#!/usr/bin/python Please work with upstream to get this ported to python3 or, if no longer maintained, file a delreq against the package -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1219309] New: connman-test requires /usr/bin/python
by bugzilla_noreply＠suse.com 08 Feb '24

08 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219309 Bug ID: 1219309 Summary: connman-test requires /usr/bin/python Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Information for package connman-test: ------------------------------------- Repository : Main Repository (OSS) Name : connman-test Version : 1.42-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 75.1 KiB Installed : No Status : not installed Source package : connman-1.42-1.1.src Upstream URL : http://www.moblin.org/ Summary : Test and example scripts for connman Description : Provides test and example scripts for Connman (Connection Manager). Requires : [2] /usr/bin/python connman >= 1.42 connman-test has a runtime dep on /usr/bin/python, aka python2. Please bring this packet up to python3 or find other ways to eliminate the python2 dependency. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219313] New: regexploit has runtime dependency on python2 (/urs/bin/python)
by bugzilla_noreply＠suse.com 08 Feb '24

08 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219313 Bug ID: 1219313 Summary: regexploit has runtime dependency on python2 (/urs/bin/python) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- > zypper info --requires regexploit Loading repository data... Reading installed packages... Information for package regexploit: ----------------------------------- Repository : Main Repository (OSS) Name : regexploit Version : 1.0.0-1.13 Arch : noarch Vendor : openSUSE Installed Size : 376.5 KiB Installed : No Status : not installed Source package : regexploit-1.0.0-1.13.src Upstream URL : https://github.com/doyensec/regexploit Summary : Find regular expressions vulnerable to ReDoS Description : Many default regular expression parsers have unbounded worst-case complexity. Regex matching may be quick when presented with a matching input string. However, certain non-matching input strings can make the regular expression matcher go into crazy backtracking loops and take ages to process. This can cause denial of service, as the CPU will be stuck trying to match the regex. This tool is designed to: * find regular expressions which are vulnerable to ReDoS * give an example malicious string which will cause catastrophic backtracking Supports: - C# - JavaScript/TypeScript (requires node to be installed) - JSON - Python - YAML Requires : [5] /usr/bin/python3 /usr/bin/python /usr/bin/node python(abi) = 3.11 python3-base >= 3.8 the dependency on /usr/bin/python should be eliminated (port all scripts to python3) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218143] New: python2-pycairo is blocking update python-rpm-macros
by bugzilla_noreply＠suse.com 08 Feb '24

08 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218143 Bug ID: 1218143 Summary: python2-pycairo is blocking update python-rpm-macros Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871412 --> https://bugzilla.suse.com/attachment.cgi?id=871412&action=edit python2-pycairo_log.txt python-rpm-macros 20231204.dd64e74 (SR#1130671) is blocked by python2-pycairo failing to build. Most relevant part of the build log (attached): [ 12s] + xargs -0 /usr/bin/python2 -c ' [ 12s] import sys, py_compile [ 12s] for f in sys.argv[1:]: [ 12s] fp=f[len("/home/abuild/rpmbuild/BUILDROOT/python2-pycairo-1.18.1-6.20.x86_64"):] [ 12s] print(f"Generating cached byte-code for {fp}") [ 12s] for o in [0, 1]: [ 12s] py_compile.compile(f, dfile=fp, optimize=o) [ 12s] ' [ 12s] File "<string>", line 5 [ 12s] print(f"Generating cached byte-code for {fp}") [ 12s] ^ [ 12s] SyntaxError: invalid syntax [ 12s] error: Bad exit status from /var/tmp/rpm-tmp.LYEGW2 (%install) This seems to be using f-strings in python2.7 where they are not yet supported. The last update of python2-pycairo is from March 2020, so I'm wondering if this package is still maintained by upsteam. However, gimp, python-gobject2, python-gtk have a direct dependency on this package. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1218948] New: kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 Bug ID: 1218948 Summary: kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156] Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: chris(a)computersalat.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello kernel support, looks like a kernel module has some problems. I am continiously getting these watchdog messages on the console: Message from syslogd@tfrs-01 at Jan 18 12:24:04 ... kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156] Message from syslogd@tfrs-01 at Jan 18 12:24:34 ... kernel:[ 3410.230328][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 140s! [kworker/0:2:156] Message from syslogd@tfrs-01 at Jan 18 12:25:04 ... kernel:[ 3440.311352][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 168s! [kworker/0:2:156] --- snip End --- This is what I see in /var/log/messages: 2024-01-18T12:18:44.564626+00:00 tfrs-01 kernel: [ 3060.657363][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 142s! [kworker/0:2:156] 2024-01-18T12:18:44.564635+00:00 tfrs-01 kernel: [ 3060.657366][ C0] Modules linked in: usbhid af_packet iscsi_ibft iscsi_boot_sysfs dmi_sysfs msr snd_hda_codec_realtek intel_rapl_msr intel_rapl_common intel _uncore_frequency intel_uncore_frequency_common intel_pmc_core x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_generic nvme ucsi_acpi coretemp ledtrig_audio kvm_intel hp_wmi sparse_keymap iTCO_wdt nls_iso88 59_1 nls_cp437 mei_pxp mei_hdcp(N) mei_wdt typec_ucsi snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_d sp snd_sof snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_hda_ext_core snd_soc_core intel_pmc_bxt vfat mei_me nvme_core typec iTCO_vendor_support snd_compress platform_pr ofile kvm fat snd_pcm_dmaengine e1000e mfd_core nvme_common wmi_bmof roles irqbypass rfkill mei pcspkr snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm 2024-01-18T12:18:44.564636+00:00 tfrs-01 kernel: [ 3060.657381][ C0] snd_timer snd soundcore i2c_i801 i2c_smbus button thermal acpi_tad(N) acpi_pad fuse configfs efi_pstore(N) ip_tables x_tables ext4 crc16 mbcache jbd2 raid1 md_mod sd_mod t10_pi sr_mod crc64_rocksoft_generic cdrom crc64_rocksoft crc64 i915 i2c_algo_bit drm_buddy drm_display_helper crc32_pclmul crc32c_intel drm_kms_helper ghash_clmulni_intel xhci_pci syscopyarea sysfillrect xhci_pci_renesas sysimgblt fb_sys_fops cec xhci_hcd rc_core ttm ahci aesni_intel drm libahci usbcore libata crypto_simd cryptd serio_raw wmi video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod efivarfs 2024-01-18T12:18:44.564636+00:00 tfrs-01 kernel: [ 3060.657394][ C0] Supported: No, Unsupported modules are loaded 2024-01-18T12:18:44.564637+00:00 tfrs-01 kernel: [ 3060.657395][ C0] CPU: 0 PID: 156 Comm: kworker/0:2 Tainted: G W L N 5.14.21-150500.55.39-default #1 SLE15-SP5 534d850193522c220e62d98d0494b02a0dde2443 2024-01-18T12:18:44.564640+00:00 tfrs-01 kernel: [ 3060.657396][ C0] Hardware name: HP HP Elite Tower 600 G9 Desktop PC/8950, BIOS U01 Ver. 02.12.02 11/28/2023 2024-01-18T12:18:44.564640+00:00 tfrs-01 kernel: [ 3060.657396][ C0] Workqueue: events output_poll_execute [drm_kms_helper] 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657401][ C0] RIP: 0010:intel_dmc_load_program.part.10+0x75/0x320 [i915] 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657440][ C0] Code: 48 8d bd 48 0e 00 00 49 89 ec 8b 51 04 31 c0 85 d2 74 1f 48 8b 51 08 89 c6 8b 34 b2 8b 11 8d 14 82 48 03 95 e8 07 00 00 89 32 <83> c0 01 3b 41 04 72 e1 48 81 c1 c0 00 00 00 48 39 f9 75 cc 65 ff 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657441][ C0] RSP: 0018:ffffa498c065fb08 EFLAGS: 00000286 2024-01-18T12:18:44.564641+00:00 tfrs-01 kernel: [ 3060.657442][ C0] RAX: 0000000000000927 RBX: 0000000000000001 RCX: ffff952ed20a0a88 2024-01-18T12:18:44.564642+00:00 tfrs-01 kernel: [ 3060.657443][ C0] RDX: ffffa498c168249c RSI: 0000000000000010 RDI: ffff952ed20a0e48 2024-01-18T12:18:44.564642+00:00 tfrs-01 kernel: [ 3060.657443][ C0] RBP: ffff952ed20a0000 R08: 0000000000000000 R09: 0000000000000001 2024-01-18T12:18:44.564642+00:00 tfrs-01 kernel: [ 3060.657444][ C0] R10: ffffa498c065f9d0 R11: ffffa498c065f8f8 R12: ffff952ed20a0000 2024-01-18T12:18:44.564643+00:00 tfrs-01 kernel: [ 3060.657444][ C0] R13: 0000000000000006 R14: 0000000000000002 R15: ffffffffc0d967a0 2024-01-18T12:18:44.564643+00:00 tfrs-01 kernel: [ 3060.657445][ C0] FS: 0000000000000000(0000) GS:ffff953dff400000(0000) knlGS:0000000000000000 2024-01-18T12:18:44.564643+00:00 tfrs-01 kernel: [ 3060.657445][ C0] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657446][ C0] CR2: 00007ffd1a37bee6 CR3: 0000000456210000 CR4: 0000000000750ef0 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657446][ C0] PKRU: 55555554 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657446][ C0] Call Trace: 2024-01-18T12:18:44.564644+00:00 tfrs-01 kernel: [ 3060.657447][ C0] <TASK> 2024-01-18T12:18:44.564645+00:00 tfrs-01 kernel: [ 3060.657447][ C0] icl_display_core_init+0x2e3/0x6d0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564645+00:00 tfrs-01 kernel: [ 3060.657485][ C0] intel_display_power_resume+0x6b/0xa0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564645+00:00 tfrs-01 kernel: [ 3060.657522][ C0] intel_runtime_resume+0x7f/0x1e0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564646+00:00 tfrs-01 kernel: [ 3060.657543][ C0] pci_pm_runtime_resume+0x76/0xb0 2024-01-18T12:18:44.564646+00:00 tfrs-01 kernel: [ 3060.657545][ C0] ? pci_pm_default_resume+0x30/0x30 2024-01-18T12:18:44.564646+00:00 tfrs-01 kernel: [ 3060.657546][ C0] __rpm_callback+0x43/0x120 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657547][ C0] rpm_callback+0x5d/0x70 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657548][ C0] ? pci_pm_default_resume+0x30/0x30 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657549][ C0] rpm_resume+0x4c0/0x770 2024-01-18T12:18:44.564647+00:00 tfrs-01 kernel: [ 3060.657550][ C0] ? pci_bus_read_config_dword+0x41/0x70 2024-01-18T12:18:44.564648+00:00 tfrs-01 kernel: [ 3060.657551][ C0] __pm_runtime_resume+0x47/0x80 2024-01-18T12:18:44.564648+00:00 tfrs-01 kernel: [ 3060.657552][ C0] __intel_runtime_pm_get+0x1e/0x90 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564648+00:00 tfrs-01 kernel: [ 3060.657577][ C0] intel_display_power_get+0x24/0x60 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657614][ C0] intel_digital_port_connected+0x3a/0xa0 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657645][ C0] intel_dp_detect+0x2c8/0x660 [i915 78bbb16e393a51161506d14678c82dbe7746ab4e] 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657675][ C0] ? newidle_balance+0x2f0/0x440 2024-01-18T12:18:44.564649+00:00 tfrs-01 kernel: [ 3060.657676][ C0] drm_helper_probe_detect_ctx+0x6a/0xf0 [drm_kms_helper 27a7978049953ab8be9c7870f7a6b929411f05a2] 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657682][ C0] output_poll_execute+0x116/0x1f0 [drm_kms_helper 27a7978049953ab8be9c7870f7a6b929411f05a2] 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657686][ C0] process_one_work+0x264/0x440 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657688][ C0] worker_thread+0x2d/0x3c0 2024-01-18T12:18:44.564650+00:00 tfrs-01 kernel: [ 3060.657689][ C0] ? process_one_work+0x440/0x440 2024-01-18T12:18:44.564651+00:00 tfrs-01 kernel: [ 3060.657690][ C0] kthread+0x154/0x180 2024-01-18T12:18:44.564651+00:00 tfrs-01 kernel: [ 3060.657691][ C0] ? set_kthread_struct+0x50/0x50 2024-01-18T12:18:44.564651+00:00 tfrs-01 kernel: [ 3060.657692][ C0] ret_from_fork+0x1f/0x30 2024-01-18T12:18:44.564652+00:00 tfrs-01 kernel: [ 3060.657694][ C0] </TASK> --- snip END --- Is there any chance to get this fixed somehow ? Thank you Kind Regards Christian -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1219019] New: Nitrokey2 app is not functional under Wayland
by bugzilla_noreply＠suse.com 07 Feb '24

07 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219019 Bug ID: 1219019 Summary: Nitrokey2 app is not functional under Wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Nitrokey app is a 35d party software provided by the producer Nitrokey. Its function should be as follows: app is resident in the tray insertion of the key triggers app to give notice "key connected" once you unlock the secure password and/or an TOTP key, this is temporarily copied into the clipboard, hence you can paste it into the respective application. Hence the core function of the app is, to provide the TOTP or password to the clipboard and make it available. Now under X-server sessions this works flawlessly, but to my dismay I discovered that it is broken under Wayland. While the generation of the TOTP/OTP and the availability of the passwords are given in Wayland, there seems to be no way to have them transferred to the clipboard, which remains blanc and hence the functionality is broken. I signed this as major because it breaks the function of the app itself and there is a potential damage to the user. Imagine you are in the middle of e.g. buying a ticket / time limited offer and you have to unlock the catch by payment now. Unfortunately you are under Wayland, so you will find out that e.g. you cannot pay. This I find it to be a major issue as it can cause financial loss to the user. Because in order to work around you have to logout the session and login the session as X, but now your offer/ticket etc is gone. (A lot of users I suppose use Wayland as default on laptops now). A further danger I see with this is, that we are talking of shifting to Wayland as default and that X-server is somewhat deprecated now. So a security conscious user may well find himself sitting on the fence to choose between using less safe X doing business, not to speak of maybe soon, not being able to use the key at all, because no X-session is available any more(although this is probably still to come in future editions of TW but...better to fix it as soon as possible). Steps to follow: wayland KDE Plasma session with the app2 insert key unlock password tell to copy to clipboard clipboard remains blanc counter proof: log into the X-session version and it works. -- You are receiving this mail because: You are on the CC list for the bug.

1 2