Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc3.3.1 Using Konq as a file manager and Lock to Current Location from the view menu or the status bar. When you try to move to different directory/folder, the error reported is 'There appears to be a configuration error. You have associated Konqueror with inode/directory, but it can't handle this file type.', which I guess is a low level error resulting from the lock, but which should be masked with a friendly error saying there's a lock on.
As a newcomer to Linux, I was totaly mislead by this error message.
Same thing here with KDE 3.2.2 from Mandrake RPMS - this is really confusing for new users, and I get hit by it often, after showing some poor soul how does "lock to current location" helps you do a lot of interesting stuff. I guess it shouldn't be hard to change the text to something more descriptive of the actuall problem. A better solution, IMO, is to just disable the "up directory" and other directory traversal buttons when in "lock mode"
This report is similar to the closed http://bugs.kde.org/show_bug.cgi?id=22605 Still in current CVS HEAD: If you open konqi with a single view, the "lock" action is disabled, but if you open a second _Tab_, then suddenly the "lock" action is available again, which then leads to the error when one tries to change the dir (e.g. up, home, etc).
Can still reproduce with 3.5.5
in 4.0.3 kubuntu a new dolphin window is opened, i guess this is ok
Thank you for your bug report. I confirm that konqueror now works properly in KDE SVN trunk (r806088). I close the bug as WORKSFORME.