Page 1 of 1
I can't start Porteus KDE 5.0rc2 in X [SOLVED]
Posted: 10 May 2021, 19:59
by wread
Hi all!
To correct some minor bugs, I tried to run Porteus in X.
Started Porteus in text mode, Ok.
logged in as root, Ok
entered "xinit", but got no X screen...
entered "ctrl-alt-backspace" and got back to text mode with the error messages that some needed fonts were not present, so X aborted!
Please try to duplicate that test..
Where are the missing fonts? I guess they will be introduced later when you start the target desktop, in my case KDE.
In my opinion, this should be corrected, I don't know if that happens with other desktops. I leave that question to the devel team!
The devel team has made a wonderful work and with a little hacking we will make it almost perfect!
EDIT:
entered "xinit", but got no X screen...
FALSE!...Only the background of the terminal is black.
Now you can click whithin the area of the terminal to activate it and give any X command...
Saludos cordiales!
I can't start Porteus KDE 5.0rc2 in X
Posted: 11 May 2021, 08:44
by burdi01
Use "startx" instead of "xinit".
The font messages are "normal" and harmless.
I can't start Porteus KDE 5.0rc2 in X
Posted: 11 May 2021, 20:20
by wread
@burdi01
Negative on that!
I need to start the X server and for that you need to call "xinit".
If you call "startx" you call the KDE desktop (in my case) direct!
Of course, the font messages are normal, they say the truth, and are harmless for the KDE-Desktop, but are a bug for the X-server!
Thanks!
I can't start Porteus KDE 5.0rc2 in X
Posted: 12 May 2021, 19:04
by beny
hi wread try in another terminal at boot time,but your xinit is like this?
Code: Select all
#!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $
userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi
if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi
if [ -f $userresources ]; then
xrdb -merge $userresources
fi
if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi
# Start the window manager:
if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
ck-launch-session dbus-launch --sh-syntax --exit-with-session startplasma-x11
else
dbus-launch --sh-syntax --exit-with-session startplasma-x11
fi
is unclear where you have to work on......
I can't start Porteus KDE 5.0rc2 in X
Posted: 19 May 2021, 12:03
by burdi01
If you call "startx" you call the KDE desktop (in my case) direct!
To me that *is* "running Porteus in X", so you must mean something else. Please elaborate.
"startx" invokes /etc/X11/xinit/xinitrc, which in Porteus KDE 5.0rc2 is a symlink to xinitrc.plasma -- do an "ls -l /etc/X11/xinit/ to confirm.
"xinit" starts a giant xterm, which most of the times is unusable.
However "xinit /etc/X11/xinit/xinitrc.openbox" starts an almost normal openbox session -- rightclick to see the menu.
I hope this helps.
Edit May 20, 2021: Corrected the above paths.
I can't start Porteus KDE 5.0rc2 in X
Posted: 19 May 2021, 19:16
by wread
@burdi01
Sorry, but in my system, when I type "xinitrc /etc/xinit/xinitrc.openbox" the answer is "command not found"
I can't start Porteus KDE 5.0rc2 in X
Posted: 20 May 2021, 10:14
by burdi01
Aarch! That should have been /etc/
X11/xinit/xinitrc.openbox ...
I can't start Porteus KDE 5.0rc2 in X
Posted: 20 May 2021, 10:54
by ncmprhnsbl
burdi01 wrote: ↑20 May 2021, 10:14
Aarch! That should have been /etc/X11/xinit/xinitrc.openbox
and i think xinit not xinitrc .. ie.
Code: Select all
xinit /etc/X11/xinit/xinitrc.openbox
though, i don't quite get what wread means by "the X server"
... are you maybe talking about
twm ? which is xorg's own window manager .. if so, you'd need to install it first:
$ getpkg twm
or if it is indeed the "giant xterm" .. there is/was some messages(generated by xterm) about missing fonts, but i don't think they were ever fatal..
I can't start Porteus KDE 5.0rc2 in X
Posted: 20 May 2021, 13:47
by burdi01
xinit /etc/X11/xinit/xinitrc.openbox
Yes, that is what it should have been.
I do not know what made me mess up things several times in a row.
Normally I do not make that kind of errors -- I hope.
And indeed wread did not elaborate as requested on what he wants to accomplish.