Hmmm...
In the case of KDE on linux (kubuntu), not having the executable flag
set results in KDE asking if you really want to run the program, and if
you press the continue button, the program actually runs and the
exclamation point is removed.
In FreeBSD, KDE gives you the same warning, but if you decide to still
run the program, it strangely tries to run the binary directly from your
home directory, ie "/home/username/pidgin". This of course fails and the
exclamation point is never removed either (and the executable flag is
never set).
Let me know if you'd like a screenshot of the error.
-Cameron
On 06/10/2012 10:06 AM, Tijl Coosemans wrote:
On 02-06-2012 20:01, Alberto Villa wrote:
On Fri, Jun 1, 2012 at 6:25 PM, Cameron Berkenpas<c...@neo-zeon.de> wrote:
I'm seeing an issue where if I drag entries from the Applications menu to
the desktop in KDE 4.8.3 (I've seen this issue with KDE 4.7.x in FreeBSD
too), I get an icon with an exclamation point. If I double click on the
icon, it attempts to run the application directly from my home directory and
I get 2 popup windows.
The 1st window states:
"This will start the program:
/home/username/pidgin
If you do not trust this program, click Cancel"
Then when I click continue I get:
"Unable to make the service Pidgin executable, aborting execution"
Note that the exclamation point remains.
I did some digging and the issue is that the icons are being created in
/home/username/Desktop with 444 permissions (and sometimes 644). To fix the
issue, the permissions need to be 755 (presumably 555 would work too).
I found that the permissions are being copied along with the icons from
/usr/local/share/applications/ (so my umask of 022 is ignored). All the
icons in /usr/local/share/applications/ are 444 (except for 2 which were
644). I "fixed" the issue by setting the permissions of
/usr/local/share/applications/*.desktop to 755. Now I can copy icons from
the applications menu without issue.
This is a problem with the pidgin port (and presumably others), which
uses ${INSTALL_DATA} to install the file manually, and that doesn't
obviously add the execution bit.
Note: Icons from other directories where the icons already have 755
permissions work with no changes (ie
/usr/local/kde4/share/applications/kde4).
Rules for their installation are inside the tarball, not our own.
Not sure if the bug is that the icons under /usr/local/share/applications/
need to be created with 755 permissions or if KDE needs to not require
executable permissions on files it doesn't directly execute (*.desktop
files).
I wouldn't call this a bug. Anyway, *.desktop files should probably be
installed with execution bit. KDE behaves just fine warning you with
the exclamation mark. I agree that a more useful error message could
be reported, but that's not the point here.
I'm forwarding this to desktop@ as it's something to be discussed with
other parties. kwm@, especially.
Should we use ${INSTALL_SCRIPT} for *.desktop files?
I'd say yes. They are effectively scripts.
I think the reason KDE requires +x is to protect against malicious desktop
files downloaded from the internet or received as email attachments.
_______________________________________________
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
