Jockey failed to properly install fglrx driver ("post-release updates"): "Sorry, installation of this driver failed"

Bug #891537 reported by Daniel Hahler
40
This bug affects 9 people
Affects Status Importance Assigned to Milestone
jockey (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have tried to install the fglrx proprietary driver, when Jockey failed after downloading it with the following error dialog:
"""
Sorry, installation of this driver failed.
Please have a look at the log for details: /var/log/jockey.log
"""

Installing the normal (non-"post-release updates") driver/variant worked.

The tail of the error log is:

2011-11-17 10:29:49,149 WARNING: /sys/module/fglrx_updates/drivers does not exist, cannot rebind fglrx_updates driver
2011-11-17 10:29:49,233 ERROR: xorg:fglrx_updates: get_alternative_by_name(fglrx-updates) returned nothing
2011-11-17 10:29:49,318 DEBUG: fglrx.enabled(fglrx_updates): target_alt None current_alt /usr/lib/nvidia-current/ld.so.conf other target alt N
2011-11-17 10:29:49,318 DEBUG: fglrx_updates is not the alternative in use
2011-11-17 10:29:49,352 DEBUG: fglrx.enabled(fglrx_updates): target_alt None current_alt /usr/lib/nvidia-current/ld.so.conf other target alt N
2011-11-17 10:29:49,352 DEBUG: fglrx_updates is not the alternative in use

I am attaching a screenshot of Jockey after the fact and the whole log.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: jockey-gtk 0.9.4-0ubuntu10
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Thu Nov 17 10:32:22 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: FUJITSU ESPRIMO P5645
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=2aaafb6d-3313-4ed7-8dc0-7bf481eb98b5 ro quiet splash vt.handoff=7
SourcePackage: jockey
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2011
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: 6.00 R1.11.2981.A1
dmi.board.name: D2981-A1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D2981-A1
dmi.chassis.type: 6
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: C$PIP3
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00R1.11.2981.A1:bd01/17/2011:svnFUJITSU:pnESPRIMOP5645:pvr:rvnFUJITSU:rnD2981-A1:rvrS26361-D2981-A1:cvnFUJITSU:ct6:cvrC$PIP3:
dmi.product.name: ESPRIMO P5645
dmi.sys.vendor: FUJITSU

Revision history for this message
Daniel Hahler (blueyed) wrote :
Revision history for this message
Daniel Hahler (blueyed) wrote :
description: updated
summary: - Jockey failed to properly install fglrx driver
+ Jockey failed to properly install fglrx driver: "Sorry, installation of
+ this driver failed"
Daniel Hahler (blueyed)
summary: - Jockey failed to properly install fglrx driver: "Sorry, installation of
- this driver failed"
+ Jockey failed to properly install fglrx driver ("post-release updates"):
+ "Sorry, installation of this driver failed"
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in jockey (Ubuntu):
status: New → Confirmed
Revision history for this message
Jack Foy (jfoy) wrote :

I believe this is not actually a duplicate of 873058 bug as marked, though it is a duplicate of https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/870560 (also incorrectly flagged as a duplicate of 873058).

It looks like /usr/share/jockey/handlers/fglrx.py in package jockey-common expects the package fgrlx-updates to create a module named 'fglrx-updates', but the module generated by building that package is actually named 'fglrx'. See https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/825339

Can someone who knows this code comment on this issue? How can we get the jockey-common and fglrx-updates maintainers to agree on an interface?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.