Problems with RPi3 + Jessie 2017-02-16

[simoncn]

I tried it with Stop/Exit/reboot and MinimServer started OK after the reboot. I will try the latest Raspbian to see if that makes a difference.

[simoncn]

I am seeing the same as you with the latest Raspbian. It looks like the way applications are started at boot has changed and this is the cause of the problem. I will post back here when I have more information.

[simoncn]

I have found a bug in the minimserver/bin/setup script that seems to be the cause of the problem. I am surprised that no-one has reported this previously. You should be able to work around the problem by setting automatic startup to enabled instead of disabled. I will release a fix in the next few days that allows you to set automatic startup to disabled. Thanks very much for letting me know about this.

[Adrianqq]

(07-03-2017 15:43)simoncn Wrote:  The installation instructions are in this section. If you follow these steps, you will be prompted for the content directory and you won't see the red icon.

You can do it the other way as well, as you have been doing. After getting the red icon, you should open Properties, enter the contentDir value, then click Restart from the minim icon. You are doing Stop/Exit/reboot and this might be related to the problem you are having. I will try this to see what happens.

Hi. Followed (and have been following prior to this) the installation instructions verbatim. Have tried Restart from the drop down box and Relaunch from properties once I've set the content directory. No dice. I've tried a brand new RPi3 - same problem. I've moved my music files from a USB drive to the micro SD card - doesn't help. Two things are puzzling me:
1: why no dialog box to request the content directory at first startup
2: why does the installed software work after setting content via the properties panel - I can start and close it down several times and it still works OK but as soon as I reboot or shutdown/power up it doesn't even start. No greyed out icon, no red box. When I configure the RPi3 I set the following:
Extend partition to use all of 8GB sd card
Boot to console with auto login
Force audio to HDMI
Set timezone, keyboard and wifi country to UK settings
are any of these settings liable to cause a problem for minimserver ?

[Adrianqq]

Sorry, missed your previous post 07/03/2017 19:26.
Please ignore my last post 09/03/2017 21:15.

[simoncn]

Does enabling automatic startup work around the problem for you?

[Adrianqq]

(09-03-2017 23:49)simoncn Wrote:  Does enabling automatic startup work around the problem for you?

Install minimserver, enable desktop, enable auto start - works after reboot.
But I have to go to desktop and stop then exit before rebooting otherwise I get a socket address already in use error. Also the uninstaller can't remove two .so files in minimserver/tmp/native folder.
I want to run the system headless and have a pushbutton to shutdown the RPi3. Commands such as minimserver/bin/stop and minimserver/bin/exit would be useful to add to the pushbutton shutdown script (would stopall work for the former ?).

[simoncn]

These problems are caused by a change to the way Raspbian is automatically logging in as the default user 'pi'. Because of this, MinimServer is being started with root privilege and this is causing the problems you are seeing. I am working on a fix.

[Adrianqq]

(10-03-2017 11:23)simoncn Wrote:  These problems are caused by a change to the way Raspbian is automatically logging in as the default user 'pi'. Because of this, MinimServer is being started with root privilege and this is causing the problems you are seeing. I am working on a fix.

Hi. Thanks. There may be another problem or it may be part and parcel of the same one.
With minimserver running with desktop and auto run enabled (green square) stop, exit, reboot, startx, gives red square-no content directory set. Going to properties shows the content directory is actually set. Clicking apply, OK, restart allows minimserver to start again.

[simoncn]

I'm not quite sure what you mean by startx.

What is your content directory? If it is on a mountable drive, the drive might not be mounted when MinimServer starts. You can set the delayStart property to fix this.