May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1223908] proton-vpn App Crashes On Connection, Breaks Network Connectivity
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223908 https://bugzilla.suse.com/show_bug.cgi?id=1223908#c1 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- Not sure what happened, but I got another error on my side. The Proton VPN app was slightly outdated, possibly a clash with newer dependencies in Factory. A package update is on the way, see https://build.opensuse.org/request/show/1175810 and https://build.opensuse.org/request/show/1175826. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222159] AUDIT-0: CVE-2024-5148: gnome-remote-desktop: Polkit and D-Bus review for Gnome 46.0
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222159 https://bugzilla.suse.com/show_bug.cgi?id=1222159#c27 --- Comment #27 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- I checked version 46.2 and the fixes seem okay so far. The remaining issues #5 and #9 don't relate to the D-Bus interface, so whitelisting the D-Bus API is okay now. Issue #9 is rather unfortunate though, since upstream doesn't want to remove the insecure CLI invocation style. Depending upon how this ends up in release 47, we could consider adding a patch in our packaging at least, that warns the user when this insecure invocation style is used. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224341] VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 125.0.6422.60
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224341 https://bugzilla.suse.com/show_bug.cgi?id=1224341#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 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224208] VUL-0: CVE-2024-4671: chromium,ungoogled-chromium: use after free in Visuals
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224208 https://bugzilla.suse.com/show_bug.cgi?id=1224208#c5 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- done -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222342] gdb history seems almost entirely broken
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222342 https://bugzilla.suse.com/show_bug.cgi?id=1222342#c2 --- Comment #2 from Tom de Vries <tdevries(a)suse.com> --- Saving history is a feature I haven't used before, but I've read the docs now to understand what it's supposed to do. I agree with Michael that it looks like at least part of the problems reported in comment 0 can be caused by using the default history file which resides in the current directory. Anyway, I've now enabled it in my .gdbinit, like so: ... $ cat ~/.gdbinit set history filename ~/.gdb_history set history save on ... and I'll test-drive it for a while. I've tried out the use case of opening two gdb sessions at the same time, and the resulting history file looks sane, so at first glance there doesn't seem to any truncating going on there. The reported "the history only has half the commands I used in the previous session" may just be the history size parameter, defaulting to 256 taking effect. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219419] New: system broken after distrobox-export --bin sudo
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219419 Bug ID: 1219419 Summary: system broken after distrobox-export --bin sudo Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Distrobox Assignee: rbrown(a)suse.com Reporter: marco.trauffler(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0 Build Identifier: sudo is not working anymore entering distrobox with --root is not working anymore in both cases command does not return anymore, memory is incrementing, CPU is working heavily system must be rebooted within 2 minutes before memory is full! Reproducible: Didn't try Steps to Reproduce: 1. create a container with distrobox create --name NAME --image IMAGE --root 2. enter the container with distrobox enter NAME --root 3. inside the container run: distrobox-export --bin sudo note: unable to reproduce on my machine because system nearly unusable, hope I do not need to reinstall. Actual Results: I do not know any solution to get sudo working again outside the container I do not know any solution to enter the container with --root anymore note: all not --root containers are still working note: rollback to previous state does not help what to do as my system gets unusable with above problems Expected Results: behaviour expected: use sudo outside of distrobox still beeing able to enter distrobox with --root actual behaviour: sudo outside of distrobox hangs and doesn't return anymore. the CPU usage is high and the memory is incrementing until full. same bahaviour when trying distrobox enter --root -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219306] [TRACKER] Remove python2 from openSUSE:Factory
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219306 Bug 1219306 depends on bug 1219740, which changed state. Bug 1219740 Summary: julia requires python2(EOL) to build https://bugzilla.suse.com/show_bug.cgi?id=1219740 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219740] julia requires python2(EOL) to build
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219740 https://bugzilla.suse.com/show_bug.cgi?id=1219740#c6 Matej Cepl <mcepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |mcepl(a)suse.com Status|IN_PROGRESS |RESOLVED --- Comment #6 from Matej Cepl <mcepl(a)suse.com> --- SR accepted! Yay! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218158] [usr-merge] yast-nfs-(server|client) hardcoded configuration file /etc/idmapd.conf
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1218158 https://bugzilla.suse.com/show_bug.cgi?id=1218158#c18 --- Comment #18 from Fabian Vogt <fvogt(a)suse.com> --- In this particular case, adding basic support for usr-merge as it is planned in TW would just mean adding a "localdomain" fallback for yast-nfs-client and removing the dialog in yast-nfs-server, which is arguably even less work than removing idmapd.conf support. Both options sound fine to me though. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224341] VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 125.0.6422.60
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224341 https://bugzilla.suse.com/show_bug.cgi?id=1224341#c3 --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- openSUSE-SU-2024:0136-1: An update that fixes 5 vulnerabilities is now available. Category: security (critical) Bug References: 1224208,1224294,1224341 CVE References: CVE-2024-4761,CVE-2024-4947,CVE-2024-4948,CVE-2024-4949,CVE-2024-4950 JIRA References: Sources used: openSUSE Backports SLE-15-SP5 (src): chromium-125.0.6422.60-bp155.2.82.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0