December 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1193334] multipathd: double free in remove_map()
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193334 http://bugzilla.opensuse.org/show_bug.cgi?id=1193334#c2 --- Comment #2 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1193334) was mentioned in https://build.opensuse.org/request/show/935254 Factory / multipath-tools -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192579] Wayland session won't start
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1192579 https://bugzilla.suse.com/show_bug.cgi?id=1192579#c9 --- Comment #9 from Peter Krause <pewkrause(a)gmx.de> --- (In reply to Fabian Vogt from comment #8) > > //home/peter/.bashrc: Zeile 14: /opt/fish/bin/fish: Datei oder Verzeichnis nicht gefunden > > While it seems to continue past this, it looks highly suspicious. > > Are you using fish as login shell? I use fish as a general bash replacement, so, when i tried to lauch the Wayland session via the terminal I logged in using the fish shell. I opened the terminal using ALT+F3 from inside a running x.org session. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192457] New: ZSTD compressed kernel module files are 35% bigger
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192457 Bug ID: 1192457 Summary: ZSTD compressed kernel module files are 35% bigger Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: schwab(a)linux-m68k.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # du -sh /lib/modules/*/kernel/ 91M /lib/modules/5.13.13-1-default/kernel/ 92M /lib/modules/5.14.14-1-default/kernel/ 125M /lib/modules/5.15.1-1.g0a42f4c-default/kernel/ # rpm -q --qf="%{NAME}-%{VERSION}: %{SIZE}\n" kernel-default kernel-default-5.13.13: 170499562 kernel-default-5.14.14: 171909997 kernel-default-5.15.1: 207900779 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1192328] New: copy files form exFAT with --preserve=timestamps
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192328 Bug ID: 1192328 Summary: copy files form exFAT with --preserve=timestamps 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: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: wilms(a)pre-sense.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853522 --> http://bugzilla.opensuse.org/attachment.cgi?id=853522&action=edit 5M exFAT partition for reproducing the error When mounting an exFAT partition in read-only mode: mount -o ro /path/to/partition /mountpoint and then trying to copy a file with: cp --preserve=timestamps /path/to/file/on/exfat /path/to/target/file then cp shows the following error: cp: preserving times for '/path/to/target/file': Invalid argument The file is copied but the timestamp is set to the current system time instead of the correct timestamp. This error occurs in a openSUSE Leap 15.3 Installation and also in the openSUSE Leap 15.3 LiveCD version. This error _does not_ occur when using Tumbleweed, which uses the native kernel implementation of exFAT due to having a more recent kernel afaik. Attached a qemu img with a 5M exFAT partition and a testfile easily reproduce the error. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1193335] New: HP plugin download and install errors: wrong checksum, Python3 vs Python2 problem
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1193335 Bug ID: 1193335 Summary: HP plugin download and install errors: wrong checksum, Python3 vs Python2 problem Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: jsmeix(a)suse.com Found By: --- Blocker: --- My printer needs HP plugin for HPLIP. In openSUSE Leap 15.3 I have installed HPLIP 3.20.11. When I try to print, GUI dialog appeared to install missing plugin. I went throw wizard and selected to download it. But when I try to download/install it, I get the following error: .hplip/hplip-3.20.11-plugin.run file does not match its checksum. File may have been corrupted or altered Later I manually managed to download it from https://developers.hp.com/sites/default/files/hplip-3.20.11-plugin.run Executing it failed: > sudo sh hplip-3.20.11-plugin.run Verifying archive integrity... All good. Uncompressing HPLIP 3.20.11 Plugin Self Extracting Archive.............................................................. Error importing HPLIP modules. Is HPLIP installed? Only later I found this error because of python2 usage instead of python3 for execution of plugin_install.py via hplip-plugin-install. Thus workaround was: wget https://developers.hp.com/sites/default/files/hplip-3.20.11-plugin.run sh ./hplip-3.20.11-plugin.run --nox11 --target mydir cd mydir sudo python3 ./plugin_install.py -i -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193124] tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193124 https://bugzilla.suse.com/show_bug.cgi?id=1193124#c42 --- Comment #42 from Takashi Iwai <tiwai(a)suse.com> --- Created attachment 854255 --> https://bugzilla.suse.com/attachment.cgi?id=854255&action=edit Fix patch -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193124] tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193124 https://bugzilla.suse.com/show_bug.cgi?id=1193124#c41 --- Comment #41 from Takashi Iwai <tiwai(a)suse.com> --- Good to hear. I'm going to submit the fix patch to upstream and merge to openSUSE kernels. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190740] TLS reference in /usr/lib64/libLLVM.so mismatches non-TLS reference in /usr/lib64/libLLVM.so when linking to LLVM on s390x
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190740 Reinhard Max <max(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ihno(a)suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193333] VUL-0: CVE-2021-4041: ansible-runner: Improper shell escaping
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1193333 Maintenance Robot <maint-coord+maintenance_robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190740] TLS reference in /usr/lib64/libLLVM.so mismatches non-TLS reference in /usr/lib64/libLLVM.so when linking to LLVM on s390x
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190740 http://bugzilla.opensuse.org/show_bug.cgi?id=1190740#c29 Reinhard Max <max(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(ihno(a)suse.com) --- Comment #29 from Reinhard Max <max(a)suse.com> --- Let's first check if there is an actual difference in behavior between OBS and IBS workers. I think so far we only know that PostgreSQL fails with llvm13 on Factory in OBS and succeeds with llvm11 on SLE-15 in IBS, so the difference that matters might be llvm13 vs. llvm12 or Factory vs. SLE-15 rather than OBS vs. IBS. I've set up a branch of postgresql14 in IBS to check this, but Factory seems to be in a major rebuild there right now, so it might take overnight until I get a result. -- You are receiving this mail because: You are on the CC list for the bug.

1 0