Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 602818 - app-emulation/virtualbox-5.1.10-r1 and app-emulation/virtualbox-bin-5.1.10.112026: machines get aborted (segfault) during screen lock
Summary: app-emulation/virtualbox-5.1.10-r1 and app-emulation/virtualbox-bin-5.1.10.11...
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Lars Wendler (Polynomial-C) (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-16 12:47 UTC by Markus Wernig
Modified: 2017-08-31 19:56 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge.info.txt,5.53 KB, text/plain)
2016-12-16 12:47 UTC, Markus Wernig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Wernig 2016-12-16 12:47:18 UTC
Created attachment 456376 [details]
emerge --info

With both app-emulation/virtualbox-5.1.10-r1 and app-emulation/virtualbox-bin-5.1.10.112026, running virtual machines get aborted when the screen locker/screen saver of the host system is active for some time.

I was not able to find out the amount of time it takes, as it does not happen simply when the screen saver is activated. 
It appears that the machines segfault whenever the screen is locked automatically by the screen saver (after 300 sec in my case). If I manually lock the screen and then unlock it within some minutes, the problem does not occur.
If the screen is locked automatically and I unlock it again within some minutes,  the problem does not occur.
So this happens only after the screen has been locked for some minutes (sorry for not being able to be more precise on the timing).

The only notice in ~/.VirtualBox/VBoxSVC.log is
11:49:58.398549 Watcher  Reaper: Pid 11703 (2db7) was signalled: 11 (0xb)

The system is amd64 with kde/plasma.

The problem does not occur with virtualbox-4.3.38.
Comment 1 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev 2017-03-28 16:24:54 UTC
I suppose this still happens with latest virtualbox-5.1.x versions?