May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222716] New: libssh tries to read config from wrong crypto-policies location
by bugzilla_noreply＠suse.com 18 Feb '25

18 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1222716 Bug ID: 1222716 Summary: libssh tries to read config from wrong crypto-policies location Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: pmonrealgonzalez(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- libssh-config ships /etc/libssh/libssh_server.config which contains # Parse system-wide crypto configuration file Include /usr/etc/crypto-policies/back-ends/libssh.config But there is no such file. It's supposed to be /etc/crypto-policies/back-ends/libssh.config Probably caused by the fix for bug 1211718. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222534] New: No wired network after hibernation
by bugzilla_noreply＠suse.com 18 Feb '25

18 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1222534 Bug ID: 1222534 Summary: No wired network after hibernation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: jonzn4suse(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20240405 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.4-rc1-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics Memory: 62.1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP ProBook 455 15.6 inch G9 Notebook PC System Version: SBKPF I can turn on WiFi and it works, but to fix the wired issue, I have to reboot. The below logs keeps repeating until a reboot. LOGS: Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.4741] device (enp1s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <warn> [1712657390.4744] device (enp1s0): Activation: failed for connection 'Wired Connection' Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.4744] device (enp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5233] dhcp4 (enp1s0): canceled DHCP transaction Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5233] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds) Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5233] dhcp4 (enp1s0): state changed no lease Tuesday, April 9, 2024 6:09:50 AM EDT kernel r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control rx/tx Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon Files changed, reloading. Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon No service file found in /etc/avahi/services. Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5760] policy: auto-activating connection 'Wired Connection' (21000dbf-984d-4441-91e7-1f4c01a5b834) Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5763] device (enp1s0): Activation: starting connection 'Wired Connection' (21000dbf-984d-4441-91e7-1f4c01a5b834) Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5764] device (enp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5766] device (enp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT kernel r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control rx/tx Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5937] device (enp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5939] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds) Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon Files changed, reloading. Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon No service file found in /etc/avahi/services. I will also test sleep to see if it has the same issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1219070] New: Chromium won't play youtube videos
by bugzilla_noreply＠suse.com 18 Feb '25

18 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1219070 Bug ID: 1219070 Summary: Chromium won't play youtube videos Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: aloisio(a)gmx.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since the last two updates, using plasma/wayland, playing won't start and a generic error is shown. The console prints: ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! Last functioning version is 119.0.6045.199-bp155.2.61.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1221568] New: VUL-0: CVE-2024-22513: python-djangorestframework-simplejwt: information disclosure via inactive user
by bugzilla_noreply＠suse.com 17 Feb '25

