March 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207289] New: windows:mingw:win{32|64}: drop obsolete BuildRoot: line in spec files
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207289 Bug ID: 1207289 Summary: windows:mingw:win{32|64}: drop obsolete BuildRoot: line in spec files Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- In the past, several changes were made to the packages of the listed projects, including the removal of the line "BuildRoot:". As this is used by many *.spec files (398 out of 547 existing): osc co windows:mingw:win32 cd windows:mingw:win32 find -maxdepth 2 -type f -name '*.spec' -exec grep -Hn "BuildRoot:" {} \; | wc -l 398 find -maxdepth 2 -type f -name '*.spec' | wc -l 547 it could save the packagers time to do this removal as a bulk change with: osc co windows:mingw:win32 cd windows:mingw:win32 find -maxdepth 2 -type f -name '*.spec' -exec gawk -i inplace '$1 == "BuildRoot:" { getline } { print $0}' {} \; osc ci -m "Drop BuildRoot:" -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1195094] New: nVidia: Remove generic (fb) driver first ...
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1195094 Bug ID: 1195094 Summary: nVidia: Remove generic (fb) driver first ... Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- Users of nVidia's proprietary driver are running into issues with the introduction of 'simpledrm'. https://forums.developer.nvidia.com/t/510-39-01-on-5-16-0-kernel-green-scre… There are workarounds available like a) patching the nvidia kernel module and no longer calling pci_request_regions(...) function b) Kernel option 'initcall_blacklist=simpledrm_platform_driver_init' c) Kerneloption ' fbcon=map:1'. But the culprit is that nVidia doesn't remove the generic driver (e.g. efifb/vesafb) first. This should be changed to address the real issue here. API under MIT license https://elixir.bootlin.com/linux/latest/source/include/drm/drm_aperture.h Example for nouveau driver. https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/nouveau/nouv… Thomas is the author of 'simpledrm'. Please correct me, if I misunderstood anything and feel free to add more details here. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1209875] New: [selinux] avc: denied for systemd-journal and /var/log/journal
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209875 Bug ID: 1209875 Summary: [selinux] avc: denied for systemd-journal and /var/log/journal Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: jsegitz(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying selinux in TW (in permissive mode) I received this from audit: > audit: type=1400 audit(1680075283.980:3): avc: denied { getattr } for pid=417 comm="systemd-journal" path="/var/log/journal/7154b830e6bb8a683db5d8d6000008fd/system@6e7e34a4fb8148f0be0964b88a38691f-0000000000128c14-0005f803c6a14050.journal" dev="sda1" ino=524660 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1 > audit: type=1400 audit(1680075284.252:4): avc: denied { read } for pid=417 comm="systemd-journal" name="system@6e7e34a4fb8148f0be0964b88a38691f-0000000000128c14-0005f803c6a14050.journal" dev="sda1" ino=524660 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1 > audit: type=1400 audit(1680075284.252:5): avc: denied { open } for pid=417 comm="systemd-journal" path="/var/log/journal/7154b830e6bb8a683db5d8d6000008fd/system@6e7e34a4fb8148f0be0964b88a38691f-0000000000128c14-0005f803c6a14050.journal" dev="sda1" ino=524660 scontext=system_u:system_r:syslogd_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=1 So maybe there are some rules for persistent journal missing? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202260] New: qemu 7.0 breaks gnulib tests
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1202260 Bug ID: 1202260 Summary: qemu 7.0 breaks gnulib tests Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: li.zhang(a)suse.com Reporter: schwab(a)suse.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The linux-user emulation in qemu 7.0 breaks the gnulib test test-free, as seen in various packages. https://build.opensuse.org/package/live_build_log/devel:RISCV:ALP/diffutils… https://build.opensuse.org/package/live_build_log/devel:RISCV:ALP/grep/stan… https://build.opensuse.org/package/live_build_log/devel:RISCV:ALP/findutils… FAIL: test-free =============== ***MEMORY-ERROR***: qemu-riscv64[11423]: GSlice: failed to allocate 496 bytes (alignment: 512): Cannot allocate memory FAIL test-free (exit status: 139) -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1202588] New: okular, forms, checkbox, chek mark not recorded in the document
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202588 Bug ID: 1202588 Summary: okular, forms, checkbox, chek mark not recorded in the document Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- SUMMARY the check mark is recorded in the form and not recorded in the document. STEPS TO REPRODUCE 1. open a pdf with forms 2. click on a checkbox 3. a check mark is written 4 record and close the document 5 open the document the checkbox is empty, no check mark 6 activate the forms there is a check mark in the checkbox No problem with text box ADDITIONAL INFORMATION open the modified and recorded document with LibreOffice Draw the check mark does not appears in the checkbox The kde team says : it is a poppler problem solved with the new version. See https://bugs.kde.org/show_bug.cgi?id=458062 please update poppler to the last version. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1176302] New: keyboard: Switch kbd keyboard defaults to xkb based ones
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1176302 Bug ID: 1176302 Summary: keyboard: Switch kbd keyboard defaults to xkb based ones Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: sbrabec(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In past, kbd had its own keymaps with different names and layouts than xkb. Several years ago we generated a set of new keymaps based on xkb keymaps, and moved old ones to the kbd-legacy sub-package. But these keymaps are still not used by default. To fix this situation, we have to: 1. Change YaST keymap selection. kbd keymap should have the same name as xkb keymap. 2a. Change keymap search path inside kbd. In case of name conflict prefer the one from /usr/share/kbd/keymaps/xkb. or 2b. When YaST will pick keymap, it will use fully qualified path. I would prefer 2a. 3. Write a migration %post script that will perform one-shot migration of legacy keymaps to xkb ones. (I will just fetch the history of keyboard/src/data/keyboards.rb 4. Remove kbd-legacy from the default installation. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1165282] New: Add browse option for selecting custom boot PBR
by bugzilla_noreply＠novell.com 05 Apr '23

05 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1165282 Bug ID: 1165282 Summary: Add browse option for selecting custom boot PBR Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: i686 OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: smetz3(a)gmu.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When installing with a custom boot, the installer has an entry field for the device into whose PBR the installer will write the loader. It would be nice to have a browse button that presented a list of all known partitions. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1159595] New: Installed vms use a path-id for suspend instead of uuid.
by bugzilla_noreply＠novell.com 05 Apr '23

