On 11/14/2014 02:02 PM, Bjarne Örn Hansen wrote:

Den 2014-11-14 19:49, John Andersen skrev:

...

An excellent unfiltered rant. Bravo.

I gave a fair warning :-)

...

I offer this as helpful information, not as a counter-rant.

You have control of baloo, by several means: 1) uninstall through Yast or zypper 2) go to Config Desktop, and add areas (partitions) that should be excluded 4) Uncheck the checkbox on that same page to turn indexing off all toghether 5) Less documented, but more powerful: edit /home/[username]/.kde4/share/config/baloorc and adjust settings to exclude file types and locations you don't want indexed.

It's this (4) and (5) that I'm having problems with. Why should I have to look for means to turn #poor idea# OFF... I should be looking for means to turn it ON, if I'd want it ... I'd probably want to ristrict this wild HOG, not merely to partitions ... but down to "individual" directories. All the way down to Documents and Pictures folder, and the like ... not my entire file system.

I think you will find it is by default restricted to /home. It is further restricted to not indexing many different file types, and you can add other restrictions. https://community.kde.org/Baloo/Configuration Where you can get into trouble is if you keep boat loads of stuff in your home working directory. I can see both sides of the issue of having it on by default or having it off by default. God knows we've been round and round this issue on this list. It would seem to me that the more massive the amount of data and files you have on your system the more likely you are to need it And until the arrival of baloo when we were struggling with that miserable nepomuk, I was fully in agreement that it should be off by default. But I've found the impact of Baloo very minimal, and the time it takes for the first index was also very minimal, and it pays for itself the FIRST time you have to grep for content in any file, or even search for a file by name. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/14/2014 10:55 AM, Carlos E. R. wrote:

On 2014-11-14 18:55, Bjarne Örn Hansen wrote:

...

And what's worse ... I am running KDE, what is parcellite doing and gvfs? Why are these gnome daemons, running on my KDE desktop?

Probably because you have started some lone gnome app which uses them.

gvfs has been with us since at least versio 11.1. It handles MTP devices like cameras. Its pretty hard to figure out what package draws it in when installing, or what recommends it or what suggests it. Yast, and zypper are pretty weak on providing tools to find out what caused installations of packages, or what suggests packages or what recommends packages. - -- After all is said and done, more is said than done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlRmVGkACgkQv7M3G5+2DLKzdQCgguCXqrUqq70TMmJdg0BQBnGP qE0An0wIWFURypIG0Wv83aSzRqR0IXJ2 =cHVP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/14/2014 11:30 AM, Patrick Shanahan wrote:

* John Andersen [11-14-14 14:16]:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On 11/14/2014 10:55 AM, Carlos E. R. wrote:

...

On 2014-11-14 18:55, Bjarne Örn Hansen wrote:

...

And what's worse ... I am running KDE, what is parcellite doing and gvfs? Why are these gnome daemons, running on my KDE desktop?

Probably because you have started some lone gnome app which uses them.

gvfs has been with us since at least versio 11.1. It handles MTP devices like cameras. Its pretty hard to figure out what package draws it in when installing, or what recommends it or what suggests it.

Yast, and zypper are pretty weak on providing tools to find out what caused installations of packages, or what suggests packages or what recommends packages.

#> rpm -q --whatrequires gvfs gvfs-backends-1.22.1-1.2.x86_64 gvfs-fuse-1.22.1-1.2.x86_64 gvfs-backend-afc-1.22.1-1.2.x86_64

#> rpm -e --test gvfs error: Failed dependencies: gvfs = 1.22.1 is needed by (installed) gvfs-backends-1.22.1-1.2.x86_64 gvfs = 1.22.1 is needed by (installed) gvfs-fuse-1.22.1-1.2.x86_64 gvfs = 1.22.1 is needed by (installed) gvfs-backend-afc-1.22.1-1.2.x86_64 libgvfscommon.so()(64bit) is needed by (installed) gvfs-backends-1.22.1-1.2.x86_64 libgvfscommon.so()(64bit) is needed by (installed) gvfs-fuse-1.22.1-1.2.x86_64 libgvfscommon.so()(64bit) is needed by (installed) gvfs-backend-afc-1.22.1-1.2.x86_64 libgvfsdaemon.so()(64bit) is needed by (installed) gvfs-backends-1.22.1-1.2.x86_64 libgvfsdaemon.so()(64bit) is needed by (installed) gvfs-backend-afc-1.22.1-1.2.x86_64

Thanks for proving my point, which you quoted, but failed to understand:

...

Yast, and zypper are pretty weak on providing tools to find out what caused installations of packages, or what suggests packages or what recommends packages.

These package have a little incestuous ring of co-dependencies, but there is nothing indication WHAT CAUSED THEM TO BE INSTALLED. Nothing else requires them. Nothing else recommends or depends on them. I did a clean install, and it decided to install these for some unknown reason. I assure you I didn't select them to be installed. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. composed on 2014-11-15 03:11 (UTC+0100):

No, gvfs is "virtual", not a permanent filesystem. Something that is running currently creates and keeps it.

The GTK (Gnome ToolKit) app most KDE users have installed, IIRC, is Firefox, but for those who don't, many do Gimp. Maybe one of those is the villain? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-11-15 04:41, John M Andersen wrote:

On 11/14/2014 6:59 PM, Felix Miata wrote:

...

Carlos E. R. composed on 2014-11-15 03:11 (UTC+0100):

...

...

No, gvfs is "virtual", not a permanent filesystem. Something that is running currently creates and keeps it.

