Bug 264974 - Unnecessarily HDD/NFS share spin up in systemsettings -> Digital Camera
Summary: Unnecessarily HDD/NFS share spin up in systemsettings -> Digital Camera
Status: RESOLVED DUPLICATE of bug 264487
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: kamera (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Marcus Meissner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-31 17:19 UTC by Jimmy Kloss
Modified: 2011-02-02 13:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jimmy Kloss 2011-01-31 17:19:04 UTC
Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

The Digital Camera Module under System Settings access all available FS, thus mounting and spinning up automounted storage like a rarely used HDD and even an NFS share.

Reproducible: Always

Steps to Reproduce:
1. Have sleeping drives accessable (e.g. automount)
2. Click on Digital Camera in System Settings
3. Hear your drives start screaming

Actual Results:  
All connected HDD scream

Expected Results:  
Sleeping HDD should not be treated as Cameras

No Digital Camera was plugged in.
Comment 1 Christoph Feck 2011-01-31 20:49:08 UTC
Since there are no changes in the camera module, the problem is likely related to Solid changes.
Comment 2 Marcus Meissner 2011-01-31 20:59:32 UTC
libgphoto2 does scan mountpoints, but the behjaviour did not really change the last years. (except after removing HAL support 

but we do filter out quite a number of filesystem types:


                        if ((NULL != strstr(mntent->mnt_fsname,"fd"))   ||
                            (NULL != strstr(mntent->mnt_fsname,"floppy")) ||
                            (NULL != strstr(mntent->mnt_fsname,"fuse")) ||
                            (NULL != strstr(mntent->mnt_fsname,"nfs"))  ||
                            (NULL != strstr(mntent->mnt_fsname,"cifs")) ||
                            (NULL != strstr(mntent->mnt_fsname,"smbfs"))||
                            (NULL != strstr(mntent->mnt_fsname,"afs"))  ||
                            (NULL != strstr(mntent->mnt_fsname,"autofs"))||
                            (NULL != strstr(mntent->mnt_fsname,"gphotofs"))
                        ) {


what fs types do you drives have?
Comment 3 Jimmy Kloss 2011-02-01 12:34:35 UTC
Both drives are mounted as autofs via systemd. The real fs is xfs on both. Also I remember that this problem also occured in earlier versions of kde, but I didn't reported it then, because I don't use the Digital Camera module, just clicked it out of curiosity.

Here's the relevant mount output:
Remote NFS (xfs):
systemd-1 on /mnt/auto/mybook type autofs (rw,relatime,fd=26,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
Local HDD (xfs):
systemd-1 on /mnt/auto/hitachi type autofs (rw,relatime,fd=40,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
Comment 4 Jimmy Kloss 2011-02-01 12:48:20 UTC
I just remembered I also have symlinks in my homedirectory which point to directories on these drives. I used to have these symlinks directly under $HOME, but at one point I hab to put them into subdirs so that konqueror/dolphin don't spin up the drives on every start.

e.g.
$HOME/Hitachi/LinkToSubfolder -> /mnt/auto/hitachi/Subfolder
Comment 5 Kevin Ottens 2011-02-01 19:06:56 UTC
From the description it's really hard to tell if that's coming from libsolid or not... Marcuss, could you point me at where libsolid is used in kcm? I could take a peek at the code I guess.
Comment 6 Marcus Meissner 2011-02-01 22:04:00 UTC
i have no idea of libsolid,   just of the camera kio slave and libgphoto2.
Comment 7 Kevin Ottens 2011-02-02 07:49:29 UTC
Checked the code, indeed no use of libsolid there.
Comment 8 Lukáš Tinkl 2011-02-02 13:47:59 UTC

*** This bug has been marked as a duplicate of bug 264487 ***