17 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1221568 Bug ID: 1221568 Summary: VUL-0: CVE-2024-22513: python-djangorestframework-simplejwt: information disclosure via inactive user Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/393624/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: mmachova(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: carlos.lopez(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- djangorestframework-simplejwt version 5.3.1 and before is vulnerable to information disclosure. A user can access web application resources even after their account has been disabled due to missing user validation checks via the for_user method. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-22513 https://www.zerodayinitiative.com/advisories/ZDI-24-101/ https://www.cve.org/CVERecord?id=CVE-2024-22513 https://github.com/dmdhrumilmistry/CVEs/tree/main/CVE-2024-22513 https://bugzilla.redhat.com/show_bug.cgi?id=2269822 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1212956] New: Linphone 5.0.16 fails to launch. Symbol lookup error
by bugzilla_noreply＠suse.com 17 Feb '25

17 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1212956 Bug ID: 1212956 Summary: Linphone 5.0.16 fails to launch. Symbol lookup error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: lair.retention968(a)4wrd.cc QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When launching Linphone, the following symbol lookup error message is shown: linphone: symbol lookup error: /lib64/liblinphone.so.10: undefined symbol: _ZN4lime11LimeManager6updateERKSt8functionIFvNS_14CallbackReturnENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEE linphone - 5.0.16-1.3 liblime - 5.2.73-1.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1225296] New: Dual monitor not recognised after upgrade 15.5 to 15.6
by bugzilla_noreply＠suse.com 15 Feb '25

15 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1225296 Bug ID: 1225296 Summary: Dual monitor not recognised after upgrade 15.5 to 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: martin.schmidt(a)io-warnemuende.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Moin, moin, I am using openSUSE 15.5 on an old intel based x86 PC, equipped with a simple nvidia gforce and two monitors. The monitors are using a displayport connnection from the graphics card to the monitors via an Y-shaped cable. Both monitors are recognised correctly and can be configured to form a single graphical work space, when the system is up and running. After upgrading to openSUSE 15.6 this does not work any more. When booting, monitor 1 shows some firmware screen and the openSUSE boot screen, where the OS version (several subversions of 15.6 and frozen snapshots of 15.5) can be selected. Using the default option (15.6 from harddrive), the output of the boot process is moving to monitor 2, but monitor 1 is going to a "power saving sleep mode" and stays inactive frome here on. The boot process is finished correctly with monitor 2 as the only graphical device. Monitor 1 cannot be activated again. Switching off monitor 2 before booting, the system comes up without any valid output device. Monitor 1 goes to sleep after the system boot started. I did not check the system status with a remote ssh-connection yet. Switching off monitor 1 before booting, lets the system come up completely with monitor 2. Also the initial hardware screen is diplayerd there. In turn, booting from a read-only snapshot with openSUSE 15.5, both monitors are used as before. The nouveau-dri drivers are used, no propriatary nvidia driver is installed. Some upgrade history: - just to test, if the few graphic card cores could be used in a cuda environment, cuda was installed under 15.5. This failed and cuda was deinstalled. However, when upgrading later from 15.5 to 15.6 the cuda development environment was reinstalled automatically together with nvidia drivers. As a result the nvidia drivers allowed only for a single low resolution vga monitor. May be, this happened, since the nvidia repository was not deleted and there was some leftover from the cuda test. - with the ascii-yast the nvidia drivers (gforce003/004) and cuda could be removed and the nouveau-dri drivers where reinstalled - together with dependencies. This allows for a single monitor OS_15.6 system with high resolution, but the second monitor (monitor 1) is lost during the boot process as described above. Before I try to install from scratch just with the hope that the error goes away, I am reporting this strange behaviour here. May be, this helps to streamline the distribution. Any hints are very welcome - especially how to modify the bootloader options. Cheers, Martin Schmidt -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1221224] New: java-21-openjdk build-time race
by bugzilla_noreply＠suse.com 15 Feb '25

15 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1221224 Bug ID: 1221224 Summary: java-21-openjdk build-time race 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: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1102408 Target Milestone: --- Found By: --- Blocker: --- Created attachment 873384 --> https://bugzilla.suse.com/attachment.cgi?id=873384&action=edit diff from build-compare While working on reproducible builds for openSUSE, I found that our java-21-openjdk binaries vary between 1-core and 4-core builds. https://rb.zq1.de/compare.factory-20240228/diffs/java-21-openjdk-compare.out has the diff (also attached) There may be additional issues from ASLR that I am still investigating. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1218136] New: Add Turkish F layout
by bugzilla_noreply＠suse.com 14 Feb '25

14 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1218136 Bug ID: 1218136 Summary: Add Turkish F layout Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: emir_sari(a)icloud.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Whilst installing Krypton, in the installer, there is no Turkish F layout, which also a common layout in Turkey, and used alongside the Q layout. Please add it as another option in the drop-down list. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1224403] New: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage'
by bugzilla_noreply＠suse.com 14 Feb '25

14 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1224403 Bug ID: 1224403 Summary: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- bpftrace fails to attach probe: # echo -e "\ninterval:s:5 { exit(); }" | cat /usr/share/bpftrace/tools/swapin.bt - | bpftrace - stdin:1-16: WARNING: swap_readpage is not traceable (either non-existing, inlined, or marked as "notrace"); attaching to it will likely fail Attaching 3 probes... cannot attach kprobe, probe entry may not exist ERROR: Error attaching probe: 'kprobe:swap_readpage' # echo $? 255 It has been failing for some time (at least since 20240412, but probably much longer). -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1217747] New: colord: reproducible builds: icc varies from CPU
by bugzilla_noreply＠suse.com 13 Feb '25

13 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1217747 Bug ID: 1217747 Summary: colord: reproducible builds: icc varies from CPU Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://github.com/omgovich/colord/issues/122 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: gnome-bugs(a)suse.de Blocks: 1100677 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for ALP+openSUSE, I found that our colord package varied from differences in .icc files caused by differences in build machine CPU capabilities (probably AVX) Also filed upstream at https://github.com/omgovich/colord/issues/122 but they seem inactive. You find a reproducer and more details there. -- You are receiving this mail because: You are on the CC list for the bug.

1 4