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

List:       kde-devel
Subject:    Re: Testing a KDE service
From:       Kevin Krammer <kevin.krammer () gmx ! at>
Date:       2004-12-19 20:36:41
Message-ID: 200412192136.41340.kevin.krammer () gmx ! at
[Download RAW message or body]

On Sunday 19 December 2004 06:30, N. Thompson wrote:
> Kevin Krammer wrote:

> >You could try restarting kded from the commandline
Another options might be to start KDE not from KDM but from commandline.
Then the output should be visible in the console you started from.

A nice way to do that is to use
startx -e startkde
which first starts an xterm window and runs startkde inside it, so you can see 
all output in the xterm window.

> Thanks, I'll give that a try. I really appreciate the answer btw, its
> the first reply I've gotten :-)

kde-devel can get a lot of traffic which sometimes means that the core 
developers don't have time to look into each single question.

And other developers like me often don't know enought about those internal 
systems to provide direct help.
The experience from other "core questions" shows that there are a lot of 
information to be found in the directories of the respective internal module 
in CVS (for example text files named DESIGN or README, etc)

Cheers,
Kevin

-- 
Kevin Krammer <kevin.krammer@gmx.at>
Qt/KDE Developer, Debian User
www.mrunix.de - German Unix/Linux programming forum
www.qtforum.org - Qt programming forum
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]