July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1195269] Installation - license agreement empty - empty license translations
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195269 http://bugzilla.opensuse.org/show_bug.cgi?id=1195269#c21 --- Comment #21 from Lubos Kocman <lubos.kocman(a)suse.com> --- Hello team, the date for the QU1 respin is Wed, Oct 5th, 2022 Quarterly Update 1 from https://en.opensuse.org/openSUSE:Roadmap -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195269] Installation - license agreement empty - empty license translations
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195269 http://bugzilla.opensuse.org/show_bug.cgi?id=1195269#c20 --- Comment #20 from Ivan Vorstanenko <ivanvorstanenko(a)proton.me> --- I was checking skelcd-openSUSE package (by adding 15.4 and 15.4:Update repos), and rpm package has fixed. https://build.opensuse.org/package/binaries/home:ivanvorstanenko:branches:o… When is it planned to release ISOs of 15.4.1? As I understand, in ISOs of 15.4.1 license translations will be shown correct. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197911] firewalld Error when booting
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1197911 https://bugzilla.suse.com/show_bug.cgi?id=1197911#c8 --- Comment #8 from Otto Hollmann <otto.hollmann(a)suse.com> --- No, but changes were already submitted (private comment #6 that you probably can't see) so new (fixed) version will be released soon. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200583] New: FreeCAD Segfaults Opening Any Example (libc.so.6)
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200583 Bug ID: 1200583 Summary: FreeCAD Segfaults Opening Any Example (libc.so.6) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: drankinatty(a)suddenlinkmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE 15.4 Application: FreeCAD FreeCAD will start, but attempting to open ANY file or start a new drawing results in a Segfault. Running FreeCAD from the command line discloses the following: $ FreeCAD FreeCAD 0.19, Libs: 0.19RUnknown � Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2021 FreeCAD is free and open-source software licensed under the terms of LGPL2+ license. FreeCAD wouldn't be possible without FreeCAD community. ##### #### ### #### # # # # # # # ## #### #### # # # # # #### # # # # # # # ##### # # # # #### #### # # # # # # # # # # # # # # ## ## ## # # #### #### ### # # #### ## ## ## connect failed: No such file or directory Program received signal SIGSEGV, Segmentation fault. #0 /lib64/libc.so.6(+0x4ad70) [0x7fef891bbd70] -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1201366] New: split filesystem package
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201366 Bug ID: 1201366 Summary: split filesystem package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: lnussel(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1165830 Found By: --- Blocker: --- The filesystem package contains quite an amount of subdirectories that are not needed on smaller systems such as /usr/share/man or /usr/share/help including all possible locales. Could be split to have eg filesystem-man. A dependency generator could be used to automatically add necessary requires to packages that put files there. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1196547] MicroOS Desktop GNOME system role doesn't preinstall language subpackages
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196547 http://bugzilla.opensuse.org/show_bug.cgi?id=1196547#c11 --- Comment #11 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Alois Wohlschlager from comment #7) > What about enabling recommends, but shipping targeted locks to prevent > installation of the worst offenders by default? That's what I currently do > on my MicroOS system, since no-recommends is too barebones, and with my > approach I get the bloat down quite a bit If you have such a list already, a first approach could also be to try to simply file sr's to eliminate those recommends. That's what I did in the past with some packages and generally didn't get much pushback. Mind trying? :-) (In reply to Alois Wohlschlager from comment #10) > (In reply to Richard Brown from comment #8) > > > > Locks are a terrible cludge that just result in broken systems > > Ok, understood that this is not a generally applicable solution. > > > I'm all for installing all language patterns all the time, I'm not for > > installing GB and GB of random junk alongside them > > Well, but recommends are not supposed to be "random junk" anyway, but rather > "generally useful, but not strictly required". Where they do pull in random > junk, I see basically three categories: > 1a. Things that are generally useful on traditional systems, but not on > MicroOS (e.g. pulling in YaST or Firefox from various desktop patterns). > Does zypp have a way to express something like "Recommends: (MicroOS or > yast2)"? If so, these could be used for a fix. Yes that is likely possible via boolean dependencies. I wonder whether it's really needed though. I'd prefer to get rid of recommends. As OS vendor we have to decide whether a package is needed or not. A stricter definition of what is a mandatory part of the OS really helps in other areas too (eg transactional-update status). > 1b. Compatibility-related, but rarely useful things, I mainly think of the > kernel's "Recommends: kernel-firmware" here. This could be fixed the same > way as 1a. > 2. Things which are arguably plain bugs, such as pulling in Jupyter from > some SELinux-related packages. These should be fixed anyway. +1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201348] [Build 20220708] transactional update: exit 1 without real indication
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201348 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |iforster(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201262] New: kernel 5.18.9 hangs at luks encryption password prompt
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201262 Bug ID: 1201262 Summary: kernel 5.18.9 hangs at luks encryption password prompt Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bugs(a)clearingstelle-eeg-kwkg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We need to use Opensuse Leap 15.3 with the kernel installed from the Kernel-Backports repository: https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standar… because it is a Ryzen 4000 CPU computer. Everything worked fine. With the kernel update 5.18.9-lp153.3.1.ge00841d the computer hangs at boot at the password prompt for the luks encryption. No keyboard input from the laptop or from an external USB-Keyboard is accepted and the boot process stops. The Laptop is an Acer Travelmate P215-41, Model No: N19Q8, Model Name TMP215-41-R0WF. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1200744] New: MD-RAID1 refuses to assemble while "mdadm -E" says the disks are fine (v1.2 superblock)
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200744 Bug ID: 1200744 Summary: MD-RAID1 refuses to assemble while "mdadm -E" says the disks are fine (v1.2 superblock) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I migrated a Xen PVM to VMware. The VM also had an MD-RAID1 using metadata version 1.2. I copied the blocks from the old disks to the new ones using dd via SSH. When examining the disks on the new VM using "mdadm -E /dev/sdc", it reports a "clean" state and a "correct" checksum. For the other disk as well. Using "mdadm -v -A /dev/md1" it found both members for md1 and the corresponding slots, but fails to assemble saying "Invalid argument". Looking in syslog I see the kernel complains "md: sdc does not have a valid v1.2 superblock, not importing!" My guess is that new new disks are a bit larger than the original ones, but still: Shouldn't "mdadm -E" complain if the kernel would not accept the disk? Or should the kernel accept what mdadm accepts? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1197911] firewalld Error when booting
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1197911 https://bugzilla.suse.com/show_bug.cgi?id=1197911#c7 M. Edwin Zakaria <medwin(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |medwin(a)opensuse.org --- Comment #7 from M. Edwin Zakaria <medwin(a)opensuse.org> --- (In reply to Otto Hollmann from comment #5) > This bug was opened for Leap 15.3 and it already received update. > > But you are right, in leap 15.4 it's not yet fixed. Same patches are already > submitted into maintenence, but not yet released. I will ping responsible > people to get it released. Do you have any info when the update will be released for 15.4? -- You are receiving this mail because: You are on the CC list for the bug.

1 0