January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219277] KDE login notification sound not playing
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219277 https://bugzilla.suse.com/show_bug.cgi?id=1219277#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(alanhants(a)gmail.c | |om) CC| |alanhants(a)gmail.com, | |fvogt(a)suse.com --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Probably related to the switch to phonon-backend-vlc. Just to make sure, that package is installed on your system? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177605] Add pam_snapper support to pam-config
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1177605 https://bugzilla.suse.com/show_bug.cgi?id=1177605#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- I don't think that pam_snapper should be added to a common file and thus pam-config at all, since this would also mean that everytime cron or something similar is running, a snapshot is created, too. pam_snapper should be added to single login services where it makes sense, but this is outside the scope of pam-config. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202663] dracut fails to remove older kernels when using the YaST upgrade option
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1202663 https://bugzilla.suse.com/show_bug.cgi?id=1202663#c7 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NORESPONSE Flags|needinfo?(droidbittin@gmail | |.com) | Status|REOPENED |RESOLVED --- Comment #7 from Michal Suchanek <msuchanek(a)suse.com> --- Works for me -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189456] Add ashmem and binder drivers
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1189456 https://bugzilla.suse.com/show_bug.cgi?id=1189456#c8 --- Comment #8 from Dmitry Markov <werwolf131313(a)gmail.com> --- *** Bug 1219258 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219258] New: add binder kernel module
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219258 Bug ID: 1219258 Summary: add binder kernel module 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: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For waydroid and anbox, as well as similar programs to work, the binder kernel module is required, which is not in the standard opensuse kernel. is it possible to add it as kmp? > [werwolf@home] ~ > ❯ zgrep BINDER /proc/config.gz > # CONFIG_ANDROID_BINDER_IPC is not set > > [werwolf@home] ~ > ❯ rpm -qf /boot/vmlinuz-6.7.1-2-default > kernel-default-6.7.1-2.1.x86_64 > > [werwolf@home] ~ > ❯ LANG=c zypper info kernel-default > Loading repository data... > Reading installed packages... > > > Information for package kernel-default: > --------------------------------------- > Repository : repo-oss > Name : kernel-default > Version : 6.7.1-2.1 > Arch : x86_64 > Vendor : openSUSE > Installed Size : 240.3 MiB > Installed : Yes > Status : up-to-date > Source package : kernel-default-6.7.1-2.1.nosrc > Upstream URL : https://www.kernel.org/ > Summary : The Standard Kernel > Description : > The standard kernel for both uniprocessor and multiprocessor systems. > > > Source Timestamp: 2024-01-26 06:32:58 +0000 > GIT Revision: 6aca25404404e4f72fa252563503b29fe5828cca > GIT Branch: stable -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1219258] add binder kernel module
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219258 https://bugzilla.suse.com/show_bug.cgi?id=1219258#c6 --- Comment #6 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Dmitry Markov from comment #5) > (In reply to Ivan Ivanov from comment #4) > > (In reply to Dmitry Markov from comment #3) > > > > > Should this be regarded as a refusal or an impossibility? > > > I reopened the report to get a final answer like "this will never be done > > > because..." or "this will be done in such and such a release" > > > > Please read comment#1 in bsc#1189456 for an explanation. > > does this mean that I should have reopened not this request but bsc#1189456 > with the same question? > Sorry, I really didn't understand. To be considerd for enabling "Android IPC" should be able to be build as "loadable modules". This is not currently possible. This should be "fixed" upstream first (like in the Linus Torvalds tree). CONFIG_ANDROID_BINDER_IPC=m -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219258] add binder kernel module
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219258 https://bugzilla.suse.com/show_bug.cgi?id=1219258#c5 --- Comment #5 from Dmitry Markov <werwolf131313(a)gmail.com> --- (In reply to Ivan Ivanov from comment #4) > (In reply to Dmitry Markov from comment #3) > > > Should this be regarded as a refusal or an impossibility? > > I reopened the report to get a final answer like "this will never be done > > because..." or "this will be done in such and such a release" > > Please read comment#1 in bsc#1189456 for an explanation. does this mean that I should have reopened not this request but bsc#1189456 with the same question? Sorry, I really didn't understand. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219258] add binder kernel module
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219258 https://bugzilla.suse.com/show_bug.cgi?id=1219258#c4 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan.ivanov(a)suse.com --- Comment #4 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Dmitry Markov from comment #3) > Should this be regarded as a refusal or an impossibility? > I reopened the report to get a final answer like "this will never be done > because..." or "this will be done in such and such a release" Please read comment#1 in bsc#1189456 for an explanation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217492] KVM vm client can no longer use a USB pass through device
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217492 https://bugzilla.suse.com/show_bug.cgi?id=1217492#c12 --- Comment #12 from Lin Ma <lma(a)suse.com> --- Emm...It looks like the relevant code paths have not been touched at all, the Conbee II stick hasn't been unbinded from cdc_acm driver in vmhost kernel, and qemu hasn't invoke the function usb_host_claim_interface either. Could you please run below test to collect more trace data? 1. Make sure the vm USB_Test is off. 2. Create a usb hostdev xml like this: e.g: cat hostdev_usb_ConbeeII.xml <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1cf1'/> <product id='0x0030'/> </source> </hostdev> 3. Remove the hostdev section from vm USB_Test configuration. 4. virsh start USB_Test 5. Add below trace events: virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_close on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_reset on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_auto_scan_enabled on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_open_* on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_parse_* on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_detach_kernel on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_attach_kernel on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_claim_interface on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_release_interface on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_set_* on" virsh qemu-monitor-command USB_Test --hmp "trace-event usb_host_req_* on" 6. Issues below commands: lsusb -d 1cf1:0030 -v lsusb -t virsh attach-device USB_Test hostdev_usb_ConbeeII.xml lsusb -t 7. Attach the outputs of step#6 and the /var/log/libvirt/qemu/USB_Test.log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218783] grub: Should Remove magic number header field check on aarch64
by bugzilla_noreply＠suse.com 29 Jan '24

29 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218783 https://bugzilla.suse.com/show_bug.cgi?id=1218783#c1 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang(a)suse.com Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Michael Chang <mchang(a)suse.com> --- Hello, The patch removing the magic number check has been submitted to openSUSE:Factory and will be released in a few days. https://build.opensuse.org/request/show/1142178 It has also been verified by the alpine kernel and initrd link in the Description. Set the resolution to fixed, feel free to reopen if it doesn't work after updating to the released package. -- You are receiving this mail because: You are on the CC list for the bug.

1 0