Package won't install but it won't give error message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
software-center (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
- I have package "virtualbox-4.0" currently installed
- I try to install package "virtualbox-4.1" by double clicking on the .deb file which I downloaded from http://
This opens the Ubuntu Software Center
- A green checkmark (as if meaning "ok") is shown and below the following message appears "Breaks existing package 'virtualbox-4.0' that conflict: "Virtualbox". But the 'xxxx.deb' provides it via: 'virtualbox'
The second part starting with "But" seems to mean that the package CAN be installed, and most importantly, there is an "Install" button on the right which is not greyed out. Together with the green checkmark this all gives me the confidence that I can safely click "Install" and expect the package to be installed.
- So I click on "Install".
=> Observed behavior: the "install" buttoninstantly greys out and nothing happens. The package is not installed and NO ERROR MESSAGE is shown
Expected behavior: either the package should be installed succesfully, or an error message dialog should appear explaining why it cannot be installed
Or, if the conflict is the reason why the package cannot be installed, the "Install" button should not be shown at all (or should be greyed out from the beginning) and a red cross icon should be shown instead of the green check mark.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: software-center 5.0.3.1
ProcVersionSign
Uname: Linux 3.0.0-15-generic i686
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sun Jan 8 15:46:50 2012
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: software-center
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (31 days ago)
description: | updated |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.