Hello, In the Message; Subject : Re: VirtualBox Quits Message-ID : <8b1758d8-a758-930f-aaf0-62ffb5347b15@gmail.com> Date & Time: Mon, 26 Dec 2022 19:44:42 +1300 [RK] == Robin Klitscher <robin.klitscher@gmail.com> has written: [...] MN> > That is, in your system, VirtualBox failed to execute; MN> > MN> > UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: MN> > Screen 0 work area is actually resized to: 0x0 x 1920x1037 RK> Yes; my call for the graphical manager just quits halfway through without RK> logging error. The question becomes why? MN> > Your problem seems to originate from your system. RK> Sure. Would any of the other system logs be likely to throw light on what's RK> going wrong? If so, which? RK> > How about this? RK> > RK> > $ ldd /usr/lib/virtualbox/* | grep "not found" RK> > RK> > RK> Doesn't produce anything useful, really. Even as root, a long series of RK> warnings that "you do not have execution permission for <a given file> MN> Moreover, tt may be a kernel-derived problem. RK> Could be. But the CLI VBoxManage works OK. Yes, I am sure so..... As for me, I suspect it's around Qt5 (especially around Qt5Widgets). First, check the dependencies around Qt5Widgets. Next, check the version consistency of the libKF5 files. KDE apps are particularly sensitive to the combination of libKF5 files, and if even one of the versions is off, it may result in a core dump or abnormal behaviour. Good luck! Regards, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "A society bound by e-mail and mobile phones deprives us of the freedom to face ourselves and indulge our fantasies." -- Michael Crichton (Speech in Japan) --