Bug 5383

Can you report a full stacktrace and attach the output to this bug?
https://fedoraproject.org/wiki/StackTraces

After run and crash VirtualBox the abrt nothing to do.
After: ```gdb VirtualBox```
GNU gdb (GDB) Fedora 8.3.50.20190824-24.fc31
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/usr/bin/VirtualBox": not in executable format: file format not recognized
(gdb) run
Starting program:  
No executable file specified.
Use the "file" or "exec-file" command.
(gdb)

(In reply to flash2071 from comment #2)
> After run and crash VirtualBox the abrt nothing to do.
>

Can't reproduce or just works for me but please try [1] Thanks

[1] 
gdb /usr/lib64/virtualbox/VirtualBox
run

Created attachment 2085 [details]
gdb trace log

Created attachment 2086 [details]
trace of strace

```strace -o ~/trace.log /usr/lib64/virtualbox/VirtualBox```

P.S. i did ```gzip trace.log``` because  file trace.log was too big

(In reply to flash2071 from comment #4)
> Created attachment 2085 [details]
> gdb trace log

to have an useful logm you need install all debuginfos [1] as gdb wrote , this may need several Gigas bytes of sapce and it will download almost one giga bytes , if internet and disk space is not a problem , please try it .

Thanks,

[1]
dnf debuginfo-install GConf2-3.2.6-27.fc31.x86_64 adwaita-qt5-1.1.0-4.fc31.x86_64 at-spi2-atk-2.34.0-1.fc31.x86_64 at-spi2-core-2.34.0-1.fc31.x86_64 atk-2.34.1-1.fc31.x86_64 brotli-1.0.7-6.fc31.x86_64 bzip2-libs-1.0.8-1.fc31.x86_64 cairo-1.16.0-6.fc31.x86_64 cairo-gobject-1.16.0-6.fc31.x86_64 cyrus-sasl-lib-2.1.27-2.fc31.x86_64 dbus-glib-0.110-6.fc31.x86_64 dbus-libs-1.12.16-3.fc31.x86_64 dconf-0.34.0-1.fc31.x86_64 elfutils-libelf-0.177-1.fc31.x86_64 expat-2.2.8-1.fc31.x86_64 fontconfig-2.13.92-3.fc31.x86_64 freetype-2.10.0-3.fc31.x86_64 fribidi-1.0.5-4.fc31.x86_64 gdk-pixbuf2-2.39.2-1.fc31.x86_64 glib2-2.62.0-1.fc31.x86_64 gtk3-3.24.11-1.fc31.x86_64 harfbuzz-2.6.0-1.fc31.x86_64 jasper-libs-2.0.14-9.fc31.x86_64 jbigkit-libs-2.1-17.fc31.x86_64 keyutils-libs-1.6-3.fc31.x86_64 krb5-libs-1.17-40.fc31.x86_64 lcms2-2.9-6.fc31.x86_64 libX11-1.6.8-3.fc31.x86_64 libX11-xcb-1.6.8-3.fc31.x86_64 libXau-1.0.9-2.fc31.x86_64 libXcomposite-0.4.4-17.fc31.x86_64 libXcursor-1.1.15-6.fc31.x86_64 libXext-1.3.4-2.fc31.x86_64 libXfixes-5.0.3-10.fc31.x86_64 libXi-1.7.10-2.fc31.x86_64 libXinerama-1.1.4-4.fc31.x86_64 libXrandr-1.5.2-2.fc31.x86_64 libXrender-0.9.10-10.fc31.x86_64 libcurl-7.66.0-1.fc31.x86_64 libdatrie-0.2.9-10.fc31.x86_64 libedit-3.1-28.20190324cvs.fc31.x86_64 libepoxy-1.5.3-4.fc31.x86_64 libffi-3.1-23.fc31.x86_64 libgcc-9.2.1-1.fc31.x86_64 libgcrypt-1.8.5-1.fc31.x86_64 libglvnd-1.1.1-5.fc31.x86_64 libglvnd-glx-1.1.1-5.fc31.x86_64 libgpg-error-1.36-2.fc31.x86_64 libicu-63.2-3.fc31.x86_64 libidn2-2.2.0-2.fc31.x86_64 libjpeg-turbo-2.0.2-4.fc31.x86_64 libmng-2.0.3-10.fc31.x86_64 libmount-2.34-3.fc31.x86_64 libnghttp2-1.39.2-1.fc31.x86_64 libpng-1.6.37-2.fc31.x86_64 libpsl-0.21.0-2.fc31.x86_64 libselinux-2.9-5.fc31.x86_64 libstdc++-9.2.1-1.fc31.x86_64 libthai-0.1.28-3.fc31.x86_64 libunistring-0.9.10-6.fc31.x86_64 libwayland-client-1.17.0-2.fc31.x86_64 libwayland-cursor-1.17.0-2.fc31.x86_64 libwayland-server-1.17.0-2.fc31.x86_64 libwebp-1.0.3-2.fc31.x86_64 libxcb-1.13.1-3.fc31.x86_64 libxcrypt-4.4.9-1.fc31.x86_64 libxkbcommon-0.8.4-2.fc31.x86_64 libxml2-2.9.9-3.fc31.x86_64 libxshmfence-1.3-5.fc31.x86_64 lz4-libs-1.9.1-1.fc31.x86_64 mesa-libgbm-19.2.0~rc3-1.fc31.x86_64 mesa-libglapi-19.2.0~rc3-1.fc31.x86_64 ncurses-libs-6.1-12.20190803.fc31.x86_64 openldap-2.4.47-3.fc31.x86_64 openssl-libs-1.1.1d-1.fc31.x86_64 pango-1.44.6-1.fc31.x86_64 pcre2-10.33-14.fc31.x86_64 pcre2-utf16-10.33-14.fc31.x86_64 qgnomeplatform-0.5-13.fc31.x86_64 qt5-qtbase-5.12.4-7.fc31.x86_64 qt5-qtbase-gui-5.12.4-7.fc31.x86_64 qt5-qtimageformats-5.12.4-2.fc31.x86_64 qt5-qtwayland-5.12.4-7.fc31.x86_64 qt5-qtx11extras-5.12.4-2.fc31.x86_64 systemd-libs-243-1.fc31.x86_64 xz-libs-5.2.4-6.fc31.x86_64 zlib-1.2.11-19.fc31.x86_64

(In reply to Sérgio Basto from comment #6)
> (In reply to flash2071 from comment #4)
> > Created attachment 2085 [details]
> > gdb trace log
> 
> to have an useful logm you need install all debuginfos [1] as gdb wrote ,
> this may need several Gigas bytes of sapce and it will download almost one
> giga bytes , if internet and disk space is not a problem , please try it .
> 
> Thanks,
> 
> [1]
> dnf debuginfo-install GConf2-3.2.6-27.fc31.x86_64
> adwaita-qt5-1.1.0-4.fc31.x86_64 at-spi2-atk-2.34.0-1.fc31.x86_64
> at-spi2-core-2.34.0-1.fc31.x86_64 atk-2.34.1-1.fc31.x86_64
> brotli-1.0.7-6.fc31.x86_64 bzip2-libs-1.0.8-1.fc31.x86_64
> cairo-1.16.0-6.fc31.x86_64 cairo-gobject-1.16.0-6.fc31.x86_64
> cyrus-sasl-lib-2.1.27-2.fc31.x86_64 dbus-glib-0.110-6.fc31.x86_64
> dbus-libs-1.12.16-3.fc31.x86_64 dconf-0.34.0-1.fc31.x86_64
> elfutils-libelf-0.177-1.fc31.x86_64 expat-2.2.8-1.fc31.x86_64
> fontconfig-2.13.92-3.fc31.x86_64 freetype-2.10.0-3.fc31.x86_64
> fribidi-1.0.5-4.fc31.x86_64 gdk-pixbuf2-2.39.2-1.fc31.x86_64
> glib2-2.62.0-1.fc31.x86_64 gtk3-3.24.11-1.fc31.x86_64
> harfbuzz-2.6.0-1.fc31.x86_64 jasper-libs-2.0.14-9.fc31.x86_64
> jbigkit-libs-2.1-17.fc31.x86_64 keyutils-libs-1.6-3.fc31.x86_64
> krb5-libs-1.17-40.fc31.x86_64 lcms2-2.9-6.fc31.x86_64
> libX11-1.6.8-3.fc31.x86_64 libX11-xcb-1.6.8-3.fc31.x86_64
> libXau-1.0.9-2.fc31.x86_64 libXcomposite-0.4.4-17.fc31.x86_64
> libXcursor-1.1.15-6.fc31.x86_64 libXext-1.3.4-2.fc31.x86_64
> libXfixes-5.0.3-10.fc31.x86_64 libXi-1.7.10-2.fc31.x86_64
> libXinerama-1.1.4-4.fc31.x86_64 libXrandr-1.5.2-2.fc31.x86_64
> libXrender-0.9.10-10.fc31.x86_64 libcurl-7.66.0-1.fc31.x86_64
> libdatrie-0.2.9-10.fc31.x86_64 libedit-3.1-28.20190324cvs.fc31.x86_64
> libepoxy-1.5.3-4.fc31.x86_64 libffi-3.1-23.fc31.x86_64
> libgcc-9.2.1-1.fc31.x86_64 libgcrypt-1.8.5-1.fc31.x86_64
> libglvnd-1.1.1-5.fc31.x86_64 libglvnd-glx-1.1.1-5.fc31.x86_64
> libgpg-error-1.36-2.fc31.x86_64 libicu-63.2-3.fc31.x86_64
> libidn2-2.2.0-2.fc31.x86_64 libjpeg-turbo-2.0.2-4.fc31.x86_64
> libmng-2.0.3-10.fc31.x86_64 libmount-2.34-3.fc31.x86_64
> libnghttp2-1.39.2-1.fc31.x86_64 libpng-1.6.37-2.fc31.x86_64
> libpsl-0.21.0-2.fc31.x86_64 libselinux-2.9-5.fc31.x86_64
> libstdc++-9.2.1-1.fc31.x86_64 libthai-0.1.28-3.fc31.x86_64
> libunistring-0.9.10-6.fc31.x86_64 libwayland-client-1.17.0-2.fc31.x86_64
> libwayland-cursor-1.17.0-2.fc31.x86_64
> libwayland-server-1.17.0-2.fc31.x86_64 libwebp-1.0.3-2.fc31.x86_64
> libxcb-1.13.1-3.fc31.x86_64 libxcrypt-4.4.9-1.fc31.x86_64
> libxkbcommon-0.8.4-2.fc31.x86_64 libxml2-2.9.9-3.fc31.x86_64
> libxshmfence-1.3-5.fc31.x86_64 lz4-libs-1.9.1-1.fc31.x86_64
> mesa-libgbm-19.2.0~rc3-1.fc31.x86_64 mesa-libglapi-19.2.0~rc3-1.fc31.x86_64
> ncurses-libs-6.1-12.20190803.fc31.x86_64 openldap-2.4.47-3.fc31.x86_64
> openssl-libs-1.1.1d-1.fc31.x86_64 pango-1.44.6-1.fc31.x86_64
> pcre2-10.33-14.fc31.x86_64 pcre2-utf16-10.33-14.fc31.x86_64
> qgnomeplatform-0.5-13.fc31.x86_64 qt5-qtbase-5.12.4-7.fc31.x86_64
> qt5-qtbase-gui-5.12.4-7.fc31.x86_64 qt5-qtimageformats-5.12.4-2.fc31.x86_64
> qt5-qtwayland-5.12.4-7.fc31.x86_64 qt5-qtx11extras-5.12.4-2.fc31.x86_64
> systemd-libs-243-1.fc31.x86_64 xz-libs-5.2.4-6.fc31.x86_64
> zlib-1.2.11-19.fc31.x86_64

Ок, I did it. And add new backtrace2.log

Created attachment 2087 [details]
second try of backtrace2.log

(In reply to flash2071 from comment #8)
> Created attachment 2087 [details]
> second try of backtrace2.log

"No symbol table info available". You need run gdb again after install debuginfo ...

Happens to me also.

(gdb) run
Starting program: /usr/lib64/virtualbox/VirtualBox 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe3ccd700 (LWP 13039)]
[Thread 0x7fffe3ccd700 (LWP 13039) exited]
[New Thread 0x7fffe3ccd700 (LWP 13041)]
Qt WARNING: QSocketNotifier: Can only be used with threads started with QThread
[New Thread 0x7fffe213b700 (LWP 13043)]
[New Thread 0x7fffe193a700 (LWP 13044)]
[New Thread 0x7fffe1139700 (LWP 13045)]
[New Thread 0x7fffe0938700 (LWP 13046)]
[New Thread 0x7fffca43a700 (LWP 13047)]
[Detaching after fork from child process 13048]
[New Thread 0x7fffc9b19700 (LWP 13051)]
[New Thread 0x7fffc9a98700 (LWP 13052)]
[Detaching after fork from child process 13053]
[New Thread 0x7fffc8d46700 (LWP 13068)]
[New Thread 0x7fffc8cc5700 (LWP 13069)]
[New Thread 0x7fffbbfff700 (LWP 13070)]

Thread 1 "VirtualBox" received signal SIGSEGV, Segmentation fault.
0x00007ffff5064970 in vtable for QInputMethod () from /lib64/libQt5Gui.so.5

Created attachment 2089 [details]
basilrabi backtrace using gdb

QT5 was recently updated in F31 but VirtualBox still won't start. This crash does not happen to me in F30.

Thank you for the report, may you some kde input stuff or something like that  [1] ...

Can you try run GDK_BACKEND=x11 virtualbox ? 


[1]
Thread 1 (Thread 0x7ffff0cb3900 (LWP 13119)):
#0  0x00007ffff5064970 in vtable for QInputMethod () from /lib64/libQt5Gui.so.5
No symbol table info available.

(In reply to Sérgio Basto from comment #13) 
> Can you try run GDK_BACKEND=x11 virtualbox ? 

GDK_BACKEND=x11 virtualbox
Qt WARNING: QSocketNotifier: Can only be used with threads started with QThread
Segmentation fault (core dumped)

GDK_BACKEND=X11 virtualbox
Qt WARNING: QSocketNotifier: Can only be used with threads started with QThread

(VirtualBox:9669): Gtk-WARNING **: 09:59:44.498: cannot open display: :0

>may you some kde input stuff or something like that
I need to install kde input stuff?

(In reply to Basil Eric Rabi from comment #14)
> (In reply to Sérgio Basto from comment #13) 
> > Can you try run GDK_BACKEND=x11 virtualbox ? 
> 
> GDK_BACKEND=x11 virtualbox
> Qt WARNING: QSocketNotifier: Can only be used with threads started with
> QThread
> Segmentation fault (core dumped)
> 
> GDK_BACKEND=X11 virtualbox
> Qt WARNING: QSocketNotifier: Can only be used with threads started with
> QThread
> 
> (VirtualBox:9669): Gtk-WARNING **: 09:59:44.498: cannot open display: :0
> 

Thanks for the feedback

> >may you some kde input stuff or something like that
> I need to install kde input stuff?

I mean you may miss something from KDE , like input virtual keyboard , but I don't have a clue what is it . I use kde and it works for me , BTW have you kde desktop ? if yes can you try boot VirtualBox on kde desktop ? 

Thanks

> I mean you may miss something from KDE , like input virtual keyboard , but I
> don't have a clue what is it . I use kde and it works for me , BTW have you
> kde desktop ? if yes can you try boot VirtualBox on kde desktop ? 

I can't install kde via `dnf -y group install "KDE Plasma Workspaces"` due to some dependency issues on the packages right now but I tried the Xorg session. Seems to work fine! Thank you for the guidance! The crash happens only to the wayland session.

good is a step 

from [1] you have more two tips , one is running [2] other is removing qt5-wayland 

[1] 
https://bbs.archlinux.org/viewtopic.php?id=237449 

[2] export QT_QPA_PLATFORM=xcb; virtualbox

I filed a bug in fedora https://bugzilla.redhat.com/show_bug.cgi?id=1758724
The maintainer said that the reason for the crash is the hard coded dependencies on X11 API, without forcing the Qt's backend to be the one it depends on.

(In reply to Basil Eric Rabi from comment #18)
> I filed a bug in fedora https://bugzilla.redhat.com/show_bug.cgi?id=1758724
> The maintainer said that the reason for the crash is the hard coded
> dependencies on X11 API, without forcing the Qt's backend to be the one it
> depends on.

With feedback of the fedora bug report , if you could test it please .
I'd like to know, if install or uninstall qt5-wayland and or running QT_QPA_PLATFORM=xcb virtualbox , fix anything in gnome Wayland session .

Thanks

(In reply to Sérgio Basto from comment #19) 

> installed qt5-qtwayland
VirtualBox does not start

> installed qt5-qtwayland + QT_QPA_PLATFORM=xcb virtualbox
VirtualBox starts, my Virtual Windows 10 starts. However, both virtual machine and VirtualBox GUI become unresponsive after a few seconds.

> uninstalled qt5-qtwayland
VirtualBox starts, my Virtual Windows 10 starts. However, both virtual machine and VirtualBox GUI become unresponsive after a few seconds.

Using QT_QPA_PLATFORM=xcb and uninstalling qt5-qtwayland both results to unresponsive gui and Virtual Machine several seconds after login in the Virtual Machine.

*** Bug 5445 has been marked as a duplicate of this bug. ***

Thanks for finding out that it works in Xorg environment, and fails only in wayland. I removed qt5-qtwayland, and it is no longer crashing. So, we have a workaround.

*** Bug 5481 has been marked as a duplicate of this bug. ***

This also happens to me. After upgrading to Fedora 31, VirtualBox stopped working (with the same crashes other people reported) on a default Gnome session, but does work when I log in a different user with X Windows. Also, as other people reported simply removing the "qt5-qtwayland" from the system makes VirtualBox work again - even in the default Gnome (and, apparently, Wayland) session.

I reported this to the qt5-qtwayland people as a bug in that package (since, without it, VirtualBox works), https://bugzilla.redhat.com/show_bug.cgi?id=1780888, but they claim it is VirtualBox's bug, not their's.

In any case, sadly the end result is that in an out-of-the-box installation of Fedora 31 with rpmfusion, VirtualBox does not work.

With the new update (6.1.0_RPMFusion r135406) , the virtual box gui can now be opened in wayland. However, starting my Windows 10 virtual machine still won't work:

    Failed to open a session for the virtual machine win10.
    
    The virtual machine 'win10' has terminated unexpectedly during startup with exit code 1 (0x1).
    
    Result Code: NS_ERROR_FAILURE (0x80004005)
    Component: MachineWrap
    Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}


Anyway, it still works in Xorg.

Qt stack including kf5-kwayland-5.64.0-2.fc31 has been pushed to stable , can you update all Qt stack , and test it ? please , I heard that have some fixes for wayland 

Thanks

(In reply to Sérgio Basto from comment #26)
> Qt stack including kf5-kwayland-5.64.0-2.fc31 has been pushed to stable ,
> can you update all Qt stack , and test it ? please , I heard that have some
> fixes for wayland 
> 

I installed kf5-kwayland from updates-testing repo. It was not installed in my case. May it should be a requirement of virtualbox rpm? Anyway, starting my windows VM still fails:

    Failed to open a session for the virtual machine win10.

    The virtual machine 'win10' has terminated unexpectedly during startup because of signal 11.

    Result Code: NS_ERROR_FAILURE (0x80004005)
    Component: MachineWrap
    Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}

I installed kf5-kwayland-5.66.0-1 along with other packages in updates-testing. VM still won't start.

VirtualBox starts now in wayland in F32. The problem is the mouse click not being detected in the guest OS (windows). Although the keyboard works fine.

(In reply to Basil Eric Rabi from comment #29)
> The problem is the mouse click not being detected in the guest OS (windows).

This seems to be an issue only when in full screen. Mouse clicks fine when not in full screen mode.

the bug should be fixed , can you check it ? please 

Thanks

Yes, I confirm that there is no more segmentation fault in wayland.

(In reply to Basil Eric Rabi from comment #32)
> Yes, I confirm that there is no more segmentation fault in wayland.

Thank you