Moonshot UI does not load on a fresh CentOS 6 box

[Stefan Paetow]

Install CentOS 6.9. Configure as usual. Configure as a usual client.

Open Terminal. Run 'moonshot'. All you get is this:

Error loading icon 'avatar-default': Icon 'avatar-default' not present in theme
Error loading icon 'avatar-default': Icon 'avatar-default' not present in theme
_

(underscore above is the cursor)

It just hangs, does nothing. Launching from the Gnome menu does nothing either. It shows a process called 'moonshot', but no window appears.

Downgrading to 0.7.2-2 fixes the problem in that the window appears. On the Terminal command-line it still shows the above two messages plus this line:

Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Please resolve this ASAP.

[Dan Breslau (dbreslau)]

I have reproduced the issue on Centos 6. Am looking into the cause now.

[Dan Breslau (dbreslau)]

We just released Moonshot UI 1.0.6 for Centos 6 on repository.project-moonshot.org. This addresses three issues that were found during testing for this issue:

1) The main UI window doesn't appear: The 1.0.5 RPM for the UI was built on moonbuildcentos.dev.ja.net, which is still running Centos 6.3. I built 1.0.6 on a VM running Centos 6.9; this version of the moonshot UI does not show the same issue. Please confirm (as I believe I've heard previously) that we do not need to support versions of Centos 6 older than 6.9, because if we do, we may need a lengthier build/test/release cycle.

2) I also found that on 6.9, the UI crashed when trying to add an ID. This was due to a compiler error in an old version of valac (0.10.4). I've modified the code in question to work around the issue.

3) The message "Error loading icon 'avatar-default': Icon 'avatar-default' not present in theme" happens when we try to load the person/avatar icon that's shown in each entry in the ID selector main window. We no longer attempt to load it on Centos 6. This should not result in any loss of functionality.

None of these issues would be expected to appear on other platforms (Centos 7 or Debian.)

[Adam Bishop (adam-omega)]

We only support the latest point release.

[Stefan Paetow (stefan-paetow)]

Well, the system on which this occurred was *not* an old version of CentOS... it was 6.9, freshly installed off their latest DVD and all updated to the latest packages (plus our latest packages). Will have to retry the packages tomorrow and if necessary, update the VirtualBox image in question, if 1.0.6 resolves the problem.