February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1206292] [SELinux] Wine/Proton not working reliably with default SELinux configuration
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1206292 Hu <cathy.hu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |FEATURE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208268] New: xdm does not launch configured default-xsession.desktop
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208268 Bug ID: 1208268 Summary: xdm does not launch configured default-xsession.desktop Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864904 --> http://bugzilla.opensuse.org/attachment.cgi?id=864904&action=edit .tgz of journalctl -b with cmdline including debug rd.debug https://paste.opensuse.org/pastes/7d8d9da97046 contains a journal produced without debug rd.debug on kernel cmdline (28 day expire). Original summary: xdm does not launch configured default-xsession.desktop # inxi -GSxxz System: Kernel: 5.14.21-150500.39-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 Console: pty pts/1 (vt 7) DM: XDM Distro: openSUSE Leap 15.5 Alpha Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu v: kernel arch: GCN-2 ports: active: DP-1, DVI-D-1, HDMI-A-1, VGA-1 empty: none bus-ID: 00:01.0 chip-ID: 1002:130f Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 7840x1440 s-dpi: 120 Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: primary,left model: NEC EA243WM res: 1920x1200 dpi: 94 diag: 612mm (24.1") Monitor-2: DP-1 mapped: DisplayPort-0 pos: center-r model: Acer K272HUL res: 2560x1440 dpi: 109 diag: 686mm (27") Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: right model: Dell P2213 res: 1680x1050 dpi: 90 diag: 558mm (22") Monitor-4: VGA-1 mapped: VGA-0 pos: center-l model: Lenovo L2251x Wide res: 1680x1050 dpi: 90 diag: 559mm (22") API: OpenGL v: 4.6 Mesa 22.3.4 renderer: AMD Radeon R7 Graphics (kaveri LLVM 15.0.7 DRM 3.49 5.14.21-150500.39-default) direct-render: Yes ## installation is a zypper dup from an unpreserved 15.4. # inxi -C CPU: Info: quad core model: AMD A10-7850K Radeon R7 12 Compute Cores 4C+8G bits: 64 type: MT MCP cache: L2: 4 MiB Speed (MHz): avg: 1700 min/max: 1700/4000 cores: 1: 1700 2: 1700 3: 1700 4: 1700 # ll /usr/share/xsessions/ total 16 drwxr-xr-x 2 root root 2048 Feb 14 19:34 . drwxr-xr-x 175 root root 6144 Feb 14 19:27 .. lrwxrwxrwx 1 root root 42 Jan 27 00:54 default.desktop -> /etc/alternatives/default-xsession.desktop lrwxrwxrwx 1 root root 13 Apr 22 2022 icewm-session.desktop -> icewm.desktop -rw-r--r-- 1 root root 2498 Apr 22 2022 icewm.desktop lrwxrwxrwx 1 root root 15 Jan 27 00:56 kde-plasma.desktop -> plasma5.desktop -rw-r--r-- 1 root root 2975 Jan 27 00:44 plasma5.desktop # update-alternatives --config default-displaymanager There are 2 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/lib/X11/displaymanagers/xdm 10 auto mode 1 /usr/lib/X11/displaymanagers/console 5 manual mode * 2 /usr/lib/X11/displaymanagers/xdm 10 manual mode Press <enter> to keep the current choice[*], or type selection number: # update-alternatives --config default-xsession.desktop There are 2 choices for the alternative default-xsession.desktop (providing /usr/share/xsessions/default.desktop). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/share/xsessions/plasma5.desktop 25 auto mode 1 /usr/share/xsessions/icewm-session.desktop 15 manual mode * 2 /usr/share/xsessions/plasma5.desktop 25 manual mode Press <enter> to keep the current choice[*], or type selection number: # head /usr/share/xsessions/default.desktop [Desktop Entry] Type=XSession Exec=/usr/bin/startplasma-x11 TryExec=/usr/bin/startplasma-x11 DesktopNames=KDE Name=Plasma (X11) # rpm -qa | grep -i dm- xdm-1.1.11-150400.23.6.x86_64 mdadm-4.2-150500.1.8.x86_64 # journalctl -b | grep aile # boot without cmdline debug rd.debug Feb 14 20:58:55 ara88 systemd[1]: haveged.service: Failed with result 'exit-code'. # journalctl -b | grep aile | wc -l # boot with cmdline debug rd.debug 1745 # cat .xsession-errors-:0 Environment variable $XAUTHORITY not set, ignoring. warning: output DP-1 not found; ignoring warning: output VGA-1 not found; ignoring warning: output DVI-D-1 not found; ignoring warning: output HDMI-1 not found; ignoring gpg-connect-agent: no gpg-agent running in this session gpg-connect-agent: no gpg-agent running in this session # Starting in multi-user.target, startx /usr/bin/startice produces a normally working session. Starting in multi-user.target, startx /usr/bin/startplasma-x11 produces in journal: kapplymousethem[864]: segfault at 0 ip 00007f413f8e0640 sp 00007ffc20ad6c48 error 4 in libQt5Gui.so.5.15.2[7f413f758000+6f1000] kcminit_startup[900]: segfault at 0 ip 00007f59a42a8640 sp 00007fffea85f5d8 error 4 in libQt5Gui.so.5.15.2[7f59a4120000+6f1000] which reinstalling libQt5Gui5 fails to fix. Problem Manifestation: Starting in graphical target, login with alternatives default set to either plasma or icewm results in an Xterm with no window decorations, no toolbar, pale gray background, and no response to mouse clicks anywhere. If with update-alternatives I have default on plasma, it causes popup window reporting kglobalaccel5 segfault. Dismissal produces a ksplashqml segfault report. Dismissal leaves a black screen with mouse pointer and nothing else. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1206292] [SELinux] Wine/Proton not working reliably with default SELinux configuration
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1206292 https://bugzilla.suse.com/show_bug.cgi?id=1206292#c2 Hu <cathy.hu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |cathy.hu(a)suse.com Resolution|--- |FIXED --- Comment #2 from Hu <cathy.hu(a)suse.com> --- Hi Imo, thank your for the question. Just to explain a bit the background why this boolean is not set per default on your MicroOS desktop: The selinux policy packages for MicroOS are build based on the rpm packaging definitions in openSUSE:Factory [0]. This is the same definition that also builds tumbleweed, non-desktop MicroOS and also where SLE distros branch off at some point in time. SELinux policies exist to protect your system. However, they are very specialized to the use case of a system. The policy in openSUSE:Factory is specialized on the use case of server loads, because that is our main target. This, however does not seem to be your use case, which is running a desktop system. In this case, some default policy rules may be too strict or do not fit to your use case. That is the reason why the SELinux project introduced SELinux booleans that allow you to modify the standard policy to your needs and use case. The recommended way from us and also intended SELinux-ish-way to solve this would be that people who are affected set the boolean according to the MicroOS desktop documentation [1] However, as security team, we can unfortunately not set this boolean as default as it would make the default policy more insecure. If you have any more questions, please feel free to reach out and reopen the bug. Kind regards, Cathy [0] https://build.opensuse.org/package/show/openSUSE:Factory/selinux-policy [1] https://en.opensuse.org/Portal:MicroOS/Desktop#Steam_Proton,_Bottles,_WINE,… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208260] Thunar 4.18.3 lp154 - Regular Expression not available in Bulk Renamer dialog
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208260 Manfred Hollstein <manfred.h(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208260] Thunar 4.18.3 lp154 - Regular Expression not available in Bulk Renamer dialog
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208260 https://bugzilla.suse.com/show_bug.cgi?id=1208260#c2 Manfred Hollstein <manfred.h(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjurg.orsku(a)gmail.com Flags| |needinfo?(bjurg.orsku@gmail | |.com) --- Comment #2 from Manfred Hollstein <manfred.h(a)gmx.net> --- The new version has been built in the X11:xfce repository. Can you please install that update and report back if it works for you? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207963] New: kdelibs3 3.5.10-241.19 causes kmail3 to stop being able to send
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207963 Bug ID: 1207963 Summary: kdelibs3 3.5.10-241.19 causes kmail3 to stop being able to send 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: michael(a)actrix.gen.nz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In TW 20230202 +, KDE3:kmail3 can no longer send via SMTP and SSL/TLS pop no longer works. The TW version doesn't seem to matter. The cause is something in kdelibs3 3.5.10-241.19, possibly in combination with kdepim3 3.5.10-290.18. There is a workaround... I used /var/cache/zypp with rpm --upgrade --force to revert to kdepim3-3.5.10-290.18.x86_64.rpm, which had no effect, but also reverting to kdelibs3-3.5.10-241.16.x86_64.rpm got everything working again. The following was logged, seems to point to protocol issues, >> Feb 06 13:48:46 ksmserver[13902]: 40CF65DC027F0000:error:0A000102:SSL routines:ssl_choose_client_version:unsupported protocol:ssl/statem/statem_lib.c:1952: >> Feb 06 13:48:49 ksmserver[13902]: 40CF65DC027F0000:error:0A000102:SSL routines:ssl_choose_client_version:unsupported protocol:ssl/statem/statem_lib.c:1952: >> Feb 06 13:48:58 ksmserver[13923]: kioslave: ####### CRASH ###### protocol = smtps pid = 13923 signal = 11 >> Feb 06 13:49:00 ksmserver[13927]: kioslave: ####### CRASH ###### protocol = smtps pid = 13927 signal = 11 >> Feb 06 13:49:27 ksmserver[13902]: 40CF65DC027F0000:error:0A000102:SSL routines:ssl_choose_client_version:unsupported protocol:ssl/statem/statem_lib.c:1952: >> Feb 06 13:49:37 ksmserver[13902]: 40CF65DC027F0000:error:0A000102:SSL routines:ssl_choose_client_version:unsupported protocol:ssl/statem/statem_lib.c:1952: >> Feb 06 13:49:49 ksmserver[13946]: kioslave: ####### CRASH ###### protocol = smtps pid = 13946 signal = 11 Details of the SMTP server, no ports work, not even 25 Port with SSL: 465 or 587 Port with TLS: 587 Port without SSL/TLS: 25 Authentication method: Password Requires sign-in Yes SSL and TLS pop on 995 stopped working, but unencrypted port 110 still works: Port with SSL/TLS: 995 Port without SSL/TLS: 110 Username: Your username Password: Your password Authentication Type: Password -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1191578] shadow: drop useradd.local etc
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1191578 https://bugzilla.suse.com/show_bug.cgi?id=1191578#c3 --- Comment #3 from Michael Vetter <mvetter(a)suse.com> --- Dropping this now. I edited your changes entry to mention all the files/patches that got dropped and removed the userdel-script.patch as well. SR#1066133 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191578] shadow: drop useradd.local etc
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1191578 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207239] New: YaST build fails: Ruby 3.2: URI("dir:///foo").to_s no longer returns "dir:/foo"
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207239 Bug ID: 1207239 Summary: YaST build fails: Ruby 3.2: URI("dir:///foo").to_s no longer returns "dir:/foo" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: YaST2 Assignee: mvidner(a)suse.com Reporter: mvidner(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- This is a continuation of https://bugzilla.suse.com/show_bug.cgi?id=1206419 Since 3.2.0, there's been a bug fix it seems and URI::Generic no longer omits the host component (it is "" instead of nil) $ ruby -r uri -e 'p URI("dir:///foo").to_s' "dir:/foo" # up to 3.1.0 "dir:///foo" # since 3.2.0 YaST builds fail in Staging:H - yast2-packager - yast2-configuration-manaegment -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1191578] shadow: drop useradd.local etc
by bugzilla_noreply＠suse.com 16 Feb '23

16 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1191578 https://bugzilla.suse.com/show_bug.cgi?id=1191578#c1 --- Comment #1 from Michael Vetter <mvetter(a)suse.com> --- Hi Ludwig, thanks for https://build.opensuse.org/request/show/1065945 and sorry for the long delay here! Unfortunately I'm also not sure if this is still used by anything. useradd-script.patch seems to be added in 2012 by Thorsten. But no bug or fate is referenced. After such a long time I doubt anybody remembers details. useradd.local reference later bugs bsc#1178296 and bsc#1173321. I will try to find out more and if I can't I guess we just take your change and see if something breaks? BTW in your SR you forgot to remove userdel-script.patch. -- You are receiving this mail because: You are on the CC list for the bug.

1 0