Ubuntu 10.10 where is software sources

By default, none of the rows in a software list view should be selected. If no item is selected, pressing the Down arrow key should select the first row, and conversely pressing the Up arrow key should select the last row. If the view does not allow selection, the arrow keys should scroll the view without highlighting rows. Unless otherwise specified, a software list view should always have a vertical scrollbar. A software list view should never have a horizontal scrollbar.

Software sources In most cases, the collection of software that USC presents should consist of the aggregate of available software items from all enabled software sources, plus any software currently installed that has no known source.

Otherwise, the same label as is used in the file manager. The installed software sources should consist of all those items in this list from which you have installed any software. Install a package from that PPA. Test case: sc Download and install a standalone. Determining information about software items Most information about a package — its title, short name, summary, and license info — should come from Aptdaemon. These are the exceptions: Icon and genre The icon should be the usual icon for the package , except that unless otherwise specified, a package that is currently installed should have its icon overlaid in the bottom left corner with the installed checkmark emblem.

If you want this to be more specific bug , do what you can to get DEP-5 implemented. If an item has a secondary category, it may also have a secondary subcategory. Each category, and each subcategory, should have its own icon. Ideas were invited on the Classification page. If it has a Section: that matches one of the subcategories listed above, then: Use the Section: value to determine the subcategory from the table.

If it has a. If it has a Section: that matches one of the categories listed above, then: Use the Section: value to determine the category from the table. The item has no secondary category or subcategory. The requirements should be comma-separated, each preceded by a text-colored checkmark if it detectably meets that requirement, an error-colored cross if it detectably fails, or nothing if the requirement is currently untestable.

In addition, whenever the computer detectably does not meet the requirements, immediately above the installation state bar should be an extra bar containing a warning specific to the unmet requirements, with a icon aligned with the button below. Activating that command should focus the search field, and even if it is focused already select its entire contents.

Inside the leading end of the field should be a symbolic magnifying glass icon. Clicking the icon should focus the field and select its entire contents. When and only when the search field is not empty, the trailing end of the field should have a symbolic clear icon.

Clicking the icon should focus the field and clear its contents. Besides the normal behavior for text fields, whenever the insertion point caret is at the trailing end of the search field, pressing the Down arrow key should focus the contents of the main pane and select the first item — such as the first category in the home screen , or the first result in any list of search results. Interpreting search text When searching anywhere in USC, any word in the search string that is followed by a space or punctuation should be treated as a a complete word, while any word that is not should be treated as if it may be either a complete word or the beginning of a word.

For the sake of people who are unfamiliar with how they should use the search, there should be a greylist of words that are downplayed when searching. In any other search that contains one or more greylisted words, the greylisted words should be ignored: only the words that are not greylisted should be searched for.

However, once the results are chosen, the presence of any greylisted words should cause a result to appear higher in the list. Instead, provide a list of words in your language that people are likely to include in a search but that should normally be ignored in the search. USC should return exactly the same results for both searches, though possibly in a different order. So clicking Back is one way to clear a search. Type Ctrl F; the search field should be focused.

Press the down arrow key once; Firefox should be selected in the results. Choose Back again; USC should return to the home screen. Suggestions: Try the 2 items in Internet that match.

The rest of the main pane should contain search results for that scope. For example, in a subcategory, the results should be limited in scope to that subcategory. If the search terms exactly match a package name, that package should be returned first in the results, even if the package was hidden by default.

Testers You can help us improve the search function by testing it in successive versions. Unlike usual search results, this list should be sorted in exactly the same order as the search string. The bottom of the pane should have an action bar. Nothing should change. If installing the software would involve removing ubuntu-desktop , the package should be treated as uninstallable just as it is with software updates bug Try again in a day or two.

If this problem persists, contact the software vendor. If the Launcher was in auto-hide mode, it should then hide again. Trying to launch the item should do nothing. While the item is installing, the Launcher should show installation progress with an overlaid progress bar. Trying to launch the item should still do nothing. The item should be installed with the standard interface. Otherwise it should be the standard status text for the operation.

If installation was successful, the launcher item should flash and become launchable. Packagers and testers Wait, what? Fifty percent? Perhaps not, but even a progress bar that varies a bit in speed is infinitely more accurate than one that fills up completely only to jump back to zero for the next step.

And you can help us make it even better. Removing software The Remove function should be disabled by default, enabled only when one or more items are selected or you are at an individual software item.

When you request to remove a software item: The Remove function for that item should become disabled, and remain disabled until the removal has been completed or cancelled. USC should handle inconsistent package state if necessary.

The package removal should be presented in the standard way. What about where X depends on a virtual package that A1 or A2 provide? Perhaps show a menu of the options? This applies not just to add-ons but to dependencies too. Maybe checked and disabled?

Maybe checked by default? The list of add-ons for the item should be presented as a series of checkboxes. Recommended add-ons should be listed first alphabetically , then suggested add-ons alphabetically. The package name should be a link that navigates to the software item screen for the package. If the main package is not installed already, the checkboxes for recommended add-ons should be checked by default, while the checkboxes for suggested add-ons should be unchecked by default.

If the main package is installed already, the checkboxes for add-ons that are currently installed should be checked by default, while those that are not should be unchecked by default. If the main package is already installed, whenever the current checkbox values no longer match the add-ons currently installed, an add-ons state bar should appear immediately below the list of checkboxes. Initially, this bar should contain the total price of any newly-selected add-ons e.

