Bug 455413 - gtk-qt-engine prevents gvim from opening
gtk-qt-engine prevents gvim from opening
Status: CLOSED DUPLICATE of bug 501427
Product: Fedora
Classification: Fedora
Component: vim (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Karsten Hopp
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-15 09:21 EDT by Mary Ellen Foster
Modified: 2009-05-26 04:54 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-05-26 04:54:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Backtrace when I killed a hanging gvim (5.61 KB, text/plain)
2008-11-05 11:42 EST, Mary Ellen Foster
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 270972 None None None Never

  None (edit)
Description Mary Ellen Foster 2008-07-15 09:21:40 EDT
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):

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
Comment 1 Rex Dieter 2008-09-05 12:19:55 EDT
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.
Comment 2 Mary Ellen Foster 2008-11-05 11:03:58 EST
Seems to be an issue in Ubuntu too ...
Comment 3 Mary Ellen Foster 2008-11-05 11:06:35 EST
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.
Comment 4 Mary Ellen Foster 2008-11-05 11:42:10 EST
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".
Comment 5 Mary Ellen Foster 2008-11-28 10:16:34 EST
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.
Comment 6 Mary Ellen Foster 2009-04-17 04:37:35 EDT
Still an issue in Rawhide with

The same workaround -- choosing a specific style for GTK widgets rather than using the default -- still applies too.
Comment 7 Karsten Hopp 2009-05-26 04:54:40 EDT

*** This bug has been marked as a duplicate of bug 501427 ***

Note You need to log in before you can comment on or make changes to this bug.