If the system is generating .desktop files automatically, then it should generate different desktop files for different binaries that are in different locations. What if I run two programs that have absolutely nothing to do with each other but whose executable file happens to have the same name?!?
Generating automatically a .desktop file based on a binary name, and reusing that for another binary of the same name, is a wrong design and should be fixed (and the fix is easy). Also, if I download an executable, place it in an arbitrary place, and run it, and then delete it, I don't expect it to leave any trash around the system that will potentially affect other programs. If _it_ does, then it's that executable's author's responsibility, but if the system does, and doesn't warn me, then the system is doing somnething wrong. At least it should show a notice (with a "don't show again" option) indicating that a desktop file has been created and showing its location, so I know that I may need to delete it later. Consider at least that. And another thing: apparently the .desktop files that are automatically generated for any executable you run, not always work. I downloaded Processing (http://processing.org). It's a .tgz that you extract to a folder and then you run an executable in it. When I run it, an icon appears on the Launcher. Right-clicking and selecting "lock to launcher" locks the icon lock to the launcher, but when I later click on the icon nothing happens. So the mechanism that creates .desktop files automatically does not always work. > I'm marking this bug as invalid because the system is actually working > completely as designed. The design is seriously wrong then, and the bug should be reopened until the design is fixed. > In this case the problem can be resolved by manually fixing the > configuration (.desktop) files that are reserved for the user, > probably by removing them. Yes, given that the user figures out that a .desktop file has been created and where. Now I know that, but I had to come here to figure out. That's ridiculous. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296909 Title: What you lock to launcher is not what you get locked to launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1296909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
