Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Okay so I was trying to install spotify onto my ubuntu...and I don't know what I did wrong, but I do not have spotify and all of my files have become read-only (everything in the file system has a padlock on it)!!! This means I cannot do anything in terminal without getting the error that it canot open anything because its a read only file system...any suggestions?


Thanks for replying so fast! I tried to follow these instructions on terminal ..none of the stuff was working anyway


1. Add this line to your list of repositories by

editing your /etc/apt/sources.list

deb stable non-free

2. If you want to verify the downloaded packages,

you will need to add our public key

sudo apt-key adv --keyserver --recv-keys 94558F59

3. Run apt-get update

sudo apt-get update

4. Install spotify!

sudo apt-get install spotify-client

Now i keep getting this error if I try and do a fsck: permission denied while trying to open /dev/sda1 you must have r/w access to the file system or be root.

I think the error happened when it kept telling me dev is not recognised so I tried to install devscripts...:( ...which was what someone else suggested (if you're having trouble installing spotify)

  • My history is just the following ..I was trying to do a screenshot but I cant save anything :(

24 vi/etc/apt/sources.list 25 deb 26 debc (spotify link) stable non-free 27 sudo apt-get install devscripts 28 debc stable non-free 29 deb (spotify link) stable non-free 30 apt-get install debian-reference 31 yes 32 sudo apt-key 4E9CFF4E 33 sudo add-apt-repository "deb (spotify link) stable non-fr

share|improve this question
Not possible to answer without knowing what you did to attempt installing spotify. Did you follow some guide you found on the net? do you have a link to it? Did you run commands in a terminal? if so, what were those commands? – geirha Jul 18 '12 at 12:13
You might have accidentally done a recursive chmod of sorts. Type in history to the terminal and post any commands you might have used to change permissions. – Gibbs Jul 18 '12 at 12:23
I edited the answer above... i'll post all the history too. thanks for getting back so fast – Hala Jul 18 '12 at 12:29
where i've put "spotify link" it refers to ...i cant post links more than twice.. – Hala Jul 18 '12 at 12:35
take a look at… – user827992 Jul 18 '12 at 12:37

Type ls -l in one of the padlocked directories to find out the permissions. You should be able to change them with chmod and chown (using sudo if not owned by your user) if they are wrong.

For example, if a file that should be writable says:

-r--r--r-- 1 user user  4160 Jul 18 15:44 file.ext

You can give yourself write permissions using chmod ug+w file.ext.

If a file that belongs to you says:

-rw-rw-r-- 1 root user  4160 Jul 18 15:44 file.ext

You can take control of it using sudo chown user file.ext.

Similarly chgrp to change the group (the second 'user' above) if that is wrong.

share|improve this answer

This can happen because there is a disk drive error. What you describe has happened several times to me. Your fstab will have an entry similar to this:

UUID=80e377f3-6e78-4126-aa93-35ee62b58272 / ext4 errors=remount-ro 0 1

This is an instruction to remount the drive read-only if there are errors. In my case this was caused by faulty sata connections to the motherboard. I reseated the sata connector and the problem went away.

But the problem kept coming back and I finally solved the problem for good, by buying new, high quality sata cables that had a spring locking clip in the connectors. YMMV :)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.