Hot answers tagged gvfs
When a drive is connected and its filesystem loaded, it is mounted, as if with the mount (or pmount) command, to a location on the root filesystem (usually somewhere inside /media). When the filesystem is no longer needed, it can be unmounted (as if with the umount or pumount commands), which flushes any pending writes to disk, so that you can remove the ...
Open your terminal and type the following command to clear the trash sudo rm -rf ~/.local/share/Trash/*
It's changed to /run/user/your_username/gvfs. It may also be at: /run/user/your_usernumber/gvfs. Example: /run/user/1000/gvfs
Solved the problem (kind of). On Ubuntu 12.10 the mountpoint appears in /run/user/(your username)/gvfs/sftp\:host\=\192.168.xxx.xxx. Hope that helps
The main differences are the following: Unmount This option will "literally" unmount the device/partition and it applies normally (In Nautilus) to hard drives, be them, internal or external. Is not common to see it for Flash Drives / Pen Drives / Thumb Drives / SD Card / Digital Camera and any other device that needs to sync before powering down. This is ...
Shell You could use the mount command in a start up script and put that in the Startup Application Preferences. mount is perfectly capable of mounting remote file systems (if you provided it with the right options and all necessary packages installed). An alternative to mount in your startup script is gvfs-mount . You can mount nautilus-type URIs with ...
Since Ubuntu 12.10, gvfs mounts can be found in /run/user/<login>/gvfs.
gvfs-... type commands can process remote locations based on a url. From man gvfs-cat: gvfs-cat works just like the traditional cat utility, but using gvfs locations instead of local files: for example you can use something like smb://server/resource/file.txt as location. For instance You can use gvfs-cat to do the following: gvfs-cat ...
There is a FUSE virtual filesystem mounted at ~/.gvfs. For the majority of filesystem accesses, permissions are ignored for the root user. However, FUSE virtual filesystem mounts are one of the rare exceptions. FUSE virtual filesystems are normally restricted to the user who mounted them. In this case, the gvfs-fuse-daemon command (run as part of your ...
The ~/.gvfs directory should be a FUSE mount handled by the gvfs-fuse-daemon process. If the directory appears to be empty, it would indicate that gvfs-fuse-daemon did not start correctly. You could try starting it manually with the following command: /usr/lib/gvfs/gvfs-fuse-daemon ~/.gvfs If that fails, you could try checking whether anything else is ...
There is a bug report here: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/754618 You can try unmounting the directory or a reboot. sudo umount ~matt/.gvfs
gio is a PyGTK module, and is not available for Python 3 because PyGTK itself is deprecated. If you want to create a GTK+ application in Python 3, you will need to use its replacement: PyGObject. In the case of Gio, you import it like this. $ python3 Python 3.2.2 (default, Sep 5 2011, 21:17:14) [GCC 4.6.1] on linux2 Type "help", "copyright", "credits" or ...
When it comes to USB devices eject only unmounts the device but it is still connected. Removing it might cause damage. After ejecting the device you have to safely remove it to be sure it won't damage yoru device.
You need to add the user option to your fstab /dev/sdc1 /media/sdc1 vfat uid=1000,noauto,user 0 0 /dev/sdd1 /media/sdd1 vfat uid=1000,noauto,user 0 0 /dev/sdb1 /media/sdb1 vfat uid=1000,noauto,user 0 0 The user option allows any user to mount a device, as said in the man: Normally, only ...
If the command sudo watch netstat -tonp shows a lot of connections caused by gvfs directly after booting, then you can consider to remove zeitgeist, geoclue, and/or ubuntu-one. You can also consider to deactivate the rhythmbox lastfm-plugin. As I don't need these programs I decided to remove them all and after the next boot, all strange gvfs connections ...
I'm pretty sure "safely remove Drive" unmounts any other partitions on that device.
Last time I checked (some months ago), I explicitly had to add a permission for "Guest" to the Windows 7 share (Advanced Sharing > Permissions) to allow password-free connections. "Everyone" alone didn't work for whatever reason. Maybe this has changed in the meantime, but it's worth a try.
Here is the script that I threw together for use with @fossfreedom's answer. It uses GIO to interface to GVFS and Tkinter for the GUI, and is written in Python 2.7. It supports multi-line annotations. The GUI looks like this: prerequisites You need to install tkinter: sudo apt-get install python-tk to use Save the code as a file using your favourite ...
Just press Ctrl+Alt+T on your keyboard to open Terminal. When it opens, run the command below. sudo apt-get install --reinstall gvfs-backends
A similar question to this was asked from "Emblems and Backgrounds" and I'm afraid its a similar answer. The Gnome Devs thought these capabilities were rarely used and in-order to streamline the codebase they removed this as core GUI functionality. Fortunately, the same terminal based commands can be used since the metadata capabilities have been retained: ...
/home/user/.gvfs is the mount point for a virtual filesystem used by Gnome. It cannot be accessed by any other user than the session owner (not even root) while a Gnome session is active. By default chown only prints error messages so if you don't get any other response from chown that means everything else worked fine. If you still can't create or delete ...
I found the answer here: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1018806 The problem results from wrong configuration of system wide proxy. If you have the same problem you can try following commands, that will reset your proxy settings to default: gsettings set org.gnome.system.proxy autoconfig-url '' gsettings set org.gnome.system.proxy ...
As you may have noticed, these man pages were made by Sun for for Solaris, so Ubuntu cannot simply copy them due to copyright restrictions. The solution is for upstream (in this case, Gnome) to create the man pages themselves. And, as already pointed out in the comments, this was requested via bug reports in both Ubuntu and Debian circa 2008. There were ...
According to the changelog this change was not included in Ubuntu but upstream. I looked at the gitlog of gvfs upstream but didn't found the exact commit that made this changes. Upstream changelog: https://git.gnome.org/browse/gvfs/log/ NEWS file: https://git.gnome.org/browse/gvfs/tree/NEWS
I suggest you change the USB mode from PTP to mass storage. It should simplify connection problems since USB mass storage is more widely supported. I had similar problems with Ubuntu 12.10 and a camera which only had PTP mode. WORKAROUND: If your camera doesn't support mass storage mode, maybe it would be easier to transfer files by removing your memory ...
The bug mdr mentions in his comment (https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1075923) is now fixed, and a gvfs update that fixes the problem was pushed out on 2013-10-03 (http://launchpad.net/ubuntu/+source/gvfs/1.16.1-0ubuntu1.1). So all you need to do at this point to fix this problem is update your ubuntu gvfs package.
Stored as GVFS metadata attributes. To get all GVFS metadata attributes for file/directory: gvfs-info '/home/user/Desktop/Untitled Folder/' To get specific attribute - icon position: gvfs-info -a 'metadata::nautilus-icon-position' '/home/user/Desktop/Untitled Document/' To set icon position: gvfs-set-attribute -t string '/home/user/Desktop/Untitled ...
A possible reason could be that you formatted/created the storage disk with a tool with root privilege and so the file-system created was owned by the root. Let's have a look at the o/p of your ls commands: $ ls -ld /media/adam/WDPassport2T drwxr-xr-x 4 root root 4096 Jan 15 16:57 /media/adam/WDPassport2T $ ls -l /media/adam/WDPassport2T total 20 ...
Thanks to LewisTM, you can find your gvfs folder in /run/user//gvfs. $ mount | grep gvfs @see http://ubuntuforums.org/showthread.php?t=2073288&s=a19d73e2b26158ee28330927102536dc&p=12305478#post12305478
To expand a bit on the comment by muru, running graphical problems with sudo can sometimes lead to problems like this. sudo runs the program as the root user account, but the program still believes that user's home directory is your regular home directory. Thus it'll end up creating files in your home directory, but owned by the root user. This will ...
Only top voted, non community-wiki answers of a minimum length are eligible