April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1218393] New: Weird screen blanking (power mgmt?) issue
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1218393 Bug ID: 1218393 Summary: Weird screen blanking (power mgmt?) issue Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: rs.opensuse(a)spitzenpfeil.org QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My screen blanks after screen power mgmt kicks in - as expected. Unfortunately the timer doesn't seem to reset. As long as I move the mouse (even after switching to a console) the screen stays on, once any screen update stops, it goes dark. Currently I to run 'xsnow' !! to keep the screen updating, so it doesn't go dark all the time. This is not fun :-( Where to look? CPU: i7-7700T Graphics: HD 630 P.S.: https://forums.opensuse.org/t/internal-lcd-of-laptop-turning-off-comes-back… -- # VERSION="20231222" ID="opensuse-tumbleweed" -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222864] New: VUL-0: CVE-2024-31497: putty: NIST P521 private keys are exposed by biased signature generation
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222864 Bug ID: 1222864 Summary: VUL-0: CVE-2024-31497: putty: NIST P521 private keys are exposed by biased signature generation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: jengelh(a)inai.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In PuTTY 0.68 through 0.80 before 0.81, biased ECDSA nonce generation allows an attacker to recover a user's NIST P-521 secret key via a quick lattice-based attack in approximately 60 signatures. This is especially important in a scenario where an adversary is able to read messages signed by PuTTY or Pageant. One scenario is that the adversary is an operator of an SSH server to which the victim authenticates (for remote login or file copy), even though this server is not fully trusted by the victim, and the victim uses the same private key for SSH connections to other services operated by other entities. Here, the rogue server operator (who would otherwise have no way to determine the victim's private key) can derive the victim's private key, and then use it for unauthorized access to those other services. Because SSH is sometimes used to authenticate to Git services, it is possible that this vulnerability could be leveraged for supply-chain attacks on software maintained in Git. It is also conceivable that signed messages from PuTTY or Pageant are readable by adversaries more easily in other scenarios, but none have yet been disclosed. https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-p521-bias.… https://www.openwall.com/lists/oss-security/2024/04/15/6 https://git.tartarus.org/?p=simon/putty.git;a=commitdiff;h=c193fe9848f50a88… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214653] New: yast2 keyboard do not allow to set bépo (french)
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214653 Bug ID: 1214653 Summary: yast2 keyboard do not allow to set bépo (french) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jonathan(a)mercier.paris QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Dear, I give a try to OpenSuse Leap 15, but I am unable to go further as they any way to set bépo layout kexyboard. I try from: 1. Leap installer : as bépo was missing I choose the french layout once installation has finished: 2. sudo yast2 keyboard: same layout proposal than given from installer 3. sudo yast2/zypper search : nothing relevant found The point (2) and (3) was done by trying to find each letter as I own only bépo keyboard. This layout is present on RHEL, RockyLinux 7,8,9 and Fedora. It would be much appreciate to add it Thanks best regards -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1221438] New: trash_kcm conflicts kio-core
by bugzilla_noreply＠suse.com 26 May '24

