On 04/20/2009 08:32 AM, David C. Rankin wrote: > NoOp wrote: >> On 04/15/2009 11:54 PM, David C. Rankin wrote: >>> Listmates, >>> >>> Downloaded and installed vb 2.2.0 on my Toshiba P35d running openSuSE >>> 11.0. I >>> have run virtualbox on this machine since 1.5.6 and never experienced a >>> crash >>> where the window just crashes and disappears. I was simply cutting and >>> pasting >>> text to notepad when it occurred. Anyone else seeing this type of problem >>> with >>> 2.2.0?? >>> >> >> Win2KPro guest on Ubuntu 8.04; repeatable crash when opening MS Word 97. >> >> I wonder if these snips from the log are related: >> 07:58:33.748 PIT: mode=2 count=0x2ead (11949) - 99.85 Hz (ch=0) >> 07:59:50.806 Changing the VM state from 'RUNNING' to 'SUSPENDED'. >> 10:37:47.588 Changing the VM state from 'SUSPENDED' to 'RUNNING'. >> 10:38:08.116 VBoxX11ClipboardStopX11: stopping the shared clipboard X11 >> backend >> 10:38:08.139 Shared clipboard: host clipboard thread terminated successfully >> 10:38:10.401 Guest Log: VBOXNP: DLL loaded. >> 10:39:14.017 Guest Log: VBoxService: Ended. > > Anytime the APCI functions get vexed, you know you are in for trouble > -- it's > vodoo when you get do to it. It looks like something suspended the VM (I don't > know screen saver, etc..) and then the clipboard dies on the transition from > 'SUSPENDED' to 'RUNNING' and then all hell breaks loose. I haven't had much > time to use XP Pro 32-bit guest much since the first crash, but after the > crash, I restarted vbox with the xp guest just fine. I'll try to play with it > a > bit more and see if I can reproduce the problem as well. > >
Found my issue & possibly yours as well - it is a fault with the VBoxSharedClipboard.so file. I first uninstalled the VBox Guest Addition & verified that MS Office (97) works without the GE. I then installed the 2.1.4 GE & that made no difference - it still crashed as soon as I opened MS Word. Looking at the log file I found these msgs: 00:02:37.122 vboxClipboardConvertToUtf8ForX11: VBoxX11ClipboardReadVBoxData returned VERR_TIMEOUT 00:02:42.124 vboxClipboardConvertToCTextForX11: VBoxX11ClipboardReadVBoxData returned VERR_TIMEOUT I googled on "VBoxX11ClipboardReadVBoxData returned VERR_TIMEOUT" and found this 2.2.0 bug: http://www.virtualbox.org/ticket/3723 [VB guest crashed while typing into window => Fixed in SVN] I downloaded the http://www.virtualbox.org/attachment/ticket/3723/VBoxSharedClipboard.so-x86 file, replaced /usr/lib/virtualbox/VBoxSharedClipboard.so with that one (renaming VBoxSharedClipboard.so to x-VBoxSharedClipboard.so-x and VBoxSharedClipboard.so-x86 to VBoxSharedClipboard.so) and all MSO apps are working again - no crash (so far). Remember to chown the file to root otherwise VBox won't start & tell you that VBoxSharedClipboard.so is an untrusted file because it's not owned by root. So, you might want to give that a try - there is also a file for amd64 if your machine is 64bit. Note to Daniel Hauck: I also tried swapping the NIC's as you suggested & that made no difference. But thank for the suggestion anyway. _______________________________________________ vbox-users mailing list vbox-users@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-users
