nvidia-173 pulls in postfix

Bug #661568 reported by Jeff Lane on 2010-10-16
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-173 (Ubuntu)
High
Unassigned
Maverick
High
Unassigned
Natty
High
Unassigned

Bug Description

attpemted to install nvidia-173 and nvidia-current via jockey-gtk on a Dell Dimension 9200.

On both occasions, an error dialog opened that said simplly:

SystemError: InstallArchives() failed.

after seeing that, I'd close jockey, re-run jockey and it would now show the driver as actually installed and activated and in use.

However, no reboot or restart of X was ever initiated or suggested.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: jockey-gtk 0.5.10-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Fri Oct 15 22:50:49 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Dell Inc. Dell DXP061
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=35ff70be-7fb4-40ed-ac62-17aff3d8dbf7 ro quiet splash initcall_debug
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: jockey
dmi.bios.date: 03/23/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.3.1
dmi.board.name: 0CT017
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.3.1:bd03/23/2007:svnDellInc.:pnDellDXP061:pvr:rvnDellInc.:rn0CT017:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Dell DXP061
dmi.sys.vendor: Dell Inc.

Jeff Lane (bladernr) wrote :
Jeff Lane (bladernr) on 2010-10-16
tags: added: pcert

I should also add that while jockey-gtk thought the driver was installed
after the failure, the nVidia control center was not installed, and I
could not open the Monitors applet from the Preferences menu. All
attempts to do so ended with a box telling me I had to use the nVidia
tool, which failed to get installed.

Ameet Paranjape (ameetp) on 2010-10-18
Changed in jockey (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Changed in jockey (Ubuntu Maverick):
status: New → Triaged
importance: Undecided → High
Ameet Paranjape (ameetp) on 2010-10-18
Changed in jockey (Ubuntu Maverick):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)

Unfortunately the log does not show the particular apt error. Can you please give me the output of

  sudo apt-get install nvidia-173

?

Changed in jockey (Ubuntu Maverick):
assignee: Canonical Desktop Team (canonical-desktop-team) → Martin Pitt (pitti)
status: Triaged → Incomplete
Changed in jockey (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → nobody
status: Triaged → Incomplete
Jeff Lane (bladernr) wrote :

I've attacked the logs from installing nvidia-173 via apt get.

Looking at the logs, it appears the errors are related to postfix... why does postfix get installed? I've noticed this with many packages I've installed. If I wanted postfix, I would have installed postfix... but I digress.

So here's what I noticed from installing nvidia-173 via apt-get:

* I am never prompted to restart X or reboot to make sure the driver is installed.
* Postfix errors (when I was prompted, I chose "No Configuration" as I did not want or need postfix
* In this latest try, the nVidia settings tool DID get installed, but appears under Administration, not Preferences, where the system default tool resides.
* even after rebooting the system and ensuring that the nvidia driver was loaded (via lsmod, of all things), the nVidia settings tool errored and advised me to run nvidia-xconfig and restart X because it thought I was not running the nvidia driver (though when I tried to run the "Monitors" app from system/preferences I was told I was running nVidia and needed to use the nVidia tool.

Jeff Lane (bladernr) wrote :

By the way, I just looked in Xorg.0.log and even after a reboot it is still loading the Nouveau driver (while doing an lsmod shows nvidia listed as a running kernel module)...

So that explains why nVidia Settings won't run...

Changed in jockey (Ubuntu):
status: Incomplete → Triaged
Changed in jockey (Ubuntu Maverick):
status: Incomplete → Confirmed
Ameet Paranjape (ameetp) on 2010-10-18
Changed in jockey (Ubuntu Maverick):
status: Confirmed → Triaged
Martin Pitt (pitti) on 2010-10-22
summary: - jockey throws error and says driver install failed yet then shows driver
- as activated
+ nvidia-173 pulls in postfix
affects: jockey (Ubuntu Maverick) → nvidia-graphics-drivers-173 (Ubuntu Maverick)
Changed in nvidia-graphics-drivers-173 (Ubuntu Maverick):
assignee: Martin Pitt (pitti) → nobody
Jeff Lane (bladernr) wrote :

Martin,

FWIW, in case they are considered separate projects, this also affects nvidia-current. Jockey gave me a choice between nvidia-173 and nvidia-current and both options demonstrate the same issue.

Jeff Lane (bladernr) wrote :

This is not related specifically to nvidia packages either. I just found this in a completely different scenario.

This time, doing cert testing on one of the systems in the Montreal DC. The scenario:

Opened a QuickTime movie with Movie Player (via Checkbox). Default Movie Player has no codec to watch QT and proposes to install the gstreamer0.10-plugins-bad and gstreamer0.10-ffmpeg. During the course of installing the two gstreamer packages, again, Postfix is pulled and installed. When prompted to choose a postfix configuration, I left it at the default "No Configuration" and again, I got the failure as noted previously with the two nVidia packages.

I also noticed the same errors about bsd-mailx as well...

Bryce Harrington (bryce) wrote :

I see that this is nominated for Natty, however has anyone tested it on natty so far? If not, maybe this target should be dropped. The bug sounds like something which might be release-specific, but I'm not sure.

Changed in nvidia-graphics-drivers-173 (Ubuntu Natty):
status: Triaged → Incomplete
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Andy Whitcroft (apw) on 2011-01-28
Changed in nvidia-graphics-drivers-173 (Ubuntu Natty):
status: Incomplete → Won't Fix
Changed in nvidia-graphics-drivers-173 (Ubuntu):
status: Incomplete → Opinion
JC Hulce (soaringsky) wrote :

This bug affects Ubuntu 10.10, Maverick Meerkat. Maverick has reached end-of-life and is no longer supported, so I am closing the bugtask for Maverick. Please upgrade to a newer version of Ubuntu.
More information here: https://lists.ubuntu.com/archives/ubuntu-announce/2012-April/000158.html

Changed in nvidia-graphics-drivers-173 (Ubuntu Maverick):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers