Showing posts with label SOLVED. Show all posts
Showing posts with label SOLVED. Show all posts

Wednesday, February 19, 2014

Automatically mount NFTS partition

In order to automatically mount an NTFS partition on Ubuntu/Mint you just need to know where it is located on the file system: to do that, open "Disk utility" from the Menu, select the hard disk containing the desired partition, select the partition and look what is written near the label "Device", usually it's something like /dev/sdaN with a number instead of N.

Assume it is for example /dev/sda4, and that you want to mount it in a folder named "Files", then:

  • type  sudo gedit /etc/fstab  in a Terminal (CTRL+ALT+T) and insert your password
  • at the end of the file add two lines as follows:
    # My automatically mounted partition
    /dev/sda4 /media/Files ntfs defaults,uid=1000,gid=1000 0 1
  • save and close
The next time you'll reboot, it will be automatically mounted! =)

Friday, January 10, 2014

[SOLVED] Could not download all repository indexes

If updating your software gives you one of the following problems

Could not download all repository indexes
The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and ensure the repository address in the preferences is correct.


Could not refresh the list of packages
ERROR###ERROR###ERROR###ERROR###ERROR###ERROR###ERROR
W:Failed to fetch http://packages.medibuntu.org/dists/precise/Release.gpg  Could not connect to packages.medibuntu.org:80 (67.215.66.132). - connect (110: Connection timed out),
W:Failed to fetch http://packages.medibuntu.org/dists/precise/free/binary-amd64/Packages
Unable to connect to packages.medibuntu.org:http:

Ign http://packages.medibuntu.org precise Release          
Ign http://packages.medibuntu.org precise/free amd64 Packages/DiffIndex
Err http://packages.medibuntu.org precise/free amd64 Packages
  Unable to connect to packages.medibuntu.org:http:
W: Failed to fetch http://packages.medibuntu.org/dists/precise/Release.gpg  Could not connect to packages.medibuntu.org:80 (67.215.66.132). - connect (110: Connection timed out)
W: Failed to fetch http://packages.medibuntu.org/dists/precise/free/binary-amd64/Packages  Unable to connect to packages.medibuntu.org:http:
E: Some index files failed to download. They have been ignored, or old ones used instead.

it's because medibuntu packages are no more available, and thus can't be updated, but are not automatically removed from the packages which have to be updated. With this single command that I found here you can definitively eliminate this annoying problem: in a terminal type

sudo sed -i '/^deb http:\/\/packages.medibuntu.org*/d' /etc/apt/sources.list /etc/apt/sources.list.d/*.list

insert your login password, and it's done! =)

Thursday, April 4, 2013

[SOLVED] Mint13 - Nvidia GeForce GT540M optimus (64 bit)

Nvidia graphic cards with Optimus technology (such as GeForce GT540M) may take to errors in case of installation through the official Nvidia .run file or apt-get install nvidia-current, and result in a horrible VGA screen resolution (in the best cases).

At write time there wasn't a single working solution, but many different forum discussions each solving a subpart of the problem. Now that I managed to solve it, I report here all and only the necessary steps to finally use your Nvidia graphic card on your Ubuntu/Mint OS.

Note: tested on Mint13 64bit.

Important: follow all the steps in order, inserting password when prompted, always confirming

REMOVE PREVIOUS NVIDIA INSTALLATION ATTEMPTS:


  • open a Terminal (CTRL+ALT+T)
  • type sudo apt-get purge nvidia- and press 2times TAB fast; with the arrow up key reselect the command and complete it with each of the found options
  • type sudo rm /etc/X11/xorg.* then enter
  • type sudo reboot then enter. The system will REBOOT! (close open programs/files before)

INSTALL BUMBLEBEE

  • open a Terminal (CTRL+ALT+T)
  • type sudo add-apt-repository ppa:bumblebee/stable then enter
  • type sudo apt-get update then enter
  • type sudo apt-get install bumblebee bumblebee-nvidia linux-headers-generic then enter
  • type sudo apt-get install virtualgl-libs:i386 then enter
  • type sudo usermod -a -G bumblebee $USER then enter
  • type sudo update-initramfs -u then enter
  • type sudo gedit /etc/init/bumblebeed.override then enter
    write:
        start on    (runlevel [2345])
        stop on     (runlevel [016])

    save and close;
  • type sudo reboot then enter. The system will REBOOT! (close open programs/files before)

TEST IT

  • open a Terminal (CTRL+ALT+T)
  • type optirun glxspheres then enter

Please let me know if it was successful for you. If some step gives you problem and you go on skipping it please let me know too! You don't need to register in order to comment!

Note: this guide solves also the following problems:
  • You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server.
  • Could not apply the stored configuration for monitors
  • The Bumblebee daemon has not been started yet or the socket path /var/run/bumblebee.socket was incorrect

Saturday, January 29, 2011

Ubuntu - Enter password for keyring ‘Default’ to unlock

If this window (or a similar one) appeared while launching an application, here is what you've got to do:
Enter password for keyring ‘Default’ to unlock
An application wants access to the keyring ‘Default’, but it is locked


  • FOR LINUX MINT & maybe recent Ubuntu (please let me know)

     0.   -->
  1. In the menu, search for Passwords and keys; open it
  2. In the "Passwords" tab you should have a folder Passwords:login
  3. Right-click on it and select "Change password"
  4. Insert your password in "Old password" and leave blank "Password" and "Confirm"
IMPORTANT NOTE: A security-information window will appear, but you can ignore it: your login password won't change, so your computer is still protected.. Maybe other users, once computer is logged in, can access those applications wich require a keyring password, but I think that if you leave someone your pc logged in, you trust them, don't you?



  • FOR UBUNTU version 11.04 (and others? please let me know, also if it is correct)
   "An application wants access to the keyring 'Default', but it's locked."
   (thanks to a reader for his/her comment)
  1. In the menu, under Applications search for Passwords and Encryption Keys
  2. Right-click on Default-user, and then "delete"
  3. Right-click on Login-user, and then "set as default"
  4. The above NOTE is valid here too.


  • FOR UBUNTU versions up to 10.10 with GNOME instead of UNITY

  1. Go to  Applications –> Accessories –> Passwords and Encryption Keys
  2. If in the "Passwords" tab you see "Passwords: default" select it, then  Edit -> Remove
  3. File –> New –> Password Keyring
  4. Insert 'Default' as name, and a password (not necessarely the login one)
  5. Now you'll be asked the previously set password every time you log out; to avoid this you can leave the password blank.
  6. The above NOTE is valid here too.

Was the post not useful to you? Here some possibly useful links: