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 884 - [stdout/stderr] tdmctl: Cannot connect socket '/var/run/xdmctl/dmctl-:0/socket'
Summary: [stdout/stderr] tdmctl: Cannot connect socket '/var/run/xdmctl/dmctl-:0/socket'
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Other
: P1 normal
Assignee: Timothy Pearson
URL:
: 648 (view as bug list)
Depends on:
Blocks: 2968
  Show dependency tree / graph
 
Reported: 2012-03-01 18:50 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 2012-03-01 18:50:01 CST 
I'm seeing this message in my xsession log.

==========
Bug No. 1:
==========

I am starting X/TDE from the command line through the startx script. TDM is not running and should not be in the big picture anywhere.

In the code I found only two apps that call tdmctl: the TDM greeter and tsak. I rebuilt tdebase with -DBUILD_TSAK=OFF. The message then disappeared from my xsession logs. Culprit found but next needed a coding solution.

In tdebase/tdmlib/tdmtsak.cpp there are two calls to tdmctl. Seems this message could be handled more gracefully to avoid the mysterious xsession messages. Patching "2>/dev/null" in the source code and rebuilding without -DBUILD_TSAK=OFF again eliminated the messages.

But is that what we want? I don't know the specific purpose for the error message. Possibly the message is useful, but seems a more graceful approach is to test whether TDM is running before trying to execute the tdmctl command.

I presume tsak remains useful when a session is started from the command line for when a user locks the session. If so then again, there should be a test before each call whether TDM is running.

The error does not appear when TDM is running. I think a simple TDM trap test is all that is needed.

Should tsak be running when TDM is not?

==========
Bug No. 2:
==========

Both calls to tdmctl in tdmtsak use the format "tdmctl list" yet there is no "list" option in tdmctl --help. What is the "list" parameter supposed to do?

==========
Bug No. 3:
==========

When I built tdebase without tsak support (-DBUILD_TSAK=OFF), and in my tdmrc I have UseSAK=false, TDM starts with the dialog to press Ctrl-Alt-Del. That should not happen.
Comment 1 Darrell 2012-03-01 20:04:52 CST 
*** Bug 648 has been marked as a duplicate of this bug. ***
Comment 2 Darrell 2012-03-24 15:45:31 CDT 
The following likely all are related:

884 tdmctl: Cannot connect socket '/var/run/xdmctl/dmctl-:0/socket'
898 tsak process taking 90-100% of CPU
906 SAK realization is mostly buggy for KDM
925 [kdesktop] SAK driven secure dialog is not available for use
Comment 3 Darrell 2014-03-07 19:22:34 CST 
Bug No.1 still exists (read the summary).

Start X/TDE from the command line and the message appears in the xsession-error log. Start X/TDE with TDM (or KDM) and the message does not appear.

The message is from tdebase/tdm/kfrontend/tdmctl.c:48.

The message should not appear when starting X/TDE from the command line because TDM --- no login manager --- is running.