June 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1137448] New: plasma5-pk-updates does not update notifications
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137448 Bug ID: 1137448 Summary: plasma5-pk-updates does not update notifications Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- plasma5-pk-updates creates persistent notifications every time something noteworthy happens. Those are never updated though and are quite annoying, especially for openQA. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1101628] Can't boot kernel for Tumbleweed installation
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1101628 http://bugzilla.suse.com/show_bug.cgi?id=1101628#c8 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |oy8oom6r(a)gmail.com Flags| |needinfo?(oy8oom6r(a)gmail.co | |m) --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- We moved a bit and we are now at 5.x kernels. Does this still happen? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1097841] [Build 2094.1] openQA test fails in first_boot - sometime got kernel panic
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1097841 http://bugzilla.suse.com/show_bug.cgi?id=1097841#c10 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |zluo(a)suse.com Flags| |needinfo?(zluo(a)suse.com) --- Comment #10 from Jiri Slaby <jslaby(a)suse.com> --- DOes this still happen? We moved a bit further in time (and kernel versions). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1119646] package perl-Curses is broken
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1119646 http://bugzilla.suse.com/show_bug.cgi?id=1119646#c3 --- Comment #3 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- @Werner, if it is not possible to enable them from ncurses I'll redefine them inside the perl-Curses package. Just for reference, here is the list of all not found symbols: function 'wattr_get' NOT found function 'color_content' NOT found function 'pair_content' NOT found function 'getyx' NOT found function 'getparyx' NOT found function 'getbegyx' NOT found function 'getmaxyx' NOT found function 'getsyx' NOT found function 'mousemask' NOT found function 'wmouse_trafo' NOT found function 'flusok' NOT found function 'getcap' NOT found function 'touchoverlap' NOT found function 'menu_format' NOT found function 'scale_menu' NOT found function 'menu_spacing' NOT found function 'scale_form' NOT found function 'field_info' NOT found function 'dynamic_field_info' NOT found Of course, not all symbols are needed and some of them are already deprecated. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1099745] [kubic][transactional server] systemd fails to boot, reports $subvolume already mounted
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1099745 http://bugzilla.suse.com/show_bug.cgi?id=1099745#c9 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #9 from Jiri Slaby <jslaby(a)suse.com> --- The patch was reenabled by: commit dd5896fb0ebbd1ff0e66df934aa7bd5dce2c4590 (origin/users/dsterba/master/for -next) Author: David Sterba <dsterba(a)suse.com> Date: Wed Jul 4 13:28:23 2018 +0200 Update patches.suse/btrfs-8447-serialize-subvolume-mounts-with-potentially-mi.patch (bsc#951844 bsc#1024015 bsc#1099745). Refresh and update for Tumbleweed. No better patch version yet. Can we close this or are we waiting for some better upstream fix? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136601] Installed grub (grubaa64.efi) is not signed - Yast-bootloader does not support SecureBoot on aarch64
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136601 http://bugzilla.suse.com/show_bug.cgi?id=1136601#c19 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #19 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- List of SR: * Grub2: https://build.opensuse.org/request/show/707954 * Yast2-bootloader: https://build.opensuse.org/request/show/708010 * perl-Bootloader: https://build.opensuse.org/request/show/708011 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137061] shim-install generates a EFI/opensuse/grub.cfg which does NOT mount btrfs subvolume /boot/grub2/x86_64-efi
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1137061 http://bugzilla.suse.com/show_bug.cgi?id=1137061#c13 --- Comment #13 from Michael Chang <mchang(a)suse.com> --- (In reply to Neil Rickert from comment #6) > "grub.efi" has to be a one-size fits all. It is digitally signed at build > time, so cannot be adapted to a particular install situation. And there is > no "btrfs" subvolume for people not using "btrfs". Yes, this is risky to break things which reminds me of resistance of doing it unless really necessary to. > > By contrast, the "grubx64.efi" (which is a copy of > "/boot/grub2/x86_64-efi/core.efi" is built at install time as part of > installing grub2, so it is adapted to what you need. > > Yes, I agree that this bug should probably be closed. But I prefer to leave > that to someone from the openSUSE development team. Perhaps they need to > add a more detailed description as to what that "secure boot support" flag > does in Yast bootloader. It means we'll install every bits necessary to boot from secure boot enabled firmware, but using unsigned kernel is not possible (So by no means you'll ever need 'linux' here). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137061] shim-install generates a EFI/opensuse/grub.cfg which does NOT mount btrfs subvolume /boot/grub2/x86_64-efi
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1137061 http://bugzilla.suse.com/show_bug.cgi?id=1137061#c12 --- Comment #12 from Michael Chang <mchang(a)suse.com> --- (In reply to Steffen Winterfeldt from comment #11) > I'm moving this to the grub2 maintainer for comments. > > Michael, feel free to close if nothing should be done on the grub side in > your opinion. Yes, I was aware of the issue but hesitate to add it to shim-install, the reasoning was as what Neil have pointed out -> we disabled loading external modules for secure boot so it doesn't matter at all whether the module can be found for the intended use case. And also I'm reluctant to touch the shim-install script, could anything go wrong in it sometimes took long to get noticed as the turnaround time from Microsoft's signing takes months, not days, weeks ... So all must be very careful on that. But I also see your point, the behavior is inconsistent for btrfs and the rest of other filesystems. Think twice and now I'm inclined to accept it as a problem, as long as we are having a real bug report for it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1119895] Factory: kmod fails to build on s390x
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1119895 http://bugzilla.suse.com/show_bug.cgi?id=1119895#c5 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(msuchanek(a)suse.co | |m) | --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- Fixed as a side-effect of this -next commit: commit 10077c9f2dae1afabab2808a0326ecf3e8e5a82c Author: Masahiro Yamada <yamada.masahiro(a)socionext.com> Date: Fri May 17 16:54:27 2019 +0900 s390: drop meaningless 'targets' from tools Makefile Pushed to master & stable. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124544] New: KDE automatically logs in
by bugzilla_noreply＠novell.com 06 Jun '19

06 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124544 Bug ID: 1124544 Summary: KDE automatically logs in Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: riderexmachina(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On openSUSE Tumbleweed, KDE will sometimes log in automatically when coming back from suspend (lid close) or start up. -- You are receiving this mail because: You are on the CC list for the bug.

1 8