August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201569] claws-mail dependency prevents upgrade
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201569 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mls(a)suse.com Assignee|screening-team-bugs(a)suse.de |mrueckert(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201989] Building a container image with "podman" leaves empty /etc/resolv.conf behind
by bugzilla_noreply＠suse.com 03 Aug '22

03 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201989 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |mls(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202036] Screen share in Plasma Wayland does not work
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202036 https://bugzilla.suse.com/show_bug.cgi?id=1202036#c4 --- Comment #4 from Daniel Noga <noga.dany(a)gmail.com> --- Created attachment 860555 --> https://bugzilla.suse.com/attachment.cgi?id=860555&action=edit leap logs -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200336] New: Wired network connection is insanely slow (except on speedtest.net)
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200336 Bug ID: 1200336 Summary: Wired network connection is insanely slow (except on speedtest.net) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: php4fan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My ISP provides a 300Mbps internet connection that arrives at my router with a coaxial cable. So, I would expect my connection speed, when connected to the router via a wired Ethernet connection, to be around 300Mbps, and the wifi to be equal or slower. I guess I have 802.11n wifi so I would expect around 100Mbps which is what I get with wifi. The issue is Ethernet connection is way slower... except when I do the test with the browser on https://speedtest.net, where I register the expected 300Mbps with the ethernet connection, proving the hardware or network itself are not at fault. Here's the tests I do and the numbers: 1) When connected only to wired ethernet connection (via an ethernet-USB adapter): - Downloading a big file with wget: about 5mbps - "speedtest-cli --single": about 12 Mbps - speedtest-cli (without --single): about 50Mbps - https://speedtest.net: about 300Mbps 2) When connected only to WiFi: - Downloading a big file with wget (from the SAME SERVER as above): about 101mbps - "speedtest-cli --single": about 80 Mbps - speedtest-cli (without --single): about 110Mbps - https://speedtest.net: about 120Mbps As you can see, wifi behaves more or less as expected. That downloading a single file from a single source, and single-threaded speed test are ever so slightly slower than a parallel speed test is kind of expected, as long as the difference isn't huge. But the results with ethernet connection show something is wrong. It's not the hardware or the physical network link, otherwise there would be no difference between single- and parallel- download tests. It's not the server side either, otherwise the file-download test would be slow on wifi too. It looks like each individual end-to-end connection via the Ethernet link has a limited speed. That might be the reason why "speedtest-cli" is faster than "speedtest-cli --single", because the former opens several parallel connections; maybe speedtest.net opens even more of them and that would explain how it is even faster, reaching the actual available bandwidth. The not-so-big difference (almost a factor of 2) between single file download and "speedtest-cli --single" might be explained by the former not accounting for the http overhead. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1202036] Screen share in Plasma Wayland does not work
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202036 https://bugzilla.suse.com/show_bug.cgi?id=1202036#c3 Daniel Noga <noga.dany(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(noga.dany(a)gmail.c | |om) | --- Comment #3 from Daniel Noga <noga.dany(a)gmail.com> --- Created attachment 860554 --> https://bugzilla.suse.com/attachment.cgi?id=860554&action=edit fedora logs -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202075] VUL-0: chromium: multiple security issues fixed in 104.0.5112.79
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202075 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 1202036] Screen share in Plasma Wayland does not work
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1202036 https://bugzilla.suse.com/show_bug.cgi?id=1202036#c2 --- Comment #2 from Daniel Noga <noga.dany(a)gmail.com> --- I tested it more today and I found, that issue is only on Leap 15.4 and both in Flatpak software and in native packages. I managed to reproduce it reliably in VirtualBox machine. Here is the test cases and results: Leap 15.4, VirtualBox, Plasma 5.24.4 Wayland: distribution's Firefox, opened https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#22754729554439… , does not work oficial Chrome 104, changed chrome://flags WebRTC PipeWire support to Enabled, opened https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing , does not work Fedora 36 Live, VirtualBox, Plasma 5.24.3 Wayland: distribution's Firefox, opened https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#22754729554439… , WORKS oficial Chrome 104, changed chrome://flags WebRTC PipeWire support to Enabled, opened https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing , WORKS Tumbleweed, VirtualBox, Plasma 5.25.3 Wayland: (very hard to test, missing cursor in Wayland session) distribution's Firefox, opened https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#22754729554439… , WORKS oficial Chrome 104, changed chrome://flags WebRTC PipeWire support to Enabled, opened https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing , WORKS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200257] New: Login to this stupid bugzilla is completely broken
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200257 Bug ID: 1200257 Summary: Login to this stupid bugzilla is completely broken Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: php4fan(a)gmail.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Steps to reproduce: 1. Be sure you are not logged in 2. Go to some bug(*), e.g. https://bugzilla.opensuse.org/show_bug.cgi?id=776117 3. Use the embedded login form at the top of the screen to log in: enter your correct username and password and click the submit button. (*) or at step 2 use the "New" link to enter a new bug, which will redirect you to log in. I face the same issue when I do that, although maybe some details may vary. Expected: should log in. Or if there's something wrong, give an error message explaining what's wrong Observed: it shows a new login page with no error message whatsoever. 4. Re-enter the correct username and password Expected: same as after step 3 Observed: keeps showing the same login form page with no error message. For MONTHS I've been having this problem, and every single time I thought I wasn't remembering my password correctly, so first I would try with the email instead of the username (or the other way around if I had tried with the email first), because the prompt says "login" which is ambiguous and you can't know which one you are supposed to use. Then I would try different password that I thought might be the correct one. I would get either the error complaining about incorrect username and/or password or again the login prompt again with no error message, and of course it was seemingly random to me and I didn't know that in one case it's this stupid bug and in the other case I'm actually entering the wrong password or username. So then, every time, I would attempted to do the "Reset password" or "Forgot password" thing, which is also broken in many ways that I don't even want to try and remember, and in the end I ended up creating a new user every time, which is also a f***ing mess (and I reached the point where I had to create a new gmail account each time), and then couldn't log in with the new user anyway, until between clearing cookies and going to the homepage (rather than a specific bug) and through the dedicated "log in" link (as opposed as using the embedded form in any random page) I could finally log in with one user or another. It is only now that I finally figured out (or at least think so) that what makes the difference is to go to the dedicated login page from the link in the home page (and maybe clearing cookies is also needed), and not clearing the cookies, at least not that alone. I am not sure whether or not this has to do with the "restrict this session to this IP address" or not. I would never check that option if it was for me, but it's checked by default so most of the time I forget to uncheck it (or fail to realise it's not a "remember me" checkbox). Either way, this is obviously a bug. If I get logged out because I was already logged in via cookies but I'm connecting from a different IP, that should not prevent me from logging in again, and if it does for any reason, should show some error message and tell me what to do about it. Note that I do NOT use any password manager, nor any of the browser's "remember passwords" features. The only way my username and password get entered from the client side (regardless of when *you* log me in automatically using a cookie) is when I type them with my hands. Not that you would be excused if the issue had to do with the browser remembering passwords (unless it was a bug in the browser) but that is not the case anyway. Everything login-related in this bug tracker is a complete mess. Login, as described here, password reset, signing up. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1201565] [SELinux] libvirt-guests missing SELinux permission on libvirt-guests state file
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201565 https://bugzilla.suse.com/show_bug.cgi?id=1201565#c8 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(virt-bugs(a)suse.de | |) | --- Comment #8 from James Fehlig <jfehlig(a)suse.com> --- I've submitted an updated libvirt package to Factory that removes the redefinition of libexecdir https://build.opensuse.org/request/show/992407 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201679] VUL-0: chromium: multiple security issues fixed in 103.0.5060.134
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201679 http://bugzilla.opensuse.org/show_bug.cgi?id=1201679#c4 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #4 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- done, closing -- You are receiving this mail because: You are on the CC list for the bug.

1 0