Version: unspecified (using KDE 4.6.4) OS: Linux Using Chromium, on webpages that allow uploading a file I cannot drag a file from Dolphin onto the “Select file” form input to upload that respective file. Dragging pictures from Gwenview’s preview sidebar works just fine but in Dolphin all the files show the "Dnd" cursor when dragging over Chromium. And Rekonq doesn’t even handle a drag event on such items, it just opens that file. Reproducible: Always Steps to Reproduce: . Expected Results: .
Same here, cannot drag/drop from Dolphin to Chrome/Chromium for file upload (i.e. GMail). Works with any other file browser (Krusader or a Gnome file browser).
Also doesn’t work in Dolphin 2.0 with the new view-engine thing.
Dragging pictures into Google-Chrome with Dolphin 2.0 works fine here (tested with GMail and Google-Image-search and by dragging a .jpg image). I currently cannot test it with Dolphin 1.7 (KDE applications 4.7) but I remember that there was an issue with that version...
I just checked dolphin 1.99 and gmail in google chrome. It worked just fine :)
Weird, neither with KDE 4.7.3 Dolphin, nor with a few days old git it worked :( No matter what kind of file I drag or what view mode is active, I always get that "Invalid" mouse pointer when dragging it over chromium; I tested it on various pages and using a simple html file with just an upload form. Didn’t work in all cases…
Git commit ab4353e2308ba6f2919b54d67d2a9408303ef76d by Peter Penz. Committed on 27/12/2011 at 15:50. Pushed by ppenz into branch 'KDE/4.8'. Fix issue that dragging pictures/videos to Google-Search/YouTube fails Related: bug 289917 Related: bug 278236 FIXED-IN: 4.8.0 M +1 -1 dolphin/src/kitemviews/kitemlistcontroller.cpp http://commits.kde.org/kde-baseapps/ab4353e2308ba6f2919b54d67d2a9408303ef76d
Git commit 7e4268535b66408ba6a649a4832ab47494e9e829 by Peter Penz. Committed on 27/12/2011 at 15:50. Pushed by ppenz into branch 'master'. Fix issue that dragging pictures/videos to Google-Search/YouTube fails Related: bug 289917 Related: bug 278236 FIXED-IN: 4.8.0 M +1 -1 dolphin/src/kitemviews/kitemlistcontroller.cpp http://commits.kde.org/kde-baseapps/7e4268535b66408ba6a649a4832ab47494e9e829
This bug appears again plasma 5 desktop :( Currently using dolphin: 15.12.0 kf5: 5.16 qt: 5.5.1
I have encountered this bug again in plasma 5. Here are my version information: Dolphin: 15.12.1 KDE Frameworks 5.16.0 Qt 5.5.1 (built against 5.5.0) the xcb windowing system
i can confirm the last comment, same here with plasma 5 info: KDE Frameworks 5.18.0 Qt 5.5.1 (compilado con 5.5.1) El sistema de ventanas xcb
(In reply to Tete from comment #10) > i can confirm the last comment, same here with plasma 5 > > info: > KDE Frameworks 5.18.0 > Qt 5.5.1 (compilado con 5.5.1) > El sistema de ventanas xcb sorry i forget to put Dolphin Version: 15.12.1
I can confirm that with KF5 5.18 Qt 5.5.1 and Dolphin 15.12.1
Reopening based on last comments.
I can confirm that too. If you need some more info, I will try to help.
I also experience this behaviour. Very frustrating as my employer uses google drive exclusively. Temporarily switched to Gnome Files so can work. Dolphin 15.12.2 KDE Plasma 5.5.5 Qt 5.5.1 kernel 4.4.3-1
Please fix it!
I confirm too
I can add that Dolphin4 works well with Chrome/Chromium
I also noticed, that I could copy&paste links to file-urls from dolphin4 (urls like "file:///home/..." via ctrl+c) into other applications (like kwrite/..) as text, which does not work anymore. I have open klipper and select "edit content.." and copy the text from there.
I confirm this problem here as well. Drag and drop from Dolphin doesn't work with emacs either.
I also encountered this problem (cannot drag-n-drop files to Opera).
This bug is Qt related. I'm now on Qt5.6. The bug is still present. Here the bug is discussed upstreamed with a proposed solution: https://bugreports.qt.io/browse/QTBUG-45812 A duplicate is this bug: https://bugs.kde.org/show_bug.cgi?id=355761
Thanks, I'll set the status of this bug report to resolved upstream.
*** Bug 355761 has been marked as a duplicate of this bug. ***
Not calling BS, but why does it work with FF if it's a QT issue?
*** Bug 358184 has been marked as a duplicate of this bug. ***