2 Apr
2011
2 Apr
'11
11 p.m.
Tim,
Do you remember what caused that particular error message when exiting KDE/Trinity and
which patch fixed the problem?
Darrell
11:25 p.m.
New subject: [trinity-devel] "kded: ERROR: : couldn't create slave : Cannot talk to klauncher"
Did some testing on a clean 3.5.10 profile. Looks like the mediamanager causes the error
messages. Does that help ring any bells? :)
Darrell
--- On Sat, 4/2/11, Timothy Pearson <kb9vqf(a)pearsoncomputing.net> wrote:
From: Timothy Pearson
<kb9vqf(a)pearsoncomputing.net>
Subject: Re: [trinity-devel] "kded: ERROR: : couldn't create slave : Cannot
talk to klauncher"
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Saturday, April 2, 2011, 6:08 PM
Tim,
Do you remember what caused that particular error
message when exiting
KDE/Trinity and which patch fixed the problem?
Darrell
No I do not, sorry.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
3 Apr
3 Apr
12:39 a.m.
New subject: [trinity-devel] "kded: ERROR: : couldn't create slave : Cannot talk to klauncher"
More info:
In Configure Desktop, Behavior section, Device Icons tab, when the "Show Device
Icons" check box is enabled, that force starts the mediamanager, even if no devices
in the list are enabled. This results in the mentioned error message when exiting KDE.
I seem to recall that Trinity no longer showed that error message and I wondered what
patch fixed the problem.
Darrell
--- On Sat, 4/2/11, Darrell Anderson <humanreadable(a)yahoo.com> wrote:
From: Darrell Anderson
<humanreadable(a)yahoo.com>
Subject: Re: [trinity-devel] "kded: ERROR: : couldn't create slave : Cannot
talk to klauncher"
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Saturday, April 2, 2011, 6:25 PM
Did some testing on a clean 3.5.10
profile. Looks like the mediamanager causes the error
messages. Does that help ring any bells? :)
Darrell
--- On Sat, 4/2/11, Timothy Pearson <kb9vqf(a)pearsoncomputing.net>
wrote:
From: Timothy Pearson
<kb9vqf(a)pearsoncomputing.net>
Subject: Re: [trinity-devel] "kded: ERROR: : couldn't
create slave :
Cannot talk to klauncher"
To: trinity-devel(a)lists.pearsoncomputing.net
Date: Saturday, April 2, 2011, 6:08 PM
> Tim,
>
> Do you remember what caused that particular
error
message when exiting
---------------------------------------------------------------------
KDE/Trinity and which patch fixed the problem?
Darrell
No I do not, sorry.
Tim
To unsubscribe, e-mail:
trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
5013
days inactive
5014
days old
3 comments
2 participants
participants (2)
-
Darrell Anderson -
Timothy Pearson