Tim Edwards posted on Thu, 02 Jun 2011 22:39:10 +0200 as excerpted:
> First off, thanks for the detailed explanation of the autostart
> locations, I've saved it to a text file as a reference.
>
> However the problem is that although all those autostart locations you
> detailed are managed by the
Kevin Krammer posted on Thu, 02 Jun 2011 21:33:11 +0200 as excerpted:
> On Thursday, 2011-06-02, Stephen Dowdy wrote:
>> I have hunted around a bit, but not come up with anything i can run
>> with yet, but want to populate the plasma panel with "standard"
>> widgets. Below is a shell script i use
Tim Edwards wrote, On 06/02/2011 02:10 PM:
> Thanks for the script. I'm not sure what you mean exactly. The config path is:
> config =
> /home/tim/.kde4/share/config/:/usr/share/kde4/config/:/etc/kde4/share/config/
> [/usr/share/kde4/config/]
>
> Does that mean KDE scans all those directories f
On Thu, 02 Jun 2011 14:54 +, "Duncan" <1i5t5.dun...@cox.net> wrote:
> Tim Edwards posted on Thu, 02 Jun 2011 11:53:52 +0200 as excerpted:
>
> > Recently I found that knetworkmanager wasn't starting up when I logged
> > into KDE. I tried looking for any mention of it in the 'startup and
> > s
On Thursday, 2011-06-02, Stephen Dowdy wrote:
> I have hunted around a bit, but not come up with anything i can
> run with yet, but want to populate the plasma panel with "standard"
> widgets. Below is a shell script i use on KDE3 to allow user to
> quickly select some standard widgets to add to '
I have hunted around a bit, but not come up with anything i can
run with yet, but want to populate the plasma panel with "standard"
widgets. Below is a shell script i use on KDE3 to allow user to
quickly select some standard widgets to add to 'kicker' panel,
but i'd like the equivalent for KDE4.
Stephen Dowdy posted on Thu, 02 Jun 2011 09:10:15 -0600 as excerpted:
> I was surprised when using the kcmshell4 autostart center that it was
> using the XDG autostart path to write a new autostart desktop function.
> I thought it would prefer the KDE4 autostart path. I'm not sure if that
> indi
Tim Edwards wrote, On 06/02/2011 03:53 AM:
> Recently I found that knetworkmanager wasn't starting up when I logged
> into KDE. I tried looking for any mention of it in the 'startup and
> shutdown' control centre module, but no luck. Eventually I found a tip
> on a forum that I had to set 'Autostar
On Thursday, June 02, 2011 10:53:52 AM Tim Edwards wrote:
> Recently I found that knetworkmanager wasn't starting up when I logged
> into KDE. I tried looking for any mention of it in the 'startup and
> shutdown' control centre module, but no luck. Eventually I found a tip
> on a forum that I had t
Tim Edwards posted on Thu, 02 Jun 2011 11:53:52 +0200 as excerpted:
> Recently I found that knetworkmanager wasn't starting up when I logged
> into KDE. I tried looking for any mention of it in the 'startup and
> shutdown' control centre module, but no luck. Eventually I found a tip
> on a forum t
>
> Meanwhile, are you going to try omitting the various sections as
> suggested, or are you taking an "if it works, don't break it" attitude?
> The don't break what's working stance is certainly a valid choice, but if
> you do try it without those sections, I'd appreciate it if you posted
John Woodhouse posted on Thu, 02 Jun 2011 01:38:01 -0700 as excerpted:
> One aspect - the script will be run via a desktop icon which I assume
> means a .desktop file to activate it running in the console. That means
> the shell will flash up briefly which is rather untidy. Maybe there is
> no nee
Recently I found that knetworkmanager wasn't starting up when I logged
into KDE. I tried looking for any mention of it in the 'startup and
shutdown' control centre module, but no luck. Eventually I found a tip
on a forum that I had to set 'Autostart=true' in
~/.kde4/share/config/networkmanagementrc
Thanks folks. As usual I haven't been here before but it looks like I have
found
a solution to my nas problems but there are complications.
One aspect - the script will be run via a desktop icon which I assume means a
.desktop file to activate it running in the console. That means the shell wi
14 matches
Mail list logo
