Greetings~

I have recently installed a fresh slackware 13.1 and enjoy it very much so far.
Something strange happend however, I am not even sure I can list everything I did.

Ok.

I still had 2 ntfs partitions on here, both should have been included during install (as umask=022) .. ok, one of them wasn't .. could have been I just clicked the wrong option, so it had this little red x on it, didn't let me open or play it.

as root I could go there with thunar and open it, well, I think I needed kdesu, though to copy something over to the ext4...

when exactly this started I am not too sure, but this is the bug that matters (sorry for the long prelude ):

when I open thunar everything is fine, I can mark and open files, but as soon as I doubleclick one folder to open it, it opens, but then I cannot click any file anymore, not even mark it, when I click anywhere in the fileview in thunar, NOTHING happens... until I close that thunar window and open a new one.... always only good for one folderopening...

weeeeeeeeeeeeird

ok, I am new to linux (a few tries years ago, but this one seems like I'll stay with it) ... so if any of you guys could help me figure out what the hell is happening there, I'll be totally thankful

edit: forgot to mention that dolphin (other filemanager) works perfectly, now that i set the other ntfs partition on umask=022 it also works perfectly there. just thunar acts up...

tried switching views in thunar?
ctrl+1
ctrl+2
ctrl+3
not a solution but workaround for a known bug

heh... thanks for the quick reply...

it works... but I would really need the detailed view...
and also know if I should just redo the whole OS (was my alternative plan to posting here )

if it is a known bug, would you know any keyterms I could search for? (here or in other forums)

That happens to me in Thunar and PCManFM, too. It's almost certainly a bug.

Here are some options:

1) Try different file managers.

2) Use the command line instead of a GUI file manager. See the tutorial links in my sig if you don't know how.

ook, i got it..

rm -rf .config/xfce4
restart...

something seemed to have been screwey there. thx anyway

!!!!!!!!edit: sry, not a fix, i had mistaken nautilus for thunar... lol

So deleting .config/xfce4 fixed it?

I believed no because it's known and reported bug. Try searching on google.

No, it didn't, sorry. I thought it did. but.. no.



It's funny, when I google for answers (various topics), I _very often_ end up in forum threads that conclude: "hey, just google it...". You do see the irony, right?



aaand, as I said two posts earlier:
It is just hard for me to believe that there is no fix for this ridiculous thing. (I mean fix, no workaround. If I'd do that I could've stayed with windoze :S )


.

I guess that the only thing I can say is use Dolphin or Nautilus.

Or just the terminal.

https://bugs.launchpad.net/ubuntu/+s...xo/+bug/520118
that should be it, i got it from firefox history