August 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 993401] New: grub2-install for EFI installs an EFI entry that is not bootable
by bugzilla_noreply＠novell.com 30 Sep '22

30 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=993401 Bug ID: 993401 Summary: grub2-install for EFI installs an EFI entry that is not bootable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: aarch64 OS: openSUSE 42.1 Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: alan(a)softiron.co.uk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Running grub2-install does not yield a bootable entry in EFI's boot menu. On Leap and Tumbleweed, this means booting relies instead on the startup.nsh in the EFI partition. This occurs on Aarch64 with both AMD/AMI firmware and Tianocore/edk2/OpenPlatformPkg firmware. Steps to reproduce: 1. Install Leap 42.1 from the OEM image 2. Restart and boot the system 2a. Observe that the startup.nsh (in the EFI partition) is used to boot the system. 3. Reboot again, but During boot-up, enter the EFI menu. 3a. Observe that in the boot manager in the EFI menus, there is no entry for Leap. 4. Restart the system or select the UEFI shell option, booting from startup.nsh 5. From the command prompt in Leap, run: grub2-install /dev/sda 6. Reboot the system 7. During start-up enter the EFI menu. 7a. Observe that in the EFI menu there is an entry called opensuse-leap42.1-arm-jeos-devel-efi, or something like it. 8. Select the opensuse-leap* boot menu item and try to boot it. 9. Observe that it does not boot, and returns to the boot menu. 10. Select the UEFI Shell option, and observe that it will boot using startup.nsh. 11. From the Linux command prompt, run "efibootmgr -v" 11a. Observe that the entry for opensuse-leap* is truncated :( 11b. Note the same can be observed by running "dumpstore" from the EFI environment. Note: The same thing happens if the bootloader is re-installed using "yast2 bootloader". Note that this is broken in Leap, but works fine in SLES, probably because the path and OS name for SLES is so much shorter. Interestingly, if I try to add my own entry with the proper path: efibootmgr -c -d /dev/sda -p 1 --loader "EFI\\opensuse-leap42.1-arm-jeos-devel-efi\\grubarm64.efi" -L Test_Entry_By_Alan and then inspect it with: efibootmgr -v I see my entry is truncated too :( Boot0007* Test_Entry_By_Alan HD(1,800,64004,cb3a713f-f051-4c9c-b643-b9e1358f6c2d)File(EFI\opensuse-leap42.1-arm-jeos-devel-ef) In summary, grub2-install and/or efibootmgr is simply putting a boot entry into NVRAM that is truncated and not valid. Thanks! Alan. -- You are receiving this mail because: You are on the CC list for the bug.

2 20

[Bug 973590] New: weird layout of bootloader screen
by bugzilla_noreply＠novell.com 21 Sep '22

21 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=973590 Bug ID: 973590 Summary: weird layout of bootloader screen 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: dmueller(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- While updating the openQA needle for openSUSE on AArch64 people noted that the "indentation" of the items in the ncurses ui looks slightly awkward. Is it intended that there is this huge empty space at the top left corner? -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 958483] New: 3rd party application UI is not behaving as required
by bugzilla_noreply＠novell.com 21 Sep '22

21 Sep '22

http://bugzilla.suse.com/show_bug.cgi?id=958483 Bug ID: 958483 Summary: 3rd party application UI is not behaving as required Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: tchvatal(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When using 3rd party module (like Virtualization) that tries to install additional packages it at this moment works like this when you are in X environment: For each package there is pop-up showing progress and then this pop-up is closed. This causes severe issue if user runs compoziting enabled environment. Imagine it like disco-bulb turning on and off as only on-top window is supposed to be rendered right and all the underlying windows are greyed out. More apps you install the more "funky" blinking you get. Prefferable solution would be to somehow include the yast2 sw_single interface that has the bottom progressbar and prints the installed packages. Added value would be mostly for openSUSE, where the default DE's have enabled compositing, but also for SLE case it would get at minimal prettier and at best more understandable about what is happening for the installed packages. For openSUSE it is quite commonly reported issue as I closed 3-4 during the bugzilla cleanup mentioning this problem. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 966042] New: yast command-line usage emits "unable to close filehandle properly" warning at exit
by bugzilla_noreply＠novell.com 09 Sep '22

