SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
Thanks for that (only place I didn't look, LQ, sheesh!).
I did go on a bug hunt -- looked for man pages (there aren't any), looked at /usr/doc/gvfs-1.12.3 (less than useless), looked all over the place in /usr (found the commands in /usr/bin, no man page, not much info with a -? option). I did a search at Wikipedia (the article which says just about nothing).
Looks like GazL's suggestion (http://www.linuxquestions.org/questi...9/#post4880848) might be the solution, so I created a ~/.xinitrc, added GVFS_DISABLE_FUSE=1 ; export GVFS_DISABLE_FUSE to it and we'll see what happens.
And I still don't know what the heck it's there for and what it actually does.
It is part of a gnome2 environment. It provides to the users gnome applications a filesystem view of configuration options. The filesystem is NOT something that can be backed up, it is also blocked from any access EXCEPT the user.
When the filesystem is not mounted, the directory will appear normal, and can be deleted. But it will also be recreated when gvfs server is started (usually on login).
Oh - gvfs is implemented using FUSE (filesystem in user space).
Since I quit using Gnome (either version 2 or 3) I haven't had problems with it.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
Quote:
Originally Posted by jpollard
Since I quit using Gnome (either version 2 or 3) I haven't had problems with it.
OK, thanks for that -- funny thing is, though, GNOME has never touched this box (it isn't even available directly from Slackware). So, I've probably gotten some GNOME-ish thing on here (that I seem to remember some application that needed it, but darned if I can remember what!).
Oh, drat, maybe one of these:
Code:
ls /var/log/packages/*gnom*
/var/log/packages/gnome-icon-theme-3.4.0-x86_64-1
/var/log/packages/gnome-keyring-3.4.1-x86_64-2
/var/log/packages/libgnome-keyring-3.4.1-x86_64-1
/var/log/packages/polkit-gnome-0.102-x86_64-1
No clue on what's using them, though -- that directory doesn't exist at log in, just after running for a while and, you know, doing work.
I'll have to one-at-a-time a few things and see who's causing it.
OK, thanks for that -- funny thing is, though, GNOME has never touched this box (it isn't even available directly from Slackware). So, I've probably gotten some GNOME-ish thing on here (that I seem to remember some application that needed it, but darned if I can remember what!).
Oh, drat, maybe one of these:
Code:
ls /var/log/packages/*gnom*
/var/log/packages/gnome-icon-theme-3.4.0-x86_64-1
/var/log/packages/gnome-keyring-3.4.1-x86_64-2
/var/log/packages/libgnome-keyring-3.4.1-x86_64-1
/var/log/packages/polkit-gnome-0.102-x86_64-1
No clue on what's using them, though -- that directory doesn't exist at log in, just after running for a while and, you know, doing work.
I'll have to one-at-a-time a few things and see who's causing it.
Thanks again.
Any or all of the last three (the icon package may not). Also check for gedit as that uses it too. As far as I know, all gnome applications use it.
I'm pretty sure Firefox starts gvfs (and gconfd-2). I don't know of any way to prevent Firefox from using them (which is annoying, because I have no use for either service).
If I start Firefox under twm, it starts gconfd-2 but not gvfs. If I start it under xmonad, it starts both (and it is definitely Firefox that is starting gvfs). The notable differences are that xmonad is launched with
I am guessing that ConsoleKit and/or dbus are responsible for launching gvfs when Firefox is started, but you may not notice it depending on how your WM/DE is started.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
Well, I dunno -- but, the "SBo" at the end of the package names means that it was requirement for some SlackBuiles.org package (and I dunno which one).
At least I know what it is, just haven't gotten around to finding out what's causing it and, for now anyway, that's good enough. Right now, the directory is there but readable and empty, Firefox is running, so, nope, not Firefox, not Thunderbird, not Xfce (fur sure).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.