Red Hat Bugzilla – Bug 138337
Drag-and-drop into gvim does not work
Last modified: 2008-02-03 05:02:23 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Description of problem:
Dragging files and selected text from Konqueror or the Desktop into an
open gvim window does not work. Cursor stays as the circle/slash icon
and nothing happens on mouse button release.
Drop+Drag between gvim and Konsole, gvim and Mozilla works as expected.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. drag a file icon, image, link or any other draggable element from
KDE Desktop or Konqueror window into an open gvim window.
2. Release mouse button.
Actual Results: Cursor indicates item cannot be dropped there.
Expected Results: File should have opened up in gvim window, or
selected text or link should have been pasted into the editing window.
sorry, it's not reproduceable in FC2 and latest FC3. Where do you get
the kdebase-3.2.3-2.0.1.kde? The official kdebase in fc2 is 3.2.2-6.FC2!
drag and drop works fine for me
drag and drop _into VIM_ works fine for you? This has been broken
since FC1, and I know others who have the same problem.
kdebase-3.2.3-2.0.1.kde came from http://kde-redhat.sf.net/ when I
tried to upgrade to fix this problem. Sorry, I forgot about that.
But this is also confirmed on FC3 as I just upgraded one system. The
versions of the packages on that are
Please reopen this bug, its not fixed and it is confirmed.
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.
Setting status to "INSUFFICIENT_DATA", however if you still
experience this problem after updating to our latest Fedora
release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.
Thank you in advance.