User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.8) Gecko/20071004 Iceweasel/2.0.0.8 (Debian-2.0.0.8-1) Build Identifier: I have a dual screen X setup (first DISPLAY=:0.0, second :0.1). When am on my second screen and I type a file-name to have thunar navigate to the entry in the current directory, the window gets placed on the first screen. Reproducible: Always Steps to Reproduce: 1. Open thunar on the secondary display 2. Type something Actual Results: path entry window gets placed on second screen instead of the first Expected Results: path entry window should get placed on the current (second) screen. If I read the code correctly, then thunar-path-entry.c implements this navigate-by-typing feature. I don't see any reference in there to GdkScreen, rather it seems like the gtk_entry_completion is just tied to the gtk_tree_model. Looking at the documentation for gtk_entry_completion, I don't see anything about specifying a screen either. That makes it look like a gtk bug. But in other applications like nautilus or brasero the same feature works fine and the window appears on the correct X screen. If you don't have a dual screen setup, maybe you can give me pointers on what to investigate next?
You are talking about the typeahead feature? Or do you mean the path entry that pops up with Ctrl+L?
Sorry for not being more precise, but I wasn't sure of the proper name. I mean the typeahead feature.
In icon view or list view?
I always use the detailed list view, there the bug appears. Not in icon or compact list mode though.
Aye, so the bug is in GtkTreeView (which is used for the list view). Please file a bug report to GTK+ (on bugzilla.gnome.org).