26 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221438 Bug ID: 1221438 Summary: trash_kcm conflicts kio-core Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: thomas.rahimi(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, in the freshly updated OpenSUSE Tumbleweed version 20240311, the trash_kcm plugin for dolphin is missing in my installation. An attempt to install the plugin leads to the message, that this conflicts kio-core and thus would lead to the removal of the overall desktop environment. I'm by far not an expert in KDE Plasma packaging, but I suspect this dependency may be resolved without leading to this conflict. Looking forward to a resolution, if any is possible Kind regards Thomas -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1221512] New: scanner MFC-J5620DW not anymore recognized by xsane or YaST2
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221512 Bug ID: 1221512 Summary: scanner MFC-J5620DW not anymore recognized by xsane or YaST2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: Willy.Weisz(a)univie.ac.at QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since the last upgrade of Tumbleweed (including kernel 6.7.7) Xsane doesn't find my Brother MFC-J5620DW. Also YaST2 doesn't find it. Up to the previous level of Tumbleweed the scanner connected via WiFi worked fine with the Brother-provided driver (brscan4-0.4.4-4.x86_64). The printer part of the 4-in-1 MFC-J5620DW works as before. What's the problem? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214013] New: Shutdown did not finish (PC was not powered off, no obvious error logged)
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214013 Bug ID: 1214013 Summary: Shutdown did not finish (PC was not powered off, no obvious error logged) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868645 --> https://bugzilla.suse.com/attachment.cgi?id=868645&action=edit Screenshot when shutdown should power off the PC Maybe the issue is related to an MD-RAID being verified (see Bug 1214004), but the system did not power off. The last message in journal were: Aug 05 01:47:01 pc.site systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Aug 05 01:47:01 pc.site systemd[1]: Stopping Device-mapper event daemon... Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd detected break while being idle for 0 second(s), exiting. Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd shutting down. Aug 05 01:47:01 pc.site systemd[1]: dm-event.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Stopped Device-mapper event daemon. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Shutdown. Aug 05 01:47:01 pc.site systemd[1]: Reached target Late Shutdown Services. Aug 05 01:47:01 pc.site systemd[1]: systemd-poweroff.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Finished System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Shutting down. Aug 05 01:47:01 pc.site systemd-shutdown[1]: Syncing filesystems and block devices. Aug 05 01:47:03 pc.site systemd-shutdown[1]: Sending SIGTERM to remaining processes... Aug 05 01:47:03 pc.site haveged[1265]: haveged: Stopping due to signal 15 Aug 05 01:47:03 pc.site haveged[1265]: haveged starting up Aug 05 01:47:03 pc.site systemd-journald[1132]: Journal stopped I'm also adding a screenshot showing the last messages (that would last until I pressed the power button). Kernel was 5.14.21-150500.55.12-default The only other thing that looked unusual was this: ... Aug 05 01:46:59 pc.site systemd[1]: Stopped Record System Boot/Shutdown in UTMP. Aug 05 01:46:59 pc.site systemd[1]: Stopping Security Auditing Service... Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 is still in use. Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Failed to deactivate: Device or resource busy Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Control process exited, code=exited, status=1> Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Failed with result 'exit-code'. Aug 05 01:46:59 pc.site systemd[1]: Stopped Cryptography Setup for cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5. Aug 05 01:46:59 pc.site auditd[1679]: The audit daemon is exiting. Aug 05 01:46:59 pc.site kernel: kauditd_printk_skb: 50 callbacks suppressed Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.741:562): op=set audit_pid=0 old=1679 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site auditctl[3127]: enabled 0 Aug 05 01:46:59 pc.site auditctl[3127]: failure 1 Aug 05 01:46:59 pc.site auditctl[3127]: pid 0 Aug 05 01:46:59 pc.site auditctl[3127]: rate_limit 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_limit 64 Aug 05 01:46:59 pc.site auditctl[3127]: lost 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog 1 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time 15000 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time_actual 0 Aug 05 01:46:59 pc.site auditctl[3127]: No rules Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.853:563): op=set audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site systemd[1]: auditd.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Security Auditing Service. Aug 05 01:46:59 pc.site systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Create Volatile Files and Directories. Aug 05 01:47:00 pc.site systemd[1]: dracut-shutdown.service: Deactivated successfully. Aug 05 01:47:00 pc.site systemd[1]: Stopped Restore /run/initramfs on shutdown. Aug 05 01:47:00 pc.site systemd[1]: Stopped target Local File Systems. Aug 05 01:47:00 pc.site systemd[1]: Unmounting /home... ... The LUKS device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 contains the PV for the system VG, so it makes no sense trying to deactivate that before unmounting the system filesystems. Layout is like this: # pvs PV VG Fmt Attr PSize PFree /dev/mapper/cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 system lvm2 a-- 199,98g 3,88g # vgs VG #PV #LV #SN Attr VSize VFree system 1 6 0 wz--n- 199,98g 3,88g # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert android system Vwi-aotz-- 50,00g thinpool 55,19 floppies system Vwi-a-tz-- 1,00g thinpool 15,18 home system -wi-ao---- 50,00g root system -wi-ao---- 32,00g swap system -wi-ao---- 4,00g thinpool system twi-aotz-- 110,00g 25,23 22,76 (System was upgraded from Leap 15.4 where shutdown worked) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221702] New: Bluetooth headphones not reconnecting upon logging in
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221702 Bug ID: 1221702 Summary: Bluetooth headphones not reconnecting upon logging in Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: kjchmielewski(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873633 --> https://bugzilla.suse.com/attachment.cgi?id=873633&action=edit hwinfo I installed opensuse leap 15.6 beta on my laptop using official ISO, then I installed the pipewire-pulseaudio package. Next, I paired Bluetooth headphones in the Bluetooth settings, and the output device was correctly added in the sound settings. The problem is that after logging out or restarting the system, the headphones do not automatically connect if they are turned on all the time. I have to turn off and turn on the headphones' power again, or initiate connection manually for them to connect and become available as an output device in the sound settings. Is this expected beheviour? In leap version 15.5, this works as I expect, that is, after logging out or restarting, the Bluetooth connection disconnects, but upon logging in, the devices are automatically connected, even if they are continuously powered on and there is no need to turn them on again, or reconnect manually. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1222175] New: rustc 1.77 adds spurious -Cstrip=debuginfo to buildline
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222175 Bug ID: 1222175 Summary: rustc 1.77 adds spurious -Cstrip=debuginfo to buildline Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This produces policy-violating packages with missing debuginfo. See eg. bitwarden build log: https://build.opensuse.org/package/live_build_log/devel:languages:nodejs/bi… Seems to be a regression from rust 1.76. A robust workaround is to explicitely add `Cstrip=none` to RUSTFLAGS. (This is e.g. what Fedora already does) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219132] New: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219132 Bug ID: 1219132 Summary: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3889391/modules/Sysc tl/steps/136 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation # Test messages # Sysctl_kernel_sched_energy_aware # failure: ValueError: invalid literal for int() with base 10: '' Possibly this is a kernel issue - possibly the kernel just no longer exposes this and the test should not care. Please advise openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-sys-param-check@64bit fails in [Sysctl](https://openqa.opensuse.org/tests/3889391/modules/Sysctl/steps/136) ## Test suite description RAM size is set to 2048, some kernel parameters change with total RAM https://github.com/openSUSE/sys-param-check ## Reproducible Fails since (at least) Build [20240123](https://openqa.opensuse.org/tests/3888589) ## Expected result Last good: [20240122](https://openqa.opensuse.org/tests/3886345) (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 1

[Bug 1223117] New: Fcitx5 can't work for Qt6 based apps
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223117 Bug ID: 1223117 Summary: Fcitx5 can't work for Qt6 based apps Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: sauntor(a)yeah.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is only fcitx5 plugin for qt5 (a.k. fcitx5-qt5, which supplies /usr/lib64/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so), but no package supplies the the plugin for qt6! As for this reason, apps developed with Qt6 (like Qt Creator) can't use fcitx5 as the input method. Tumbleweed seems has the same problem too. -- You are receiving this mail because: You are on the CC list for the bug.

1 1