June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1226201] New: dialog box opens in other screen in dual monitor
by bugzilla_noreply＠suse.com 18 Jul '24

18 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226201 Bug ID: 1226201 Summary: dialog box opens in other screen in dual monitor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: devguy.ca(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug has shown up maybe a few weeks back. Whenever I open a dialog box, like file open, it will open the dialog box on a different screen in my dual monitor setup. Why can't KDE be smart to just center the dialog over the app it belongs too? Operating System: openSUSE Tumbleweed 20240610 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217306] New: distrobox stuck at starting container
by bugzilla_noreply＠suse.com 18 Jul '24

18 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1217306 Bug ID: 1217306 Summary: distrobox stuck at starting container 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: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870843 --> https://bugzilla.suse.com/attachment.cgi?id=870843&action=edit few seconds of strace -p 5212 2>&1 | tee /tmp/strace-out.log Following happened on Leap 15.6 lkocman@localhost:~/Workspace> distrobox enter mirror Error: no such container mirror Cannot find container mirror Creating the container with command: /usr/bin/distrobox-create -i registry.opensuse.org/opensuse/distrobox:latest -n mirror Trying to pull registry.opensuse.org/opensuse/distrobox:latest... Getting image source signatures Copying blob 942e611a39d7 done Copying blob 1517c1ea8bb6 done Copying config 8372decf75 done Writing manifest to image destination 8372decf752e74665fcb94d31b9b378dd1790233ab36b03d37f63dac462e0fbc Creating 'mirror' using image registry.opensuse.org/opensuse/distrobox:latest [ OK ] Distrobox 'mirror' successfully created. To enter, run: distrobox enter mirror Container mirror is not running. Starting container mirror run this command to follow along: podman logs -f mirror Starting container... # Stuck here for 30 minutes or so lkocman@localhost:~/Workspace> ps aux | grep distro lkocman 5210 0.0 0.0 11096 3328 pts/0 S+ 08:13 0:00 /bin/sh /usr/bin/distrobox enter mirror lkocman 5212 2.1 0.0 11224 3840 pts/0 S+ 08:13 0:53 /bin/sh /usr/bin/distrobox-enter mirror lkocman 27424 0.0 0.0 8212 2304 pts/1 S+ 08:56 0:00 grep --color=auto distro Strace seems that the program itself is busy Not sure if this isn't an issue rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=27782, si_uid=1000, si_status=0, si_utime=2, si_stime=0} --- wait4(-1, 0x7ffc3cd5bbd0, WNOHANG, NULL) = -1 ECHILD (No child processes) rt_sigreturn({mask=[]}) = 0 openat(AT_FDCWD, "/home/lkocman/.cache/.mirror.fifo", O_RDONLY) = 3 fcntl(0, F_GETFD) = 0 fcntl(0, F_DUPFD, 10) = 10 fcntl(0, F_GETFD) = 0 fcntl(10, F_SETFD, FD_CLOEXEC) = 0 dup2(3, 0) = 0 close(3) = 0 ioctl(0, TCGETS, 0x7ffc3cd5c4f0) = -1 ENOTTY (Inappropriate ioctl for device) -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1226170] New: Chromium - widevine not being loaded in arm64 Linux
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226170 Bug ID: 1226170 Summary: Chromium - widevine not being loaded in arm64 Linux Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: gmbr3(a)opensuse.org Reporter: mrkcee(a)protonmail.com QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I noticed that Chromium in openSUSE Tumbleweed does not look for Widevine despite it being installed manually in the proper places. I have verified this in Tumbleweed running on both Apple Silicon (via Asahi Linux) and in an aarch64 VM (via UTM in macOS). This bug logged in Ubuntu explains the issue: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008433 Would it be possible to include the following patch (which is similar to the patch included in the Ubuntu bug report) to enable widevine checking for non-amd64 Linux systems? The first part of this patch I know is already being implemented. https://build.opensuse.org/projects/home:mrkcee:branches:network:chromium/p… I am able to build the package successfully in my branch. And is now working as expected. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222533] New: Libreoffice needs 100% CPU for 3 minutes to open Lenovo compatibility matrix
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222533 Bug ID: 1222533 Summary: Libreoffice needs 100% CPU for 3 minutes to open Lenovo compatibility matrix Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874156 --> https://bugzilla.suse.com/attachment.cgi?id=874156&action=edit perf record data for loading the file with native TW package Upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=160595 Environment: OpenSUSE Tumbleweed 20240329, GNOME/X11, libreoffice-calc-24.2.2.2-1.2.x86_64 Offending file: Lenovo Accessories and Options Compatibility Matrix (OCM) https://download.lenovo.com/pccbbs/options_iso/ocm_apr_2024.xlsx (access via http://www.lenovo.com/accessoriesguide) Steps to reproduce: Download and open the file with calc. Results: Calc hangs with 100% CPU with "load document" progress bar at ~80%. It finishes after ~3 minutes. With the flatpak version of Libreoffice, opening the file takes only ~15s. "perf report" shows for the openSUSE native package: Samples: 520K of event 'cycles:P', Event count (approx.): 366840243651 Overhead Command Shared Object Symbol 49.69% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7a8 27.60% soffice.bin libglib-2.0.so.0.8000.0 [.] g_node_insert_before 2.49% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7ac 1.32% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7af 0.85% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7b7 0.43% soffice.bin libc.so.6 [.] malloc 0.27% soffice.bin libuno_cppu.so.3 [.] typelib_typedescriptionreference_equals 0.23% soffice.bin libc.so.6 [.] _int_free -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1218122] New: Aeon: Unable to load any usable ISO8859 font
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1218122 Bug ID: 1218122 Summary: Aeon: Unable to load any usable ISO8859 font Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: alexlevinb(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:120.0) Gecko/20100101 Firefox/120.0 Build Identifier: I am getting Unable to load any usable ISO8859 font error when installing Veracrypt with ./veracrypt-1.26.7-setup-gtk3-gui-x64 Same error when running xmessage test: alex@dell-desktop:~> xmessage test Warning: Unable to load any usable ISO8859 font Error: Aborting: no font found I am getting the sam Reproducible: Always Steps to Reproduce: Run xmessage test -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219979] New: Bash exported function are renamed internally then are ignored by Systemd - Kde desktop
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1219979 Bug ID: 1219979 Summary: Bash exported function are renamed internally then are ignored by Systemd - Kde desktop Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: jcdole(a)free.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have bash definition functions and variables that are sourced from /etc/profile.d (case 1) or from ~/.profile (case 2) In case 1, journald show : Feb 15 17:13:55 15-4---G731GV-VM-04 startplasma-x11[1725]: Skipping syncing of environment variable "BASH_FUNC__MY_ECHO_%%" as name contains unsupported characters None of my function are exported to user environment. None of my functions use the double characters '%%' I have environment variables that defined colors : MY_LIGHT_RED=$'\e[1;31m' Journald show : Feb 15 17:13:55 15-4---G731GV-VM-04 startplasma-x11[1725]: Skipping syncing of environment variable "MY_LIGHT_RED" as value contains unsupported characters These colors definition are not exported to user environment. In case 2, journald show the same errors but in this case functions and env var are exported to the user environment. Any help is very welcome. -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1226400] New: Some applications don't support variable fonts well
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226400 Bug ID: 1226400 Summary: Some applications don't support variable fonts well Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: obs.coke518(a)passinbox.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- google-noto-sans-cjk-fonts and google-noto-serif-cjk-fonts switched to variable fonts, but some applications don't support it well. For the following two examples, assume the font "Noto Sans CJK JP" is installed as a variable font. JDownloader (installed by flatpak): 1. Open Settings from the menu 2. Select Advanced Settings in the left panel 3. enter "font name" in the textbox to filter the settings 4. enter Noto Sans CJK JP in the value field 5. Restart JDownloader 6. The new characters are too thin. It seems like it's using the smallest weight. And there is no way to select other weights. Freeplane (from repo http://download.opensuse.org/repositories/Office/openSUSE_Tumbleweed/) 1. Select Noto Sans CJK JP by the pulldown menu in the the toolbar 2. The characters in nodes are very thin For static fonts, all weights are installed as separate fonts and can be selected in the UI of the applications. I think giving users the option to install static fonts instead is more feasible than identifying all those applications incompatible with variable fonts and have them support it. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1224250] New: [Build 20240514] zdup from leap15.5[or 15.6], Detected 6 file conflicts with package libicu73
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1224250 Bug ID: 1224250 Summary: [Build 20240514] zdup from leap15.5[or 15.6], Detected 6 file conflicts with package libicu73 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4189488/modules/zdup /steps/111 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Created attachment 874891 --> https://bugzilla.suse.com/attachment.cgi?id=874891&action=edit Full serial log ## Description I can see below error messages when upgrading the system from leap15.5/15.6 to tw via "zdup" method. Is it an expected behavior? Please see attached file for detail serial log. ################### >Checking for file conflicts: [...............................................error] >Detected 6 file conflicts: > >File /usr/lib64/libicudata.so.73.2 > from install of > libicu73-73.2-3.3.x86_64 (repo1) > conflicts with file from package > libicu73_2-73.2-150000.1.7.1.x86_64 (@System) > >File /usr/lib64/libicui18n.so.73.2 > from install of > libicu73-73.2-3.3.x86_64 (repo1) > conflicts with file from package > libicu73_2-73.2-150000.1.7.1.x86_64 (@System) > >File /usr/lib64/libicuio.so.73.2 > from install of > libicu73-73.2-3.3.x86_64 (repo1) > conflicts with file from package > libicu73_2-73.2-150000.1.7.1.x86_64 (@System) > >File /usr/lib64/libicutest.so.73.2 > from install of > libicu73-73.2-3.3.x86_64 (repo1) > conflicts with file from package > libicu73_2-73.2-150000.1.7.1.x86_64 (@System) > >File /usr/lib64/libicutu.so.73.2 > from install of > libicu73-73.2-3.3.x86_64 (repo1) > conflicts with file from package > libicu73_2-73.2-150000.1.7.1.x86_64 (@System) > >File /usr/lib64/libicuuc.so.73.2 > from install of > libicu73-73.2-3.3.x86_64 (repo1) > conflicts with file from package > libicu73_2-73.2-150000.1.7.1.x86_64 (@System) > >File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. >Continue? [yes/no] (no): ################### ## Observation openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-Leap-15.6-gnome@64bit fails in [zdup](https://openqa.opensuse.org/tests/4189488/modules/zdup/steps/111) ## Test suite description Maintained by qe-core ## Reproducible Fails since (at least) Build [20240514](https://openqa.opensuse.org/tests/4189488) (current job) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1226232] New: Going to sleep and Hibernate often fails with black screen
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226232 Bug ID: 1226232 Summary: Going to sleep and Hibernate often fails with black screen Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: guidopro(a)mailbox.org QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Maybe same problem as in Tumbleweed Bug 1190357 : I was on Leap 15.5 with seperate partitions for /, /home and swap. Until now the automatic hibernation/suspend-to-disk after some time in sleep mode worked flawlessly. Now, after the upgrade to Leap 15.6, manually start hibernation and wake up again works, but when going automatically to sleep/ hibernate-after-sleep the screen is black and no button to wake up works, system freezes and has to be hard rebooted (because of that no log entry captured). Operating System: openSUSE Leap 15.6 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.4.0-150600.21-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-7100U CPU @ 2.40GHz Memory: 11.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1227139] New: Redis→valkey migration sets wrong permissions
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227139 Bug ID: 1227139 Summary: Redis→valkey migration sets wrong permissions 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: matt(a)milliams.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Previously I had redis installed and would start it with `sudo systemctl start redis@localhost`. With the move to valkey, I have updated my system and if I do `sudo systemctl start valkey@localhost` I get a failure. `sudo journalctl -u valkey(a)localhost.service` gives: ``` Jun 27 15:30:56 HEX systemd[1]: Starting Valkey instance: localhost... Jun 27 15:30:56 HEX valkey-server[31189]: 31189:C 27 Jun 2024 15:30:56.152 # Fatal error, can't open config file '/etc/valkey/localhost.conf': Permission denied Jun 27 15:30:56 HEX systemd[1]: valkey(a)localhost.service: Main process exited, code=exited, status=1/FAILURE Jun 27 15:30:56 HEX systemd[1]: valkey(a)localhost.service: Failed with result 'exit-code'. Jun 27 15:30:56 HEX systemd[1]: Failed to start Valkey instance: localhost. ``` and if I look at the old config file for redis, it's owned by the `redis` group: ``` $ sudo ls -hl /etc/redis total 108K -rw-r----- 1 root redis 106K May 31 11:42 localhost.conf.bak ``` but the new config file is owned by root (and not readable by others): ``` $ sudo ls -hl /etc/valkey/localhost.conf -rw-r----- 1 root root 106K Jun 26 22:52 /etc/valkey/localhost.conf ``` Looking at the migration script, I see from package `valkey-compat-redis` in `/usr/libexec/migrate_redis_to_valkey.bash`: ```bash ... cp $configfile /etc/valkey/$configfilename ... ``` which I'm assuming runs as root and therefore creates the new file with root ownership. If I do `sudo chgrp valkey /etc/valkey/localhost.conf` it at least gets past that part (though now it fails with:) ``` Jun 27 15:44:59 HEX systemd[1]: Starting Valkey instance: localhost... Jun 27 15:44:59 HEX valkey-server[2090]: *** FATAL CONFIG FILE ERROR (Version 7.2.5) *** Jun 27 15:44:59 HEX valkey-server[2090]: Can't open the log file: Permission denied Jun 27 15:44:59 HEX systemd[1]: valkey(a)localhost.service: Main process exited, code=exited, status=1/FAILURE Jun 27 15:44:59 HEX systemd[1]: valkey(a)localhost.service: Failed with result 'exit-code'. Jun 27 15:44:59 HEX systemd[1]: Failed to start Valkey instance: localhost. ``` which I can't see a reason for yet. -- You are receiving this mail because: You are on the CC list for the bug.

1 2