October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1231067] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - driver does not function after kernel 6.10
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231067 https://bugzilla.suse.com/show_bug.cgi?id=1231067#c12 --- Comment #12 from Stefan Dirsch <sndirsch(a)suse.com> --- This is getting more and more confusing. Maybe you should redo all the tests and run cat /proc/cmdline when testing to see what is really set as driver options. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231175] New: [Build 20240930] openQA test fails in add_box_virtualbox: vagrant does not support virutalbox 7.1
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231175 Bug ID: 1231175 Summary: [Build 20240930] openQA test fails in add_box_virtualbox: vagrant does not support virutalbox 7.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4525032/modules/add_ box_virtualbox/steps/41 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation INFO interface: error: The provider 'virtualbox' that was requested to back the machine 'default' is reporting that it isn't usable on this system. The reason is shown below: Vagrant has detected that you have a version of VirtualBox installed that is not supported by this version of Vagrant. Please install one of the supported versions listed below to use Vagrant: 4.0, 4.1, 4.2, 4.3, 5.0, 5.1, 5.2, 6.0, 6.1, 7.0 A Vagrant update may also be available that adds support for the version you specified. Please check www.vagrantup.com/downloads.html to download the latest version. openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_vagrant@64bit fails in [add_box_virtualbox](https://openqa.opensuse.org/tests/4525032/modules/add_b… ## Test suite description Maintainer: dancermak. Test vagrant, vagrant plugins and the vagrant boxes ## Reproducible Fails since (at least) Build [20240814](https://openqa.opensuse.org/tests/4403837) ## Expected result Last good: [20240813](https://openqa.opensuse.org/tests/4402156) (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 1

