I experience this too and I was surprised not to see the 'Mark as trusted' option that was in 9.10.
Whether this is a regression bug where functionality has been affected by a change elsewhere or whether this is functionality by design is not clear. What is clear is that to a standard user the error text "The application launcher "xxxx.desktop" has not been mark as trusted. If you do not know the source of this file, launching it may be unsafe" is of no use whatsoever. And offering cancel as the only selection to proceed with no guidance on how to rectify the problem is even less useful. The average user will right click the icon and look for and option like "Mark as trusted". Even if the do look at the permissions tab in file properties, there is no correlation between "Allow executing file as a program" and "Mark as trusted". The hope is the user will make this correlation or make a lucky guess and select this option without being sure of the real consequences. Since when did a file with the execute bit set become known as a "trusted file", did I miss a memo? In fact trusted/untrusted aren't standard Linux file permissions aer they and so this wording is misleading at best. Especially when a simple Google search for "how to mark file as trusted in ubuntu" results in pages describing this bug and no "how-tos" on how to make a file trusted. It's bad terminology. At least if the "Mark as trusted" option were retained users who do know the source of the launcher would have an easy mechanism to be able to execute it without resorting to a Google search and looking through a bug report for command line based workarounds. As such I believe this sits firmly in regression bug territory, if only because there is no mechanism for making a launcher trusted provided in the pop-up window or even described in the error text. I can only assume this behaviour has been implemented by a developer (not necessarily an Ubuntu dev) used to the nannying ways of Windows where at all times the user needs to be encouraged to be safe, but has erred on the side of "ultra-nanny" whereby no option to 'trust' the launcher is provided and the nanny won't even tell you how to do it via alternative means. It's disappointing that situations like this are being implemented and/or devs are seeing this as good practice, because its really elementary usability design. Let's hope "ultra-nanny" isn't part of Ubuntu's re-branding and that this is a simple bug, acknowledged, easily remedied by re-introducing the previous behaviour of the pop-up and users aren't being encouraged to resort to command line based solutions. -- Can't launch untrusted app-launchers (.desktop) in GNOME https://bugs.launchpad.net/bugs/572918 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
