Mint Menu preferences...custom places not working?

[baking666]

I have a folder /media/Ubuntu Home/bking/home/Music that is valid address but mint menu custom places doesn't think so....does custom places have to be off home?

[Sid32]

Its a bug with the space in "ubuntu home" hard-drive name. I'm having the same problem. Hopefully its fixed soon.

[Husse]

Please specify the folder name - do not include the mount point (but tell us that separately anyway)
I think Sid32 is right but is the folder name ubuntu home?

[Sid32]

My Hd is called 'Big Ones' and I get pop up errors saying 'Media/Big' not found and 'Ones/documents' not found.

I am trying to get the folder in the menu to link to 'media/big ones/documents'

[hansmc]

I just tested it on my computer. If I put the place in double quotes it works. Like this "/home/me/test one".

[Sid32]

Not working over here. Try setting a link to a HD that has a space in its name. The link that I am trying to get it to open is:
"/media/BIG ONES/files/Downloads" Where 'Big Ones' is a 2nd hardrive.

[Husse]

/media/BIG ONES/files/Downloads
Is that the mount point?
/media/"BIG ONES"/files/Downloads
That should do it I think

[Sid32]

Sorry same error...

[Husse]

This is strange - as you probably know there is no problem with spaces in the GUI - look at the shortcut to home on your desktop - it's called your_name's Home and there is a space
I don't know about the custom places but it should be no different
In the terminal you have to escape spaces - can't remember how and I have to quit now - will return

[altair4]

I can confirm this is a very strange bug.

I just tested it on my computer. If I put the place in double quotes it works. Like this "/home/me/test one".

I duplicated this and it does work but it appears to work only in the home directory.

I have a partition that I do not normally mount since it houses my boot loader. So I created a mountpoint and an entry in fstab to mount it at boot:

sudo mkdir /media/"BOOTIT NG"
UUID=16D7-0200 /media/BOOTIT\040NG vfat defaults 0 0

No matter how I crafted the entry into the Menus' Places:

"media/BOOTIT NG"
media/"BOOTIT NG"
I even tried /media/BOOTIT\040NG

I get the same results as Sid32. The error message tells me it can't find either "BOOTIT" or "NG"

However, and to answer the original posters question, If I change the mount point to /media/BOOTIT and change the entry in the Menu to /media/BOOTIT then it does work. So it appears that spaces in the home directory are OK, spaces outside the home directory are not OK.

[Husse]

Hmm - it seems that outside home it becomes more like the terminal, but then the normal escape for space should work and it did not
Can we say this is semi-solved?
Make a mount point in home for the disk and you are ok...

[Fred]

altair4,

I am not sure what Nautilus is actually doing here. Remember, you mount partitions, not folders on a partition. You Bind folders on a partition. Remember your question about binding a folder on an NTFS partition a while back?

Folder or file names with spaces or strange characters are always problematic. You might try using the single quote, or double quote enclosing a string that has single quotes within it.

We are talking about Nautilus here, so I wouldn't be too surprised at a broken outcome.

Fred

[altair4]

Fred,

I am mounting a partition ( UUID=16D7-0200 ) to a mount point in /media ( /media/BOOTIT NG ).

I can bring up Nautilus and when I open /media/BOOTIT NG I can access the files.

It's Mint 8's ability to edit the "Places" section of the start Menu that's the problem. It can't handle spaces in the mount point ( EDIT: It can't handle spaces in the directory name ) outside of one's home directory. I tried the following permutations in the Menu:

"/media/BOOTIT NG"
/media/"BOOTIT NG"
'/media/BOOTIT NG'
/media/'BOOTIT NG'
/media/BOOTIT\040NG
"/media/'BOOTIT NG'"
'/media/"BOOTIT NG"'

None of it works. It parses the phrase as media/BOOTIT and media/NG and gives me two error messages that it can't find either.

Did I miss something in your post and am I still confused?

[Fred]

altair4 wrote:

I am mounting a partition ( UUID=16D7-0200 ) to a mount point in /media ( /media/BOOTIT NG ).

First, let me point out that I haven't yet downloaded or looked at Mint 8 so there could easily be something going on that I haven't seen.

To start with, the UUID looks suspect. I am not sure what to think about that. I would make sure that you have "mtools" installed.

The problems in this thread may not be the same. My point above was to make a distinction between a LABEL for a physical drive and a partition LABEL. Trying to mount to a drive LABEL, even if it has only one partition, will be problematic since you mount partitions and not drives. I suspect something is getting the two confused.

I would assign a LABEL to the FAT partition with gparted. Instead of using what appears to me to be a flaky UUID to mount with, use the LABEL= SomeLabel in fstab instead. If you must use a two word label put it in quotes. Example: LABEL="BOOTIT NG" /media/"BOOTIT NG" ...etc.

Fred

[altair4]

Fred,

I chose the following partition because it's the only one I don't mount at boot and was the easiest to experiment with:

From blkid: /dev/sda3: SEC_TYPE="msdos" LABEL="BOOTIT EMBR" UUID="16D7-0200" TYPE="vfat"
I only have 3 vfat partitions in my network and they all have that UUID format.

I created the mount point with a space in it and it's unique and doesn't match any LABEL:
sudo mkdir /media/"BOOTIT NG"
In retrospect I should have called it My Test or something to avoid confusion.

I then added an entry in fstab:
UUID=16D7-0200 /media/BOOTIT\040NG vfat defaults 0 0

I could have used the LABEL from blkid instead of the UUID but I thought I was pushing it with a space in the mount point BTW the '\040' is the only way I know of to have a space in fstab so that's why it's there.

I didn't create the label for /dev/sda3, BOOTIT did. I've used BOOTIT since SuSE 6.1 and have never had a GRUB issue when multibooting. Since it seems to work with GRUB2 I may never have an issue with grub. I'd just as soon not change the LABEL

EDIT: I'm fairly certain the mounting part of this experiment is OK since I can access /media/BOOTIT NG 's files in Nautilus. I just can't access them from the Mint Menu shortcut.

[Fred]

altair4,

It would appear from your post that this is a Mint menu issue. You would probably have to look at the source to see why this is happening.

Fred

[Husse]

UUID="16D7-0200"

You get UUIDs like that when you mount a USB disk and possibly also any vfat disk
I have a 150 GB fat32 disk and it gets the UUID 000B-EA3B

[clhodapp]

I actually wrote that part of the mintMenu code and I can confirm your experience: it seems to fail whenever the name of a directory has a space if it's outside of the user's home folder. I'll have a look and see if I can figure out why. It's strange: I never tested it with this particular case.

[DJ_Baldey]

Variant correction of the menu in Linux Mint 8:
edit file places.py:

Code: Select all

sudo nano /usr/lib/linuxmint/mintMenu/plugins/places.py

find this lines (are located separately):

Code: Select all

Button4.connect( "clicked", self.ButtonClicked, "nautilus " + desktopDir )
command = ( "nautilus " + self.custompaths[index] )

and edit them so:

Code: Select all

Button4.connect( "clicked", self.ButtonClicked, "nautilus \"" + desktopDir + "\"" )
command = ( "nautilus \"" + self.custompaths[index] + "\"" )

after save, execute:

Code: Select all

cd /usr/lib/linuxmint/mintMenu/ && sudo python compile.py

After menu reboot will work correctly.

[Sid32]

Problem not fixed in Mint Menu 3.9.4. Removed places and added again. Still not working....