I have been experiencing this on a regular basis with VMWare Workstation
6.0.4 build-93057. I am running an AMD Phenom 9850+ BE with the 64bit
version of Kubuntu. My kernel version is 2.6.24-19 I am running KDE4
and I am using the Nvidia Xorg driver. I'm glad that the "setxkbmap"
workaround was
Oh, and just to add, my keyboard is attached to a KVM as well, not sure
if that's part of the cause.
--
Shift key (and caps lock) stop working when using VMWare
https://bugs.launchpad.net/bugs/195982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Yeh, which would be valid if only people with Ubuntu 8.04 were
experiencing this issue, which is not the case since I've been seeing
reports of this issue from people running all different types of Linux
distros. If they are not prepared to investigate what is causing this
issue then they might as
Yeh, I actually just put in an official support request with VMWare
since my 30 days of complimentary support should still be valid at this
point. We'll see what they say...
--
Shift key (and caps lock) stop working when using VMWare
https://bugs.launchpad.net/bugs/195982
You received this bug n
Oh, and just to point out that Andrés P. Ferrando posted above that he
is using OpenSUSE 10.2 (which is on the list of supported distros) and
is also experiencing this issue. This is definitely not related to one
specific distro.
--
Shift key (and caps lock) stop working when using VMWare
https
You'll see a line in /boot/grub/menu.lst that looks something like this:
kernel /boot/vmlinuz-2.6.27-9-generic root=UUID=4c5d576a-
7d38-43b2-b1d0-9bb18fdae820 ro quiet pci=nomsi
Just add the option to the end of the line, so that it looks something
like:
kernel /boot/vmlinuz-2.
I can confirm that this is happening to me as well after upgrading from
Ubuntu Hardy to Intrepid. I have an Asus M3N-HT Deluxe Mempipe (with
latest BIOS update) with a Phenom 9850+ Black Edition processor. When
booting the initial boot process will get stuck on one message, then I
need to press a
Oh, I forgot to mention that it freezes up the first time right after I
see the following message:
[0.004000] Aperture pointing to e820 RAM. Ignoring.
[0.004000] Your BIOS doesn't leave a aperture memory hole
[0.004000] Please enable the IOMMU option in the BIOS setup
[0.004000] Th
Here is the link for the Aperture issue which has also been logged as a
bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/271070
I'm not sure if the two issues are related or if the Aperture message
has always been there and people have just been noticing it more because
of this freezing
Has anyone else noticed that the new kernel is causing system
instability as well? I'm constantly coming back to my computer being
frozen on a black screen after leaving it running for a few hours. Not
sure if anyone else is observing this behaviour? This only started
after the upgrade.
--
Sys
Philip, this seems to possibly have something to do with ACPI (in part),
which is the power management in general. It's either that, or it's the
kernel recognizing the power supply much as it would recognize a usb
device (since there's been reports that plugging in a USB device has
much the same b
I would like to point out that the people complaining about hanging
should refer to the following bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/272247
I have confirmed that the aperture message was present in the old
2.6.24-21 kernel as well. The only reason that you guys are actuall
I just updated to kernel version 2.6.27-9 from 2.6.27-7. The new
version does nothing to address this issue. Is this being looked at?
It's definitely the most annoying bug that I've ever seen in Linux.
--
System freezes during boot, unless I hold a key down
https://bugs.launchpad.net/bugs/27224
I can't quite explain how incredibly annoying this suhosin patch is.
Even if I use the config option which supposedly disables it, it
continues to mess with code responsible for saving password crypts to a
database (it's forcing it to use sha-512 instead of salted md5,
incredibly annoying and a hug
This bug affects me as well but not when resizing windows. If I take a
window and drag it to the edge of a screen to initiate a cube rotate,
when the windows makes it to the next side of the cube it snaps down to
the bottom of the screen (so that there's now space between my cursor
and the top of
I should add that I am using a Radeon HD5450 with dual monitors running
Ubuntu 12.04 with unity disabled (installed gnome-panel). If I use the
ctrl-shift-alt-left/right shortcut to move a window between virtual
desktops instead of the window staying in it's original position on the
new desktop lik
I've attached a video of what I'm describing. You'll notice near the
end of the video that the window completely snaps away from my cursor
even though I'm still grabbing it (it ends up on a different virtual
desktop than the one I'm on). You'll also notice maximized windows
snapping to the second
This bug and bug #862430 are the two bugs that are absolutely killing me
with this version of Compiz. It would be nice to get a PPA setup that
has both of the fixes attached until they can do an official release
with the fixes.
--
You received this bug notification because you are a member of Ub
@Daniel van Vugt (vanvugt): Any chance of getting the patch for bug
#974242 included in your preproposed PPA as well? I just tried the
patch out using a different PPA and it works great. The only problem is
that the other PPA doesn't include the patch for bug #862430 so I'm
stuck with that bug ag
19 matches
Mail list logo
