Bug 681 - Complete freeze after some time in Virtualbox
Summary: Complete freeze after some time in Virtualbox
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: Mageia 1
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-04-07 12:47 CEST by thomas bjo
Modified: 2012-02-03 13:39 CET (History)
1 user (show)

See Also:
Source RPM: virtualbox src.rpm
CVE:
Status comment:


Attachments

Description thomas bjo 2011-04-07 12:47:31 CEST
Mageia freezes completely (repetedly) after some times use of FF4. I cannot say if this is FF4 related  - but that is when it happens to me.
I have not been able to reconstruct this with Chromium or during other activities.

To reconstruct:
In VB
Open FF4 and use it for a while.
Comment 1 Manuel Hiebel 2011-09-02 22:11:50 CEST
Hi, I think this issue is resolved no ?

Keywords: (none) => NEEDINFO
Source RPM: FF4? => firefox
Whiteboard: (none) => check

Comment 2 thomas bjo 2011-09-05 13:51:52 CEST
I have not been able to reproduce the freeze of the entire Mageia system. 
I managed to do a 64bit flash install and started to write a post in a forum when firefox-bin (FF6) got completely unresponsive.
I tried to start a terminal but it would not pop and although I could navigate the menus the "shutdown" or "restart" did not work.
So basically I got the cursor movement back - but it is still frozen for practical purposes.

After a brutal restart I was able to reproduce the error within 5 minutes. Terminal with htop and Firefox6 were running

This time the entire system froze like before. Different FF version - same problem.
So the problem remains.
Manuel Hiebel 2011-09-23 22:31:41 CEST

Whiteboard: check => (none)

Comment 3 Manuel Hiebel 2011-10-16 01:00:23 CEST
Do you have log of crash ? /var/log/Xorg.0.log /var/log/syslog or another one ?
Comment 4 thomas bjo 2011-11-04 14:30:22 CET
Xorg.0.log:

[   679.683] (EE) VBoxVideo(0): Unable to determine whether the virtual machine supports mouse pointer integration - request initialization failed with return code -4


It looks like it confuses my USB sidewinder Keyboard with the mouse. Because it is the keyboard that gets inresponsive.

Also the error does not occur when I use Opera So it might be triggered by FF somehow.
Comment 5 thomas bjo 2011-11-04 14:47:52 CET
It just froze while using Opera so it is not specific for FF. I can move the cursor and get the dropdown menus and start some applications like the terminal.
I cannot write anything in the terminal.
And I am unable to close Opera.
Comment 6 Marja Van Waes 2011-12-29 15:51:24 CET
@ Thomas

Is the problem still there?

If so, do you only get it when web browsing, or also when using other applications?

You're using cauldron and you have a completely updated system, or do you use Mageia 1 at the moment?

Which version of VirtualBox do you use?

Is it only the keyboard that freezes, atm ?

Does it help to unplug the keyboard and plug it back in?

If that helps, please open a terminal and as root type
tailf /var/log/messages 2>&1 | tee output.txt

and attach output.txt here

When you start your browser from a console, do you see any interesting messages when this happens?

CC: (none) => marja11
Source RPM: firefox => virtualbox src.rpm

Comment 7 Marja Van Waes 2012-01-18 07:42:13 CET
@ Thomas

Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD.
Comment 8 Marja Van Waes 2012-02-03 13:39:17 CET
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.