September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1193579] New: Lifearea misses python3-cairo dependency
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1193579 Bug ID: 1193579 Summary: Lifearea misses python3-cairo dependency Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: bluedzins(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Lifearea misses python3-cairo dependency, without using TrayIcon plugin is impossible, and in turn it is not possible to close&stay Lifera window, which for such type of the program is basically a must. For the record -- my report in Lifearea github: https://github.com/lwindolf/liferea/issues/1025 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1184334] New: Missing translation fixes for YaST and Welcome screen
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1184334 Bug ID: 1184334 Summary: Missing translation fixes for YaST and Welcome screen Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: noga.dany(a)gmail.com QA Contact: ke(a)suse.com Found By: --- Blocker: --- openSUSE-Leap-15.3-DVD-x86_64-Build117.13-Media.iso During installation via YaST with Czech translation I saw strange czech text "Zm��rn��n�� CPU" . I wanted to fix it, but it looks correct here https://l10n.opensuse.org/translate/yast-installation/master/cs/?checksum=6… Another wrong translation was with Welcome screen, where is czech text "Uk��zat p��i p��t��m sup��t��n��", where is typo, which I fixed almost year ago: https://l10n.opensuse.org/translate/opensuse-welcome/master/cs/?checksum=f7… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1185441] New: "system is compromised" during boot after grub2+shim update
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1185441 Bug ID: 1185441 Summary: "system is compromised" during boot after grub2+shim update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: robert.simai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed the most recent kernel-default-5.3.18-lp152.72.1.x86_64 shim-15.4-lp152.4.8.1.x86_64 grub2-2.04-lp152.7.25.1.x86_64 on my Dell Precision 3620 this week and rebooted as required. The system doesn't come up but shows "system is compromised" for a second, followed by power down. If I change from "UEFI with secure boot" to "UEFI without secure boot" it behaves well again and just boots. I've set "mokutil --set-verbosity true" as advised which outputs a lot of messages, I unfortunately have no serial console at hand to connect and save them. I'll try to attach a video from the screen that shows the boot process and messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1202281] New: UTF-8 smileys gone (or mutilated) in gnome-terminal, xemacs,...
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1202281 Bug ID: 1202281 Summary: UTF-8 smileys gone (or mutilated) in gnome-terminal, xemacs,... Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: gp(a)suse.com QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860713 --> https://bugzilla.suse.com/attachment.cgi?id=860713&action=edit Testfile with some UTF-8 smiley characters This is a recent (Tumbleweed 20220805) regression. UTF-8 smiley characters either are not rendered any more at all when viewed in gnome-terminal, XEmacs, LibreOffice Writer ... or rendered monochrome instead of yellow and harder to view. Firefox interestingly shows them properly, as I had it for the last years, when contents is pasted into a text field. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1186315] New: Flatpak packages installed without pre-configured repo, making "out-of-the-box" usage impossible
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1186315 Bug ID: 1186315 Summary: Flatpak packages installed without pre-configured repo, making "out-of-the-box" usage impossible Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: blst(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Flatpak's goal to make software installation easier on Linux systems. This approach was also designed for less experienced users. But the way it is implemented in Leap 15.2 makes it hard to use. 1) It is not installed per default (other distributions install the packages during the setup process) 2) The user can install the Flatpak system via the package manager, but after the installation it requires additional configuration. It seems that there are no Flatpak repos configured per default. The main source for Flakpak is flathub.org. To make at least the install command lines at Flathub working, I had to >flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo Suggestion a) add the Flathub repo per default or b) make a seperate flathub.org repo installation package available -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1188023] New: GNOME:Apps/fractal:
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188023 Bug ID: 1188023 Summary: GNOME:Apps/fractal: Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: william.brown(a)suse.com QA Contact: screening-team-bugs(a)suse.de Found By: --- Blocker: --- I've recently started a project to automatically scan for potential security issues in rust packages with cargo audit. I noticed the following on fractal: * RUSTSEC-2021-0026 -> crate: comrak, cvss: None, class: ['format-injection'] * RUSTSEC-2021-0063 -> crate: comrak, cvss: None, class: ['format-injection'] * RUSTSEC-2020-0060 -> crate: futures-task, cvss: None, class: ['code-execution', 'memory-corruption'] * RUSTSEC-2020-0059 -> crate: futures-util, cvss: None, class: ['thread-safety'] * RUSTSEC-2020-0146 -> crate: generic-array, cvss: None, class: ['memory-corruption'] * RUSTSEC-2021-0020 -> crate: hyper, cvss: None, class: ['format-injection'] Most of these should be able to be resolved with cargo update and re-vendoring the dependencies. Alternately upstream may have released a Cargo.toml/Cargo.lock with updates for this. It would be great if you could look into updating and resolving these :) Thank you! -- more info https://github.com/openSUSE/obs-service-cargo_audit/blob/main/README.md https://en.opensuse.org/Packaging_Rust_Software -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1201804] New: Building the GNOME text editor for PCRE2 usage
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201804 Bug ID: 1201804 Summary: Building the GNOME text editor for PCRE2 usage Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The dependencies for the software package ��gnome-text-editor 42.2-1.1�� contain the information ��Requires: libpcre.so.1()(64bit)��. How are the chances to support the API ��PCRE2�� (with library versions �� 10.40)? https://github.com/PCRE2Project/pcre2 https://build.opensuse.org/package/view_file/openSUSE:Factory/gnome-text-ed… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1196707] New: lxqt-config-appearance fails to open due to missing liblxqt-config-cursor.so
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1196707 Bug ID: 1196707 Summary: lxqt-config-appearance fails to open due to missing liblxqt-config-cursor.so Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: mvetter(a)suse.com Reporter: slemke(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- slemke@notebook:~> zypper info lxqt-config Loading repository data... Reading installed packages... Information for package lxqt-config: ------------------------------------ Repository : Main Repository Name : lxqt-config Version : 1.0.0-bp154.1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 1.3 MiB Installed : Yes (automatically) Status : up-to-date Source package : lxqt-config-1.0.0-bp154.1.1.src Upstream URL : http://www.lxqt.org Summary : LXQt Control Center Description : System Configuration and Control Center for LXQt slemke@notebook:~> slemke@notebook:~> lxqt-config-appearance lxqt-config-appearance: error while loading shared libraries: liblxqt-config-cursor.so: cannot open shared object file: No such file or directory slemke@notebook:~> Some maybe useful outputs: slemke@notebook:~> rpm -qa |grep -i lxqt |grep -c 1.0.0 25 slemke@notebook:~> rpm -qa |grep -ic lxqt 35 slemke@notebook:~> rpm -qa |grep -i lxqt |grep -v 1.0.0 patterns-lxqt-lxqt-20170319-lp154.1.2.x86_64 lxqt-theme-openSUSE-default-0.1-bp154.1.2.noarch lxqt-globalkeys-1.0.1-bp154.1.1.x86_64 lxqt-theme-openSUSE-leaper-0.1-bp154.1.2.noarch lxqt-globalkeys-lang-1.0.1-bp154.1.1.noarch lxqt-archiver-0.5.0-bp154.1.1.x86_64 lxqt-archiver-lang-0.5.0-bp154.1.1.noarch liblxqt-globalkeys-ui1-1.0.1-bp154.1.1.x86_64 liblxqt-globalkeys1-1.0.1-bp154.1.1.x86_64 lxqt-theme-openSUSE-light-0.1-bp154.1.2.noarch slemke@notebook:~> -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1200182] New: systemd-resolved cannot bind port 53
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200182 Bug ID: 1200182 Summary: systemd-resolved cannot bind port 53 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: paul(a)pbarker.dev QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a fresh installation of OpenSUSE MicroOS, I have attempted to switch to systemd-networkd and systemd-resolved to manage my network connections following the instructions in https://en.opensuse.org/Network_Management_With_Systemd. However, when trying to enable systemd-resolved I hit an error: alpha:~ # systemctl enable --now systemd-resolved Created symlink /etc/systemd/system/dbus-org.freedesktop.resolve1.service �� /usr/lib/systemd/system/systemd-resolved.service. Created symlink /etc/systemd/system/multi-user.target.wants/systemd-resolved.service �� /usr/lib/systemd/system/systemd-resolved.service. Job for systemd-resolved.service failed because the control process exited with error code. See "systemctl status systemd-resolved.service" and "journalctl -xeu systemd-resolved.service" for details. alpha:~ # journalctl -xeu systemd-resolved.service �� Subject: Automatic restarting of a unit has been scheduled �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� Automatic restarting of the unit systemd-resolved.service has been scheduled, as the result for �� the configured Restart= setting for the unit. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: Stopped Network Name Resolution. �� Subject: A stop job for unit systemd-resolved.service has finished �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A stop job for unit systemd-resolved.service has finished. �� The job identifier is 1376 and the job result is done. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: Starting Network Name Resolution... �� Subject: A start job for unit systemd-resolved.service has begun execution �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� A start job for unit systemd-resolved.service has begun execution. �� The job identifier is 1376. Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Positive Trust Anchors: Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.> Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Using system hostname 'alpha.cephei.uk'. Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to process RTNL link message: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to process RTNL link message: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to process RTNL link message: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv6(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to listen on UDP socket 127.0.0.53:53: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: Failed to start manager: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv4(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd-resolved[1643]: LLMNR-IPv6(UDP): Failed to bind socket: Permission denied Jun 02 21:51:19 alpha.cephei.uk systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE �� Subject: Unit process exited �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� An ExecStart= process belonging to unit systemd-resolved.service has exited. �� The process' exit code is 'exited' and its exit status is 1. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. �� Subject: Unit failed �� Defined-By: systemd �� Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel �� The unit systemd-resolved.service has entered the 'failed' state with result 'exit-code'. Jun 02 21:51:19 alpha.cephei.uk systemd[1]: Failed to start Network Name Resolution. It appears that the permission denied errors when systemd-resolved tried to bind port 53 are caused by SELinux. I confirmed that this is the case by disabling SELinux and retrying the command - this resulted in systemd-resolved successfully starting. Therefore I think there is an error in the SELinux policy here - systemd-resolved should be able to bind port 53 on localhost to offer DNS resolution services. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202351] New: dracut: remove mkinitrd wrapper
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1202351 Bug ID: 1202351 Summary: dracut: remove mkinitrd wrapper Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dracut-maintainers(a)suse.de Reporter: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Upstream support removed in March 2021 (https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation announcement on factory mailing list in May 2021 (https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…) ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in Tumbleweed first. Affected packages that need to be updated before (at least): # zypper se --requires mkinitrd Loading repository data... Reading installed packages... S | Name | Summary | Type ---+---------------------+----------------------------------------------------+-------- | kernel-debug | A Debug Version of the Kernel | package i+ | kernel-default | The Standard Kernel | package | kernel-default-base | The Standard Kernel - base modules | package | kernel-kvmsmall | The Small Developer Kernel for KVM | package | kernel-pae | Kernel with PAE Support | package | kernel-vanilla | The Standard Kernel - without any SUSE patches | package i | mdadm | Utility for configuring "MD" software RAID devices | package -- You are receiving this mail because: You are on the CC list for the bug.

1 16