August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201569] claws-mail dependency prevents upgrade
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201569 https://bugzilla.suse.com/show_bug.cgi?id=1201569#c3 Marcus R�ckert <mrueckert(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Marcus R�ckert <mrueckert(a)suse.com> --- This is already solved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201966] Package yast2-installation requires xrdb and ultimately libX*
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201966 https://bugzilla.suse.com/show_bug.cgi?id=1201966#c8 --- Comment #8 from David Diaz <dgonzalez(a)suse.com> --- (In reply to Ladislav Slez�k from comment #7) > The fix has been backported in yast2-x11-4.4.2 > (https://github.com/yast/yast-x11/pull/26) and yast2-installation-4.4.56 > (https://github.com/yast/yast-installation/pull/1056) Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202090] New: [SELinux] mdadm / mdmonitor systemd service not allowed to write env (mdadm_env.sh)
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202090 Bug ID: 1202090 Summary: [SELinux] mdadm / mdmonitor systemd service not allowed to write env (mdadm_env.sh) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: alexander.wenzel(a)qbeyond.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The mdmonitor and mdcheck systemd service create a ENV file before starting. --- cut --- EnvironmentFile=-/run/sysconfig/mdadm ExecStartPre=-/usr/lib/mdadm/mdadm_env.sh --- cut --- Due to a bad type transition, the shell script is not allowed to write the ENV file. The script will create a directory "sysconfig" under /var/run [var_run_t] in the context of [unconfined_service_t]. The directory will be labeled with [net_conf_t], which is not accessible by [init_t]. Flow: systemd [init_t] -> executes mdadm_env.sh [init_t] -> mkdir sysconfig [unconfined_service_t] -> echo ENV [init_t] -- denied --- cut --- # sesearch -T -s init_t -t var_run_t | grep net_conf_t type_transition init_t var_run_t:dir net_conf_t cloud-init; # sesearch -T -s unconfined_service_t -t var_run_t | grep net_conf_t type_transition unconfined_service_t var_run_t:dir net_conf_t; --- cut --- Tested with a freshly installed openSUSE Tumbleweed 20220731 in "server" role and SELinux set in permissive mode. --- cut --- # ausearch -m AVC -ts boot -se init_t -c mdadm_env.sh ---- time->Wed Aug 3 09:00:15 2022 type=AVC msg=audit(1659510015.835:162): avc: denied { add_name } for pid=1505 comm="mdadm_env.sh" name="mdadm" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=dir permissive=1 ---- time->Wed Aug 3 09:00:15 2022 type=AVC msg=audit(1659510015.835:163): avc: denied { create } for pid=1505 comm="mdadm_env.sh" name="mdadm" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1 ---- time->Wed Aug 3 09:00:15 2022 type=AVC msg=audit(1659510015.835:164): avc: denied { write } for pid=1505 comm="mdadm_env.sh" path="/run/sysconfig/mdadm" dev="tmpfs" ino=1283 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1 ---- time->Wed Aug 3 09:00:15 2022 type=AVC msg=audit(1659510015.835:165): avc: denied { append } for pid=1505 comm="mdadm_env.sh" name="mdadm" dev="tmpfs" ino=1283 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:net_conf_t:s0 tclass=file permissive=1 --- cut --- IMHO adding [net_conf_t] to the init policy [init_t] seems not right. Maybe adding mdadm_env.sh to the raid policy [mdadm_exec_t] is a better way to go? As this is an SUSE specific issue, I'm not sure, where to add a patch (selinux policy upstream / obs - policy project). Quickly reproducible with: --- cut --- # runcon system_u:object_r:init_t:s0 mkdir /run/transition_ok # runcon system_u:object_r:init_t:s0 bash -c "mkdir /run/transition_bad" # ls -dlZ /run/transition* --- cut --- To watch transitions, use strace with selinux compiled in. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202043] firewalld can no more use ipsets with iptables
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202043 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187513] New: Spanish keyboard randomly stops working in some applications
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187513 Bug ID: 1187513 Summary: Spanish keyboard randomly stops working in some applications 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: teo8976(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On Spanish keyboards (among others, I guess), you type accented characters such as "��" or "��" by hitting the key for the accent ("`" or "��" in the examples above) followed by the letter. This normally works in all applications that I've ever tried in OpenSUSE. Starting recently, it sometimes randomly happens that this suddenly stops working in some applications but not others. When this happens, hitting the accent key followed by a letter results in just the plain unaccented letter. For example, "`"+"e" results in "e" instead of "��". Until today (and since it started happening a few days ago), I had only seen this in Kate. It would stop working in Kate while still working in other applications (usually I would try Chrome) and more importantly, it would get fixed by restarting Kate. Today it happened once more but it also started failing in Konsole and Telegram Desktop. This time, restarting any of the affected application would NOT fix that application. And even restarting all the apparently affected applications didn't. Rebooting did. I reported this to KDE because initially I was observing it only in Kate but they told me: """" Looks like the Qt key composition is broken for you. That would explain why this fails for Qt applications (Telegram Desktop is Qt based, too). I would propose to report this upstream to openSUSE. This seems to be no KDE/Kate specific issue. """" https://bugs.kde.org/show_bug.cgi?id=438820 Operating System: openSUSE Tumbleweed 20210612 KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9-1-default (64-bit) Graphics Platform: X11 Processors: 8 �� Intel�� Core�� i7-1065G7 CPU @ 1.30GHz Memory: 7.3 GiB of RAM Graphics Processor: Mesa DRI Intel�� Iris�� Plus Graphics -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1201966] Package yast2-installation requires xrdb and ultimately libX*
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201966 https://bugzilla.suse.com/show_bug.cgi?id=1201966#c7 Ladislav Slez�k <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Ladislav Slez�k <lslezak(a)suse.com> --- The fix has been backported in yast2-x11-4.4.2 (https://github.com/yast/yast-x11/pull/26) and yast2-installation-4.4.56 (https://github.com/yast/yast-installation/pull/1056) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194199] zypper dup on multiple HPE servers freezes, resulting system will not start
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1194199 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |zypp-maintainers(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190949] pam_csync: use %_pam_moduledir
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190949 http://bugzilla.opensuse.org/show_bug.cgi?id=1190949#c3 --- Comment #3 from Ludwig Nussel <lnussel(a)suse.com> --- https://build.opensuse.org/request/show/992459 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201572] gimp-plugin-resynthesizer not installable anywhere but Factory?
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201572 https://bugzilla.suse.com/show_bug.cgi?id=1201572#c3 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar(a)opensuse.org --- Comment #3 from Alynx Zhou <alynx.zhou(a)suse.com> --- (In reply to Lance Haverkamp from comment #1) > Oh, and the experimental installation for 15.4 fails installation with: > > Problem: nothing provides 'gimp-plugins-python' needed by the to be > installed gimp-plugin-resynthesizer-2.0.3.20210530-lp154.5.2.x86_64 This is because the SLE version of gimp does not build gimp-plugins-python, and Leap 15.4 uses the same binary with SLE. Maybe Dominique can help us on why this is not enabled on SLE. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199404] /sys/firmware/efi/efivars/dump-* not cleaned up, grub gone and failed to reinstall
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1199404 https://bugzilla.suse.com/show_bug.cgi?id=1199404#c2 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |ro(a)suse.com --- Comment #2 from Chenzi Cao <chcao(a)suse.com> --- I assign it to filesystem maintainer to take a look at it, please feel free to reassign whenever necessary, thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 0