July 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185528] shim-15.4-lp152.4.6.1 fails to mirror enrolled keys
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1185528 https://bugzilla.suse.com/show_bug.cgi?id=1185528#c4 Darius Davis <darius(a)vmware.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |darius(a)vmware.com --- Comment #4 from Darius Davis <darius(a)vmware.com> --- Created attachment 850727 --> https://bugzilla.suse.com/attachment.cgi?id=850727&action=edit Verbose shim console log from VMware virtual machine I can reproduce the exact same problem in a VMware virtual machine: shim seems to enrol the added MOK correctly but does not reflect it into MokListRT, and "mokutil -l" reports that "MokListRT is empty". It's super easy to collect logs from the VM, so I've attached the console-log.txt with the verbose shim log captured from EFI's StdErr. The debug logs from the hypervisor (not attached here) show that our virtual NVRAM device is operating as expected, only the "expected" errors appear (i.e. buffer-too-small when sizing a buffer for GetVariable), and there is plenty of free variable space... over 200 kBytes free, and a maximum variable size of just under 64 kBytes. Let me know if I can perform any further tests or provide any further information. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1156745] [Build 20191112] openQA test fails in libreoffice_recent_documents; keyboard shortcuts can't open some menu in gtk3 under wayland
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1156745 https://bugzilla.suse.com/show_bug.cgi?id=1156745#c1 --- Comment #1 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: desktopapps-documentation-wayland https://openqa.opensuse.org/tests/1813915 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187138] Document required AutoYaST XML changes for Leap 15.3
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187138 https://bugzilla.suse.com/show_bug.cgi?id=1187138#c4 --- Comment #4 from Georg Pfuetzenreuter <mail(a)georg-pfuetzenreuter.net> --- Hi Carla, Thanks for getting back. I was thinking, for example bug 1187180 or 1184457 or some of the no-longer existing patterns would have been handy to be informed about upon migrating my YaST deployment to 15.3. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184457] Additional, non-specified, firewall rules are being added during the deployment
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184457 https://bugzilla.suse.com/show_bug.cgi?id=1184457#c9 Georg Pfuetzenreuter <mail(a)georg-pfuetzenreuter.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #848067|0 |1 is obsolete| | Attachment #848333|0 |1 is obsolete| | Status|RESOLVED |REOPENED Resolution|NORESPONSE |--- Assignee|yast2-maintainers(a)suse.de |mail(a)georg-pfuetzenreuter.n | |et --- Comment #9 from Georg Pfuetzenreuter <mail(a)georg-pfuetzenreuter.net> --- Created attachment 850726 --> https://bugzilla.suse.com/attachment.cgi?id=850726&action=edit Update: Leap 15.3 Hi! Apologies for re-opening this, but whilst the solution worked flawlessly on 15.2, now on 15.3, I encounter error messages during the deployment whilst using the same firewall section in my autoinst.xml. It looks like it no longer "likes" empty values. Would you be so kind to check my screenshots and XML file once again? Note that it continued to produce error messages for all the defined zones, I only attached one of them, as the error message is the same with all of them. Also note that the installed system does not show any services in the YaST firewall, so the solution still seems to work, just with added error messages during the installation which need to manually be confirmed. Best, Georg -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187734] inst_system_analysis.rb failed with 'undefined method `fetch' for "":String' (NoMethodError).
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187734 https://bugzilla.suse.com/show_bug.cgi?id=1187734#c4 --- Comment #4 from Georg Pfuetzenreuter <mail(a)georg-pfuetzenreuter.net> --- Thank you very much! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186561] pipewire user services presets are not set on a new installation
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1186561 https://bugzilla.suse.com/show_bug.cgi?id=1186561#c6 --- Comment #6 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2021:0953-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1186561 CVE References: JIRA References: Sources used: openSUSE Leap 15.2 (src): systemd-presets-common-SUSE-15-lp152.9.9.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187946] New: openSUSE DVD ISO upgrade - Numerous use of word "update"
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187946 Bug ID: 1187946 Summary: openSUSE DVD ISO upgrade - Numerous use of word "update" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Minor Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: tonysu(a)su-networking.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- We who use openSUSE differ from numerous other distros in that we clearly differentiate between an update making minor changes and an upgrade which is also referred to as a "distribution upgrade" which makes major changes to the system. Although I doubt anyone would be confused or cause problems during an upgrade, it would be good form to use the "upgrade" term properly instead of "update" as is seen in many places during the DVD upgrade. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187945] New: openSUSE 15.3 ISO Upgrade - Modify Repos has been removed
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187945 Bug ID: 1187945 Summary: openSUSE 15.3 ISO Upgrade - Modify Repos has been removed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: tonysu(a)su-networking.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Running an upgrade from 15.2 > 15.3. Specifically using an DVD ISO to upgrade, It looks like the simple solution to modify repo URLs has been to simply remove all old repos and install repos likely with the $releasever variable. A consequence of removing all repos entirely is that if the User has any number of repos with sometimes odd or unusual URI paths, those will all have to be researched and set up again, or the User has to cancel the upgrade, backup or otherwise archive the repo list and then run the upgrade again. Of course, the upgrade repo option other than to remove the repo is impossible, which is to leave the repo enabled with the 15.2 repo path. Request for future ISO upgrades is to re-enable the "Disable" option, and optionally to make the necessary path changes to use $releasever. If this request is implemented, maybe a warning should also display that disabled repos should not be re-enabled without close examination to make sure the repo exists for the upgraded openSUSE version and verified configured properly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187859] New: filesystem repository path missmatch on Leap15.3 and SLE 15SP3
by bugzilla_noreply＠suse.com 02 Jul '21

