Good evening everybody,
@ Damian: thank you very much for your hint!
Deleting the 'sip-communicator-bin'-folder did not work out.
It however inspired me to copy outright the '.jitsi'-folder of my
'/'-account (remember: with "sudo jitsi", Jitsi would start and not get
stuck) to my '/home/user'-account, i.e. to replace the former
'user'-'.jitsi'-folder. -->and it worked!
Subsequent try-and-error approach (replacing one of the old 'user'
'.jitsi-sub-folders with the '/'-'.jitsi'-subfolder-equivalent then
showed that it's the 'sip-communicator.properties'-file (and not any
other subfolder or file) which actually caused the problem. I could
leave all old 'user'-'.jitsi'-subfolders and -files unchanged and change
the latter file and jitsi would run anew through my ordinary
Thank you again for your quick feedback and helpful hint!
Am 28.10.2014 um 12:00 schrieb email@example.com:
Send users mailing list submissions to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."
1. Re: jitsi 2.5.5065-1_amd64.deb: stuck with 'UI Service
Provider Implementation'-status while run as normal user
Date: Tue, 28 Oct 2014 09:09:45 +0200
From: Damian Minkov <firstname.lastname@example.org>
To: Jitsi Users <email@example.com>
Subject: Re: [jitsi-users] jitsi 2.5.5065-1_amd64.deb: stuck with 'UI
Service Provider Implementation'-status while run as normal user
Content-Type: text/plain; charset=UTF-8
it is a strange one, never seen it before. You can try deleting the
felix cache folder. It is located in the jitsi's home folder
(https://jitsi.org/faq#jitsi-home), the folder is named
On Tue, Oct 28, 2014 at 1:56 AM, abc123 <firstname.lastname@example.org> wrote:
I am using Jitsi for some time now and I am really happy it is
OpenSource and about its' privacy/encryption-features.
However, today (running Jitsi on Debian Jessie) I happened to minimise
Jitsi (I did not quit through menu-item 'file' -->'quit'). After that I
was unable to go back to/reactivate Jitsi. I then killed the respective
java-process (ps -aux | grep jitsi ...) and tried to start Jitsi again.
It would however get stuck with status 'UI Service Provider
Implementation' (please see screep-print attached). Reboot did not help.
When starting it through the terminal, however the following message
"sun.awt.image.PNGImageDecoder$PNGException: crc corruption", after
which Jitsi ends up getting stuck again with 'UI Service Provider
Now, when I run Jitsi with "sudo", no such "crc corruption" message
appears in the shell and Jitsi starts normally, is useable and is not
getting stuck with status 'UI Service Provider Implementation'.
I have the 2 log-files (normal user log-file and super user log-file)
attached, did not happen to identify anything tangible error-source. May
be anyone of you - given your experience - is able to detect the cause
of the error... ?
-->I attach as well the normal user shell-content (containing the normal
user error-message 'crc corruption', as opposed to the super-user shell,
where no such message appears).
Your information and hints are greatly appreciated, please do let me
know should any further information be required from my side.
End of users Digest, Vol 19, Issue 46