Jockey has been superseded by software-properties, which now handles
third-party driver configuration.
** Changed in: jockey (Ubuntu Precise)
Status: Incomplete => Invalid
** Changed in: jockey (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
** Tags removed: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
To manage notifications about this bug go to:
https:
Is this still a problem is Precise?
** Changed in: jockey (Ubuntu Oneiric)
Status: Confirmed => Won't Fix
** Changed in: jockey (Ubuntu Precise)
Status: Triaged => Incomplete
** Changed in: jockey (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification
** Changed in: jockey (Ubuntu Oneiric)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
To
Hi Martin,
you must be the bearer of knowledge, so why does this not get shared
with less experienced but interessted users?
bug 948053 Comment #42, 5.5.2012 : Have asked to publish this issue at
least in the release-notes.
If I don't find a hint there I've got to think everything will be going
Dropping rls-p-tracking. We currently only have one working driver
anyway (-current), so this should not be a dealbreaker and can also be
fixed in an SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
The logs still say that "/usr/lib/nvidia-173/ld.so.conf" is the current
alternative (from NvidiaDetector.alternatives.MultiArchUtils), this
seems to be the root cause of it. I'm afraid this requires an actual
nvidia system to reproduce and debug. Alberto, can you see what's wrong
here?
** Changed
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
To manage notifications about this bug go to:
h
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
To manage notifications about this bug go t
** Changed in: jockey (Ubuntu Precise)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3r
That's interesting :-)
As requested
ootest@ootest-VGN-AR51SU:~$ python -c 'from NvidiaDetector.nvidiadetector
import NvidiaDetection; print NvidiaDetection().selectDriver()'
nvidia-current
As you can see, the output says nvidia-current, even though the nvidia-
settings screen clearly shows the 1
Can you please give me the output of this command (from a Terminal):
python -c 'from NvidiaDetector.nvidiadetector import NvidiaDetection;
print NvidiaDetection().selectDriver()'
Thanks!
** Changed in: nvidia-graphics-drivers-173 (Ubuntu Precise)
Status: New => Invalid
** No longer aff
I've unduped bug #893760 to focus on the -173 build issue, which
appears to be specific to precise. This bug report can focus on the
issue with jockey picking -173 instead of -current, which appears to
affect oneiric and precise.
** Changed in: jockey (Ubuntu Precise)
Status: Incomplete
Ok, re-installed OO again and the Nvidia 173 driver was installed again.
Output of jockey-text --list is [code]ootest@ootest-VGN-AR51SU:~$ jockey-text
--list
xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Enabled, In
use)
xorg:nvidia_173_updates - NVIDIA accelerated graphics d
oops, didn't know code tags don't work here!
** Attachment added: "jockey.log"
https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/876499/+attachment/2608219/+files/jockey.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Quackers [2011-11-25 16:49 -]:
> I could install oneiric again and then post the outputs you request
> if you think that might help.
Either from oneiric or a precise install would be fine. It should tell
me more about why it selects the 173 driver. Thanks!
--
You received this bug notificati
My oneiric install has now been upgraded to precise so presumably my logs won't
help. In fact /var/log/jockey.log is empty.
I could install oneiric again and then post the outputs you request if you
think that might help.
--
You received this bug notification because you are a member of Ubuntu
There seem to be two different issues here:
The -173 version does not build:
Nov 21 19:42:40 ubuntu ubiquity: First Installation: checking all kernels...
Nov 21 19:42:40 ubuntu ubiquity: Building only for 3.1.0-2-generic
Nov 21 19:42:40 ubuntu ubiquity
As for the wrongly detected driver version, can someone with an affected
NVidia system please attach /var/log/jockey.log after the failed
install? It should be in the target system, i. e. after reboot, not in
the live environment. It would also be helpful if you could give me the
output of
jocke
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-173 (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-173 (Ubuntu Oneiric)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Thanks for all the info Bryce, and the extra bugs. The problem seems to
have gone largely un-noticed previously, possibly because most people
don't check that box during installation? I know I don't usually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bug #888273 has the same warning (against 11.10), although description
is ambiguous if it was encountered under same conditions as this.
** Description changed:
During 11-10 install on checking the 3rd party programs box the Nvidia 173
driver is installed.
However my graphics card uses the n
I have a sense that it is selecting -173 because it's the last thing in
the list. However I'm not spotting in the code where exactly that list
might be.
The error message is from get_modinfo() in detection.py.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
In digging through ubiquity, it looks like ubiquity hands off control to
jockey via dbus, and it seems jockey runs into trouble. In the log it
seems jockey is unable to find (or create?) it's cache, and so I wonder
if that may be what's steering it off the cliff.
** Package changed: ubiquity (Ubu
Alright, well it definitely affects precise. I'll add an oneiric tag so
once the issue is discovered it can be evaluated for possible SRU.
** Also affects: nvidia-graphics-drivers (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu Oneiric)
Importanc
Yes, at the time I was doing a fresh install of 11-10 which was to be upgraded
to 12-04 for testing.
I checked the box for the 3rd party drivers and after installation and
rebooting I found that the 173 driver had been installed rather than the
nvidia-current driver, which is the correct driver
Was able to reproduce this bug myself (#893760) after a fresh install of
Precise.
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Triaged
** Changed in: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided => Hi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/8764
Quackers, can you explain what you mean by "This is not a 12-04 bug,
it's a 11-10 installer bug"? Are you reproducing this fresh installing
Oneiric onto a system? I'm definitely seeing this on Precise but don't
recall running into it for Oneiric install testing.
--
You received this bug notific
I'm setting the priority of the -nvidia bug task to High, although I
think this isn't a fault in the driver itself, but rather an error in
the algorithm selecting the binary package to be installed. (Ubiquity
presumably??)
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed
Here's the installer logs
** Attachment added: "/var/log/installer/syslog (Ubiquity syslog)"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/876499/+attachment/2605304/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checkin
Just installed 12.04. Same issue but worse. Could not get to graphical screens
at all. Alt-f2 gave me command line. Did updates Nov 10, 2011 and still would
not fully boot.
Uninstalled 173, installed nvidia-current , finally got to gui, but it used
default video as it then popped up saying I cou
Nothing yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
To manage notifications about this bug go to:
https://bugs.launc
The additional drivers now shows three entries. The installed 173,
current and an updated which I gather is the current but will be
updated?
Is this left over from alpha or beta as it seemed then the only driver
was the 173 as there were issues with everything else?
--
You received this bug noti
while the 173 driver is what is installed during installation , after
install nvidia-current shows as recommended by additional drivers .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
In
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
This is not a 12-04 bug, it's a 11-10 installer bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
To manage notifications a
41 matches
Mail list logo
