December 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1180071] New: Allow YaST to Force a Seperate Unencrypted Boot Partition
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1180071 Bug ID: 1180071 Summary: Allow YaST to Force a Seperate Unencrypted Boot Partition Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PC OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: christian.hollinger2003(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.67 Safari/537.36 Build Identifier: It would be nice if YaST could be configured during installation to have a seperate, unencrypted boot partition. This way, the user would not have to enter the same encryption password twice during boot. I would suggest that, if this is implemented; this be set as the default setting when Disk Encryption is enabled in YaST during installation. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1173712] $releasever in add_on_repositories.xml does not work
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1173712 https://bugzilla.suse.com/show_bug.cgi?id=1173712#c10 --- Comment #10 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2020:3807-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1172870,1173712 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): yast2-packager-4.2.67-3.12.1 SUSE Linux Enterprise Installer 15-SP2 (src): yast2-packager-4.2.67-3.12.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179449] VUL-1: CVE-2020-11867: audacity: saves temporary files to /var/tmp/audacity-$USER by default, which permissions are set to 755.
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179449 https://bugzilla.suse.com/show_bug.cgi?id=1179449#c9 --- Comment #9 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2020:2261-1: An update that fixes one vulnerability is now available. Category: security (moderate) Bug References: 1179449 CVE References: CVE-2020-11867 JIRA References: Sources used: openSUSE Leap 15.2 (src): audacity-2.2.2-lp152.4.3.1 openSUSE Leap 15.1 (src): audacity-2.2.2-lp151.3.3.1 openSUSE Backports SLE-15-SP2 (src): audacity-2.2.2-bp152.4.3.1 openSUSE Backports SLE-15-SP1 (src): audacity-2.2.2-bp151.4.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179061] Yast2 bootloader fails with: parent subvolume not found by uuid
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1179061 https://bugzilla.suse.com/show_bug.cgi?id=1179061#c12 --- Comment #12 from Karl Mistelberger <karl.mistelberger(a)nefkom.net> --- Added https://download.opensuse.org/repositories/YaST:Head/openSUSE_Tumbleweed/Ya… and installed libstorage-ng1: Yast2 bootloader works again. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177358] EFI system partition: VFAT or FAT16 or FAT12 or FAT32?
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1177358 https://bugzilla.suse.com/show_bug.cgi?id=1177358#c7 --- Comment #7 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Nikolai Nikolaevskii from comment #6) > Good, but not excellent. Excellence is definitely not the goal of the automatic partitioning proposal. It must be a one-size-fits-all solution that causes no problems, specially to newbies. > Minimal FAT32 partition has 32 MiB in size, As far as I know, that's not true for Advanced Format 4K Native drives (4-KB-per-sector). As commented several times before in this and other bugs, the minimum FAT32 size in those systems is 256 MiB, as reported by this official Microsoft document: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/confi… > minimal FAT16 partition has 4.1 > MiB in size (with ordinary settings). > Typical occupied space for openSUSE installation is 7-8 MiB in /boot/efi/. > > You may change suggested minimal size: > > ------------------------------------------------------------------- > When proposing a new EFI partition in x86 > ... > - when aiming for the minimal size > * does not enforce FAT32 or 16 (FAT size will be decided by USER) > * requires /boot/efi to be at least 32 MiB > * requires /boot/efi to be at most 512 MiB > ------------------------------------------------------------------- > > > Changes: > 1. "decided by mkfs.vfat" -> "decided by user" How exactly would that be decided by the user? This is about the automatic partitioning proposal. It should be calculated without user intervention. At most, the user could influence some aspects using the "Guided Setup" button, but IMO there is no room in the Guided Setup for advanced questions like the size of the FAT table. Of course the user can decide to tweak the size of the partition or the type of the FAT table using the Expert Partitioner. But that's a completely different matter, out of the scope of this bug. > 2. "to be at least 128 MiB" -> "to be at least 32 MiB". Which will leave no room for other operating systems to be installed in the same machine. Again, that could be fine for an advanced user who can use the Expert Partitioner, but I don't think it's an educated default. The document already linked above states that MS Windows expects at least 100MiB there. You are free to kill the possibility of installing other operating systems in the same machine by using the Expert Partitioner to define your own partitioning schema, but I don't think the automatic proposal should do that. It should stay safe. > Hint: UEFI specification requires support for long file names (LFN) for all > FAT32/16/12, i.e. FATxx will always goes with VFAT. YaST uses vfat in all cases, so we should be safe in that regard. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[opensuse-bugs] [Bug 1179085] New: llvm8 and llvm9 fail to build with '-mbranch-protection=standard' option
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1179085 Bug ID: 1179085 Summary: llvm8 and llvm9 fail to build with '-mbranch-protection=standard' option Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com Found By: --- Blocker: --- Created attachment 843787 --> http://bugzilla.opensuse.org/attachment.cgi?id=843787&action=edit llvm9 build log llvm8 and llvm9 fail to build with '-mbranch-protection=standard' option introduced in Factory last Friday (20th of November). Relevant error log seems to be: [12856s] [1300/5627] CCACHE_CPP2=yes CCACHE_HASHDIR=yes /usr/bin/ccache /home/abuild/rpmbuild/BUILD/llvm-9.0.1.src/stage1/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Target/AArch64/Disassembler -I../lib/Target/AArch64/Disassembler -I../lib/Target/AArch64 -Ilib/Target/AArch64 -Iinclude -I../include -Ilib/Target/AArch64/Disassembler/.. -I../lib/Target/AArch64/Disassembler/.. -mbranch-protection=standard -O2 -Wall -D_FORTIFY_SOURCE=0 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -fPIC -fvisibility-inlines-hidden -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wno-comment -Wstring-conversion -fdiagnostics-color -ffunction-sections -fdata-sections -O2 -g -DNDEBUG -fno-exceptions -MD -MT lib/Target/AArch64/Disassembler/CMakeFiles/LLVMAArch64Disassembler.dir/AArch64Disassembler.cpp.o -MF lib/Target/AArch64/Disassembler/CMakeFiles/LLVMAArch64Disassembler.dir/AArch64Disassembler.cpp.o.d -o lib/Target/AArch64/Disassembler/CMakeFiles/LLVMAArch64Disassembler.dir/AArch64Disassembler.cpp.o -c ../lib/Target/AArch64/Disassembler/AArch64Disassembler.cpp [12856s] FAILED: lib/Target/AArch64/Disassembler/CMakeFiles/LLVMAArch64Disassembler.dir/AArch64Disassembler.cpp.o [12856s] CCACHE_CPP2=yes CCACHE_HASHDIR=yes /usr/bin/ccache /home/abuild/rpmbuild/BUILD/llvm-9.0.1.src/stage1/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Target/AArch64/Disassembler -I../lib/Target/AArch64/Disassembler -I../lib/Target/AArch64 -Ilib/Target/AArch64 -Iinclude -I../include -Ilib/Target/AArch64/Disassembler/.. -I../lib/Target/AArch64/Disassembler/.. -mbranch-protection=standard -O2 -Wall -D_FORTIFY_SOURCE=0 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -fPIC -fvisibility-inlines-hidden -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wno-comment -Wstring-conversion -fdiagnostics-color -ffunction-sections -fdata-sections -O2 -g -DNDEBUG -fno-exceptions -MD -MT lib/Target/AArch64/Disassembler/CMakeFiles/LLVMAArch64Disassembler.dir/AArch64Disassembler.cpp.o -MF lib/Target/AArch64/Disassembler/CMakeFiles/LLVMAArch64Disassembler.dir/AArch64Disassembler.cpp.o.d -o lib/Target/AArch64/Disassembler/CMakeFiles/LLVMAArch64Disassembler.dir/AArch64Disassembler.cpp.o -c ../lib/Target/AArch64/Disassembler/AArch64Disassembler.cpp [12856s] fatal error: error in backend: fixup value out of range -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 951144] kdump package should try both kexec_load and kexec_file_load interface
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=951144 https://bugzilla.suse.com/show_bug.cgi?id=951144#c20 Petr Tesa��k <ptesarik(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.hiller(a)hpe.com --- Comment #20 from Petr Tesa��k <ptesarik(a)suse.com> --- *** Bug 1115252 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1065588] These packages need to be selected to install: ntfs-3g, ntfsprogs
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1065588 https://bugzilla.suse.com/show_bug.cgi?id=1065588#c19 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #19 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Implemented in yast2-storage-ng 4.3.30, which has been already submitted to openSUSE Tumbleweed (see https://build.opensuse.org/request/show/856005) and will be part of the installer in openSUSE Leap 15.3. For those devices that are intended to be mounted in the final system, the corresponding packages are still added to the software proposal as required. But packages associated to devices that will not be mounted are only added as optional, which means the user can de-select them without blocking the whole system installation. For example, if the system contains a file system that are not assigned to any mount point (let's say, a NTFS or JFS partition from another operating system), the user can deselect the corresponding packages and finish the installation without them. See more details at https://github.com/yast/yast-storage-ng/pull/1188 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1168077] Yast2 Partitioner refreshes repositories prior to performing partitioning operations
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1168077 https://bugzilla.suse.com/show_bug.cgi?id=1168077#c12 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED --- Comment #12 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #5) > > On the other hand, we could fine-tune the list of packages we try to > install. Implemented in yast2-storage-ng 4.3.30, which has been already submitted to openSUSE Tumbleweed (see https://build.opensuse.org/request/show/856005) and will also be available in openSUSE Leap 15.3. Now the Partitioner will only check and install packages that are needed in order to perform the requested operations, ignoring devices that are not involved in the changes. As a side effect of that, the mere presence of NTFS file systems will not longer trigger an extra repository refresh, except in cases in which those file systems are going to be modified or created. See more details at https://github.com/yast/yast-storage-ng/pull/1188 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176706] fpc PIE linking fails in Tumbleweed
by bugzilla_noreply＠suse.com 15 Dec '20

15 Dec '20

https://bugzilla.suse.com/show_bug.cgi?id=1176706 https://bugzilla.suse.com/show_bug.cgi?id=1176706#c14 --- Comment #14 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1176706) was mentioned in https://build.opensuse.org/request/show/856001 15.2 / fpc -- You are receiving this mail because: You are on the CC list for the bug.

1 0