KDE5: minimwatch can not create sys tray icon

[simoncn]

(22-01-2016 23:04)tarnkappe Wrote:  Which black/whitelisting properties do you mean? Is this an option in java somewhere or in KDE or X, etc?

I have reported the issue. Will see if someone reacts.

See this post and subsequent discussion on the same thread. It isn't exactly the same problem but it might be related.

[tarnkappe]

The mentioned solution is for the unity-desktop. I cannot find something similar for KDE/plasma. Also the problem is different, because the icon already appears, but only the context menu does not. I think, if I really need it, I have to log into a different desktop or window manager (like icewm or maybe unity or gnome3). In most cases I need it for rescanning the library. But this can also be done via bubbleupnp or the minimserver web gui. So I am not completely lost.

[simoncn]

(23-01-2016 12:37)tarnkappe Wrote:  The mentioned solution is for the unity-desktop. I cannot find something similar for KDE/plasma. Also the problem is different, because the icon already appears, but only the context menu does not. I think, if I really need it, I have to log into a different desktop or window manager (like icewm or maybe unity or gnome3). In most cases I need it for rescanning the library. But this can also be done via bubbleupnp or the minimserver web gui. So I am not completely lost.

The other workaround is to use the MinimWatch console interface. Please let me know if you get any response from the KDE guys.

[ReneZ]

With regards to the earlier referenced post; I'm in the same situation again (still using Ubuntu 12.04 LTS). I had it running OK for some time. but it changed again with the upgrade to Minimwatch 8.0.3 (? - latest - the one you had to install separately). Meantime it also doesn't work any more on my W10/64 machine, after the same upgrade. It now throws a Java exception, however its incomplete (can't see what the message is as it disappears too quick - something about "unsatisfiedlinkerror"). Haven't had time to look further. There was a recent upgrade to Java, don't know if that's the issue.

[simoncn]

(23-01-2016 20:21)ReneZ Wrote:  With regards to the earlier referenced post; I'm in the same situation again (still using Ubuntu 12.04 LTS). I had it running OK for some time. but it changed again with the upgrade to Minimwatch 8.0.3 (? - latest - the one you had to install separately). Meantime it also doesn't work any more on my W10/64 machine, after the same upgrade. It now throws a Java exception, however its incomplete (can't see what the message is as it disappears too quick - something about "unsatisfiedlinkerror"). Haven't had time to look further. There was a recent upgrade to Java, don't know if that's the issue.

You should be able to find the details of the exception by looking in the minimwatch.log file in the C:\Users\your-user-name\AppData\Roaming\MinimWatch\data folder. The AppData folder is hidden in Windows Explorer by default, so you need to type this full path into the Explorer address bar.

This problem is usually caused by using 64-bit MinimServer with 32-bit Java. See step 1 of this section for more information. This is often the result of applying a Java update using a 32-bit browser, which can replace the previously installed 64-bit Java with 32-bit Java.

[tarnkappe]

(23-01-2016 16:23)simoncn Wrote:  The other workaround is to use the MinimWatch console interface. Please let me know if you get any response from the KDE guys.

Ah, cool, I wasn't aware of the existence of the console interface.

This is my report for KDE:
https://bugs.kde.org/show_bug.cgi?id=358328

But I will give you a note if something new happens.