Destination folder "(null)" does not exist when dragging over chromium

[Richard Eames]

Steps to reproduce:
- Open an archive with the file-roller gui
- Place the window over top of chromium
- Open a nautilus window
- Drag the contents of file-roller (to extract them) over to the nautilus window making sure that the dragged content passes over the chromium window.

Expected Results:
- Nothing should happen until I drop the contents onto the nautilus window at which point the content is extracted

Actual Results:
- An error message pops up: Destination folder "(null)" does not exist. Do you want to create it

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: file-roller 3.14.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat May 9 13:04:35 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-08-21 (261 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
SourcePackage: file-roller
UpgradeStatus: Upgraded to vivid on 2015-04-07 (31 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Carkis (carlosdark)]

This also happens when dragging the files on top of Chrome.

[Victor Englund (victor-englund)]

This also happens when dragging onto another monitor (in a dual monitor setup).

[Richard Eames (naddiseo)]

@victor, I can't replicate that with my tri-monitor setup, so it must be a different bug (with same symptoms perhaps).

[Victor Englund (victor-englund)]

@richard, sorry, my mistake - I actually had a _small_ portion of chromium behind when I dragged it to nautilus on my second monitor.

[Cristiano Fraga G. Nunes (cfgnunes)]

Fix committed, see:

https://git.gnome.org/browse/file-roller/commit/?id=af95f7d8db4e99e7c661022f77097c69b0becfe2

[Sebastien Bacher (seb128)]

the new version including the fix is in wily
https://launchpad.net/ubuntu/+source/file-roller/3.16.3-0ubuntu1

[Richard Eames (naddiseo)]

Can the fix be back ported so I don't have to wait until October for it?

[Sebastien Bacher (seb128)]

It probably could if somebody is interested to work on that, it's a small cosmetic issue though so not high in the team todolist, especially on a non LTS version