Segmentation fault in VirtualBox

[marco.fortina]

Hi there! My VirtualBox crash and can not use it!

There are the step to reproduce the step: 1) create a new VM 2) start it 3) when prompted for iso click on the browse icon HERE IT CRASH!

Can you help me, please? What can I check? Which logs do you need?

Thanks, Marco

[Socratis]

May I suggest something? It's usually better and faster, if problems like this one (configuration, question) get first addressed in the forums (​https://forums.virtualbox.org/). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

So, if you can, please open a new thread in the ​VirtualBox on Linux Hosts section.

[Wesleyorama]

With a little research (after having the same issue) this seems to be caused by using Wayland instead of X. With more and more Linux distros (Ubuntu is changing to Wayland in next LTS) this is going to be a bigger problem.

Here is the error I am reeiving when attempting to set an ISO on a virtual disk drive.

(VirtualBox:15699): Gdk-WARNING **: /build/gtk+3.0-qPyWJl/gtk+3.0-3.22.11/./gdk/x11/gdkwindow-x11.c:5573 drawable is not a native X11 window
Segmentation fault (core dumped)

The immediate way to work around this is to switch to a X session by logging out and selecting the non-wayland session to log into.

[Wesleyorama]

Replying to socratis:

May I suggest something? It's usually better and faster, if problems like this one (configuration, question) get first addressed in the forums (​https://forums.virtualbox.org/). More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

So, if you can, please open a new thread in the ​VirtualBox on Linux Hosts section.

This isn't a config issue. It is a bug with virtualbox interacting with Wayland. While a few distros currently ship with Wayland, it seems it is going to be the defacto replacement for X. There is nothing anyone can do, short of editing code to fix this issue. Although there is a workaround of not using Wayland, with isn't exactly easy or possible for some.

[Wesleyorama]

Replying to Wesleyorama:

With a little research (after having the same issue) this seems to be caused by using Wayland instead of X. With more and more Linux distros (Ubuntu is changing to Wayland in next LTS) this is going to be a bigger problem.

Here is the error I am reeiving when attempting to set an ISO on a virtual disk drive.

(VirtualBox:15699): Gdk-WARNING **: /build/gtk+3.0-qPyWJl/gtk+3.0-3.22.11/./gdk/x11/gdkwindow-x11.c:5573 drawable is not a native X11 window
Segmentation fault (core dumped)

The immediate way to work around this is to switch to a X session by logging out and selecting the non-wayland session to log into.

There is another workaround for anyone looking to get around this issue, link the iso using the command line. ​https://superuser.com/questions/741734/virtualbox-how-can-i-add-mount-a-iso-image-file-from-command-line

[Socratis]

Just for the record, there is no evidence whatsoever that you're having the same problem as the OP. The OP talked about a "segmentation fault". In general. No indication about host, guest or the kind of error. That's why I prompted them to open a thread in the forums, like I do everyone else that doesn't provide even the minimum required information. "It crashes" is 95% not a bug.

You on the other hand have provided plenty of information. If you had opened a thread in the forums, I would have prompted you to open a bug ticket ;)

[Wesleyorama]

Replying to socratis:

Just for the record, there is no evidence whatsoever that you're having the same problem as the OP. The OP talked about a "segmentation fault". In general. No indication about host, guest or the kind of error. That's why I prompted them to open a thread in the forums, like I do everyone else that doesn't provide even the minimum required information. "It crashes" is 95% not a bug.

You on the other hand have provided plenty of information. If you had opened a thread in the forums, I would have prompted you to open a bug ticket ;)

Yeah, sorry if that came off as a bit hostile. Just wanted to get more information out there on the issue I am seeing. I had also been dealing it it at an inopportune moment. I felt that this defect was close enough to my issue that opening another ticket would have been unnecessary noise. Thanks for keeping an eye on this ticket.