After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 331774 - Drag and drop a track from library to nautilus desktop creates a duplicate
Drag and drop a track from library to nautilus desktop creates a duplicate
Status: RESOLVED NOTABUG
Product: rhythmbox
Classification: Other
Component: general
HEAD
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-19 14:01 UTC by Alex Lancaster
Modified: 2006-02-21 16:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alex Lancaster 2006-02-19 14:01:47 UTC 
If I drag and drop a track to the nautilus desktop, then it creates a duplicate entry inside the library.  Note: I don't have watch enabled, so I can't figure out why it would keep track of the exported file.
Comment 1 Alex Lancaster 2006-02-21 16:42:03 UTC 
Looks like this happened to be a file that I must have inadvertantly "added" to the library from the Desktop (probably when I aborted a drag and drop), and thus had a "hidden" entry, which then "reappeared" after I dragged it to the Desktop again.  Yet another argument for committing the patch at bug #167763 (easier to see such problems).

I did notice that dragging on top of an unopened folder on the Desktop in nautilus doesn't work (i.e. the folder isn't highlighted) and the files always appear on the Desktop rather than within the intended destination folder.  I'll open up another bug on that.
Comment 2 Alex Lancaster 2006-02-21 16:51:30 UTC 
(In reply to comment #1)

> I did notice that dragging on top of an unopened folder on the Desktop in
> nautilus doesn't work (i.e. the folder isn't highlighted) and the files always
> appear on the Desktop rather than within the intended destination folder.  I'll
> open up another bug on that.

bug #332056