June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1183192] osc forces you to use vim
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1183192 https://bugzilla.suse.com/show_bug.cgi?id=1183192#c3 Daniel Mach <daniel.mach(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Daniel Mach <daniel.mach(a)suse.com> --- osc defaults to 'editor' on Debian for some time already: https://github.com/openSUSE/osc/blob/master/osc/core.py#L1922 Let me close this bug, but if you still experience any issues, reopen it or ideally create an upstream issue on github. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225808] windows:mingw:win64/mingw64-openssl: No sources included in debug package
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225808 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fstrba(a)suse.com |ralf.habacker(a)freenet.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225837] New: bluetooth obex does not respect the active user sessions and always transfers files only in the first tty active session (first user session on the system to be opened at boot)
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225837 Bug ID: 1225837 Summary: bluetooth obex does not respect the active user sessions and always transfers files only in the first tty active session (first user session on the system to be opened at boot) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This is a curious thing in deed: open one user A (with BT support) in plasma open another user B (with BT support in plasma. User A is bound to tty2 User B is bound to tty3 (or if you do some error it shifts to tty7 as the new behavior is like this if you use alt+cntrl+Fn to shift to another tty (and forget that it is not yet open). Long story short, go to the second user session. It will connect problem free to the BT phone or whatever you wish to do a file transfer. Start the sending of the file on the e.g. Android phone. It will fail silently. Now shift with alt+cntr+Fn to the first(!) opened user session. Now the transfer if it is still active on the phone will suddenly start, transferring the file to the wrong user session. I also tried the following to avoid this: switch off BT in the first user (A)session, switch to the second user session (B), switch there BT on, try to transfer the file, fails silently, then go back to the first user session. BT will be active as expected and here it will receive immediately the files. Hence this is a focus stealing issue. And when you look at dmesg it complains of anything and lists only: [17822.836978] [ T1445] input: Pan Galactic Gargle Blaster (AVRCP) as /devices/virtual/input/input31 [17862.458018] [ T1445] input: Pan Galactic Gargle Blaster (AVRCP) as /devices/virtual/input/input32 [17910.817347] [ T1445] input: Pan Galactic Gargle Blaster (AVRCP) as /devices/virtual/input/input33 [18020.812264] [ T1445] input: Pan Galactic Gargle Blaster (AVRCP) as /devices/virtual/input/input34 where Pan Galactic Gargle Blaster is the name of the phone (Poco X3 Pro). In journalctl you find the following (very few) lines: giu 03 14:21:00 silversurfer bluetoothd[1445]: src/profile.c:ext_io_disconnected() Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107) giu 03 14:21:00 silversurfer obexd[2731]: disconnected: Transport got disconnected giu 03 14:21:00 silversurfer obexd[2731]: DISCONNECT(0x1), Success(0x20) giu 03 14:21:00 silversurfer obexd[2731]: DISCONNECT(0x1), <unknown>(0xff) giu 03 14:20:55 silversurfer bluetoothd[1445]: /org/bluez/hci0/dev_8C_D9_D6_3B_1E_4F/fd3: fd(42) ready giu 03 14:20:55 silversurfer systemd-logind[1504]: Watching system buttons on /dev/input/event26 (Pan Galactic Gargle Blaster (AVRCP)) before there is only one line that speaks about a problem: giu 03 14:19:33 silversurfer wireplumber[6733]: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.bluez.Error.AlreadyExists: Already Exists (end of excerpt from journal). You find this combination of errors for all aborted transfers. What the software does: getting an incoming file from a BT sender, the active session should be the receiver, and NOT the first tty user session that was opened that day. What the software does: aborts transfers to the user session if it is not the first in chronological line of log in (first active tty for GUI). Software involved Bluez, bluetoothd and obex -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201049] Make MicroOS GNOME Desktop RC/Released
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1201049 Derek Walker <derek(a)dwredshoes.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |derek(a)dwredshoes.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225526] Tumbleweed KDE install does not include terminus-bitmap fonts or set /etc/vconsole.conf properly on hiDPI systems
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225526 https://bugzilla.suse.com/show_bug.cgi?id=1225526#c8 --- Comment #8 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Franck Bui from comment #7) > I'm not aware of any logic implemented in systemd, the font default is > configured via /etc/vconsole.conf, which in its turn is created by the > installer (I suppose). > > It seems that the logic implemented by the installer needs to be extended to > deal with high resolution monitors. Arguably that needs to be a runtime decision (as done by the kernel apparently), to support monitor and resolution changes. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225522] New: sharing a folder in nautilus gives a usershare failed error
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225522 Bug ID: 1225522 Summary: sharing a folder in nautilus gives a usershare failed error Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: hotel-brot.0z(a)icloud.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: sharing a folder in nautilus gives a usershare failed error: Called "net usershare info" but it failed: »net usershare« returned error 255: net usershare: usershares are currently disabled Reproducible: Always Steps to Reproduce: 1.create any folder for testing 2.right click on folder in nautilus -> Sharing Options -> Share this folder -> Create Share Actual Results: Called "net usershare info" but it failed: »net usershare« returned error 255: net usershare: usershares are currently disabled Expected Results: successful sharing of a folder journalctl does not show more than the same error given above -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1208369] New "lo" connection
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1208369 https://bugzilla.suse.com/show_bug.cgi?id=1208369#c12 Cosmin Tanczel <cosmin.tanczel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED --- Comment #12 from Cosmin Tanczel <cosmin.tanczel(a)gmail.com> --- I mean it also shouldn't be viewable in the network manager list. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208369] New "lo" connection
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1208369 https://bugzilla.suse.com/show_bug.cgi?id=1208369#c11 --- Comment #11 from Cosmin Tanczel <cosmin.tanczel(a)gmail.com> --- Created attachment 875271 --> https://bugzilla.suse.com/attachment.cgi?id=875271&action=edit Tumbleweed VERSION_ID="20240524" No, it is not solved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225825] New: Migrated systems do not apply language to it's full extend
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225825 Bug ID: 1225825 Summary: Migrated systems do not apply language to it's full extend Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hey there, I just found that systems migrated from RC 1 to RC 2 do not apply the preferred user language to it's full extend. 1) In gnome-settings everything is set to be the default, English. It seems the preferred language from the former home of the user seems not to be carried over properly 2) Since /usr/bin/aeon-firstboot is not executed either, additional packages for more locales are missing as well. This can be fixed manually as the user can change the language any time and then manually execute aeon-firstboot. Might be a wont fix, as there are probably not too many users migrating from RC 1 to RC 2. But I guess it's up to you to decide. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225690] New: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 125.0.6422.141
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225690 Bug ID: 1225690 Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 125.0.6422.141 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: andrea.mattiazzo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The Stable channel has been updated to 125.0.6422.141/.142 for Windows, Mac and 125.0.6422.141 for Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log. Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes 11 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. - CVE-2024-5493: Heap buffer overflow in WebRTC. - CVE-2024-5494: Use after free in Dawn. - CVE-2024-5495: Use after free in Dawn. - CVE-2024-5496: Use after free in Media Session. - CVE-2024-5497: Out of bounds memory access in Keyboard Inputs. - CVE-2024-5498: Use after free in Presentation API. - CVE-2024-5499: Out of bounds write in Streams API. As usual, our ongoing internal security work was responsible for a wide range of fixes: [343518382] Various fixes from internal audits, fuzzing and other initiatives Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL. [0] https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-des… -- You are receiving this mail because: You are on the CC list for the bug.

1 5