openSUSE 42.2 - Ícone da bandeja não abre
 

Uso o cliente Spark, e por algum motivo, somente no openSUSE (KDE) tem esse problema, quando o Spark é fechado e minimizado na bandeja, o usuário não consegue abrir nem com 1 ou 2 cliques, o programa fica funcionando entretanto e recebendo PVT inclusive.

Utilizei o mesmo programa no Windows e Xubuntu, e funciona bem o ícone da bandeja.

Também tentei trocar de versões mas a reação é a mesma (.rpm).

Se houver um meio de impor uma regra para abrir todos os app da bandeja com 1 clique (como os do sistema) creio que resolva.

**I dont speak english, but my client Spark (messenger), i close and go systemtray in openSUSE, i dont can open 2 clicks, or 1 click, i need help this problem.

I don't use Spark, but you probably need to change some setting in the configuration to be able to maximize it from the system tray with a single or double click.

The program does not have this option, nor does openSUSE itself.

I think it's something Java related, because Spark uses Java, but jdk is already up to date.

Rightklick does not help?

I remember when I used Mercury Messenger, you had to use the official Java from Oracle in order for it to work properly. It was also necessary to use a special tray library to have a tray. Which Java are you using?

So don't use Spark....both Kopete and Kadu both support the Jabber protocol, and I use it instead of Spark on any Linux machine.

Yes.

Java 1_7_0, is already.

I need Spark, is all sector in my county, and is complete.

I discussed the problem in the forum in Brazil, and a user gave me a suggestion, and nothing worked.

Until we found a bug in openSUSE, problem is the openSUSE Java in KDE, is JavaEmbeedFrame, bug is in Plasma 5 I think.

Java + KDE is the problem, the tray icon works correctly with XFCE on Xubuntu and Windows.

Here bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1026999

Last try: zypper ar http://download.opensuse.org/reposit...workspace.repo
zypper -n --gpg-auto-import-keys dup

I accept new suggestions.

No idea what that means. As said, both Kadu and Kopete are 'complete' and work with the EXACT same protocols/plugins that openfire/jabber uses. They support video using jitsi, and work perfectly. Sorry, just no reason to use a clunky (as you've seen), client when there is a native client that works much better.
This is wrong. I had the exact same bug with the Spark client and plasma4, and have ALSO seen it happen on Gnome. The Spark client is junk, period.

I need Spark, I work in the computer sector of my city (city here in Brazil are much larger than in the US), all public places (Hospital, School etc) are already with Spark, I would just like to fix, and not migrate to another client.

I've tested some clients (including native openSUSE / Xubuntu clients), but most had problems sending attachment (not sending), Spark was the only one that worked in this part.

But good news, openSUSE 42.3 has been released now, I will tester in VirtualBox with Spark.

Sorry, still makes absolutely no sense. You "NEED Spark"...because others use it? No...what you need is a client that works. As I've said before, twice now, both Kadu and Kopete work ABSOLUTELY FINE. I can send attachments, use video conferencing, group chat, etc. No problems at all. What 'sector of your city' you live in isn't relevant.

The client you're trying to load is garbage, and always has been. Has nothing to do with version/distro of Linux at all. Either live with the behavior that you're seeing, or load something else. Nothing else anyone can do for you.

I need because all the PCs already have, there are more than 200 computers in distant places, as I've already said, Hospital, Library, etc ...

It is easier to solve the problem than to migrate all machines, I just test Kopete in openSUSE and did not receive / send attachments, it expires, and as I said, Spark works fine on Windows and Xubuntu, the problem is the KDE.

Still makes zero sense; if you have 200 machines, you will STILL have to apply whatever fix you find to all 200 of those machines...same as you could install new clients on all 200 machines, isn't it? And you don't have to 'migrate all machines'...those clients are either already loaded or easily loaded with a single command from repositories. And as I said, Spark for Linux is garbage. Your choices remain:

1. Live with whatever problem you get from Spark
2. Use a different client
3. Use a different desktop which you claim 'solves' the problem

Choose one.

Well, just came up with a fourth option:

- Install the new 42.3 and see that really openSUSE 42.2 was crap =]

The new 42.3 is with many environments available, unlike the 42.2 with this problematic, only read complaints without solution.

I installed 42.3 with XFCE and that's it, Spark works correctly, everyone happy, now I'm going to migrate and get a definitive solution.

New openSUSE is fine, who knows now can compete with Ubuntu.