I had the same problem and I could fix it by manually installing
libssl1.0.0 from:
http://packages.ubuntu.com/lucid/libssl-dev
I needed to kill a process which were locking
/var/cache/debconf/config.dat before (I don't know if only killing this
process could be solved the problem).
Hi,
well, obviously there have been a lot of changes since then in the
KPackagekit department. On my Maverick desktop the issue is gone, and
the update progress window doesn't dance around any more: it has a fixed
width.
I did not test the ubiquity installation, as that involves actually
The same happens inside KPackagekit when doing an update. The progress
windows keeps resizing itself continually. It gets bigger or smaller
depending on the package it is updating. That leaves a very bad and
flaky impression.
--
Install progress report window shouldn't resize
I'm still on Feisty so I can't tell.
But I finally got it working on Feisty.
xorg.conf attached. The installed drivers are nvidia-glx-new
1.0.9755+2.6.20.5-16.29
Can someone confirm that this xorg.conf works? it doesn't have any EDIC,
ESID hacks at all.
** Attachment added: xorg.conf
Confirmed using architecture i386.
Loading images is way slower than on edgy after upgrade.
--
Gwenview scaling very slow
https://bugs.launchpad.net/bugs/99768
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Andrew: the nv diver works perfectly on edgy and feisty. Resolutions all
the way up to 1280x1024. The problem is with the binary nvidia drivers
AND DVI output with the L70A TFT monitor. Using analog VGA output works.
Apparently somewhere a year and a half ago nvidia altered their EDIC
algorithms
I can confirm this bug, a show-stopper for those affected.
I have a Hyundai ImageQuest L70A TFT. Native resolution is 1280x1024.
In Dapper, the nv driver works (both with a Geforce4200Ti at first, then
upgraded to a Geforce6600GT), but the nvidia 3D driver doesn't. You get
a 1024x768 resolution.
Confirmed here. I must add that it eventually works :
Just fire up WLAssistant and connect. It will say connection error. Just
let it be. After a while you'll be connected. Weird.
I'm also concerned that this bug doesn't have a priority assigned yet.
It is a MAJOR bug for laptop people!
--
