Karmic has long since stopped to receive any updates. Marking the Karmic
task for this ticket as "Won't Fix".
** Changed in: nvidia-graphics-drivers-180 (Ubuntu Karmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Karmic is past End of Life, and is no longer supported. As such, this
bug is being marked "Won't Fix" against the Karmic bug task.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in Ubuntu.
https://bugs.launchpad.net/b
I believe this issue is a thing of the past. In any case, if it still
occurs with Ubuntu precise 12.04 or newer, we'd need an updated bug
report. Please file a new report if this still happens.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: Triaged => Fix Released
--
You r
This problem drives me crazy :-(
Whenever a new kernel gets installed I have to boot up with the old kernel and
remove the nvidia driver, then boot into the new kernel and install the driver
again.
PLEASE fix this for Karmic
--
DKMS build fails, but package upgrade still successful
https://bug
I'm going to invalidate the DKMS tasks. This should be less of a worry
in Lucid because DKMS will be more resilient to build failures and
provides an upstart task before GDM gets a chance to go at the system.
Alberto's recommendation about checking for the existence of the kernel
module is about
Honestly I'm not sure what else we can do in the nvidia package other
than checking the existence of the kernel module.
In the postinst script of the nvidia package we check the exit status of
the script that we use to build the module:
case "$1" in
configure)
/usr/lib/dkm
** Also affects: nvidia-graphics-drivers-180 (Ubuntu Karmic)
Importance: Undecided
Status: New
--
DKMS build fails, but package upgrade still successful
https://bugs.launchpad.net/bugs/438398
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Ideally, this known and safe cause of build failure could be
distinguished from real build failures. Does DKMS check that the headers
are actually available (I think it does not)?
In any case this seems to require some special handling, as nvidia
package control file probably cannot instruct dpkg
So the problem with declaring the package as failed if the DKMS build
failed is that it may actually pass or fail depending on how far along
into the updates you are.
Say you are updating to a new linux-headers with a new ABI at the same
time as installing the NVIDIA package.
Well if the NVIDIA p
Interesting, you're right that in such a case the package upgrade should
not be marked as succeeding. This may be exacerbating the situation
when the package fails to build for other reasons.
--
DKMS build fails, but package upgrade still successful
https://bugs.launchpad.net/bugs/438398
You rec
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: New => Triaged
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Importance: Undecided => High
--
DKMS build fails, but package upgrade still successful
https://bugs.launchpad.net/bugs/438398
You received this bug notificati
11 matches
Mail list logo
