November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1184072] New: Gnome login failure
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184072 Bug ID: 1184072 Summary: Gnome login failure Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: 8494(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fresh install of 15.3 Beta. Using Thinkpad E595 AMD 3700u. Selecting Gnome login option. ( the X11 versions all work like classic etc ) The screens goes to black for a second or two after clicking login button, the mousepointer seems to freeze and then I'm back at the login screen. Anyone know of logs I should attach? -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Bug 1182510] New: broken formatting for man page: modesetting
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1182510 Bug ID: 1182510 Summary: broken formatting for man page: modesetting Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: comes(a)naic.edu QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 846331 --> http://bugzilla.opensuse.org/attachment.cgi?id=846331&action=edit fix for modesetting man page xorg-server < 1.20.6 On leap 15.2 the command man modesetting shows incorrect formatting (like: MODESETTING(@drivermansuffix@) instead of: MODESETTING(4)) This issue was fixed upstream in xorg-server-1.20.6 however since the upcoming leap 15.3 still comes with xorg-server-1.20.3 I suggest to apply the attached patch to the package xorg-x11-server in order to fix the issue in 15.2/15.3 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 786024] vsftpd broken: audit_log_acct_message() failed: Operation not permitted
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=786024 https://bugzilla.suse.com/show_bug.cgi?id=786024#c77 --- Comment #77 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2022:3888-1: An update that solves one vulnerability, contains one feature and has four fixes is now available. Category: security (important) Bug References: 1021387,1052900,1187678,1187686,786024 CVE References: CVE-2021-3618 JIRA References: PM-3322 Sources used: SUSE Linux Enterprise Server 12-SP5 (src): vsftpd-3.0.5-51.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 1204180] [15.4][autoyast][installation] test fails in installation for transactional server role with error msg "install(4119) [Ruby] modules/Kdump.rb(update_initrd_with):421 Error updating initrd"
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204180 https://bugzilla.suse.com/show_bug.cgi?id=1204180#c13 Ignaz Forster <iforster(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(iforster(a)suse.com | |) | --- Comment #13 from Ignaz Forster <iforster(a)suse.com> --- (In reply to Josef Reidinger from comment #12) > 2. In previous ages for CAASP product we add that specific call that is > called always for kdump, even when kdump is not enabled ( see comment#8 for > code ). I am not sure if it is correct to call it always. I think this code is still needed for openSUSE MicroOS / SLE Micro / ALP, otherwise kdump wouldn't be configured on first boot I guess? > 3. I am not sure if `transactional-update kdump` handle disabled kdump. We > need to have it when user configure kdump and then change mind. Is it > correct to call also `transactional-update kdump` in that case? Yes, it checks whether the kdump.service is activated and only runs if that is the case. However that check is performed in transactional-update itself, not in /usr/sbin/tu-rebuild-kdump-initrd, the helper script which is called from YaST directly during installation (where Package.IsTransactionalSystem doesn't seem to be true from how I understand the code). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190434] crash is unable to find debuginfo of usrmerged kernel
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190434 http://bugzilla.opensuse.org/show_bug.cgi?id=1190434#c10 --- Comment #10 from Dominique Leuenberger <dimstar(a)opensuse.org> --- The UsrMerge patch has been included in Tumbleweed as part of https://build.opensuse.org/request/show/1032553#tab-pane-changes in snapshot 20221027 This has changed the error now, as can be seen in openQA: https://openqa.opensuse.org/tests/2857536#step/kdump_and_crash/60 > Dwarf error: wrong version in compilation unit header (is 5, should be 2, 3, or 4) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204790] gcc12: don't require glibc-devel-32bit if %disable_32bit
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204790 https://bugzilla.suse.com/show_bug.cgi?id=1204790#c5 --- Comment #5 from Ludwig Nussel <lnussel(a)suse.com> --- Heretic question. Do we actually need gcc -m32 support at all anymore in TW? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 944832] installing updates during shutdown causes reboot
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=944832 http://bugzilla.opensuse.org/show_bug.cgi?id=944832#c25 --- Comment #25 from Milachew <milachew(a)mail.lv> --- (In reply to Lubos Kocman from comment #24) > All set, feel free to do the SR Ok... it was fast :) Done : https://build.opensuse.org/request/show/1034340 https://build.opensuse.org/request/show/1034326 ------------------------------------------------- (a small departure from the topic) Also, it would be appropriate to set the SP4:Update branch by default for everyone (or only for non-maintainers) who does submit in SP4 via build.opensuse.org? This would make it possible not to close similar requests with text similar to c#19. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205136] New: Silent bluetooth audio in Teams: Bluetooth: hci0: SCO packet for unknown connection handle 257
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205136 Bug ID: 1205136 Summary: Silent bluetooth audio in Teams: Bluetooth: hci0: SCO packet for unknown connection handle 257 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: andreas_nordal_4(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This morning, bluetooth audio output in the native Teams client for Linux became silent. It worked last week. I have rebooted inbetween, due to zypper updates. Other pulseaudio programs work fine, but a test call in Teams yields this in journalctl --follow: Bluetooth: hci0: SCO packet for unknown connection handle 257 Bluetooth: hci0: urb 000000001d57a72c submission failed (90) Bluetooth: hci0: sending frame failed (-90) Bluetooth: hci0: urb 000000001d57a72c submission failed (90) Bluetooth: hci0: sending frame failed (-90) Bluetooth: hci0: SCO packet for unknown connection handle 257 I can only test with bluetooth audio on Leap, because only Tumbleweed recognizes the audio jack on this machine (HP Elitebook 840 G6). With Teams and bluetooth, this symptom usually means you have to restart Teams after connecting a bluetooth headset and set it in HFP mode, but that is apparently no longer enough. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 944832] installing updates during shutdown causes reboot
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=944832 http://bugzilla.opensuse.org/show_bug.cgi?id=944832#c24 --- Comment #24 from Lubos Kocman <lubos.kocman(a)suse.com> --- All set, feel free to do the SR -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 944832] installing updates during shutdown causes reboot
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=944832 http://bugzilla.opensuse.org/show_bug.cgi?id=944832#c23 --- Comment #23 from Lubos Kocman <lubos.kocman(a)suse.com> --- It's missing attr https://build.opensuse.org/attribs/SUSE:SLE-15-SP3:Update in https://build.opensuse.org/attribs/SUSE:SLE-15-SP4:Update I've already reached out to autobuild, I'll ping you once it's set (or you can check the attrs by yourself on listed url). -- You are receiving this mail because: You are on the CC list for the bug.

1 0