[Windows 10] Account and contacts lost after you exit Jami; no audio device detected after changing the output scaled resolution of OBS
Something strange happend: (using newest version of Jami AND OBS Studio, Windows 10)
I wanted to test out OBS-VirtualCam.
I've opened Jami (you automatically sign in to the Jami user account) and I've selected video source "OBS-VirtualCam".
OBS: Normally (previous versions of Jami) if you didn't click on "Start Virtual Camera" Jami only shows the following picture: Link: https://streamtalk.de/attachment/1894-obs-png/?thumbnail=1 And if you click on "Start Virtual Camera" you can see your screen etc.
However - This time everything I've seen is a black screen. I've tried it a couple of times again AND suddenly after a few seconds I saw the video of the OBS-VirtualCam.
I can't remember what happend next but I think I tried to return to another camera. Returning didn't work. So I quitted Jami.
Suddenly- as soons as I wanted to open Jami my account was missing: I used the option transfer my account to another device and was able to log in again.
BUT- As soon as I've closed Jami and open the program again the account is still missing again (I have to transfer my account again).
So I restarted my PC.
Since then Jami has no audio source anymore - no audio source is showing up (microphone, output device and ringtone device).
Every time I exit Jami and open the program again my account is logged out automatically and I have to transfer my account from another device again.
Activity
The account was deleted and suddenly shown again (after importing the Jami account; together with "new"(=same) devices). - Many times I closed and reopened Jami.
I don't have these problems anymore. So I will close this issue.
But @sblin If this issue occurs again how do I get the logs from the daemon (Windows)? I only see "On GNU/Linux".
Edited by ElysSame issue again (logged out if I restart, Windows 10). It's actually: #568 (closed)
Seems to happen randomly?
@sblin How do I get the logs from the daemon?
Edited by ElysEDIT: Suddenly everything works again. I opened Jami after a short time again. (However the day before I very often exit and launched Jami again and it never changed)
Not sure if it's important. I used a usb webcam for a few times and the removed the device today. But I think I had this issues in the past even if I didn't use a usb webcam.
Edited by Elys
mentioned in issue #568 (closed)
Same issue again. I used OBS-VirtualCam before and other software. (Not sure if this is important to mention).
@sblin Here are the logs:
[1646844644.962|24960|ringbuffer.cpp :55 ] Create new RingBuffer audiolayer_id [1646844644.994|24960|video_device.h :135 ] Default video settings: 640x480, 29.97000002997 FPS [1646844644.999|24960|video_device_monitor.cpp:222 ] Failed to add device video=@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{27B05C2D-93DC-474A-A5DA-9BBA34CB2A9C}: invalid map key [1646844645.004|24960|video_device_monitor.cpp:222 ] Failed to add device video=@device_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{9E2FBAC0-C951-4AA8-BFA9-4B196644964C}: invalid map key [1646844645.010|24960|manager.cpp :713 ] Not initialized [1646844645.011|24960|manager.cpp :713 ] Not initialized 17:50:45.017 os_core_win32. !pjlib 2.11 for win32 initialized [1646844645.017|24960|manager.cpp :784 ] Using PJSIP version 2.11 for win32 [1646844645.018|24960|manager.cpp :785 ] Using GnuTLS version 3.6.7 [1646844645.018|24960|manager.cpp :786 ] Using OpenDHT version 2.3.0 [1646844645.018|24960|manager.cpp :787 ] Using FFmpeg version 4.0.0-2597-g21c8feb73 [1646844645.019|24960|manager.cpp :790 ] Using Libgit2 version 1.1.0 [1646844645.025|24960|sipvoiplink.cpp :742 ] SIPVoIPLink@0000023B708E64F0 [1646844645.027|24960|manager.cpp :806 ] Configuration file path: C:\Users\Myusername\AppData\Local\jami\dring.yml Error initializing daemon No accounts to migrate QObject::connect(lrc::api::ContactModel, ContactAdapter): invalid nullptr parameter Can't update current account info data for "" NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar NewAccountModel::getAccountInfo, can't find dummy ; Using default avatar latest: 202112221025 current: 202112221635 No new version foundI still don't know how I can get the daemon logs using Windows 10.
Aren't these just the client logs ?
EDIT: It seems it it takes a lot of time (weeks ?) that Jami can "remember" the user account. Otherwise you have to import your account again which means you have multiple devices connect (although you "just" have one pc)
@sblin or @atraczyk How do I get the daemon (NOT the client) logs if I am using Windows 10? Or is it simply not possible to get the daemon logs if I use windows 10?
But this issue seems to also appear if you are using a linux distro:
See: #568 (closed)
I am using Ubuntu 18 with Jami installed via snap.
Edited by ElysYes, the Windows client file logging mechanism was broken during the addition of the GUI log widget. There is a fix for that in review(https://review.jami.net/c/jami-client-qt/+/21247) and also an improvement to the console logging mechanism in which the logs will be routed to the parent console window if possible(https://review.jami.net/c/jami-daemon/+/21251). This will allow the logs to persist beyond the lifetime of Jami.exe.
@atraczyk you will need to update https://git.jami.net/savoirfairelinux/jami-project/-/wikis/tutorials/Bug-report-guide#client-qt-windows-gnulinux once the patches will be merged
@sblin will do
@sblin @atraczyk But will this patch allow to get the DAEMON logs (NOT "just" the client logs) like it should be possible if I were using a linux distro?
Since the Ring GUI and daemon are separated processes, the easiest way to get logs from both is to start them one at a time, manually.
And how will I get the daemon logs if my account is lost at the beginning? Because the log system of Jami only works once Jami is started (AFTER the welcome page)? And the cmd.exe only shows the client logs?
Or are the daemon logs already included if I use Windows 10?
But - as mentioned:
If you take a look at the logs below are they enough to reproduce and fix this issues?
And how will I get the daemon logs if my account is lost at the beginning? Because the log system of Jami only works once Jami is started (AFTER the welcome page)? And the cmd.exe only shows the client logs?
@El4 The logging patches I posted previously will soon be merged and correct this behavior.
Regarding this issue, can you please clarify what you mean by "account logged out"? Or better yet, what indicates to you that you must re-import your account? (e.g. account expired/migration required, account disconnected)
I've just tested several scenarios using version 202203161422 on Windows 10 and OBS Studio 27.2.3, and I get expected results when routing the
OBS Virtual Cameradevice as my video input. Have you tried version 202203161422?Audio and video device detection mechanisms are different. So this issue looks like 3 issues in one. Something like:
- account corruption
- missing audio device
- black screen only for
OBS Virtual Camera
Can you confirm/clarify/comment?
@atraczyk I am not sure if OBS Virtual Cam is related to this issue. I also had this issue if I was using a "real" webcam. So it seems to be just a coincidence. (regarding the OBS-Virtual Cam)
It's actually the same as: #568 (closed)
But Jami also does not remember the audio devices:
I just get Audiomanager "portaudio". I have no microphone, no video input and no ring device.
In the past I had no issues: All audio devices were displayed correctly. (I just have this issue (jami-project#1401 (moved)) but probably not (?) because of the mentioned issue)
So this is my scenario [using Windows 10, newest (no-beta) version of Jami]:
Normally:
I double-click on Jami. (I don't have welcome page since I already created my Jami user account)
Now I can make calls, write text messages, etc.
This issue:
- I double-click on Jami.
- Suddenly I can see the welcome page (although I already have linked my account to this device before)
- However I link my acount to this device AGAIN. (using my Android smartphone)
- Jami shows the page where I can make video calls etc. .
- However:
I just get Audiomanager "portaudio". I have no microphone, no video input and no ring device.
- I exit Jami.
- As soon as I open (/double-click on) Jami again I see the welcome page again AND I have to link my account again (and again ....)
However, in the past - maybe after a few weeks and 20 attempts - everything worked again.
I just get Audiomanager "portaudio". I have no microphone, no video input and no ring device.
And my own profile picture in contact list is missing
Logs:
[1647460564.086|19504|manager.cpp :2181 ] Audio layer not initialized [1647460564.088|19504|manager.cpp :2181 ] Audio layer not initialized [1647460564.095|19504|manager.cpp :2197 ] Audio layer not initialized [1647460564.099|19504|fileutils.cpp :159 ] Path expansion not implemented, returning original [1647460564.201|19504|manager.cpp :2181 ] Audio layer not initialized [1647460564.203|19504|manager.cpp :2197 ] Audio layer not initializedEdited by ElysIf I restart I get the same issue -again. Jami does not remember the account anymore.
Again "Error initializing daemon".
The following logs I only get if I import my account from another device:
[1647458384.156| 2320|account_manager.cpp:79 ] Error loading identity: Can't convert string to wstringI changed the Account to 9291d08f66856eeb (not really my account)
[1647458384.157| 2320|jamiaccount.cpp :2419 ] [Account 9291d08f66856eeb] disconnected [1647458384.158| 2320|jamiaccount.cpp :1698 ] [Account 9291d08f66856eeb] Bootstrap node: bootstrap.jami.net [1647458384.159|30652|pupnp.cpp :366 ] PUPnP: Start search for IGD: attempt 1 [1647458384.160| 2320|jamiaccount.cpp :821 ] Exported account to C:\Users\Myusername\AppData\Local\jami\9291d08f66856eeb\config.yml NewAccountModelPimpl::slotVolatileAccountDetailsChanged, can't find "9291d08f66856eeb" [1647458384.163| 2320|jamiaccount.cpp :1667 ] [Account 9291d08f66856eeb] Starting account..[Can't open file: "C:/Users/Myusername/AppData/Local/jami/9291d08f66856eeb/profile.vcf" [1647458384.232|31648|account_manager.cpp:457 ] getContacts(): account not loaded [1647458384.233|31648|account_manager.cpp:549 ] getTrustRequests(): account not loaded [1647458384.234|31648|jamiaccount.cpp :2252 ] Calling convModule() with an uninitialized account. [1647458384.235|31648|jamiaccount.cpp :2252 ] Calling convModule() with an uninitialized account.Edited by ElysThe next logs
[1647458387.168|30804|account.cpp :497 ] [1647458387.168|22520|upnp_context.cpp :423 ] Couldn't find key "Account.bootstrapListUrl" Successfully unregistered controller 00000286334799A0 [1647458387.169|30804|account.cpp :497 ] Couldn't find key "Account.archivePassword" [1647458387.171|22520|upnp_context.cpp :149 ] Stopping UPNP context [1647458387.171|30804|account.cpp :497 ] Couldn't find key "Account.archivePIN" [1647458387.172|30652|pupnp.cpp :321 ] [1647458387.172|28144|igd.cpp :48 ] PUPnP: clearing IGDs and devices lists [1647458387.172|30804|account.cpp :507 ] IGD 192.168.1.1 [NAT-PMP] was disabled Couldn't find key "Account.archivePath"[1647458387.186|31684|jamiaccount.cpp :2600 ] Failed to load DhParams file 'C:\Users\Myusername\.cache\jami\9291d08f66856eeb\dhParams': Can't open: C:\Users\Myusername\.cache\jami\9291d08f66856eeb\dhParams [1647458387.187|22520|jamiaccount.cpp :1857 ] [Account 9291d08f66856eeb] Starting account... [1647458387.188|31684|diffie-hellman.cpp:87 ] Generating DH params with 3072 bits [1647458387.189|22520|jamiaccount.cpp :2501 ] Could not load C:\Users\Myusername\.cache\jami\9291d08f66856eeb\treatedMessages[1647458387.293|31648|account.cpp :514 ] Couldn't find key "Account.allModeratorEnabled"[1647458387.317|22520|jamiaccount.cpp :2501 ] Could not load C:\Users\Myusername\.cache\jami\9291d08f66856eeb\treatedMessages[1647458404.596|26380|jamiaccount.cpp :4183 ] invalid filename 'C:\Users\Myusername\AppData\Local\jami\9291d08f66856eeb\profile.vcf'Now I have the same devices linked a multiple times (if I recover my account)
Edited by Elys
mentioned in issue #536 (closed)
@atraczyk I just updated Jami and now I have the newest version of Jami.
However - still same issue (again and again):
I can see the welcome page (although I already have linked my account to this device before)
Now I always use "Import account from backup file".
Jami shows the page where I can make video calls etc. .
I just get Audiomanager "portaudio". I have no microphone, no video input and no ring device.
However all video devices are shown.
As soon as I open (/double-click on) Jami again I see the welcome page again AND I have to link my account again (and again ....)
Sometimes I can see only one linked device but I think I've already seen many linked devices (same account, same pc)
@atraczyk I just wanted to mention: If this issue occurs I get this other issue (again):#604 (closed)
@sblin @atraczyk Now I am using the newest beta version. Same issue remains. (I think in the past after a few weeks/months everything suddenly worked again)
I need to add that if you plug new audio devices into the audio jack / usb port (after you launched Jami) Jami still does not detect any audio device.
However webcams ("videos") are detected (but you can't use the audio input / microphone)
Edited by Elysmentioned in issue jami-docs#5 (closed)
I have to mention that also your contacts (you have added before) in contact list are lost after you exit Jami.
If I take a look at the logs it seems there is an issue because of the "account.cpp" and "jamiaccount.cpp"
For example "Error loading identity: Can't convert string to wstring"
If I use the proxy:
"[1648840835.694| 3096|jamiaccount.cpp :331 ] [Account dummy] Can't load proxy URL from cache: Can't open: C:\Users\Myusername.cache\jami\dummy\dhtproxy"[1648840837.877| 7820|jamiaccount.cpp :2653 ] Failed to load DhParams file 'C:\Users\Myusername\.cache\jami\1234..d\dhParams': Can't open: C:\Users\Myusername\.cache\jami\1234..d\dhParams1234..d was edited
So maybe it's an issue because of the cache?
Edited by Elys@Mehdighayour Until now I can't use Jami because of this issue (I can't use any audio device (input/output) and Jami does not remember the account). The other developers seem busy.
Regarding the bug report: https://git.jami.net/savoirfairelinux/jami-project/-/wikis/tutorials/Bug-report-guide#providing-additional-information
Is it (now) possible to get seperate DAEMON (NOT client) logs if I am using Windows 10?
@Mehdighayour Not sure if this helps/ is useful for developers ... but if it is ... Can you add the Gitlab option relates to #568 (closed) ? (Because it's nearly the same but I have more bugs)
added BacklogHigh label
marked this issue as related to #568 (closed)
@El4 Sure, I related #568 (closed) to this ticket, just in case it would be helpful!
@Mehdighayour Thanks. Should you / the developers reopen the issue (#568 (closed)) or do we just continue using this forum thread?
-
@El4 No problem! Developers will decide on that. If it's needed to reopen that, they'll do that.
Jami is still unusable because of this issue. I will keep testing as soon as this bug is fixed
Edited by Elysmentioned in issue #722 (closed)
added non-reproducible label
Nobody seems to reproduce it on a lot of devices.
@sblin Nope. This issue has been already reported (but not using the Windows 10 client, but a linux client). See: #568 (closed)
I am using Ubuntu 18 with Jami installed via snap.
I've asked the same question many times but still got not the right answer:
Can you get the DAEMON (not client) logs if you are using Windows 10? The docs don't show any way how I can differentiate between the daemon and client logs if I am using Windows (NOT any Linux distro).
(It seems you can just get daemon and client logs if you are using GNU/Linux)
As mentioned: I once suddenly had this issue for a few weeks. Then everything suddenly worked again. ( I used Jami ~40 times) Now I have this issue again.
Edited by Elys-
This issue has been already reported (but not using the Windows 10 client, but a linux client
It still not reproductible by us, contains no scenario for us, no answer about the datas (#568 (comment 31228) I asked there, or infos for windows: https://git.jami.net/savoirfairelinux/jami-project/-/wikis/tutorials/Frequently-Asked-Questions#basics-5)
for logs, infos are on the bug report guide page:
For Windows
Open a terminal(cmd.exe) and launch Jami.exe with the following options:
-
-dto log to the console -
-f <logfile>to write logs to<logfile>
and this get the logs from the daemon.
But again, without scenario this issue will probably never advance, and are accounts in the directory.
The most probable thing is that your camera from OBS is just unusable, corrupting dring.yml, cause "
evice_sw_{860BB310-5D01-11D0-BD3B-00A0C911CE86}\{27B05C2D-93DC-474A-A5DA-9BBA34CB2A9C}: invalid map ke" this makes no sense for your settings. (cc @atraczyk ) -
-
So yeah, precise the exact step. But for me, as it's related to the usage of virtual camera with incorrect settings. it's not a "high priority" issue (cc @Mehdighayour) as it's not a common use case.
-
Thanks @sblin for the response. As it's a rare scenario and needs more details to reproduce, I'll label it as "Backlog-low".
I think this issue just once happend randomly while using OBS. (At first I just thought it might be related)
@atraczyk @sblin My issue still persists / reappears even if I never used OBS again.
contains no scenario for us
I already posted the logs I got. - I just used -d ... and the first logs show "Error initializing daemon" and then if I select "Import account from backup file" (I have to do that every time I exit and enter Jami again) I get issues like "Can't load from cache"
precise the exact step
-
Open Jami (it does not matter if you run Jami as an admin or not)
-
All settings (except language settings) and your account(s) are lost - You see the "Welcome page"
-
Import account from backup file
-
Now you can see your own account
-
No contacts are in your contact list (even if you added them before you used Jami the last time)
-
Add contacts
-
Write messages/ make calls (-doesn't make sense since no audio device is detected)
-
Exit Jami -> Now you start from step 1 again
However - you can NEVER use any audio device (or just the audio of your webcam)- "no audio device detected" (although before this issue appeared I was able to select all my audio devices)
Edited by Elys-
-
Can't load from cache
Is ok, as you import there is no cache yet
By scenario is how we can reproduce ourself. If I reproduce step 1 to 8 on several computers I never saw this issue, so something is missing. It means that a config or other thing needs to be determined.
C:\Users\Myusername\AppData\Local\jami\dring.ymlis probably malformed and the important thing to understand is how you scrap your config. Without this information, there is no magic, the issue will just not advance. As we said, we can't reproduce on a lot of devices. And personally I don't have any clue and never saw that If I reproduce step 1 to 8 on several computers I never saw this issue, so something is missing.
That's actually the point. This is why I first thought it is related to OBS. But it seems this is wrong/just a coincidence?
And personally I don't have any clue and never saw that
That's actually also strange. I NEVER changed any settings and suddenly I got this issue in the past. After a few weeks (I always tried using Jami) it suddenly worked again. I never had this issue again... at least over months
And now - same issue again. I think it happens randomly but once this issue occurs it stays very long. (BTW: I am using now the newest beta version of Jami). I think that the developers (at least Windows 10 users ... Ubuntu? dont't know) might get this issue suddenly after you use Jami.
(I think there was no Windows update that could be the reason ... but I'm not sure ... if it's just because of a specific windows update Ubuntu users should never had this (same/similar) issue?)
But at the moment I can't use Jami since you can only make video calls or ... audio calls ... WITHOUT any audio or audio device... and that doesn't make any sense.
removed BacklogHigh label
added BacklogLow label
mentioned in issue jami-project#1401 (moved)
mentioned in issue #739 (closed)
@sblin I suddenly had the same issue again. Not sure - but this time OBS was involved again.
Steps to reproduce?
I opened Jami; I saw that the resolution of OBS VirtualCam was not right (I did NOT open OBS Studio - Although the Virtual Cam showed up)
Now I opened OBS-Studio: Base resolution: 1360x768 did not change anything. However I changed the output scaled resolution to 1360x768 (before I had 1280 x 564?) and changed the common fps value to 30 fps (instead of 60 fps).
Now I exit Jami and launch OBS Virtual Cam.
Now I want to open Jami. Suddenly "Account and contacts lost after you exit Jami; no audio device detected ".
I stopped the virtual cam and exit OBS-Studio.
I used "Import account from backup file".
However this time
The first time I opened Jami just the contacts were lost and no audio device was detected.
Then I exit Jami again.
After I open Jami again just one contact in the contact list was missing.
I exit Jami and launch OBS-VirtualCam. This time the contacts in the contact list are shown again.
Not sure if it related to OBS or it just happens randomly.
Now I don't have any issues again. Maybe I can reproduce later?
EDIT 1: The account in the contact list appears again if I launch Jami AND start OBS-VirtualCam -I always keep OBS-Studio (NOT!! OBS-VirtualCam) running
EDIT 2: I think I found the solution how to reproduce:
It always happens if you change the output scaled resolution of OBS.
Steps to reproduce:
- You open Jami and view another resolution of OBS-VirtualWebcam (/and or fps; you have to select other camera sources in Jami and select OBS-VirtualCam again so that it is displayed right) - for example 1020 x 576. (Note: You did NOT launch OBS-VirtualCam - so Jami only displays the blue preview image of OBS-VirtualCam: Example: https://www.bandicam.com/blog/wp-content/uploads/2021/08/zoom-obs-virtual-camera-1.jpg )
- Now exit Jami.
- Open OBS-Studio / or if OBS-Studio is already running go to settings: Change the output scaled resolution of OBS to for example 1360x768.
- After you apply the settings and launch OBS Virtual Cam
- Start Jami.
- Jami: Suddenly your account is lost.
@Mehdighayour @atraczyk @sblin Can you reproduce AND fix?
Edited by Elys
