May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1223352] X11 sessions do not unlock after locking for inactivity
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223352 https://bugzilla.suse.com/show_bug.cgi?id=1223352#c4 --- Comment #4 from epp(a)mcom.com --- Created attachment 875006 --> https://bugzilla.suse.com/attachment.cgi?id=875006&action=edit Photo of display with X11 session not unlocking after inactivity -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223352] X11 sessions do not unlock after locking for inactivity
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223352 https://bugzilla.suse.com/show_bug.cgi?id=1223352#c3 --- Comment #3 from epp(a)mcom.com --- (In reply to Stefan Dirsch from comment #2) > Could this please retested with current TW, please? TW 20240520: Yes, still occurs. Attaching photo of display. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222346] snapperd can't work
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222346 https://bugzilla.suse.com/show_bug.cgi?id=1222346#c6 --- Comment #6 from Wenruo Qu <wqu(a)suse.com> --- I'm wondering if snapper is not handling rescan correctly. Yes, qgroup is very heavy, but that's so far the only way to get accurate accounting numbers, considering how many tricks we put to get super fast snapshotting. All the super fast snapshotting has put a lot of complexity to qgroups. Not to mention the extra complexity from multi-level qgroups, utilized by snapper. But for the RESCAN_WAIT returns immeidately problem, I think it's something from the snapper side. Snapper should check if qgroup is even enabled and rescan is running. Or RESCAN_WAIT ioctl immediately return 0 if qgroup rescan is not running nor qgroup is enabled. Any clue how snapper triggers qgroup rescan? Did it check if qgroup is enabled or handles qgroup rescan return value correctly? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224822] New: error in permctl manpage
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224822 Bug ID: 1224822 Summary: error in permctl manpage Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My brand-new permctl manpage says (re-formatted for readability) EXAMPLES permctl --set /usr/share/permissions/permissions /usr/share/permissions/permissions.secure Parses the files /usr/share/permissions/permissions and /usr/share/permissions/permissions and sets ... The "Parses the files ..." line mentions the same filename twice. The second filename should be the *.secure file. While on it: permctl --system /bin/ping Run in system mode and only correct permissions of /bin/ping. You might want to UsrMerge that example to /usr/bin/ping ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224819] Please update Kicad to version 8.0
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224819 https://bugzilla.suse.com/show_bug.cgi?id=1224819#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |stefan.bruens(a)rwth-aachen.d | |e CC| |Andreas.Stieger(a)gmx.de --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- > 15.6: unresolvable: nothing provides wxGTK3-devel >= 3.2.4, > (got version 3.1.5-150400.3.7.1 provided by wxGTK3-3_2-devel) It does not look like this is deliverable for Leap 15.6. openSUSE Tumbleweed ships 8. Assigning to Stefan for commenting and/or closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195615] Please upgrade KiCad to 6.0.1 or later
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1195615 https://bugzilla.suse.com/show_bug.cgi?id=1195615#c2 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED CC| |Andreas.Stieger(a)gmx.de --- Comment #2 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- 15.5 has 6.0.11, closing -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216969] New: Recent Applications and Recent Files are no longer updated
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1216969 Bug ID: 1216969 Summary: Recent Applications and Recent Files are no longer updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent Applications and Recent Files are no longer updated in KDE's Application menu. The links are existing in .local/share/RecentDocuments, though. Didn't find any directory for Recent Apps. Operating System: openSUSE Tumbleweed 20231106 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1224820] New: Crash after resuming from suspend with Threadripper Pro/WRX90 chipset
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224820 Bug ID: 1224820 Summary: Crash after resuming from suspend with Threadripper Pro/WRX90 chipset Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I recently assembled a computer based on the ASUS WRX90E Sage motherboard and a 32-core AMD Threadripper PRO CPU. In the BIOS, I enabled 64-bit PCIe remapping support to allow the OS to remap devices to 64-bit address space. For some odd reason, however, the system went into standby and could not recover. Pressing Control+Alt+F10 reported problems remapping the PCIe devices, and then there was a failure with BTRFS reading bad data, and the system hung. The NVME drive is an old Intel PCIe card I had lying around that only had light usage. I strongly suspect there are compatibility issues with the new motherboard chipset since it is pretty new. The WRX90 chipset is only used in two motherboards I am aware of, the ASUS board and an ASRock board. I could not capture the messages directly since the FS went read-only and it started spewing a ton of BTRFS errors before I could capture the screen. As for why it went into suspend mode to begin with, I have no idea. The reason I know it did is I sshed into the box remotely and got a broadcast message: Broadcast message from aaronw@localhost (Tue 2024-05-21 14:09:53 PDT): The system will suspend now! I will try disabling S4/S5 support in the BIOS and see if that helps and I can also try disabling the 64-bit PCIe remapping as well. System specs: ASUS Pro WRX90E Sage SE EEB motherboard with latest BIOS firmware AMD Threadripper Pro 7975WX CPU Gigabyte Ge-Force RTX4090 Windforce V2 24G graphics card Intel NVME drive Kingston Fury Renegade Pro 128GB ECC Registered DDR5 (PC5 48000) memory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224819] New: Please update Kicad to version 8.0
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224819 Bug ID: 1224819 Summary: Please update Kicad to version 8.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The included Kicad is stuck at version 6 where it is now at version 8. The version included in the engineering repository is broken (and stuck somewhere between 6 and 7. Note that Kicad 8 requires Python > 3.6, i.e. Python 3.11, with wxWidget and wxPython support for Python 3.11. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224818] VUL-0: chromium: multiple vulnerabilities fixed in 125.0.6422.76
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224818 Maintenance Automation <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