May 2024 - openSUSE Bugs - openSUSE Mailing Lists

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