October 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1177448] New: Installer freezes up at 98% during installation of packages.
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177448 Bug ID: 1177448 Summary: Installer freezes up at 98% during installation of packages. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: bugzilla(a)axion.demon.nl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 842386 --> http://bugzilla.opensuse.org/attachment.cgi?id=842386&action=edit save_y2logs result. Installer freezes up at 98% during installation of packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1173115] kernel updates lead to showing mok screen on reboot
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1173115 https://bugzilla.suse.com/show_bug.cgi?id=1173115#c39 --- Comment #39 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1173115) was mentioned in https://build.opensuse.org/request/show/840296 15.1 / kernel-source -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177419] [Build 20201003] udisks2ctl randomly fails to set up loop device for /root/udisk_test.iso: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error waiting for loop object after creating '/dev/loop0': Timed out waiting for object
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177419 https://bugzilla.suse.com/show_bug.cgi?id=1177419#c5 --- Comment #5 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Martin Loviska from comment #4) > Please let me know if you miss anything else. > > Thanks! Thanks, the information is sufficient and I could reproduce the issue. It seems that this is already reported upstream: https://github.com/storaged-project/udisks/issues/800 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177456] New: Wrong path for sftp-server in sshd_config
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1177456 Bug ID: 1177456 Summary: Wrong path for sftp-server in sshd_config Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mitch(a)comwestcr.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The initial sshd_config file contains the following configuration option: Subsystem sftp /usr/lib/ssh/sftp-server The correct path is: Subsystem sftp /usr/libexec/ssh/sftp-server -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1176757] New: Since 5.3.18-lp152.41 Boot process hangs at "fb0: switchting to amdgpudrmfb from EFI VGA"
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176757 Bug ID: 1176757 Summary: Since 5.3.18-lp152.41 Boot process hangs at "fb0: switchting to amdgpudrmfb from EFI VGA" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: lx(a)stoneshire.de QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0 Build Identifier: After the kernel update from 5.3.18-lp152.36-default to 5.3.18-lp152.41-default my system is unable to boot. The system hangs after printing "fb0: switchting to amdgpudrmfb from EFI VGA" and is not able to boot any further. When using "Advanced boot options" and booting via the older kernel, everything works as expected and the system boots up without hanging. Reproducible: Always Steps to Reproduce: 1. Have AMD RX-5700 graphics card 2. Upgrade to Leap 15.2 to kernel 5.3.18-lp152.41-default 3. Try to boot Actual Results: Boot hangs with blinking cursor in the left upper edge. When booting up without splash-screen the message "fb0: switchting to amdgpudrmfb from EFI VGA" is seen as the last line. Expected Results: After GRUB, boot up normally and log in via graphical login manager I had the AMD GPU driver version 20.30 installed. Uninstalling it (via booting the older, working kernel) did not change the (faulty) boot behaviour with the new kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1177273] Updating wicked 0.6.63 to 0.6.64 breaks tap0
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177273 https://bugzilla.suse.com/show_bug.cgi?id=1177273#c3 Malcolm Lewis <malcolmlewis(a)cableone.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wicked-maintainers(a)suse.de Flags| |needinfo?(wicked-maintainer | |s(a)suse.de) --- Comment #3 from Malcolm Lewis <malcolmlewis(a)cableone.net> --- (In reply to Rubén Torrero Marijnissen from comment #1) > Hi Malcom, > > Thanks for the bug report. Could you provide us with more logs following > https://en.opensuse.org/openSUSE:Bugreport_wicked ? > > Also, could you provide more details about your setup, e.g. how you > configure br0 and tap0 devices and what brings them up, etc.. ? Hi Attached, please find logs as requested. Four folders, old version, new version and with qemu running with both versions. On the host system the interfaces are all configured via YaST Network Settings to add the bridge and tap device. The tap0 device is activated when qemu is started via a script option as indicated in bug report creation; Portion of qemu script used for interface; -nic tap,ifname=tap0,script=no,downscript=no The qemu machines use gpu (nvidia GT710) and sata (PCIe mini card) passthrough. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177273] Updating wicked 0.6.63 to 0.6.64 breaks tap0
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177273 https://bugzilla.suse.com/show_bug.cgi?id=1177273#c2 --- Comment #2 from Malcolm Lewis <malcolmlewis(a)cableone.net> --- Created attachment 842412 --> https://bugzilla.suse.com/attachment.cgi?id=842412&action=edit wicked logs -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177256] Kernel update breaks amdgpu Pro drivers due to amdgpu's firmware files not being available in /lib/firmware/<new-kernel>
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177256 https://bugzilla.suse.com/show_bug.cgi?id=1177256#c15 --- Comment #15 from Darren Davis <ddavis(a)suse.com> --- Adding AMD for awareness. Alex, let me know if there are others at AMD we should involve. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177256] Kernel update breaks amdgpu Pro drivers due to amdgpu's firmware files not being available in /lib/firmware/<new-kernel>
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177256 Darren Davis <ddavis(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexander.deucher(a)amd.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176401] [WSL] missing user and group nobody which is used by quite some tools
by bugzilla_noreply＠suse.com 08 Oct '20

08 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1176401 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low -- You are receiving this mail because: You are on the CC list for the bug.

1 0