February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1208208] New: Yast error during install
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208208 Bug ID: 1208208 Summary: Yast error during install Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: A Yast error message suggest that I report a bug. I will attach logs. It looks as if all software did install. But booting is not installed, and there are no users. The root account is not fully setup (password not properly set). The install uses: openSUSE-Leap-15.5-DVD-x86_64-Build395.1-Media.iso I did a successful install two days ago, to a USB external drive. But my install yesterday failed. The install was to a KVM system using a virtio disk. Reproducible: Always Steps to Reproduce: I did repeat the install attempt. For the repeat, I set it to install only a generic desktop (i.e. icewm) to keep the install time shorter. This still failed in the same way. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1205953] During upgrade of 15.3 to 15.4 several repos were deactivated with no warning.
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

1 0

[Bug 1205953] During upgrade of 15.3 to 15.4 several repos were deactivated with no warning.
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1205953 https://bugzilla.suse.com/show_bug.cgi?id=1205953#c11 Ladislav Slez�k <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lslezak(a)suse.com) | --- Comment #11 from Ladislav Slez�k <lslezak(a)suse.com> --- (In reply to Carlos Robinson from comment #0) > Problem is, several repos also changed names; example: > > http://download.opensuse.org/repositories/Education/openSUSE_Leap_15.3/ > > became: > > http://download.opensuse.org/repositories/Education/15.4/ That's a change on the OBS side. When you add the 15.3 repository into your OBS project the default name is "openSUSE_Leap_15.3". That's also included in the repository URL. But if you add the 15.4 repository then the default name is "15.4". That's why the URLs changed. :-/ > That's fine, but YaST did not warn it could not find the repository. It just > went ahead trying to find a solution, dropping packages to the standard OSS > repo, or did not upgrade the package at all. 2022-11-27 07:18:44 <1> install(4134) [Pkg] modules/ProductLicense.rb:1704 Pkg Builtin called: SourceLoad ... 2022-11-27 07:18:48 <3> install(4134) [Pkg] Source_Load.cc(SourceLoadImpl):327 Error in SourceLoad: [OBS_Emulators_Wine|http://download.opensuse.org/repositories/Emulators:/Win…] Valid metadata not found at specified URL ... 2022-11-27 07:18:54 <2> install(4134) [Pkg] Source_Load.cc(SourceLoadImpl):441 Ignoring packages from repository 'LocalRepo' (LocalRepo) - refresh has failed 2022-11-27 07:18:54 <2> install(4134) [Pkg] Source_Load.cc(SourceLoadImpl):441 Ignoring packages from repository 'OBS: Emulators: Wine' (OBS_Emulators_Wine) - refresh has failed 2022-11-27 07:18:54 <2> install(4134) [Pkg] Source_Load.cc(SourceLoadImpl):441 Ignoring packages from repository 'OBS: security' (OBS_security) - refresh has failed It seems that this pkg-call does not report errors during repository refresh. I think we should call the repository refresh call explicitly to get the errors (Pkg.SourceRefreshNow()). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208003] Support EFI 32/64 bit mixed mode (Was: installation images do not support 32-bit EFI)
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208003 https://bugzilla.suse.com/show_bug.cgi?id=1208003#c20 --- Comment #20 from Steffen Winterfeldt <snwint(a)suse.com> --- Ah, yes: and the EFI config grub2-install created for 32 bit did not look fully correct either. But that's a different thing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208003] Support EFI 32/64 bit mixed mode (Was: installation images do not support 32-bit EFI)
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208003 https://bugzilla.suse.com/show_bug.cgi?id=1208003#c19 --- Comment #19 from Steffen Winterfeldt <snwint(a)suse.com> --- Running an x86 (64 bit) install on 32 bit EFI left more or less a mess of various EFI boot files on the EFI partition. Manual fixing was needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208003] Support EFI 32/64 bit mixed mode (Was: installation images do not support 32-bit EFI)
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208003 https://bugzilla.suse.com/show_bug.cgi?id=1208003#c18 --- Comment #18 from Steffen Winterfeldt <snwint(a)suse.com> --- FWIW, I've checked an installation (i386, 32bit EFI firmware) with openSUSE-Tumbleweed-DVD-i586-Snapshot20230212-Media.iso and it basically all worked out-of-the-box. There were a few issues, though: 1. You must enable online repos to get the grub2-i386-efi package but you cannot do this as the link to the XML file does not work. It tries to use https://download.opensuse.org/YaST/Repos/openSUSE_i586_Factory_Servers.xml but correct (or at least working) is https://download.opensuse.org/YaST/Repos/openSUSE_Factory_Servers.xml Adjusting /control.xml fixed this. 2. Bootloader defaulted to grub2, had to be changed to grub2-efi. The storage proposal created an EFI layout, though. 3. Secure boot had to be turned off. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208123] Random audio pops, crackling sound on HQ USB DAC Fulla Shiit
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208123 https://bugzilla.suse.com/show_bug.cgi?id=1208123#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(cartesius68@gmail | |.com) | --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- We need to check how the problem can be reproduced with the raw access without PA or PW daemon. Namely, try the following: - Prepare sample WAV files in different formats (16, 24 and 32 bit) and different sample rates (44100 and 48000Hz). You can try with sox to convert WAV files, for example. - For PW, stop the pipewire temporarily via % systemctl --user stop wireplumber and run aplay directly for the test WAV file such as % aplay -Dhw:0,0, -vv foo.wav where hw:0,0 corresponds to the card#0, device#0. Take a look at /proc/asound/cards and use the different number if your USB device is assigned to a different slot. - Verify the aplay runs with different formats and sample rates, check whether the problem appears. - If aplay alone doesn't show the problem, try to run arecord simultaneously while running aplay, e.g.: % arecord -vv -Dhw:0,0 -r44100 -c2 -fS16_LE bar.wav If the above still doesn't show the problem, you'd need to try the different buffer/period sizes via --buffer-size and --period-size options for aplay/arecord. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208204] Kernel modules no longer build for nvidia G04 hardware
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208204 https://bugzilla.suse.com/show_bug.cgi?id=1208204#c6 --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- Could this be a duplicate of boo#1208198 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180471] New: diff-pdf has incorrect description in manpage
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1180471 Bug ID: 1180471 Summary: diff-pdf has incorrect description in manpage Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: munix9(a)googlemail.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1047218 Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our diff-pdf package varies across builds: +++ /usr/share/man/man1/diff-pdf.1 .SH DESCRIPTION -18:55:41: Error: Unable to initialize GTK+, is DISPLAY set properly? +08:12:21: Error: Unable to initialize GTK+, is DISPLAY set properly? This comes from help2man. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1207562] U-Boot: Raspberry Pi 4 booting from USB stopped booting
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207562 https://bugzilla.suse.com/show_bug.cgi?id=1207562#c27 --- Comment #27 from Stefan Seyfried <seife(a)novell.slipkontur.de> --- (In reply to Michal Suchanek from comment #26) > (In reply to Guillaume GARDET from comment #2) > > Could you try the u-boot package from > > https://build.opensuse.org/package/show/home:michals/u-boot and report the > > result here, please? > > Updated with > https://patchwork.ozlabs.org/project/uboot/patch/20230212150706.2967007-2- > sjoerd(a)collabora.com/ instead does not boot for me: raspi4a:~ # rpm -q u-boot-rpiarm64 u-boot-rpiarm64-2023.01-250.1.aarch64 from home:michals Still the same Found EFI removable media binary efi/boot/bootaa64.efi ** Reading file would overwrite reserved memory ** Failed to load 'efi/boot/bootaa64.efi' 8GB raspberry pi4 booting from usb3 connected SSD. -- You are receiving this mail because: You are on the CC list for the bug.

1 0