Bug 291219 - cifs file created in network directory when viewing option changed in Dolphin
Summary: cifs file created in network directory when viewing option changed in Dolphin
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 1.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-10 22:06 UTC by jmeidal
Modified: 2013-07-26 08:14 UTC (History)
0 users

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 jmeidal 2012-01-10 22:06:11 UTC
Version:           1.7 (using KDE 4.7.4) 
OS:                Linux

When I am browsing in Dolphin on a cifs mounted drive (mounted through fstab at
start-up) and I toggle views (between Icons and Details for example, or using
Ctrl+1, Ctrl+2), or sort a list, or change to Preview, I have a "cifs*****"
file created in that directory--every time!

Reproducible: Always

Steps to Reproduce:
1. Open Dolphin
2. Browse to a network mounted directory
My fstab line looks like this:
//192.168.123.136/docs/ /home/username/dir cifs  
guest,_netdev,uid=username,gid=users,comment=systemd.automount   0 0
3. Press Ctrl-1 or Ctrl-2 to toggle view from Icon to Detail

Actual Results:  
a cifs***** file appears listed in the directory
e.g. file "cifs2a6d" is created with the code:
19616
dolphin
username

Expected Results:  
Simply a sort or modified view of the directory, no adding of a file.

Also filed here: https://bugzilla.novell.com/show_bug.cgi?id=740572
Comment 1 jmeidal 2012-02-02 23:10:48 UTC
I can confirm this still occurs in Dolphin 2.0
Comment 2 Jeroen van Meeuwen (Kolab Systems) 2012-08-24 16:19:49 UTC
Resetting assignee to default as per bug #305719
Comment 3 Frank Reininghaus 2013-04-30 12:47:22 UTC
Hm, Dolphin itself does most likely not create such files. Maybe this is done by the kioslave that provides the cifs access?
Comment 4 Frank Reininghaus 2013-05-24 08:27:02 UTC
Is that still reproducible in KDE 4.10? If yes, we should probably reassign this to a more suitable product.
Comment 5 Frank Reininghaus 2013-07-26 08:14:22 UTC
No feedback -> closing.