FS#22225 - [virtualbox] Segfault on click to Settings

Attached to Project: Community Packages
Opened by Sébastien Luttringer (seblu) - Monday, 27 December 2010, 00:45 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 19 January 2011, 21:30 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Ionut Biru (wonder)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description: VirtualBox 4.0.0 package segfault when i click to Settings icon or right click to settings on a selected VM.

shell ouput:
rwolf ~ $ VirtualBox (1:40)[0]
zsh: segmentation fault VirtualBox
rwolf ~ $

dmesg output:
VirtualBox[4853]: segfault at 20 ip 00007f9089172078 sp 00007fff18d18e60 error 4 in libQtGui.so.4.7.1[7f9088f66000+a4a000]

Additional info:
* package version: 4.0.0 + guest additions + vbox-ext-oracle

Steps to reproduce:
VirtualBox
Select a VM
Click on settings. => segfault.

Can they have a issue with Qt?

A custom compiled version from virutalbox_bin package in AUR don't segfault.
Stracing and Ltracing is not usable.
This task depends upon

Closed by  Ionut Biru (wonder)
Wednesday, 19 January 2011, 21:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  virtualbox 4.0.2
Comment by Ionut Biru (wonder) - Monday, 27 December 2010, 00:54 GMT
http://www.virtualbox.org/ticket/7912
Comment by Ionut Biru (wonder) - Monday, 27 December 2010, 00:55 GMT
does it happen only on old VMs?
Comment by Sébastien Luttringer (seblu) - Monday, 27 December 2010, 01:09 GMT
This happend with old and new VMs. But tips of clicking on right side works well!

You don't have this issue?
Comment by Marek Niklicek (Dogmeat) - Monday, 27 December 2010, 01:54 GMT
I can confirm segmentation fault after clicking on Settings in virtualbox 4.0.0-2 from community repo. Before I started Virtualbox 4 I removed old ~/.VirtualBox. I can launch Virtualbox 4, create a virtual machine, but can't change settings due to segfault.
Comment by Ionut Biru (wonder) - Monday, 27 December 2010, 08:50 GMT
@Seb no. maybe is an x86_64 issue only?
Comment by Jelle van der Waa (jelly) - Monday, 27 December 2010, 12:49 GMT
i don't have this issue with Virtualbox 4.0.0-2 and old VM on 64 bit
Comment by Sébastien Luttringer (seblu) - Monday, 27 December 2010, 21:12 GMT
@wonder: maybe, i cannot test on x86 :/ I found the same issue today on Orable debian package amd64.

@jelly: can we understand: you have this issue with new VM on 64bits?
Comment by Ionut Biru (wonder) - Monday, 27 December 2010, 21:21 GMT
nice to see is not a packaging issue. the only way to fix this is to debug and submit everything upstream and hope they would fix it.

i'll try tomorrow to build a debug version for vbox+qt
Comment by Marek Niklicek (Dogmeat) - Monday, 27 December 2010, 21:48 GMT
Besides x86_64 I can reproduce it on i686 as well (on a different machine). It happens on new VMs (I don't have old ones).
Comment by Ionut Biru (wonder) - Monday, 27 December 2010, 23:17 GMT
http://pkgbuild.com/~ioni/vbox/

get the packages from here.
gdb virtualbox
run
(make it crash)
bt full
Comment by Marek Niklicek (Dogmeat) - Monday, 27 December 2010, 23:35 GMT
I already tried to do it but I wasn't able to start Virtualbox from gdb. Output of my first debug build and yours is in 1.log + virtualbox-error-01.png and output from my second build with --disable-hardening is in 2.log + virtualbox-error-02.png.

I can start Virtualbox outside gdb normally.
   1.log (0.9 KiB)
   virtualbox-error-01.png (28.8 KiB)
   2.log (0.8 KiB)
   virtualbox-error-02.png (28.9 KiB)
Comment by Ionut Biru (wonder) - Monday, 27 December 2010, 23:57 GMT
lets stop debugging. i found another upstream bug with a lot of info:

http://www.virtualbox.org/ticket/7909
Comment by Thomas Dziedzic (tomd123) - Tuesday, 04 January 2011, 06:47 GMT
pasting original br: http://www.virtualbox.org/ticket/7875
All the previous bug reports have been marked as duplicates of 7875.
Comment by Jeremy LaCroix (jlacroix) - Tuesday, 04 January 2011, 17:47 GMT
Same problem here.
Comment by Sébastien Luttringer (seblu) - Tuesday, 04 January 2011, 20:37 GMT
please note thant package virtualbox_bin in AUR is not affected because it embeds the qt libraries.
Comment by Damien Sticklen (ubiquitous1980) - Saturday, 08 January 2011, 11:07 GMT
I can confirm that this segfault occurs for virtualbox (OSE) version 4.0.0-3 under the following conditions:

Running KDE under GDM
Running KDE under KDM

I can confirm that this segfault does NOT occur under the following conditions:

Running GNOME under GDM
Running GNOME under KDM

Therefore, it seems the common factor is KDE. I provide the following system details:

Linux archlinux 2.6.36-ARCH #1 SMP PREEMPT Fri Dec 10 20:01:53 UTC 2010 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ AuthenticAMD GNU/Linux
kde-meta-kdebase 4.5-2 (providing in fact, KDE SC 4.5.5)
extra/gnome-desktop 2.32.1-1

I hope that this helps towards finding a resolution. I will update as information surfaces.

[update:] As per https://bbs.archlinux.org/viewtopic.php?id=91083 I changed my theme to cleanlooks via system settings in KDE. Under these conditions, the bug disappears. This link that I provided has previously allowed users to "Solve" this issue. I am not sure that including the bundled QT for virtualbox counts as a solve however.

Comment by Sébastien Luttringer (seblu) - Tuesday, 18 January 2011, 22:45 GMT
seems to be fixed in 4.0.2. See changelog: http://www.virtualbox.org/wiki/Changelog
Comment by Ionut Biru (wonder) - Tuesday, 18 January 2011, 23:27 GMT
check our packages and report back
Comment by Ionut Biru (wonder) - Wednesday, 19 January 2011, 19:32 GMT
so, in the end works or not?
Comment by Marek Niklicek (Dogmeat) - Wednesday, 19 January 2011, 21:26 GMT
With virtualbox 4.0.2-3 it works properly.

Loading...