[Jaunty] Desktop launchers created with wrong permissions set

Bug #340425 reported by nyarnon
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Panel
Fix Released
Medium
gnome-desktop
Invalid
Undecided
Unassigned
gnome-panel (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

When I create a launcher on the desktop it will not be marked as a executable thus triggering the message if you want it to mark as one when you try to execute it.

Related branches

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Revision history for this message
khoma (khoma1985) wrote :

I do confirm the bug. When creating a new launcher on the desktop it is not marked as executable, consequently it triggers the message of warning and it doesn't show the icon.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

What warning does it show? Desktop files don't need to be executable AFAIK. If it is a warning about the launcher being untrusted, and gives you the option to mark it as trusted then that is a design decision and is expected behaviour.

Revision history for this message
Tuomas Aavikko (taavikko) wrote :

Discussion on ubuntuforums: http://ubuntuforums.org/showthread.php?t=1087697

lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

The behaviour described in the forum thread isn't a problem with creating launchers - it is the expected behaviour of Nautilus due to a recent patch meaning that you have to manually mark new launchers you create as being trusted.

Changed in gnome-desktop:
status: Incomplete → Invalid
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Ok, I see now. Nautilus does require the desktop files to be executable now, as a fix to bug 153438. So perhaps newly created launchers should be executable by default, or would that defeat the original reason for this change?

Changed in gnome-desktop:
status: Invalid → Confirmed
Revision history for this message
nyarnon (cabal) wrote :

Thats the issue I will be more detailed next time sorry. And if it would defeat the original purpose I think we have a problem. It's not very logicaly to John Doe to create a launcher and then not being able to see f.i. the icone going with it. That already might prevent him from even to try to run it. Thats what started the thread http://ubuntuforums.org/showthread.php?t=1087697 and see where it brought us.

Revision history for this message
nyarnon (cabal) wrote :

How about adding a dialog during creation asking for confirmation to make it executable. That would clearify things.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

I'm not sure how a confirmation dialog when you create it is better than a confirmation dialog when you launch it really. If the Nautilus change was purely to protect people inadvertently downloading malicious desktop files, then I think that newly created desktop files should just be created with the executable it set.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

I've added an upstream task, with the intention of forwarding this upstream when I get a few minutes spare this afternoon. Perhaps someone here would like to send it to http://bugzilla.gnome.org/ ?

Revision history for this message
nyarnon (cabal) wrote :

@Chris

A confirmation dialog would clarify that the launcher isn't more then a plain textfile untill it gets executable rights and therefore explain why it wouldn't show an icon. As running a launcher it the default choice for a user they would certainly confirm the question and thus not be confronted with an iconless something on their desktop. And what better time to make that choise on creation?

Ofcourse I rather see it just set the right permissions by itself.

Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream confirmed that's a gnome-panel bug and should be opened on bugzilla as 2.26 blocker

Changed in gnome-desktop:
assignee: nobody → desktop-bugs
milestone: none → ubuntu-9.04-beta
Changed in gnome-desktop:
status: New → Invalid
Changed in gnome-panel:
status: Confirmed → Triaged
Changed in gnome-panel:
status: Unknown → New
Revision history for this message
kindofabuzz (kindofabuzz) wrote :

Yeah this is a very annoying bug.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-panel - 1:2.26.0-0ubuntu1

---------------
gnome-panel (1:2.26.0-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    - Mark desktop files as trusted when it makes sense (lp: #340425)

 -- Sebastien Bacher <email address hidden> Tue, 17 Mar 2009 02:13:51 +0100

Changed in gnome-panel:
status: Triaged → Fix Released
Changed in gnome-panel:
status: New → Fix Released
Changed in gnome-panel:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.