Date: Wed, 30 Oct 2013 19:19:50 +0400 From: Oleg Ginzburg <olevole@olevole.ru> To: freebsd-emulation@freebsd.org Cc: pkubaj@riseup.net Subject: Re: VirtualBox segfaults on 10.0-CURRENT Message-ID: <4044910.ioSRPsz5Ae@gizmo.nevosoft.local> In-Reply-To: <CAFt_eMrft6UdmH%2BKJthGZ96%2BZWNcd3uKoKMaRw-D5XL25KzgkQ@mail.gmail.com> References: <524EF2FA.9040200@riseup.net> <e4fa1291-e7c3-4ee7-89f3-97083230309c@email.android.com> <CAFt_eMrft6UdmH%2BKJthGZ96%2BZWNcd3uKoKMaRw-D5XL25KzgkQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: Miguel C. <miguelmclara@gmail.com>
> Date: Fri, Oct 4, 2013 at 9:13 PM
> Subject: Re: VirtualBox segfaults on 10.0-CURRENT
> To: Piotr Kubaj <pkubaj@riseup.net>, freebsd-emulation@freebsd.org
>
>
>
> I have a similar report in the list... I'm able to run VirtualBox with sudo
> -u myuser had a workarround. But I'm not sure why it works.
>
I have some issues with VirtualBox. Looks like this is KDE4-specific problem
because when i run VirtualBox from any other WM all works fine. The same
behavior (Segfaults in KDE4 and not in fluxbox/lxde ..) is security/keepassx2.
I assume that KDE4 execute program differently (for example in trace outside
KDE i have no lots of stat(~/.{config,kde4}/{app}rc) files.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4044910.ioSRPsz5Ae>