I'm using KDE and experience problems with several applications that I guess all use the gtk file chooser. These are firefox, inkscape, gimp and so on. When a dialog opens to select a file name to open or save to, and I type "~" at the beginning of the location bar, that expands to my user name followed by a slash. I'd expect it to be the absolute path to my home directory instead. Steps to reproduce: 1. Run KDE (without kde-misc/kgtk) 1. Start firefox / gimp / inksacpe / ... 2. File / Open... 3. Select "Location" text field 4. Type "~" Expected behaviour: Expanded to /home/myname/ Actual behaviour: Expanded to myname/ with the / being selected I'm not sure where the source of this problem lies, whether it's KDE or GTK or the apps.
Seems to work fine here (I use gnome) with gtk+ 2.12.8 and 2.12.9-r1. Which version of gtk+ do you have?
(In reply to comment #1) > Seems to work fine here (I use gnome) with gtk+ 2.12.8 and 2.12.9-r1. Which > version of gtk+ do you have? I've got gtk+-1.2.10-r12, as this is an up-to-date ~x86 system. I can reproduce the issue on xfce. I'll try emerge gnome for a try there.
(In reply to comment #2) > I'll try emerge gnome for a try there. On current ~x86 gnome-2.20.3 here there is no expansion of ~ at all. I can start a path with "~/", and can even tab-complete it. So ~ represents the home directory as it should, but doesn't get substituted in the user interface. On KDE or xfce, the moment I press ~ in an empty location bar, it gets replaced as described in comment #0.
(In reply to comment #2) > I've got gtk+-1.2.10-r12 Sorry, copied the wrong version number from my eix output. WHile that version is indeed installed as well, I also have x11-libs/gtk+-2.12.9-r1, and I'd assume that's the one that gets used. Seems like the issue is more likely related to desktop environment than GTK version.
This should now work better in gtk+-2.12.9-r2. (In reply to comment #1) > Seems to work fine here (I use gnome) with gtk+ 2.12.8 and 2.12.9-r1. Which > version of gtk+ do you have? It was fine because it was a GtkFileSystemUnix specific problem, that is, the gtk+ filechooser backend, whereas under GNOME gnome-vfs or gio backends are used instead (depending on GNOME version and if the key had been set in gconf before). Outside of GNOME there is no good documented mechanism to get the GIO/GVFS love, so people just use gtk+ filechooser backend and were affected by this bug. Anyhow, a patch grabbed from gtk-2.12 SVN branch included in 2.12.9-r2 now.
