July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1096833] New: VUL-0: matrix-synapse: event visibility rules not applied correctly
by bugzilla_noreply＠novell.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1096833 Bug ID: 1096833 Summary: VUL-0: matrix-synapse: event visibility rules not applied correctly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: okurz(a)suse.com Reporter: astieger(a)suse.com QA Contact: security-team(a)suse.de Found By: --- Blocker: --- from https://github.com/matrix-org/synapse/releases/tag/v0.31.1 Changes in synapse v0.31.1 (2018-06-08) v0.31.1 fixes a security bug in the get_missing_events federation API where event visibility rules were not applied correctly. We are not aware of it being actively exploited but please upgrade asap. Bug Fixes: Fix event filtering in get_missing_events handler (PR #3371) https://github.com/matrix-org/synapse/commit/ad9edd1d968f19dd4d7c65102fe552… -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1201127] New: python-brotlicffi / setuptools build_ext reproducible builds
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201127 Bug ID: 1201127 Summary: python-brotlicffi / setuptools build_ext reproducible builds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mcepl(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- I found https://github.com/python-hyper/brotlicffi/blob/main/setup.py#L66 needed a "sorted(sources)" to become fully reproducible, but IMHO that should not have to be added into setup.py but one layer up, e.g. in build_ext similar to https://github.com/pypa/setuptools/commit/5a0404fa3875a069f7a6436f508116e85… https://github.com/pypa/setuptools/pull/1068/files -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1029190] New: Support for package variants according to the evaluation of bigger regular expressions
by bugzilla_noreply＠novell.com 24 Nov '22

24 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1029190 Bug ID: 1029190 Summary: Support for package variants according to the evaluation of bigger regular expressions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de CC: astieger(a)suse.com Found By: --- Blocker: --- I noticed that the parameter “--with-link-size=2” is used so far in a package specification. https://build.opensuse.org/package/view_file/openSUSE:Factory/pcre2/pcre2.s… This setting limits the size of regular expressions. I would like to work with bigger search patterns occasionally. So I suggest to generate also variants for this software with an internal link size of 3 (and 4) for the data processing with 8 and 16 bit characters. See also: Selection of system properties for the regular expressions engine at run time https://bugs.exim.org/show_bug.cgi?id=1922 By the way: How do you think about to use the specifications “LDFLAGS“ und “%{?_smp_mflags}“ as parameters for the script “%configure“ there? -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1201615] New: pcapdump does not work after installing
by bugzilla_noreply＠suse.com 23 Nov '22

23 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201615 Bug ID: 1201615 Summary: pcapdump does not work after installing Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jmader2(a)gmu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # zypper in pcapdump Loading repository data... Reading installed packages... Resolving package dependencies... The following 2 NEW packages are going to be installed: pcapdump perl-Net-Pcap # pcapdump Can't locate Data/Hexdumper.pm in @INC (you may need to install the Data::Hexdumper module) (@INC contains: /usr/lib/perl5/site_perl/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.26.1 /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.26.1 /usr/lib/perl5/5.26.1/x86_64-linux-thread-multi /usr/lib/perl5/5.26.1 /usr/lib/perl5/site_perl) at /usr/bin/pcapdump line 3. BEGIN failed--compilation aborted at /usr/bin/pcapdump line 3. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1200579] New: After upgrading Raspberry Pi4B from 15.3 to 15.4 Grub.cfg has 15.3 not 15.4 on menus
by bugzilla_noreply＠suse.com 23 Nov '22

23 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200579 Bug ID: 1200579 Summary: After upgrading Raspberry Pi4B from 15.3 to 15.4 Grub.cfg has 15.3 not 15.4 on menus Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: aarch64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: llrainey15(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I did 3 raspberry pi4b from 15.3 to 15.4. Everything boots normally but the grub menu shows 15.3 not 15.4. This did not happen on the X86-64 upgrades. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1201056] New: flatpak firefox from flathub chooses a bad quality helvetica font on some sites
by bugzilla_noreply＠suse.com 23 Nov '22

23 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201056 Bug ID: 1201056 Summary: flatpak firefox from flathub chooses a bad quality helvetica font on some sites Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: c.chalu(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859931 --> http://bugzilla.opensuse.org/attachment.cgi?id=859931&action=edit bad display with Helvetica Font Hello, On Tumbleweed : firefox from flathub uses a bad quality helvetica font, while firefox from openSUSE repository uses Liberation. See the screenshots. I have the same issue with flatpak on Leap 15.4 On fedora kinoite, firefox from flathub uses Liberation font, there is not the same bug as on openSUSE. Test with : https://github.com/vkohaupt/vokoscreenNG Operating System: openSUSE Tumbleweed 20220628 KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.2 Kernel Version: 5.18.6-1-default (64-bit) Graphics Platform: Wayland Processors: 8 �� 11th Gen Intel�� Core�� i7-1165G7 @ 2.80GHz Memory: 7.5 Gio of RAM Graphics Processor: Mesa Intel�� Xe Graphics Manufacturer: Micro-Star International Co., Ltd. Product Name: Modern 15 A11M System Version: REV:1.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1052740] New: convert X keyboards into kbd and set unicode console font for languages with non-Latin alphabets
by bugzilla_noreply＠novell.com 22 Nov '22

22 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1052740 Bug ID: 1052740 Summary: convert X keyboards into kbd and set unicode console font for languages with non-Latin alphabets Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Now openSUSE for languages with Latin alphabets use converted keyboard layouts from X into kbd, also use unicode console font (as converted layouts supports it). Remaining task is to do same transition for non-Latin console keyboard layouts and set appropriate console font. Perhaps we should preconfigure option to switch between native and US QWERTY in console for these non-Latin languages and keyboard layouts. As noted in https://bugzilla.suse.com/show_bug.cgi?id=942896#c70 , As noted in https://bugzilla.suse.com/show_bug.cgi?id=942896#c69 Greek seems not have converted console keyboard layout from X into kbd. For Greek perhaps we can use eurlatgr console font (like for Latin alphabets) All Cyrillic layouts now use UniCyr_8x16.psf font, but this font seems to be compatible with cp866, cp1251, iso8859-5 and koi8-r (according http://www.tldp.org/HOWTO/Belarusian-HOWTO/x28.html) and not compatible with unicode per se. But openSUSE seems don't provide converted layouts for Russian, Ukrainian, Serbian, Bulgarian, Tajik. For Cyrillic alphabets we should use LatArCyrHeb-14, LatArCyrHeb-16+ or LatArCyrHeb-16 console font, that support unicode. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1178338] New: [installation] Support for 64-bit processors on motherboards with 32-bit UEFI (mixed-mode support)
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1178338 Bug ID: 1178338 Summary: [installation] Support for 64-bit processors on motherboards with 32-bit UEFI (mixed-mode support) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: jslaby(a)suse.com QA Contact: jsrain(a)suse.com CC: glin(a)suse.com, jens(a)krieger-juhnke.de, jlee(a)suse.com, jslaby(a)suse.com, mbenes(a)suse.com, mchang(a)suse.com, tiwai(a)suse.com Blocks: 1172292 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1172292 +++ On some devices (In my case a Lenovo Ideapad 100s-11iby) have 64 bit processors, but a 32-bit UEFI, so the 64-bit installation mediums are not recognized by it. Steps to Reproduce: 1. Grab a device with a 64-bit processor and a 32-bit UEFI 2. Try to boot from a 64-bit installation medium Actual Results: The installation medium is not listed in the boot menu. Expected Results: The installation medium is listed correctly, just like on a machine with a 64-bit UEFI. I did a bit of research, and found out the following: Fedora has natively supported 32-bit UEFI for 64 bit installs since Fedora 27. There seems to be a a workaround, but this is not very practical for new users, which adds a file from Github (https://github.com/hirotakaster/baytail-bootia32.efi) to the installation medium. ===================== Could x86_64 installation media contain this file on the installation media in the EFI partition: EFI/boot/bootia32.efi ? It should be copied from /usr/share/efi/i586/grub.efi from grub2-i386-efi package, the same as is EFI/boot/bootx64.efi from grub2-x86_64-efi. This will add support for 32bit FW with 64-bit CPUs. It used to work fine when I tried last time on such a machine. I had EFI/boot/bootia32.efi on an USB stick and loaded config from a DVD. Then continued the installation the usual way. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1196085] New: Calling external programs from YaST fragile with full paths
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1196085 Bug ID: 1196085 Summary: Calling external programs from YaST fragile with full paths Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: shundhammer(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After a security audit some years ago we changed all calls to external programs in YaST to use the full path, i.e. from "foobar" to "/sbin/foobar". The rationale was that this would prevent a potential attacker from manipulating the $PATH to include some directory containing a malicious version of the program, i.e. a "/my/hacked/foobar" with $PATH also containing "/my/hacked". With the transition from /bin to /usr/bin and /sbin to /usr/sbin that turned out to be a bad idea since now we need to update those full paths in the YaST code whenever any of those binaries makes that transition, i.e. it's moved from /sbin to /usr/sbin. Worse, if the transition is done in one supported product like Tumbleweed or Leap, yet another one like SLES still uses the old path, we would have to maintain different paths (and not forget to adapt them when that other product makes that transition as well); or we would need to create our own fallback logic to search all the possible paths which one to invoke. But that fallback logic exists, and if handled correctly, it's just as secure as using a full path; but more flexible and not fragile against tools being moved from one system location to another: It's $PATH. We need to make sure that $PATH only contains directories that are not writeable by non-privileged users, and of course not "." (the current directory) or any path that starts with "."; e.g. export PATH="/usr/sbin:/usr/bin:/sbin:/bin" And we already do that in YaST code. So we should migrate calls to external programs back to calling them without the full path and use our secure $PATH instead. For a more in-depth discussion, see also https://github.com/yast/yast-iscsi-client/issues/111 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1190524] New: baloo keeps my laptop hot
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190524 Bug ID: 1190524 Summary: baloo keeps my laptop hot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: saba(a)sabanet.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Build Identifier: Baloo file indexer is running since days at 100% CPU and I'm not sure if it will ever finish. Reproducible: Always Steps to Reproduce: 1. Installed Tumbleweed from scratch on a brand new notebook (LG gram 2021 i7-1165G7) 2. Copied my home directory from my old laptop (approx. 700GB of data) 3. Watch baloo running at 100% CPU for days/weeks Actual Results: Baloo seems to get slower and slower: gram:~> balooctl status ; sleep 3600 ; balooctl status Baloo File Indexer is running Indexer state: Indexing file content Total files indexed: 3,683,585 Files waiting for content indexing: 160,364 Files failed to index: 0 Current size of index is 71.48 GiB Baloo File Indexer is running Indexer state: Indexing file content Total files indexed: 3,683,065 Files waiting for content indexing: 159,844 Files failed to index: 0 Current size of index is 71.48 GiB This means in one hour the number of files waiting to be indexed decreased only by 520 (which would mean 7 seconds to add a single file to the index). At this speed, I'd need to wait another 300 hours before the indexer completed its job. Expected Results: Indexing should complete *much* faster. -- You are receiving this mail because: You are on the CC list for the bug.

1 4