Bug 41797 - kfmclient kioslave permission lockout quirk
Summary: kfmclient kioslave permission lockout quirk
Status: RESOLVED NOT A BUG
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-28 04:48 UTC by warren
Modified: 2003-12-06 08:09 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 warren 2002-04-28 04:43:57 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           konqueror
Version:           KDE 3.0.0 
Severity:          normal
Installed from:    RedHat RPMs
Compiler:          gcc-2.96-110
OS:                Linux
OS/Compiler notes: Red Hat Skipjack Beta 2

Red Hat Bugzilla Report
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=63469

Within a kfmclient FTP or SFTP session if you click select Properties then Permissions of any file/folder and click "OK" a lock appears on that file/folder icon and you no longer have access to read the file.  It occurs regardless of if you change any permissions or not.  After the lock-out you can however still change the permissions.

This occurs to happen with all folders but not all files.  A filename "dmesg.txt" did not trigger this bug on my system.

Close the window and re-open and you again have access to the locked out file. 
  
Version-Release number of selected component (if applicable): 
Skipjack beta 2
kdebase-3.0.0-9
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1. sftp://username@servername.com 
2. Right-click any file Properties Permissions tab click OK. 
3. Lock out!
  
Actual Results:   
Lock appears on file or folder.  No longer able to read it via kfmclient. 
 
Expected Results:   
Shouldn't lock.



(Submitted via bugs.kde.org)
Comment 1 Dawit Alemayehu 2003-12-06 08:09:34 UTC
The redhat bug report was closed by reporter. Let's do the same here...