After I log in, I can view my desktop but I get an error message (see title) and abolsutely nothing will work, except the [ok] button to return to the login screen. When I start it via Xsession, same promlem - nothing works - cannot even logout because the logout button needs tooltalk!
If I try to start rpc.ttdserver (something I'd rather not do) I get " traps: rpc ttdbserver general protection ip error " and a segmentation fault.
It's probably a host issue, but my /etc/hosts is correct. From my research I found a lot of outdated security issues with tooltalk with solutions being to disable it. I would like to resolve this issue with or without tooltalk. I have read that it is possible to disable tooltalk
According to one site: "Most sites do not need to use the ToolTalk server daemon. Xi Graphics Security recommends that non-essential services never be enabled. To disable the ToolTalk server on your system, edit /etc/inetd.conf and comment out, or remove, the 'rpc.ttdbserver' line. Then, either restart inetd, or reboot your machine. " - http://www.securiteam.com/unixfocus/5DP0D0A7PQ.html
I do not have an inetd, so the instructions do not apply, but since every app seems to think it needs tooltalk (only whn ran from within CDE), I am not sure how this would work anyways - it gives hope there is (or was) a way.
I primarily want to be able to use the CDE desktop with or without tooltalk. However I can run all my CDE applications fine from any other desktop or window manager just now dtwm(?). This makes me think Tooltalk is unnecessary.
So either of two things are fine:
Getting into CDE with tooltalk working and being able to use it OR;
Disabling tooltalk, and ridding myself of something I am already despising (preferable)
Last edit: Trent Mo 2018-05-31
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You do not need rpc.ttdbserver - In fact, I would recommend not running that. You do however need tooltalk (ttsession). CDE is built around it.
You could try to see if rpcbind is running, and see if 'rpcinfo -p' gives you reasonable output. You could check ~/.dt/errorlog and ~/.dt/sessionlogs/* to see if anything useful was output there.
Failure to start tooltalk is almost always network related (or there is no rpcbind server running). Unfortunately I do not see this problem, so I cannot help much. Some fixes went into master yesterday, so you might also try updating to the latest and see if anything changed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As a sanity check, make sure that all the prereqs listed on the wiki got installed... I had a similar issue and it turned out that some of the prereq packages for Ubuntu 18.04 S LTS didn't get picked up when I used the one-liner from the wiki. I went and checked and installed each package manually and afterwards this issue went away. Before I would get the 'messenging service could not start' error each time and the logs were less than helpful. It turned out being something more simple than anticipated. Good luck.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You didn't mention your OS, but there is a change in master that may fix this problem. If you noticed ttsession eating up 100% of your CPU after failing, then this may be the same problem. It was seen on SUSE Tumbleweed and ArchLinux systems with TIRPC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After I log in, I can view my desktop but I get an error message (see title) and abolsutely nothing will work, except the [ok] button to return to the login screen. When I start it via Xsession, same promlem - nothing works - cannot even logout because the logout button needs tooltalk!
If I try to start rpc.ttdserver (something I'd rather not do) I get " traps: rpc ttdbserver general protection ip error " and a segmentation fault.
It's probably a host issue, but my /etc/hosts is correct. From my research I found a lot of outdated security issues with tooltalk with solutions being to disable it. I would like to resolve this issue with or without tooltalk. I have read that it is possible to disable tooltalk
According to one site: "Most sites do not need to use the ToolTalk server daemon. Xi Graphics Security recommends that non-essential services never be enabled. To disable the ToolTalk server on your system, edit /etc/inetd.conf and comment out, or remove, the 'rpc.ttdbserver' line. Then, either restart inetd, or reboot your machine. " - http://www.securiteam.com/unixfocus/5DP0D0A7PQ.html
I do not have an inetd, so the instructions do not apply, but since every app seems to think it needs tooltalk (only whn ran from within CDE), I am not sure how this would work anyways - it gives hope there is (or was) a way.
I primarily want to be able to use the CDE desktop with or without tooltalk. However I can run all my CDE applications fine from any other desktop or window manager just now dtwm(?). This makes me think Tooltalk is unnecessary.
So either of two things are fine:
Getting into CDE with tooltalk working and being able to use it OR;
Disabling tooltalk, and ridding myself of something I am already despising (preferable)
Last edit: Trent Mo 2018-05-31
You do not need rpc.ttdbserver - In fact, I would recommend not running that. You do however need tooltalk (ttsession). CDE is built around it.
You could try to see if rpcbind is running, and see if 'rpcinfo -p' gives you reasonable output. You could check ~/.dt/errorlog and ~/.dt/sessionlogs/* to see if anything useful was output there.
Failure to start tooltalk is almost always network related (or there is no rpcbind server running). Unfortunately I do not see this problem, so I cannot help much. Some fixes went into master yesterday, so you might also try updating to the latest and see if anything changed.
As a sanity check, make sure that all the prereqs listed on the wiki got installed... I had a similar issue and it turned out that some of the prereq packages for Ubuntu 18.04 S LTS didn't get picked up when I used the one-liner from the wiki. I went and checked and installed each package manually and afterwards this issue went away. Before I would get the 'messenging service could not start' error each time and the logs were less than helpful. It turned out being something more simple than anticipated. Good luck.
You didn't mention your OS, but there is a change in master that may fix this problem. If you noticed ttsession eating up 100% of your CPU after failing, then this may be the same problem. It was seen on SUSE Tumbleweed and ArchLinux systems with TIRPC.