July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220524] New: Files in virtualbox shared folder (on the guest) show wrong timestamp
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220524 Bug ID: 1220524 Summary: Files in virtualbox shared folder (on the guest) show wrong timestamp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: suse.junky(a)t-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On my openSUSE Tumbleweed system (bare metal) Operating System: openSUSE Tumbleweed 20240225 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.6-1-default (64-bit) Graphics Platform: X11 I use virtualbox # zypper se -si virtual* Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------------+---------+-----------------------+--------+------------------ i | virtualbox | package | 7.0.14-3.1 | x86_64 | (System Packages) i+ | virtualbox-kmp-default | package | 7.0.14_k6.7.6_1-3.2 | x86_64 | (System Packages) i+ | virtualbox-qt | package | 7.0.14-3.1 | x86_64 | (System Packages) # One guest is an openSUSE Tumbleweed 20240225 system with # zypper se -si virtualbox* Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------------+---------+---------------------+--------+------------------ i+ | virtualbox-guest-tools | package | 7.0.14-3.1 | x86_64 | (System Packages) i+ | virtualbox-kmp-default | package | 7.0.14_k6.7.6_1-3.2 | x86_64 | (System Packages) # The host shares a directory (/mnt/Lokal/VM_share) with the guest. On the host system I have (in my home directory) a file > ls -la *.jpg -rw-r--r-- 1 A users 40749 Mar 3 2023 Opensuse_beer_label.jpg when I copy this file to the shared directory > cp -a Opensuse_beer_label.jpg /mnt/Lokal/VM_share/ everything looks fine (on the host) > ls -la /mnt/Lokal/VM_share/ total 64 drwxr-xr-x 3 A users 4096 Feb 27 09:51 . drwxr-xr-x 7 root root 4096 Jan 3 2022 .. -rw-r--r-- 1 A users 40749 Mar 3 2023 Opensuse_beer_label.jpg > but on the guest system I see in the shared folder > ls -la total 64 drwxrwx--- 1 root vboxsf 4096 Jan 1 1970 . dr-xr-xr-x 5 root root 4096 Feb 27 09:40 .. -rwxrwx--- 1 root vboxsf 40749 Feb 27 09:44 Opensuse_beer_label.jpg > The timestamps in the share of the VM don’t make sense to me. This happens to all files copied to the share. Even when I copy files in the guest to the share their timestamps are changed (in the share) to the current date . However when I look at those files on the host they do have the correct date; i.e. the date of the original file in the guest. On MS Windows 11 (bare metal) with virtualbox 7.0.14 and openSUSE Tumbleweed 20240225 as guest I see the same behaviour. Kubuntu (as guest) does not show this behaviour although it uses VBoxGuestAdditions_7.0.14 as well. I discussed this already here: https://forums.opensuse.org/t/files-in-the-virtualbox-share-show-wrong-time… and a third user could very this behaviour in its setup as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1217824] New: longterm kernel: figure out how to build KMPs
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1217824 Bug ID: 1217824 Summary: longterm kernel: figure out how to build KMPs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: rfrohl(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tiwai(a)suse.com Target Milestone: --- Found By: --- Blocker: --- One of the major open questions, before introducing the longterm kernel to Factory, is how KPMs can be build. This issue is supposed to server as a reminder, that this likely blocks the addition to Factory until it is resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215463] New: VirtualBox shared folders no longer working in Tumbleweed 20230915
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215463 Bug ID: 1215463 Summary: VirtualBox shared folders no longer working in Tumbleweed 20230915 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: nixuser(a)linuxmail.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent updates in the last two week or so have broken shared folders in VirtualBox. You can mount the shares, and "ls" the files, but any attempt to access a file results in "killed" as a response. If I launch Thunar in Xfce it locks up and must be killed. Video scaling is working, and copy/paste between the host and guest are also working. Issue exists for Tumbleweed guests with a Fedora or Win10 host. Other hosts not tested. Tumbleweed guest fully up to date 20230915. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1226347] New: display-manager.service unconditionally overwrites /etc/vconsole.conf on start
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1226347 Bug ID: 1226347 Summary: display-manager.service unconditionally overwrites /etc/vconsole.conf on start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: srid(a)rkmail.ru QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When display-manager.service starts, it unconditionally overwrites console configuration in /etc/vconsole.conf. display-manager.service is a part of 'xdm' package. It contains a script /etc/X11/xdm/keytable, which is run at service start. The script unconditionally changes system locale according to KEYMAP setting in /etc/vconsole.conf. This is not an acceptable behavior! For various reasons, user might want to have different values for KEYMAP and XKBLAYOUT. And sometimes, the preferred KEYMAP would not have an XKB counterpart leaving user without XKB settings at all. In my opinion, the keytable script should not unconditionally touch system configuration. What happens now: 1. The keytable script looks for /etc/vconsole. If it exists, it reads $KEYMAP and $KEYMAP_TOGGLE variables 2. Then it looks for /etc/X11/xorg.conf.d/00-keyboard.conf file. If this file does not exist, it calls 'localectl set-x11keymap us', which results in overwriting both $KEYMAP and $XKBLAYOUT variables in /etc/vconsole.conf, as localectl does automatic conversion of layout settings. 3. Then, it checks if previously stored $KEYMAP has a matching XKB layout in /us/share/systemd/kbd-model-map, but takes no action other than informing user with messages. 4. It calls 'localectl set-keymap $KEYMAP $KEYMAP_TOGGLE', overwriting /etc/vconsole.conf once more. 5. Last thing, script checks if /etc/X11/xorg.conf.d/00-keyboard.conf has appeared, and if it does not, it gives a warning. To me, all above makes no sense. I have no idea why we need this script at all. I believe, something like this should happen: 1. Script checks if /etc/X11/xorg.conf.d/00-keyboard.conf exists. If it is there, take no action and exit peacefully. It's not our business if the user has incorrect/inconsistent keyboard configuration. 2. If 00-keyboard.conf does not exist, script should check /etc/vconsole.conf for $XKBLAYOUT. If $XKBLAYOUT exists, it should be poke localectl with 'localectl --no-convert $XKBLAYOUT $XKBMODEL $XKBVARIANT $XKBOPTIONS' to generate new 00-keyboard.conf. Ideally, localectl should have an option to just touch XOrg config, without making changes to vconsole.conf. 3. If $XKBLAYOUT does not exists, or is empty, etc, it *might* be intentional, give a warning and let XOrg to start without 00-keyboard.conf file at all. I believe it should default to 'US' layout anyway. On the other hand, the Tumbleweed XDM package contains no such script at all, and everything continues to work if I delete it on Leap 15.6 manually. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227200] New: kdeconnect crashes after upgrading to Leap:15.6
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1227200 Bug ID: 1227200 Summary: kdeconnect crashes after upgrading to Leap:15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: davejplater(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875777 --> https://bugzilla.suse.com/attachment.cgi?id=875777&action=edit KDE crash trace back I already had kdeconnect running when my system was Leap:15.5 but after doing a zypper dup --allow-vendor change with only Main repository and dvd enabled, whenever my phone with kdeconnect installed tries to connect kdeconnect on my pc apparently crashes. I've installed updates and removed any packages that have lp155 then restored the unrestricted packages I had before it's still the same. I've tried gdb on kdeconnectd but when the unhappy face appears on the taskbar about eight times it simply says process exited normally. I'll attach the kde crash trace but I can't fathom anything from it. Surprisingly nobody else has filed a bug. to get the crash I open kdeconnect on my phone (same version as before) and it crashes continually. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1221763] New: ptrace(PTRACE_ATTACH) fails on processes of the same user
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1221763 Bug ID: 1221763 Summary: ptrace(PTRACE_ATTACH) fails on processes of the same user Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: giuliano.belinassi(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent updates of tumbleweed broke `ptrace(PTRACE_ATTACH, ...)` when attaching to a process from the same user. This breaks attaching a debugger (gdb) to a process and userspace livepatching. A single line reproducer in a clean system is: ``` $ sleep 5000 & gdb -p $(pidof sleep) ``` If you see the following message: ``` Attaching to process 12606 ptrace: Operation not permitted. ``` This means ptrace is not working. As a contrast, running gdb with sudo works as intended. Value of /proc/sys/kernel/yama/ptrace_scope: ``` $ cat /proc/sys/kernel/yama/ptrace_scope 1 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 40

[Bug 1225142] New: Kernel oops in nfs
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225142 Bug ID: 1225142 Summary: Kernel oops in nfs Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msvec(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875055 --> https://bugzilla.suse.com/attachment.cgi?id=875055&action=edit Kernel oops log As I already mentioned in bug 1223640 I'm getting oops in NFS (see the attached log) It happens in both kernel-default-5.14.21-150500.55.59.1.x86_64 kernel-default-5.14.21-150500.55.62.2.x86_64 Until and including the previous one it's been fine: kernel-default-5.14.21-150500.55.52.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215976] New: Hawk fails to build in Factory
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215976 Bug ID: 1215976 Summary: Hawk fails to build in Factory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: aburlakov(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After the update in the Factory, there has disappeared the useradd and groupadd commands. Adding the shadow package in the BuildRequires has fixed it. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1220891] New: HAWK: Update sanity check for passwd existance
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220891 Bug ID: 1220891 Summary: HAWK: Update sanity check for passwd existance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: aburlakov(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The /etc/pam.d/passwd is optional in fact, for example there is none in the tumbleeweed. So let's relax the condition: if there is no /etc/pam.d/passwd, check if there is a passwd binary in /usr/bin of /usr/sbin. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1220890] New: Update validation for the newer versions of rails
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220890 Bug ID: 1220890 Summary: Update validation for the newer versions of rails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: aburlakov(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with Rails6.1 there has changed the validation. Namely, the ActiveModel::Errors has changed it's structure. -- You are receiving this mail because: You are on the CC list for the bug.

1 2