Found this information, please see my comments each below:

1. Armitage does not display hosts from the database

Type hosts in the Metasploit Framework console. If you see hosts there, but not in Armitage, you have this issue. There are three possible causes:

The first (possible) cause is you are using the Metasploit Framework's workspaces (the workspace command). Armitage is not compatible with the Metasploit Framework's concept of workspaces. You must leave this at default and not change it.

This is, what I did!

The second potential cause is that Armitage is not using the same database configuration as the Metasploit Framework. This is driven by the database.yml file in your Metasploit Framework environment. Type db_status in a Metasploit Framework console and verify that this is the same database Armitage uses (go to Armitage -> Preferences and find the connect.db_connect.string value).

I found:

msf> db_status
[*] postgresql connected to msf3

and in preferences

db_connect string msf:"gtkw7HajGCR2jxn4PAc15h6Sy4GQlQdhFVdDfjmPn4w="@localhost:5432/msf

However, I changed this to "msf3", but at next start, the above string appeared again.

The third potential cause is that Metasploit made two default workspaces for you. Why? I don't know. This messes up things with Armitage though. Type workspace. If you see two workspaces with the name default, then this bit you. To fix it, type: workspace -D and restart Armitage.

Checked it, but I only saw one default.

msf > workspace

• default

I hope this helps!

Best

Hans

Discovered the following:

With kali-livefile + LXDE armitage does not show icons.
With kali-livefile + XFCE armitage does show icons (just by chance???)

I also reinitialized the database (msfdb reinit) = no success
and then deleteted and created a new one (msfdb delete && msfdb create && msfdb start) = no success

Trying more, if I know more, I will send.

Hans

Fixed it by myself.

Removed and purged armitage, then reinstalled.
After this did also "aptitude purge ~c"to get rid of old configurations. Looks like it is working again, but found not the cause for the issue. That is sad, caus I have nothing learnt at.

However, bug can be closed for now.