09 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=966042 Bug ID: 966042 Summary: yast command-line usage emits "unable to close filehandle properly" warning at exit Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: bk(a)ancilla.ca QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Specifically, it says: Warning: unable to close filehandle properly: Bad file descriptor, <STDIN> line 21 during global destruction (#1) (S io) An error occurred when Perl implicitly closed a filehandle. This usually indicates your file system ran out of disk space. This happens with (as far as I can tell, I haven't tested exhaustively) all command-line yast invokations that involve a module. So, e.g., "yast users help" or "yast sysconfig help" will produce this message. "yast help" on its own, however, won't. It does not appear to affect yast's exit code, or it's ability to do its job; if I run "yast sysconfig set LOADER_TYPE=none", it does the right thing and then produces that message while exiting. Despite the hint that it may be space-related, this happens on multiple computers, all of them with plenty of space available on all filesystems. These systems are all running recent (~2 weeks) versions of Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 952799] New: bogofilter-{db,sqlite3} insists on using wordlist.tc
by bugzilla_noreply＠novell.com 06 Sep '22

06 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=952799 Bug ID: 952799 Summary: bogofilter-{db,sqlite3} insists on using wordlist.tc Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gour(a)atmarama.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In the past, when using other Linux distros I was mostly using bogofilter with sqlite3 back-end, but after switching to openSUSE I've decided to convert to 'default' (Berkeley) DB backend. Unfortunately, after bogofilter package was updated in openSUSE, it looks it does insist on using $HOME/.bogofilter/wordlist.tc for the database name even if one uses Berkeley DB or Sqlite3 back-ends? When I try to use my old wordlist.db, Bogofilter plugin (Claws & Evolution) starts from the scratch and creates wordlist.tc. I wonder about this line in *.spec: %if 0%{?suse_version} > 1320 iow. whether the new Bogofilter package is ready to use existing setup with appropriate back-end (not equal to TokyoCabinet)? -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 907495] New: adding a manual route to a dhcp configured interface results in failed dhcp setup (wicked managed)
by bugzilla_noreply＠novell.com 26 Aug '22

26 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=907495 Bug ID: 907495 Summary: adding a manual route to a dhcp configured interface results in failed dhcp setup (wicked managed) Classification: openSUSE Product: openSUSE 12.3 Version: Final Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hpj(a)urpla.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When adding a manual route to a dhcp configured eth interface managed by wicked, the dhcp setup fails with a silly message: device enp7s0 failed: "call to org.opensuse.Network.Addrconf.ipv4.static.requestLease failed: General failure" Add a manual route to a dhcp configured interface and restart your system. Be prepared, that this interface will not come up correctly. BTW: the routing editor allows selecting configured interfaces only. The usual order is: setup interface, add route, but you have to confirm the interface setup first, reenter yast network and add the interface based route there after. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 992494] New: áÁéÉíÍóÓúÚüÜ cannot be typed in any app using Asturian language and spanish Asturian variant keyboard
by bugzilla_noreply＠novell.com 23 Aug '22

23 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=992494 Bug ID: 992494 Summary: áÁéÉíÍóÓúÚüÜ cannot be typed in any app using Asturian language and spanish Asturian variant keyboard Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: enolp(a)softastur.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The key combination for typing áÁéÉíÍóÓúÚüÜ does not working, (they appear as aAeEiIoOuUuU), by setting "España - asturianu (ast_ES)" locale and "Asturian (Spain, with bottom-dot H and bottom-dot L)" keyboard layout in any application. However, Ḥḥ, Ḷḷ and Ññ Asturian letters are typed correctly in KDE and GTK applications except Firefox, where all works perfectly. yast2-country package was recently patched because of a similar bug, but updating it, doesn't fix the problem. https://bugzilla.suse.com/show_bug.cgi?id=981008 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[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 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