Antonis,
I always use dtlogin to start CDE and have no problems.
caveat: I'm running and older version of CDE.
Add this to the end your boot scripts, after rpcbind is started,
networking and DNS are up, etc.:
/usr/dt/bin/dtlogin -daemon
Then login graphically to CDE. When you exit CDE, it should prompt
you to save your session. The next time you login, it should restore
any clients you had open when you last exited. If you use dtlogin,
it starts Xsession for you.
To the best of my knowledge, startx is for running X outside of a
session manager. You login on a text console and just type 'startx'.
While it can take arguments, I've never had to give it any. See
startx(1) about the arguments. startx processes your ~/.xinitrc
if you want to start some clients automatically, and finally should
execute your preferred window manager.
If you want to use dtwm with the startx method, just change
/usr/X11R6/bin/mwm to /usr/dt/bin/dtwm in ~/.xinitrc, as below.
If doing this, do *not* start dtlogin (as above).
Example:
....................cut here....................
# $HOME/.xinitrc
# Commands in this file are run when you run 'startx'.
# startx runs xinit, which starts the X Windows System when you are
# not using a display manager, e.g. xdm(1).
#
# start some xclients
xclock &
xterm &
#
# exec window manager last and not in background
if [ -x /usr/X11R6/bin/mwm ]; then
exec /usr/X11R6/bin/mwm
else
exec /usr/X11R6/bin/twm
fi
....................cut here....................
Xsession, on the the hand, is used with a login manager like xdm(1).
To use xdm, you would start it at the end of your boot scripts:
exec /usr/X11R6/bin/xdm > /var/adm/xdm.log 2>&1 &
Then you should be presented with a graphical login. xdm will
process ~/.xsession and takes the place of .xinitrc used in the
startx method.
....................cut here....................
# $HOME/.xsession
# X session startup
# When logging into X via xdm, /usr/X11R6/lib64/X11/xdm/Xsession
# (global) is run, then this script is run.
# This is an executable shell script.
# All commands should be run in the background except the
# window manager which is started last.
#
# start some xclients
xclock &
xterm &
#
# Exec window manager last and not in the background
exec /usr/X11R6/bin/mwm > $HOME/xsession.log 2>&1
....................cut here....................
dtlogin works like xdm, only you start it with
/usr/dt/bin/dtlogin -daemon
instead of
/usr/X11/bin/xdm &
Choose one method: startx --OR-- xdm or dtlogin.
Do you have ~/.xinitrc and/or ~/.xsession files?
Try renaming or removing them.
Other places to check for errors:
* Xorg log, usually /var/log/Xorg.$DISPLAY.log
* Dtlogin.errorLogFile, usually /var/dt/Xerrors
On the hung/frozen process thing, try strace(1):
$ ps -ef | egrep 'X|Xsession|dtlogin|dtwm' ## depending on what is running
$ strace -p pid_of_process
When I'm logged into CDE using dtlogin, I have these processes running:
$ ps -ef | egrep 'X|Xsession|dtlogin|dtwm' | grep -v egrep
root 3775 1 0 Oct28 ? 00:00:00 /usr/dt/bin/dtlogin -daemon
root 3783 3775 0 Oct28 tty10 01:23:21 /usr/bin/X :0 -auth
/var/dt/authdir/authfiles/A:0-ZZAhRD
root 3971 3775 0 Oct28 ? 00:00:00 dtlogin <:0> -daemon
user1 4055 3971 0 Oct28 ? 00:00:00 /bin/ksh
/usr/dt/bin/Xsession
user1 4091 4075 0 Oct28 ? 00:02:11 dtwm
scot
Antonis Tsolomitis wrote:
Steps:
while in mate-desktop
rm -rf .dt/
rm -f .dtprofile
logout and login to CDE. Everything looks OK. It auto starts Help and
Filemanager
logout and login again. It starts the Filenamager but not the Help. Also the cde
bar does not display the name of the month now.
Everything is frozen.
Switched to console.
.dt/errorlog remains empty.
in .dt/sessionlogs/ there is only one entry called 'damo_DISPLAY=:0' (damo is
the name of the machine)
This file if cat says to enable logging in .dtprofile
pkill -9 Xsession
Enable loging in .dtprofile and login one more time. Same behavior. No Help,
everything frozen.
switch to console.
cat .dt/sessionlogs/damo_DISPLAY\=\:0
<stdin>:170:58: warning: missing terminating ' character
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 5571 requests (5565 known processed) with 0 events remaining.
X connection to :0.0 broken (explicit kill or server shutdown).
PipeRead: broken pipe, ppid=1 pid=2880598 fd=11
After the XIO is the fact I killed the Xsession. The previous line says
something:
if a terminating character is missing someplace the CDE waits for something to
complete.
But what is this <stdin>:170:58: ???
top shows nothing interesting. The system is idle. Most probably waiting for
something to terminate...
If there maybe something interesting in the sessions folder please advice.
ls -R .dt/sessions
sessions/:
current/ dtwmfp.session system/
sessions/current:
dtCT3zeg dt.resources dtsession.db dt.settings dtwm.db
sessions/system:
=================
startlog has also no error:
[atsol@damo .dt]$ cat startlog
--- Πεμ 03 Νοε 2022 04:43:35 μμ EET
--- /usr/dt/bin/Xsession starting...
--- Xsession started by startcdesession
--- setting font path...
--- sourcing /home/atsol/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0060.dtsysenv...
--- starting /usr/dt/bin/dthello -file /usr/dt/copyright &
--- starting /usr/dt/bin/dtsearchpath -ksh
--- starting /usr/dt/bin/dtappgather &
--- execing /usr/dt/bin/dtsession ...
not execing /home/atsol/.profile (see /home/atsol/.dtprofile)
Antonis.
On 2/11/22 22:13, Edmond Orignac wrote:
It is difficult to see what could be freezing your session the second time you
log in. I haven't seen this issue on Ubuntu with CDE 2.5.0. I have only a few
suggestions to try to detect the origin of the problem.
Have you examined the files created under .dt/sessions ? Is there something
started in sessionetc
that does not go in the background ? Are there some files under
.dt/sessionlogs/ ?
Can you switch consoles with ctrl+alt+Fn and run top on the machine ?
Alternatively, can you use a second PC to ssh in the machine and run top to
see if a program is using 100% of memory or CPU ?
You may then try to kill the program and see if the session starts correctly
or ends.
Le 31/10/2022 à 14:47, Antonis Tsolomitis a écrit :
I am trying to use the latest stable CDE on Manjaro. Compilation and
installation
goes through with no problem.
I remove old .dtprofile and old .dt/ from my home.
startx /usr/dt/bin/Xsession
All is well.
Logout and try again:
startx /usr/dt/bin/Xsession
CDE starts and freezes immediately
Same behavior from lightdm login manager or dtlogin manager. The first
attempt (without .dt/ and .dtprofile) works.
The second attempt (now we have .dt/ and .dtprofile) always freezes.
$HOME/.dt/errorlog remains empty.
$HOME/.dt/startlog shows no error:
$ cat startlog
--- Δευ 31 Οκτ 2022 03:36:42 μμ EET
--- /usr/dt/bin/Xsession starting...
--- Xsession started by xinit
--- setting font path...
--- sourcing /home/atsol/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0060.dtsysenv...
--- starting /usr/dt/bin/dthello -file /usr/dt/copyright &
--- starting /usr/dt/bin/dtsearchpath -ksh
--- starting /usr/dt/bin/dtappgather &
--- execing /usr/dt/bin/dtsession ...
not execing /home/atsol/.profile (see /home/atsol/.dtprofile)
Has anyone seen this behavior? How can I find what is wrong. It does the very
same thing
on two pcs with updated Manjaro Linux. It does exactly the same if I install
cdesktopenv-git
from AUR.
Antonis.
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
This body part will be downloaded on demand.
This body part will be downloaded on demand.
_______________________________________________
cdesktopenv-devel mailing list
cdesktopenv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
