July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213614] New: Mesa-dri: Segmentation fault in freedreno [msi-dri.so] while running on Lenovo x13s laptop
by bugzilla_noreply＠suse.com 14 Sep '23

14 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1213614 Bug ID: 1213614 Summary: Mesa-dri: Segmentation fault in freedreno [msi-dri.so] while running on Lenovo x13s laptop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: chester.lin(a)suse.com QA Contact: gfx-bugs(a)suse.de CC: afaerber(a)suse.com, andrea.porta(a)suse.com, ivan.ivanov(a)suse.com, mbenes(a)suse.com, mbrugger(a)suse.com, sndirsch(a)suse.com, stanimir.varbanov(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 868409 --> https://bugzilla.suse.com/attachment.cgi?id=868409&action=edit Lenovox13s-logs The Mesa-dri-23.1.3-353.1 package from Factory cannot run on Lenovo x13s [An aarch64-laptop. CPU: Qualcomm 8cx Gen3, GPU: Qualcomm Adreno 690], a segmentation fault always occurs when gdm tries to run Xorg.bin. The same symptom can be seen as well when trying to run Xwayland. The Mesa-dri was installed on my experimental JeOS built on OBS since x13s is not supported by openSUSE tumbleweed yet: https://build.opensuse.org/project/show/home:clin:branches:X13S This test kernel is based on upstream v6.4-final + some reviewing patches for x13s in upstream, and a GPU firmware "a690_gmu.bin" required by the Adreno kernel driver [adreno_device.c] is still missing from linux-firmware upstream although it should not crash GNOME initialization since the linaro-customized-debian for x13s can still work without loading GPU firmware blobs successfully. The attached log files include some basic logs [dmesg, journal, installed Mesa package list ] and a supportconfig tgz I collected from the laptop. gdm error log ============= Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: MESA: error: get_param:232: get-param failed! -6 (No such device or address) Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: MESA: error: get_param:232: get-param failed! -6 (No such device or address) Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: MESA: error: get_param:232: get-param failed! -6 (No such device or address) Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: MESA: error: get_param:232: get-param failed! -6 (No such device or address) Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: MESA: error: fd_pipe_new2:52: allocation failed Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) Backtrace: Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x68) [0xaaaac5def608] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 1: /usr/bin/Xorg.bin (0xaaaac5c20000+0x1d8954) [0xaaaac5df8954] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 2: linux-vdso.so.1 (__kernel_rt_sigreturn+0x0) [0xffffb29ae7a0] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 3: /usr/lib64/dri/msm_dri.so (0xffffaf760000+0x94fb7c) [0xffffb00afb7c] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 4: /usr/lib64/dri/msm_dri.so (0xffffaf760000+0xab6ae4) [0xffffb0216ae4] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 5: /usr/lib64/dri/msm_dri.so (0xffffaf760000+0xecd0c) [0xffffaf84cd0c] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 6: /usr/lib64/dri/msm_dri.so (0xffffaf760000+0x66fe08) [0xffffafdcfe08] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 7: /usr/lib64/dri/msm_dri.so (0xffffaf760000+0xf4bf0) [0xffffaf854bf0] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 8: /usr/lib64/dri/msm_dri.so (0xffffaf760000+0xe3470) [0xffffaf843470] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 9: /lib64/libgbm.so.1 (0xffffb12a0000+0xe79c) [0xffffb12ae79c] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 10: /lib64/libgbm.so.1 (0xffffb12a0000+0x109dc) [0xffffb12b09dc] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 11: /lib64/libgbm.so.1 (0xffffb12a0000+0xe4c0) [0xffffb12ae4c0] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 12: /lib64/libgbm.so.1 (gbm_create_device+0x130) [0xffffb12ae624] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 13: /usr/lib64/xorg/modules/libglamoregl.so (glamor_egl_init+0x1d4) [0xffffb12e9078] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 14: /usr/lib64/xorg/modules/drivers/modesetting_drv.so (0xffffb13a0000+0xfc3c) [0xffffb13afc3c] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 15: /usr/bin/Xorg.bin (InitOutput+0x1084) [0xaaaac5ccbaf4] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 16: /usr/bin/Xorg.bin (0xaaaac5c20000+0x4f558) [0xaaaac5c6f558] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 17: /lib64/libc.so.6 (0xffffb1ed0000+0x2abc8) [0xffffb1efabc8] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 18: /lib64/libc.so.6 (__libc_start_main+0x9c) [0xffffb1efaca0] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) 19: /usr/bin/Xorg.bin (_start+0x30) [0xaaaac5c701f0] Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) Segmentation fault at address 0x10 Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: Fatal server error: Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) Caught signal 11 (Segmentation fault). Server aborting Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) Jul 24 11:11:58 localhost.localdomain /usr/libexec/gdm/gdm-x-session[1119]: (EE) -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1212874] New: External Monitor on USB-C Docking station AMD Graphics
by bugzilla_noreply＠suse.com 13 Sep '23

13 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1212874 Bug ID: 1212874 Summary: External Monitor on USB-C Docking station AMD Graphics Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: j.g.joseph4884(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Just reinstalled OpenSuse Tumbleweed to see if my install was impacting the external monitor connection on my docking station - Still occurs; Hardware * Laptop - Thinkoad E595 | AMD Ryzen 5 * Docking Station - Lenovo 40AS0090US * External Monitors - 1 High Refresh Rate 1080p (Displayport) & 1 UltraWide 1080p (HDMI) On Windows - The Laptop displays on all monitors with no issues at the highest refresh rates for both monitors Been having issues since the start of Kernel 6.0 where I cannot use both my external monitors with my laptop at 1080p. When I keep the laptop plugged into the docking station and let the device sleep, it crashes before it can fully sleep with the cursor still slightly visible on a dark background. If I keep the laptop plugged into the docking station on startup, it crashes right when the loading circle starts to spin above the Tumbleweed logo. Let me know what commands I need to enter to output info to assist the kernel developers -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1213555] New: obs-service-tar fails on Rawhide (python 3.12 problems)
by bugzilla_noreply＠suse.com 13 Sep '23

13 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1213555 Bug ID: 1213555 Summary: obs-service-tar fails on Rawhide (python 3.12 problems) Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: Fedora Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Packages which use tar service set to buildtime cannot be built for Fedora rawhide. Example log (from devel:languages:nodejs/bitwarden) [ 36s] Unpacking bitwarden-2023.5.1.obscpio ... [ 37s] 37175 blocks [ 37s] Running build time source services... [ 37s] Traceback (most recent call last): [ 37s] File "/usr/lib/obs/service/tar", line 30, in <module> [ 37s] main() [ 37s] File "/usr/lib/obs/service/tar", line 26, in main [ 37s] TarSCM.run() [ 37s] File "/usr/lib/obs/service/TarSCM/__init__.py", line 39, in run [ 37s] task_list.process_list() [ 37s] File "/usr/lib/obs/service/TarSCM/tasks.py", line 131, in process_list [ 37s] self.process_single_task(task) [ 37s] File "/usr/lib/obs/service/TarSCM/tasks.py", line 211, in process_single_task [ 37s] self.scm_object = scm_object = scm_class(args, self) [ 37s] ^^^^^^^^^^^^^^^^^^^^^ [ 37s] File "/usr/lib/obs/service/TarSCM/scm/base.py", line 82, in __init__ [ 37s] self._calc_repocachedir() [ 37s] File "/usr/lib/obs/service/TarSCM/scm/base.py", line 234, in _calc_repocachedir [ 37s] repocachedir = Config().get('tar_scm', 'CACHEDIRECTORY') [ 37s] ^^^^^^^^ [ 37s] File "/usr/lib/obs/service/TarSCM/config.py", line 47, in __init__ [ 37s] self.configs.append(self._init_config(fname)) [ 37s] ^^^^^^^^^^^^^^^^^^^^^^^^ [ 37s] File "/usr/lib/obs/service/TarSCM/config.py", line 73, in _init_config [ 37s] config.readfp(tmp_fp) [ 37s] ^^^^^^^^^^^^^ [ 37s] AttributeError: 'RawConfigParser' object has no attribute 'readfp'. Did you mean: 'read'? [ 37s] service run failed for service 'tar' -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212835] New: make modules_install fails with kmod-30-4.1
by bugzilla_noreply＠suse.com 11 Sep '23

