Version: (using KDE 4.1.1) OS: Linux Installed from: Unspecified Linux OK... i'm attaching a ZIP file originated in windows 2000 and windows XP containing some folders. Trying to extract these in KDE will result in a "file doesn't exists". You can use other managers to do the trick (nautilus, preferently in a GNOME enviroment) but if you return to kde, these files will look strange symbols and trying to browse with dolphin with these, will result in a "file doesn't exist" message. The same occurs if you try to decompress in windows (it will be OK) share them, and browse them from a windows share, a samba share configured using UTF-8 Encoding. Happens in both, local and from a share. Using other manages (nautilus, thunar with fuse trick) will work as workaround. I don't include one folder created under KDE since i can't create one cleanly. (Dolphin allows to create them, but will produce an error message after create them (file doesn't exists) and the folder/file produced will contain strange charaters unrecognizable for nautilus/thunar. These two can create files with these characters cleanly and with no problems, and are readable from nautilus/thunar/windows 2000/xp/vista with no problem. 4.0 crashes, 4.0.2 doesn't crash anymore, 4.1.1 buggy and 4.1.2 (using archlinux) is buggy also. Hope this is clear... english is not my language (in case you haven't figured out by now). J.
Created attachment 27603 [details] Test folders created under windows 2000 sp4 and compressed using 7zip
Created attachment 27604 [details] Test folders created under windows XP Sp3 and compressed using 7zip
*** This bug has been confirmed by popular vote. ***
KDE 4.1.3 still has the bug. UPDATE: when browsing from a windows share, dolphin will print "The process for the smb://winshare protocol died unexpectedly. J.
" UPDATE: when browsing from a windows share, dolphin will print "The process for the smb://winshare protocol died unexpectedly. " It can be connected with bug 173778 http://bugs.kde.org/show_bug.cgi?id=173778 .
*** This bug has been marked as a duplicate of bug 158639 ***