May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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 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