Jaunty has reached end-of-life, so I'll close this report. The bug is
marked as being fixed in later versions of Ubuntu
** Changed in: update-manager (Ubuntu Jaunty)
Status: Triaged = Won't Fix
** Changed in: update-manager (Ubuntu Jaunty)
Assignee: Alberto Milone (albertomilone) =
** Branch linked: lp:ubuntu/update-manager
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package update-manager - 1:0.120
---
update-manager (1:0.120) karmic; urgency=low
* The 'Ready for karmic' version
* DistUpgrade/DistUpgradeController.py:
- do not fail in partial upgrades if apport must be
enabled (LP: #357755)
- when
** Tags added: jaunty regression-release
** Tags removed: regression-potential
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I would normally have restricted enabled. However I use my ISP's mirror
of the ubuntu repository normally , and this gets disabled at the start
of the upgrade.
In this case shouldnt update manager enable the restricted when it
re-enables the official repo's?
On 04/17/2009 11:49 PM, Martin
OK, so if restricted was disabled, then the only thing update-manager
could do is to warn and offer to enable it again.
Since this seems to be a corner case with -nv and a corner case with
local configuration, I take it off the release radar.
** Changed in: xserver-xorg-video-nv (Ubuntu Jaunty)
I should be more clear, I commited a fix that comments out Driver
nvidia in xorg.conf instead of rewriting it. It should probably also
warn the user that he is using a restricted driver but does not have
restricted enabled. but that is not done yet.
--
nvidia -177 needs to be transitioned to
The -nv not working on this hardware is an unrelated issue and should
be reported separately. If the user was using the proprietary driver
before, the upgrade should keep it, otherwise it'd be a functionality
regression either way.
** Changed in: xserver-xorg-video-nv (Ubuntu)
Status: New
ok so I probably should pay more attention during the upgrade process
next time :) tho I am sure there were nvidia-glx packages still
installed after the upgrade (and not 180) maybe they were just the older
ones, I was using nvidia-glx-177 in intrepid, and at some stage was
using -envy
Looking at the logs it seems nvidia-glx-177 got removed and the driver
in xorg.conf changed to nv. This is expected behavior if no other
driver can be found that supports this card. So it seems the problem is
really the nv driver (that is used on the livecd by default and having
problems as well).
yes I do recall there was an issue with ca-certificates during the
upgrade, needless to say I got slightly distracted when X wouldn't
start and forgot all about it.
On 15/04/09 18:49, Michael Vogt wrote:
Looking over the logs, I see there is a unreleated problem:
...
Setting up
There is a additional solution:
The oldDrivers should just be a file as well in nvidia-common instead of part
of the source
then u-m can just extract them as during build time (just as its doing now with
the modalias files).
--
nvidia -177 needs to be transitioned to -180 on upgrade
Looking over the logs, I see there is a unreleated problem:
...
Setting up ca-certificates (20080809) ...
Xlib: extension Generic Event Extension missing on display :0.0.
Xlib: extension Generic Event Extension missing on display :0.0.
Xlib: extension Generic Event Extension missing on
I was looking not carefully enough, update-manager is already including a copy
of the jaunty nvidia detector and the nvidia-glx-177 is correctly identified
and removed. So the problem is really:
a) why nv.selectDriver() did not pick nvidia-glx-180
b) should we use vesa instead of nv for certain
It turns out that (a) is not selected because restricted is not
enabled
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
In conclusion we found 2 different bugs.
1) If restricted is disabled, Update Manager won't know what driver to
select, in which case it should simply comment out the Driver line in xorg.conf
so that X.org can use an open source driver which works (or is supposed to
work) with the card.
2)
** Also affects: xserver-xorg-video-nv (Ubuntu)
Importance: Undecided
Status: New
** Package changed: nvidia-common (Ubuntu Jaunty) = update-manager
(Ubuntu Jaunty)
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug
The update-manager problem is fixed in lp:~mvo/update-manager/post-
jaunty
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Alberto, indeed for more complicated cases we can only rely on update-
manager.
apt.log has lots of
ERROR:root:NvidiaDetector can not be imported No module named
NvidiaDetector.nvidiadetector
which is most probably the cause of the failed transition here. This
might be the cause or followup:
Martin, the following problem depended on Python but, according to doko it's
fixed now:
ERROR:root:NvidiaDetector can not be imported No module named
NvidiaDetector.nvidiadetector
As regards this error:
ERROR:root:NvidiaDetection returned a error: dir ./modaliases/ not found
it looks like only
** Attachment added: /var/log/dist-upgrade files
http://launchpadlibrarian.net/25326641/dist-upgrade.logs.tar.bz2
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs,
Larrin: Nvidia dropped the support for 177 and there's nothing we can do
about it, other than migrating users to 180.
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs,
Martin:
yes, that could be done (in this very specific case) but it would still be nice
to see what happened.
In this case the transition can be smooth but usually there is no such
clear transition to new drivers. For example what happens if 180 is no
longer supported and part of the cards that
I just tried to upgrade to Jaunty from Intrepid using Nvidia 177. 173
had issues with buggy scrolling and 180 freezes ALL the time. Now that I
have Jaunty installed there is no option to install 177. It is not
supported on AMD64. That's odd because it was support and worked fine in
Intrepid.
** Changed in: nvidia-common (Ubuntu Jaunty)
Milestone: None = ubuntu-9.04
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Tim: what's the output of this command?
nvidia-detector
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
$ nvidia-detector
none
On 09/04/09 18:02, Alberto Milone wrote:
Tim: what's the output of this command?
nvidia-detector
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
the fact that it returns none (now that 177 is no longer installed) is
ok.
nvidia-common is already used by Update Manager to migrate drivers from
obsolete versions to more appropriate versions. I wonder why this didn't
work.
Michael: any ideas?
--
nvidia -177 needs to be transitioned to -180
If I force the installation of driver 177 in Jaunty and I type nvidia-detector
I get this:
$ nvidia-detector
nvidia-glx-180
which means that nvidia-glx-180 should be installed instead.
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You
Tim: did you upgrade your system using Update Manager or did you use the
command line?
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I upgraded using update manager.
nvidia-detector (nvidia-common package) was not installed just before
when I tried to run it. All though I may have removed it when I was
removing all the old drivers to get things working after the upgrade,
not sure.
On 09/04/09 21:01, Alberto Milone wrote:
I still think it would be more robust to have transitional -177
packages just depending on the -180 ones. This will ensure that people
using apt-get dist-upgrade won't end up with an unbootable system, and
is probably also more reliable than the migration in u-m. The latter
is still a good idea,
32 matches
Mail list logo