...

The GTK (Gnome ToolKit) app most KDE users have installed, IIRC, is Firefox, but for those who don't, many do Gimp. Maybe one of those is the villain? --

Well, I'd just like to know HOW it got installed, when no package has any of those packages as prerequisites, or recommends or anything. So packaging error is my guess. But it would be nice to have a tool that told you succinctly why a package is installed. I wander if there is any way to find other packages that do not need to be installed.

Wrong. It needs to be installed, because something is running it now, or else, that something would complain that it could not run what it expects to run. Ah, correction: the directory .gvfs can be deleted if not currently in use, but it is created again when needed, ie, when the gvfs daemon starts.

We've wandered a bit far of the original question about Baloo.

The OP asked about 'gvfs' in the first message. There is a "man gvfs" page about it. It is not really a gnome service, but a Glib one. An API for services. The directory ~/.gvfs corresponds to, or rather is created by, the daemon "gvfsd-fuse". As I use XFCE, I'm not in a position to find out when the directory is created on an KDE system. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On Sat, 2014-11-15 at 00:53 -0500, Felix Miata wrote:

John M Andersen composed on 2014-11-14 19:41 (UTC-0800):

...

Well, I'd just like to know HOW it got installed, when no package has any of those packages as prerequisites, or recommends or anything. So packaging error is my guess.

FWIW: YaST Installation is when it was installed on my last fresh 13.2 installation, 2 weeks ago. Like most of my installations, I chose minimal X Window for DE, then added selected packages and deleted selected things I don't use in package selection details, before letting package installation proceed.

Grepping RpmDb in the original y2log, gvfs was installed immediately after the kernel and immediately before device-mapper. After device-mapper followed the xf86* packages, usbutils, libusb, libpcap1, libopenobex2, libmtp9, then gvfs-fuse and gvfs-backend.

After installation, before installing any more packages, I set solver.onlyRequires = true in zypp.conf, after which I installed KDE3, before initial start of graphical.target.

/var/log/zypp/history does not contain gvfs.

To me these, plus what Carlos wrote about GLib, suggests gvfs is very likely part of one of the foundational patterns.

On that installation, ~/.gvfs does not exist. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/ If I recall correctly gvfs enables the ability to mount virtual filesystems such as CD DVD or USB flash media. I do remember many version ago having to install it manually to enable the ability to mount .iso on the desktop to use as a virtual drive.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-11-15 19:48, John Andersen wrote:

Still, because it has no "required by" in the RPMs of this little circle of packages, un-installing them would be allowed, with no warnings.

Recommends don't count. The packages should have dependencies if system functionality will be impaired.

It's still a packaging error in my opinion.

No. Installing a recommended package is not an error. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/16/2014 04:18 AM, Carlos E. R. wrote:

On 2014-11-15 19:12, Roger Luedecke wrote:

...

If I recall correctly gvfs enables the ability to mount virtual filesystems such as CD DVD or USB flash media. I do remember many version ago having to install it manually to enable the ability to mount .iso on the desktop to use as a virtual drive.

As documented:

Main processes:

· gvfsd - the main gvfs daemon

· gvfs-fuse-daemon - mounts gvfs as a fuse filesystem

· gvfsd-metadata - writes gvfs metadata

Volume monitors:

· gvfs-udisks2-volume-monitor - a udisks-based volume monitor

· gvfs-afc-volume-monitor - a volume monitor for Apple iPhone/iPod Touch devices

Mount backends:

· gvfsd-afc - mounts iPhone/iPod touch volumes

· gvfsd-afp - mounts Apple Filing Protocol volumes

· gvfsd-afp-browse - browses Apple Filing Protocol volumes

· gvfsd-archive - mounts archive files in various formats

· gvfsd-burn - provides a location for burning CDs

· gvfsd-cdda - mounts audio CDs

· gvfsd-computer - provides computer://

· gvfsd-dav - mounts DAV filesystems

· gvfsd-dnssd - browses dnssd

· gvfsd-ftp - mounts over FTP

· gvfsd-http - mounts over HTTP

· gvfsd-localtest - a test backend

· gvfsd-network - provides network://

· gvfsd-obexftp - mounts over obexftp

· gvfsd-recent - provides recent://

· gvfsd-sftp - mounts over sftp

· gvfsd-smb - mounts Windows Shares Filesystem volumes

· gvfsd-smb-browse - browses Windows Shares Filesystem volumes

· gvfsd-trash - provides trash://

The question isn't WHAT it does, its HOW did it get installed when there are no dependencies on it or any of its little circle of co-dependencies. - -- After all is said and done, more is said than done. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlRo+DYACgkQv7M3G5+2DLK80gCgrsv/zMjatposlGx70cEGQvkD O30AoKuZKHMze3o/I0MbtRBDYmMYLjAd =1U2h -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Fri, 14 Nov 2014 19:41:58 -0800 John M Andersen пишет:

On 11/14/2014 6:59 PM, Felix Miata wrote:

...

Carlos E. R. composed on 2014-11-15 03:11 (UTC+0100):

...

...

No, gvfs is "virtual", not a permanent filesystem. Something that is running currently creates and keeps it. The GTK (Gnome ToolKit) app most KDE users have installed, IIRC, is Firefox, but for those who don't, many do Gimp. Maybe one of those is the villain? --

Well, I'd just like to know HOW it got installed, when no package has any of those packages as prerequisites, or recommends or anything.

gvfs is recommended by libgtk-2_0-0 which you almost certainly have. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org