issue after login

[theokeist]

Hi I'm having this issue after successful build on fedora 39, is there way to access terminal or something else? Graphic login is working

[MagnetarRocket]

Is the screen actually upside-down like that?

[theokeist]

No 😂 just wrong photo, mistake. it's correct now

[trunkmaster]

First of all, try to install binary release - you may have built from sources during my active development (sometimes it's buggy and it's normal).

If you have enough Linux skills you may try: load into single user mode, connect to this OS with SSH and inspect contents of /tmp/GNUstep<your user ID>/console.log and send its contents here.

Some psossible reasons of failing start of Workspace are:

• dynamic linker can't find libraries
• SELinux is enabled
• your user home incorrectly set up.

Anyway, I think I have to add console.log inspection right into panel from your screenshot.

BTW, may issue #437 be closed?

[mbert]

The following has worked for me to run a NEXTSpace session from an ordinary display manager like gdm: /usr/share/xsessions/NEXTSpace.desktop:

[Desktop Entry]
Name=NEXTSpace
Comment=Run a NEXTSpace Session
Exec=/usr/local/bin/NEXTSpace.sh
TryExec=/usr/local/bin/NEXTSpace.sh
DesktopNames=NEXTSpace
X-GDM-SessionRegisters=true

/usr/local/bin/NEXTSpace.sh:

#!/bin/sh

gnustep-services start
exec /usr/NextSpace/Apps/Workspace.app/Workspace "$@"

[MagnetarRocket]

@mbert , i'm running Nextspace on a virtual machine on a M1 mac (in UTM), i've tried and it still does not work.

[pcardona34]

Hi Sergii,

I just achieved to install NextSpace from sources on debian 12 yesterday : My context:

debian version: 12.8 ; uname -a: Linux pi400 6.6.62+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1 (2024-11-25) aarch64 GNU/Linux) .

I only tweaked some dependencies like these in debian-12.deps.sh :

Orginal	Mine
libjpeg8	libjpg-tools
libtiff5	libtiff-tools
libicu70	libicu72

And then, everything was made and installed in the order You defined.

At the first time, I had to adjust screen resolution in Preferences.app. After that, bad resolution was persistant only for Login.app, and after Login, things seemed to work well in the Workspace. I could mount a usb key, change parameters inside Preferences.app to get a french profile user... until today: I am now facing the same error session login panel like the above:

"Login - Session finished with error"

And there is no way to launch the Workspace again, even with "quit" or "restart".

Sometimes, I can see some error messages inside the log panel at the bottom of the alert box itself, like these after "... Workspace initialized ! ===":

• "malloc(): unaligned tcache chunk detected"
• "free(): double free detected in tcache 2"
• "double free or corruption (fasttop)"

With thanks for the great work You already did. Patrick

[pcardona34]

P.S.: Finally, I removed Login.app : so I got again access to the Workspace (xdm alternative). I hope we could one day use again Login.app.

[theokeist]

How exactly did you removed it? Just app remove after install? I wanna try it as well 👍

[pcardona34]

Hi Theokeist,

The exact word should be: 'I disabled...'

These are the steps I tried, according to my bash history.

Because raspi-config ignore Login.app as a potential session manager, I needed to install xdm to enable a desktop (xorg and WM) session first...

Inheriting the default .xinitrc

cp .xinitrc .xsession

Installing xdm the first time

sudo apt install xdm 
sudo raspi-config

There: choose to load desktop with login required, etc.

sudo reboot

How Login.app has been enabled then and started

• First disable and stop xdm:

    sudo systemctl disable xdm.service
    sudo systemctl stop xdm.service
  

• Then, to enable Login.app:

    sudo systemctl enable /usr/NextSpace/Apps/Login.app/Resources/loginwindow.service
    sudo systemctl start loginwindow
    reboot
  

How to switch to xdm session manager again:

• Disable Login.app as a service:

    sudo systemctl disable loginwindow.service
    sudo systemctl stop loginwindow.service
  

• Then enable xdm as a session manager service :

    sudo systemctl enable xdm.service
    sudo sytemctl start xdm.service
    sudo reboot
  

Now xdm launches the Workspace session.

N.B.: Because it is not a whole Netstspace session, when logging out, of course the shutdown button does not the job anymore: so You must open a console and exec:

sudo halt

[trunkmaster]

Hi Sergii,

I just achieved to install NextSpace from sources on debian 12 yesterday : My context:

debian version: 12.8 ; uname -a: Linux pi400 6.6.62+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1 (2024-11-25) aarch64 GNU/Linux) .

I only tweaked some dependencies like these in debian-12.deps.sh : Orginal Mine libjpeg8 libjpg-tools libtiff5 libtiff-tools libicu70 libicu72

My development environment is Fedora now. Debian is not my primary target OS so you may create a PR for this changes.

And then, everything was made and installed in the order You defined.

At the first time, I had to adjust screen resolution in Preferences.app. After that, bad resolution was persistant only for Login.app, and after Login, things seemed to work well in the Workspace. I could mount a usb key, change parameters inside Preferences.app to get a french profile user... until today: I am now facing the same error session login panel like the above:

"Login - Session finished with error"

And there is no way to launch the Workspace again, even with "quit" or "restart".

Sometimes, I can see some error messages inside the log panel at the bottom of the alert box itself, like these after "... Workspace initialized ! ===":

• "malloc(): unaligned tcache chunk detected"
• "free(): double free detected in tcache 2"
• "double free or corruption (fasttop)"

It's Workspace crash for some reason. Xorg XrandR extension sometimes behaves strange. That need to be investigated more. Also it might be some ARM-specific bug. Too little info. Also I've noticed some problems running Xorg if wayland DE were previously installed (like GNOME).

With thanks for the great work You already did. Patrick

[trunkmaster]

@theokeist I guess the original problems should be fixed in other issues. Is this issue still relevant?

[trunkmaster]

This issue has resolved during #451 discussion. Closing this.