05 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1159595 Bug ID: 1159595 Summary: Installed vms use a path-id for suspend instead of uuid. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: william.brown(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When the system is installed with default partitioning (no changes), which should use UUID's, suspend to disk in /etc/default/grub is configured with swap by a path-id instead. This can lead to VM's that are unable to boot when their swap partition changes location (IE changing from virtio to scsi) or a hardware machine that changes pci paths in some way (relocation of a disk controller or disk controller replacement due to RMA etc). This causes machines to be unbootable because the resume=/dev/disk/path-id can never be resolved and has an infinite timeout. The machine then must be forced off and the resolution steps are unclear Work around is to add noresume at boot, and to edit /etc/default/grub post install to remove the resume option. See also: https://bugzilla.suse.com/show_bug.cgi?id=1159236 -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1187782] New: YaST2 NFS server does not export file shares
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1187782 Bug ID: 1187782 Summary: YaST2 NFS server does not export file shares Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: jm-hotmail(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- At the conclusion of establishing a network share with YaST2 NFS server, one must manually export the share(s), either with the command exportfs -a (or -rav, etc.), or restart the server. The Reference manual does not mention this in section 22.3 (https://doc.opensuse.org/documentation/leap/reference/html/book-reference/c…) Could the exportfs function be added to the YaST2 process? -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1194851] New: autoyast replaces $releasever in add-on repos with the version number (e.g. 15.3) in /etc/zypp/repos.d files
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1194851 Bug ID: 1194851 Summary: autoyast replaces $releasever in add-on repos with the version number (e.g. 15.3) in /etc/zypp/repos.d files Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers(a)suse.de Reporter: adaugherity(a)tamu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 855378 --> https://bugzilla.suse.com/attachment.cgi?id=855378&action=edit AutoYaST add-on profile Summary: basically #1172477, but for AutoYaST I have the update repos added to my autoyast profile so that the latest packages are installed from the start, rather than having to do the install and then run updates. See the attached file for details. (It uses my internal mirror for most repos, but this issue applies equally to download.opensuse.org.) I've started using $releasever in the AY profile so I don't have to modify it for every new release. This works, but the generated /etc/zypp/repos.d/*.repo files contain the specific version (e.g. 15.3) rather than $releasever, so when it comes time to upgrade to the next release, the documented upgrade procedure of 'zypper --releasever ...' will not work. Example: <media_url>http://download.opensuse.org/update/leap/$releasever/sle/</media_url> in the AY profile gets turned into baseurl=http://download.opensuse.org/update/leap/15.3/sle in the repo file. Note that this only applies to the URL -- $releasever in the name is left unmodified. It looks like this issue was originally fixed in AutoYaST in #972046; more details on GitHub: https://github.com/yast/yast-add-on/pull/28#issuecomment-291116098 . However, the code has been refactored since then and it seems the bug has reappeared. -- You are receiving this mail because: You are on the CC list for the bug.

1 18