Elv13
commented
7 years ago (edit: are you sure the ring-lrc is the work5 branch of my GitHub fork?)
I tried to reproduce a hundred time and it all worked. Before I create more VMs and start testing improbable causes, I would like you to attach (or email) me some debug logs. Anyway, if you are to report more issues, the logs are needed/helpful/save_time, so better start with this issue.
Whatever is different on your system isn't visible in the screenshot, so it will take a little more data to figure this one out. I guess if you show this screenshot, then it was a timeout. Otherwise it would have displayed a more relevant error message in red after a while. The bad thing about timeouts is that there is an endless way to get them, so it takes many logs to pinpoint the cause. Here's less or more what can cause a timeout:
To debug this, I need those logs:
The daemon and client logs
killall ring-kde
killall dring
killall dring
killall dring
# note that `export SIPLOGLEVEL=4` is required for some bugs, but not this one
$(find /usr -iname dring -type f) -c -d
# in another term
ring-kde(note that upstream disable debug by default, so systemd journalctl wont help)
The IPC log
sudo apt install bustle # many deps, I know
bustle
# do a capture
# save it
# grep to make sure no personal data got leaked, if yes, replace themPackets
I don't think this is relevant for this bug. So we can skip it.
Off topic
Also, here's a pedantic terminology note. Ring account cannot be called "local" or "global". A local account exists in Ring-KDE for something else (DNS based SIP LAN communications). Upstream calls what you call "global" "registered".
Registered and unregistered Ring accounts are 100% the same thing. Same protocol, same files, same handshake, same network, everything. Except that a registered one has been declared to a naming directory service to map the username to the public key. Beside that, unregistered account can call registered ones and vice-versa[1]. Registration is a layer on top of the account, not something about the account itself. Just saying that because you can test the video even if the registration failed.
Oh, and I fixed the white-on-white label bug. I use a dark color theme, I should have been more careful during testing.
[1] Using the ring:01234567890abcdef number at the bottom of the Ring-KDE client. That's your "phone number".
star-buck
shadeslayer
i always get this error (red error timeout) after a while when trying to register a new available global username:
Now my network works fine, and i have added a local account already, so not sure why it fails to have a global account.