September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1199020] Wrong resolution at Installation / Window background not cleared
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199020 https://bugzilla.suse.com/show_bug.cgi?id=1199020#c61 --- Comment #61 from Stefan Hundhammer <shundhammer(a)suse.com> --- So AFAICS while using a nice dpi value that can be divided by 48 probably prevents drawing artifacts for rendering fonts, at the same time scaling it up to 200% is way over the top. Desktop scaling factors e.g. in KDE Plasma use multiples of 25%, i.e. 100%, 125%, 150%, 200%; and that seems to work quite well. I don't see a reason why that shouldn't work for our YaST installer. So we should make Qt not enforce such rigid scaling factors and rather stick with what we tell it with the Xft.dpi X resource; that's already rounded well enough. I'll try different scale factor rounding policies; that seems to be the root of the problem here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199020] Wrong resolution at Installation / Window background not cleared
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199020 https://bugzilla.suse.com/show_bug.cgi?id=1199020#c60 --- Comment #60 from Stefan Hundhammer <shundhammer(a)suse.com> --- AFAICS we have two heuristics which are now (since the introduction of that scale factor rounding) defeating each other: - We calculate a DPI value from the physical screen dimensions in millimeters that "xrandr" reports and "clean it up", i.e. we make sure it's a number that can be divided by 48 (but no less than 96), i.e. one of 96, 144, 192, 240, 288 (but no more than that) and set the "Xft.dpi" X resource to that value. - Qt reads that X resource and stores the value as QXcbScreen::logicalDpi() - It uses that value and a default dpi value of 96 to calculate a scaling factor, e.g. 144 / 96 = 1.5 (which would be a reasonable factor) - It uses its new default rounding policy for that factor to round it to the next integer number; in this case 2. - It now uses that nicely rounded scaling factor for everything: Window size, widget sizes including borders and line widths; and fonts. As a result, the fonts are now insanely oversized; no longer 150% of what we previously used, but 200%. And since all other geometry values in our YaST Qt UI depend on the font sizes, everything becomes way too large: Static texts, buttons, list content, everything. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202159] pssh throwing multiple Python errors
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202159 Jeff Lindholm <jlindholm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlindholm(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202159] pssh throwing multiple Python errors
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202159 https://bugzilla.suse.com/show_bug.cgi?id=1202159#c1 Diego Vinicius Akechi <dakechi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dakechi(a)suse.com --- Comment #1 from Diego Vinicius Akechi <dakechi(a)suse.com> --- Assigning to the current maintainer. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202159] pssh throwing multiple Python errors
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202159 Diego Vinicius Akechi <dakechi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|dakechi(a)suse.com |xliang(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203027] No way of setting mount points for btrfs subvolumes in YaST
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203027 https://bugzilla.suse.com/show_bug.cgi?id=1203027#c8 --- Comment #8 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- BEWARE: philosophical conversation/digression ahead (not really useful to get the main issue addressed). (In reply to Richard Brown from comment #6) > > Isn't that why the Installation Summary screen lets you review everything > YaST is doing before the install starts? Mostly true. The "everything" word is the only part that is a bit over the top. ;-) YaST cannot do everything that is technically possible in the system. As you mention, the user can always jump to the corresponding screen to correct unwanted decisions made by the automatic proposals... But, of course, the user can only modify those things that are supported by YaST. Whatever is not supported by YaST, falls out of that "everything". ;-) Several examples: YaST doesn't have the ability to configure LUKS2 unlocking via TPM2, YaST doesn't have the ability to define several mount points for the same block device, YaST doesn't have the ability to configure LVM cache (only bcache is supported) and YaST doesn't have the ability to define a subvolume whose mount point is not below the mount point of its corresponding Btrfs file-system. So there is no screen where the user can jump to "correct" those aspects of the proposal... because YaST can't simply do those things. In the TPM2 example, is not that YaST decided to use a password instead of TPM2 for LUKS2 unlocking. It's simply that using a passphrase is the only way YaST knows. So the user cannot "correct" the proposal to use a different unlocking mechanism, even if that is something that can perfectly be done manually. We are not talking about the automatic proposal choosing the wrong option, we are talking about YaST limitations and lack of features. In the same way, subvolumes in YaST have been historically limited to just be mounted below its file-system according to the path of the subvolume (so they are treated as subdirectories on steroids). It has been like that since Btrfs was introduced in the distribution. YaST has never offered the possibility to adjust the mount point or the mount options of a subvolume in a completely independent and arbitrary way. Cannot be done with the Expert Partitioner, cannot be done with AutoYaST, cannot be configured in the control file and, of course, the installer cannot propose it automatically. > The fact that YaST is auto-calculating mount points for subvolumes and not > giving users a chance to correct any mistakes and/or set mount points for > any additional subvolumes sure still feels like a bug to me that runs > counter to how we typically do everything else in YaST... I disagree with reasoning done to get to the idea that the current subvolume handling goes counter to how we do things in YaST (already explained). Having said that, I don't think it makes a big difference calling it a bug or a (lack of) feature. That doesn't change the fact that allowing totally arbitrary mount points (and mount options) per subvolume implies changing the whole historical approach of YaST to subvolumes. That means deep changes would be needed in YaST. Changes in the user interface, changes in the AutoYaST schema and, of course, internal changes. We really want to improve that part, but sadly we have not found time in the last couple of years because the people who sets the priorities always had something more pressuring. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199020] Wrong resolution at Installation / Window background not cleared
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1199020 https://bugzilla.suse.com/show_bug.cgi?id=1199020#c59 --- Comment #59 from Stefan Hundhammer <shundhammer(a)suse.com> --- My steadily growing collection of notes about this DPI and font size issue: https://gist.github.com/shundhammer/79d534b8452554b16fb2f667f58290f9 One noteworthy intermediate result is that Qt introduced a "rounding policy" for its scale factor with Qt 5.14 (i.e. not so long ago; right now we have 5.15 in TW), and it defaults to "Round", i.e. it will be rounded to the next integer number; so in practice, it's either 1.0 or 2.0, not 1.5 or similar which it might have used in the past; thus maybe the drastic increase of font sizes from a certain DPI value on. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202116] New: nvidia update 470.129.06 => 470.141.03 fails
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202116 Bug ID: 1202116 Summary: nvidia update 470.129.06 => 470.141.03 fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: paul.pgp-7(a)gmx.com QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- On openSUSE Leap 15.3 nvidia update (from https://download.nvidia.com/opensuse/leap/15.3) 470.129.06-lp153.57.1 => 470.141.03-lp153.53.1 fails due to: "nothing provides 'kernel-default-devel = 5.3.18-57'" The 15.3 kernel is currently at 5.3.18-150300.59.87.1 Full conflict log: #### YaST2 conflicts list - generated 2022-08-03 16:58:10 #### nothing provides 'kernel-default-devel = 5.3.18-57' needed by the to be installed nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] do not install nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] break nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 by ignoring some of its dependencies nothing provides 'kernel-default-devel = 5.3.18-57' needed by the to be installed nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] break nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 by ignoring some of its dependencies [ ] do not install x11-video-nvidiaG05-470.141.03-lp153.53.1.x86_64 nothing provides 'kernel-default-devel = 5.3.18-57' needed by the to be installed nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] do not install nvidia-glG05-470.141.03-lp153.53.1.x86_64 [ ] break nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 by ignoring some of its dependencies nothing provides 'kernel-default-devel = 5.3.18-57' needed by the to be installed nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 [ ] do not install nvidia-computeG05-470.141.03-lp153.53.1.x86_64 [ ] break nvidia-gfxG05-kmp-default-470.141.03_k5.3.18_57-lp153.53.1.x86_64 by ignoring some of its dependencies #### YaST2 conflicts list END ### -- You are receiving this mail because: You are on the CC list for the bug.

1 40

[Bug 1175328] ipmievd: not working
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1175328 https://bugzilla.suse.com/show_bug.cgi?id=1175328#c33 --- Comment #33 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2022:3143-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1175328,1181063 CVE References: JIRA References: Sources used: openSUSE Leap 15.3 (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Manager Server 4.1 (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Manager Retail Branch Server 4.1 (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Manager Proxy 4.1 (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Linux Enterprise Server for SAP 15-SP2 (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Linux Enterprise Server 15-SP2-LTSS (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Linux Enterprise Server 15-SP2-BCL (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Linux Enterprise Module for Server Applications 15-SP3 (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Linux Enterprise Module for Basesystem 15-SP3 (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Linux Enterprise High Performance Computing 15-SP2-LTSS (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Linux Enterprise High Performance Computing 15-SP2-ESPOS (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.1 SUSE Enterprise Storage 7 (src): ipmitool-1.8.18+git20200204.7ccea28-150200.3.8.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 1198794] scanimage -L: "No scanners were identified" for USB HP DeskJet F2492 All-in-One with "hpaio"
by bugzilla_noreply＠suse.com 07 Sep '22

07 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1198794 https://bugzilla.suse.com/show_bug.cgi?id=1198794#c41 --- Comment #41 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2022:3149-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 1198794 CVE References: JIRA References: Sources used: openSUSE Leap 15.4 (src): hplip-3.21.10-150400.3.3.1 SUSE Linux Enterprise Module for Desktop Applications 15-SP4 (src): hplip-3.21.10-150400.3.3.1 SUSE Linux Enterprise Module for Basesystem 15-SP4 (src): hplip-3.21.10-150400.3.3.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