November 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 938955] New: Desktop selection overridden when installing without recommended packages.
by bugzilla_noreply＠novell.com 23 Aug '22

23 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=938955 Bug ID: 938955 Summary: Desktop selection overridden when installing without recommended packages. Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: cwh(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Chosing not to install recommnded packages leads to a minimal installation even without xorg and desktop environment although a desktop environment has been selected before. Either the patterns have to be fixed or the no-recommends option should only be allowed for the minimal pattern. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1074138] New: Yast2 package manager UI very slow
by bugzilla_noreply＠novell.com 23 Aug '22

23 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=1074138 Bug ID: 1074138 Summary: Yast2 package manager UI very slow Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: amajer(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have a basic install. I would like to look through installed package list and uninstall extra things I don't really need anymore. So, 1. yast2 -> Package Manager 2. list all packages 3. click on a package like Mesa-libGLESv2-devel and click uninstall 4. wait 30+ seconds while Package Manager window is completely unresponsive and 100% CPU usage. workaround, 1. filter to only list few packages. 2. click uninstall Please fix. There is no reason Qt based UI should be slow, especially for simple tables like this. This problems seems to exist in all versions of Yast. -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 948370] New: One-Click-Installer YMP file cannot match group section for Tumbleweed
by bugzilla_noreply＠novell.com 23 Aug '22

23 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=948370 Bug ID: 948370 Summary: One-Click-Installer YMP file cannot match group section for Tumbleweed Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: tgoettlicher(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0 Build Identifier: One-Click-Installer YMP files can contain sections for different distribution versions, e.g.: <group distversion="openSUSE 13.2"> You can match against a specific Tumbleweed build: <group distversion="openSUSE 20150924"> But it's not possible to match for Tumbleweed in general because the version of Tumbleweed changes with every build. Can the one-click-installer be extended to not only match against the version but also against the codename? For example: <group distcodename="openSUSE Tumbleweed"> Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 930110] New: yast ncurses menus not properly formatted for tumbleweed ppc64 guest install
by bugzilla_noreply＠novell.com 23 Aug '22

23 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=930110 Bug ID: 930110 Summary: yast ncurses menus not properly formatted for tumbleweed ppc64 guest install Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: normand(a)linux.vnet.ibm.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- yast ncurses menus not properly formatted for tumbleweed ppc64 guest install Detailed flow: * On a Power KVM host I defined a libvirt twppc64.xml using the Tumbleweed-BE-DVD-ppc64-Snapshot20150505-Media.iso retrieved from https://openqa.opensuse.org/tests/60778/asset/3110 * from a ssh session to the PowerKVM I started a screen window from which I started the ppc64 guest. === virsh define twppc64.xml virsh start --console twppc64 === * I captured successively the ncurses menus and did a yast2_ncurse_bad_format.tgz tarball with all those png files. * The first problem is that the text is not properly aligned eg: yast2_img1_installation.png * The 2nd problem is that some characters from previous menu are not cleaned up when new menu is presented. eg: yast2_img4_installation_option.png * The third problem is popup window hardly visible eg: yast2_img9_confirm_password.png -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1172028] New: Wrong patch4 in Plymouth.
by bugzilla_noreply＠suse.com 22 Aug '22

22 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1172028 Bug ID: 1172028 Summary: Wrong patch4 in Plymouth. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: olivier.lahaye1(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please remove patch4 in Plymouth package as it seems counter productive on emu. I'm using emu-5.0.0 on MacOS-X with HVF acceleration, and my Plymouth theme with script module fails to go to graphic mode in my specially crafter initrd. (SystemImager-NG) If I rebuild the Plymouth package without the patch 4 (plymouth-only_use_fb_for_cirrus_bochs.patch), and if I re-generate my initrd, my theme works fine. (everything is displayed as expected) I'm using tianocore UEFI bios on emu-5.0.0 on MacOS with HVF acceleration. kernel: vmlinuz-5.3.18-lp152.14-default plymouth: plymouth-0.9.4+git20190304.ed9f201-lp152.4.4.x86_64 See more infos and log here: https://lists.freedesktop.org/archives/plymouth/2020-May/000890.html -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1162535] New: Update openSUSE Plymouth theme for 15.2 to bgrt
by bugzilla_noreply＠novell.com 22 Aug '22

22 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1162535 Bug ID: 1162535 Summary: Update openSUSE Plymouth theme for 15.2 to bgrt Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: stasiek(a)michalski.cc QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Following Tumbleweed, change the line setting the default theme to `sed -i -e 's/spinner/bgrt/g' src/plymouthd.defaults` -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 980750] New: Plymouth prevents loading DRM/KMS driver for newly installed graphics card
by bugzilla_noreply＠novell.com 22 Aug '22

22 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=980750 Bug ID: 980750 Summary: Plymouth prevents loading DRM/KMS driver for newly installed graphics card Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: maximilian.staudt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When changing a VGA card in an already installed system, Plymouth will prevent its modern (DRM/KMS) kernel mode driver to be loaded. Example: 1. Install Leap 42.1 in QEMU using the emulated Cirrus card (-vga cirrus). 2. The system boots up with a splash screen. 3. Shut down the system. 4. Start the VM, this time with the Bochs VGA card (-vga std). 5. A splash screen will be shown, but then X falls back to the VESA driver. As a bonus, switching to a text VT (Ctrl-Alt-F1) only gives a blinking cursor. The VT works just fine and is usable, except the user has to operate it blindly as no video is shown. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1156421] New: devel:kubic:images: no persistent systemd journal for aarch64/armv7l
by bugzilla_noreply＠novell.com 18 Aug '22

18 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=1156421 Bug ID: 1156421 Summary: devel:kubic:images: no persistent systemd journal for aarch64/armv7l Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: fvogt(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The images for Raspberry Pi 2/3 from devel:kubic:images have no persistent systemd journal logging, the x86-64 has. The /var/log/journal directory seems to exist, no idea why the log is written to /run/log/journal instead. -- You are receiving this mail because: You are on the CC list for the bug.

2 35

[Bug 1177358] New: EFI system partition: VFAT or FAT16 or FAT12 or FAT32?
by bugzilla_noreply＠suse.com 17 Aug '22

17 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177358 Bug ID: 1177358 Summary: EFI system partition: VFAT or FAT16 or FAT12 or FAT32? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kaykaykay123(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Why openSUSE installer specifies "EFI system partition" as VFAT? What file system is actually used? By standard we need FAT32 for EFI system partition + fixed drives: https://en.wikipedia.org/wiki/EFI_system_partition "FAT32 is always expected on fixed drives". VFAT is not equal to FAT32: https://en.wikipedia.org/wiki/File_Allocation_Table Windows requires FAT32 for EFI system partition. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1012883] New: System hangs at reboot/shutdown: A stop job is running for User Manager for UID 1000 (1min30)
by bugzilla_noreply＠novell.com 15 Aug '22

15 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1012883 Bug ID: 1012883 Summary: System hangs at reboot/shutdown: A stop job is running for User Manager for UID 1000 (1min30) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jeckferson(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- It's an upstream systemd bug as described in: https://github.com/systemd/systemd/issues/1615 It also manifested in 42.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 28