[jitsi-dev] General settings tab not displaying correctly


#1

Hi,

Please see attached screenshot. Running 2.3.4970-x64 on Windows 8 x64. Also experienced this on 2.3.4889-x64 and x86.

Oddly, I was running 2.3.4889-x86 and was having this issue. I then uninstalled 4889 and installed 4970,

When I FIRST open 4970, I was able to view the General settings. Next time I ran Jitsi I was (and still) cannot.

This is reproducible on another Windows 8 x64 system.

Aaron Dixon
IT Specialist
aaron.dixon@ssdcservices.com

SSDC Services
28125 Cabot Drive, Suite 201
Novi, MI 48377
O: (248) 277-9304
C: (248) 935-7353
F: (248) 344-1623
www.ssdcservices.com<http://www.ssdcservices.com/>


#2

Please see attached screenshot. Running 2.3.4970-x64 on Windows 8 x64. Also
experienced this on 2.3.4889-x64 and x86.

Please send us Jitsi's logs. https://jitsi.org/Documentation/FAQ#logs

When I FIRST open 4970, I was able to view the General settings. Next time I
ran Jitsi I was (and still) cannot.

Should we presume you're able to navigate away from the Audio tab to
any tab other than General?

By the way, why are you using PortAudio instead of Windows Audio
Session API (WASAPI)?

···

2013/12/11 Aaron Dixon <aaron.dixon@ssdcservices.com>:


#3

"Archive Logs" button does not prompt me to save logs in 2.3.4970 on Windows 8 x64.

<< Should we presume you're able to navigate away from the Audio tab to any tab other than General?

Yes I can navigate away. And then when I navigate back it shows whatever tab I was on previously.

<< By the way, why are you using PortAudio instead of Windows Audio Session API (WASAPI)?

Was just doing testing.

log.zip (26.7 KB)

···

------------

OK. I just reproduced this glitch. I uninstalled Jitsi. Deleted Jitsi folder in APPDATA\Roaming and APDDATA\Local of my userprofile. Then re-installed 2.3.4970. Upon first launch I was able to view the "General" settings AND export logs. I then exited Jitsi and re-opened. Now am not able to export Logs or view General settings.

I have attached %LOCALDPPDATA%\Jitsi\log

Aaron Dixon
IT Specialist
aaron.dixon@ssdcservices.com

SSDC Services
28125 Cabot Drive, Suite 201
Novi, MI 48377
O: (248) 277-9304
C: (248) 935-7353
F: (248) 344-1623
www.ssdcservices.com

-----Original Message-----
From: dev-bounces@jitsi.org [mailto:dev-bounces@jitsi.org] On Behalf Of Lyubomir Marinov
Sent: Tuesday, December 10, 2013 7:07 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] General settings tab not displaying correctly

2013/12/11 Aaron Dixon <aaron.dixon@ssdcservices.com>:

Please see attached screenshot. Running 2.3.4970-x64 on Windows 8 x64.
Also experienced this on 2.3.4889-x64 and x86.

Please send us Jitsi's logs. https://jitsi.org/Documentation/FAQ#logs

When I FIRST open 4970, I was able to view the General settings. Next
time I ran Jitsi I was (and still) cannot.

Should we presume you're able to navigate away from the Audio tab to any tab other than General?

By the way, why are you using PortAudio instead of Windows Audio Session API (WASAPI)?

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


#4

As that question seems to suggest that we should be avoiding using
PortAudio, I feel I should point out that if I use WASAPI I have no
option for my webcam mic (PS3 Eye), nor can I select my Razer Surround
for the output but both are selectable using PortAudio. Obviously I
don't need surround for voice chat but if I select the Realtek output
whilst Razer is activated (either in PortAudio or WASAPI), I get no
output and it's not practical to keep disabling/enabling Razer
depending on what I'm doing, so PortAudio allows me to avoid needing
to, as well as letting me use my PS3 Eye mic. The actual camera still
doesn't work with Jitsi but I understand that's because it uses some
sort of driver that's incompatible with the way Jitsi works, even
though I can use it in other apps.

Regards
Derek

···

