By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 647 - [stdout/stderr] Odd Dcop messages in xsession log when starting TDE
Summary: [stdout/stderr] Odd Dcop messages in xsession log when starting TDE
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdelibs (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Other
: P1 minor
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2011-11-19 12:51 CST by Darrell
Modified: 2018-08-30 02:52 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2011-11-19 12:51:50 CST 
In my xsession log I see the following:

kdeinit: Shutting down running client.
kdeinit: Killing kdeinit/klauncher.
kdeinit: Launched DCOPServer, pid = 2155 result = 0
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/users/tester/.DCOPserver_hairy__0
and start dcopserver again.
---------------------------------


As I am starting my TDE for the first time of the day, with no saved session, what client is running and needs to be killed?

As I have no $HOME/.DCOPserver* files when I start TDE and I know that TDE is not already running, why do I receive that message?