August 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1188963] Printer activation in yast for HP printers/scanners requiring plugins is not working
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188963 https://bugzilla.suse.com/show_bug.cgi?id=1188963#c1 Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix(a)suse.com, | |kanderssen(a)suse.com, | |martin.wilck(a)suse.com Flags| |needinfo?(martin.wilck@suse | |.com), | |needinfo?(jsmeix(a)suse.com) --- Comment #1 from Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> --- Could you take a look? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183858] python36-core is requiring python38-core
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1183858 https://bugzilla.suse.com/show_bug.cgi?id=1183858#c7 Matej Cepl <mcepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #7 from Matej Cepl <mcepl(a)suse.com> --- Fixed in python36/Tumbleweed, it is going to be sent to other TW pythons, and it doesn't matter for SLE, where python3-Sphinx is only one package (non-standard python3 packages have only the main interpreter, setuptools and pip, no Sphinx). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188976] VUL-0: CVE-2021-37601: Prosody 0.11.0 through 0.11.9 allows remote attackers to obtain sensitive information (list of admins, members, owners, and banned entities of a Multi-User chat room) in some common configurations.
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188976 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 1188436] Fan running really loud upon loading any type of web content
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188436 https://bugzilla.suse.com/show_bug.cgi?id=1188436#c11 --- Comment #11 from Nenad Latinovi�� <latinovicne(a)gmail.com> --- Thanks :) You're the best :) I'll get on it in the morning and will upload in a day or two the results of the outputs. What do you need, dmesg and lspci only? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188436] Fan running really loud upon loading any type of web content
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188436 https://bugzilla.suse.com/show_bug.cgi?id=1188436#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- Yeah, it is :) I mean, a simple sound playback (e.g. aplay or whatever), and check whether you get some unexpected high load that triggers fan running. If this happens reliably, it is likely related with the hardware and the driver. Or if the simple network load would trigger the fan spinning, we should doubt about the network stack. That is, the basic strategy is divide-and-conquer. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188909] "zypper search --details [PkgName]" show two repos
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188909 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|ma(a)suse.de |zypp-maintainers(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188909] "zypper search --details [PkgName]" show two repos
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188909 https://bugzilla.suse.com/show_bug.cgi?id=1188909#c2 --- Comment #2 from Michael Andres <ma(a)suse.com> --- (In reply to Brian Wengel from comment #0) > Running "zypper search --details [PackageName]" result in two hits of the > exact same package, one for the repo "Main Repository" and one for the repo > "openSUSE-Leap-15.3-1". > It might depend on package, but at least for many packages, e.g. "pv". > > I will claim this behaviour is new, right? No, this is not new. It's just not very common that you have multiple repos with exactly the same content. In the details views you see one entry for every available package. Identical packages in different reopos are not unified in the tables. They may nevertheless have slightly different properties due to e.g. repo priorities or packages locks applied pper repo. Both are tagged with an 'i' if the identical package is installed. In the summary views however we just show one of the repos and not all of them. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186730] New: zypper dup 20210519 => 20210527 (UsrMerge) failed
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1186730 Bug ID: 1186730 Summary: zypper dup 20210519 => 20210527 (UsrMerge) failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: dleuenberger(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Some background: * The machine was originally setup with Tumbleweed in November 2014 * It was regularly (sometimes daily, sometimes weekly) zypper dup'ed The latest snapshot installed was 20210519 Upon a zypper dup to 0527 (UsrMerged/gcc11), the dup failed with: ( 116/3569) Installing: filesystem-15.5-40.2.x86_64 ................................................................................................................................................[error] Installation of filesystem-15.5-40.2.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Make a copy of `/bin'. Merge the copy with `/usr/bin'. Clean up duplicates in `/usr/bin'. Make a copy of `/sbin'. Merge the copy with `/usr/sbin'. Clean up duplicates in `/usr/sbin'. Make a copy of `/lib'. Warning: /lib/udev conflicts with directory /usr/lib/udev and will be removed Merge the copy with `/usr/lib'. Clean up duplicates in `/usr/lib'. Make a copy of `/lib64'. Merge the copy with `/usr/lib64'. Clean up duplicates in `/usr/lib64'. Switch to new `/usr/bin'. Switch to new `/usr/sbin'. Switch to new `/usr/lib'. Switch to new `/usr/lib64'. Create `/bin' symlink. Create `/sbin' symlink. Create `/lib' symlink. Create `/lib64' symlink. Clean up backup files. /usr/bin.usrmerge ... mv: relocation error: /lib64/libc.so.6: symbol _dl_fatal_printf, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference Something failed, cleaning up rm: relocation error: /lib64/libc.so.6: symbol _dl_fatal_printf, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference error: lua script failed: [string "%pretrans(filesystem-15.5-40.2.x86_64)"]:37: exit error: filesystem-15.5-40.2.x86_64: install skipped error: filesystem-15.5-39.1.x86_64: erase skipped At that point, it was only possible to either ignore (sounded bad, as nothing could be started, incl. rpm call outs from zypper), so I opted to 'abort' At that point, the symlink /bin => /usr/bin (and libmlib64,sbin) have been in place. A reboot did, unsurprisingly, not work, as it ended up in a kernel panic (init start failed with the same glibc relocation error) I recovered using a live image, zypper --root /mnt dup the system back to operational. This bug is to collect some information on how this could possibly have happened, ideas how to mitigate it (SLE-Next will presumably be UsrMerge,so the issue is not just a one-off on TW) -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1188436] Fan running really loud upon loading any type of web content
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188436 https://bugzilla.suse.com/show_bug.cgi?id=1188436#c9 --- Comment #9 from Nenad Latinovi�� <latinovicne(a)gmail.com> --- (In reply to Takashi Iwai from comment #8) > Debugging a performance of the browser application is a very tough thing, as > it's really a complex monster... So if you can reproduce a similar problem > with some more simpler application, it'd be helpful. e.g. whether such a > problem is seen with some audio playback application or video, or whatever. > > Then the next step would be profiling, e.g. via perf program. But, again, a > simpler program can be better spotted. Hi again, Thanks. Would Spotify app do (Flatpak) or is that also too complex? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188436] Fan running really loud upon loading any type of web content
by bugzilla_noreply＠suse.com 02 Aug '21

02 Aug '21

https://bugzilla.suse.com/show_bug.cgi?id=1188436 https://bugzilla.suse.com/show_bug.cgi?id=1188436#c8 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Debugging a performance of the browser application is a very tough thing, as it's really a complex monster... So if you can reproduce a similar problem with some more simpler application, it'd be helpful. e.g. whether such a problem is seen with some audio playback application or video, or whatever. Then the next step would be profiling, e.g. via perf program. But, again, a simpler program can be better spotted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0