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 Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
Status in “jockey” package in
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 Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking
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 Desktop
Packages, which is subscribed to jockey in Ubuntu.
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 Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
Status in “jockey” package in
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed by checking 3rd party box
Status in “jockey” package
** Changed in: jockey (Ubuntu Precise)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/876499
Title:
Incorrect Nvidia driver installed
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
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
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 Desktop
Packages, which is subscribed to jockey in Ubuntu.
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 Desktop
Packages, which is subscribed to jockey in Ubuntu.
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 Desktop
Packages, which is subscribed to jockey in 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
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
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
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
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 Desktop
Packages, which is subscribed to jockey
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
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 Desktop
Packages,
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
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
24 matches
Mail list logo
