July 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1160707] qemu VNC console corruption
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1160707 Santiago Zarate <santiago.zarate(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jose.ziviani(a)suse.com Flags| |needinfo?(jose.ziviani@suse | |.com) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1020631] configure script can not detect the correct icu version with sed 4.3
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1020631 http://bugzilla.opensuse.org/show_bug.cgi?id=1020631#c10 --- Comment #10 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1020631) was mentioned in https://build.opensuse.org/request/show/904702 15.3 / seamonkey -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187616] [RPi4] does not boot from USB-Stick if no bootable SD card is present
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187616 https://bugzilla.suse.com/show_bug.cgi?id=1187616#c4 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan.ivanov(a)suse.com --- Comment #4 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Hi Axel, you know, by default RPi4 boot from SD card. Not sure how do you interrupt and select USB boot when there is a bootable SD card, but if there is no bootable SD card you can't boot from USB. Unless you change boot device order (more about this in Matthias links). Personally I am using "Raspberry Pi Imager"[1]. Choose: Misc utility image -> Bootloader -> USB boot. And the main question is what do you want to achieve? [1] https://snapcraft.io/install/rpi-imager/opensuse -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183082] [Build 20210304] Xvnc in inst-sys crashes due to incomplete crypto-policies installation
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1183082 https://bugzilla.suse.com/show_bug.cgi?id=1183082#c20 --- Comment #20 from Steffen Winterfeldt <snwint(a)suse.com> --- I'll have a look. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188068] [Build 20210705][WSL] YaST2 firstboot prompts user to define root password
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188068 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Assignee|yast2-maintainers(a)suse.de |yast-internal(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188068] [Build 20210705][WSL] YaST2 firstboot prompts user to define root password
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188068 https://bugzilla.suse.com/show_bug.cgi?id=1188068#c3 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |jreidinger(a)suse.com --- Comment #3 from Josef Reidinger <jreidinger(a)suse.com> --- thanks, for report. We will add it to top of our queue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187701] Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187701 https://bugzilla.suse.com/show_bug.cgi?id=1187701#c24 --- Comment #24 from Joerg Roedel <jroedel(a)suse.com> --- (In reply to Joerg Roedel from comment #23) > Can you please provide the output of 'lspci -vvv -xxxx' and 'lspci -t' with > the working and with the broken kernel? There must be a difference which > explains why MMIO read and writes are going to nowhere. A full dmesg of the broken kernel would also be helpful. Thanks, Joerg -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183082] [Build 20210304] Xvnc in inst-sys crashes due to incomplete crypto-policies installation
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1183082 https://bugzilla.suse.com/show_bug.cgi?id=1183082#c19 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger(a)suse.com Flags| |needinfo?(snwint(a)suse.com) --- Comment #19 from Josef Reidinger <jreidinger(a)suse.com> --- Steffen - can you please check it? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187761] brcmfmac problem
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187761 https://bugzilla.suse.com/show_bug.cgi?id=1187761#c4 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werwolf131313@gma | |il.com) | --- Comment #4 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Please, could you attach full kernel log after inserting brcmfmac module, not just 30 lines. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187701] Ten64 fails to boot (kernel panic in initramfs) from nvme after upgrade to kernel 5.3.18-59.5-default
by bugzilla_noreply＠suse.com 08 Jul '21

08 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187701 https://bugzilla.suse.com/show_bug.cgi?id=1187701#c23 --- Comment #23 from Joerg Roedel <jroedel(a)suse.com> --- (In reply to Daniel Wagner from comment #22) > TL;DR: the value says 'synchronous external abort' :) Thanks for the explanations. So this means that your previous analysis of where the issues are triggered is correct, which is a good start. The errors happen when the kernel tries a read or write on PCI memory regions. This does not sound related to the patches I backported, but I have another look on what might cause this. Can you please provide the output of 'lspci -vvv -xxxx' and 'lspci -t' with the working and with the broken kernel? There must be a difference which explains why MMIO read and writes are going to nowhere. -- You are receiving this mail because: You are on the CC list for the bug.

1 0