February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1206572] nVidia driver gfxG06 RPM doesn't install
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1206572 https://bugzilla.suse.com/show_bug.cgi?id=1206572#c6 --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- We have another update online since Feb 13. Please give it a try. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206769] post install prime-select issues.
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1206769 https://bugzilla.suse.com/show_bug.cgi?id=1206769#c5 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |NORESPONSE --- Comment #5 from Stefan Dirsch <sndirsch(a)suse.com> --- Still waiting for a response for more than a month now. Please reopen once you can provide the requested feedback. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202933] VUL-0: CVE-2022-3560: pesign: pesign-authorize ExecStartPost script allows privilege escalation from pesign to root
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1202933 https://bugzilla.suse.com/show_bug.cgi?id=1202933#c25 --- Comment #25 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:0484-1: An update that solves one vulnerability can now be installed. Category: security (important) Bug References: 1202933 CVE References: CVE-2022-3560 Sources used: openSUSE Leap 15.4 (src): pesign-0.112-150000.4.15.1 Basesystem Module 15-SP4 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise High Performance Computing 15 SP1 LTSS 15-SP1 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise High Performance Computing 15 SP2 LTSS 15-SP2 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP3 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP3 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise Real Time 15 SP3 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise Server 15 SP1 LTSS 15-SP1 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise Server 15 SP2 LTSS 15-SP2 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise Server for SAP Applications 15 SP1 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise Server for SAP Applications 15 SP2 (src): pesign-0.112-150000.4.15.1 SUSE Linux Enterprise Server for SAP Applications 15 SP3 (src): pesign-0.112-150000.4.15.1 SUSE Manager Proxy 4.2 (src): pesign-0.112-150000.4.15.1 SUSE Manager Retail Branch Server 4.2 (src): pesign-0.112-150000.4.15.1 SUSE Manager Server 4.2 (src): pesign-0.112-150000.4.15.1 SUSE Enterprise Storage 7.1 (src): pesign-0.112-150000.4.15.1 SUSE Enterprise Storage 7 (src): pesign-0.112-150000.4.15.1 SUSE CaaS Platform 4.0 (src): pesign-0.112-150000.4.15.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 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c54 --- Comment #54 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:0485-1: An update that solves six vulnerabilities, contains two features and has 53 fixes can now be installed. Category: security (important) Bug References: 1175995, 1186449, 1198971, 1202712, 1202713, 1203332, 1203693, 1204356, 1204514, 1204662, 1205149, 1205397, 1205495, 1206602, 1206635, 1206640, 1206641, 1206642, 1206643, 1206645, 1206646, 1206648, 1206649, 1206677, 1206698, 1206784, 1206855, 1206858, 1206873, 1206876, 1206877, 1206878, 1206880, 1206882, 1206883, 1206884, 1206885, 1206887, 1206888, 1206890, 1207036, 1207092, 1207093, 1207094, 1207097, 1207102, 1207103, 1207104, 1207107, 1207108, 1207134, 1207168, 1207186, 1207195, 1207237, 1207773, 1207795, 1207875, 1208108 CVE References: CVE-2022-36280, CVE-2022-47929, CVE-2023-0045, CVE-2023-0266, CVE-2023-0590, CVE-2023-23454 Jira References: PED-1706, SLE-15608 Sources used: SUSE Linux Enterprise Real Time 12 SP5 (src): kernel-source-rt-4.12.14-10.115.1, kernel-syms-rt-4.12.14-10.115.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 1208133] Launching any application causes computer to crash when bbswitch is loaded
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208133 https://bugzilla.suse.com/show_bug.cgi?id=1208133#c4 --- Comment #4 from Stefan Dirsch <sndirsch(a)suse.com> --- Any news on this one? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207724] New: gpg key generation must be aborted after having entered mismatches pass phrases
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207724 Bug ID: 1207724 Summary: gpg key generation must be aborted after having entered mismatches pass phrases Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When generating a GPG key, a popup asks to enter a passphrase twice. However when you have a typing error, the only option is to abort the dialog, causing key generation to be aborted. Expectation is that the user has a chance to correct the misspelled passphrase. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1198668] Tumbleweed: Purge old kernels service block during boot
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1198668 http://bugzilla.opensuse.org/show_bug.cgi?id=1198668#c21 --- Comment #21 from Ulrich Windl <Ulrich.Windl(a)rz.uni-regensburg.de> --- systemd-analyze blame said (Leap 15.4): 3min 46.428s plymouth-quit-wait.service 3min 26.981s purge-kernels.service ... Startup finished in 813ms (kernel) + 15.409s (initrd) + 4min 7.745s (userspace) = 4min 23.968s graphical.target reached after 4min 7.705s in userspace However there are two things I don't understand, considering the unit file: # /usr/lib/systemd/system/purge-kernels.service [Unit] Description=Purge old kernels After=local-fs.target ConditionPathExists=/boot/do_purge_kernels ConditionPathIsReadWrite=/ [Service] Type=oneshot Nice=19 IOSchedulingClass=idle Environment=ZYPP_LOCK_TIMEOUT=-1 ExecStart=/usr/bin/zypper -n purge-kernels ExecStartPost=/bin/rm -f /boot/do_purge_kernels [Install] WantedBy=multi-user.target ------------ First which unit is waiting for this one to finish, and if waiting is intended, it makes little sense to use "Nice=19; IOSchedulingClass=idle" as this just makes the unit slower. I found it: /usr/lib/systemd/system/YaST2-Firstboot.service:After=purge-kernels.service /usr/lib/systemd/system/YaST2-Second-Stage.service:After=purge-kernels.service One comment says: # Run after kernels are purged to prevent a zypper lock (bsc#1196431) After=purge-kernels.service Well, but even if that unit has nothing to do it will delay the whole process in case there is something to do. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208567] qemu-system-x86_64: Failed to lock byte 100
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208567 https://bugzilla.suse.com/show_bug.cgi?id=1208567#c8 --- Comment #8 from David Disseldorp <ddiss(a)suse.com> --- (In reply to James Fehlig from comment #7) > (In reply to David Disseldorp from comment #6) > > @James: it appears that the qemu-ovmf-x86_64 paths are SUSE-specific. Do you > > think upstream would be open to this change? > > Let's see > > https://listman.redhat.com/archives/libvir-list/2023-February/238113.html > > If not, I'll add it to the downstream patch containing the virt-aa-helper > hunk. Looks good, thanks James! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208623] New: Gnome crashes with drm:amdgpu_job timedout
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208623 Bug ID: 1208623 Summary: Gnome crashes with drm:amdgpu_job timedout Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: christian.hagenest(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865093 --> http://bugzilla.opensuse.org/attachment.cgi?id=865093&action=edit journalctl dump Hi there, during a teams meeting today, my system (MicroOS Gnome) crashed randomly, only showing @ signs on the screen. I had to turn the device of with the power button and reboot. It seems to be related to the AMD gpu / DRM: Feb 23 14:46:54 localhost.localdomain kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=22369137, emitted seq=22369139 Feb 23 14:46:54 localhost.localdomain kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 2069 thread gnome-shel:cs0 pid 2080 Feb 23 14:46:54 localhost.localdomain kernel: amdgpu 0000:33:00.0: amdgpu: GPU reset begin! Feb 23 14:46:54 localhost.localdomain kernel: amdgpu 0000:33:00.0: amdgpu: free PSP TMR buffer Feb 23 14:46:54 localhost.localdomain kernel: amdgpu 0000:33:00.0: amdgpu: MODE2 reset Feb 23 14:46:54 localhost.localdomain kernel: amdgpu 0000:33:00.0: amdgpu: GPU reset succeeded, trying to resume Feb 23 14:46:54 localhost.localdomain kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F43FC00000). Feb 23 14:46:54 localhost.localdomain kernel: [drm] PSP is resuming... Feb 23 14:46:54 localhost.localdomain kernel: [drm] reserve 0xa00000 from 0xf43e000000 for PSP TMR Feb 23 14:46:55 localhost.localdomain kernel: amdgpu 0000:33:00.0: amdgpu: RAS: optional ras ta ucode is not available Feb 23 14:46:55 localhost.localdomain kernel: amdgpu 0000:33:00.0: amdgpu: RAP: optional rap ta ucode is not available Feb 23 14:46:55 localhost.localdomain kernel: amdgpu 0000:33:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Feb 23 14:46:55 localhost.localdomain kernel: amdgpu 0000:33:00.0: amdgpu: SMU is resuming... Feb 23 14:46:55 localhost.localdomain kernel: amdgpu 0000:33:00.0: amdgpu: SMU is resumed successfully! [...] Feb 23 14:46:56 localhost.localdomain gnome-shell[2069]: amdgpu: The process will be terminated. Feb 23 14:46:56 localhost.localdomain kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! Feb 23 14:46:56 localhost.localdomain nautilus[23561]: Error reading events from display: Broken pipe Feb 23 14:46:56 localhost.localdomain gsd-power[2352]: Error reading events from display: Broken pipe I have attached a longer dump of journalctl. Please excuse me if this is the wrong way to report this, this is my first bug report -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1208567] qemu-system-x86_64: Failed to lock byte 100
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208567 https://bugzilla.suse.com/show_bug.cgi?id=1208567#c7 --- Comment #7 from James Fehlig <jfehlig(a)suse.com> --- (In reply to David Disseldorp from comment #6) > @James: it appears that the qemu-ovmf-x86_64 paths are SUSE-specific. Do you > think upstream would be open to this change? Let's see https://listman.redhat.com/archives/libvir-list/2023-February/238113.html If not, I'll add it to the downstream patch containing the virt-aa-helper hunk. -- You are receiving this mail because: You are on the CC list for the bug.

1 0