trunkmaster
A documented way to start without login-manager?
As the title says it, is there a documented way to start without Login? I am running NextSpace from a virtualized Ubuntu sever 23 install running on a mac with the UTM virtual machine; and so far on that arch, login seems to just hang up.
As the title says it, is there a documented way to start without
Login? Yes, you may start it manually like this:
# Xorg :0 -noreset -background none -seat seat0 -nolisten tcp -keeptty vt1 &
$ gnustep-services start
$ export DISPLAY=:0.0
$ /usr/NextSpace/Apps/Workspace.app/Workspace
I am running NextSpace from a virtualized Ubuntu sever 23 install running on a mac with the UTM virtual machine; and so far on that arch, login seems to just hang up. What do you mean by "hang up"? Is cursor blinking? Does mouse cursor move? Can you enter something with keyboard? I guess you have missing some driver packages installed. Some time ago I've managed to build and start NEXTSPACE in UTM VM on MacBook Air M2 without a problem.
Starting with writing down what Ubuntu server does:
Ubuntu Server's X11 just crashes…
changing
seat0 to just 0 still does not solve the problem. I had a debian one, but had to restart my M1 MacBook air and lost what i've written down. Will try to recreate it for when i can.
Edit: Oh, another thing i found is that if you say yes to enabling login at system start in the installer, the next time the system boots: display doesn't work.
Starting with writing down what Ubuntu server does: Ubuntu Server's X11 just crashes…
It doesn't crash - it won't start due to your OS setup. Try run Xorg without options and check output.
changing
seat0to just0still does not solve the problem.
seat0 is not an option it's a parameter to option -seat. Check if you correctly specified options to Xorg.
I had a debian one, but had to restart my M1 MacBook air and lost what i've written down. Will try to recreate it for when i can.
Edit: Oh, another thing i found is that if you say yes to enabling login at system start in the installer, the next time the system boots: display doesn't work.
Probably you've some Xorg drivers installed. Check /var/log/Xorg.0.log for hints.
The debian one is the stock ARM image from https://mac.getutm.app/gallery/debian-12 and the nextstep image was the recent 0.95 release. Also, trying to start gnustep-services start in the debian-12 VM always results in the error of:
/usr/NextSpace/bin/gnustep-services: 19: gpbs: Exec format error
/usr/NextSpace/bin/gnustep-services: 17: gdnc: Exec format error
I've decided to try and make a .desktop file for nextspace myself, but having gnustep-services start give out errors might be a blocker for when it's a required step to starting nextspace.
Also decided to reinstall the Ubuntu VM with the recent LTS release.
Now problem becomes more clear - you're trying to run x86_64 binary code on ARM. You may try to build NextSpace from source, follow the steps described in README located in nextspace/Packaging/Sources.
Might also want to try and check the releases install script on Aarch64. Create new Arch dependent issue with release binaries and close this one?
On a unrelated note i created dock logo icons for Rasbian and Oracle Linux/Solaris. I can send those over if you want the two icons.
Building from source just only gave one error (I'd stringed tougher all the build scripts into one line, which i advise not to do so):
./7_build_libs_back.sh: 28: .: cannot open /Developer/Makefiles/GNUstep.sh: No such file
Apt has the needed file, but unsure of dependency clashes as it wants to use the vanilla GNUStep-common package too.
Building from source just only gave one error (I'd stringed tougher all the build scripts into one line, which i advise not to do so):
./7_build_libs_back.sh: 28: .: cannot open /Developer/Makefiles/GNUstep.sh: No such fileApt has the needed file, but unsure of dependency clashes as it wants to use the vanilla GNUStep-common package too.
NextSpace is self-contained - no dependencies on official GNUstep packages. GNUstep official packages have different directory hierarchy - remove them and run NextSpace build scripts one by one.
Might also want to try and check the releases install script on Aarch64. Create new Arch dependent issue with release binaries and close this one?
Sorry, I don't have ARM-based laptop. My workhorse is x86_64 based. I have occassional access to Air M2, but I can't rely on it.
On a unrelated note i created dock logo icons for Rasbian and Oracle Linux/Solaris. I can send those over if you want the two icons.
I may add those icons, but I have no ability to develop/test project on variety of OS/hardware. Do you want to be a volonteer?
Sorry, my personal life got in the way. & also the UTM machine i was using needs to be nuked & then replaced with a new virtual machine in its place.
Now have a new virtual machine, but trying to run 9_build_Applications.sh always gives a full blank screen with a blinking cursor. So far i have no way out of that blank screen with a blinking cursor that i know of…
Edit: also said machine does not have gnustep installed from the main repos.
Running 9_build_Applications.sh doesn't start anything - it only configures system. Did you mean running systemctl start loginwindow?
Looking at our past conversation and UTM I think you need to install appropriate graphics driver for Xorg. I don't have UTM now because I'm using VMware Fusion - it's free for non-commercial use. But I remember that setting correct graphics card in qemu (UTM is a graphical frontend to qemu) is not a trivial task.
Once you'll manage to start plain Xorg (just Xorg command without options) without errors you may get success on starting loginwindow service.
The bare-bones enviroment did work:
But then running 9_build_Applications.sh will always ruin systemd's delicate login manager prefrences somehow…
And thus i'm stuck with a external software terminal just to interact with shown VM, might as well go through 9_build_Applications.sh backwards and see how i can undo what that script did to my system…
At current state of source code loginwindow.service located at /usr/NextSpace/lib/systemd.
You don't need to copy loginwindow.service manually - it's copied by install routine of Login.app. To sum up: you may disable service with command sudo systemctl disable loginwindow.service and enable with command sudo systemctl enable /usr/NextSpace/lib/systemd/loginwindow.service.
After that you can reboot OS or start sevice manually with sudo systemctl start loginwindow.
Got 9_build_Applications.sh up and running, but i think a session manager has to be disabled in order to run it. The black screen was caused by a misselected virtual graphics option in UTM.
On the other hand…
And i'll close this.