[jitsi-dev] bugs/RFE I ran into


#1

Hello,

I've reported some of the bugs I ran into as well as some RFE to launchpad.

https://bugs.launchpad.net/ubuntu/+source/jitsi/+bugs?search=Search&field.bug_reporter=r0lf

1) MSN chat network is gone (migrated to Skype)
2) RFE: please redirect errors to a log file instead of stderr
3) jitsi ignores LC_MESSAGES

My understanding is that you guys want to discuss bugs first before they
are entered into the jitsi.org tracker, so here they are.

I ran into more than those three issues, in fact jitsi is currently
unusable for me since I cannot add account information successfully.
For example, even though my XMPP jabber.org account information is
correct, I always get an error that there was an error on login. This
might be due to some error in my package, though, so I haven't reported
that yet.

Regards

Rolf


#2

Redirecting this to the users ML where as I can see now it should have
gone in the first place. Sorry about that.

···

On 06.03.2014 12:13, Rolf Leggewie wrote:

Hello,

I've reported some of the bugs I ran into as well as some RFE to launchpad.

https://bugs.launchpad.net/ubuntu/+source/jitsi/+bugs?search=Search&field.bug_reporter=r0lf

1) MSN chat network is gone (migrated to Skype)
2) RFE: please redirect errors to a log file instead of stderr
3) jitsi ignores LC_MESSAGES

My understanding is that you guys want to discuss bugs first before they
are entered into the jitsi.org tracker, so here they are.

I ran into more than those three issues, in fact jitsi is currently
unusable for me since I cannot add account information successfully.
For example, even though my XMPP jabber.org account information is
correct, I always get an error that there was an error on login. This
might be due to some error in my package, though, so I haven't reported
that yet.

Regards

Rolf


#3

Hi,

Hello,

I've reported some of the bugs I ran into as well as some RFE to launchpad.

https://bugs.launchpad.net/ubuntu/+source/jitsi/+bugs?search=Search&field.bug_reporter=r0lf

1) MSN chat network is gone (migrated to Skype)

Well the msn connection is still active and I can still login, not
sure when it will be shutdown or whether we need to drop it before
that, as there maybe users using it.

2) RFE: please redirect errors to a log file instead of stderr

There are console loggers and file loggers and everything is logged in
the file, of course there are some libs that have some stderr logs and
we catch everything from java, but we are unable to do so for logs
from native code.

3) jitsi ignores LC_MESSAGES

Hum, we are using java property user.language. Not sure how java
detects this property, or is it a problem in java itself must check
it.

My understanding is that you guys want to discuss bugs first before they
are entered into the jitsi.org tracker, so here they are.

I ran into more than those three issues, in fact jitsi is currently
unusable for me since I cannot add account information successfully.
For example, even though my XMPP jabber.org account information is
correct, I always get an error that there was an error on login. This
might be due to some error in my package, though, so I haven't reported
that yet.

You can always try installing from our repo or running from source
(ant rebuild run) and test with those builds.

Regards
damencho

···

On Thu, Mar 6, 2014 at 6:13 AM, Rolf Leggewie <foss@rolf.leggewie.biz> wrote:

Regards

Rolf

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


#4

1) MSN chat network is gone (migrated to Skype)

Well the msn connection is still active and I can still login, not
sure when it will be shutdown or whether we need to drop it before
that, as there maybe users using it.

MSN itself is gone yes, but the API still exists for at least another month
for "foreign" applications - such as Jitsi. If you want to remove it from
your package:
- remove /src/net/java/sip/communicator/impl/protocol/msn
- remove /test/net/java/sip/communicator/slick/protocol/msn
- remove /lib/jml-1.0b5.jar
- remove all references to bundle-msn, bundle-msn-slick and
bundle-plugin-msnaccregwizz from /build.xml
- remove protocol-msn.jar and msnaccregwizz.jar from
/lib/felix.client.run.properties

However, I guess it's likely that we will remove it too before the next
stable release.

2) RFE: please redirect errors to a log file instead of stderr

There are console loggers and file loggers and everything is logged in
the file, of course there are some libs that have some stderr logs and
we catch everything from java, but we are unable to do so for logs
from native code.

Isn't it common practice to print errors on stderr? If not, most of those
can easily be eliminated by changing or removing the ConsoleHandler logger
in lib/logging.properties. Log files exist anyway (~/.jitsi/log).

3) jitsi ignores LC_MESSAGES

Hum, we are using java property user.language. Not sure how java detects
this property, or is it a problem in java itself must check it.

This is a problem with Java locales. They don't support that level of
abstraction. If at all, please file a bug against Java (I know that this
would be pointless).

My understanding is that you guys want to discuss bugs first before they
are entered into the jitsi.org tracker, so here they are.

Yes, thank you.

I ran into more than those three issues, in fact jitsi is currently
unusable for me since I cannot add account information successfully.
For example, even though my XMPP jabber.org account information is
correct, I always get an error that there was an error on login. This
might be due to some error in my package, though, so I haven't reported
that yet.

You can always try installing from our repo or running from source
(ant rebuild run) and test with those builds.

Or take a look into the logs or send them over.

Regards
damencho

Regards
Rolf

Ingo


#5

Thanks, Ingo and Damien for your comments.

1) MSN chat network is gone (migrated to Skype)

[...]

However, I guess it's likely that we will remove it too before the next
stable release.

That's good enough. It's not like it's creating any problem.

2) RFE: please redirect errors to a log file instead of stderr

There are console loggers and file loggers and everything is logged in
the file, of course there are some libs that have some stderr logs and
we catch everything from java, but we are unable to do so for logs
from native code.

Isn't it common practice to print errors on stderr? If not, most of those
can easily be eliminated by changing or removing the ConsoleHandler logger
in lib/logging.properties. Log files exist anyway (~/.jitsi/log).

