February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201484] Nautilus crashes when some extensions are enabled and an external drive is accessed
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1201484 https://bugzilla.suse.com/show_bug.cgi?id=1201484#c4 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE --- Comment #4 from Alynx Zhou <alynx.zhou(a)suse.com> --- Closed as noresponse. Feel free to reopen it if you still reproduce it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208714] New: HiDPI plasma 5.27.x
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208714 Bug ID: 1208714 Summary: HiDPI plasma 5.27.x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with plasma 5.27.x I have problems with HiDPI settings. I use a DELL XP13 notebook with an internal 4 K display (3840x2400 16:10) and an externel display with 2560x1440 (16:9). To achieve the best results for usage with and without the external display I wrote a small script, that uses xrandr to find out, if the external display is connected or not. If it is not connected, so that the internal display is the only one, the script is setting: GDK_SCALE=2 GDK_DPI_SCALE=0.5 XCURSOR_SIZE=48 SPOTIFY_SCALE=--force-device-scale-factor=2 QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCREEN_SCALE_FACTORS=eDP-1=2 PLASMA_USE_QT_SCALING=1 Except for the XCURSOR_SIZE this worekd perfectly up to plasma 5.26.x, but stopped working in 5.27.x. The script works as usual, but it seems as if the variables are ignored now by plasma and all KDE applications. For GTK I read, that GDK_* variables are no longer used with plasma 5.27.x, but I couldn't find anything regarding the QT_* variables. As long as this isn't solved, my notebook is completely unusable without the excternal display. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1208704] /etc/sysctl.conf handling
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208704 https://bugzilla.suse.com/show_bug.cgi?id=1208704#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kukuk(a)suse.com --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Ludwig Nussel from comment #0) > TODO: get upstream to read /etc/sysctl.conf agin or if that fails move it > with some migration script. I would move it: test -f /etc/sysctl.conf && mv /etc/sysctl.conf /etc/sysctl.conf.d/99-sysctl.conf Done. And we have a clean /etc without any hacks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173619] New: VUL-0: unbound: LPE from unbound to root
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1173619 Bug ID: 1173619 Summary: VUL-0: unbound: LPE from unbound to root Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: darin(a)darins.net Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- via security(a)suse.de: I believe to have found a configuration issue in the Unbound package. Or, depending on how you look at it, in the Unbound server itself. 1. Before starting the Unbound server, systemd routinely runs unbound-anchor. From 'systemctl cat unbound': ExecStartPre=/usr/bin/sudo -u unbound /usr/sbin/unbound-anchor -a /var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem As you can see this process is run as user unbound. 2. The Unbound server writes a pid file before dropping privileges, i.e. as root. It then chown's the file in a second step. 'grep username /etc/unbound/unbound.conf': username: "unbound" And from the Unbound source: https://github.com/NLnetLabs/unbound/blob/2a90e8fa1e22aa75d1cf67a1f71ebbf3f… As you can see in the source, Unbound doesn't check if there is already a symbolic link in place of the pid file. 3. openSUSE configures Unbound to create the pid file in a directory owned by the unbound user. 'grep pidfile /etc/unbound/unbound.conf': pidfile: "/var/run/unbound/unbound.pid" 'cat /usr/lib/tmpfiles.d/unbound.conf': D /run/unbound 0755 unbound unbound - 4. unbound-anchor is a nice little "do-one-thing-and-do-it-right" tool. But if it is compromised, and as it has write permission in the pid file directory and reliably runs before the server, an attacker could easily gain full root privileges by just creating a symbolic link /run/unbound/unbound.pid. 5. IMHO this would be best fixed in openSUSE by creating a root owned /run/unbound directory, or changing the pid file path to /run/unbound.pid or something like that. I think this would have the added advantage that openSUSE could ship and maybe enforce the Unbound AppArmor profile used in Debian and Ubuntu: https://gitlab.com/apparmor/apparmor-profiles/-/blob/master/ubuntu/20.04/us… With the current openSUSE setup there is the problem that if AppArmor filters CAP_DAC_OVERRIDE, Unbound has no permission to create a pid file in /run/unbound anymore. If you have questions please don't hesitate to contact me. Thanks for taking a look. Kind regards, Detlef -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1181471] New: libcurl hangs in a __poll below curl_easy_cleanup
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1181471 Bug ID: 1181471 Summary: libcurl hangs in a __poll below curl_easy_cleanup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: ma(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi Predro, a puzzle for the curl maintainers. I'm lost how to further investigate it. Maybe you've got an idea: [https://github.com/openSUSE/zypper/issues/364] - 'Proot' is used to chroot into an openSUSE TW system. This might be the reason, at least ZYPP never received a similar issue report, neither on aarch64 nor on any other architecture. From within the system, libzypp (via libcurl) is able to connect to e.g. download. opensuse.org (the log shows a successful head request). But when closing the connection libcurl reproducible hangs below a call to curl_easy_cleanup (for 20+ minutes before killing zypper). A stacktrace created by libzypp shows curl_easy_cleanup staying in a call to poll: > [bt]: (0) /lib64/libc.so.6 : __poll+0xec [0x7f8a71618c] > [bt]: (1) /usr/lib64/libcurl.so.4 : +0x5e088 [0x7f8a54f088] > [bt]: (2) /usr/lib64/libcurl.so.4 : +0x6024c [0x7f8a55124c] > [bt]: (3) /usr/lib64/libcurl.so.4 : +0x47240 [0x7f8a538240] > [bt]: (4) /usr/lib64/libcurl.so.4 : +0x4740c [0x7f8a53840c] > [bt]: (5) /usr/lib64/libcurl.so.4 : +0x1a3c4 [0x7f8a50b3c4] > [bt]: (6) /usr/lib64/libcurl.so.4 : +0x6e7d0 [0x7f8a55f7d0] > [bt]: (7) /usr/lib64/libcurl.so.4 : curl_easy_cleanup+0x40 [0x7f8a506db0] > [bt]: (8) /usr/lib64/libzypp.so.1722 : zypp::media::MediaCurl::disconnectFrom()+0x2c [0x7f8ada0bdc] > [bt]: (9) /usr/lib64/libzypp.so.1722 : zypp::media::MediaHandler::disconnect()+0x34 [0x7f8ad8bab4] The same is seen in the strace log: > https://github.com/openSUSE/zypper/files/5856500/zypper.strace.log.zip > (search for 'Releasing media http<http://download.opensuse.org' After writing the log line libzypp calls curl_easy_cleanup. Then you see just an endless loop of ppoll calls. Any idea/hint how to circumvent this is welcome. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1194660] New: Installation does not find repositories
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1194660 Bug ID: 1194660 Summary: Installation does not find repositories Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In current Leap 15.3 build for aarch64 - when booting from NET-ISO, system hangs at Adding Repositories -> Download documentation - when booting from DVD, when reading list of online repositories (Unable to download list of repositories or no repositories defined) (Yes, there is an online connection ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1181471] libcurl hangs in a __poll below curl_easy_cleanup
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1181471 http://bugzilla.opensuse.org/show_bug.cgi?id=1181471#c4 --- Comment #4 from Sebastian Parschauer <sebastian.parschauer(a)instana.com> --- This is actually why I use wget for everything as wget knows how to do SSL properly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181471] libcurl hangs in a __poll below curl_easy_cleanup
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1181471 http://bugzilla.opensuse.org/show_bug.cgi?id=1181471#c3 Sebastian Parschauer <sebastian.parschauer(a)instana.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian.parschauer@instan | |a.com --- Comment #3 from Sebastian Parschauer <sebastian.parschauer(a)instana.com> --- OMG, is this stuff still broken? I reported for SLES 15.0 already that libcurl violates the SSL network state machine by closing SSL connections three times in curl_easy_cleanup() instead of only once. I even had a patch for it dropping the two duplicate closes when I sill worked at SUSE. But nobody dared to apply it. Do tcpdumps and watch the RST flowing. See: https://bugzilla.suse.com/show_bug.cgi?id=1113787. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208003] Support EFI 32/64 bit mixed mode (Was: installation images do not support 32-bit EFI)
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208003 https://bugzilla.suse.com/show_bug.cgi?id=1208003#c25 --- Comment #25 from Stefan Hundhammer <shundhammer(a)suse.com> --- Lubos, this is waiting for input from you; see comment #8. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203261] [Build 272.2] openQA test fails in yast2_control_center - incorrect expectation of ports 15.5 update repo
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1203261 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |lubos.kocman(a)suse.com Flags|needinfo?(lubos.kocman@suse | |.com) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0