July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1210750] KDE:Extra/Digikam 8.x - no sound support
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1210750 https://bugzilla.suse.com/show_bug.cgi?id=1210750#c6 --- Comment #6 from Roland Kummler <rke(a)arcor.de> --- console messages during video playback: digiKam-8.1.0-x86-64.appimage, sound available ... QtAV::AVDemuxer::setStreamIndex: invalid index 0 ( valid is 0 ~ 0 ) for stream type 2 QtAV::audioFormatToAL: OpenAL audioFormatToAL error (null context): 0xa004 QtAV::AudioResamplerFF::prepare: src audio parameters 'channel layout(or channels),sample rate and sample format must be set before initialize resampler QtAV::VideoDecoderFFmpegBase::decode: no frame could be decompressed: Error number 54487 occurred 0 / 54487 QtAV::VideoThread::run: invalid video frame from decoder. undecoded data size: 0 digikam 8.1.0 KDE:Extra repo, no sound ... digikam.qtav.warn: invalid index 0 ( valid is 0 ~ 0 ) for stream type 2 digikam.qtav.warn: invalid video frame from decoder. undecoded data size: 0 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213765] New: nvidia driver removal does not run depmod making subsequent dracut calls fail
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213765 Bug ID: 1213765 Summary: nvidia driver removal does not run depmod making subsequent dracut calls fail Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- 2023-07-28 18:55:37|command|root@uefi|'zypper' 'rm' '--clean-deps' 'nvidia-driver-G06-kmp-default'| 2023-07-28 18:55:43|remove |nvidia-compute-G06-32bit|535.86.05-10.1|x86_64|| 2023-07-28 18:55:45|remove |nvidia-gl-G06-32bit|535.86.05-10.1|x86_64|| 2023-07-28 18:55:47|remove |nvidia-video-G06-32bit|535.86.05-10.1|x86_64|| 2023-07-28 18:56:07|remove |nvidia-gl-G06|535.86.05-10.1|x86_64|| 2023-07-28 18:56:09|remove |nvidia-video-G06|535.86.05-10.1|x86_64|| 2023-07-28 18:56:13|remove |libnvidia-egl-wayland1|1.1.12-1.1|x86_64|| 2023-07-28 18:56:18|remove |nvidia-compute-G06|535.86.05-10.1|x86_64|| # 2023-07-28 18:56:33 nvidia-driver-G06-kmp-default-535.86.05_k6.4.3_1-10.1.x86_64 removed ok # warning: /usr/lib/modprobe.d/50-nvidia-default.conf saved as /usr/lib/modprobe.d/50-nvidia-default.conf.rpmsave # warning: /usr/lib/dracut/dracut.conf.d/60-nvidia-default.conf saved as /usr/lib/dracut/dracut.conf.d/60-nvidia-default.conf.rpmsave # update-alternatives: warning: alternative /usr/lib/nvidia/alternate-install-present-default (part of link group alternate-install-present) doesn't exist; removing from list of alternatives 2023-07-28 18:56:33|remove |nvidia-driver-G06-kmp-default|535.86.05_k6.4.3_1-10.1|x86_64|root@uefi| So far so good, but subsequent dracut fails with dracut[I]: *** Including module: kernel-modules-extra *** realpath: updates/nvidia-modeset.ko: No such file or directory realpath: updates/nvidia-peermem.ko: No such file or directory realpath: updates/nvidia-drm.ko: No such file or directory realpath: updates/nvidia-uvm.ko: No such file or directory realpath: updates/nvidia.ko: No such file or directory dracut[F]: installkernel failed in module kernel-modules-extra Because user@uefi:~> ll /usr/lib/modules/6.4.4-1-default/updates/ total 0 user@uefi:~> grep nvidia /usr/lib/modules/6.4.4-1-default/modules.dep kernel/drivers/net/ethernet/nvidia/forcedeth.ko.zst: kernel/drivers/usb/typec/altmodes/typec_nvidia.ko.zst: kernel/drivers/usb/typec/altmodes/typec_displayport.ko.zst kernel/drivers/usb/typec/typec.ko.zst kernel/drivers/i2c/busses/i2c-nvidia-gpu.ko.zst: kernel/drivers/i2c/busses/i2c-ccgx-ucsi.ko.zst kernel/drivers/platform/x86/nvidia-wmi-ec-backlight.ko.zst: kernel/drivers/acpi/video.ko.zst kernel/drivers/platform/x86/wmi.ko.zst updates/nvidia-modeset.ko: updates/nvidia.ko kernel/drivers/acpi/video.ko.zst kernel/drivers/platform/x86/wmi.ko.zst updates/nvidia-peermem.ko: updates/nvidia-drm.ko: updates/nvidia-modeset.ko updates/nvidia.ko kernel/drivers/acpi/video.ko.zst kernel/drivers/platform/x86/wmi.ko.zst updates/nvidia-uvm.ko: updates/nvidia.ko updates/nvidia.ko: user@uefi:~> ll /usr/lib/modules/6.4.4-1-default/modules.dep -rw-r--r-- 1 root root 655367 Jul 25 21:47 /usr/lib/modules/6.4.4-1-default/modules.dep user@uefi:~> So modules.dep was not updated when drivers were removed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213577] uncomplete waydroid installation
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213577 https://bugzilla.suse.com/show_bug.cgi?id=1213577#c2 --- Comment #2 from Episteme PROMENEUR <epistemepromeneur(a)free.fr> --- done here https://build.opensuse.org/package/show/home%3AonlyJak0b%3AStable%3Awaydroi… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213743] virsh socket connect fail after Modular libvirt change
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213743 https://bugzilla.suse.com/show_bug.cgi?id=1213743#c3 --- Comment #3 from Michiya Hagimoto <kokeko(a)mac.com> --- Thanks, Yes I didnot see SLE bugs. OK, I use libvirt.conf default_uri setting for compatible. virtproxyd is same effect, but it have some compatibility problem for libvirt-guest service on reboot. all machine is forced terminate. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210750] KDE:Extra/Digikam 8.x - no sound support
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1210750 https://bugzilla.suse.com/show_bug.cgi?id=1210750#c5 --- Comment #5 from Roland Kummler <rke(a)arcor.de> --- Unfortunately, there is the identical problem with Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210750] KDE:Extra/Digikam 8.x - no sound support
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1210750 https://bugzilla.suse.com/show_bug.cgi?id=1210750#c4 --- Comment #4 from Roland Kummler <rke(a)arcor.de> --- (In reply to Christophe Marin from comment #3) > please run `zypper lr` then `sudo zypper dup --from <id>` > > where id is the packman repository. > > Does it propose switching packages? No changes have been performed since my packman repo has anyway higher priority (95). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1170890] VUL-0: CVE-2018-21232: re2c: uncontrolled recursion causes stack consumption in find_fixed_tags
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1170890 https://bugzilla.suse.com/show_bug.cgi?id=1170890#c2 Peter Simons <peter.simons(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Peter Simons <peter.simons(a)suse.com> --- I submitted a fix for SLE-15 in https://build.suse.de/request/show/304163. We cannot fix this issue in SLE-12 or SLE-11, because the re2c versions we have there are way older than the one in SLE-15 (which is itself pretty old) and none of the patches to fix this issue apply. The only way to fix that issue in SLE-12 and SLE-11 would be to upgrade re2c to a later version (such as the one in SLE-15). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210750] KDE:Extra/Digikam 8.x - no sound support
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1210750 https://bugzilla.suse.com/show_bug.cgi?id=1210750#c3 Christophe Marin <christophe(a)krop.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rke(a)arcor.de Flags| |needinfo?(rke(a)arcor.de) --- Comment #3 from Christophe Marin <christophe(a)krop.fr> --- please run `zypper lr` then `sudo zypper dup --from <id>` where id is the packman repository. Does it propose switching packages? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213721] New: [SELinux] <topic>
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213721 Bug ID: 1213721 Summary: [SELinux] <topic> Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: jbohac(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The new versions of kdump (since v1.9.0) save the initrd in /var/lib/kdump/initrd and maintain a symlink to the kernel the initrd has been build for in /var/lib/kdump/kernel. E.g.: dhcp198:~ # ls -lZ /var/lib/kdump/ total 35476 -rw-------. 1 root root system_u:object_r:kdump_var_lib_t:s0 36322984 Jul 27 14:28 initrd lrwxrwxrwx. 1 root root system_u:object_r:kdump_var_lib_t:s0 40 Jul 27 14:28 kernel -> /usr/lib/modules/6.3.9-5-default/vmlinuz SELinux blocks the following of the symlink during kdump service start. audit2allow suggests: allow kdump_t kdump_var_lib_t:lnk_file read; To me (a comlete SELinux noob) this makes sense and indeed creating and loading a module with audit2allow -M kdump-fix < /var/log/audit/audit.log semodule -i kdump-fix.pp fixes the problem. Operating System: openSUSE MicroOS SELinux status, mode and policy name: <TODO> SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 33 SELinux policy version and repository: <TODO> dhcp198:~ # rpm -qa|grep selinux-pol selinux-policy-20230622-2.1.noarch selinux-policy-targeted-20230622-2.1.noarch The software (incl. version) that is affected by the SELinux issue and the error message: kdump SELinux Audit log: dhcp198:~ # ausearch -ts today -m avc ---- time->Thu Jul 27 14:26:15 2023 type=PROCTITLE msg=audit(1690467975.028:134): proctitle=2F7362696E2F6B65786563002D70002F7661722F6C69622F6B64756D702F6B65726E656C002D2D617070656E643D2072642E74696D656F75743D36302072642E72657472793D34352071756965742073797374656D642E73686F775F7374617475733D79657320636F6E736F6C653D74747953302C31313532303020636F6E73 type=SYSCALL msg=audit(1690467975.028:134): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7ffd0d633da7 a2=0 a3=0 items=0 ppid=4833 pid=4834 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="kexec" exe="/usr/sbin/kexec" subj=system_u:system_r:kdump_t:s0 key=(null) type=AVC msg=audit(1690467975.028:134): avc: denied { read } for pid=4834 comm="kexec" name="kernel" dev="sda3" ino=48130 scontext=system_u:system_r:kdump_t:s0 tcontext=system_u:object_r:kdump_var_lib_t:s0 tclass=lnk_file permissive=0 ---- time->Thu Jul 27 14:26:15 2023 type=PROCTITLE msg=audit(1690467975.032:135): proctitle=2F7362696E2F6B65786563002D70002F7661722F6C69622F6B64756D702F6B65726E656C002D2D617070656E643D2072642E74696D656F75743D36302072642E72657472793D34352071756965742073797374656D642E73686F775F7374617475733D79657320636F6E736F6C653D74747953302C31313532303020636F6E73 type=SYSCALL msg=audit(1690467975.032:135): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7ffc2c117daa a2=0 a3=0 items=0 ppid=4835 pid=4836 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="kexec" exe="/usr/sbin/kexec" subj=system_u:system_r:kdump_t:s0 key=(null) type=AVC msg=audit(1690467975.032:135): avc: denied { read } for pid=4836 comm="kexec" name="kernel" dev="sda3" ino=48130 scontext=system_u:system_r:kdump_t:s0 tcontext=system_u:object_r:kdump_var_lib_t:s0 tclass=lnk_file permissive=0 ---- time->Thu Jul 27 14:26:15 2023 type=PROCTITLE msg=audit(1690467975.032:136): proctitle=2F7362696E2F6B65786563002D70002F7661722F6C69622F6B64756D702F6B65726E656C002D2D617070656E643D2072642E74696D656F75743D36302072642E72657472793D34352071756965742073797374656D642E73686F775F7374617475733D79657320636F6E736F6C653D74747953302C31313532303020636F6E73 type=SYSCALL msg=audit(1690467975.032:136): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7ffc2c117daa a2=0 a3=0 items=0 ppid=4835 pid=4836 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="kexec" exe="/usr/sbin/kexec" subj=system_u:system_r:kdump_t:s0 key=(null) type=AVC msg=audit(1690467975.032:136): avc: denied { read } for pid=4836 comm="kexec" name="kernel" dev="sda3" ino=48130 scontext=system_u:system_r:kdump_t:s0 tcontext=system_u:object_r:kdump_var_lib_t:s0 tclass=lnk_file permissive=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213743] virsh socket connect fail after Modular libvirt change
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213743 https://bugzilla.suse.com/show_bug.cgi?id=1213743#c2 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #2 from James Fehlig <jfehlig(a)suse.com> --- Agree it's a duplicate, but might not be visible to the reporter since it's a SLE bug. From comment 10 of that bug: --- Support for modular daemons can be thought of in two phases. The first phase is making clients aware of modular daemons. They should be able to work equally well with monolithic libvirtd or modular daemons. This phase is what I aim to fix here by building the library with support for modular daemons. The second phase is switching new deployments from the monolithic libvirtd to modular daemons. This phase has been done in Factory/Tumbleweed and is under consideration for SLE15 SP6 via jira PED-4804. --- Some workarounds until the fix reaches Leap 15.5: 1. Specify the connection URI directly, e.g. 'virsh -c qemu:///system list'. Optionally add the URI to 'uri_default' in /etc/libvirt/libvirt.conf or in LIBVIRT_DEFAULT_URI env variable to avoid specifying it each time you use virsh or other libvirt client. 2. Enable and start virtproxyd.service. It proxies client connections on the old monolithic socket (/var/run/libvirt/libvirt-sock) to the appropriate modular daemon socket. *** This bug has been marked as a duplicate of bug 1213352 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0