[Bug 623593] Re: package nvidia-current 256.44-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build

2011-02-20 Thread Charles Manning
Problem went away in subsequent updates ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/623593 Title: package

[Bug 623593] Re: package nvidia-current 256.44-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build

2010-08-24 Thread Charles Manning
** Attachment added: ".proc.driver.nvidia.cards.0.txt" https://bugs.launchpad.net/bugs/623593/+attachment/1516516/+files/.proc.driver.nvidia.cards.0.txt ** Attachment added: ".proc.driver.nvidia.registry.txt" https://bugs.launchpad.net/bugs/623593/+attachment/1516517/+files/.proc.driver.n

[Bug 623593] [NEW] package nvidia-current 256.44-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build

2010-08-24 Thread Charles Manning
Public bug reported: This happened while installing http://kernel.ubuntu.com/~kernel- ppa/mainline/daily/current/linux- image-2.6.36-999-generic_2.6.36-999.201008241121_i386.deb ProblemType: Package DistroRelease: Ubuntu 10.10 Package: nvidia-current 256.44-0ubuntu1 ProcVersionSignature: Ubuntu 2

[Bug 614712] Re: dconf-service crashed with signal 5 in g_closure_invoke()

2010-08-18 Thread Charles Manning
OK This in itself is perhaps not a bug, but this is what popped up when trying to do some software installation. The SIGABRT perhaps is what caused the installation to crap out. Trying to install from the standard A3 maverick x86 iso is a lost cause. A bit of a let down after 8.04..9.04 were so sl

[Bug 58307] Re: --append-to-version made it fail

2010-08-15 Thread Charles Manning
Actually this fails even without --append-to-version -- --append-to-version made it fail https://bugs.launchpad.net/bugs/58307 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com http

[Bug 58307] Re: --append-to-version made it fail

2010-08-15 Thread Charles Manning
Got exactly the same problem here... == making target debian/stamp/build/kernel [new prereqs: vars]== This is kernel package version 12.032. The changelog says we are creating 2.6.35custom However, I thought the version is 2.6.35custom+ exit 1 Anyone know of a work around? -- --append-

[Bug 524366] Re: Regression: CRC error an i386

2010-05-13 Thread Charles Manning
gzrecover foo.tar.gz does not generate a fixed gz file. It will generate a file called foo.tar.recovered which is not a gz file. If you want to make a new gz file you will have to do something like gzrecover foo.tar.gz mv foo.tar.recover new-foo.tar gzip new-foo.tar Now you have new-foo.tar.gz w

[Bug 524366] Re: Regression: CRC error an i386

2010-05-12 Thread Charles Manning
There is a manual workaround that works, but is sucky. sudo apt-get install gzrt gzrecover foo.tar.gz That will give you foo.tar.recovered -- Regression: CRC error an i386 https://bugs.launchpad.net/bugs/524366 You received this bug notification because you are a member of Ubuntu Bugs, which i

[Bug 524366] Re: Regression: CRC error an i386

2010-05-11 Thread Charles Manning
Is there some way to go back to a previous version of gzip + dependencies apart from rolling back to 9.10? -- Regression: CRC error an i386 https://bugs.launchpad.net/bugs/524366 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu

[Bug 524366] Re: Regression: CRC error an i386

2010-05-11 Thread Charles Manning
Fedora has the same problem: https://bugzilla.redhat.com/show_bug.cgi?id=588644 The suggestion there is that this is caused by a recent rsyc patch. ** Bug watch added: Red Hat Bugzilla #588644 https://bugzilla.redhat.com/show_bug.cgi?id=588644 -- Regression: CRC error an i386 https://bugs.l

[Bug 209414] Acer 4315 wifi proken on Hardy

2008-05-06 Thread Charles Manning
*** This bug is a duplicate of bug 182489 *** https://bugs.launchpad.net/bugs/182489 I had this bug on an Acer 4315 too. corrected by adding the line: blacklist ath_pci to /etc/modprobe.d/blacklist What is really odd is that previous versions of the file had this blacklist entry but it go