On 26/12/2022 00:15, Carlos E. R. wrote:

<snip>

Well, the information is in that coredump, for use by developers.

You can run "coredumpctl" to see them.

TIME PID UID GID SIG COREFILE EXE SIZE Sun 2022-10-02 22:38:27 CEST 5704 1000 100 SIGSEGV missing /usr/lib/xfce4/panel/wrapper-2.0 n/a Mon 2022-10-03 11:57:33 CEST 5705 1000 100 SIGABRT missing /usr/lib/xfce4/panel/wrapper-2.0 n/a ... Thu 2022-12-22 14:53:47 CET 6942 1000 100 SIGSEGV present /usr/bin/xfce4-terminal 5.5M Fri 2022-12-23 00:10:51 CET 25259 1000 100 SIGBUS present /usr/lib64/tumbler-1/tumblerd 3.0M lines 561-582/582 (END)

Telcontar:~ # coredumpctl info 25259

gives information on that event, but it is basically useless to us mere mortals.

coredumpctl as su returns "No coredumps found". But as you say that probably doesn't matter because I wouldn't understand it anyway! -- Robin K Wellington "Harbour City" New Zealand

On 26/12/2022 11:12, Carlos E. R. wrote:

On 2022-12-25 22:51, Robin Klitscher wrote:

<snip>.

...

...

coredumpctl as su returns "No coredumps found".  But as you say that probably doesn't matter because I wouldn't understand it anyway!

Ah. maybe you need the systemd-coredump package ?  No, impossible, you would not then have the coredumpctl program. Must be something else. maybe you have coredumps disabled.

Yes, it is only of use to developers.

Just for the record: ~> rpm -qa | grep coredump systemd-coredump-249.12-150400.8.13.1.x86_64 -- Robin K Wellington "Harbour City" New Zealand

On 26/12/2022 10:05, Bengt Gördén wrote:

Maybe this?

From Reddit: I had the same problem, with VirtualBox 7.0.2 running under macOS Ventura on a MacBook Pro 16 (2019) and Windows 11 (22H2) as guest. My **workaround** is **manually setting the virtual graphics controller to VBoxVGA** (instead of VBoxSVGA).

https://www.reddit.com/r/virtualbox/comments/yh4dad/windows_11_guest_os_keep...

<snip> Could be possible, but because the several registered VMs still work when called individually from the commandline VBoxManage utility, I'd infer that I may be looking at a system error in Qt(?) rather than something to do with the VirtualBox GUI manager in isolation. So I'll hold off on your suggestion meantime. But thanks for the trouble anyway. -- Robin K Wellington "Harbour City" New Zealand

On 26/12/2022 13:06, Masaru Nomiya wrote:

Hello,

<snip>

Robin, please show us the selectorwindow.log (which　is　 in　~/.VirtualBox) when the problem occurred.

BEGINS 00:00:00.375408 VirtualBox GUI VM Selector Window 7.0.4_SUSE r154605 linux.amd64 (no date no time) release log 00:00:00.375410 Log opened 2022-12-26T01:15:19.040872000Z 00:00:00.375410 Build Type: release 00:00:00.375412 OS Product: Linux 00:00:00.375413 OS Release: 5.14.21-150400.24.38-default 00:00:00.375413 OS Version: #1 SMP PREEMPT_DYNAMIC Fri Dec 9 09:29:22 UTC 2022 (e9c5676) 00:00:00.375429 DMI Product Name: Z490 VISION G 00:00:00.375432 DMI Product Version: -CF 00:00:00.375436 Firmware type: UEFI 00:00:00.375552 Secure Boot: Disabled 00:00:00.375575 Host RAM: 32028MB (31.2GB) total, 27106MB (26.4GB) available 00:00:00.375578 Executable: /usr/lib/virtualbox/VirtualBox6 00:00:00.375578 Process ID: 12355 00:00:00.375578 Package type: LINUX_64BITS_GENERIC (OSE) 00:00:00.375594 Qt version: 5.15.7 00:00:00.375902 GUI: UIMediumEnumerator: Initial medium-enumeration finished! 00:00:00.404356 GUI: UIMediumEnumerator: Medium-enumeration started... ENDS The Secure Boot line looks a bit odd. When the GUI manager was working Secure Boot was marked as enabled - which as I understand it must have been the case for Win 11 to install at all, let alone to work properly when called from the command line with VBoxManage startvm <name> (although, on inspection after starting one of the Win 11 VMs with VBoxManage I see the related VBoxSVC log also says Secure Boot is disabled, so maybe it doesn't matter). -- Robin K Wellington "Harbour City" New Zealand

