remove partition from places menu

You can edit the places menu somewhat with this file;
$ sudo gedit ~/.gtk-bookmarks

I'll leave this open in case someone has a better soloution.

sorry I hit the wrong button lol

Thanks John Bruno for your answer.

That file only record folder bookmarks... I need to remove the mounted partition...
Been doing some research but I still hasn't been able to hide the partition entry.

I believe it also gets entry's from the mounted drive(s) on your desktop, but it will load a new entry every time you re-login. If there is no other solution available (I could not find one) you may be able to write a small script to delete the entry at every boot time.

Hope you find a better solution. Good luck.

I don't see a way to write such script. Stuff appears on the Desktop but they are not in the ~/Desktop folder. They are somewhat "virtual" and I don't know how to remove by script. If you have a way, please show me an example.

At least the volume icons on the desktop are removeable:
Exec gconf-editor and browse to /apps/nautilus/desktop, there you can uncheck volumes_visible

Thanks for your response Jan-Philipp.

But I need to remove the partition from the Places menu. I had already removed from desktop.
I have a bug report open linked to this question. Again, thank you.

You might try altering the fstab entry for this partition to keep it from being automatically mounted. You could then add a command to mount it to the login script for any users that should be able to see it on the Places menu.

My places menu looks thus:
username
Desktop
File System
Network
13 GB File System
234 GB File System
1000 GB File System

The final 3 are unmounted and don't contain file systems. They're the block devices that luks uses for my / /home and generalized storage location. If I click on them, I get errors like "Unable to mount 234 GB Filesystem: /dev/mapper/chome is mounted"

I would like to remove these 3 entries. They're useless.

@Bob/Paul: The solution provided by cheics solves the initial problem. Yours is a different issue concerning encrypted drives, please file a different bug report for it.

Thanks cheics, that solved my question.