<issue_start>username_0: A lot of applications like Firefox, Chrome etc, get closed when I accidentally press `Ctrl`+`Q` instead of `Ctrl`+`W` because of the proximity of the *`Q`* and *`W`* keys on the keyboard. Is there a way this shortcut can be removed or reset on a system wide basis?<issue_comment>username_1: Probably inserting the shortcut under System -> Preferences -> Keyboard Shortcuts and "disabling" it should do the trick.
Upvotes: 3 <issue_comment>username_2: The best way is to disable the keyboard setting in your specific application. For Firefox there is an extension [keyconfig](http://forums.mozillazine.org/viewtopic.php?t=72994). This allows you to change keyboard settings.

If you want to disable `Ctrl`+`Q` for your whole system, I would suggest to make a new setting:

1. Go to System -> Preferences -> Keyboard settings
2. Click **Add**
3. Give it a name like *fake setting* and enter `/bin/false` as command. Apply your changes.
4. Click on '**Disabled**' and press `Ctrl`+`Q`.

Now you should have a new entry with your applied name and your keyboard setting. Every time you press `Ctrl`+`Q` your system will run the command `/bin/false` which basically does nothing. So this is a workaround to disable the setting.
Upvotes: 8 [selected_answer]<issue_comment>username_3: You can go to System → *Preferences* → *Keyboard Shortcuts* and assign this combo to an unused action. For example I assigned `Ctrl`+`Q` to switch to workspace 12 (no, I don't have 12 workspaces).

As a result this system wide setting overrides application one and `Ctrl`+`Q` no longer closes Firefox (likely the combo never reaches Firefox). It just does nothing.
Upvotes: 3 <issue_comment>username_4: If `Ctrl` + `Q` closes the keyboard settings window, like it did for me, youi can do the following:

1. Set the shortcut to another value.
2. Close the window and wait until the updated shortcut appears somewhere in `~/.gconf/desktop/gnome/keybindings/*`.
3. Open that file and edit the `stringvalue` of that command to read `<Primary>q`.
4. Reboot the PC.

This worked for me as opposed to the accepted answer.
Upvotes: 2 <issue_comment>username_5: Here is a command-line version of the already-supplied GUI version. On some systems `Ctrl`+`Q` will close the accelerator input window without setting the shortcut, so this can be needed:

```
gconftool-2 --type string --set /desktop/gnome/keybindings/inhibit_ctrl_Q/name "Inhibit Ctrl+Q"
gconftool-2 --type string --set /desktop/gnome/keybindings/inhibit_ctrl_Q/action /bin/false
gconftool-2 --type string --set /desktop/gnome/keybindings/inhibit_ctrl_Q/binding "q"

```

Note that this solution is for GNOME 2/Unity. A similar solution should be possible with `gsettings` for GNOME 3.
Upvotes: 2 <issue_comment>username_6: For me, disabling the `Ctrl`+`Q` shortcut system-wide is not the perfect solution, because it prevents applications other than Firefox, Chrome etc., to be notified when you use that shortcut. For example, IntelliJ IDEA uses `Ctrl`+`Q` as a default binding to show quick documentation pop-up.

If you are looking for a Firefox-only solution, I highly recommend [Disable Ctrl-Q Shortcut](https://addons.mozilla.org/en-us/firefox/addon/disable-ctrl-q-shortcut/) plugin. In my opinion it's a better option than [keyconfig](http://forums.mozillazine.org/viewtopic.php?t=72994) mentioned by @username_2 because its source is available on [GitHub](https://github.com/choobin/dcqs), while keyconfig is available only as a binary.
Upvotes: 0 <issue_comment>username_7: On Linux with Firefox Quantum, there is currently a [bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1325692) that prevents extensions and explicit configuration from changing a built-in shortcut such as `Ctrl`+`Q`.

A workaround is to block it at the system level by e.g. installing the script from <https://github.com/sasawat/firefox-ctrl-q-workaround> and assigning it as the action of `Ctrl`+`Q` as a global shortcut.
Upvotes: 1 <issue_comment>username_8: My current workaround is to create a new shortcut in System Settings → *Keyboard* → *Shortcuts*. If the shortcut is accidentally pressed, we receive an informative message.

* Title: *Quit Prevention*
* Command: `notify-send 'Dear idiot' "Don't press ctrl-Q"`
* Shortcut: `Ctrl`+`Q`

This disables the command system-wide, however, which might be an acceptable tradeoff depending on your use case.

The above is Tested in Ubuntu 16.04.
Upvotes: 2 <issue_comment>username_9: For newer Firefox versions, you can disable it as follows:

1. Go to `about:config`.
2. Set `browser.quitShortcut.disabled` to `true`.
3. Restart the browser.

For other applications, the steps will differ. Chrome no longer closes on `Ctrl`+`Q`, so there is no need to change anything there. Note that in many other applications, `Ctrl`+`Q` is a useful shortcut, so disabling it system wide would break that functionality.
Upvotes: 2 <issue_comment>username_10: My way is going to System → *Preferences* → *Keyboard Shortcuts* (yeah I know it's not there). Here you add one more shortcut with the *Name* "Do nothing", with a random *Command* with the *Shortcut* `Ctrl`+`Q`. Then the deadly combo should not bother you anymore anywhere.

[![screenshot](https://i.stack.imgur.com/E4vMT.png)](https://i.stack.imgur.com/E4vMT.png)
Upvotes: -1


<issue_start>username_0: It's great that the indicator applet tells me I have 2 hours and 12 minutes of battery left, or that it will be charged in 1 hour 8 minutes, but I might well change my pattern of usage during that time and am frankly not confused by percentages.

How do I make the applet show a percentage charged or discharged instead?<issue_comment>username_1: I don't think the indicator shows that information yet.

You can click on the menu entry which says "X hours YY minutes left to (dis)charge" and it will open the battery profile dialog. That one has percentages under "Laptop Battery -> Details (scroll to bottom)"
Upvotes: 2 <issue_comment>username_2: The percentage was intentionally removed by the power house that is the Canonical design team.
See the comments by MPT here: <http://design.canonical.com/2010/04/battery/>
Upvotes: 1 <issue_comment>username_3: <NAME>, an interface designer for Canonical's Ubuntu team, [in his blog comments](http://design.canonical.com/2010/04/battery/) this April wrote "I think the only point in showing a percentage charge is so that a human can get an idea of how much time is left. But we have computers to do those sort of calculations now. If a battery’s estimated time remaining is wrong, its percentage will be even less informative."

There is also a comment on [the Ubuntu wiki](https://wiki.ubuntu.com/BatteryStatusMenu) that says "This coloring is deliberately time-based, not percentage-based; how much time you have left is more important than how long the battery can theoretically last."

![Mockup of new battery indicator menus](https://i.stack.imgur.com/OpKmw.jpg)
Upvotes: 5 [selected_answer]<issue_comment>username_4: You can install the Battery-Stats applet, which will replace the Power-Managers's applet with more information and some power-management options as a bonus.

```
sudo apt-get install battery-stats
battery-stats-collector

```

Then see /var/log/battery-stats for sample information.
Upvotes: 3 <issue_comment>username_5: I had this problem, as far as i search there is not any way to solve this problem in unity panel but i solved it buy installing cairo-dock. It has some theme that can show percentages over its image.

You can install cairo-dock from repository

```
sudo apt-get install cairo-dock

```

then after running it:

1. in cairo-dock configuration go to add-ons tab.
2. tick "Power Manager" applet and click apply button.
3. in the dock right click on "Power Manager" applet and from "power manager" menu click on edit button.
4. in shown dialogue goto "Configuration" tab.
5. from first combo bos ("choose the style of disply") select "Gauge".
6. open Gauge section and from "choose one of the available theme" select a theme that show percentages in its image (theme like, "Battery-Mono" , "Battery:MeeGo theme" , "Battery:Oxygen theme" ,...)
Upvotes: 1 <issue_comment>username_6: I just wrote a new applet for the sole task of showing the battery percentage in the panel. It comes as a python script. For more information and to download visit the [github repo for the project](https://github.com/benkaiser/ubuntu_battery_percentage).
Upvotes: 1 <issue_comment>username_7: Add this as a "command" somewhere in your notification area:

```
upower -d | grep percentage: | awk '{print $2} ' | head -1

```
Upvotes: 0 <issue_comment>username_8: Right click applet, choose Configure, select Show percentage.
Upvotes: 1


<issue_start>username_0: Is there a way to remove the File, Edit, View... toolbar from Firefox (so that I will have only the address toolbar visible)?
I think in Windows from version 3.5 you can just right click on the toolbar and you can just unselect it...
I don't have Firefox installed, i use Swiftfox...<issue_comment>username_1: I use the [tiny menu extension](https://addons.mozilla.org/en-US/firefox/addon/1455/) to reduce the menu bar to an icon next to my address bar.
![The back/forward/stop buttons are all hidden when not needed](https://i.stack.imgur.com/iYgCw.png)

Otherwise, you should be able to create a new toolbar and drag the menu bar onto it, then hide that toolbar.
Upvotes: 2 <issue_comment>username_2: Try the [Hide Menubar](https://addons.mozilla.org/en-US/firefox/addon/4762/) addon. The menubar is hidden by default but you can toggle it with the `Alt` key.
Upvotes: 3 [selected_answer]<issue_comment>username_3: I have used Tiny Menu extension in the past, but now I use Compact Menu 2. It works like a charm and you can put the menu anywhere.

<https://addons.mozilla.org/en-US/firefox/addon/4550/>
Upvotes: 0


<issue_start>username_0: Every hour I get an email with error like this,

```
Subject: Cron  root cd / && run-parts --report /etc/cron.hourly

/bin/sh: root: not found

```

Contents of /etc/crontab is as follows, either I remove user "root" or not (6th column), I get the same error.

```
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user  command
11 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
25 6    * * *   test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6    * * 7   test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6    1 * *   test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#

```

There are two files in my cron.hourly directory,

```
$ ll /etc/cron.hourly/
total 0
lrwxrwxrwx 1 root root 25 2009-10-29 09:24 ntpsync -> /home//bin/ntpsync
lrwxrwxrwx 1 root root 28 2009-10-23 10:33 foo -> /home//bin/foo

```

First script reads as follows,

```
$ cat ~/bin/ntpsync
#!/usr/bin/env bash
echo "user: $USER"
if [[ "$USER" == "root" ]] ; then
    ntpdate ntp.ubuntu.com
else
    sudo ntpdate ntp.ubuntu.com
fi

```

Even I remove both scripts in my /etc/cron.hourly/ directory, I still get the same error email every hour. I tried to restart cron and I still get the same error email. The next idea I have is to reboot but I'd avoid that.

```
$ sudo /etc/init.d/cron restart

```

My Ubuntu version is as follows,

```
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu 8.04.1"

```

**Update:** I removed the 6th columns "root" from my /etc/crontab file earlier because when I searched online someone mentioned that could fix the problem. Now I think the problem was that I was messing around with the system crontab config instead of that of the root's.

```
$ sudo crontab -l
# m h  dom mon dow   command
17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )

```<issue_comment>username_1: I know you said you still get the errors after you remove the "root" in the sixth column, but it really looks like the issue.

For example, look at the other lines. They all start with "test". That's not a user, that's the beginning of a command. Removing the "root" would make your command start with "cd".

Especially since the error message says it can't find "root" which is the error you get when you try to run a program that doesn't exist.

So I'd say try removing that again.
Upvotes: 1 <issue_comment>username_2: The default crontab file from the cron package (3.0pl1-100ubuntu2.1 this is the latest version of ubuntu 8.04) looks like this:

```
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user  command
17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )

```

You should just be able to take this and paste it into the file, but you might also want to make sure that you have the latest version of the package. You can do this by doing:

```
apt-get update
apt-get install cron

```

**Update:**

There are two different types of crontab's one is the system's crontab that is located in `/etc/crontab`. This crontab has this fromat:

```
minute hour dayOfMonth month dayOfWeek userToRunAs restOfLineIsCommand

```

The other type is the users crontab's this can be modified by using the `crontab`. The actual configuration is located in `/var/spool/cron/crontabs/USERNAME` and is always executed as the user that owns it, and thous the format of that file is:

```
minute hour dayOfMonth month dayOfWeek restOfLineIsCommand

```
Upvotes: 4 [selected_answer]<issue_comment>username_3: Your `/etc/crontab` looks funny indeed. Every line should actually have a user column actually, which is the funniest part. For example, mine reads:

```
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user  command
17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#

```

By the way, it is usually not a good idea to touch this file. If you need to add more generic crontabs, use `/etc/cron.d` for this. You can try to restore the default configuratino for the cron package with:

```
$ sudo apt-get install --reinstall --yes -o DPkg::Options::=--force-confmiss -o DPkg::Options::=--force-confnew cron

```

and see if it fixes the issue.
Upvotes: 1 <issue_comment>username_4: There are really two issues at play here. One (the more obvious) is the improper 6th column in root's personal crontab. The second silent one - is that ever command after the hourly cron line in `/etc/crontab` is not executing properly. The fixes are below:

---

You can remove the bogus user crontab file by running `sudo crontab -r`

---

Once that's complete you'll need to add the root user in the `/etc/crontab` file for each line after the hourly cron line - like so:

```
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user  command
11 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#

```

This should resolve those email issues.
Upvotes: 1 <issue_comment>username_5: **Do it:**

```
# crontab -r

```

And **do NOT do it**:

```
# crontab /etc/crontab

```

Instead, edits file ***/etc/crontab*** manually.
Upvotes: 0


<issue_start>username_0: Complete story:

When I installed <NAME>'s Portable Puzzle Collection via Ubuntu software center, I noticed some of the newest puzzles were missing. So I decided to get the source files and compile them myself. I uninstalled the collection and downloaded the appropriate tar.gz file from the creator's [website](http://www.chiark.greenend.org.uk/~sgtatham/puzzles/).

When I tried `make`, I got many error messages and I found out I was missing some libraries. I went on installing lib-gtk-2.0 (I think) and my first compilation ever on linux was a success.

I didn't have any decent shortcuts on the appropriate subfolder on the gnome menu (I'm using UNE), so I used `alacarte` to attach the correct images to the shortcuts.

The first thing I noticed was that the other user accounts didn't have the shortcuts as well. Also, all games suffered from the same problem. Whenever the user opened the system menu in any game, that menu remained drawn forever on the window.

I didn't like that at all, so I decided to only keep the puzzles that were missing form the original collection and reinstall the rest from Ubuntu software center. I though I would at least have most of the games behaving correctly. Therefore, I used `alacarte` again to delete the "common" shortcuts. After the installation though, I wasn't getting any of the shortcuts on the gnome menu (other user accounts had them correctly), so I decided to delete alacarte's configuration files found inside `~/.config/?` (I'm not in front of an Ubuntu-running computer at the moment, so I can't tell for sure).

Now my user account profile is broken. When I log on, the top (and only) bar is not loading at all. I don't want to mess up the profile further so I decided to stop here and ask for help. How to restore the top gnome bar missing and have my shortcuts working correctly from now on? Deleting and recreating the user account is not an option.

Sorry for the long story (I believe it was necessary to explain the steps I took in order to help others help me). Kudos to the guy who can also tell me why the system menus didn't work correctly when I compiled the games myself.

**Update**:

I'm also missing the windows title bars and borders around. Also the z-order of the windows cannot be changed (Gnome is not bringing the active window in front). Finally, under "Files & Folders" no shortcuts are not working (I'm getting the message "No application is registered as handling this file").<issue_comment>username_1: I assume (perhaps incorrectly) that the UNE uses the same config as normal gnome. To reset your menus to a system-wide standard, run this:

```
mv ~/.config/menus ~/.config/backupmenus

```

If you can't log in graphically (to the point where you can get a terminal window up), Control+Alt+F1 will give you a text login from whence you can fire off the command.

I suspect the menu isn't loading because there's something awry with the config - that's usually how these things work. If resetting the menu structure doesn't work, you might want to try moving the whole of `.config`, `.gconf`, `.gnome` and `.gnome2` out the way, in that order, to see if any fixes things.
Upvotes: 2 <issue_comment>username_2: I have read in [OMG Ubuntu](http://www.omgubuntu.co.uk/2010/08/new-ubuntu-tweak-beta-adds-desktop.html) that the new beta of UbuntuTweak can do it with a single click. I had never tried it (the new function, I did try UbuntuTweak but I didn't like it), it's beta software, etc, etc, all the usual warnings, but you can try it as a last measure.
Upvotes: 1 <issue_comment>username_3: When you "remove" a menu entry with `alacarte`, what it really does is create a user-local file that describes the application according to the [FreeDesktop.org "Desktop Entry Specification"](http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec), and indicates that it should be hidden from the menu. Local "desktop entry" files override system-wide ones. These local files are located in `~/.local/share/applications/`. Remove the local \*.desktop file, and the system-wide one (as installed by the package) will take over again.
Upvotes: 4 [selected_answer]<issue_comment>username_4: `gconftool --recursive-unset /apps/panel && killall gnome-panel` (from #ubuntu's ubottu) will reset your panels to the default. If alt+f2 is available you can just run that from there.
Upvotes: 2


<issue_start>username_0: Closing the lid on my Dell Studio 15 which is running Ubuntu 10.04 freezes the screen. This is a new problem in Ubuntu 10.04 which did not exist in 9.10

I have tried playing with all the settings in System->Preferences->Screensaver but nothing seems to make any difference. (please note the Power Management settings are accessible from here so I have tried those too.)

I don't need hibernate or suspend. I just want to be able to close the lid, and then open it and still have a working laptop.

Is their a settings somewhere that will make Ubuntu ignore the lid closing?<issue_comment>username_1: These settings are in System -> Preferences -> Power Management.

![power management](https://i.stack.imgur.com/sxfKE.png)
Upvotes: 2 <issue_comment>username_2: Make sure there is no SD card inserted.

<http://ubuntuforums.org/showthread.php?t=1478787> has 120,000 views of 980 responses - it is still possible that one of the solutions will work for you.

<http://bugs.launchpad.net/bugs/585765> is about the most useful bug report, although <https://bugs.launchpad.net/bugs/528981> worked for me (mainline kernel 2.6.34 solution).
Upvotes: 1 <issue_comment>username_3: `gconftool-2 --type string --set /apps/gnome-power-manager/buttons/lid_ac "nothing"`
Upvotes: 1 <issue_comment>username_4: I solved this by changing to the closed source FLGRX driver.
Upvotes: 3 [selected_answer]


<issue_start>username_0: Basically my network won't start. Can't use wired connections.

To make it a further brain-scratcher, when booting into recovery, and using the network console, the network comes up and works. Outside of recovery nothing.

As far as I can tell no settings changed between powering off and on since last time it worked, except for an automatic kernel upgrade. Using an older kernel does not seem to help.

Also this hardware configuration worked perfectly fine for over a year with kernel upgrades and all. Network was always automatic.

Information for follow up questions...

Network manager is running.

Strangely enough, my network interface was never started, nor was DHCP. Where in the configuration can I find this?

To manually resolve the problem:

```
sudo ifconfig eth0 up
sudo /etc/dhclient

```

What could have happened in my config to not make this work automatically.

Info gathered:

```
> lspci | grep net
> 6:00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02)

```

Contents of /etc/network/interfaces

```
auto lo
iface lo inet loopback

```

After adding

```
auto eth0
iface eth0 inet dhcp

```

the eth0 interface comes up, but the `dhclient` does not.

--

The problem re-occurred when waking up from sleep.<issue_comment>username_1: What does `ifconfig -a` show when it's not working? Is there an `eth0`? If it's not, I'd check the modules blacklists `/etc/modprobe.d/blacklist*`. I would have expected the recovery console to honour these though so moving on...

If you do have an interface, it could be some dodgy config inside network-manager. Recovery mode just uses some defaults IIRC so I'd open up the network settings (right click the applet, click edit connections) and check a few things:

* Connect Automatically is checked
* You have a MAC address
* MTU is automatic
* 802.1x security is disabled
* IPv4 is set to Automatic (DHCP)
* Require IPv4 is checked
* There should be no special routes
* IPv6 is set to ignore

If `ifconfig -a` isn't showing an `eth0` device, it could be something bizarrely hardware specific. What does `lspci | grep net` show? If nothing, do you know what the network chipset is?
Upvotes: 1 <issue_comment>username_2: You are likely missing the line for this in the interfaces file. Open `/etc/network/interfaces` and check if there is a line for `eth0` If not add the following:

```
auto eth0
iface eth0 inet dhcp

```

This will add the `eth0` interface - and use DHCP on boot and wakeup.

If you're still not getting DHCP response you may also need to add dhcp back into defaults:

`sudo update-rc.d dhcp3-server defaults`
Upvotes: 5 [selected_answer]<issue_comment>username_3: Could `pm-powersave` be the cause of your problem? My answer to [How to connect wirelessly in a cafe with 11.04](https://askubuntu.com/questions/65001/how-to-connect-wirelessly-in-a-cafe-with-11-04/65606#65606) might apply
Upvotes: 0 <issue_comment>username_4: I've installed dhcpcd5 and it worked for me.

sudo apt-get install dhcpcd5
Upvotes: -1


<issue_start>username_0: I keep reading about [Personal Package Archives](https://launchpad.net/ubuntu/+ppas) ('PPAs') and people answer questions with a link to a PPA. What's the best way to use these?

---

There are multiple valid answers for this question spanning over several versions of Ubuntu. For your convenience, an index of each is below.

* [Ubuntu 11.04 and newer](https://askubuntu.com/a/40351)
* [Ubuntu 10.10](https://askubuntu.com/a/5102)
* [Ubuntu 10.04](https://askubuntu.com/a/5139)
* [Command Line](https://askubuntu.com/a/4987)

---

* [What is a PPA?](https://askubuntu.com/a/4990)
* [Removing a PPA](https://askubuntu.com/a/91660)<issue_comment>username_1: What is PPA?
============

PPAs are for non standard software/updates. They are generally used by people who want the latest and greatest. If you are going extra lengths to get this kind of software, then you are expected to know what you are doing. The selection in the Software Centre is ample for most human beings.

Command Line
============

On the command line you can add a PPA using `add-apt-repository`, e.g.:

```
sudo add-apt-repository ppa:gwibber-daily/ppa

```

To remove a PPA remove the corresponding files in /etc/apt/sources.list.d (this does not remove the packages you installed from the PPA). To see the packages available from a PPA or remove packages installed from a PPA press the "Origin" button on the lower left of the Synaptic window and choose the PPA from the list.

With can use the usual Software Sources dialog and add *ppa:gwibber-daily/ppa* where it asks for a *APT line* and enable or disable them just like other repositories.

As anybody can create a PPA there's no guarantee for quality or security of a PPA - just like with any other unofficial software source you have to decide yourself if a PPA it's trustworthy or not. And like any other unofficial software packages from a PPA can cause all sorts of difficulties especially when upgrading to a new release of Ubuntu.

---

If you get an error that the `add-apt-repository` command could not be found:

* On 12.04 and earlier, install the `python-software-properties` package:

```
  sudo apt-get install python-software-properties

```
* On 14.04 and later:

```
  sudo apt-get install software-properties-common

```
Upvotes: 8 <issue_comment>username_2: What is a PPA?
--------------

It's all very simple once you get the hang of it. I have run into problems here and there, but generally speaking, PPA's are the only way to get your software updated in Ubuntu between distro releases (don't get me into a rant about that). It's too much to explain here, so I will point you to some worthwhile documentation. But first, a few simple rules:

Know what you're installing. Most likely you'll use Launchpad for the majority of your PPA needs, but even so it can be dangerous to your computer. Usually the worry for me is not malicious intent, but conflicting packages. If package A requires a modified version of ffmpeg, and package B in a different repository requires a modified version of ffmpeg too, well, now there's a good chance you might not be able to watch videos, for example, with package A or B or at all.

Keep in mind that anyone can create a PPA, even you. Just because a person signs the Code of Conduct doesn't mean they know what they're doing. On Launchpad there is not only updates to stable releases, but also beta and alpha software, and even stuff that doesn't quite work at all yet. There are many useful repositories, such as to get the latest Nvidia drivers or the current stable release of Pidgin. Then again, there's stuff that some guy made in his basement for himself and a couple of friends.

That said, the Ubuntu documentation web pages should have everything you need to know in a pretty understandable format.

Repositories in Ubuntu: <https://help.ubuntu.com/community/Repositories/Ubuntu>

Software management: <https://help.ubuntu.com/community/SoftwareManagement>

Repositories and the command line: <https://help.ubuntu.com/community/Repositories/CommandLine>

A quick note: I assume you're using Ubuntu 10.04. If you're using 10.10 there is no more "Software Sources" in your menu, even though it is referred to in some of the documentation. To access it simply open the Synaptic Package Manager then select Settings -> Repositories from the menu.

Good Luck and I hope this was helpful.

Edit: Please know that installing software through the Ubuntu Software Center can be troublesome. This is because it does not tell you what dependencies a particular app you want to install requires. That is, you could install the entire KDE desktop, hundreds of MB's worth of stuff, just to get a screen ruler or firewall configurator. I learned this the hard way... For example, type "kruler" in the search box and you will see the final install size as almost 100 MB. At least pay close attention to the final install size if you insist on using the USC. Most new users are unfamiliar with the concepts of window managers and desktop environments having only known Windows, so be careful about simply relying on USC and not learning all about PPAs, which is what I recommend. It's a little more work and this is just my opinion, but you'll probably be happy you did! :)
Upvotes: 5 <issue_comment>username_3: For Ubuntu 10.10
================

While many find it easier to add PPAs using command line tools, this can be done through **Ubuntu Software Center** for those who prefer graphical interfaces. For this demo, we will be adding the [PPA for the Banshee Team](https://edge.launchpad.net/%7Ebanshee-team/+archive/ppa) in order to get the latest stable release of Banshee.

We'll begin by opening the Ubuntu Software Center which can be found in the Applications menu.

```
Applications > Ubuntu Software Center

```

![manu](https://i.stack.imgur.com/3QAb7.png)

Now in Software Center, go to `Edit > Software Sources`

![menu2](https://i.stack.imgur.com/APtnG.png)

You will be asked to enter your administrative password.

![gksu](https://i.stack.imgur.com/7cIvy.png)

Now in Software Sources open the `Other Software` tab and press `Add`.

![add](https://i.stack.imgur.com/xWmra.png)

In this dialog, we will enter the PPA's information.

![software-properties-gtk](https://i.stack.imgur.com/4zOd7.png)

This information is found on the PPA's website in bold under the heading **Adding this PPA to your system**. For the [Banshee PPA](https://edge.launchpad.net/%7Ebanshee-team/+archive/ppa), it looks like this:

![ppa](https://i.stack.imgur.com/8aCqB.png)

Now we can close Software Sources and Software Center will automatically update so that you can access the new packages from the PPA.

![update](https://i.stack.imgur.com/eAZHw.png)

The packages available from the PPA can be seen by expanding the Get Software menu in Software Center's left column.

![new](https://i.stack.imgur.com/iC7iT.png)
Upvotes: 7 <issue_comment>username_4: <http://www.winehq.org/site/download-deb> is my attempt at doing this for the Wine PPA.

I'll note that Maverick changed and now I have to edit the instructions again (there is no more administration->software sources but instead you have to go there from Software Center).

Launchpad's built in instructions are a bit better than they were a year or so ago, but still pretty bad.
Upvotes: 3 <issue_comment>username_5: For Ubuntu 10.04
================

To add a PPA in Ubuntu 10.04:

* Run System->Administration->Software Sources:

![menu](https://i.stack.imgur.com/1SAAz.png)

* You will be prompted for your password. Note that you can only add a PPA if you are an administrator user due to the security risks and system wide consequences of adding a PPA. Enter your password into the dialog to continue:

![gksu](https://i.stack.imgur.com/8wN1N.png)

* In the Software Sources window, click on the 'Other Software' tab and click the 'Add...' button. This will bring up a prompt asking for the 'APT line':

![apt line](https://i.stack.imgur.com/hy7HU.png)

* The text to paste into this box is found on the launchpad page in the 'Adding This PPA to your System' in bold letter.

![](https://i.stack.imgur.com/8aCqB.png)

* Paste the line you copied into the text box in Software Sources (`CTRL`+`V`):

![enter image description here](https://i.stack.imgur.com/2MXPG.png)

* Close the Software Sources window; you will be asked to reload your package information. Do this by clicking the 'Reload' button:

![reload sources](https://i.stack.imgur.com/lEwnS.png)

* You can now find software packages from this PPA in Ubuntu Software Centre:

![software centre](https://i.stack.imgur.com/SLqRw.png)
Upvotes: 6 <issue_comment>username_6: If you are having a hard time figuring out the correct `add-apt-repository` command to run, someone has created a script called `ppasearch` to make this task easier. To install ppasearch, you will need to run the following commands:

```
sudo add-apt-repository ppa:wrinkliez/ppasearch
sudo apt-get update
sudo apt-get install ppasearch

```

If you are on maverick, you can manually [download](https://edge.launchpad.net/~wrinkliez/+archive/ppasearch/+files/ppasearch_0.7.2-0ubuntu1_all.deb) and install the lucid deb. It should work fine.

This will add the ppasearch PPA (and its key) and install the package. You can run the script by typing the following command in a terminal:

`ppasearch PPANAME`

So to find the Cardapio team PPA, you might run:

`ppasearch cardapio`

As you can see from the screenshot below, you are then presented with a list of matching PPAs. Once you select the PPA you want, it will get added by the script by using `add-apt-repository`. ppasearch will even run `sudo apt-get update` for you if you wish to update your sources.

![ppasearch screenshot](https://i.stack.imgur.com/z7O1H.png)

There is also a [video](http://www.youtube.com/watch?v=EyA9QGgALPQ) of the script in action, but it is slightly out-of-date.

This script should make it easy for you to add PPAs and their keys without having to search around Launchpad.
Upvotes: 4 <issue_comment>username_7: One thing to keep in mind about using PPAs is that when you add a PPA to your Software Sources, you're giving Administrative access (root) to everyone that can upload to that PPA. Packages in PPAs have access to your entire system as they get installed (just like a regular package from the main Ubuntu Archive), so always decide if you trust a PPA before you add it to your system.
Upvotes: 5 <issue_comment>username_8: For Ubuntu 11.04 and newer
==========================

Before adding a PPA you should be aware of some of the risks involved:

* [Are PPA's safe to add to my system and what are some "red flags" to watch out for?](https://askubuntu.com/questions/35629/are-ppas-safe-to-add-to-my-system-and-what-are-some-red-flags-to-watch-out)

Always remember that PPAs are provided by the community, you should be aware of the possible risks before just adding a PPA.

* First open the dash by either clicking on the Home button (On the top-left Corner) or pressing the `Super` Key .

![enter image description here](https://i.stack.imgur.com/vhfmM.png)
* Search for 'Software Center' and launch the Ubuntu software center.

![enter image description here](https://i.stack.imgur.com/QcKpH.png)
* Move the mouse to the top panel where the name of the application is written.
* Now Go to the *Edit* menu and select *Software Sources*.

![enter image description here](https://i.stack.imgur.com/Au7Ta.png)

For newer versions, right click and click **Software and Updates**
[![enter image description here](https://i.stack.imgur.com/VRZ9Q.png)](https://i.stack.imgur.com/VRZ9Q.png)

Then, click Other Software,
[![enter image description here](https://i.stack.imgur.com/SNeGC.png)](https://i.stack.imgur.com/SNeGC.png)

* Enter your password when prompted.

![enter image description here](https://i.stack.imgur.com/0bW7P.png)
* Switch to the 'Other Software' tab.

![enter image description here](https://i.stack.imgur.com/IzoaQ.png)
* Now click 'Add', a box will appear.

![enter image description here](https://i.stack.imgur.com/EHRbj.png)
* You have to enter the PPA in the box. It can be found in **BOLD** on the launchpad page.

![enter image description here](https://i.stack.imgur.com/A7osv.png)

![enter image description here](https://i.stack.imgur.com/fyIpo.png)
* Now click 'Add source' and close the Software Sources. The cache will be refreshed

![enter image description here](https://i.stack.imgur.com/cmbM3.png)
* Now install the software from the software center.

![enter image description here](https://i.stack.imgur.com/yDHeN.png)
Upvotes: 9 [selected_answer]<issue_comment>username_9: Removing a PPA with [ppa-purge](http://packages.ubuntu.com/ppa-purge) [Install ppa-purge](http://apt.ubuntu.com/p/ppa-purge)
----------------------------------------------------------------------------------------------------------------------------

It may not be safe to just disable any PPA added to our sources by removing it from `sources.list` or by unticking the PPA in our *Software Sources* settings. It would then be a much better idea to also remove all packages that were installed from this PPA and replace them with Ubuntu default packages.

To do so we have the script [ppa-purge](http://packages.ubuntu.com/ppa-purge) [![Install ppa-purge](https://i.stack.imgur.com/PQiaS.png)](http://apt.ubuntu.com/p/ppa-purge) that will not only remove the unwanted PPA but also will replace packages that were installed from this PPA by the default Ubuntu versions. After installation simply run

```
sudo ppa-purge ppa:/

```

where `/` is the same name we entered to our sources when adding this PPA. The PPA will then be removed. Packages installed from this PPA will be replaced by default Ubuntu packages (installed packages that are not in the default repositories will not be deleted).
Upvotes: 5 <issue_comment>username_10: For Information on PPA (**Personal Package Archive**) Visit Ubuntu help on [PPA](https://help.ubuntu.com/community/PPA).

---

There is [Y PPA Manager](https://launchpad.net/y-ppa-manager) available for Ubuntu. It is a GUI tool to manage PPAs in the best possible way.

To install `y-ppa-manager` run following command in the terminal:

```
sudo add-apt-repository ppa:webupd8team/y-ppa-manager
sudo apt-get update
sudo apt-get install y-ppa-manager

```

For more information and key-features, visit <https://launchpad.net/y-ppa-manager>.

---

**How to find PPA?** (Solution when `apt` unable to locate package)

You can find PPA from [launchpad](https://launchpad.net/ubuntu/+ppas) page as suggested in following image:

---

![adding ppa to your system](https://i.stack.imgur.com/vp4fS.png)

---

You can find PPA from [Ubuntuupdates](http://ubuntuupdates.org) -Package Search as shown in the following picture:

---

![adding third party repository](https://i.stack.imgur.com/9K4q1.png)

---

Then Add repository from terminal as following:

```
sudo add-apt-repository ppa:
sudo apt-get update

```
Upvotes: 3


<issue_start>username_0: I found a problem with an application on Ubuntu.

Questions :

* How do I best report the issue?
* What sort of information should I provide?<issue_comment>username_1: If you know the application in question (specifically the package name), I would recommend using the `ubuntu-bug` command from a terminal. `ubuntu-bug packagename` will gather some automated information and take you right to the launchpad report a bug page, where you can describe the problem.

It's also a good time to search for potential duplicates, and if you find one click the "affects me too" button.

This help page has a lot more useful info: [ReportingBugs - Community Ubuntu Documentation](https://help.ubuntu.com/community/ReportingBugs)
Upvotes: 5 <issue_comment>username_2: The most current guide appears to be [ReportingBugs - Community Ubuntu Documentation](https://help.ubuntu.com/community/ReportingBugs)

It looks pretty up to date to me, and I think it would be redundant to put that information on here.
Upvotes: 6 <issue_comment>username_3: The Ubuntu Wiki has [a very thorough guide](https://help.ubuntu.com/community/ReportingBugs) that is well illustrated and covers many possible scenarios.

The essence of that page is that you first need a [Launchpad account](https://launchpad.net/+login), then press `Alt`+`F2` and enter `ubuntu-bug packagename`. In 11.04 and later you can enter `ubuntu-bug -w` and click on the affected window.

There are also methods described on that wiki page telling you how to:

* file bugs against running programs
* against no particular package ([and how to decide which package](https://wiki.ubuntu.com/Bugs/FindRightPackage))
* and from computers with no internet access.

There is a [quick tutorial video](https://www.youtube.com/watch?v=18nsScrDIa0) that explains better.

And some more information on this site about how to gather information for a bug report:

* [I've got Internal Error whilst running a Ubuntu Beta. How to gather information and find out what it is?](https://askubuntu.com/questions/109779/ive-got-internal-error-whilst-running-a-ubuntu-beta-how-to-gather-information)
Upvotes: 9 [selected_answer]<issue_comment>username_4: If you're having a X error (graphical subsystem), the X Debugging page is very useful:

* [X/Debugging - Ubuntu Wiki](https://wiki.ubuntu.com/X/Debugging)

Usually doing an `ubuntu-bug xorg` will get all the right information to Launchpad. Bryce adds:

>
> Yes, definitely a good recommendation. But also make sure to actually describe the problem. The most common mistake made in filing X bug reports is not fully describing what actually happened. Don't assume the logs alone tell the full story - be verbose.
>
>
>
Upvotes: 5 <issue_comment>username_5: It's as easy as [visiting Launchpad](https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect) and filling the 2 or 3 fields that are there. Command line is not the only way.

Alternatively, you can use this (replace `PACKAGENAME` in the URL with the package name. For example: unity, gnome-shell, etc):

```
http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect

```

It's mentioned in the [Ubuntu documentation](https://help.ubuntu.com/community/ReportingBugs#Filing_bugs_manually_at_Launchpad.net).
Upvotes: 5 <issue_comment>username_6: >
> The most general, and comprehensive set of instructions can be found at [this community-maintained help page.](https://help.ubuntu.com/community/ReportingBugs) This answer essentially, consolidates that page, and hence it is advised that you read it, and if you are hunting bugs, it is *required* that you read it.
>
>
>

Short version:
--------------

* Know the package at fault? go type `ubuntu-bug`  in a terminal.
* Have a window before you thats buggy? go type `ubuntu-bug -w` in a terminal, and click on the window.
* Have the pid? go type `ubuntu-bug`  in a terminal.

You may also use Run dialog (`Alt`+`F2`) instead of terminal.

Long version:
-------------

Step one: Preliminaries
=======================

* Create an account at [Launchpad](https://launchpad.net/), if you don't already have one.

It is advised that you read [Launchpad Help on creating a new account](https://help.launchpad.net/YourAccount/NewAccount).

[Direct Login/signup link here](https://launchpad.net/+login)
* [Determine if it is really a bug.](https://help.ubuntu.com/community/ReportingBugs#A2._Determine_if_the_bug_is_really_a_bug)
* Make sure the bug hasn't been already reported by searching [Existing Bugs](https://launchpad.net/distros/ubuntu/+bugs).

>
> This is important to not trouble the volunteer [Bug Squad](https://launchpad.net/~bugsquad), who help in resolving bugs. If you found an existing bug, you can answer 'Does this bug affect you' with 'This bug affects me' and add any additional information as comments.
>
>
>
> Step two: Determine the [package](https://help.ubuntu.com/community/InstallingSoftware#What%20is%20a%20package?) at fault
> =========================================================================================================================
>
>
>

If you know which [package](https://help.ubuntu.com/community/InstallingSoftware#What%20is%20a%20package?) is at fault, you can run `ubuntu-bug`  to initiate the bug reporting process. you may now proceed to the next step.

[Detailed instructions on finding the right package are given here](https://wiki.ubuntu.com/Bugs/FindRightPackage)
And if those detailed instructions didn't help, you have a last resort.

### As a last Resort:

You can type `ubuntu-bug` in a terminal, or Run window, and answer few questions to gather some information on the bug.

>
> If all else fails, and you were unable to determine the right package, you may ask for help in IRC channels, or go ahead and report a bug against no particular package. Kindly note that this adds extra effort on our small group of volunteers, and you are requested to use it, as the title reads, only as a last resort. Also note that this may delay the process of resolution for your bug, and thats another reason to put in all the effort you can, to find the right package.
>
>
>

You may file a bug against no particular package by going [here](https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect).

Step three: Submitting the bug report
=====================================

*(quoted verbatim from [ReportingBugs](https://help.ubuntu.com/community/ReportingBugs) for completeness.)*

After executing any of the above commands, Apport (Ubuntu bug-reporter) will collect necessary data. A window will then pop up, asking you if you want to report the bug. Click "Send Report" if you wish to proceed, or click "Content of the report" if you want to review the information Apport collected.

![apport-problem-report](https://help.ubuntu.com/community/ReportingBugs?action=AttachFile&do=get&target=apport-problem-report.png)

>
> Apport will then upload the problem information to Launchpad, and a
>  new browser window will then open to inform you that the bug report is
>  being processed. After the bug report data has been processed, a new
>  page will open that will ask you for the bug report's title. The bug
>  title will appear in all bug listings so make sure it represents the
>  bug well. When you're done, click "Next". A search will then occur
>  based on the title you gave to the bug report, and will show
>  potentially similar ones. If one of these seems to be the exact bug
>  you're reporting, click its title, then "Yes, this is the bug I'm
>  trying to report". If not, click "No, I need to report a new bug".
>  Launchpad will then ask you for further information. It's important
>  that you specify three things:
>
>
> * What you expected to happen
> * What actually happened
> * If possible, a minimal series of steps necessary to make it happen, where step 1 is "start the program"
>
>
> Fill in the description field with as much information as you can, it
>  is better to have too much information in the description than not
>  enough.
>
>
> At then bottom of the page, there are some extra options you can use
>  to make your bug report more complete:
>
>
> * This bug is a security vulnerability: Please check this only if your bug report describes a behaviour that could be exploited to crack
>  your system. (TODO: better wording?)
> * Tags: You can add here tags that pertain to your bug report. The predefined values should be left alone.
> * Include an attachment: Using this option, you can add supporting attachments to explain or help others reproduce the bug. This might
>  include a screenshot, a video capture of the problem or a sample
>  document that triggers the fault. Additional attachments, if
>  necessary, can be added after the bug is reported via Add a
>  comment/attachment at the bottom of the page.
>
>
>

When you're done, click "Submit bug report".

If you require to collect data while off-line, u may use `apport-cli` for that. Detailed instructions on this, and many other tips can be found at [ReportingBugs](https://help.ubuntu.com/community/ReportingBugs)
Upvotes: 7 <issue_comment>username_7: To report bugs to Debian use [reportbug](https://help.ubuntu.com/community/reportbug). Open Terminal and type:

```
$ reportbug

```

Is not installed by default. Install it with `sudo apt install reportbug`.

Now you can Report the Bug:

```
$ reportbug
Please enter the name of the package in which you have found a problem.
> packagename
*** Welcome to reportbug.  Use ? for help at prompts. ***
Detected character set: UTF-8
Please change your locale if this is incorrect.

```
Upvotes: 2


<issue_start>username_0: I tried to change the resolution using the following commands (found [here](https://wiki.ubuntu.com/X/Config/Resolution)):

Use `xrandr` to check the current configuration and available modes:

```
$ xrandr
Screen 0: minimum 64 x 64, current 800 x 600, maximum 32000 x 32000
VBOX1 connected 800x600+0+0 0mm x 0mm
   800x600        60.0*+
   640x480        59.9

```

Use `cvt` to get the proper modeline for 1280x800:

```
$ cvt 1280 800
# 1280x800 59.81 Hz (CVT 1.02MA) hsync: 49.70 kHz; pclk: 83.50 MHz
Modeline "1280x800_60.00"   83.50  1280 1352 1480 1680  800 803 809 831 -hsync +vsync

```

Create the new mode using `xrandr --newmode`:

```
$ xrandr --newmode "1280x800_60.00"   83.50  1280 1352 1480 1680  800 803 809 831 -hsync +vsync

```

Use `xrandr` again to check that the mode was created successfully:

```
$ xrandr
Screen 0: minimum 64 x 64, current 800 x 600, maximum 32000 x 32000
VBOX1 connected 800x600+0+0 0mm x 0mm
   800x600        60.0*+
   640x480        59.9
  1280x800_60.00 (0x11a)   83.0MHz
        h: width  1280 start 1352 end 1480 total 1680 skew    0 clock   49.4KHz
        v: height  800 start  803 end  809 total  831           clock   59.5Hz

```

However, when I try to add the new mode to the display with `xrandr --addmode` I get the following error:

```
$ xrandr --addmode VBOX1 1280x800_60.00
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  150 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  18
  Current serial number in output stream:  19

```

Of course, if I try to set the new resolution for my current display it fails (the mode isn't associated to te display):

```
$ xrandr --output VBOX1 --mode 1280x800_60.00
xrandr: cannot find mode 1280x800_60.00

```<issue_comment>username_1: Seems that you're trying within VirtualBox. If it's the case, just install VirtualBox Guest Addition, you can get any resolution (by resizing the VirtualBox window)
Upvotes: 3 [selected_answer]<issue_comment>username_2: you can use:

```
sudo xrandr --output VBOX1 --scale 1.5x1.5

```

you can change the 1.5x1.5 per another scale factor
Upvotes: 0


<issue_start>username_0: I have both KDE and Gnome installed on my desktop. If I upgrade to 10.10 will both desktops, KDE and Gnome, be upgraded too?<issue_comment>username_1: Yes, all installed packages should be updated when you switch to 10.10. Unless, of course, 10.10 does not have newer versions of the packages.
Upvotes: 2 <issue_comment>username_2: Yes, a system upgrade will upgrade all packages including KDE and Gnome, no matter whether you're using Ubuntu or Kubuntu.
Upvotes: 3 [selected_answer]<issue_comment>username_3: Yes, and you can do the same from a fresh installation. Just back up your installed package list to a text file using Synaptic. Go to File, Save Markings (tick box save full state). Copy the file to a usb key or somewhere safe. Re-install and then open Synaptic and choose Read markings and point to the text file. Come back when Synaptic is done and you have things back to normal.

I know that you asked about upgrades, but they don't always work out and fresh installations are always better because in my experience, they never fail. :)
Upvotes: 0


<issue_start>username_0: How can I enable multi touch in Ubuntu 10.10 for my Acer Aspire 4740 notebook ?

```
Screen 14.1-inch glossy LED-backlit
1366x768 res
CPU Intel Core i5-430m 2.26GHz
RAM 1GB DDR3
HDD 320GB
Graphics Onboard Intel GMA HD
USB Ports 3
DVD Writer Yes
Gigabit Ethernet Yes
Wi-Fi 802.11 b/g/n
HDMI/eSATA/FireWire Yes/No/No
Multicard Reader Yes
ExpressCard Slot No

```<issue_comment>username_1: If your laptop built with Synaptics touchpad you need to install the synaptics drivers for your environment. To configure, you need gsynaptics configuration tool as well. With tose you can enjoy moultitouch features.
Upvotes: 1 <issue_comment>username_2: Create the following file with this command

```
sudo gedit /etc/hal/fdi/policy/99-x11-synaptics.fdi

```

And paste this into it.

---

```
xml version="1.0" encoding="ISO-8859-1"?

 on
 true
 true
 true
 35
 8
 false
 false
 245
 0
 3
 2
 41

```

---
Upvotes: 0 <issue_comment>username_3: Multitouch and the synaptics driver are installed and ready for use. Have you checked the touchpad settings under System > Preferences > Mouse and the Touchpad tab?

If you are not able to activate multitouch like me:

![alt text](https://i.stack.imgur.com/BILen.png)

you can force the setting by

```
gconftool-2 --set --type=int /desktop/gnome/peripherals/touchpad/scroll_method 2

```

If multitouch is not working after this, try a reboot. If it is still not working, try the following script:

```
#!/bin/bash
# list of synaptics device properties http://www.x.org/archive/X11R7.5/doc/man/man4/synaptics.4.html#sect4
# list  current synaptics device properties: xinput list-props "SynPS/2 Synaptics TouchPad"
#

sleep 2

xinput --set-prop --type=int --format=32 "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Pressure" 10

#   Below width 1 finger touch, above width simulate 2 finger touch. - value=pad-pixels
xinput --set-prop --type=int --format=32 "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Width" 7

#   vertical scrolling, horizontal scrolling - values: 0=disable 1=enable
xinput --set-prop --type=int --format=8  "SynPS/2 Synaptics TouchPad" "Synaptics Two-Finger Scrolling" 1 1

#   vertical, horizontal, corner - values: 0=disable  1=enable
xinput --set-prop --type=int --format=8  "SynPS/2 Synaptics TouchPad" "Synaptics Edge Scrolling" 0 0 0

#   stabilize 2 finger actions - value=pad-pixels
xinput --set-prop --type=int --format=32 "SynPS/2 Synaptics TouchPad" "Synaptics Jumpy Cursor Threshold" 120

#xinput --set-prop --type=int --format=8 "SynPS/2 Synaptics TouchPad" "Synaptics Tap Action" 0 0 0 0 1 2 0

```

If this makes it work, put it in a file, make it executable and add it to your Startup Applications.
Upvotes: 1 <issue_comment>username_4: [This page](https://help.ubuntu.com/community/SynapticsTouchpad#Enabling%20True%20Multitouch) describes the necessary steps to enable multi-touch.

I used it as guide and was able to activate multi-touch on my system.
Upvotes: 2


<issue_start>username_0: The trackpad on my ASUS laptop doesn't work after I press off and then on. Before I press off the first time it works well, afterwards it doesn't work even though the light indicator is on. This problem has happened to me since Ubuntu 10.04/Linux Mint 9/and now 10.10, it works fine on Win7, but I don't really want to boot there ;).<issue_comment>username_1: Please file a bug. <https://wiki.ubuntu.com/Hotkeys/Troubleshooting>
Upvotes: 2 <issue_comment>username_2: it is indeed a bug as discussed here:

<https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/546503>

this is not a cure for the bug, but get your trackpad running again, run:

```
gconftool --type bool --set /desktop/gnome/peripherals/touchpad/touchpad_enabled true

```
Upvotes: 2


<issue_start>username_0: I guess it's also a matter of personal taste, but since I'm starting with a fresh 10.10 install I thought maybe this time I'll keep my system more organized.

What is/are the conventional place(s) to store software and applications?

I have some stuff I get using `git` (e.g. `bioperl`), there are some apps I simply download and extract to some place (e.g. `eclipse`) and obviously I install software using `apt-get`.

Where is the conventional place to put all of these?<issue_comment>username_1: The traditional places to install additional software is either `/opt` or `usr/local` See also the [other similar question](https://askubuntu.com/questions/1148/what-is-the-best-place-to-install-user-apps)
Upvotes: 3 <issue_comment>username_2: For software installed via package management you do not need to care where it is installed, you will only manage it with some package management software like apt-get, aptitude or synaptic anyway.

The usual places are, as already mentioned by username_1, `/opt` and `/usr/local`. I would generally put software that I compile myself into `/usr/local`, as that has the usual directory structure (bin, lib, ...) already in place. Big software that expects a directory of its own I install into `/opt`, I think that is the original intent of that folder.

I'm also using a folder for small, self-contained applications in my home folder for some apps, mainly because my home folder is on a seperate partition that I keep when reinstalling the system. So I don't have to install those applications again.
Upvotes: 3 [selected_answer]<issue_comment>username_3: like everyone else said, the package manager will put things where it needs them to be put.

I tend to have a projects/ folder where I checkout my random git projects.

Eclipse likes to keep its projects in workspace/ Depending on how much development I do under eclipse I would do something like $HOME/workspaces/{AndroidStuff, CrazyRandomIdeas} depending on if the things I'm working on should be in its own workspace or is a small project.

Also, occasionally I like to install things in my $HOME since i'm just playing with things and don't want to pollute my filesystem, which I tend to put in $HOME/local. Again this is just my style.. but I end up with

```
 $HOME/
      bin/  -->symlinks to binaries I installed locally and added to $PATH
      local/  --> local installs of applications, libs etc.
      projects/  --> git check/svn checkouts etc of random code.
      workspace/ --> eclipse stuff.

```

Try not to install anything in your root filesystem (/) unless you package it. It's a royal pain to uninstall things, (there's always a make install but rarely do you ever get a make uninstall). Also, that's the entire point of a packaging system, to keep track of your programs, files, configs, etc.
Upvotes: 2


<issue_start>username_0: When I have "automatic login" activated, the "Unlock the Gnome Keyring" box asks for my password. But this happens three times. There are three boxes asking me for my password. In 10.04 the box appeared one time.<issue_comment>username_1: Try deleting your keyring and creating a new one by issuing this command

```
sudo rm ~/.gnome2/keyrings/*.keyring

```

Reboot.

When you login a box will pop up asking you to create a new keyring. Hope this works.
Upvotes: 0 <issue_comment>username_2: You could go into "Password and Encryption Keys" in your Control Panel. Right click on the Password: Login put in your current password and then leave the new password blank. This will stop this coming up also.
Upvotes: 0 <issue_comment>username_3: I'm not quite sure but I think you should also be able to go to System -> Settings -> Password and Encryption Keys and then delete (right click on them) two of the three keyrings you should see in the list (tab Passwords).
This would be sort of a combined solution of username_1's and <NAME>'s.
Upvotes: 0 <issue_comment>username_4: Make sure you've disabled auto login as per this guide:

<http://www.liberiangeek.net/2010/10/disable-auto-login-ubuntu-10-0410-10-maverick-meerkat/>

Then when you login again & are prompted to unlock keyring, click "Details" & there will be an option to automate the unlocking process.

Repeat for each prompt.

You should now only be prompted the one time at login.

This worked for me, hope it is some help to someone...
Upvotes: 3 <issue_comment>username_5: Take a look at "Passwords and Encryption Keys". A friend of mine had the same problem:

It's possible to create several bundles of keys. However, you have to unlock every single bundle after logging in (and a program tries to access it).

Here's what it should look like:
![my key-bundle setup](https://i.stack.imgur.com/Hy8z5.png)

Good luck

Tom
Upvotes: 2 <issue_comment>username_6: The keyring prompts are because your keyring and logon passwords are different or your system is set to autologon. The fix is to go to "Passwords and Encryption Keys" under System/Preferences right click on Passwords select "Change Password" set it to blank for no password (useful if your system is set to auto logon) or change it to your current logon password.

The e-mail prompts may be some program is trying to check mail at logon. Disable the program or set it to save your password.
Upvotes: 1 <issue_comment>username_7: I too had several password requests after auto-login (between 3 to around 8). I just deleted my chat accounts and now it only asked once! I know this is not a solution but it could help to pinpoint the problem.
Upvotes: 0 <issue_comment>username_8: Get this [patch](https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/744929/+attachment/2148983/+files/dont-prompt-multiple-times-rebased.patch), apply the patch to gkd-secret-unlock.c in gnome-keyring's source, rebuild the gnome-keyring package and install it. For more details on the bug and patch see [Bug 744929 for gnome-keyring](https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/744929).

If you're not familiar with the above process, here is what I did:

1. apt-get source gnome-keyring
	* Get the source code
2. patch daemon/dbus/gkd-secret-unlock.c dont-prompt-multiple-times-rebased.patch
	* Apply the patch (you'll need to specify the correct file locations)
3. dpkg-buildpackage -uc -b
	* Build the package
4. sudo dpkg -i gnome-keyring\_2.92.92.is.2.32.1-0ubuntu2\_amd64.deb
	* Install it. Your package name may be different from mine.

Note I'm on version 11.04, so I don't know if the patch will work for 10.10. Both have version 2.92.92 except the number is different after the .is. and I'm not sure what that indicates in versioning.

Thanks to <NAME> for providing the patch backport.
Upvotes: 1


<issue_start>username_0: Hey! I am having this really strange problem. I can't convert a file to utf8 it's always in us-ascii.

I have tried this:

>
> iconv --verbose --output=test2 -t
>  UTF-8 test
>
>
>

(I have also specified the -f with iso-8859-1 and us-ascii)
and when I do

>
> file --mime-encoding test2
>
>
>

I get us-ascii
The file contains some html and php. I really don't understand this. I have tried using notepad++ (I am sharing this folder to a win7 pc). I set the encoding to utf8 without bom, the file seems to change (the icon turns red) but when I save and check it continues to do be us-ascii.

I have checked the $LANG and it outputs en\_US.UTF-8 (should I change something in the locales? I would prefer this not to anything country specific)

I have also tried recode which also didn't work.

Note: Some files are being created in utf8 (I am using eclipse and have set the project properties to encode in utf8) but for some strange reason some are not being correctly encoded. Again their contents are html and php.

Please someone help me out. I am trying to show my site in utf8 and some parts are getting messed up because of this!

Thanks!<issue_comment>username_1: If your file does only contain characters that are part of (7-bit) ASCII there is no way to tell the difference between UTF-8 & ASCII, so I'm not surprised `file` would say that file is ASCII then.

If you want to serve those files as UTF-8, you better make it explicit in your HTML, PHP code, or server configuration.
Upvotes: 3 [selected_answer]<issue_comment>username_2: Your file can be displayed fine...UTF8 only does the tricks above the ascii characters.
So the first 128 chars are the same. And if you do not use any special non-ascii chars it can be identified as us-ascii (= ascii).
Technically an ASCII text file and an UTF-8 with the same contents are equivalent then.

If there are still issues on the server it might be one of its settings...
Upvotes: 1