11 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1212835 Bug ID: 1212835 Summary: make modules_install fails with kmod-30-4.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: msuchanek(a)suse.com Reporter: ptesarik(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the usrmerge patches, depmod now accesses $base/usr/lib/modules instead of $base/lib/modules. Unfortunately, scripts/depmod.sh in the kernel sources cannot cope with that and fails with a slightly confusing message: depmod: ERROR: could not open directory /srv/research/dynswiotlb-9p/usr/lib/modules/99.98.6.5.0-devel+: No such file or directory I can see how this is fixed for RPM builds (https://github.com/SUSE/kernel-source/commit/da84579e78f4c4efa5b3b910484fda…) but I can no longer run "make modules_install" from the expanded kernel tree. -- You are receiving this mail because: You are on the CC list for the bug.

1 43

[Bug 1213197] New: yupdate does not run pre/post scripts
by bugzilla_noreply＠suse.com 10 Sep '23

10 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1213197 Bug ID: 1213197 Summary: yupdate does not run pre/post scripts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lslezak(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- The yupdate tool does not run pre/post scripts when applying the patch from GitHub. Patching from a local server ("rake server") works fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213459] New: suse-module-tools: allow to replace regenerate-initrd-posttrans
by bugzilla_noreply＠suse.com 05 Sep '23

05 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1213459 Bug ID: 1213459 Summary: suse-module-tools: allow to replace regenerate-initrd-posttrans Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: martin.wilck(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There's currently no integration of dracut with the way the systemd-boot prototype support works (https://en.opensuse.org/Systemd-boot) So calling dracut to generate an initrd would lead to the initrd in the wrong place aka useless. Instead one would have to call "sdbootutil add-kernel" resp "sdbootutil add-all-kernels". The interface is still WIP so I wouldn't want to ask for adding those calls actually. Instead I'd like to have a way to override the script. The rpm scriptlets are already in a subpackage so I can provide alternatives. How about moving regenerate-initrd-posttrans there too? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213120] New: [trackerbug] docker 24.0.3-ce update
by bugzilla_noreply＠suse.com 05 Sep '23

05 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1213120 Bug ID: 1213120 Summary: [trackerbug] docker 24.0.3-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.3-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/24.0/#2403>. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213745] New: cirrus logic speaker (cs35l41-hda, sof-firmware) not working after resuming from suspend
by bugzilla_noreply＠suse.com 01 Sep '23

01 Sep '23

https://bugzilla.suse.com/show_bug.cgi?id=1213745 Bug ID: 1213745 Summary: cirrus logic speaker (cs35l41-hda, sof-firmware) not working after resuming from suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: ofrofro(a)qq.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868475 --> https://bugzilla.suse.com/attachment.cgi?id=868475&action=edit dmesg output after a "fresh boot -> suspend-resume -> suspend-resume" sequence (i clicked the sound check in each time in gnome control center) Dear OpenSUSE development team, The cirrus logic speaker on my "hp zbook fury g9" laptop (a relatively new model) will stop working after the first suspend after system boot, but will work again after second/third/... suspend, though the sound volume will get significantly lower. By the way, when doing research on the internet I found Mr. Takashi Iwai's communication with a cirrus developer on LKML: https://lkml.org/lkml/2023/7/21/901 It seems that the problem will be fixed with the next kernel update, but I'm not really sure about that due to my non-technical background. And if that is so, could I ask for an rough estimation of the date for this relevant kernel update to arrive in tumbleweed? Thanks for your time and the great work. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1213153] New: x11vnc slow and generates mouse errors after kernel 6.3.7 - Debian reports fix for x11vnc.
by bugzilla_noreply＠suse.com 29 Aug '23

29 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213153 Bug ID: 1213153 Summary: x11vnc slow and generates mouse errors after kernel 6.3.7 - Debian reports fix for x11vnc. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: llrainey15(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I get log entries that do not happen in Leap 15.5. Also response it extremely slow typing. Searching the internet I found the aur version x11vnc-git 1:0.9.16.r12 it fixed the issue. It appears to be a 6.3.7 and newer kernel issue. Link https://aur.archlinux.org/packages/x11vnc-git I think they are mouse movements - that is what is in most of the Debian issues. 08/07/2023 10:38:47 client 1 network rate 35445.7 KB/sec (95144.3 eff KB/sec) 08/07/2023 10:38:47 client 1 latency: 0.7 ms 08/07/2023 10:38:47 dt1: 0.0410, dt2: 0.0465 dt3: 0.0007 bytes: 3090570 08/07/2023 10:38:47 link_rate: LR_LAN - 1 ms, 35445 KB/s 08/07/2023 10:38:47 client_set_net: 192.168.20.101 0.0003 08/07/2023 10:38:57 created selwin: 0x1700040 08/07/2023 10:38:57 called initialize_xfixes() *** fb_push ublen NOT ZERO: 16311911 *** fb_push ublen NOT ZERO: 1526748927 *** fb_push ublen NOT ZERO: -301943553 *** fb_push ublen NOT ZERO: -1728058381 *** fb_push ublen NOT ZERO: 457704657 *** fb_push ublen NOT ZERO: -205 *** fb_push ublen NOT ZERO: 1208277247 *** fb_push ublen NOT ZERO: 655148 *** fb_push ublen NOT ZERO: 1226440954 *** fb_push ublen NOT ZERO: 1094748757 *** fb_push ublen NOT ZERO: -70254515 *** fb_push ublen NOT ZERO: -49267 *** fb_push ublen NOT ZERO: 1905121 *** fb_push ublen NOT ZERO: 1834029090 *** fb_push ublen NOT ZERO: 1241519162 *** fb_push ublen NOT ZERO: 1230537984 *** fb_push ublen NOT ZERO: 1392507903 *** fb_push ublen NOT ZERO: -16777472 *** fb_push ublen NOT ZERO: 14810963 *** fb_push ublen NOT ZERO: -402849681 user@LLR4:~> x11vnc --version x11vnc: 0.9.16 lastmod: 2019-01-05 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213657] New: Firefox and Thunderbird don't launch when using dash-sh
by bugzilla_noreply＠suse.com 28 Aug '23

28 Aug '23

https://bugzilla.suse.com/show_bug.cgi?id=1213657 Bug ID: 1213657 Summary: Firefox and Thunderbird don't launch when using dash-sh 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: rx2l5t+4zshakz4lenfc(a)sharklasers.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Both Firefox and Thunderbird's bin files seem to use bashisms and exit out with this error: 154: Syntax error: "(" unexpected (expecting "fi") Making it use bash fixes the issue. I know Firefox started erroring out in the 115 releases, not sure about Thunderbird. -- You are receiving this mail because: You are on the CC list for the bug.

1 4