December 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1174749] New: Gedit: gedit-ternimal can not change directory
by bugzilla_noreply＠suse.com 26 Nov '22

26 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174749 Bug ID: 1174749 Summary: Gedit: gedit-ternimal can not change directory Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 840229 --> http://bugzilla.opensuse.org/attachment.cgi?id=840229&action=edit The screen record Open a text document with gedit, pop the menu with right-click and choose "Change Directory" ingedit-ternimal, but nothing happens. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1193516] New: Telegram-desktop should be updated to a valid version
by bugzilla_noreply＠suse.com 26 Nov '22

26 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193516 Bug ID: 1193516 Summary: Telegram-desktop should be updated to a valid version Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 854394 --> http://bugzilla.opensuse.org/attachment.cgi?id=854394&action=edit 2.5.8 The Telegram-desktop popups a warning "Please update you app to the latest version. The version you are using is out of data and will not no longer work. " It should be updated for Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1193005] New: VUL-1: CVE-2021-41281: synapse: Path traversal when downloading remote media
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193005 Bug ID: 1193005 Summary: VUL-1: CVE-2021-41281: synapse: Path traversal when downloading remote media Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/315558/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: meissner(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2021-41281 https://github.com/matrix-org/synapse/releases/tag/v1.47.1 https://github.com/matrix-org/synapse/security/advisories/GHSA-3hfw-x7gx-43… Impact Synapse instances with the media repository enabled can be tricked into downloading a file from a remote server into an arbitrary directory, potentially outside the media store directory. The last two directories and file name of the path are chosen randomly by Synapse and cannot be controlled by an attacker, which limits the impact. Homeservers with the media repository disabled are unaffected. Homeservers configured with a federation whitelist are also unaffected. Patches Server administrators should upgrade to 1.47.1 or later. Workarounds Server administrators using a reverse proxy could, at the expense of losing media functionality, block the following endpoints: /_matrix/media/r0/download/{serverName}/{mediaId} /_matrix/media/r0/download/{serverName}/{mediaId}/{fileName} /_matrix/media/r0/thumbnail/{serverName}/{mediaId} Alternatively, non-containerized deployments can be adapted to use the hardened systemd config, located at contrib/systemd/override-hardened.conf. References n/a For more information If you have any questions or comments about this advisory, e-mail us at security(a)matrix.org. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1190038] New: VUL-0: CVE-2021-39164: matrix-synapse: Improper authorisation of /members discloses room membership to non-members
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190038 Bug ID: 1190038 Summary: VUL-0: CVE-2021-39164: matrix-synapse: Improper authorisation of /members discloses room membership to non-members Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/308825/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mrueckert(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: security-team(a)suse.de CC: asarai(a)suse.com Found By: Security Response Team Blocker: --- rh#1999844 Matrix is an ecosystem for open federated Instant Messaging and Voice over IP. In versions 1.41.0 and prior, unauthorised users can access the membership (list of members, with their display names) of a room if they know the ID of the room. The vulnerability is limited to rooms with `shared` history visibility. Furthermore, the unauthorised user must be using an account on a vulnerable homeserver that is in the room. Server administrators should upgrade to 1.41.1 or later in order to receive the patch. One workaround is available. Administrators of servers that use a reverse proxy could, with potentially unacceptable loss of functionality, block the endpoints: `/_matrix/client/r0/rooms/{room_id}/members` with `at` query parameter, and `/_matrix/client/unstable/rooms/{room_id}/members` with `at` query parameter. https://github.com/matrix-org/synapse/security/advisories/GHSA-3x4c-pq33-4w… https://github.com/matrix-org/synapse/releases/tag/v1.41.1 https://github.com/matrix-org/synapse/commit/cb35df940a References: https://bugzilla.redhat.com/show_bug.cgi?id=1999844 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-39164 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39164 https://github.com/matrix-org/synapse/security/advisories/GHSA-3x4c-pq33-4w… https://github.com/matrix-org/synapse/releases/tag/v1.41.1 https://github.com/matrix-org/synapse/commit/cb35df940a -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1190037] New: VUL-0: CVE-2021-39163: matrix-synapse: Adding a private/unlisted room to a community exposes room metadata in an unauthorised manner
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190037 Bug ID: 1190037 Summary: VUL-0: CVE-2021-39163: matrix-synapse: Adding a private/unlisted room to a community exposes room metadata in an unauthorised manner Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/308826/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mrueckert(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: security-team(a)suse.de CC: asarai(a)suse.com Found By: Security Response Team Blocker: --- rh#1999846 Matrix is an ecosystem for open federated Instant Messaging and Voice over IP. In versions 1.41.0 and prior, unauthorised users can access the name, avatar, topic and number of members of a room if they know the ID of the room. This vulnerability is limited to homeservers where the vulnerable homeserver is in the room and untrusted users are permitted to create groups (communities). By default, only homeserver administrators can create groups. However, homeserver administrators can already access this information in the database or using the admin API. As a result, only homeservers where the configuration setting `enable_group_creation` has been set to `true` are impacted. Server administrators should upgrade to 1.41.1 or higher to patch the vulnerability. There are two potential workarounds. Server administrators can set `enable_group_creation` to `false` in their homeserver configuration (this is the default value) to prevent creation of groups by non-administrators. Administrators that are using a reverse proxy could, with partial loss of group functionality, block the endpoints `/_matrix/client/r0/groups/{group_id}/rooms` and `/_matrix/client/unstable/groups/{group_id}/rooms`. https://github.com/matrix-org/synapse/security/advisories/GHSA-jj53-8fmw-f2… https://github.com/matrix-org/synapse/releases/tag/v1.41.1 https://github.com/matrix-org/synapse/commit/cb35df940a References: https://bugzilla.redhat.com/show_bug.cgi?id=1999846 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-39163 https://github.com/matrix-org/synapse/security/advisories/GHSA-jj53-8fmw-f2… http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39163 https://github.com/matrix-org/synapse/releases/tag/v1.41.1 https://github.com/matrix-org/synapse/commit/cb35df940a -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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 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 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 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