Hello, In the Message; Subject : Re: VirtualBox Quits Message-ID : <7329f20d-2724-cae1-0535-9b011f7672d9@gmail.com> Date & Time: Mon, 26 Dec 2022 14:35:44 +1300 [RK] == Robin Klitscher has written: RK> On 26/12/2022 13:06, Masaru Nomiya wrote: RK> > Hello, RK> > RK> <snip> RK> > RK> > Robin, please show us the selectorwindow.log (which　is　 RK> > in　~/.VirtualBox) when the problem occurred. RK> > RK> > RK> BEGINS RK> 00:00:00.375408 VirtualBox GUI VM Selector Window 7.0.4_SUSE r154605 linux.amd64 RK> (no date no time) release log RK> 00:00:00.375410 Log opened 2022-12-26T01:15:19.040872000Z RK> 00:00:00.375410 Build Type: release RK> 00:00:00.375412 OS Product: Linux RK> 00:00:00.375413 OS Release: 5.14.21-150400.24.38-default RK> 00:00:00.375413 OS Version: #1 SMP PREEMPT_DYNAMIC Fri Dec 9 09:29:22 UTC 2022 RK> (e9c5676) RK> 00:00:00.375429 DMI Product Name: Z490 VISION G RK> 00:00:00.375432 DMI Product Version: -CF RK> 00:00:00.375436 Firmware type: UEFI RK> 00:00:00.375552 Secure Boot: Disabled RK> 00:00:00.375575 Host RAM: 32028MB (31.2GB) total, 27106MB (26.4GB) available RK> 00:00:00.375578 Executable: /usr/lib/virtualbox/VirtualBox6 RK> 00:00:00.375578 Process ID: 12355 RK> 00:00:00.375578 Package type: LINUX_64BITS_GENERIC (OSE) RK> 00:00:00.375594 Qt version: 5.15.7 RK> 00:00:00.375902 GUI: UIMediumEnumerator: Initial medium-enumeration finished! RK> 00:00:00.404356 GUI: UIMediumEnumerator: Medium-enumeration started... RK> ENDS [...] Thanks. BTW, what's this? RK> 00:00:00.375578 Executable: /usr/lib/virtualbox/VirtualBox6 You're trying to use the version 6.x's VirtualBox binary? In may case; 00:00:06.259444 Executable: /usr/lib/virtualbox/VirtualBox Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "A bachelor’s degree still holds prestige as a ticket to the middle class, but its value has received increasing scrutiny. In the last several years, rising tuition and student loan debt have led more Americans to reconsider an investment in postsecondary education." -- Washington Post --

Hello, Sorry for late reply. In the Message; Subject : Re: VirtualBox Quits Message-ID : <537d0ac9-d5bf-0c73-ab30-2d926cb7d4ce@gmail.com> Date & Time: Mon, 26 Dec 2022 15:42:42 +1300 [RK] == Robin Klitscher has written: RK> On 26/12/2022 15:12, Masaru Nomiya wrote: MN> > Hello, MN> > MN> <snipped> MN> > MN> > BTW, what's this? MN> > MN> > MN> 00:00:00.375578 Executable: /usr/lib/virtualbox/VirtualBox6 MN> > MN> > You're trying to use the version 6.x's VirtualBox binary? MN> > MN> > In may case; MN> > MN> > 00:00:06.259444 Executable: /usr/lib/virtualbox/VirtualBox MN> > RK> I wondered about that too, and re-installed (update unconditional) the three RK> virtualbox packages in Yast, but to no effect. RK> In my system /usr/lib/virtualbox/VirtualBox is a symlink pointing to the RK> executable VirtualBoxVM. /usr/lib/virtualbox/VirtualBox6 is a RK> raw executable. RK> Both of them appear to have come from the package virtualbox-qt ver RK> 7.0.4-lp154.2.20.2 Sorry, I confirmed it. Another question. In your log; [...] 00:00:00.375594 Qt version: 5.15.7 00:00:00.375902 GUI: UIMediumEnumerator: Initial medium-enumeration finished! 00:00:00.404356 GUI: UIMediumEnumerator: Medium-enumeration started... but, in my log; 00:00:00.295652 Qt version: 5.15.7 00:00:00.296416 GUI: UIMediumEnumerator: Initial medium-enumeration finished! 00:00:00.314027 GUI: UIMediumEnumerator: Medium-enumeration started... 00:00:00.787007 GUI: UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x0 x 1920x1037 00:00:00.874360 GUI: UIMediumEnumerator: Medium-enumeration finished! 00:00:08.151981 GUI: UIMediumEnumerator: Medium-enumeration finished! 00:00:11.047878 GUI: UIMediumEnumerator: Medium-enumeration finished! 00:00:19.146880 GUI: UIMediumEnumerator: Medium-enumeration finished! 00:02:07.130392 GUI: UICommon: Handling aboutToQuit request.. 00:02:08.135623 GUI: UICommon: aboutToQuit request handled! That is, in your system, VirtualBox failed to execute; UIDesktopWidgetWatchdog::sltHandleHostScreenAvailableGeometryCalculated: Screen 0 work area is actually resized to: 0x0 x 1920x1037 Your problem seems to originate from your system. How about this? $ ldd /usr/lib/virtualbox/* | grep "not found" Moreover, tt may be a kernel-derived problem. In the Message; Subject : VirtualBox Quits Message-ID : <53b45d31-d22a-f1c0-2201-d7e3da9f26d5@gmail.com> Date & Time: Sun, 25 Dec 2022 20:34:36 +1300 [RK] == Robin Klitscher has written: RK> openSUSE Leap 15.4 RK> KDE Plasma Version: 5.26.4 RK> KDE Frameworks Version: 5.101.0 RK> Qt Version: 5.15.7 RK> Kernel Version: 5.14.21-150400.24.38-default (64-bit) RK> VirtualBox 7.0.4. Does anyone else have VirtualBox 7.0.4 in the same environment as Robin without problems? Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "The question of who holds the platform and whether the person or organisation holding it is trustworthy has serious and profound implications in these volatile times. Once trust is broken, it is extremely difficult to restore. It is necessary to diversify in advance." -- Financial Times --

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 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) --

On 26/12/2022 20:55, Robin Klitscher wrote:

On 26/12/2022 20:10, Masaru Nomiya wrote:

<..........>

...

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,

Thank you again.  I'll do some thinking on it.  I'd earlier thought that I might have to wait for the next update of Qt5 stuff.

Whatever the problem was, happy to say that today's update of VirtualBox 7.0.4 has fixed it ..... -- Robin K Wellington "Harbour City" New Zealand