kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Dirk, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Summary changed:

- Gnome problems after VMWare fullscreen
+ [VMWare Workstation 6.0.3] Gnome problems after fullscreen

** This bug is no longer a duplicate of bug 195982
   Shift key (and caps lock) stop working when using VMWare

** Package changed: ubuntu => linux (Ubuntu)

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/225529

Title:
  [VMWare Workstation 6.0.3] Gnome problems after fullscreen

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This problem started after upgrading to Hardy:

  After switching VMware Workstation 6.0.3 into full screen mode, the
  shift and caps lock keys won't function anymore in the host OS (Ubuntu
  8.04). They are still ok in the guest OS.

  Gnome applications that were started before VMWare goes fullscreen,
  continue to run and they can receive keyboard events. Gnome
  applications that were started afterwards will segfault as soon as
  they receive keyboard input. Non-Gnome applications like xterm won't
  segfault.

  I don't think that this has anything to do with the guest OS because
  the same thing happens with W2k and Debian 4.0 + Gnome as the guest.
  But apparently it does have to be an OS with "big video". I also tried
  DOS and Windows 3 (I'm keeping this just for fun, I also have Windows
  1), but then it doesn't happen. Using the fullscreen mode in Gimp, VLC
  and gThumb does not generate this effect.

  Here are some of the segfaults:

  May  2 12:53:19 queens kernel: [596672.630436] gedit[18474]: segfault at 00000028 eip b76e2275 esp bf8d4270 error 4
  May  2 12:54:30 queens kernel: [596743.983154] gcalctool[18482]: segfault at 00000057 eip b7b3f275 esp bfae93b0 error 4
  May  2 13:07:27 queens kernel: [597519.129764] nautilus[19411]: segfault at 00000026 eip b7874275 esp bf9f9db0 error 4

  My video card is a Matrox P650 and I am using matroxdriver_mtx-
  x86_32-1.4.5.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/225529/+subscriptions