User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 Build Identifier: When we want to "print in a file" from Firefox, Inkscape or any other program based on GTK in the KDE environment, it's possible to rename the file, but soon as that we select the directory, it's not possible anymore to rename the file Reproducible: Always Steps to Reproduce: After opening Firefox (or other GTK based program like Inkscape, Gimp, etc.) print the document and in the Window (See the attached picture) : 1. Select print to a file 2. Select a folder 3. Try to rename the document Actual Results: Impossible to rename the file Expected Results: Possibility to rename the file It's possible to rename the file before to select the directory but not after.
This is gtk2 and gtk3 bug. For gtk2 apps workaround is downgrade to gtk2-2.24.10 because bug appeared in 2.24.11.
confirmed with thunderbird too. It's worse, once one selects the folder field of the print dialog, it's impossible to do *any* keyboard input into any widget/field on the print dialog, not just the filename field. Tested shotwell, a gtk3 app, and that one didn't suffer this problem, so seems specific to gtk2 (or gtk3 has already been fixed?). $ rpm -q gtk2 gtk3 oxygen-gtk2 oxygen-gtk3 gtk2-2.24.11-1.fc17.x86_64 gtk2-2.24.11-1.fc17.i686 gtk3-3.4.4-1.fc17.x86_64 oxygen-gtk2-1.3.0-1.fc17.x86_64 oxygen-gtk3-1.1.0-1.fc17.x86_64
In the meantime, if a gtk2 fix isn't coming quickly, we could consider the oxygen-gtk workaround mentioned in https://bugs.kde.org/show_bug.cgi?id=299121#c11 to comment out the line GtkComboBox::appears-as-list = 1 in /usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc
*** Bug 857007 has been marked as a duplicate of this bug. ***
It seems that this behavior is caused by the commit 3f6592f60fd15fb353fc84600caefba3054dc892 (Iconification using _NET_WM_STATE_HIDDEN hint if supported by WM). The window probably needs to have called "_gdk_xgrab_check_unmap()" on itself in the UnmapNotify X event handler even if the screen supports _NET_WM_STATE_HIDDEN. I'll continue on this tomorrow. Regards Marek
The problem was really the one I've commented about in comment #5. Fortunately enough it is already fixed in 2.24.12, 3.4.4 and master. See commits http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=a9fb816a3f64227936f4b25882e4f20ab5018c9c , http://git.gnome.org/browse/gtk+/commit/?h=gtk-3-4&id=18de282771b30e6e9ab8c2c8ba314484a29ac643 and http://git.gnome.org/browse/gtk+/commit/?id=16458b0de2203a0956c55f21d18e6af916e4c066. We just don't have gtk+-2.24.12 in updates yet. Regards Marek
> We just don't have gtk+-2.24.12 in updates yet. And when can we expect it?
FYI, nucleo asked the same question on IRC and got this answer: <mclasen_> will appear sometime this week, I hope
*** Bug 854994 has been marked as a duplicate of this bug. ***
gtk2-2.24.13 built for F19 and for F18 but not for F17, so this bug still actual.
This update should fix bug https://admin.fedoraproject.org/updates/FEDORA-2012-16441
gtk2-2.24.13-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-16441/gtk2-2.24.13-1.fc17