Install MM on Debian 12

[sdetweil]

@DarrenO-0

pm2 is having trouble on debian 12. I opened an issue on pm2 and wayland a few weeks ago
https://github.com/Unitech/pm2/issues/5820
its the same error

0|MagicMirror  | Authorization required, but no authorization protocol specified
0|MagicMirror  | [13888:0625/223821.984899:ERROR:ozone_platform_x11.cc(244)] Missing X server or $DISPLAY
0|MagicMirror  | [13888:0625/223821.984944:ERROR:env.cc(257)] The platform failed to initialize.  Exiting.
PM2            | App [MagicMirror:0] exited with code [1] via signal [SIGINT]

pm2 stop all
cd ~/MagicMirror
npm start

works fine (running in my vmware as a vm)

[DarrenO 0]

@sdetweil LOL. Thanks
I’ll wait to hear back what you find out.

I figured there’d have to be some sort of Desktop environment for it to work on a physical machine.
Just didn’t/don’t know if I had to use of the various Desktop flavors available during the OS installation or if I could just use the base Debian environment.

[DarrenO 0]

@sdetweil yeah, that was the error I was seeing in the pm2 logs as well

Perhaps, I’ll have to go back to Debian 11 for the time being.

[sdetweil]

@DarrenO-0 there might be some way to switch back to x11. I know raspi bookworm provides that

[DarrenO 0]

@sdetweil
Just trying Debian12 again and ran your script.
It failed during the node and npm installation stage…

installing correct version of node and npm, please wait
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)
xz: (stdin): Unexpected end of input
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

Error: failed to download archive for 20.8.0

node failed to install, exiting

Going back to Debian11 now to see if I can get things back up and running.

[sdetweil]

@DarrenO-0 that is a networking error.

[DarrenO 0]

@sdetweil retried 3x and same result.
I was SSH’d into the device at the time and it had internet access at all times

[sdetweil]

@DarrenO-0 I just execute the curl command. I have no control over its networking code.

every time it’s failed due to networking there has been a real problem somewhere