December 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1206069] New: VUL-0: CVE-2022-4170: rxvt-unicode: code execution via background OSC
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206069 Bug ID: 1206069 Summary: VUL-0: CVE-2022-4170: rxvt-unicode: code execution via background OSC Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/349770/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mrueckert(a)suse.com Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2022-4170 Posted by David Leadbeater on Dec 05I've discovered rxvt-unicode 9.25 and 9.26 are vulnerable to remote code execution, in the Perl background extension, when an attacker can control the data written to the user's terminal and certain options are set. The "background" extension is automatically loaded if certain X resources are set such as 'transparent' (see the full list at the top of src/perl/background[1]). So it is possible to be using this... References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4170 https://seclists.org/oss-sec/2022/q4/168 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206063] New: inkscape doesn't start, missing lib
by bugzilla_noreply＠suse.com 06 Dec '22

06 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206063 Bug ID: 1206063 Summary: inkscape doesn't start, missing lib Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bugz57(a)top.geek.nz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Name : inkscape Version : 1.2.1 Release : lp154.106.1 Architecture: x86_64 Distribution: graphics / 15.4 Graphics repo. > inkscape inkscape: error while loading shared libraries: libinkscape_base.so: cannot open shared object file: No such file or directory This is a tad ridiculous, do the packagers give things a sanity check to see if they as much as start up? Same as bug 1193183 for openSUSE 15.3. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1193183] New: inkscape-1.1.1-lp153.87.2 is not working
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193183 Bug ID: 1193183 Summary: inkscape-1.1.1-lp153.87.2 is not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: michael.kasimir(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- as reported in openSUSE support mailing list 28 Nov 2021 18:36 https://lists.opensuse.org/archives/list/support@lists.opensuse.org/thread/… after upgrade from 15.2 to 15.3, the start of inkscape could not be launched. Package version: inkscape-1.1.1-lp153.87.2.x86_64.rpm Terminal .bash run shows the following error message: $ inkscape inkscape: error while loading shared libraries: libinkscape_base.so: cannot open shared object file: No such file or directory As message shows apparently it should have to do with libinkscape_base.so The issue has been verified on a new, updated Leap 15.3 system and inkscape installed via opi from graphics-repository https://download.opensuse.org/repositories/graphics/openSUSE_Leap_15.3/x86_… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1195435] Braille translation mismatches with 'liblouis'
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1195435 https://bugzilla.suse.com/show_bug.cgi?id=1195435#c7 --- Comment #7 from Michael Gorse <mgorse(a)suse.com> --- Make sure you're using the translation table for the type of Braille that you're trying to generate. I'm not sure why you're using en-chardefs.cti; it is an include used in a few tables and appears not to be a full translation table in and of itself. There are multiple English Braille codes. In the U.S., for instance, there is the older EBAE code (the en-us-*.ctb tables in liblouis give you that in various forms). UEB is newer and was designed to unify the various English Braille codes (liblouis has en-ueb-*.ctb for that). If I translate using en-ueb-g1.ctb, rather than en-chardefs.cti, then I get results much closer to what you're expecting. The results for the symbols still differ slightly, and I'm not sure why off-hand; it may or may not be a bug in liblouis. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205818] Issues with barrierc KVM client since latest libX11 update
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205818 http://bugzilla.opensuse.org/show_bug.cgi?id=1205818#c34 --- Comment #34 from Stefan Dirsch <sndirsch(a)suse.com> --- https://build.opensuse.org/request/show/1040432 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205818] Issues with barrierc KVM client since latest libX11 update
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205818 http://bugzilla.opensuse.org/show_bug.cgi?id=1205818#c33 --- Comment #33 from Stefan Dirsch <sndirsch(a)suse.com> --- More back and forth. :-( Mon Dec 5 20:33:29 UTC 2022 - Stefan Dirsch <sndirsch(a)suse.com> - Update to version 1.8.1 This release fixes the --enable-thread-safety-constructor option to the configure script to work as intended. In the previous release, the changes for this option may not have been enabled when the option was not specified or when the --enable option was specified. While we have enabled it by default, believing that doing so will reduce the number of bugs users encounter running libX11 clients, in some cases it may expose bugs in which clients had previously gotten away with calling libX11 functions while a libX11 lock is already held, and thus now deadlock, as discussed in https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/157 - let's hope this version doesn't suffer yet from the regressions reported in boo#1205778, boo#1205818 (reported against 1.8.2); we need libX11 thread safe for totem (GNOME 43) :-( -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205778] Firefox sometimes hangs when copy / pasting with libx11 1.8.2
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205778 https://bugzilla.suse.com/show_bug.cgi?id=1205778#c17 --- Comment #17 from Stefan Dirsch <sndirsch(a)suse.com> --- https://build.opensuse.org/request/show/1040432 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205778] Firefox sometimes hangs when copy / pasting with libx11 1.8.2
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205778 https://bugzilla.suse.com/show_bug.cgi?id=1205778#c16 --- Comment #16 from Stefan Dirsch <sndirsch(a)suse.com> --- More back and forth. :-( Mon Dec 5 20:33:29 UTC 2022 - Stefan Dirsch <sndirsch(a)suse.com> - Update to version 1.8.1 This release fixes the --enable-thread-safety-constructor option to the configure script to work as intended. In the previous release, the changes for this option may not have been enabled when the option was not specified or when the --enable option was specified. While we have enabled it by default, believing that doing so will reduce the number of bugs users encounter running libX11 clients, in some cases it may expose bugs in which clients had previously gotten away with calling libX11 functions while a libX11 lock is already held, and thus now deadlock, as discussed in https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/157 - let's hope this version doesn't suffer yet from the regressions reported in boo#1205778, boo#1205818 (reported against 1.8.2); we need libX11 thread safe for totem (GNOME 43) :-( -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205947] Image downloads from downloadcontent-us1.opensuse.org not working
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205947 https://bugzilla.suse.com/show_bug.cgi?id=1205947#c3 --- Comment #3 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- I changed the config on Downloadcontent-us1 today to forward .tar.gz files to the Nuremberg server. I plan to have a closer look into the problem later this week. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205950] New: waybar can not be updated
by bugzilla_noreply＠suse.com 05 Dec '22

05 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205950 Bug ID: 1205950 Summary: waybar can not be updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Problem: the to be installed waybar-0.9.16-1.1.x86_64 requires 'waybar-branding = 0.9.16', but this requirement cannot be provided not installable providers: waybar-branding-upstream-0.9.16-1.1.noarch[repo-oss] Solution 1: deinstallation of waybar-0.9.15-1.2.x86_64 Solution 2: deinstallation of waybar-branding-openSUSE-0.14-1.7.noarch Solution 3: keep obsolete waybar-0.9.15-1.2.x86_64 Solution 4: break waybar-0.9.16-1.1.x86_64 by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

1 4