Bug 108272 - cannot enter directory via fish called "core"
Summary: cannot enter directory via fish called "core"
Status: RESOLVED DUPLICATE of bug 106648
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: fish (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Jörg Walter
URL:
Keywords:
: 115013 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-06-28 15:24 UTC by rgpublic
Modified: 2005-10-24 18:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Screenshot (193.41 KB, image/png)
2005-06-28 15:27 UTC, rgpublic 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description rgpublic 2005-06-28 15:24:04 UTC 
Version:            (using KDE KDE 3.4.1)
Installed from:    SuSE RPMs

We have a directory called "core" which cannot 
be entered via FISH because the file type is not
shown as "directory" but as "crash report" (or sth.
like that in English) and a bomb icon. Sounds strange,
so I'll better attach a screenshot (follows)...
Comment 1 rgpublic 2005-06-28 15:27:28 UTC 
Created attachment 11614 [details]
Screenshot
Comment 2 Nicolas Goutte 2005-06-29 15:55:49 UTC 
Basically it is the same as bug #106648.

As only the file name is tested, KDE considers that the file name "core" is a core file.

Have a nice day!

*** This bug has been marked as a duplicate of 106648 ***
Comment 3 Nicolas Goutte 2005-06-29 21:24:07 UTC 
After thinking more, I am reverting the status of duplication of bug #108272. 
The reason is that #106648 can be solved in another way by testing that the 
filenmae check should be careful about not finding an extension when its is 
the only file name.

However bug #1
Comment 4 Thiago Macieira 2005-07-01 04:31:41 UTC 
No, it's the same bug. kio_fish detects file types on directory entries that aren't files.

"core" is no different than "lib*.so" or "*.cc".

*** This bug has been marked as a duplicate of 106648 ***
Comment 5 Maksim Orlovich 2005-10-24 18:46:48 UTC 
*** Bug 115013 has been marked as a duplicate of this bug. ***