July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1199337] [Tumbleweed][libssh][Build_20220507] virsh remote connect by using libssh2 failed with "Username/PublicKey combination"
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1199337 Roy Cai <roy.cai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pstivanin(a)suse.com, | |roy.cai(a)suse.com, | |tjyrinki(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197458] [TW][Build 20220322][Security][OVMF][swtpm2.0] openQA test fails in tpm2_measured_boot
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1197458 Roy Cai <roy.cai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pstivanin(a)suse.com, | |roy.cai(a)suse.com, | |tjyrinki(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192106] New: [Tumbleweed][security][pam][Build_20211026] zypper in pam_mount failed
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1192106 Bug ID: 1192106 Summary: [Tumbleweed][security][pam][Build_20211026] zypper in pam_mount failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: weixuan.hao(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- susetest:~ # uname -m x86_64 susetest:~ # cat /etc/*release NAME="openSUSE Tumbleweed" # VERSION="20211026" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20211026" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20211026" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" Issue description: susetest:~ # zypper in pam_mount Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: pam_mount 1 new package to install. Overall download size: 0 B. Already cached: 110.7 KiB. After the operation, additional 303.4 KiB will be used. Continue? [y/n/v/...? shows all options] (y): y In cache pam_mount-2.18-1.7.x86_64.rpm (1/1), 110.7 KiB (303.4 KiB unpacked) Checking for file conflicts: ..................................................................................................................................[done] (1/1) Installing: pam_mount-2.18-1.7.x86_64 ..................................................................................................................[error] Installation of pam_mount-2.18-1.7.x86_64 failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/sbin/mount.crypt;617a4de9: cpio: open failed - No such file or directory error: pam_mount-2.18-1.7.x86_64: install failed Abort, retry, ignore? [a/r/i] (a): a Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1200767] Amarok doesn't start due to missing dbus service file
by bugzilla_noreply＠suse.com 10 Jul '22

10 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200767 https://bugzilla.suse.com/show_bug.cgi?id=1200767#c8 --- Comment #8 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2022:10050-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1200767 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP4 (src): amarok-2.9.75git.20220614T014846~dc55a00143-bp154.2.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195269] New: Installation - license agreement empty when selecting language French
by bugzilla_noreply＠suse.com 10 Jul '22

10 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1195269 Bug ID: 1195269 Summary: Installation - license agreement empty when selecting language French Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: michelduquaine(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 855699 --> https://bugzilla.suse.com/attachment.cgi?id=855699&action=edit screenshot During installation via YaST2 at "Language, Keyboard and License Agreement" page: when selecting Language => French, the License Agreement zone is empty (cfr attached screenshot) Expected : a french translation of the license agreement should be displayed -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1172650] License not displayed in german & other translated languages
by bugzilla_noreply＠suse.com 10 Jul '22

10 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1172650 https://bugzilla.suse.com/show_bug.cgi?id=1172650#c10 --- Comment #10 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2022:10051-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1172650,1195269 CVE References: JIRA References: Sources used: openSUSE Backports SLE-15-SP4 (src): translate-toolkit-2.5.0-bp154.2.3.1, translate-toolkit-test-2.5.0-bp154.2.3.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201351] New: MMIO Stale Data CPU bug present and SMT on, data leak possible
by bugzilla_noreply＠suse.com 10 Jul '22

10 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201351 Bug ID: 1201351 Summary: MMIO Stale Data CPU bug present and SMT on, data leak possible Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0 Build Identifier: I have updated openSUSE Tumbleweed (incl. firmware) today on my Lenovo Thinkpad T14. Then I wanted to check, whether all is fine again (after a former bug). The dmesg output is saying the following today: [ 0.116366] smp: Bringing up secondary CPUs ... [ 0.116366] x86: Booting SMP configuration: [ 0.116366] .... node #0, CPUs: #1 #2 #3 #4 [ 0.117480] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_s… for more details. [ 0.117480] #5 #6 #7 [ 0.121058] smp: Brought up 1 node, 8 CPUs It seems, that data leaks are possible at the moment. Reproducible: Always Steps to Reproduce: 1. Hardware: Lenovo ThinkPad T14 Gen 1 with Intel�� Core�� i7-10510U �� 8 2. Latest firmware updates and update of openSUSE Tumbleweed 3. dmesg output is referencing data leak Actual Results: data leak is possible Expected Results: No security issues -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1199323] New: telegram-desktop 3.7.3 (Qt6) static stickers are not displayed (qt.svg: Error while inflating gzip file: SVG format check failed)
by bugzilla_noreply＠suse.com 10 Jul '22

10 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199323 Bug ID: 1199323 Summary: telegram-desktop 3.7.3 (Qt6) static stickers are not displayed (qt.svg: Error while inflating gzip file: SVG format check failed) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ilya(a)ilya.cf QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating from 3.6.1 (Qt5) to 3.7.3 (Qt6) static stickers are not displayed. Static and animated emoticons and animated stickers are displayed, but static stickers are no longer. Log from Oss: (telegram-desktop:3102): Telegram-WARNING **: 23:35:50.586: Application was built without embedded fonts, this may lead to font issues. [ALSOFT] (EE) Failed to set real-time priority for thread: �� (1) error: : cannot open error: : cannot open error: : cannot open qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.svg: Error while inflating gzip file: SVG format check failed qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.svg: Error while inflating gzip file: SVG format check failed The binary build from the official site works fine. Log from official binary: [ALSOFT] (EE) Failed to set real-time priority for thread: �� (1) error: : cannot open error: : cannot open error: : cannot open qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment qt.gui.imageio.jpeg: Corrupt JPEG data: premature end of data segment And the worst thing 3.6.1 no longer builds in Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1149986] New: telegram-desktop cannot be started with enabled GTK integration and libqt5-qtstyleplugins-platformtheme-gtk2 installed
by bugzilla_noreply＠novell.com 10 Jul '22

10 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1149986 Bug ID: 1149986 Summary: telegram-desktop cannot be started with enabled GTK integration and libqt5-qtstyleplugins-platformtheme-gtk2 installed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: tux93(a)opensuse.org Reporter: tux93(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to start telegram-desktop built with enabled GTK integration and libqt5-qtstyleplugins-platformtheme-gtk2 installed fails with > ~>telegram-desktop > (telegram-desktop:4205): GLib-GObject-WARNING **: 17:15:44.346: cannot register existing type 'GdkDisplayManager' > (telegram-desktop:4205): GLib-CRITICAL **: 17:15:44.346: g_once_init_leave: assertion 'result != 0' failed > (telegram-desktop:4205): GLib-GObject-CRITICAL **: 17:15:44.346: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed Currently this is resolved by a conflict of telegram-desktop with libqt5-qtstyleplugins-platformtheme-gtk2 which leads to cunfusion of users (bug 1148509) Ideally the root cause should be found and patched. A package without the conflict for testing can be found at https://build.opensuse.org/project/show/home:tux93:tdesktop-no-conflict -- You are receiving this mail because: You are on the CC list for the bug.

2 33

[Bug 1200583] FreeCAD Segfaults Opening Any Example (libc.so.6)
by bugzilla_noreply＠suse.com 10 Jul '22

10 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200583 https://bugzilla.suse.com/show_bug.cgi?id=1200583#c7 --- Comment #7 from Stefan Br�ns <stefan.bruens(a)rwth-aachen.de> --- I said *I* will not support FreeCAD on 15.4. It does build, and the test suite runs successfully. Everything else has to many outside dependencies. Graphics drivers, other installed packages, whatever. You are free to debug it and then send an SR with eventual fixes. Stop demanding, start contributing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0