April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1223117] New: Fcitx5 can't work for Qt6 based apps
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223117 Bug ID: 1223117 Summary: Fcitx5 can't work for Qt6 based apps Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: sauntor(a)yeah.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is only fcitx5 plugin for qt5 (a.k. fcitx5-qt5, which supplies /usr/lib64/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so), but no package supplies the the plugin for qt6! As for this reason, apps developed with Qt6 (like Qt Creator) can't use fcitx5 as the input method. Tumbleweed seems has the same problem too. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217466] New: Missing fonts for Indic and south Asian languages.
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217466 Bug ID: 1217466 Summary: Missing fonts for Indic and south Asian languages. Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: sebastian(a)cozycabin.se QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0 Build Identifier: After installing, I noticed a lack of font support for a lot of Indic and south Asian languages. They are both pretty populous areas so it seems like an oversight to not include their basic fonts in the default installation. Reproducible: Always Steps to Reproduce: 1. Open Firefox from Flatpak (as installed by default). 2. Go to https://meta.wikimedia.org/wiki/List_of_Wikipedias 3. Look at the "Other languages" box at the top of the page. Actual Results: I see TOFU for several languages including Kannada. Expected Results: I expected to see all languages in that box be rendered by default. I did a bit of research, and we are talking about at least these ones, listed in order of native speakers counted in millions (based on quick Wikipedia data): | Language | Native Speakers | L2 Speakers | | ---------- | -----------------:| --------------:| | Telugu | 83 | 13 | | Kannada | 44 | 15 | | Burmese | 33 | 10 | | Khmer | 17 | 1 | | Santali | 7.6 | - | | Shan | 4.7 | - | | Tulu | 1.85 | - | | Manipuri | 1.8 | 1.2 | | Tibetan | 1.2 | - | | Mon | 0.9 | - | | Pa'O | 0.86 | - | | Dzongkha | ~0.2 | ~0.4 | | ========== | ================= | ============== | | Total | 196.11 million | 40.6 million | While it would be nice to have all of them, I don't think that should be a priority, but having at least fonts for the top ones seems reasonable. That would be a very small impact while being very useful to a large number of people. Fedora for instance, have already done some of this research which we could leverage. Which I found here: https://fedoraproject.org/wiki/Changes/Indic_Noto_fonts It basically would include including these fonts in the pattern, in both Sans and Sans-Serif versions: - google-noto-sans-bengali-vf-fonts - google-noto-sans-devanagari-vf-fonts - google-noto-sans-gujarati-vf-fonts - google-noto-sans-kannada-vf-fonts - google-noto-sans-oriya-vf-fonts - google-noto-sans-tamil-vf-fonts - google-noto-sans-telugu-vf-fonts As an alternative, there is the indic-fonts package which Fedora intended to switch away from, Zypper marks it as being only 6.2 MiB when installed. This does not to my knowledge include fonts for Khmer or Burmese, so that would require some additional research. Unfortunately I don't know any of these languages so I can not comment on any specifics when it comes to which font should be used for which language. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213055] New: locale problems in the default distrobox configuration
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213055 Bug ID: 1213055 Summary: locale problems in the default distrobox configuration Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: All OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Distrobox Assignee: rbrown(a)suse.com Reporter: shadenk30011(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Build Identifier: When creating a new container using "distrobox-create" the container fails to display directory names properly. For example the directory named "Stažené" shows up as "'Sta'$'\305\276''en'$'\303\251'" when using ls. Reproducible: Always Steps to Reproduce: 1. Use the czech locale 2. Create a directory inside the home that uses one of the offending symbols 3. Create a new distrobox container and run "ls" Actual Results: Directory name isn't properly displayed. Expected Results: Directory name is properly displayed. A workaround is to install the "glibc-locale" package. This can be automated by adding 'container_additional_packages="glibc-locale"' into the distrobox configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1221521] New: kup-backup not present in Plasma6 Systemsettings
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221521 Bug ID: 1221521 Summary: kup-backup not present in Plasma6 Systemsettings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ub22(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After update to Plasma 6, kup-backup is no more present inside of the Plasma Systemsettings application. I Installed and Reinstallt it meanwhile - but not present in the Systemssetting. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221513] New: Dolphin looses locations view when minimizing (X11)
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221513 Bug ID: 1221513 Summary: Dolphin looses locations view when minimizing (X11) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: oliver(a)schwabedissen.name QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When minimizing dolphin and then restoring the window, the locations view on the left is disabled. It has to be activated again using F9. Happens since Plasma6 when using X11 (seems fine with Wayland). -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223174] New: libkwin6: undefined symbol drmSyncobjEventfd
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223174 Bug ID: 1223174 Summary: libkwin6: undefined symbol drmSyncobjEventfd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: IA64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: edercarneiru(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Try running plasma 6.0.2 from opensuse tw unstable repos, result in: `kwin_wayland: symbol lookup error: /lib64/libkwin.so.6: undefined symbol: drmSyncobjEventfd` software versions: libkwin6-6.0.80git.20240419T230656~fba948b3-ku.41.1.x86_64 libdrm2-2.4.120-1.3.x86_64 libdrm2 already satisfies what is required here: https://invent.kde.org/plasma/kwin/-/merge_requests/5610 running 'nm -D /usr/lib64/libdrm.so.2 | grep SyncobjEvent' returns 000000000000c0b0 T drmSyncobjEventfd tried also rpmrebuild, no success. My KDE repos: 1 | KDE:Qt6 | KDE:Qt6 2 | KDE:Unstable:Applications | KDE:Unstable:Applications 3 | KDE:Unstable:Extra | KDE:Unstable:Extra 4 | KDE:Unstable:Frameworks | KDE:Unstable:Frameworks 5 | KDE:Unstable:Qt | KDE:Unstable:Qt -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223167] New: upgrade from Leap 15.4 to 15.5 failed in inst_repositories_initialization
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223167 Bug ID: 1223167 Summary: upgrade from Leap 15.4 to 15.5 failed in inst_repositories_initialization Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: carlsonj(a)workingcode.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 874393 --> https://bugzilla.suse.com/attachment.cgi?id=874393&action=edit YaST log files I attempted to do the offline/DVD upgrade of an existing Leap 15.4 system to 15.5. I downloaded the DVD image and verified the SHA signature before burning the image. On booting the DVD image and selecting "Upgrade" from the initial menu, I was eventually given the attached pop-up window before the "welcome" stage of upgrade. The text in that window says: YaST2 Calling the YaST module `inst_repositories_initialization has failed. More information can be found near the end of the /var/log/YasT2/y2log' file. This is worth reporting a bug at http://bugzilla.suse.com/: Please, attach also all YaST logs stored in the /var/log/YaST2/' directory. See http://en.opensuse.org/Bugs/YaST for more information about YasT logs. I was able to tar up the /var/log/YaST2 directory; the contents are attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1222408] New: VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222408 Bug ID: 1222408 Summary: VirtualBox not allowed to access USB devices although user is in vboxusers group Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: michael.nickol(a)t-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- same as bug #1222186 but now for leap 15.5 after update today (7. april 2024) symptom: Silentmax:~ # /usr/lib/virtualbox/vboxdrv.sh status chmod: cannot access '/etc/vboxusb/': No such file or directory chmod: cannot access '/etc/vboxusb/*': No such file or directory chmod: cannot access '/etc/vboxusb/*/*': No such file or directory VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp) are loaded. Silentmax:~ # uname -a Linux Silentmax.fritz.box 5.14.21-150500.55.52-default #1 SMP PREEMPT_DYNAMIC Tue Mar 5 16:53:41 UTC 2024 (a62851f) x86_64 x86_64 x86_64 GNU/Linux virtualbox - VirtualBox is an Emulator Version: 7.0.14-lp155.2.19.1 Installed: 7.0.14-lp155.2.19.1 Size: 84.7 MiB Media No.: 0 License: GPL-2.0-or-later Source Package: virtualbox-7.0.14-lp155.2.19.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1223144] New: GIMP segmentation fault
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223144 Bug ID: 1223144 Summary: GIMP segmentation fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: oberkut(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874375 --> https://bugzilla.suse.com/attachment.cgi?id=874375&action=edit Crash log GIMP Segmentation fault 1.Open GIMP. 2.Create Project. 3.Draw any image. 4.Close GIMP (Not saved changes). -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1219419] New: system broken after distrobox-export --bin sudo
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219419 Bug ID: 1219419 Summary: system broken after distrobox-export --bin sudo Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Distrobox Assignee: rbrown(a)suse.com Reporter: marco.trauffler(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:122.0) Gecko/20100101 Firefox/122.0 Build Identifier: sudo is not working anymore entering distrobox with --root is not working anymore in both cases command does not return anymore, memory is incrementing, CPU is working heavily system must be rebooted within 2 minutes before memory is full! Reproducible: Didn't try Steps to Reproduce: 1. create a container with distrobox create --name NAME --image IMAGE --root 2. enter the container with distrobox enter NAME --root 3. inside the container run: distrobox-export --bin sudo note: unable to reproduce on my machine because system nearly unusable, hope I do not need to reinstall. Actual Results: I do not know any solution to get sudo working again outside the container I do not know any solution to enter the container with --root anymore note: all not --root containers are still working note: rollback to previous state does not help what to do as my system gets unusable with above problems Expected Results: behaviour expected: use sudo outside of distrobox still beeing able to enter distrobox with --root actual behaviour: sudo outside of distrobox hangs and doesn't return anymore. the CPU usage is high and the memory is incrementing until full. same bahaviour when trying distrobox enter --root -- You are receiving this mail because: You are on the CC list for the bug.

1 4