Printable View
Hello
I have a problem with a new installation of Slackware 12.
Kdevelop in KDE doesn't run. I click on the icon but nothing happens.
For instance, Quanta works good.
I'm a new linux-user so I don't know how to solve this problem.
Thanks a lot for attention
Andrea
Andrea wrote:[color=blue]
> Hello
> I have a problem with a new installation of Slackware 12.
> Kdevelop in KDE doesn't run. I click on the icon but nothing happens.
> For instance, Quanta works good.
>
> I'm a new linux-user so I don't know how to solve this problem.[/color]
Try starting it from an xterm, should give you a idea about what
is/isn't working.
Blumf
On 5 Nov, 11:34, Blumf <bl...@hotSPAMmail.com> wrote:[color=blue]
> Andrea wrote:[color=green]
> > Hello
> > I have a problem with a new installation of Slackware 12.
> > Kdevelop in KDE doesn't run. I click on the icon but nothing happens.
> > For instance, Quanta works good.[/color]
>[color=green]
> > I'm a new linux-user so I don't know how to solve this problem.[/color]
>
> Try starting it from an xterm, should give you a idea about what
> is/isn't working.
>
> Blumf[/color]
ok, but what is/are the command/s I have to type to make some tests?
Andrea wrote:[color=blue]
> On 5 Nov, 11:34, Blumf <bl...@hotSPAMmail.com> wrote:[color=green]
>> Andrea wrote:[color=darkred]
>>> Hello
>>> I have a problem with a new installation of Slackware 12.
>>> Kdevelop in KDE doesn't run. I click on the icon but nothing happens.
>>> For instance, Quanta works good.
>>> I'm a new linux-user so I don't know how to solve this problem.[/color]
>> Try starting it from an xterm, should give you a idea about what
>> is/isn't working.
>>
>> Blumf[/color]
>
> ok, but what is/are the command/s I have to type to make some tests?[/color]
Just open up an xterm and type kdevelop
If it works from that then there's probably something wrong with the
icon on your desktop. If it doesn't work you should at least get some
error messages that'll help you work out what the problem is.
Blumf
On 2008-11-05, Blumf <blumf@hotSPAMmail.com> wrote:[color=blue]
> Andrea wrote:[color=green]
>> On 5 Nov, 11:34, Blumf <bl...@hotSPAMmail.com> wrote:[color=darkred]
>>> Andrea wrote:
>>>> Hello
>>>> I have a problem with a new installation of Slackware 12.
>>>> Kdevelop in KDE doesn't run. I click on the icon but nothing happens.
>>>> For instance, Quanta works good.
>>>> I'm a new linux-user so I don't know how to solve this problem.
>>> Try starting it from an xterm, should give you a idea about what
>>> is/isn't working.
>>>
>>> Blumf[/color]
>>
>> ok, but what is/are the command/s I have to type to make some tests?[/color]
>
> Just open up an xterm and type kdevelop
>
> If it works from that then there's probably something wrong with the
> icon on your desktop. If it doesn't work you should at least get some
> error messages that'll help you work out what the problem is.
>
> Blumf[/color]
Just to add, if it will not start from the comd line with kdevelop, try
starting it using the full path to the binary, probaby
/opt/kde/bin/kdevelop. If it starts, then the path to the binary isn't in
your path statement.
Or, just go to a xterm window and type:
printenv [enter]
to check the path statement.
ken
No_One wrote:[color=blue]
>
> Or, just go to a xterm window and type:
>
> printenv [enter]
>
> to check the path statement.
>[/color]
The output from that can be a bit verbose... ;)
Succinct is `echo $PATH'
On 2008-11-06, Chris Sorenson <csoren@isd.net> wrote:[color=blue]
> No_One wrote:[color=green]
>>
>> Or, just go to a xterm window and type:
>>
>> printenv [enter]
>>
>> to check the path statement.
>>[/color]
>
> The output from that can be a bit verbose... ;)
>
> Succinct is `echo $PATH'[/color]
yep
ken
On Thu, 06 Nov 2008 01:35:06 -0600, Chris Sorenson wrote:
[color=blue]
> No_One wrote:[color=green]
>>
>> Or, just go to a xterm window and type:
>>
>> printenv [enter]
>>
>> to check the path statement.
>>
>>[/color]
> The output from that can be a bit verbose... ;)
>
> Succinct is `echo $PATH'[/color]
Yeah, but you can also do that with "printenv PATH" (or any other
environment variable name) and get just the one line. Although it doesn't
seem to do that for SHELLOPTS on my PC. Granted, echo and the variable
name is four characters shorter than using printenv, but then you have to
put a $ in front of the variable name.
--
Chick Tower
For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
On Thu, 06 Nov 2008 01:35:06 -0600, Chris Sorenson wrote:
[color=blue]
> No_One wrote:[color=green]
>>
>> Or, just go to a xterm window and type:
>>
>> printenv [enter]
>>
>> to check the path statement.
>>
>>[/color]
> The output from that can be a bit verbose... ;)
>
> Succinct is `echo $PATH'[/color]
Yeah, but you can also do that with "printenv PATH" (or any other
environment variable name) and get just the one line. Although it doesn't
seem to do that for SHELLOPTS on my PC. Granted, echo and the variable
name is four characters shorter than using printenv, but then you have to
put a $ in front of the variable name.
--
Chick Tower
For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net