GNOME Bugzilla – Bug 759078
An icon can be inadvertently dragged on top of another icon so as to cover it completely causing it to all appearances be "lost"
Last modified: 2015-12-09 12:13:37 UTC
Thanks for taking the time to report this. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read https://bugzilla.gnome.org/page.cgi?id=bug-writing.html and add a more useful description to this bug by providing exact steps to reproduce plus environment and version information. When providing a better description, please reset the status of this bug report from NEEDINFO to its previous status.
Ubuntu 14.04 LTS I recently moved over from Windows XP and I find the learning curve steep enough to want stay away from the technical side as far as possible. Still, I sympathize with open source and so I take the effort to report bugs. Downstream asked me to report the bug upstream and so I did. IMO the description I gave is an adequate instruction of how to replicate the bug. If you can't replicate this then I am at a loss of what to say. Something is wrong so somebody should do something about it. PS I cannot reset the status, because the status drop-down box only has choices of needinfo and resolved
(In reply to hpvpp@optusnet.com.au from comment #2) > Ubuntu 14.04 LTS > > I recently moved over from Windows XP and I find the learning curve steep > enough to want stay away from the technical side as far as possible. Still, > I sympathize with open source and so I take the effort to report bugs. > Downstream asked me to report the bug upstream and so I did. IMO the > description I gave is an adequate instruction of how to replicate the bug. > If you can't replicate this then I am at a loss of what to say. Something > is wrong so somebody should do something about it. Mentioning something like "the icons representing files on the desktop can overlap in version X.Y.Z" would be a good start. And the people "downstream" (from the looks of it from Ubuntu) should have helped you file a better bug. > PS I cannot reset the status, because the status drop-down box only has > choices of needinfo and resolved That's expected. Reassigning to a nautilus version 4 versions behind the current one.
Thanks for taking the time to report this bug. However, you are using version 3.10.x which is too old and not supported anymore by GNOME developers. GNOME developers are no longer working on that older version, so unfortunately there will not be any bug fixes by GNOME developers for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a recent version of GNOME, or feel free to file a bug report in the bug tracking system of your Linux distribution if your distribution still supports your version 3.10.x. If downstream asked you to report the bug upstream, please provide a link to the downstream bug report.
Thanks for these comments. I changed over from Windows because I hate it when I have to learn a new interface with every upgrade. And that is also why I opted for the LTS version of Ubuntu: because it is (relatively) stable. Now I find that my Ubuntu LTS is lagging behind development. Okay, I can live with that. Problem is, however, that I now have no easy means to decide whether it is worth reporting a bug, because it might already have been fixed though not yet placed in repository to be sent out as an update. Anyway, the downstream bug report is at https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1520726
That issue is still there in 3.18 and easy to trigger, just dnd an icon on top of another one, nautilus let you those overlap, reopening the bug... (would have been as easy to confirm with your current version than to go the negative way and to tell people off for using an older one)
(In reply to Sebastien Bacher from comment #6) > (would have been as easy to confirm with your current version than to go the > negative way and to tell people off for using an older one) @Seb128: The even easier and better way is to do this one stage earlier: Checking downstream in 3.18 first whether it's still a problem, and only after confirming it asking users to report to upstream in order to save user's time.
@Andre, right, which is what I did ;-) Current Ubuntu has 3.18 and that's what I'm using, I confirmed the bug and asked the user to report upstream. I guess I should have added "note in the bug that the issue is still happening on 3.18 as well", but I assumed it was easy enough to be verified that it wouldn't be an issue, seems like I was wrong...
Setting the version field is enough for me. But it's true that if the reporter says it's using ubuntu 14.04 is confusing. It's better a explicit confirmation of someone using 3.18 in a comment, even if it is easy to reproduce, it's kind of hard to keep track of all bug reports. For this one you can use keep-aligned option if you don't want them to overlap. So I would say it's not a bug and I'm closing it. Feel free to reopen if I'm mistaken.
(In reply to Sebastien Bacher from comment #8) > @Andre, right, which is what I did ;-) Current Ubuntu has 3.18 and that's > what I'm using, I confirmed the bug and asked the user to report upstream. Ah I wasn't aware of that! Thank you! > I guess I should have added "note in the bug that the issue is still > happening on 3.18 as well", but I assumed it was easy enough to be verified > that it wouldn't be an issue, seems like I was wrong... Such clarification is definitely welcome (and also asking the reporter who forwards it to upstream to mention that fact). That would help everybody to save some time and avoid potential misunderstandings on both sides. :)