February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207831] New: Incorrect path in message generated by yast2-ldap package
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207831 Bug ID: 1207831 Summary: Incorrect path in message generated by yast2-ldap package Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: ralf.habacker(a)freenet.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When configuring a new ldap server instance, messages are displayed in case of error or success. This message refers to a log file named "/var/log/YaST/y2log" that is not present on an installation of openSUSE Leap 15.4 and may confuse user. The locations where this incorrect path are used: $ grep -rn "YaST/y2log" /usr/share/YaST2/ /usr/share/YaST2/lib/authserver/dir/ds389.rb:59: # The output of setup script is written into file .y2log or /var/log/YaST/y2log /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:156: Popup.Error(_('Failed to create Kerberos KDC connection user! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:163: Popup.Error(_('Failed to create Kerberos KDC connection user! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:170: Popup.Error(_('Failed to create Kerberos administration user! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:177: Popup.Error(_('Failed to create Kerberos KDC administration user! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:201: Popup.Error(_('Failed to create password file! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:208: Popup.Error(_('Failed to create password file! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:217: Popup.Error(_('Kerberos initialisation failure! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:226: Popup.Error(_('Failed to modify directory permission! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:233: Popup.Error(_('Failed to modify directory permission! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_krb_inst.rb:251: Popup.Message(_('New instance has been set up! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_dir_inst.rb:123: Popup.Error(_('Failed to set up new instance! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_dir_inst.rb:132: Popup.Error(_('Failed to set up new instance! Log output may be found in /var/log/YaST/y2log')) /usr/share/YaST2/lib/authserver/ui/new_dir_inst.rb:145: Popup.Message(_('New instance has been set up! Log output may be found in /var/log/YaST/y2log')) The correct path is /var/log/YaST2. Looking for references to the mentioned logfile gives: $ grep -rnw "y2log" /usr/share/YaST2/ ... /usr/share/YaST2/clients/inst_kickoff.rb:221: Ops.add(Directory.logdir, "/y2log") /usr/share/YaST2/clients/inst_kickoff.rb:285: Ops.add(Directory.logdir, "/y2log") /usr/share/YaST2/clients/inst_kickoff.rb:348: Ops.add(Directory.logdir, "/y2log") /usr/share/YaST2/clients/inst_kickoff.rb:406: Ops.add(Directory.logdir, "/y2log") which means that a Ruby variable with the correct path exists and should be used in the relevant places. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1207734] AMDGPU related freeze when returning from monitor powersave
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207734 https://bugzilla.suse.com/show_bug.cgi?id=1207734#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matti.kettunen(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(matti.kettunen@gm | |ail.com) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- I'm building a test kernel with the possible upstream fix patch. It's being built in OBS home:tiwai:bsc1207734 repo. After finishing the build (usually takes an hour or so), the kernel package will appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1207734/pool/ Please give it a try later. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207807] kcompactd0 consumes 100% cpu apparently causing virtual machine to freeze for extended times
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207807 https://bugzilla.suse.com/show_bug.cgi?id=1207807#c3 --- Comment #3 from Michal Hocko <mhocko(a)suse.com> --- Seems like a duplicate of bug 1206848 (resp. bug 1207115)? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207519] New: AMDGPU graphics hang after failed suspend (IB test failed on gfx (-110))
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207519 Bug ID: 1207519 Summary: AMDGPU graphics hang after failed suspend (IB test failed on gfx (-110)) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: gfx-bugs(a)suse.de Reporter: linus.kardell(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Sometimes my laptop failed to suspend (see https://bugzilla.suse.com/show_bug.cgi?id=1191519) When this happens, I get an amdgpu error: jan 24 20:47:22 putsa kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx (-110). jan 24 20:47:22 putsa kernel: [drm:process_one_work] *ERROR* ib ring test failed (-110). And the graphics stop working (including kscreenlocker_greet segfaulting). I can still switch to a console with ctrl+alt+f1, but anything graphical will not work. Operating System: openSUSE Tumbleweed 20230122 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-1-default (64-bit) Graphics Platform: Wayland Processors: 8 � AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 29.3 Gibyte of RAM Graphics Processor: AMD Radeon Vega 10 Graphics Manufacturer: Acer Product Name: Aspire A315-41 System Version: V1.18 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1207807] kcompactd0 consumes 100% cpu apparently causing virtual machine to freeze for extended times
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207807 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhocko(a)suse.com, | |tiwai(a)suse.com, | |vbabka(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207763] Since 5.14.21-150400.24.41-default, machine fails to recover from hibernation.
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207763 https://bugzilla.suse.com/show_bug.cgi?id=1207763#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos.e.r(a)opensuse.org, | |tiwai(a)suse.com Flags| |needinfo?(carlos.e.r@opensu | |se.org) --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Could you verify that the hibernation still works with the previous kernel? Then attach both dmesg outputs after the hibernation (success and fail), as well as the hwinfo outputs from both kernels. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207761] CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207761 https://bugzilla.suse.com/show_bug.cgi?id=1207761#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |FEATURE --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- The restriction seems mentioned in the man page of the git repo. See discussions in bug 1200669. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207808] New: systemd: missing ACLs for wheel group access to system journal
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207808 Bug ID: 1207808 Summary: systemd: missing ACLs for wheel group access to system journal Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: luca.dimaio1(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On OpenSUSE, journald directories and files are created without the suggested ACLs, this leads to various problems; In systemd documentation, they stated: """ It is also recommended to grant read access to all journal files to the system groups "wheel" and "adm" with a command like the following in the post installation script of the package: # setfacl -nm g:wheel:rx,d:g:wheel:rx,g:adm:rx,d:g:adm:rx /var/log/journal/ """ As stated here: https://cgit.freedesktop.org/systemd/systemd/tree/README?id=4a792f4676e5f8f… We can in fact see that ACLs are not set for journal files: ``` # getfacl /var/log/journal/d5f96fc2dee54e87a1894f94c3f57996/system.journal # file: /var/log/journal/d5f96fc2dee54e87a1894f94c3f57996/system.journal # owner: root # group: 498 user::rw- group::r-- other::--- ``` On other distros the ACLs are instead set correctly: ``` [root@fedora ~]# getfacl /var/log/journal/4fc96fa7b9a4486e9400e7765fd5ab69/system.journal # file: var/log/journal/4fc96fa7b9a4486e9400e7765fd5ab69/system.journal # owner: root # group: systemd-journal user::rw- group::r-x #effective:r-- group:adm:r-- group:wheel:r-- mask::r-- other::--- ``` This grants users in the wheel group to read (and read-only) system logs. Missing those ACLs has repercussions in the journalctl command, and leads to problem with other software, one of which is podman in rootless mode. here we have a bug report for podman problems: https://bugzilla.suse.com/show_bug.cgi?id=1199871 That leads to podman logs being empty because journalctl doesn't correctly get system logs -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1165273] zathura-plugin-pdf-mupdf not loaded due to error.
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1165273 Dan ��erm��k <dcermak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|dcermak(a)suse.com | -- 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 01 Feb '23

01 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1202933 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com, | |security-team(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0