[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Adding Application Icon to Desktop
From:       Dave Feustel <dfeustel () mindspring ! com>
Date:       2006-01-29 20:39:01
Message-ID: 200601291539.02454.dfeustel () mindspring ! com
[Download RAW message or body]

On Sunday 29 January 2006 14:45, Philip Rodrigues wrote:
> Dave Feustel wrote:
> 
> This is YA question for a different mailing list (viz, kde@kde.org).
> 
> > Whether or not it was intended to be, adding an application
> > icon to the desktop is currently a two-step process.
> > 
> > The first step is simply creating the icon.
> > All input to icon fields is rejected because the
> > icon starts out with even the owner having read-only
> > access.
> > 
> > The second step: once the icon has been created and installed
> > on the desktop,then the icon fields can be modified. Ie the user
> > can now fill in the description, the command, the icon,
> > etc., but only *after* the user gives himself r/w permissions
> > and checks the "is executable" box.
> > 
> > Is this the way adding icons to the desktop is *supposed* to work?
> 
> I don't see that behaviour here. Right-click on desktop->create new->link to
> application. Set the name to whatever, set the command to (say) 'kwrite'.
> Click OK. Click on the icon. KWrite opens.
> 
> Have you set your umask to something bizarre?

Is umask 077 bizarre? I also chmod 600 all my kde-related sockets as 
soon as I start kde, and nothing seems to break. 
> 
> Regards,
> Philip

-- 
Lose, v., experience a loss, get rid of, "lose the weight"
Loose, adj., not tight, let go, free, "loose clothing"
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]