[jitsi-users] Some bugs still in jitsi 2.3


#1

A couple of months ago I filed a bug report on this mailing list for
jitsi here: http://lists.jitsi.org/pipermail/users/2013-August/004826.html
I haven't gotten a request from the devs to file a bug report in the
tracker, so I waited, but the email seems to have been forgotten. At
the time I was using Jitsi 2.2, but the bugs still seem to be present
on version 2.3.4872 on XUbuntu 13.10. This does not happen in Windows
7.

Emil, shall I add a ticket for these bugs?


#2

Hey there,

A couple of months ago I filed a bug report on this mailing list for
jitsi here: http://lists.jitsi.org/pipermail/users/2013-August/004826.html
I haven't gotten a request from the devs to file a bug report in the
tracker, so I waited, but the email seems to have been forgotten.

Yes that happens, sorry about that.

At
the time I was using Jitsi 2.2, but the bugs still seem to be present
on version 2.3.4872 on XUbuntu 13.10. This does not happen in Windows
7.

Emil, shall I add a ticket for these bugs?

Let's see what they were:

I'm using Jitsi v2.2 stable on Xubuntu 13.04 running XFCE, and I've
noticed some cosmetic problems.

First of all Jitsi always seems to create a very tiny inert window on
my desktop (I'm not sure, if I can call it a window though). This
"window" always appears on the top left of the screen, and is about
16x16 pixels. It looks like whatever pixels were last present at that
corner of the screen. If I run Jitsi normally, the window is not
visible, because it copies the pixels from the background and
disguises itself. But when I change the desktop background to another
image, the window becomes visible. Sometimes it steals pixel colors
from active windows. It doesn't seem to serve any purpose, doesn't
react when clicked on and cannot be moved. When I exit jitsi, the
window disappears. Please fix this so that the window does not appear.

It sounds like this one is related to the systray.

Secondly, the graphics for the task tray icon is ugly. The jitsi
symbol is misaligned - it appears on the bottom right corner of the
icon space rather than its center. It also lacks any transparency, and
instead has this ugly blue background.

Systray again.

Lastly, the right-click menu seems to be misbehaving. A lot of times
when I right-click the icon, the menu appears and then suddenly
disappears when I release the right mouse button. Right-clicking is
usually done very fast, so the menu is only visible for a brief
moment. Only in very rare instances will the menu stay up.

Is that the systray or the regular menu?

Another thing I noticed is that sometimes the menu will refuse to
close when left-clicking on the desktop (or anywhere outside the menu
for this matter). The only way to close the menu is to either select a
menu item on it (i.e. "Show") or by right-clicking the task icon to
have it reappear and hopefully disappear (see previous bug).

Same quesiton.

The lib that we've been using for showing the systray is obviously severely outdated now so we need to integrate a new one.

Could you please open a ticket for that?

Thanks,
Emil

···

On 26.11.13, 19:25, Cpp wrote:

--
https://jitsi.org


#3

The lib that we've been using for showing the systray is obviously
severely outdated now so we need to integrate a new one.

The systray "library" we use is the JRE. I recently looked into it and they
finally plan to fix it: in JRE9... So unless we really want to introduce a
library specifically for all the desktop managers, I guess we're stuck with.

And it's not that the distributions couldn't fix that in their package
manager's flavor of the JRE.

Could you please open a ticket for that?

I'm tempted to ask that this should be done on the distribution's tracker...

Thanks,
Emil

Ingo


#4

This looks like a small solution that is really easy to adopt, and thus I
think it's worth the time:
https://github.com/taksan/native-tray-adapter

It should not introduce new problems because it falls back to the JRE systray
whenever a different implementation is not available for whatever reason.
(At least if it does what the description promises.)

Tim

···

Am Dienstag, 26. November 2013, 22:01:12 schrieb Ingo Bauersachs:

> The lib that we've been using for showing the systray is obviously
> severely outdated now so we need to integrate a new one.

The systray "library" we use is the JRE. I recently looked into it and they
finally plan to fix it: in JRE9... So unless we really want to introduce a
library specifically for all the desktop managers, I guess we're stuck with.

And it's not that the distributions couldn't fix that in their package
manager's flavor of the JRE.

> Could you please open a ticket for that?

I'm tempted to ask that this should be done on the distribution's tracker...
> Thanks,
> Emil

Ingo

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users


#5

The lib that we've been using for showing the systray is obviously
severely outdated now so we need to integrate a new one.

The systray "library" we use is the JRE.

I thought we still fallback to jdic in some cases ... or maybe we don't. Not that it matters. They both started out from the same codebase

I recently looked into it and they
finally plan to fix it: in JRE9...

Eeer. So that's ... what ... 2015? 2016?

So unless we really want to introduce a
library specifically for all the desktop managers, I guess we're stuck with.

It's more that we need than we want. Currently the systray is particularly ugly on Linux not to mention unusable in some cases. I don't think it would be that hard to integrate such a lib though. And we should only need to do it on Linux. OS X is fine with the one from the JRE and Windows is more acceptable.

We could potentially also look for a cross platofm alternative.

We are shipping a 2 Meg libunbound after all and I think it's a fairly safe bet that more people will get to use the systray lib. (And this is not an attack on libunbound. I am just putting things into perspective).

And it's not that the distributions couldn't fix that in their package
manager's flavor of the JRE.

I think they can't actually. It's not just a matter of packaging. At least not for the core problems.

Could you please open a ticket for that?

I'm tempted to ask that this should be done on the distribution's tracker...

I am not against this. Not sure it will be enough though.

Emil

···

On 26.11.13, 22:01, Ingo Bauersachs wrote:

Thanks,
Emil

Ingo

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
https://jitsi.org


#6

The lib that we've been using for showing the systray is obviously
severely outdated now so we need to integrate a new one.

The systray "library" we use is the JRE.

I thought we still fallback to jdic in some cases ... or maybe we don't.
Not that it matters. They both started out from the same codebase

I thought we've thrown JDIC out when we got to 1.6 because it became part of
the JRE?

I recently looked into it and they
finally plan to fix it: in JRE9...

Eeer. So that's ... what ... 2015? 2016?

Maybe :slight_smile:
This was more a joke.

So unless we really want to introduce a
library specifically for all the desktop managers, I guess we're stuck
with.

It's more that we need than we want. Currently the systray is
particularly ugly on Linux not to mention unusable in some cases. I
don't think it would be that hard to integrate such a lib though. And we
should only need to do it on Linux. OS X is fine with the one from the
JRE and Windows is more acceptable.

Windows is fine too, no need for an alternative.

We could potentially also look for a cross platofm alternative.

We are shipping a 2 Meg libunbound after all and I think it's a fairly
safe bet that more people will get to use the systray lib. (And this is
not an attack on libunbound. I am just putting things into perspective).

Oh I don't care about the size - it was more the pain of building and
maintaining yet another native lib (that really really should be part of a
sane framework).

And it's not that the distributions couldn't fix that in their package
manager's flavor of the JRE.

I think they can't actually. It's not just a matter of packaging. At
least not for the core problems.

Could you please open a ticket for that?

I'm tempted to ask that this should be done on the distribution's

tracker...

I am not against this. Not sure it will be enough though.

Emil

Thanks,
Emil

Ingo

Ingo