Screenshot showing same behavior, xorg + None for paravirtualization:
https://i.imgur.com/6pB3Npc.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971010
Title:
[vmwgfx] Screen and mouse
I have the exact same bug, using Xorg. VM worked until updated to
Jammy, now shows just like in OP's video: Launcher is drawn fully, but
only the top left part of the background draws. Dragging windows in
working portion of screen with mouse doesn't work.
The paravirtualization setting has no
This appears to have been fixed at some point. Testing with current
packages is not showing the problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1163404
Title:
xerver-xorg-core
Public bug reported:
When installing drivers, particularly graphics drivers, new users
commonly find themselves at a black screen with no idea of how to back
out their updates. It would be nice if Ubuntu offered a fallback option
at grub that booted to a GUI, loading the last drivers that were
I tested with the nvidia-313-updates package on my new P150EM and got
the same results. Backleveling xserver -xorg-core works around the
problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
As Alain-Olivier stated, and I can confirm: This happens even with
single monitor on a fully patched Quantal install.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1060511
Title:
Left
I tested with the 304.43 edgers package and the new drivers do fix the
crash with these applications, as well as with the Unity and other 3D
desktops.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
Yes, Rocko - It's in the nvidia driver. See Daniel's message #6.
Unless I misunderstand what he said: Nvidia built/released the 304.37
drivers to what they thought would be 1.13 compliant around the 13th,
but there was a change in the ABI on the 17th, that broke their
compatibility, before the
As a *workaround*, you can enable the nouveau driver in
/etc/X11/xorg:
Unless you happen to own a GTX 560/GF114 card like some of us, as there
is a curent Nouveau bug that causes it to throw PFIFO - playist update
failed, and failed to idle channel... messages while repeatedly
restarting
As Dave points out, the real problem is not that there are unmet
dependencies for the current package, but that the 302.17 package needs
to be recompiled against the new X ABI. It's a bit confusing for users
though, since the current package is relatively new.
--
You received this bug
I'm in a very similar boat myself, actually. I too am just an alpha
tester here, and this has pretty much put the kibosh to most of my
Quantal usage for the moment. Nouveau doesn't work too well with my
GTX560Ti (It will only came up in lower resolutions that don't match my
monitor) on my main
If you're really stuck, you can workaround the problem like I just did:
I manually grabbed the 302.17 nvidia-current and nvidia-current-dev from
the xorg-edgers ppa here: https://launchpad.net/~xorg-
edgers/+archive/ppa/+sourcepub/2512683/+listing-archive-extra, and
manually installed them with
Sure thing. Attached!
** Attachment added: nvidia-bug-report.log.gz
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/901386/+attachment/2729452/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I can confirm that I too am able to boot 3.2.0-10 without adding
intel_iommu=off.
I did *not* have to reinstall any drivers like Sander though.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
Has anyone had any luck with newer kernels than 3.2rc4?
No luck here. As of 3.2.0.9 I still have to disable intel_iommu in grub
to get it to work, even with the new 290.10 nvidia-current packages.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I can confirm Haitao's workaround as well. I added intel_iommu=off and
was then able to boot 3.2.0-6 without issue.
Thanks Haitao!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
Looks like I have to back off the without issue in my previous
statement. I just noticed that the USB3.0 devices attached to my Marvel
88SE91xx adapter are not being seen when I use this workaround. Of
course, at this point I'm assuming it's caused by the work around and
not an entirely separate
Just tested and found that acpi=off lets me boot the 3.2.0-6 too - and
it works fine with the nvidia-current drivers. Too bad it means my
i980x is treated single-core.
I'm not sure you'll find the trouble in a diff of the more recent
mainline configs - both mainline rc5 and rc6 don't work for me
Happens to me with both 3.2.0-1 and 3.2.0-2 using a GTX560 card and
nvidia-current (285.05.09-0ubuntu1) drivers. I can reboot to 3.1 kernel
and all is fine.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
*** This bug is a duplicate of bug 810221 ***
https://bugs.launchpad.net/bugs/810221
I updated my sons computer to oneiric from natty yesterday so that he
could do some alpha testing and ran into the same problem (i.e. it was
using nouveau after the upgrade, but was working fine with nvidia-
New nvidia-current drivers appear to have been uploaded in the last few
hours, fixing 798049.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/798007
Title:
[Oneiric] Latest mesa (7.10.3) breaks
Marc: Unlocking the screen on crash isn't a direct loss of privacy?
I am experiencing this issue too - and am not really concerned to find
my screen/keyboard unlocked when I return. But, if this were an
enterprise desktop sitting in a high traffic area, I might be quite
upset.
--
There definitely needs to be a rollback feature, but not one specific to
synaptic (it's not even installed by default in Kubuntu, no?).
It should probably be an option from the recovery menu: roll back
packages since [time|last-successful-boot].
This probably won't happen much to non-alpha/beta
Locking them in Synaptic will only effect upgrades done through
Synaptic. Pinning the versions will prevent any of the utilities from
seeing the updates.
After you backlevel the following packages to the 9 release, create a new file
called '/etc/apt/preferences' which contains everything
Pauli's observations match with my own: I noticed the problem right
after upgrading the libc6 packages. taking them back to the ubuntu9
versions made the issue disappear.
--
[karmic] Xorg (and anything GLX) crashes on startup
https://bugs.launchpad.net/bugs/429003
You received this bug
This is a dupe of bug 394262.
** This bug has been marked a duplicate of bug 394262
[Karmic] nvidia DKMS building and installation for kernel 2.6.31-1-generic
fails with exit status 10
--
[karmic] Nvidia DKMS installation fails
https://bugs.launchpad.net/bugs/394343
You received this bug
I can confirm seeing the same behavior, as have others in duplicate
reports.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: New = Confirmed
--
[Karmic] nvidia DKMS building and installation for kernel 2.6.31-1-generic
fails with exit status 10
Appears to have been fixed in the 180.60 drivers.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: Confirmed = Fix Released
--
package nvidia-glx-180-dev 180.29-0ubuntu2 failed to install/upgrade:
subprocess pre-installation script returned error exit status 2
That's probably why they still have 180.51 listed as the current stable
version.
It looks like 185.18.14 is the release candidate now, and also fixes bug
353502.
--
Stable NVIDIA driver 180.53 released - please upgrade in Jaunty
https://bugs.launchpad.net/bugs/364965
You received this bug
29 matches
Mail list logo