02 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187859 Bug ID: 1187859 Summary: filesystem repository path missmatch on Leap15.3 and SLE 15SP3 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: kokeko(a)mac.com QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- Report bug on following requet. https://bugzilla.opensuse.org/show_bug.cgi?id=1187770 filesystem repository Leap 15.3 and SLE 15SP3 's repository paths is miss configure. https://build.opensuse.org/repositories/filesystems openSUSE_Leap_15.3 x86_64 Repository paths: openSUSE:Leap:15.3:Update/standard openSUSE:Leap:15.3/standard SLE_15_SP3 x86_64 Repository paths: SUSE:SLE-15-SP3:GA/standard It is not accesss to SLE update repo and cannot update kernel module package. please add SLE15-SP3 update repo? openSUSE:Backports:SLE-15-SP3:Update/standard -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1187259] Tearing prevention only works on Full screen repaints
by bugzilla_noreply＠suse.com 01 Jul '21

01 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187259 http://bugzilla.opensuse.org/show_bug.cgi?id=1187259#c4 --- Comment #4 from Stefan Dirsch <sndirsch(a)suse.com> --- I think you need to enable TearFree here. # man xorg.conf Option "TearFree" "boolean" Disable or enable TearFree updates. This option forces X to per- form all rendering to a backbuffer prior to updating the actual display. It requires an extra memory allocation the same size as a framebuffer, the occasional extra copy, and requires Damage tracking. Thus enabling TearFree requires more memory and is slower (reduced throughput) and introduces a small amount of output latency, but it should not impact input latency. However, the update to the screen is then performed synchronously with the vertical refresh of the display so that the entire update is completed before the display starts its refresh. That is only one frame is ever visible, preventing an unsightly tear between two visible and differing frames. Note that this replicates what the compositing manager should be doing, however TearFree will redirect the compositor updates (and those of fullscreen games) directly on to the scanout thus incurring no additional overhead in the composited case. Also note that not all compositing man- agers prevent tearing, and if the outputs are rotated, there will still be tearing without TearFree enabled. Default: TearFree is disabled. --> /etc/X11/xorg.conf.d/50-device.conf Section "Device" Identifier "Default Device" Driver "intel" Option "TearFree" "on" EndSection -- You are receiving this mail because: You are on the CC list for the bug.

1 0