You are not logged in.
VirtualBox crashes when I click on an ISO file to load using the VBox GUI.
I use Arch with a KDE Plasma DE on Wayland as the host OS.
Here's what I've tried so far:
- downgrade VBox to 7.10 (which used to worked properly, and now it does not)
- enabled/disabled 3D acceleration
- used virtualbox-host-modules-lts (I'm using the LTS kernel package because I use the Linux LTS kernel)
Just to state, I did not have to encounter this problem before upgrading to Plasma 6 or upgrading to VBox 7.12, so I do not know when it might have started. Maybe it could be an issue related to either. It does state libmpv is being called, and that is facing an issue.
Below is the output for
journalctl | grep -i virtualboxJul 24 10:56:33 archlinux kernel: VirtualBox[10765]: segfault at 48 ip 000077b7515197f0 sp 00007ffe6c5889e0 error 4 in libmpv.so.2.5.0[1197f0,77b75141c000+177000] likely on CPU 3 (core 3, socket 0)
Jul 24 10:56:33 archlinux systemd-coredump[10871]: Process 10765 (VirtualBox) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Jul 24 10:56:34 archlinux systemd-coredump[10872]: Process 10765 (VirtualBox) of user 1000 dumped core.
Jul 24 10:56:34 archlinux drkonqi-coredump-processor[10873]: "/usr/lib/virtualbox/VirtualBox" 10765 "/var/lib/systemd/coredump/core.VirtualBox.1000.fd8fdb4450444aed8ddd3ea08f20a28f.10765.1753334793000000.zst"
Jul 24 10:56:34 archlinux drkonqi-coredump-launcher[10907]: Unable to find file for pid 10765 expected at "kcrash-metadata/VirtualBox.fd8fdb4450444aed8ddd3ea08f20a28f.10765.ini"Just to add, I am able to use VMs that are already installed without an issue.
Where can I look to fix this?
Last edited by tyrobro31 (2025-07-25 04:36:55)
Offline
Moving to Applications & Desktop Environments as requested by forum mail.
Next time please use the report button (bottom right) to send a message to all moderators.
Welcome to archlinux forums.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline