Description of problem: After changing directory Thunar can't select a file/dir anymore. This only happens with "view as detailed list" (ctrl-2). Version-Release number of selected component (if applicable): Thunar-1.0.1-7.fc13.x86_64 (Fedora 13 prerelease) How reproducible: Always Steps to Reproduce: 1. Start thunar and select "view as detailed list" (ctrl-2). 2. double click on any directory in the right panel to chdir there 3. try to double click on any file or directory to open it or chdir etc. Actual results: The file/dir in "3" can't be selected and one can't open it, chdir etc. Expected results: The file in question should be selected and available for opening etc.
Does the entire Thunar window become unresponsive at that point? Or is it still responsive, but you cannot select/open one particular dir?
Thunar still functions, e.g. I can change dirs using the buttons above the file list or using the left panel, the menu is still functional and I can even right-click on the right panel and the Create Folder/Create Document/etc. pop-up appears. I can't only select individual (any) files/dirs on the right panel, thus I can open them, chdir there and so on. Changing the view to Icons/Compact List fixes the problem temporarily, changing to Detailed List allows for selecting a file/dir once, and it breaks again. Looks like GTK misuse.
I was wondering if you were seeing another case of bug 579356 here, but it sounds different. Just to be sure, can you try updating: http://admin.fedoraproject.org/updates/exo-0.3.106-3.fc13 and see if that changes the behavior any?
I think both reporters describe the same issue, both are in detailed list view. both have opened a folder with the mouse previously... I can confirm this behavior when Thunar is set to use double clicks. If single click is used, everything is fine. I have updated to exo-0.3.106-3 now and the bug is gone.
Right, exo-0.3.106-3 fixes this problem for me as well. Thanks a lot.
Thanks. If you could add karma to the above update link that would be great! *** This bug has been marked as a duplicate of bug 579356 ***