October 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1146932] New: lvm cachepool on system lv causes system to be unbootable
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1146932 Bug ID: 1146932 Summary: lvm cachepool on system lv causes system to be unbootable Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: william.brown(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- If a suse leap 15.1 machine is configured post-install to have a lvm cache pool device on the system lv, grub2 fails to boot with "Error invalid segment". IE the lvs are: # lvs home system rwi-aor--- 104.00g 100.00 root system rwi-aor--- 80.00g 100.00 swap system rwi-aor--- 8.00g 100.00 cache system rwi-aor--- .... -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1105075] New: grub2-once does not parse /etc/sysconfig/bootloader properly
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1105075 Bug ID: 1105075 Summary: grub2-once does not parse /etc/sysconfig/bootloader properly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jack(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 779931 --> http://bugzilla.suse.com/attachment.cgi?id=779931&action=edit Patch to make grub2-once sysconf parsing more permissive grub2-once parses /etc/sysconfig/bootloader to determine value of LOADER_TYPE variable. However the regular expression there assumes that loader type has to have quotes around the value which is not always the case (generally assignments are treated the same way as in shell). This causes failure of grub2-once when used on openstack instances. I suggest the regexp should be more permissive to allow but not require quotes. Something like attached patch. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1045886] New: ecryptfs problems with recent Tumbleweed
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1045886 Bug ID: 1045886 Summary: ecryptfs problems with recent Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: roger.whittaker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ecryptfs and the ecryptfs tools have stopped working correctly on recent versions of Tumbleweed. I noticed this because an existing ecryptfs Private directory could only be seen after a local login. ecryptfs-mount-private over ssh stopped working. On investigation, it is no longer possible to do ecryptfs-setup-private for a new user. $ ecryptfs-setup-private Enter your login passphrase [roger]: Enter your mount passphrase [leave blank to generate one]: ************************************************************************ YOU SHOULD RECORD YOUR MOUNT PASSPHRASE AND STORE IT IN A SAFE LOCATION. ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase THIS WILL BE REQUIRED IF YOU NEED TO RECOVER YOUR DATA AT A LATER TIME. ************************************************************************ Done configuring. Testing mount/write/umount/read... Inserted auth tok with sig [83ecc1d632221288] into the user session keyring Inserted auth tok with sig [90e42628446d371b] into the user session keyring mount: No such file or directory ERROR: Could not mount private ecryptfs directory In the system logs we see: 2017-06-25T07:04:39.396038+01:00 [localhost] kernel: [140502.266628] Could not find key with description: [90e42628446d371b] 2017-06-25T07:04:39.396052+01:00 [localhost] kernel: [140502.266630] process_request_key_err: No key 2017-06-25T07:04:39.396054+01:00 [localhost] kernel: [140502.266631] Could not find valid key in user session keyring for sig specified in mount option: [90e42628446d371b] 2017-06-25T07:04:39.396056+01:00 [localhost] kernel: [140502.266631] One or more global auth toks could not properly register; rc = [-2] 2017-06-25T07:04:39.396072+01:00 [localhost] kernel: [140502.266632] Error parsing options; rc = [-2] $ uname -r 4.11.6-1-default $ grep VERSION_ID /etc/os-release VERSION_ID="20170620" -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 941931] New: GRUB2 graphical menu is extremely slow
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=941931 Bug ID: 941931 Summary: GRUB2 graphical menu is extremely slow Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jmatejek(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 643998 --> http://bugzilla.suse.com/attachment.cgi?id=643998&action=edit screen showing output of vbeinfo i'm using an AMD GPU and a 2560x1440 native display. on this configuration, the GRUB2 UI is slow to the point of unusability; it takes a full second to flip from one menu item to another, 3-5s just to display the boot menu, before booting starts. drawing the chameleon logo is visible line-by-line, too lowering the resolution helps, at 1280x960x32 the speed is almost usable, 1280x960x16 is sluggish but OK (so i'm sticking with this resolution for now) my GPU is reported as follows: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] detected graphics modes are attached -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 1098354] New: VUL-0: CVE-2018-1002209: quazip: arbitrary file write vulnerability achieved by using a specially crafted zip archive
by bugzilla_noreply＠novell.com 18 Apr '22

18 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1098354 Bug ID: 1098354 Summary: VUL-0: CVE-2018-1002209: quazip: arbitrary file write vulnerability achieved by using a specially crafted zip archive Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://smash.suse.de/issue/208490/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: crrodriguez(a)opensuse.org Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- rh#1593011 A vulnerability has been found in the way developers have implemented the archive extraction of files. An arbitrary file write vulnerability, that can be achieved using a specially crafted zip archive (affects other archives as well, bzip2, tar,xz, war, cpio, 7z), that holds path traversal filenames. So when the filename gets concatenated to the target extraction directory, the final path ends up outside of the target folder. Of course if an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily. This affects multiple libraries that lacks of a high level APIs that provide the archive extraction functionality. References: https://snyk.io/research/zip-slip-vulnerability References: https://bugzilla.redhat.com/show_bug.cgi?id=1593011 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1002209 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1119186] New: KDE:Extra/kdevelop5: Code completion and parser don't work
by bugzilla_noreply＠novell.com 15 Apr '22

15 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1119186 Bug ID: 1119186 Summary: KDE:Extra/kdevelop5: Code completion and parser don't work Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: kde-maintainers(a)suse.de Reporter: krzysio.kurek(a)wp.pl QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- Installed with zypper without any additional parameters. Works with same options on the same project if using AppImage. -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1148955] New: regression: wicked obtains incorrect ipv4 address for bridge
by bugzilla_noreply＠novell.com 15 Apr '22

15 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1148955 Bug ID: 1148955 Summary: regression: wicked obtains incorrect ipv4 address for bridge Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With these files, wicked does not get the correct ipv4 address in Tumbleweed, but it does so in Leap, SLE15, SLE12: stein-schneider:/etc/sysconfig/network # head ifcfg-* ==> ifcfg-br0 <== BOOTPROTO='dhcp' BRIDGE='yes' BRIDGE_FORWARDDELAY='0' BRIDGE_PORTS='eth0' BRIDGE_STP='off' STARTMODE='auto' ==> ifcfg-eth0 <== BOOTPROTO='none' STARTMODE='auto' It gets some random address from the pool, instead of the assigned address for this specific MAC. With just this file it gets the expected address: ==> /etc/sysconfig/network/ifcfg-eth0 <== BOOTPROTO='dhcp' STARTMODE='auto' DHCLIENT_CLIENT_ID='01:00:26:55:23:e5:46' Appending the clientid to ifcfg-br0 makes zero difference. It just gets another random address from the pool. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1146017] New: UEFI "Boot Linux System" from installation media screen 2 consistently fails quickly
by bugzilla_noreply＠novell.com 11 Apr '22

11 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1146017 Bug ID: 1146017 Summary: UEFI "Boot Linux System" from installation media screen 2 consistently fails quickly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://forums.opensuse.org/showthread.php/537185-UEFI -installation-media-gt-Boot-Linux-System?p=2911641#pos t2911641 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 814369 --> http://bugzilla.opensuse.org/attachment.cgi?id=814369&action=edit y2logs .tgz from fresh installation of 15.2a build 481 on Asus Kaby Lake on which "Boot Linux System" last attempted Initial Summary: UEFI "Boot Linux System" from installation media screen 2 consistently fails quickly To reproduce: 1-boot installation media in UEFI mode 2-choose "More ..." 3-choose "Boot Linux System" 4-(optional) append/edit linuxefi line, e.g. add video=1440x900 and/or 3 and/or noresume or remove splash=silent 5-answer the questions asked/make appropriate selections about kernel, options and root filesystem Actual results: 1-instant message in yellow text on red background: "Sorry, system didn't boot" 2-on vtty4: kexec_file: kernel signature verification failed (-129). 3-sh: dmesg: command not found on tty9 4-tty[2,5,6] shell absent 5-sh: systemctl: command not found on tty9 Expected results: 1-installed system boots, or 2-something more than instant failure report Note: forum thread comments report failure also happens with a VM, and with 15.1, and with either OM or USB boot media. Other info from installation on which last attempt made (using NET OM): # efibootmgr BootCurrent: 0000 Timeout: 1 seconds BootOrder: 0000,0007,0006,0003 Boot0000* opensuse Boot0003* CD/DVD Drive Boot0006* Hard Drive Boot0007* UEFI: Optiarc DVD RW AD-7200S # parted -l highlights Disk /dev/sda: 40.0GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 337MB 336MB fat16 P01 EFI System (ESP) boot, esp 2 337MB 1202MB 865MB linux-swap(v1) P02 swapper swap 3 1202MB 9590MB 8389MB ext4 P03 linuxroot1 4 9590MB 40.0GB 30.4GB ext4 P04 linuxhome -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1134289] New: ghostscript should not have a hard dependency on AppArmor
by bugzilla_noreply＠novell.com 08 Apr '22

08 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1134289 Bug ID: 1134289 Summary: ghostscript should not have a hard dependency on AppArmor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: max(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As a matter of personal preference I ususally set a "don't install" lock on AppArmor in my installations. But with sr#687694 a hard runtime dependency on apparmor-abstractions was added to the ghostscript package, which in turn pulls other AppArmor packages and makes it impossible to have an AppArmor-free system with ghostscript. As AppArmor is optional, I don't think packages like ghostscript should have such a hard dependency on it. Instead it should either be a weak dependency or no dependency at all. If a hard dependency is needed for some reason the AppArmor stuff for GS should be in an optional subpackage to retain the possibility to install GS without AppArmor. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1115942] New: Fonts in all applications are green and magenta or have a cast of that
by bugzilla_noreply＠novell.com 07 Apr '22

07 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1115942 Bug ID: 1115942 Summary: Fonts in all applications are green and magenta or have a cast of that Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've updated to Tumbleweed yesterday morning (2018-11-13) and then all fonts started to have a green an magenta case or are mostly green. See https://xor.cryptomilk.org/pics/fonts.png -- You are receiving this mail because: You are on the CC list for the bug.

2 5