Random "windows key pressed" [SOLVED]
Random "windows key pressed" [SOLVED]
I'm experiencing random "windows key" pressed, expecially moving the mouse.
I don't know how to resolve this issue and is quite annoing, the vm is not really usable.
vbox: 4.1.20 r80170
host: windows 7
guest: fedora 17
just insalled this vbox version, previous one has not this problem.
Any help greatly appreciated
nb.
I don't know how to resolve this issue and is quite annoing, the vm is not really usable.
vbox: 4.1.20 r80170
host: windows 7
guest: fedora 17
just insalled this vbox version, previous one has not this problem.
Any help greatly appreciated
nb.
Last edited by nb on 31. Aug 2012, 12:39, edited 1 time in total.
-
michaln
- Oracle Corporation
- Posts: 2973
- Joined: 19. Dec 2007, 15:45
- Primary OS: MS Windows 7
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Any and all
- Contact:
Re: Random "windows key pressed"
Please describe exactly step by step how to reproduce.nb wrote:Any help greatly appreciated
Re: Random "windows key pressed"
I was not quite precise on previous post
What I did is:
- update fedora
- update vbox from 4.1.18 x to 4.1.20
- restarted vm
- recompile vbox addons
- restart vm
using the vm (fedora 17 with normal DE Gnome 3.x) lot of time (really often, resulting in an unusable vm) the DE behave like the "windows key" is pressed.
I've not a precise sequence of action to execute to manifest this problem, as soon as I can find something I will post it; I can only suppose that installing fedora 17 from scratch and updating it will lead same result.
In previous post I said that previously was not happening, I intended with vbox 4.1.18 and without the fedora updates.
Just because I did 2 updates: fedora and vbox, I will try to returned to vbox 4.1.18 to check if it's more related to fedora than vbox.
current fedora is updated to kernel: 3.5.2-3.fc17.x86_64
really annoying behaviour!
What I did is:
- update fedora
- update vbox from 4.1.18 x to 4.1.20
- restarted vm
- recompile vbox addons
- restart vm
using the vm (fedora 17 with normal DE Gnome 3.x) lot of time (really often, resulting in an unusable vm) the DE behave like the "windows key" is pressed.
I've not a precise sequence of action to execute to manifest this problem, as soon as I can find something I will post it; I can only suppose that installing fedora 17 from scratch and updating it will lead same result.
In previous post I said that previously was not happening, I intended with vbox 4.1.18 and without the fedora updates.
Just because I did 2 updates: fedora and vbox, I will try to returned to vbox 4.1.18 to check if it's more related to fedora than vbox.
current fedora is updated to kernel: 3.5.2-3.fc17.x86_64
really annoying behaviour!
Re: Random "windows key pressed"
Moving to vbox 4.1.18 and recompilying vbox add, obviously using the informations on the ticket 10709
is behaving in the same way.
As said mainly when using the mouse; can mean some problem related to mouse drivers changes in kernel update? do you think there is some configuration I can try to overcame this problem?
to reproduce on my vm I open the gnome menu on top right (the one on the user name) and move the mouse on the menu choices, after one or two time I move over the menu entries the problem manifest itself.
nb
is behaving in the same way.
As said mainly when using the mouse; can mean some problem related to mouse drivers changes in kernel update? do you think there is some configuration I can try to overcame this problem?
to reproduce on my vm I open the gnome menu on top right (the one on the user name) and move the mouse on the menu choices, after one or two time I move over the menu entries the problem manifest itself.
nb
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Random "windows key pressed"
I also see this on occasion, but have not tracked it down. What happens if you turn off 3D in the guest settings? (guest must be shut down first)
F17 is using some software acceleration for Gnome3 and it appears to cause some kind of conflict (maybe)?
F17 is using some software acceleration for Gnome3 and it appears to cause some kind of conflict (maybe)?
Re: Random "windows key pressed"
I switched off 3D and restarted; strangely gnome is not falling in the legacy mode.
Finally the result is the same, still the problem is manifesting.
nb.
Finally the result is the same, still the problem is manifesting.
nb.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Random "windows key pressed"
Not strange at all. Like I said they are running some kind of software acceleration to allow Gnome3 on units that fall short of the necessary graphics.
Thanks for checking though.
Thanks for checking though.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Random "windows key pressed"
I might mention that (for me) when you finally are logged in to the Gnome3 DT all I need to do is wiggle the mouse in the center of the DT to trigger the activation of the menu.
I say after I finally get logged in because it sometimes takes 2 or 3 ctrl+alt+bkspace to get the login menu. It just sits there and does nothing until I do. Just another reason why I am not using Gnome3 on anything these days.
I'll upload logs here in a bit.
VBox.log,messages,Xorg.0.log
I say after I finally get logged in because it sometimes takes 2 or 3 ctrl+alt+bkspace to get the login menu. It just sits there and does nothing until I do. Just another reason why I am not using Gnome3 on anything these days.
I'll upload logs here in a bit.
VBox.log,messages,Xorg.0.log
Re: Random "windows key pressed"
Sorry but I have to disagree. Previously was working fine and I never had big problems like this on a linux+gnome3 installed as main OS instead of VM;I think there are some incompatibilities on the mouse driver, the mouse is behaving strangly also on other function like highlighting more lines and scrolling.
Following are the fedora upgraded packages, as you can see no gnome core stuff was updated (I think wireshark-gnome does not matter); I think main problems should arise from kernel stuff or xorg ones.
Any other idea?
Following are the fedora upgraded packages, as you can see no gnome core stuff was updated (I think wireshark-gnome does not matter); I think main problems should arise from kernel stuff or xorg ones.
Any other idea?
Code: Select all
Packages Altered:
Updated ImageMagick-6.7.5.6-3.fc17.x86_64 @anaconda-0
Update 6.7.5.6-4.fc17.x86_64 @updates
Updated ImageMagick-c++-6.7.5.6-3.fc17.x86_64 @anaconda-0
Update 6.7.5.6-4.fc17.x86_64 @updates
Updated avahi-0.6.31-3.fc17.x86_64 @updates
Update 0.6.31-5.fc17.x86_64 @updates
Updated avahi-autoipd-0.6.31-3.fc17.x86_64 @updates
Update 0.6.31-5.fc17.x86_64 @updates
Updated avahi-glib-0.6.31-3.fc17.x86_64 @updates
Update 0.6.31-5.fc17.x86_64 @updates
Updated avahi-gobject-0.6.31-3.fc17.x86_64 @updates
Update 0.6.31-5.fc17.x86_64 @updates
Updated avahi-libs-0.6.31-3.fc17.i686 @updates
Updated avahi-libs-0.6.31-3.fc17.x86_64 @updates
Update 0.6.31-5.fc17.i686 @updates
Update 0.6.31-5.fc17.x86_64 @updates
Updated avahi-ui-gtk3-0.6.31-3.fc17.x86_64 @updates
Update 0.6.31-5.fc17.x86_64 @updates
Updated cheese-2:3.4.2-3.fc17.x86_64 @updates
Update 2:3.4.2-4.fc17.x86_64 @updates
Updated cheese-libs-2:3.4.2-3.fc17.x86_64 @updates
Update 2:3.4.2-4.fc17.x86_64 @updates
Updated exiv2-libs-0.22-5.fc17.x86_64 @anaconda-0
Update 0.22-6.fc17.x86_64 @updates
Updated fedora-logos-17.0.2-1.fc17.noarch @anaconda-0
Update 17.0.2-5.fc17.noarch @updates
Updated grep-2.13-1.fc17.x86_64 @updates
Update 2.14-1.fc17.x86_64 @updates
Updated grub2-1:2.0-0.37.beta6.fc17.x86_64 @updates
Update 1:2.0-0.38.beta6.fc17.x86_64 @updates
Updated grub2-tools-1:2.0-0.37.beta6.fc17.x86_64 @updates
Update 1:2.0-0.38.beta6.fc17.x86_64 @updates
Updated ibus-libpinyin-1.4.2-1.fc17.x86_64 @updates
Update 1.4.91-1.fc17.x86_64 @updates
Updated iniparser-3.0-1.fc17.x86_64 @fedora
Update 3.1-1.fc17.x86_64 @updates
Erase kernel-3.5.0-2.fc17.x86_64 @updates
Install kernel-3.5.2-3.fc17.x86_64 @updates
Erase kernel-devel-3.5.0-2.fc17.x86_64 @updates
Install kernel-devel-3.5.2-3.fc17.x86_64 @updates
Updated kernel-headers-3.5.2-1.fc17.x86_64 @updates
Update 3.5.2-3.fc17.x86_64 @updates
Updated libburn-1.2.2-1.fc17.x86_64 @anaconda-0
Update 1.2.4-1.fc17.x86_64 @updates
Updated libisofs-1.2.2-1.fc17.x86_64 @anaconda-0
Update 1.2.4-1.fc17.x86_64 @updates
Updated libpinyin-0.6.92-2.fc17.x86_64 @updates
Update 0.7.1-1.fc17.x86_64 @updates
Updated libpinyin-data-0.6.92-2.fc17.x86_64 @updates
Update 0.7.1-1.fc17.x86_64 @updates
Updated libquvi-scripts-0.4.4-1.fc17.noarch @anaconda-0
Update 0.4.7-1.fc17.noarch @updates
Updated lohit-kannada-fonts-2.5.1-1.fc17.noarch @anaconda-0
Update 2.5.1-2.fc17.noarch @updates
Updated minizip-1.2.5-6.fc17.x86_64 @anaconda-0
Update 1.2.5-7.fc17.x86_64 @updates
Updated nspluginwrapper-1.4.4-9.fc17.x86_64 @updates
Update 1.4.4-11.fc17.x86_64 @updates
Updated opencc-0.3.0-1.fc17.x86_64 @anaconda-0
Update 0.3.0-4.fc17.x86_64 @updates
Updated openldap-2.4.31-7.fc17.x86_64 @updates
Update 2.4.32-2.fc17.x86_64 @updates
Updated openssh-5.9p1-22.fc17.x86_64 @anaconda-0
Update 5.9p1-26.fc17.x86_64 @updates
Updated openssh-clients-5.9p1-22.fc17.x86_64 @anaconda-0
Update 5.9p1-26.fc17.x86_64 @updates
Updated openssh-server-5.9p1-22.fc17.x86_64 @anaconda-0
Update 5.9p1-26.fc17.x86_64 @updates
Updated python-urlgrabber-3.9.1-14.fc17.noarch @updates
Update 3.9.1-16.fc17.noarch @updates
Updated qt-settings-4.8-16.fc17.noarch @updates
Update 4.8-18.fc17.noarch @updates
Updated ruby-1.9.3.194-14.fc17.x86_64 @updates
Update 1.9.3.194-15.fc17.x86_64 @updates
Updated ruby-irb-1.9.3.194-14.fc17.noarch @updates
Update 1.9.3.194-15.fc17.noarch @updates
Updated ruby-libs-1.9.3.194-14.fc17.x86_64 @updates
Update 1.9.3.194-15.fc17.x86_64 @updates
Updated rubygem-bigdecimal-1.1.0-14.fc17.x86_64 @updates
Update 1.1.0-15.fc17.x86_64 @updates
Updated rubygem-io-console-0.3-14.fc17.x86_64 @updates
Update 0.3-15.fc17.x86_64 @updates
Updated selinux-policy-3.10.0-145.fc17.noarch @updates
Update 3.10.0-146.fc17.noarch @updates
Updated selinux-policy-devel-3.10.0-145.fc17.noarch @updates
Update 3.10.0-146.fc17.noarch @updates
Updated selinux-policy-targeted-3.10.0-145.fc17.noarch @updates
Update 3.10.0-146.fc17.noarch @updates
Updated telepathy-gabble-0.16.1-1.fc17.x86_64 @updates
Update 0.16.2-1.fc17.x86_64 @updates
Updated tracker-0.14.1-1.fc17.x86_64 @anaconda-0
Update 0.14.2-1.fc17.x86_64 @updates
Updated wireshark-1.6.8-1.fc17.x86_64 @updates
Update 1.6.10-1.fc17.x86_64 @updates
Updated wireshark-gnome-1.6.8-1.fc17.x86_64 @updates
Update 1.6.10-1.fc17.x86_64 @updates
Updated wqy-zenhei-fonts-0.9.46-4.fc17.noarch @updates
Update 0.9.46-6.fc17.noarch @updates
Updated xorg-x11-server-Xephyr-1.12.2-4.fc17.x86_64 @updates
Update 1.12.3-1.fc17.x86_64 @updates
Updated xorg-x11-server-Xorg-1.12.2-4.fc17.x86_64 @updates
Update 1.12.3-1.fc17.x86_64 @updates
Updated xorg-x11-server-common-1.12.2-4.fc17.x86_64 @updates
Update 1.12.3-1.fc17.x86_64 @updates
Updated zlib-1.2.5-6.fc17.i686 @anaconda-0
Updated zlib-1.2.5-6.fc17.x86_64 @anaconda-0
Update 1.2.5-7.fc17.i686 @updates
Update 1.2.5-7.fc17.x86_64 @updates
Re: Random "windows key pressed"
seems related
downgrading to xorg-x11-server-xorg 1.12.0 - 2.fc17
is working again
nb.
not working in my case, the pointer is no more visible in this wayVirtualBox GUI -> menu -> machine -> disable mouse integration
not workingxset m 1/3 0
downgrading to xorg-x11-server-xorg 1.12.0 - 2.fc17
is working again
nb.
-
Rich Green
- Posts: 1
- Joined: 31. Aug 2012, 17:30
Re: Random "windows key pressed" [SOLVED]
There was me thinking I was going out of my mind ... was my laptop overheating? Was I leaning on the mousepad in some strange way. Was the fix to downgrade xorg ??
Re: Random "windows key pressed" [SOLVED]
yes downgrading the xorg-x11-server-xorg package resolved this issue.
Currently not other problems are manifesting.
Currently not other problems are manifesting.