MXFB Raspberry Final

[Jerry3904]

I already responded to this complaint that you put on the Blog post, but I'll repeat it here.

Patching is not necessary, it's only for people who already downloaded the B2: as indicated by the label "B2-Final" and stated explicitly in the file "How to use the patch." They can download the "Final" image instead, which is as Final as it's going to get for a while.

I have seen those video reviews and we have already been in touch now a couple of weeks ago, but thanks.

[Senpai]

Hi:
I have MX-Fluxbox on the raspberrypi 3B, I have installed Kodi 18.7, but to make Kodi run smoother from "raspi-config" it is set to boot on my user in "console mode".
Before I had Raspbian configured like this, and from the console mode I would run "Kodi" or "startx" to start in PC mode...
That doesn't work for me in MX-fluxbox. What would be the command to start Fluxbox from console mode?

Best regards from Senpai

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

[Jerry3904]

Try this:

Code: Select all

startfluxbox

[Senpai]

Try this:

Code: Select all

startfluxbox

With "startfluxbox" I get these errors:

Code: Select all

user@raspberrypi:~ $ startfluxbox
/home/user/.fluxbox/startup: 23: /home/user/.fluxbox/startup: xdg-user-dirs-gtk-update: not found
error, can't open display.: Success
tint2: could not open display!
Unable to init server: Could not connect: Connection refused

(polkit-gnome-authentication-agent-1:2268): Gtk-WARNING **: 11:26:55.906: cannot open display: 
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Unrecognized option '--AE'.
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
wmalauncher ver. 2020.0124 - (c) 2018-2020, Sébastien Ballet <slacker6896@gmail.com> -

Failed to open display ''
rm: no se puede borrar '/home/user/.config/pulse': File or directory does not exist
E: [pulseaudio] main.c: Could not stop daemon: Process does not exist
Unable to init server: Could not connect: Connection refused

(nm-applet:2307): Gtk-WARNING **: 11:26:58.296: cannot open display: 
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused

(blueman-applet:2308): Gtk-CRITICAL **: 11:26:58.811: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed

(blueman-applet:2308): Gtk-CRITICAL **: 11:26:58.839: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Traceback (most recent call last):
  File "/usr/bin/blueman-applet", line 121, in <module>
    BluemanApplet()
  File "/usr/bin/blueman-applet", line 52, in __init__
    setup_icon_path()
  File "/usr/lib/python3/dist-packages/blueman/Functions.py", line 178, in setup_icon_path
    ic.prepend_search_path(ICON_PATH)
AttributeError: 'NoneType' object has no attribute 'prepend_search_path'
/home/user/.fluxbox/startup: 73: /home/user/.fluxbox/startup: bluez: not found
/home/user/.fluxbox/startup: 82: /home/user/.fluxbox/startup: /usr/lib/at-spi2-core/at-spi-bus-launcher: not found
/home/user/.fluxbox/startup: 76: /home/user/.fluxbox/startup: xfce4-power-manager: not found
feh ERROR: Can't open X display. It *is* running, yeah?
Unable to init server: Could not connect: Connection refused
Cannot open display: 
Unable to init server: Could not connect: Connection refused

(clipit:2315): Gtk-WARNING **: 11:27:00.326: cannot open display: 
Error: Couldn't connect to XServer passing null display

I tried also with "startx fluxbox" and it gives this error:

Error startx fluxbox.png

[Senpai]

Try this:

Code: Select all

startfluxbox

Hi:
Thanks for the idea, I found the rest of the solution here, https://wiki.debian.org/es/FluxBox#Sesi.2BAPM-n_Fluxbox
I was missing to create the ".xinitrc" file in the home directory,

Code: Select all

nano .xinitrc

and insert the following line to it:

Code: Select all

exec startfluxbox

, after that with "startx" starts the Fluxbox session without problems.

Greetings from Senpai

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

[SmithTech]

How can I install XFCE and make it look like the install on my laptop?

Thanks

[chrispop99]

There is no way of doing this easily from MXFB Raspberry Pi.

There are other distribution available that have an Xfce version for the Raspberry Pi.

Chris

[HackerKitty]

I finally got my hands on Raspberrypi 4 and installed MX par advice given by Jerry back in January.

I had to settle for 4GB version as the 8GB version was out of stock
But even with 4GB, MX runs impressively fast and whole installation procedure went very sooth.
I also noticed Pi generates less heat than the official 32bit PasPiOS which I tested before installing MX.

Thanks again for the great work!

[chrispop99]

I finally got my hands on Raspberrypi 4 and installed MX par advice given by Jerry back in January.

I had to settle for 4GB version as the 8GB version was out of stock
But even with 4GB, MX runs impressively fast and whole installation procedure went very sooth.
I also noticed Pi generates less heat than the official 32bit PasPiOS which I tested before installing MX.

Thanks again for the great work!

I noticed the heat reduction also.

The Pi 4 needs some cooling help if you ever over-clock it, or build it into a case. There are good passive cooling solutions; you don't need a fan.

Chris

[HackerKitty]

[/quote]

I noticed the heat reduction also.

The Pi 4 needs some cooling help if you ever over-clock it, or build it into a case. There are good passive cooling solutions; you don't need a fan.

Chris
[/quote]

Hello Chris,

Thanks for confirming my observation :)

I am using this Pi as a local WordPress server.
I installed a fan SHIM from Pimeroni which is set to kick in at 65 C.
But Pi's temperature never exceeds 60 C.
Well, so much for my temperature controlling Python script...