April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220302] New: MComix smart scroll up doesn't work on wayland
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220302 Bug ID: 1220302 Summary: MComix smart scroll up doesn't work on wayland 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: piotrus3g(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20240223 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.5-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82SG System Version: IdeaPad 5 15ABA7 Issue description: When on wayland, smart scroll in MComix doesn't work as expected, as it's only possible to smart scroll down, but not up. Observed behavior: Default keyboard shortcut for smart scroll up (shift + space) does the same thing as smart scroll down (space). Expected behavior: Smart scroll down scrolls down, smart scroll up scrolls up. Additional information: On X11 smart scrolling works as expected. Other keyboard shortcuts that also use the shift key work properly on wayland and X11. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222156] After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c14 --- Comment #14 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. Makes sense. Thanks for feedback. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222214] New: [SlowRoll] Incorrect SHA sum for ISO current image
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222214 Bug ID: 1222214 Summary: [SlowRoll] Incorrect SHA sum for ISO current image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: bluedzins(a)wp.pl QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- http://download.opensuse.org/slowroll/iso/ There is Current ISO file and associated SHA sum file. However the sum file targets snapshot not Current. After changing the name within sum file, check is positive. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222214] [SlowRoll] Incorrect SHA sum for ISO current image
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222214 https://bugzilla.suse.com/show_bug.cgi?id=1222214#c1 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de Component|Installation |Other Assignee|yast2-maintainers(a)suse.de |screening-team-bugs(a)suse.de --- Comment #1 from Stefan Hundhammer <shundhammer(a)suse.com> --- This is clearly 100% not a problem of the installer. If you don't know, please follow the instructions on the "New Bug" page and select component "Other", NOT "Installation". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 Pinkernell <pinkernell(a)ph-heidelberg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pinkernell(a)ph-heidelberg.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221840] podman with pasta (passt) fails with apparmor
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221840 https://bugzilla.suse.com/show_bug.cgi?id=1221840#c15 --- Comment #15 from Stefano Brivio <sbrivio(a)redhat.com> --- (In reply to Danish Prakash from comment #14) > Thanks for the patch, even though I can invoke `pasta` without any errors, > I'm still getting the same permission denied error on the netns: > > > Couldn't open network namespace /proc/9080/ns/net: Permission denied > > Adding the following rule to usr.bin.passt doesn't help either: > > > /proc/@{pid}/ns/ r, That should be '/proc/@{pid}/ns/**', but anyway that's already covered by abstractions/pasta: @{PROC}/[0-9]*/ns/net r, # pasta_wait_for_ns(), @{PROC}/[0-9]*/ns/user r, # conf_pasta_ns() ...you should make sure that those rules are taken into account, though. > On the contrary, setting the two usr.bin.pas* profiles to complain mode, > things are back to normal so perhaps the rules are still not right? Definitely, it's an issue with AppArmor rules. Can you tail -f /var/log/audit/audit.log while you run 'pasta' and check what AppArmor is denying as you do that? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 https://bugzilla.suse.com/show_bug.cgi?id=1222186#c20 --- Comment #20 from Javier de San Pedro <javispedro(a)gmail.com> --- (In reply to Larry Rainey from comment #18) > You have to replace the one in /usr/lib/virtualbox/vboxdrv.sh with the one > in susepaste just running will not fix the issue - you have to vi new.sh > with the code in susepaste then chmod 755 new.sh, then sudo new.sh. If it > fixes your usb issue then move new.sh to /usr/lib/virtualbox/vboxdrv.sh > > I matched exactly how Oracle Virtualbox installed the device nodes. Regarding the /vbox/vboxdrvu permissions and owner, I agree: this is how Oracle installs things. However, I wouldn't do this change anyway because it just opens up some attack surface to users outside the vboxusr group. I also don't see why this would fix any vboxusb issue. The problem with vboxusb is because of these snippets: diff -u /usr/lib/virtualbox/vboxdrv.sh pastebin_vboxdrv.sh @@ -60,6 +60,10 @@ [ -r /etc/default/virtualbox ] && . /etc/default/virtualbox +chmod "${DEVICE_MODE}" /dev/vboxusb/ +chmod "${DEVICE_MODE}" /dev/vboxusb/* +chmod "${DEVICE_MODE}" /dev/vboxusb/*/* + begin_msg() { test -n "${2}" && echo "${SCRIPTNAME}: ${1}." This should be entirely removed. chmod /dev/vboxusb to 0660 just makes accessing this directory impossible for vboxuser users and _should not be needed at all_ since the VBoxCreateUsbNode.sh script works fine (and also require no patches). If this was for bug 1219766, we should never silently workaround it in the script, and rather fix it in systemd level (which to my knowledge has already been fixed). Also, regarding this other change: @@ -249,6 +254,20 @@ if grep -q usb_device /proc/devices; then mkdir -p -m 0750 /dev/vboxusb 2>/dev/null chown root:vboxusers /dev/vboxusb 2>/dev/null + + rm /dev/vboxnetctl + mknod -m 0660 /dev/vboxnetctl c 10 120 + # mknod -m 0660 /dev/vboxnetctl with major 10 and minor 120 + chown root:vboxusers /dev/vboxnetctl + rm /dev/vboxdrvu + mknod -m 0666 /dev/vboxdrvu c 10 121 + # mknod -m 0666 /dev/vboxdrvu with major 10 and minor 121 + chown root:root /dev/vboxdrvu 2>/dev/null + rm /dev/vboxdrv + mknod -m 0660 /dev/vboxdrv c 10 122 + # mknod -m 0660 /dev/vboxdrv with major 10 and minor 122 + chown root:vboxusers /dev/vboxdrv 2>/dev/null + fi succ_msg "VirtualBox services started" } This is dangerous. (misc) minors can be assigned dynamically and may be different between different sessions. But I just can't see how this can be possibly related to USB, unless we are merging multiple issues here. Can't we do just something like https://build.opensuse.org/package/rdiff/home:javispedro:branches:Virtualiz… to remove these vboxusb workarounds? For me at least it fixes the issue. I would be submitting a request, but I can't get OBS to cooperate today (it fails to publish my packages due to requiring a SSL certificate, the first time I see this). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 https://bugzilla.suse.com/show_bug.cgi?id=1222186#c19 --- Comment #19 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- I just use "diff -u", but if you want a decent diff-gui "kompare" or "kdiff" are not bad (KDE of course). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 https://bugzilla.suse.com/show_bug.cgi?id=1222186#c17 --- Comment #17 from T Adams <timothyadams(a)ymail.com> --- >After a reboot, I have to run again > /usr/lib/virtualbox/vboxdrv.sh restart Thanks, Claudio. I did try this, but without effect on the enumeration error. I fear I'm not competent enough to do extensive editing of these configuration files, will wait until you more knowledgeable openSUSErs find a fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222183] pcr-oracle fails to parse LOADER_CONF_EVENT_TAG_ID
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222183 https://bugzilla.suse.com/show_bug.cgi?id=1222183#c2 --- Comment #2 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Andrei Borzenkov from comment #0) > Apart from the obvious bug in pcr-oracle, this invalidates any claim of > "immutability" of MicroOS - failed update makes it impossible to boot > MicroOS without human intervention. Also comment here that the ESP, /etc and /var are outside of the transaction. This bug is a very interesting case where a side effect (the update of the boot loader) affect all the transactions at the same time: the new boot loader is visible for all the snapshots. We are thinking how to fix this. One option can be that when doing a rollback, recover the old boot loader from the snapshot. This is the correct approach in general, but if the user select an old snapshot from the boot loader, it is still using the most updated one. -- You are receiving this mail because: You are on the CC list for the bug.

1 0