[Bug 1231176] New: segmentation fault in trace-cmd
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231176 Bug ID: 1231176 Summary: segmentation fault in trace-cmd Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: andrea.manzini(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- package version: # rpm -qai trace-cmd Name : trace-cmd Version : 3.2 Release : 2.1 Architecture: x86_64 Install Date: Mon Sep 30 17:36:48 2024 Group : Development/Tools/Debuggers Size : 1271417 License : GPL-2.0-only Signature : RSA/SHA512, Sat May 11 19:29:12 2024, Key ID 35a2f86e29b700a4 Source RPM : trace-cmd-3.2-2.1.src.rpm Build Date : Fri May 10 11:19:23 2024 Build Host : reproducible Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git Summary : Configuration tool for Ftrace Description : trace-cmd is a command-line tool for configuring Ftrace. Distribution: openSUSE Tumbleweed to reproduce the issue, trace functions from PID 1 (systemd) : # zypper in trace-cmd # trace-cmd start -p function -P 1 plugin 'function' *** buffer overflow detected ***: terminated Aborted (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230118] [SELinux] Select SELinux as default MAC in enforcing mode in the tumbleweed installer
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230118 https://bugzilla.suse.com/show_bug.cgi?id=1230118#c3 --- Comment #3 from Cathy Hu <cathy.hu(a)suse.com> --- openQA Job group change: https://github.com/os-autoinst/opensuse-jobgroups/pull/522 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230236] Opensuse 15.6 Tiger Lake-LP Smart Sound Technology Audio Controller no output
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230236 https://bugzilla.suse.com/show_bug.cgi?id=1230236#c19 --- Comment #19 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Chris Stephens from comment #12) > (In reply to Takashi Iwai from comment #11) > > OK, that's something always problematic in the past, I vaguely remember. > > > > At best, please report to the upstream SOF devs, e.g. > > https://github.com/thesofproject/linux/issues > > In case it's relevant: https://github.com/thesofproject/linux/issues/5174 This seems to be the issue of the old sof-firmware. You can install the latest one from OBS multimedia:libs repo: http://download.opensuse.org/repositories/multimedia:/libs/15.6/ Maybe I should push the new sof-firmware as a maintenance update for Leap 15.6, too. (Hopefully it won't break other things.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231127] New: SELinux: health-checker change causes denial
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231127 Bug ID: 1231127 Summary: SELinux: health-checker change causes denial 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fcrozat(a)suse.com, iforster(a)suse.com Target Milestone: --- Found By: --- Blocker: --- With https://github.com/openSUSE/health-checker/pull/21/files, health-checker calls rpm --verifydb with a custom lock path because /usr/ is not writable. The modified check fails now because SELinux blocks rpm from writing to /run/rpmdb: type=AVC msg=audit(1727697272.028:122): avc: denied { open } for pid=2368 comm="rpmdb" path="/run/rpmdb" dev="tmpfs" ino=2281 scontext=unconfined_u:unconfined_r:rpmdb_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_run_t:s0 tclass=file permissive=0 type=AVC msg=audit(1727697272.028:123): avc: denied { open } for pid=2368 comm="rpmdb" path="/run/rpmdb" dev="tmpfs" ino=2281 scontext=unconfined_u:unconfined_r:rpmdb_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_run_t:s0 tclass=file permissive=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1231155] "zypper -ps" should report haveged as a service
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231155 https://bugzilla.suse.com/show_bug.cgi?id=1231155#c1 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ndordea(a)gmail.com Flags| |needinfo?(ndordea(a)gmail.com | |) --- Comment #1 from Michael Andres <ma(a)suse.com> --- @Nick: We'd need to see the line(s) zypper reports and for the reported PID the content of the "/proc/PID/cgroup" file. If the cgroup file does not contain any "*/system.slice/*" entries, please add the cgroup file for the reported PPID as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1229061] Laptop that will only run Plasma/Wayland, not Plasma X11
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1229061 https://bugzilla.suse.com/show_bug.cgi?id=1229061#c7 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(marc@marcchamberl | |in.com) CC| |fvogt(a)suse.com --- Comment #7 from Fabian Vogt <fvogt(a)suse.com> --- Sep 28 15:43:01 marcslaptop sddm-helper[3048]: Starting: "/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\"" Sep 28 15:43:01 marcslaptop sddm-helper[3089]: Adding cookie to "/run/user/1000/xauth_WVbjKe" Sep 28 15:43:01 marcslaptop sddm[1701]: Session started Sep 28 15:43:01 marcslaptop sddm-helper[3048]: [PAM] Ended. Hm, apparently this fails for some reason, but I can't tell why. Just a wild guess: Does it work after uninstalling xf86-video-nouveau and xf86-video-nv and rebooting? If wayland works, modesetting works, so xorg should work without any HW specific drivers. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231167] Enable CONFIG_SCSI_UFS_QCOM for UFS support on QCOM platforms
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231167 https://bugzilla.suse.com/show_bug.cgi?id=1231167#c1 --- Comment #1 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Thanks, but I think this module will need to be added into initramfs too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219803] Lenovo Yoga 14APH8 headphones jack requires bass speaker to be full volume
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219803 https://bugzilla.suse.com/show_bug.cgi?id=1219803#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |agesen(a)cs.stanford.edu --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- *** Bug 1230887 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 1230887] unable to attain normal sound levels on headphone jack (super low levels only)
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230887 https://bugzilla.suse.com/show_bug.cgi?id=1230887#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. This is a known problem, see bsc#1219803. I'll have to work on the driver to apply some workaround. *** This bug has been marked as a duplicate of bug 1219803 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230279] Running rpi-eeprom-update gives error
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230279 https://bugzilla.suse.com/show_bug.cgi?id=1230279#c5 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Pull request accepted. Closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230149] PPC64LE: ioctl(LOOP_SET_BLOCK_SIZE) accepts values larger than pagesize
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230149 https://bugzilla.suse.com/show_bug.cgi?id=1230149#c10 --- Comment #10 from Coly Li <colyli(a)suse.com> --- (In reply to Jiri Slaby from comment #9) > (In reply to Coly Li from comment #8) > > > Tumbleweed sources from the stable branch, so 6.11. > > > Do we have a branch for Tumbleweed kernel? I don't see it in kernel-source. > > Yes, as noted above, the "stable" branch :). Thank you again :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230149] PPC64LE: ioctl(LOOP_SET_BLOCK_SIZE) accepts values larger than pagesize
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230149 https://bugzilla.suse.com/show_bug.cgi?id=1230149#c9 --- Comment #9 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Coly Li from comment #8) > > Tumbleweed sources from the stable branch, so 6.11. > Do we have a branch for Tumbleweed kernel? I don't see it in kernel-source. Yes, as noted above, the "stable" branch :). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230149] PPC64LE: ioctl(LOOP_SET_BLOCK_SIZE) accepts values larger than pagesize
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230149 https://bugzilla.suse.com/show_bug.cgi?id=1230149#c8 --- Comment #8 from Coly Li <colyli(a)suse.com> --- (In reply to Jiri Slaby from comment #7) > (In reply to Coly Li from comment #6) > > And for Tumbleweed kernel, it is always from Factory of the latest mainline > > kernel. Now I see the master branch is updated to 6.12-rc1, so I assume the > > fixing patch is included in Tumbleweed kernel already. > > Tumbleweed sources from the stable branch, so 6.11. I believe the commit is > not in 6.11 yet? (You didn't share the SHA and I don't see it in. Neither in > -next.) I meant the patches you addressed in comment #2 in upstream. Obviously I mentioned misleading one and thanks for you pointing out this. Do we have a branch for Tumbleweed kernel? I don't see it in kernel-source. Thanks. Coly Li -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231068] modprobe v4l2loopback: key rejected by service / opensuse i6.4.0-150600.23.22-default
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231068 https://bugzilla.suse.com/show_bug.cgi?id=1231068#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |obs(a)akr.yagii.de, | |tiwai(a)suse.com Flags| |needinfo?(obs(a)akr.yagii.de) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- I guess you enabled Secure Boot? Have you imported / deployed MOK for openSUSE properly? Otherwise a module built in OBS won't be loaded. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231167] Enable CONFIG_SCSI_UFS_QCOM for UFS support on QCOM platforms
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231167 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |afaerber(a)suse.com, | |andrea.porta(a)suse.com, | |ivan.ivanov(a)suse.com, | |stanimir.varbanov(a)suse.com, | |tiwai(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230149] PPC64LE: ioctl(LOOP_SET_BLOCK_SIZE) accepts values larger than pagesize
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230149 https://bugzilla.suse.com/show_bug.cgi?id=1230149#c7 --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Coly Li from comment #6) > And for Tumbleweed kernel, it is always from Factory of the latest mainline > kernel. Now I see the master branch is updated to 6.12-rc1, so I assume the > fixing patch is included in Tumbleweed kernel already. Tumbleweed sources from the stable branch, so 6.11. I believe the commit is not in 6.11 yet? (You didn't share the SHA and I don't see it in. Neither in -next.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230149] PPC64LE: ioctl(LOOP_SET_BLOCK_SIZE) accepts values larger than pagesize
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230149 https://bugzilla.suse.com/show_bug.cgi?id=1230149#c6 --- Comment #6 from Coly Li <colyli(a)suse.com> --- (In reply to Coly Li from comment #5) > (In reply to Avinesh Kumar from comment #4) > > Looks like this issue is being addressed in - > > https://lore.kernel.org/all/20240827081757.37646-1-liwang@redhat.com/ > > Thanks for the notice. After it is merged into upstream kernel, I will pick > it for necessary kernel(s). OK now they are in mainline kernel. I checked SLE15-SP6 we don't have the breaker commit fe3d508ba95b ("block: Validate logical block size in blk_validate_limits()"), so it is unnecessary to backport the fix at this moment. And for Tumbleweed kernel, it is always from Factory of the latest mainline kernel. Now I see the master branch is updated to 6.12-rc1, so I assume the fixing patch is included in Tumbleweed kernel already. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231067] X11:Drivers:Video:Redesign/nvidia-open-driver-G06-signed: Bug - driver does not function after kernel 6.10
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231067 https://bugzilla.suse.com/show_bug.cgi?id=1231067#c11 --- Comment #11 from pallas wept <pallaswept(a)proton.me> --- > No, NVIDIA claims 550.120 has fixed that issue. Sorry, I should have said, all of the *available* drivers. I mean to say, all the ones I could install from the oss, nvidia or cuda repos. I anticipate that it will be fixed in .120. > > With nvidia_drm.fbdev=1 in the kernel command line (and conf), boots into > > plasma, without corruption, but with 100% CPU usage and unusably slow > I guess you're now implicitely using > nvidia-drm modeset=0 nvidia_drm.fbdev=1 In this state, fbdev is added to stock, that is the only change. So, modeset=1 should be set by the conf file here. fbdev=1 should be set twice, once in boot command, once in conf file. This seems true, as with the 550 driver, I see the boot message that the param is not supported and has been ignored, twice. Note that the behaviour is different with fbdev=1 specified in both places, compared to specified only in the conf file. > 550 closed driver (nvidia repo) Unmodified is just like 560 > With nvidia_drm.fbdev=1 in the kernel command line (and conf), boots into > plasma, seems normal > This sounds unexpected. It is most unexpected. This is the real problem I am reporting here, the behaviour of the boot command and modprobe conf files seems inconsistent. I don't even know if it's limited to the nvidia packages. We just see it here, because of the fbdev bug in the driver. It's probably nothing, but it is potentially major, so I thought I should follow up. > Mabye you didn't run 'dracut -f' after changinge the config? In that scenario, I set the boot command with yast, and I'm fairly sure that rebuilds the initrd, as dracut would? I did not change the modprobe conf, just kept the stock modeset=1 fbdev=1 from the existing conf file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231166] New: The qemu translation is not being installed
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231166 Bug ID: 1231166 Summary: The qemu translation is not being installed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: heitormoreira(a)yahoo.com.br QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The qemu-lang package is not being installed together with the qemu package for users whose system is configured with some language that has translation provided. -- You are receiving this mail because: You are on the CC list for the bug.

1 0