@sdetweil Hi
Yes I see that as well in bullseye, that is what I mean with ‘screen configuration app’.
If I rotate it in that (to left), the monitor just goes black?
@BKeyport it’s there in bullseye, but not previous versions.

I have a RPi 3B+ with Buster on it, and it works ok, though I can’t have screencast and remote installed at the same time. So I wanted to make a new install, and I downloaded the RaspberryOS Bullseye 32bit.
With that I can run the two modules together, but now I can’t rotate the screen to portrait.
The old version was just a question of adding display_hdmi_rotate=1 to the /boot/config.txt, but this doesn’t work with bullseye.
So how do I rotate the screen on the Bullseye?
I tried doing it from inside ‘X’ by using the Screen Configuration app, but when I do that (rotation=left), the screen goes black, and nothing happens, I can’t press the ‘verify’ button, so if I reboot it, it is still in landscape mode.
What can I do?

@sdetweil Hi there, yes I did, and I ran it again, and then it worked.
But thanks for the hint!

I was on 2.18, and got a notification that there was a new version, and today I finally tried to update it, and now I see this message in the logfile
0|MagicMirror | sh: 1: ./node_modules/.bin/electron: not found

The software is installed with @sdetweil 's script originally.

What to do?

@sdetweil Ok, good to know, so at least it’s not them making problems for MMM-ScreenCast and MMM-RemoteControl.

So I did a new install completely from scratch on a Raspbian Buster, and did a ‘manual’ install this time, still same error:

[25.02.2022 16:00.46.615] [LOG] Launching application.
[1789:0225/160048.427469:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[1828:0225/160048.917933:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

Monitor is in portrait mode, these settings are in boot/config.txt

display_rotate=1
enable_uart=1
avoid_warnings=1

Hi Guys

I’m having some problems with the installation.
I’ve done a brand new Raspbian Buster install.
Fully updated.
I then ran @sdetweil 's install script.

I’m now modifying the module config one by one, and installing the custom modules.

I’ve yet to install a custom module, so far I have changed the software to da-DK, I’ve made the compliments module fetch my gist compliments file, and I’ve changed the calendar module to use a danish provider.

I already see these two messages:

0|MagicMirror  | [3635:0225/103036.868905:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
0|MagicMirror  | [3680:0225/103037.331723:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.

@fribse I just did another video for valentines :-)

@lhops Try to log your temperature, the reboot sounds like a temp issue.
It would also suit the PiR that registers a rising temperature.

I live in CEST timezone, and I fear that is part of the problem.
I have a config like this for the module:

{
                        module: "MMM-MyCommute",
                        position: "bottom_right",
                        classes: "xsmall",
                        header: "Trafik",
                        config: {
                                apiKey: "xxx",
                                startTime: "05:00",
                                endTime: "12:00",
                                hideDays: [0,6],
                                origin: "Home",
                                destinations: [
                                        {
                                                destination: "Address1",
                                                label: "Company1",
                                                mode: "driving",
                                                color: "#82E5AA"
                                        },
                                        {
                                                destination: "Address2",
                                                label: "Company2",
                                                mode: "driving",
                                                color: "#82E5AA"
                                        }
                                ]
                        }
                },

My hope was that it would be active between 5 in the morning and midday, and not show up in weekends.
But this morning (tuesday) it diedn’t show up at around 8.

Has anybody else gotten this to work, and is there a trick to it?