December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234617] New: [Build 20241213] openQA test fails in ovs_server: missing dep to ipsec
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234617 Bug ID: 1234617 Summary: [Build 20241213] openQA test fails in ovs_server: missing dep to ipsec Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4703817/modules/ovs_ server/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Dec 14 16:11:16 server ovs-monitor-ips[2379]: ovs| 3 | ovs-monitor-ipsec | ERR | traceback Traceback (most recent call last): File "/usr/share/openvswitch/scripts/ovs-monitor-ipsec", line 1398, in <module> main() File "/usr/share/openvswitch/scripts/ovs-monitor-ipsec", line 1342, in main monitor = IPsecMonitor(root_prefix, args.ike_daemon, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/openvswitch/scripts/ovs-monitor-ipsec", line 1072, in __init__ self.ike_helper.restart_ike_daemon() File "/usr/share/openvswitch/scripts/ovs-monitor-ipsec", line 245, in restart_ike_daemon subprocess.call([self.IPSEC, "restart"]) File "/usr/lib64/python3.11/subprocess.py", line 389, in call with Popen(*popenargs, **kwargs) as p: ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/subprocess.py", line 1026, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib64/python3.11/subprocess.py", line 1955, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: '/usr/sbin/ipsec' Dec 14 16:11:16 server systemd[1]: openvswitch-ipsec.service: Control process exited, code=exited, status=1/FAILURE openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-ovs-server@64bit fails in [ovs_server](https://openqa.opensuse.org/tests/4703817/modules/ovs_server/st… ## Test suite description Regression test for openvswitch-ipsec. Maintainer: Anna Minou ## Reproducible Fails since (at least) Build [20241213](https://openqa.opensuse.org/tests/4703619) ## Expected result Last good: [20241211](https://openqa.opensuse.org/tests/4698396) (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 2

[Bug 1233674] Webcamoid does not find uvc camera anymore
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233674 https://bugzilla.suse.com/show_bug.cgi?id=1233674#c4 --- Comment #4 from Frank Krüger <fkrueger(a)mailbox.org> --- It seems that no one (users/devs) cares about this crappy version of webcamoid, so how is the procedure to request the removal from Tumbleweed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234612] New: nagios install doesn't create /var/lib/nagios/rw and thus won't start
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234612 Bug ID: 1234612 Summary: nagios install doesn't create /var/lib/nagios/rw and thus won't start Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: novell(a)whitleymott.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- nagios install doesn't create /var/lib/nagios/rw and thus nagios won't start, until it is created. See https://forums.opensuse.org/t/nagios-started-then-deactivated-systemd-spec-… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1234055] New: Unable to reach dual monitor resolution with 2x 4k UHD side by side to 7680x2160
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234055 Bug ID: 1234055 Summary: Unable to reach dual monitor resolution with 2x 4k UHD side by side to 7680x2160 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: otrebor(a)hispeed.ch QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878829 --> https://bugzilla.suse.com/attachment.cgi?id=878829&action=edit xrandr log Hi I have a recently bought Lenovo X1 Carbon Gen 12 with an Intel Core Ultra 7 Processor 165U and 64Gig Memory. This Notebook is attached to a Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock via a TB4 cable. Plugged into the dock there are two EIZO FlexScan EV2740X Displays. Both attached via DisplayPort. The NB runs OpenSuse Leap 15.6 all patches applied. Also all available firmware updates have been installed via fwupdmgr. The problem is, that this setup does not run with both EIZO displays set to 4k UHD resolution side-by-side. (in 7680x2160 resolution setup). This fails with or without having the internal NB display active or not. Another NB running Win11 with an Nvidia Graphics card attached to the same dock runs both display just fine at 4k UHD resolution. So, i guess the problem lies with the Lenovo X1 Carbon and its Intel i915 graphics driver. According to the intel specs here this should work: https://www.intel.com/content/www/us/en/products/sku/237329/intel-core-ultr… The setup runs fine when i set the resolution on both EIZOS to the lower 2560x1440 and arrange them side by side. I'm a bit puzzled, as is this limited by design or is there something wrong with the drivers. In single display config both displays run fine at 4k UHD (3840x2160) mode. I have attached a number of log files. If you wouldn't mind helping me on this, I'd be grateful. I'm no hardware or kernel geek. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1234621] [SELinux] full relabelling required after booting to recovery/single-user mode
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234621 https://bugzilla.suse.com/show_bug.cgi?id=1234621#c5 --- Comment #5 from pallas wept <pallaswept(a)proton.me> --- Ahhh my mistake then! Thanks for the correction. So, is there an existing method, a 'right way' to ensure that "security=selinux" is added to the recovery mode entries in grub? Is it normally done, by the installer, by a package, only manually, not at all (intentionally) or not at all (unintentionally)? Probably something else that I didn't think of yet? :) A little bit off-topic, but I also wonder how does a new installation add that parameter, for the normal boot entries (which I did manually already per the document linked above)? Is that an installer feature, packaged, etc? Although that's working fine for me now, I wonder because I'd like to understand how it works for the future of my machines. I couldn't see anything about it in packages so I figured that the installer must modify /etc/default/grub ... but that's just a guess. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232496] [SELinux] sl micro 5.5 has enforcing=1 in grub config, so /etc/selinux/config is ignored
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232496 https://bugzilla.suse.com/show_bug.cgi?id=1232496#c6 --- Comment #6 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2024:4334-1: An update that has three fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-ru-20244334-1 Category: recommended (moderate) Bug References: 1216052, 1232496, 1233789 Maintenance Incident: [SUSE:Maintenance:36558](https://smelt.suse.de/incident/36558/) Sources used: openSUSE Leap Micro 5.5 (src): selinux-policy-20230511+git21.861b7a02-150500.3.26.1 SUSE Linux Enterprise Micro 5.5 (src): selinux-policy-20230511+git21.861b7a02-150500.3.26.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216052] selinux failure with sssd
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1216052 https://bugzilla.suse.com/show_bug.cgi?id=1216052#c9 --- Comment #9 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2024:4334-1: An update that has three fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-ru-20244334-1 Category: recommended (moderate) Bug References: 1216052, 1232496, 1233789 Maintenance Incident: [SUSE:Maintenance:36558](https://smelt.suse.de/incident/36558/) Sources used: openSUSE Leap Micro 5.5 (src): selinux-policy-20230511+git21.861b7a02-150500.3.26.1 SUSE Linux Enterprise Micro 5.5 (src): selinux-policy-20230511+git21.861b7a02-150500.3.26.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234469] YaST2 Qt UI can't connect to display
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234469 https://bugzilla.suse.com/show_bug.cgi?id=1234469#c9 --- Comment #9 from Stefan Hundhammer <shundhammer(a)suse.com> --- In my /etc/sudoers, long ago I added this line which IMHO is a life-saver: Defaults env_keep = "DISPLAY QT_QPA_PLATFORMTHEME LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE" Those are the environment variables that I want kept when I invoke 'sudo'; in particular DISPLAY. But surely somebody will pop up who will claim that this is so very unsafe... it might actually make the thing usable and not just nailed down beyond any use by mere mortals. Important: That line must be after all 'include' etc. commands in the file which might overwrite it again. That's also why I keep it in /etc/sudoers and not in /etc/sudoers.d where it's anybody's guess in what order what file outside of the directory (e.g. /etc/sudoers) will be evaluated. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234469] YaST2 Qt UI can't connect to display
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234469 https://bugzilla.suse.com/show_bug.cgi?id=1234469#c8 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEW |RESOLVED Flags|needinfo?(hoiatl@spreadsuse | |.net) | --- Comment #8 from Stefan Hundhammer <shundhammer(a)suse.com> --- So it looks like your 'sudo' environment changed with one of those recent updates. In general, ony of 'kdesu' or 'gnomesu' (or 'xdg-su' which is an elaborate alias for them) is recommended to start a GUI program with root permissions on your user desktop. AFAIK the major desktops use those to start YaST Qt (or other GUI programs that need root permissions) from the menus. But when you try the same from a command line, you need to invoke them manually, of course. 'sudo' can work, but only if you tweaked your 'sudo' configuration in /etc/sudoers to keep some environment variables like $DISPLAY; the default 'sudo' setup is to forget almost all of them. That may be more secure, but it's a royal PITA; it's an unneccessary incentive for users to work more, not less, with root permissions. 'su' behaves a bit differently; IIRC it doesn't just kill your carefully set up environment the way 'sudo' does. That might be just that little difference that made it work for you. But there are also the permissions of the desktop itself. X11 has elaborate methods to close it even to root processes, so you need to open it a bit to let a root GUI program use it (both ways, displaying the GUI and receiving input from your keyboard and mouse). There is the old general 'xhost +' command which all security experts advise against. I am sure Wayland has equivalent methods, but I have been a happy X11 user since about 1990, so I don't know much about that. But please try 'kdesu' (on KDE) or 'gnomesu' (on GNOME or Xfce) first. That should do the trick. But anyway, this is not a problem on the YaST level. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234448] When sharing Yubikey from the host, I get "can't set config #1, error -32"
by bugzilla_noreply＠suse.com 16 Dec '24

16 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234448 https://bugzilla.suse.com/show_bug.cgi?id=1234448#c5 --- Comment #5 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Alberto Planas Dominguez from comment #4) > (In reply to Fabian Vogt from comment #3) > > Right, that's unrelated and means your user is not member of the "kvm" > > group. > > I see, now I have: > > spice-client-error-quark: Could not redirect Yubico YubiKey OTP+FIDO+CCID > [1050:0407] at 1-73: Device is in use by another application (0) > > For what I read this is similar to the -EPIPE error that I had? One > explanation is that libusb is not able to delegate ownership. Did you remove the device from the static redirection to the VM? If yes, it might be some other process that has the usb device opened: fuser sudo fuser /dev/bus/usb/001/XXX (with XXX being the device number of the yubikey on that bus). -- You are receiving this mail because: You are on the CC list for the bug.

1 0