May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1223444] New virt-v2v dependency on btrfsprogs causes error with zypper dup on systems without btrfs installed
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223444 https://bugzilla.suse.com/show_bug.cgi?id=1223444#c2 --- Comment #2 from Rodney Baker <rodney.baker(a)iinet.net.au> --- There is no "requires" for e2fsprogs, ntfsprogs or any other similar file system packages - surely the same applies to them if trying to convert an image that uses ext[2,3,4] or ntfs? Why should btrfsprogs be any different? "Recommends" seems to make more sense here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215323] New: [trackerbug] docker 24.0.6-ce update
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1215323 Bug ID: 1215323 Summary: [trackerbug] docker 24.0.6-ce update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- - Update to Docker 24.0.6-ce. See upstream changelong online at <https://docs.docker.com/engine/release-notes/24.0/#2406>. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213500] New: [trackerbug] docker 24.0.4-ce update
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213500 Bug ID: 1213500 Summary: [trackerbug] docker 24.0.4-ce update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- - Update to Docker 24.0.4-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/24.0/#2404>. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1223572] virt-manager: Mouse remains hidden after guest stops
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223572 https://bugzilla.suse.com/show_bug.cgi?id=1223572#c4 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs(a)suse.de |carnold(a)suse.com --- Comment #4 from Charles Arnold <carnold(a)suse.com> --- Are you seeing this directly on the console or via ssh (or both)? Are you running the VM in full screen mode? My testing is being done with Tumbleweed release 20240430, both host and guest. I have not yet hit the problem but I'm working over ssh. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223444] New virt-v2v dependency on btrfsprogs causes error with zypper dup on systems without btrfs installed
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223444 https://bugzilla.suse.com/show_bug.cgi?id=1223444#c1 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs(a)suse.de |carnold(a)suse.com --- Comment #1 from Charles Arnold <carnold(a)suse.com> --- (In reply to Rodney Baker from comment #0) > A new dependency on btrfsprogs has been added to virt-v2v on 18/04/2024. > This causes an error when doing a zypper dup on TW systems not using btrfs. > I do not use and have no intention of using btrfs - it is really necessary > for this to be a hard dependency rather than a "recommend"? It is less about what your host uses but rather what the guest VMs use that you are trying to convert. If you are trying to convert a Xen VM to KVM that uses btrfs which is the default for Leap and SLE products, then you need btrfsprogs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223617] New: systemd-tmpfiles-setup finds configuration in /etc/tmpfiles.d as duplicate instead of overridding base config
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223617 Bug ID: 1223617 Summary: systemd-tmpfiles-setup finds configuration in /etc/tmpfiles.d as duplicate instead of overridding base config Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ethan.bonick(a)ibm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Systemd is not overwriting but marking as duplicate and ignores desired changes in configuration files. This is also seen on SUSE 15.SP5 as both are using the same version of systemd. foobar:~ # rpm -qa |grep systemd systemd-lang-249.17-150400.8.40.1.noarch systemd-presets-common-SUSE-15-150500.20.6.1.noarch systemd-default-settings-branding-openSUSE-0.10-150300.3.7.1.noarch python3-systemd-234-5.3.5.x86_64 systemd-default-settings-0.10-150300.3.7.1.noarch systemd-249.17-150400.8.40.1.x86_64 systemd-sysvinit-249.17-150400.8.40.1.x86_64 systemd-rpm-macros-15-150000.7.39.1.noarch libsystemd0-249.17-150400.8.40.1.x86_64 util-linux-systemd-2.37.4-150500.9.6.1.x86_64 systemd-presets-branding-openSUSE-12.2-lp155.4.5.noarch systemd-network-249.17-150400.8.40.1.x86_64 grub2-systemd-sleep-plugin-2.06-150500.29.25.12.noarch systemd-doc-249.17-150400.8.40.1.x86_64 foobar:~ # uname -r 5.14.21-150500.55.59-default ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static) Active: active (exited) since Wed 2024-05-01 13:10:13 CDT; 59min ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 795 ExecStart=systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=0/SUCCESS) Main PID: 795 (code=exited, status=0/SUCCESS) May 01 13:10:13 foobar systemd[1]: Starting Create Volatile Files and Directories... May 01 13:10:13 foobar systemd-tmpfiles[795]: /usr/lib/tmpfiles.d/systemd-resolve.conf:10: Duplicate line for path "/etc/resolv.conf", ignoring. May 01 13:10:13 foobar systemd-tmpfiles[795]: /etc/tmpfiles.d/var.conf:14: Duplicate line for path "/var/log", ignoring. May 01 13:10:13 foobar systemd-tmpfiles[795]: /etc/tmpfiles.d/var.conf:15: Duplicate line for path "/var/log/wtmp", ignoring. May 01 13:10:13 foobar systemd-tmpfiles[795]: /etc/tmpfiles.d/var.conf:16: Duplicate line for path "/var/log/btmp", ignoring. May 01 13:10:13 foobar systemd-tmpfiles[795]: /etc/tmpfiles.d/var.conf:17: Duplicate line for path "/var/log/lastlog", ignoring. May 01 13:10:13 foobar systemd-tmpfiles[795]: /etc/tmpfiles.d/var.conf:19: Duplicate line for path "/var/cache", ignoring. May 01 13:10:13 foobar systemd-tmpfiles[795]: /etc/tmpfiles.d/var.conf:21: Duplicate line for path "/var/lib", ignoring. May 01 13:10:13 foobar systemd-tmpfiles[795]: /etc/tmpfiles.d/var.conf:23: Duplicate line for path "/var/spool", ignoring. May 01 13:10:13 foobar systemd[1]: Finished Create Volatile Files and Directories. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223607] New: Gleam Language Package Stalled on Devel Project Maintainer Review
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223607 Bug ID: 1223607 Summary: Gleam Language Package Stalled on Devel Project Maintainer Review Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: pirateclip(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My SR to submit the gleam programming language has not been review or commented on by a single devel project maintainer in devel:languages:misc even though the original SR was submitted 22 days ago: https://build.opensuse.org/request/show/1166294 and the staging bot has pinged all 11 maintainers on three separate instances. I would appreciate if there can be a prompt feedback from one of the maintainers soon. Here is the current SR: https://build.opensuse.org/request/show/1170637 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1223610] New: Require kio-gdrive with KOrganizer
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223610 Bug ID: 1223610 Summary: Require kio-gdrive with KOrganizer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: me(a)cubiclenate.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The Google Groupware module of Korganizer cannot remember the credentials and is unable to stay updated after a restart of Kontact / KOrganizer. The fix for this is to install the kio-gdrive package to ensure that this functions properly. Since the Google Groupware is part of KOrganizer by default, I am recommending that kio-gdrive is required as part of the collection of packages installed with korganizer. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223613] New: irqbalance: Cannot change IRQ 180 affinity: Read-only file system
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223613 Bug ID: 1223613 Summary: irqbalance: Cannot change IRQ 180 affinity: Read-only file system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: munix9(a)googlemail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Get this with version 1.9.4.0.git+f8b8cdd-1.1 $ systemctl status irqbalance ● irqbalance.service - irqbalance daemon Loaded: loaded (/usr/lib/systemd/system/irqbalance.service; enabled; preset: enabled) Active: active (running) since Wed 2024-05-01 09:32:25 CEST; 8h ago Docs: man:irqbalance(1) https://github.com/Irqbalance/irqbalance Main PID: 1324 (irqbalance) Tasks: 2 (limit: 4915) CPU: 4.343s CGroup: /system.slice/irqbalance.service └─1324 /usr/sbin/irqbalance ‐‐journal May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 180 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 180 affinity is now unmanaged May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 181 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 181 affinity is now unmanaged May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 120 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 120 affinity is now unmanaged May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 121 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 121 affinity is now unmanaged May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 213 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 213 affinity is now unmanaged Solved this with a patch from fedora: https://src.fedoraproject.org/rpms/irqbalance/blob/main/f/0001-Drop-Protect… See also https://build.opensuse.org/package/show/home:munix9:test/irqbalance https://bugzilla.redhat.com/show_bug.cgi?id=2276314 https://src.fedoraproject.org/rpms/irqbalance/tree/main Maybe the patch https://src.fedoraproject.org/rpms/irqbalance/blob/main/f/0001-irqbalance-u… is also interesting. If desired, I can create a SR. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

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

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219740 https://bugzilla.suse.com/show_bug.cgi?id=1219740#c4 --- Comment #4 from Soc Virnyl Estela <uncomfy+openbuildservice(a)uncomfyhalomacro.pl> --- Still a few bunch of "workarounds" for offline builds. Still failing but it is getting there. I wonder what's the ETA for removing python? I won't mind deleting julia from Factory for the time being. The devel project already uses Python3 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223443] New: OpenSUSE Aeon (in its current RC from) doesn't ship Mesa Vulkan drivers out of the box
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223443 Bug ID: 1223443 Summary: OpenSUSE Aeon (in its current RC from) doesn't ship Mesa Vulkan drivers out of the box Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: ultragreensaliterium(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Mobile Safari/537.36 Build Identifier: OpenSUSE Aeon (in its final form) should ship Mesa Vulkan drivers OOTB, at least "libvulkan_intel" and "libvulkan_radeon". GTK 4 now has a new Vulkan renderer that will most likely be enabled by default in a future version. With the Mesa Vulkan drivers installed, the system Gnome apps on Aeon that are built with GTK 4 + Libadwaita (for example, Nautilus and Gnome Software), will use the Vulkan renderer instead of the GL renderer. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1175678] complete packages --unneeded featureset (mostly "apt-mark auto")
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1175678 https://bugzilla.suse.com/show_bug.cgi?id=1175678#c12 --- Comment #12 from Moritz Duge <duge(a)pre-sense.de> --- The patches mentioned in the automatic comment 4 and comment 7 add new options. Thanks for that! Unfortunately zypper is still missing an "apt-mark auto" equivalent (workaround below). https://github.com/openSUSE/zypper/commit/de255f3cfff42c3a3d147d2280f9887bb… > - packages: Add --autoinstalled and --userinstalled options to > list them. zypper-1.14.71 Patches for openSUSE 15.3, 15.4 and 15.5. Tumbleweed since Snapshot20240429 NEW: # apt-mark showauto zypper packages --autoinstalled # old workaround: zypper search '' | grep -E '^i ' # ("zypper search" and "zypper packages" work too) # apt-mark showmanual zypper packages --userinstalled # old workaround: zypper search '' | grep -E '^i\+' STILL MISSING: # A counterpart to this command is still missing: # (marks as automatically installed) apt-mark auto PACKAGE # Workaround: # Add the package name to the text file /var/lib/zypp/AutoInstalled EXISTING: zypper remove --clean-deps PACKAGE zypper packages --unneeded # apt-mark manual PACKAGE zypper install --force PACKAGE # similar to "apt autoremove" and "apt autopurge" zypper packages --unneeded zypper remove --clean-deps PACKAGE # Workaround from Hans in comment 1 # zypper rm -u $(zypper pa --unneeded | grep 'i |' | cut -d'|' -f3 | tr -d ' ' | uniq | tr '\n' ' ') SEE ALSO: https://build.opensuse.org/projects/openSUSE:Leap:15.5:Update/packages/zypp… https://github.com/openSUSE/zypper/commit/aeec0c91191629af992cf6197ca43f69c… https://github.com/openSUSE/zypper/blob/aeec0c91191629af992cf6197ca43f69c7e… BY THE WAY: I didn't know that one yet :-) zypper install-new-recommends -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217350] New: Some Electron-based applications are unable to detect dark mode
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217350 Bug ID: 1217350 Summary: Some Electron-based applications are unable to detect dark mode Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870861 --> https://bugzilla.suse.com/attachment.cgi?id=870861&action=edit Visual Studio Code, though preconfigured by default with a dark theme, has a light titlebar, suggesting that Electron detects a light theme in the system. Some Electron-based applications are unable to detect that the system is running with a dark theme, despite dark mode being the default configuration for openSUSE Aeon. This can lead to a lack of UI consistency. I noticed this primarily in apps like Visual Studio Code and Signal. It's worth pointing out that this doesn't occur on every Electron app (namely, the Webcord Flatpak is able to handle theming just fine). I'll also point out that this isn't necessarily an issue with the apps alone or GNOME, because the aforementioned apps--whether packaged as a Flatpak, tarball, or run within a distrobox--do correctly use a dark theme on Ubuntu 23.10. I'm not an expert on SELinux, but it is my best guess as to why this is happening. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212071] Aeon: Fingerprint reader not supported out of the box
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1212071 https://bugzilla.suse.com/show_bug.cgi?id=1212071#c5 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Richard Brown <rbrown(a)suse.com> --- addressed in patterns-aeon -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208869] MicroOS - Urdu Lanuage (Pakistan) Keyboard,Formats, Language and Region Support, Arabic Keyboard (Pakistan) layout support
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1208869 https://bugzilla.suse.com/show_bug.cgi?id=1208869#c3 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(abuturaaab+opensu | |se(a)proton.me) CC| |abuturaaab+opensuse@proton. | |me --- Comment #3 from Richard Brown <rbrown(a)suse.com> --- Is the suggested workaround acceptable for the reporter? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208869] MicroOS - Urdu Lanuage (Pakistan) Keyboard,Formats, Language and Region Support, Arabic Keyboard (Pakistan) layout support
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1208869 https://bugzilla.suse.com/show_bug.cgi?id=1208869#c2 --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- I think the best way of addressing this would be to have users run the following on their Aeon machine `transactional-update run zypper aloc $LOCALE` where Urdu (Pakistan) would be ur_PK If we added every languages required locale info, font packages, and language supporting binaries we'd easily be doubling the size of the image, if not more -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223305] New: [Regression] Bluetooth audio devices reset/disconnected/audio profile changed(??) when wine/proton applications initialize sound
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223305 Bug ID: 1223305 Summary: [Regression] Bluetooth audio devices reset/disconnected/audio profile changed(??) when wine/proton applications initialize sound Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: el(a)horse64.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'm sadly having what seems to be a regression possibly related to Plasma 5 to 6. Now often when wine or proton applications initialize audio , e.g. when I startup EA App inside Steam at launch, or something like REAPER's windows version ( https://reaper.fm/ the trial is free and unrestricted) at any time I press "play", the following happens: 1. Audio drops out completely for a split second. 2. A visible notification is shown like my bluetooth device just freshly connected 3. Audio profile is degraded to something horrible, it sounds like the worst quality headset telephony codec. 4. Sometimes a second later it resets back to what bluetooth profile I had before, usually high-quality playback only "AAC". But sometimes it also just doesn't. This can be checked in plasma's audio device panel, where it will show the telephony codec "Headset Unit ... mSBC" profile in case it didn't reset properly. This also happens when another application is already playing audio in parallel, which sadly makes this disruptive. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1179536] URL of "crash" package needs updating
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1179536 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Minor -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon(SI and CIK): After an upgrade the graphical interface no longer works (Regression with Mesa 24.0x)
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c76 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #76 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. So we see confirmations for Southern and Sea Islands this regression has been fixed with latest Mesa 24.0.5. So closing as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon(SI and CIK): After an upgrade the graphical interface no longer works (Regression with Mesa 24.0x)
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c75 --- Comment #75 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Sebastian Kuhne from comment #72) > So, now the kernel loads the radeon module by default. > I have two questions where I would appreciate your feedback. > - Since I had never investigated in that before, is this the desired > behavior, such as for new installations? Yes, that's correct behaviour for Southern/Sea Islands GPUs. Previously I claimed it to be different, but I was proven wrong. Sorry for the confusion! > - Shouldn't I/we/all rather stay with amdgpu (by considering the information > on 'https://wiki.archlinux.org/title/AMDGPU'? I don't think we should change upstream behaviour here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon(SI and CIK): After an upgrade the graphical interface no longer works (Regression with Mesa 24.0x)
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c74 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #74 from Stefan Dirsch <sndirsch(a)suse.com> --- I've updated Mesa from 24.0.3 to 24.0.5 in TW. I guess this has fixed the issue, when it's no longer needed to force usage of amdgpu kernel driver. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223548] Renoir/Cezanne Crashing on 3D Game/Project Usage Randomly but Frequently - NOT PRESENT ON OTHER OS
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223548 https://bugzilla.suse.com/show_bug.cgi?id=1223548#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |padreadamo(a)gmail.com Flags| |needinfo?(padreadamo@gmail. | |com) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- OK, a test kernel based on 6.8.8 with a potential crash fix patch for Tumbleweed is being built in OBS home:tiwai:bsc1223548 repo. Once after the build finishes (takes an hour or so), it'll appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1223548/standard/ Please give it a try later. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon(SI and CIK): After an upgrade the graphical interface no longer works (Regression with Mesa 24.0x)
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c72 --- Comment #72 from Sebastian Kuhne <sebastian.kuhne(a)mailbox.org> --- Many thanks for the hint. I have removed the kernel parameters radeon.cik_support=0 amdgpu.cik_support=1. I can confirm that this setup is working for me, too. It works on both, X11 and Wayland. I have compared the two inxi -GSaz outputs (with radeon.cik_support=0 amdgpu.cik_support=1 and without): 6c6 < loglevel=3 radeon.cik_support=0 amdgpu.cik_support=1 --- > loglevel=3 9c9 < Tumbleweed 20240419 --- > Tumbleweed 20240429 11,12c11,12 < Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu < v: kernel alternate: radeon arch: GCN-2 code: Sea Islands --- > Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: radeon > v: kernel alternate: amdgpu arch: GCN-2 code: Sea Islands So, now the kernel loads the radeon module by default. I have two questions where I would appreciate your feedback. - Since I had never investigated in that before, is this the desired behavior, such as for new installations? - Shouldn't I/we/all rather stay with amdgpu (by considering the information on 'https://wiki.archlinux.org/title/AMDGPU'? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176976] libfreetype6 causes wish crashes
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1176976 https://bugzilla.suse.com/show_bug.cgi?id=1176976#c1 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #1 from Fridrich Strba <fstrba(a)suse.com> --- I was unable to reproduce this one. And this bug report is isolated with no other report about crashes. Closing as WORKSFORME. Feel free to reopen if it happens still. -- You are receiving this mail because: You are on the CC list for the bug.

1 0