On 11 December 2013 15:24, Aaron Dixon <aaron.dixon@ssdcservices.com> wrote:

"Archive Logs" button does not prompt me to save logs in 2.3.4970 on Windows 8 x64.

<< Should we presume you're able to navigate away from the Audio tab to any tab other than General?

Yes I can navigate away. And then when I navigate back it shows whatever tab I was on previously.

<< By the way, why are you using PortAudio instead of Windows Audio Session API (WASAPI)?

Was just doing testing.


#5

Aaron, thank you for the logs! The following is causing the problems
in both cases:

java.lang.UnsatisfiedLinkError:
C:\Users\ki3255\AppData\Local\Temp\jna2017702072837409083.dll: Access
is denied

Do you have an idea what could be denying the access to that file?
Anti-virus software, for example?

···

2013/12/11 Aaron Dixon <aaron.dixon@ssdcservices.com>:

Now am not able to export Logs or view General settings.


#6

As that question seems to suggest that we should be avoiding using
PortAudio,

WASAPI should be preferred over PortAudio when possible.

I feel I should point out that if I use WASAPI I have no
option for my webcam mic (PS3 Eye), nor can I select my Razer Surround
for the output but both are selectable using PortAudio. Obviously I
don't need surround for voice chat but if I select the Realtek output
whilst Razer is activated (either in PortAudio or WASAPI), I get no
output and it's not practical to keep disabling/enabling Razer
depending on what I'm doing, so PortAudio allows me to avoid needing
to, as well as letting me use my PS3 Eye mic. The actual camera still
doesn't work with Jitsi but I understand that's because it uses some
sort of driver that's incompatible with the way Jitsi works, even
though I can use it in other apps.

I am not aware of a Jitsi developer who is in possession of such hardware.

···

2013/12/11 Derek Moss <dmts@stoptheviolence.co.uk>:


#7

That was it! Thank you and my apologies.

···

-----Original Message-----
From: dev-bounces@jitsi.org [mailto:dev-bounces@jitsi.org] On Behalf Of Lyubomir Marinov
Sent: Wednesday, December 11, 2013 1:48 PM
To: Jitsi Developers
Subject: Re: [jitsi-dev] General settings tab not displaying correctly

2013/12/11 Aaron Dixon <aaron.dixon@ssdcservices.com>:

Now am not able to export Logs or view General settings.

Aaron, thank you for the logs! The following is causing the problems in both cases:

java.lang.UnsatisfiedLinkError:
C:\Users\ki3255\AppData\Local\Temp\jna2017702072837409083.dll: Access is denied

Do you have an idea what could be denying the access to that file?
Anti-virus software, for example?

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


#8

Obviously we can't expect Jitsi devs to have access to every webcam
but I imagine all devices must use one or another standard interface
to the OS, as if they used something proprietary and non-standard the
webcam wouldn't work in any app.

Is there anything I can do at my end that will produce some debug
information that will help the devs to identify how to make it work
with Jitsi? I imagine this would not just enable Jitsi to work with
the PS3 Eye but also other webcams that use the same interface to the
OS.

···

On 11 December 2013 18:38, Lyubomir Marinov <lyubomir.marinov@jitsi.org> wrote:

2013/12/11 Derek Moss <dmts@stoptheviolence.co.uk>:

As that question seems to suggest that we should be avoiding using
PortAudio,

WASAPI should be preferred over PortAudio when possible.

I feel I should point out that if I use WASAPI I have no
option for my webcam mic (PS3 Eye), nor can I select my Razer Surround
for the output but both are selectable using PortAudio. Obviously I
don't need surround for voice chat but if I select the Realtek output
whilst Razer is activated (either in PortAudio or WASAPI), I get no
output and it's not practical to keep disabling/enabling Razer
depending on what I'm doing, so PortAudio allows me to avoid needing
to, as well as letting me use my PS3 Eye mic. The actual camera still
doesn't work with Jitsi but I understand that's because it uses some
sort of driver that's incompatible with the way Jitsi works, even
though I can use it in other apps.

I am not aware of a Jitsi developer who is in possession of such hardware.