Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lost bookmarks & history; lost profile. Did Firefox change the name of a mount point?

more options

This is so strange as to be almost unbelieveable. It began as a profile issue. Everything is okay now, but there was much weirdness. I think this is a worthwhile read and I'm eager to hear any ideas regarding what happened.

The bottom line: If Firefox changed the name of a mount point, that was/is a bad idea -- developers take note.

I run Firefox (latest) in a Linux Mint Guest inside a VirtualBox virtual machine with a Windows Host. The Firefox application is installed as usual, but the profile is here: 'FireFox Profile.vhd' -- a virtual USB that, on VM boot, VBox mounts here: '/media/mark/FireFox Profile/'.

The profile is: '/media/mark/FireFox Profile/mwad0hks.default/'.

Events: 1 - In a proven Linux Mint VM, today I booted the VM as usual but Firefox apparently lost my bookmarks & history. Why? I'll probably never know. 2 - I created a new profile hoping that in the process, I'd be given the option to use an existing profile -- no dice, FF created a new, blank profile. 3 - I discovered that I now had these: 3.1 - '/media/mark/FireFox Profile/', and 3.2 - '/media/mark/FireFox Profile1/'. 4 - I closed FF, launched Nemo, and tried to delete 'FireFox Profile1' but was refused. 5 - After much fiddling of the contents of 'FireFox Profile.vhd' mounted in Windows (to make it accessable outside the VM) I backed up 'FireFox Profile.vhd' -- good thing I did that. 6 - I realized that the mount point must have been renamed from '/media/mark/FireFox Profile/' to '/media/mark/FireFox Profile1/'. 7 - Sure enough, I launched the VM and deleted '/media/mark/FireFox Profile/' -- remember that '/media/mark/FireFox Profile1/' could not be deleted. 8 - So I concluded that "something" must have renamed the Linux VM mount point from '/media/mark/FireFox Profile/' to '/media/mark/FireFox Profile1/'.

I conclude that FF must have done the renaming in step 2.

I launched the Linux VM aiming to search how to rename the mount point back to its original name and low and behold, FF now found the correct profile and everything was happiness again. End of story. Or is it?

This is so strange as to be almost unbelieveable. It began as a profile issue. Everything is okay now, but there was much weirdness. I think this is a worthwhile read and I'm eager to hear any ideas regarding what happened. The bottom line: If Firefox changed the name of a mount point, that was/is a bad idea -- developers take note. I run Firefox (latest) in a Linux Mint Guest inside a VirtualBox virtual machine with a Windows Host. The Firefox application is installed as usual, but the profile is here: 'FireFox Profile.vhd' -- a virtual USB that, on VM boot, VBox mounts here: '/media/mark/FireFox Profile/'. The profile is: '/media/mark/FireFox Profile/mwad0hks.default/'. Events: 1 - In a proven Linux Mint VM, today I booted the VM as usual but Firefox apparently lost my bookmarks & history. Why? I'll probably never know. 2 - I created a new profile hoping that in the process, I'd be given the option to use an existing profile -- no dice, FF created a new, blank profile. 3 - I discovered that I now had these: 3.1 - '/media/mark/FireFox Profile/', and 3.2 - '/media/mark/FireFox Profile1/'. 4 - I closed FF, launched Nemo, and tried to delete 'FireFox Profile1' but was refused. 5 - After much fiddling of the contents of 'FireFox Profile.vhd' mounted in Windows (to make it accessable outside the VM) I backed up 'FireFox Profile.vhd' -- good thing I did that. 6 - I realized that the mount point must have been renamed from '/media/mark/FireFox Profile/' to '/media/mark/FireFox Profile1/'. 7 - Sure enough, I launched the VM and deleted '/media/mark/FireFox Profile/' -- remember that '/media/mark/FireFox Profile1/' could not be deleted. 8 - So I concluded that "something" must have renamed the Linux VM mount point from '/media/mark/FireFox Profile/' to '/media/mark/FireFox Profile1/'. I conclude that FF must have done the renaming in step 2. I launched the Linux VM aiming to search how to rename the mount point back to its original name and low and behold, FF now found the correct profile and everything was happiness again. End of story. Or is it?

Alle svar (1)

more options

Additional: I don't know whether VirtualBox, or Linux Mint, or Firefox fixed the issue. I wish I knew. I suspect VirtualBox was involved because it automatically assigns mount points for attached virtual disks.

PS: I just remembered. At one point, FF grabbed another, nearby profile that's used by the Pale Moon browser. I know that because FF told me via 'about:profile'. So obviously, FF does things behind the scenes and does them silently -- I don't like that, I don't appreciate machines that fix themselves silently.

Ændret af Mark Filipak den