summaryrefslogtreecommitdiffstats
path: root/ubuntu/maverick_automake/kdelibs/debian/man/tdelauncher-kde3.1
diff options
context:
space:
mode:
Diffstat (limited to 'ubuntu/maverick_automake/kdelibs/debian/man/tdelauncher-kde3.1')
-rw-r--r--ubuntu/maverick_automake/kdelibs/debian/man/tdelauncher-kde3.12
1 files changed, 1 insertions, 1 deletions
diff --git a/ubuntu/maverick_automake/kdelibs/debian/man/tdelauncher-kde3.1 b/ubuntu/maverick_automake/kdelibs/debian/man/tdelauncher-kde3.1
index efad216e3..c718e204c 100644
--- a/ubuntu/maverick_automake/kdelibs/debian/man/tdelauncher-kde3.1
+++ b/ubuntu/maverick_automake/kdelibs/debian/man/tdelauncher-kde3.1
@@ -8,7 +8,7 @@ tdelauncher
.sp 1
\fBtdelauncher\fP is a daemon responsible for service activation in KDE. It operates closely together with the kdeinit master process to start new processes. KDE applications communicate with \fBtdelauncher\fP via DCOP to start new applications or services.
.sp 1
-The error message "KLauncher could not be reached via DCOP" either indicates a serious problem with the \fBdcopserver\fP or \fBtdelauncher\fP crashed.
+The error message "TDELauncher could not be reached via DCOP" either indicates a serious problem with the \fBdcopserver\fP or \fBtdelauncher\fP crashed.
.sp 1
Note: \fBtdelauncher\fP is not the "run command" dialog (Alt+F2)!
.SH SEE ALSO