Description of problem: While gtk-qt-engine was enabled, I wasn't able to open gvim; it would hang without ever showing a window and had to be Ctrl-C'd. As soon as I removed gtk-qt-engine (didn't try disabling it), gvim opened fine again. Version-Release number of selected component (if applicable): gtk-qt-engine-1.1-1.fc9 How reproducible: Every time Steps to Reproduce: 1. Type "gvim" Actual results: Hang until it's killed Expected results: My favourite retro text editor to open
I can reproduce the failure. Odds are it's an application bug (gtk-qt-engine is good at exposing stuff like that). Reassigning to vim.
Seems to be an issue in Ubuntu too ...
Additional information gathered from the Ubuntu bug: running "gvim -X" (telling it not to connect to the X server) seems to work around the bug.
Created attachment 322606 [details] Backtrace when I killed a hanging gvim Here's the backtrace I got (missing some details, sorry) when I ran gvim under gtk-qt-engine, waited for it to hang, and then typed "bt".
Another workaround: explicitly specifying a GTK style in the chooser (e.g., "Bluecurve") instead of the default "Use my style" also seems to fix the issue.
Still an issue in Rawhide with gtk-qt-engine-1.1-5.fc11.i586 vim-X11-7.2.148-1.fc11.i586 The same workaround -- choosing a specific style for GTK widgets rather than using the default -- still applies too.
*** This bug has been marked as a duplicate of bug 501427 ***