Thunar is practically unusable on F29. The current version, 1.8.4-1.fc29 has a bug in which the folder/tree view pane moves, when you select a folder in the view. This should not happen. It does not happen in earlier versions of Thunar. In earlier versions, the tree pane does not move unless you scroll up or down. The folder view pane MUST NOT MOVE, when you are expanding folders or selecting folders. It Absolutely MUST NOT move. It is incredibly disorienting, if you select or expand something, and then the entire tree moves underneath your mouse. You completely lose track of where you are and what you were looking at. I repeat. The tree/folder pane MUST NOT MOVE. Version-Release number of selected component (if applicable): 1.8.4 How reproducible: easily. Steps to Reproduce: 1. Open Thnar, switch to tree/folder view in the left pane. 2. Expand some folders so there are bunch of folders that dont fit on the screen, so a scrollbar appears. 3. Select a folder here or there in the tree view, and behold, as the tree view moves up and down... Actual results: Tree view moves. Expected results: Tree view does not move. Additional info: As if this bug isn't bad enough, and it is, believe me... it is just impossible to navigate around deep folder trees or trees with lots of subfolders, when the folder view is moving of its own acord. It is impossible... But... in addition to this bug, if i downgrade Thunar to the other version available in f29, Thunar 1.8.1 - i hit another bug with Thunar ignoring the Adwaita-Dark theme that i have set. So, suddenly, i have a white Thunar glaring at me, completely blinding me. It is appalling. The combination of these two bugs means Thunar is completely unusable currently, on f29. Pls fix... ASAP. i have also created a bug for tihis in Red Hat Fedora bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1701829
Thanks for reporting, should be fixed in master / 4.14 branch. Fix not yet released. Please take a try for the fix. rich.trefz still reports minor problems, however I cannot reproduce them .. thats why the bug is still open. *** This bug has been marked as a duplicate of bug 15174 ***