Yes, it's common practice. But given the amount of errors (which might
be only warnings, I don't remember now), it seems better to redirect
them to a file for the time IMVHO.

3) jitsi ignores LC_MESSAGES

[...]

This is a problem with Java locales. They don't support that level of
abstraction. If at all, please file a bug against Java (I know that this
would be pointless).

:frowning:

I was afraid that might be the case.

I ran into more than those three issues, in fact jitsi is currently
unusable for me since I cannot add account information successfully.

[...]

Or take a look into the logs or send them over.

I suppose http://paste.debian.net/86228/ is the relevant part.

Best regards

Rolf

···

On 08.03.2014 22:22, Ingo Bauersachs wrote:


#6

2) RFE: please redirect errors to a log file instead of stderr

There are console loggers and file loggers and everything is logged in
the file, of course there are some libs that have some stderr logs and
we catch everything from java, but we are unable to do so for logs
from native code.

Isn't it common practice to print errors on stderr? If not, most of those
can easily be eliminated by changing or removing the ConsoleHandler

logger

in lib/logging.properties. Log files exist anyway (~/.jitsi/log).

Yes, it's common practice. But given the amount of errors (which might
be only warnings, I don't remember now), it seems better to redirect
them to a file for the time IMVHO.

[...]

I ran into more than those three issues, in fact jitsi is currently
unusable for me since I cannot add account information successfully.

[...]

Or take a look into the logs or send them over.

I suppose http://paste.debian.net/86228/ is the relevant part.

java.lang.NoClassDefFoundError: org/xbill/DNS/TextParseException

What dnsjava.jar are you using? If you open it in an archive utility, does
it contain a META-INF/manifest.mf file with OSGi declarations?

Best regards
Rolf

Ingo


#7

As a Ubuntu Precise user, I might very well be affected by that bug with
OSGi data. The package of libdnsjava-java is version 2.0.8-1 and thus
unpatched from Debian. The content of the file you were asking for is

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.1
Created-By: 16.0-b10 (Sun Microsystems Inc.)
Implementation-Title: dnsjava
Implementation-Version: 2.0.8

Nothing else. I hope that answers the question.

···

On 08.03.2014 23:49, Ingo Bauersachs wrote:

Or take a look into the logs or send them over.

I suppose http://paste.debian.net/86228/ is the relevant part.

java.lang.NoClassDefFoundError: org/xbill/DNS/TextParseException

What dnsjava.jar are you using? If you open it in an archive utility, does
it contain a META-INF/manifest.mf file with OSGi declarations?


#8

Or take a look into the logs or send them over.

I suppose http://paste.debian.net/86228/ is the relevant part.

java.lang.NoClassDefFoundError: org/xbill/DNS/TextParseException

What dnsjava.jar are you using? If you open it in an archive utility,

does

it contain a META-INF/manifest.mf file with OSGi declarations?

As a Ubuntu Precise user, I might very well be affected by that bug with
OSGi data. The package of libdnsjava-java is version 2.0.8-1 and thus
unpatched from Debian. The content of the file you were asking for is

The OSGi metadata was introduced with the 2.1.5 upload to Debian.

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.1
Created-By: 16.0-b10 (Sun Microsystems Inc.)
Implementation-Title: dnsjava
Implementation-Version: 2.0.8

Nothing else. I hope that answers the question.

Yes. I see two options for backporting:
- Use an embedded dnsjava with the necessary OSGi metadata included
- Use the hacks we need for other libraries:
  - create a directory named "dnsjava.jar" in Jitsi's bundle directory
  - symlink the systems' dnsjava.jar into this directory
  - create the dir dnsjava.jar/META-INF
  - create manifest.mf inside this directory, it must contain
    - everything that is in the original manifest.mf
    - the required OSGi metadata (which is missing in the original)
    - the additional property Bundle-ClassPath=.,dnsjava.jar

See the json.jar directory for an example that uses the same technique.

But even with that workaround, I'm not sure if 2.0.6 is going to work. I
think we updated it because we ran into bugs with that version, although I
don't remember what it was right now.

Ingo

···

On 08.03.2014 23:49, Ingo Bauersachs wrote:


#9

The OSGi metadata was introduced with the 2.1.5 upload to Debian.

Are you sure it was 2.1.5 and not 2.1.4? The changelog seems to suggest
the latter.

Yes. I see two options for backporting:

Thank you for the explanation. I'll look into those options with
regards to Debian and Ubuntu.

But even with that workaround, I'm not sure if 2.0.6 is going to work.

2.0.8

···

On 10.03.2014 18:18, Ingo Bauersachs wrote:


#10

The OSGi metadata was introduced with the 2.1.5 upload to Debian.

Are you sure it was 2.1.5 and not 2.1.4? The changelog seems to suggest
the latter.

Which changelog?
Debian is definitely 2.1.5, but 2.1.4 will do too.

Yes. I see two options for backporting:

Thank you for the explanation. I'll look into those options with
regards to Debian and Ubuntu.

But even with that workaround, I'm not sure if 2.0.6 is going to work.

2.0.8

That was a typo.
The binary in our repo is 2.1.3 with a patch that got included in the 2.1.4
release.

Ingo

···

On 10.03.2014 18:18, Ingo Bauersachs wrote:


#11

I misread the question. Yes. 2.1.4.

Ingo

···

On 10.03.2014 18:18, Ingo Bauersachs wrote:

The OSGi metadata was introduced with the 2.1.5 upload to Debian.

Are you sure it was 2.1.5 and not 2.1.4? The changelog seems to suggest
the latter.


#12

I've made the necessary changes locally and pushed them to the PPA as well.

···

On 10.03.2014 22:33, Ingo Bauersachs wrote:

2.1.4 will do too.