Hello,
I am sourcing GNUstep within .profile and I have experienced good
stability and no more crashing adding some 'sleep' delays like this in
my '.xinitrc':
#!/bin/sh
# $HOME/.xinitrc
### Start Xserver & Window Manager in a DBus session:
PID_XSESSION=$$
/usr/lib/policykit-1/polkit-agent-helper-1 &
wmaker --no-dock --no-clip --static &
notify-send "PiSi Desktop is loading..."
sleep 1
openapp SimpleAgenda &
sleep 2
exec dbus-launch --sh-syntax --exit-with-session openapp GWorkspace
kill $PID_XSESSION
############ INFO ###############################################
### DMPS and blanking issues on RPI machine
### are fixed (xset) within
### $HOME/.config/openbox/autostart
### Not here!
#################################################################
### Setting GNUstep environment
### This is done with .profile, not here.
#################################################################
And I launch some other things with Window Maker
'GNUstep/Library/WindowMaker/autostart':
#!/bin/bash
#
# Place applications to be executed when WindowMaker is started here.
# This should only be used for non-X applications or applications that
# do not support session management. Other applications should be
restarted
# by the WindowMaker session restoring mechanism. For that, you should
# either set SaveSessionOnExit=YES or select "Save Session" in the
Workspace
# submenu of the root menu when all applications you want started are
# running.
#
# WindowMaker will wait until this script finishes, so if you run any
# commands that take long to execute (like a xterm), put a ``&'' in the
# end of the command line.
#
# This file must be executable.
#
xset m 20/10 4
### This is to prevent DMPS and blanking issues on RPI machine
xset -dpms
xset s off
# gdnc
gdomap -L GDNCServer || gdnc &
# compton
pgrep compton || compton -b
# TopBar: removed
#pgrep TopBar || openapp TopBar &
### Notifications
systemctl --user import-environment DISPLAY &
pgrep dunst || dunst &
# conky
pgrep conky || sleep 10 && conky -c ~/.config/pisi/conky.conf &
### Updater notification
sleep 30 && ~/.local/bin/Updater.sh -d &
## End of autostart
Hope it could help.
On 2025-08-19 21:48:14 +0200 Riccardo Mottola
<[email protected]> wrote:
Hi,
Nathan Koch wrote:
##GNUStep
. /usr/local/share/GNUstep/Makefiles/GNUstep.sh &
gdnc &
gpbs &
make_services
##
Still to no avail. Was wondering the proper way of starting it
You only need to source the script:
. /usr/local/share/GNUstep/Makefiles/GNUstep.sh
(no ampersand is needed, the script will terminate and you need it
execution
before other things start)
gdnc and gpbs do not need to be started manually since a long time
anymore.
You can do it though, no harm and speeds you the first app start.
make_services is also not strictly needed. You need to execute it
only after
an application is installed so that the database of types is updated.
If you
install GS apps through packages and they are done conveniently, it
will done
during the install script (I am not sure OpenBSDs one are done that
way).
then you can start any gnustep app from terminal.
GNUstep does not provide a windowmanager, you probably want
WindowMaker.
If you do this in your xinitrc, as Lars suggests:
. /usr/local/share/GNUstep/Makefiles/GNUstep.sh
wmaker &
exec GWorkspace
GWorkspace will manage the session and exiting / logging our
GWorkspace will
work as expected, but you need GWorkspace
If you have an issue with with GWorkspace and need to restart it or
it
crashes, it will kill your session (*)
if you instead have:
. /usr/local/share/GNUstep/Makefiles/GNUstep.sh
exec wmaker
wmaker "drives" your session, so you can strictly speaking not run
GNUstep
apps yet, but any app you want, including GNUstep apps, from the
window maker
menu. You can also run GWorkspace that way. If an app needs
GWorkspace it
will also start for you.
Sum up:
First method is the "clean" way to have sort of full GNUstep
workspace,
GWorkspace+WindowMaker
The latter method is less pure, but more versatile and with two
clicks ens
with the same stuff open, but allows also e.g. just run X11 with an
xterm if
needed (e.g. on a low-spec machine or if you are on a hurry)
(*) certain people report in certain setups mysterious crashes or
abnormous
CPU usage after days or certain conditions, which cannot be
reproduced and so
debugged.
--
Patrick Cardona - Pi400 - GNU/Linux (Debian 12 aarch64: RPI OS Lite)
Xorg (1:1.7.1-1.2) - libcairo2 (1.16.0-7+rpt1 arm64)
Window Maker (0.96.0) - GWorkspace (1.1.0 - 02 2025) - Theme: PISI -
MUA: GNUMail (1.4.0)