But changing add-ons for an installed item should be presented as a separate task for each add-on. If you sign on successfully and USC realizes you have already purchased this item, it should return to the software item screen, which should now be showing the download and installation progress.

Do we need to show more feedback? Once it has loaded completely, the main pane should display the Canonical Payment Service screen for buying the item. Once you complete the payment, USC should return to the software item screen, which should now be showing the download and installation progress. Perhaps highlight the change and ask you to reconfirm. That URL should then redirect to the developer support site, or the Canonical Support form, depending on the reason.

Begin publishing the name and source, for each package installed on this computer, to the OneConf server. Try again in a few minutes. Why are all the programs free?

There is also an online FAQ for issues with purchases. These are based on the questions most frequently asked by real customers: Software Center purchase issues I tried to buy something but it failed. What should I do? How do I reinstall software I've purchased in the past?

Where can I view my purchases and my payment history? Can I get a refund for my Software Center purchase? I had some failed attempts to make a purchase. Could you cancel my incomplete transactions? How can I get more detail about the error? About window The About window should be a standard window not a dialog following the standard Gnome About window layout, using the appropriate application summary.

The Launcher should handle the rest. This item should be enabled only when you are already signed in or when any USC purchases are installed. Activating the item should open a confirmation alert, which lists installed purchases only if there are any. The menu should contain two items, the backport version and the version that would normally be installed, in ascending order.

The default should be the release version, if it is one of the items, otherwise the highest version. Region restrictions For any item which you may not install in your region: The Install command should not be available. A common reason for region restrictions is banning of particular logos or imagery.

Features you can implement These are mini-specifications for new features and other changes that anyone is welcome to implement. Some are more important than others; some are more difficult than others.

If you would like to implement any of them, please do so in a branch and propose it for merging. Once a feature is implemented, the mini-specification here will similarly be merged into the main specification.

Atop the screen for each individual software source should be a header containing the icon and name for the source. Installing from external media bug If you insert a volume that consists of software packages, but is not installation media, Ubuntu Software Center should launch to or navigate to the screen for that volume as an individual source.

If a volume is added as a software channel, Ubuntu should cache all its package details so that you can request installation without having the media inserted. If the media is detectably inserted, the alert should go away automatically. This avoids repetition on the home screen, giving visibility to more items. Its text should be whichever is appropriate of these: Ubuntu has a newer version of this software. Ubuntu has a trusted version of this software.

Launching from multiple standalone. Dragging a software item bug A software item should be draggable, wherever in USC it appears — on the home screen, in any other tile view, in a list view, or for its icon only in the software item screen itself. Otherwise: If the item is already installed, and already in the Launcher, the Launcher item should move to the new location. Otherwise: If the item is already installed, and not already in the Launcher, it should be added to the Launcher at that location.

Otherwise: The icon should appear as a greyed-out item in the Launcher until installation completes or fails. Dragging an item anywhere else, except the Launcher, should drop its icon as a graphic or its title as text. Would you like to review it? The link should begin the review process for that application.

Test case: Install an application for which Backports has a newer version. Enhancement: Launcher item emblem In the Unity launcher, the icon for Ubuntu Software Center should have a badge containing the number of updates, regardless of whether USC is running.

Whenever Ubuntu updates are not available, the checkbox should be both disabled because changing it has no effect and unchecked because no Ubuntu updates will be installed when you update anything else.

Test case: replaces previous test case Install Ubuntu without installing updates. Activating this command should remove the update from the list indefinitely. Smarter ellipsis of software list view items In a software list view , if the secondary text is wider than the space available, it should be ellipsized in the middle, not the trailing end because unique parts of package names are often at the trailing end.

If the item has a custom icon, it should also be copied as both a bitmap and as a vector image if available. Downloading while waiting to install bug When an item to be installed is waiting for other tasks, but the package is not yet downloaded, it should start downloading immediately.

Or maybe when fewer than 3-ish items are already downloading? If you drag the row up or down, the rows for other unstarted tasks should scoot out of the way to show where the dragged row would end up if dropped. As a keyboard equivalent, Ctrl Up and Ctrl Down should, when possible, make the selected task swap places with the previous or next task respectively.

Consistent progress bar for installations and removals Regardless of whether you are installing a free item, installing a for-purchase item, or removing an item, the progress bar in the installation state bar should appear at exactly the same moment: immediately after USC knows that you are authenticated for the action.

Choosing it should copy a Web link for the selected package. Clicking the button should: over two seconds, draw a ring around the interface element e. AppArmor is a security extension similar to SELinux that should provide extended security. In my opinion you don't need it to configure a secure system, and it usually causes more problems than advantages think of it after you have done a week of trouble-shooting because some service wasn't working as expected, and then you find out that everything was ok, only AppArmor was causing the problem.

This feature is only available to subscribers. Get your subscription here. Log in or Sign up. Suggested articles. Your name or email address: Do you already have an account? No, create an account now.

Accept the dependencies by clicking on Mark :. After you've selected the desired packages, click on the Apply button:. The packages are now being downloaded from the repositories and installed.

This can take a few minutes, so please be patient:. To check if the TrueType fonts have been installed correctly, open a word processor like OpenOffice. You should now find your new Windows fonts there:.

This feature is only available to subscribers. Get your subscription here.