I’ve just found that the command to make noseguy appear is

/usr/libexec/xscreensaver/noseguy

So, any idea of any module to launch this command and integrates in MM?

@sdetweil

The thing is that noseguy is not a gif, it’s a screensaver from xscreensaver. Maybe it’s not possible to run another program over MM. I don’t know

Hello!

I would like to make a proposal for a possible module (if possible, of course). The idea is to show “noseguy” in the MM, or in a window inside MM.

noseguy is a screensaver included in the xscreensaver package, where it can be configured for example with the fortune package to randomly display a “fortune biscuit”, a famous phrase, etc. Those of you who have been using gnu-linux for a few years will surely know what I’m talking about.

I leave here a video of this screensaver, the audio is added in the video, the screensaver has no audio.

https://www.youtube.com/watch?v=ONJlg9Y_TLI

I think it would be an interesting module and I don’t think it would consume too many resources to, for example, run it on a MM with raspberry pi. Also, as you can see, the background is black ;)

I look forward to your opinions about it.

Regards,
Quique.

Translated with www.DeepL.com/Translator (free version)

@Cliff365

Hi, today I have an update on MMM-Wallpaper module too. I updated it using git pull && npm install. A few hours later, I had another update, so I repeated the process. I think it’s not an error. I think it’s the module developer that is making some changes to the code.

Try to check if the response on the terminal is always the same when updating or if they are different. In the case I just told you about, the updates were different.

Well, I think I can tag this post with SOLVED, all day with MMM-RAIN-MAP module disabled and no more black screens.

Thanks all for your advice.

@sdetweil

It is possible that in the end the problem was with the resource-intensive MMM-RAIN-MAP module. Now it’s disabled, let’s see what happens…

In the end, my method is as simple as trial-and-error until it’s solved.

I’m starting to see my problem…

Fortunately I had saved an old config.js file with less modules than the one I have now. In studying the differences, I find this in my current config.js file:

Too many calls to the newsfeed module, surely that’s the reason for the error.

This is the configuration in the MMM-Pages module that was giving me problems

{
module: 'MMM-pages',
     config: {
          modules:
               [[ "calendar_monthly", "MMM-Tools", "MMM-OpenWeatherForecast", "newsfeed"],
               [ "calendar", "MMM-AirQuality"],
               [ "MMM-TelegramBot", "MMM-EyeCandy"],
               [ "calendar_monthly", "MMM-Tools", "MMM-OpenWeatherForecast", "newsfeed"],
               [ "MMM-SolarPicture", "MMM-Lunartic", "MMM-Comics"],
               [ "MMM-Comics" ],
               [ "MMM-RAIN-MAP" ],
               [ "calendar_monthly", "MMM-Tools", "MMM-OpenWeatherForecast", "newsfeed"],
               [ "MMM-RandomPhoto", "MMM-History"],
               [ "MMM-WeatherChart"],
               [ "MMM-AirQuality", "newsfeed"],
               [ "MMM-Wallpaper"]],
rotationTime: 30000,
fixed: ["alert", "updatenotification", "clock", "MMM-OpenmapWeather", "MMM-page-indicator"]
}
},

@MMRIZE

The thing is, now that I remember, during the weekend I disabled completely newsfeed module, and the error does not disappeared. Now I’ll try disabling more modules.

@MMRIZE

Maybe, I’ll try disabling some modules. Thanks. i will tell u when I try it.

@MMRIZE

I don’t know, I have now 14 url of rss feeds, But I’ve tried with less of them and the error does not disappear.