jami-daemon issueshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues2024-03-08T19:26:14Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/5daemon: call goes to failure instead of over2024-03-08T19:26:14ZJami Botdaemon: call goes to failure instead of overIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>Steps to reproduce:</p>
<p>- make a call</p>
<p>- Bob hangs up</p>
<p>- Alice can go to Failure instead of Over (i...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>Steps to reproduce:</p>
<p>- make a call</p>
<p>- Bob hangs up</p>
<p>- Alice can go to Failure instead of Over (it does not happen every time I think)</p>
<p> </p>
<p>This is the log generated:</p>
<pre>
<strong>1457970175.894|0x70000021d000|tls\_session.cpp:638 ] [TLS] shutdown
1457970175.894|0x1019b7000|siptransport.cpp:209 ] pjsip transport@0x1031c4088 TLS to 208.88.110.46:7170 -> DISCONNECTED
1457970175.894|0x1019b7000|sipcall.cpp:205 ] call:12405873968647423475] Ending call because underlying SIP transport was closed
1457970175.894|0x1019b7000|call.cpp:144 ] [call:12405873968647423475] state change 1/4, cnx 4/0, code 54
1457970175.894|0x1019b7000|call.cpp:163 ] [call:12405873968647423475] emit client call state change FAILURE, code 54
1457970175.894|0x1019b7000|manager.cpp:1778 ] [call:12405873968647423475] Failed
1457970175.894|0x1019b7000|corelayer.cpp:226 ] START STREAM
1457970175.894|0x1019b7000|call\_factory.cpp:39 ] Removing call 12405873968647423475
1457970175.894|0x1019b7000|call\_factory.cpp:43 ] Remaining 0 SIP call(s)
1457970175.895|0x1019b7000|call.cpp:144 ] [call:12405873968647423475] state change 4/5, cnx 0/0, code 0
1457970175.895|0x1019b7000|call.cpp:163 ] [call:12405873968647423475] emit client call state change OVER, code 0</strong></pre>
<p>The problem seems to be in the daemon, it emits first a FAILURE state changed before a OVER. LRC puts the call in failed and does nothing when the OVER signal is received:</p>
<p>Log in LRC:</p>
<pre>
<strong>Call State Changed for call "12405873968647423475" . New state : "FAILURE"
Call found Call(0x6000002321e0) "Talking"
Calling stateChanged "FAILURE" -> 6 on call with state "Talking" . Become "Failed"
Call State Changed for call "12405873968647423475" . New state : "OVER"
Call found Call(0x6000002321e0) "Failed"
Origin and destination states are identical "Failed" "Failed" doing nothing Call(0x6000002321e0)
Calling stateChanged "OVER" -> 7 on call with state "Failed" . Become "Failed"
</strong></pre>Guillaume RoguezGuillaume Roguezhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/4Improve message engine API2024-03-08T19:26:14ZJami BotImprove message engine APIIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>- Current daemon API exposes message status as strings which causes a lot of string comparisons.</p>
<p>- change callback na...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>- Current daemon API exposes message status as strings which causes a lot of string comparisons.</p>
<p>- change callback name AccountMessageStatus -> AccountMessageStatusChanged, and add the account it's linked with and the uri it is send to.</p>
<p> </p>
<p>This changes will also impact LRC</p>https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/3remove IAX account and usage of libiax2024-03-08T19:26:14ZJami Botremove IAX account and usage of libiaxIssue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
libiax in current form has a licence not compatible with our GPLv3 licence.
As IAX account has not been updated and no more supp...Issue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
libiax in current form has a licence not compatible with our GPLv3 licence.
As IAX account has not been updated and no more support is done on it since first Ring release,
and there is no significant usage of it in the community, the Ring Team has decided to remove it from sources.
daemon, lrc and all clients are impacted by this ticket.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/9dtmf tones do not work2024-03-08T19:26:14ZJami Botdtmf tones do not workIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>A user reported that sending dtmf tones (SIP or RTP) does not work.<br />
<br />
I think RTP tones are broken in the daem...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>A user reported that sending dtmf tones (SIP or RTP) does not work.<br />
<br />
I think RTP tones are broken in the daemon since a while ago. Its also possible that SIP tones work, but are not accepted in all cases on the other end?</p>
<p>Also the gnome UI is not very nice for sending them, so could also be an input issue.</p>SIP support - first iterationSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/2ring-daemon fails to build with opendht 1.2.1 using clang2024-03-08T19:26:13ZJami Botring-daemon fails to build with opendht 1.2.1 using clangIssue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
I am getting these errors from clang-38 with both current ring-lrc and 1.0.0 ring-lrc:
```
In file included from configurationmanager.cpp:4...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
I am getting these errors from clang-38 with both current ring-lrc and 1.0.0 ring-lrc:
```
In file included from configurationmanager.cpp:40:
/usr/ports/net-im/ring-daemon/work/ring-daemon-56ec56f/src/ringdht/ringaccount.h:347:42: error: no member named 'Dht' in namespace 'dht'; did you mean 'dht'?
void saveNodes(const std::vector<dht::Dht::NodeExport>&) const;
\^\~\~\~\~\~\~\~
dht
/usr/local/include/opendht/default\_types.h:36:11: note: 'dht' declared here
namespace dht {
\^
In file included from configurationmanager.cpp:40:
/usr/ports/net-im/ring-daemon/work/ring-daemon-56ec56f/src/ringdht/ringaccount.h:348:43: error: no member named 'Dht' in namespace 'dht'; did you mean 'dht'?
void saveValues(const std::vector<dht::Dht::ValuesExport>&) const;
\^\~\~\~\~\~\~\~
dht
```
Spotted on FreeBSD.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/1daemon: account maintenance regression2024-03-08T19:26:13ZJami Botdaemon: account maintenance regressionIssue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
Migration/Maintenance system is broken: not able to recreate a new device if ring\_device.\* files missing (ex: filesystem corrupt...Issue generated from Tuleap's migration script.
**Originally submitted by: Guillaume Roguez (guillaume)**
Migration/Maintenance system is broken: not able to recreate a new device if ring\_device.\* files missing (ex: filesystem corruption).
Was tested on GNU/Linux-GNOME and Win32 platforms, using lasted sources.
I only indicate GNU/Linux-GNOME below.
\* Environment:
daemon: 1ed6a0f video: disable auto quality by default
lrc: 68c8ad0 AccountModel: separate selected and chosen account
gnome:
\* Reproduce steps:
- Create a new ring account
- stop ring
- delete ring\_device.\* files associated to this account
- restart ring
\* Expected result:
- the client ask for the password
- the client shows the normal screen after correct password given, with new ring device generated
\* Actual result:
- the client loops in password askingAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/28"Blob" class split for increased clarity2022-11-14T21:52:31ZJami Bot"Blob" class split for increased clarityIssue generated from Tuleap's migration script.
**Originally submitted by: Macony Gautradis (teamlog8430)**
The Account class is showing the first signs of becoming a monolithic "Blob" antipattern. Our solution is to split the "Blob" cl...Issue generated from Tuleap's migration script.
**Originally submitted by: Macony Gautradis (teamlog8430)**
The Account class is showing the first signs of becoming a monolithic "Blob" antipattern. Our solution is to split the "Blob" class into multiple separate subclasses, by issues, used to ease maintenance and upgrades of the code by separating relevant and linked methods into more descriptive subclasses. This initial work splits some functions of Account into the CodecContainer subclass.
The other modifications were made throughout the project to reflect the changes to Account. The makefile was updated to automake using our new class.
Here is a more thorough list of changes:
CHANGED FILES:
(all in daemon/)
MAJOR CHANGES:
src/account.h
src/account.cpp
description: Removed ALL codec-related functions, added CodecContainer class to
replace said functions,
added std::shared\_ptr<CodecContainer> codecContainer\_; and
std::shared\_ptr<CodecContainer> getCodecContainer(); definitions
Removed \#include "media\_codec.h" because it makes no sense to have
it here anymore
src/codeccontainer.h
src/codeccontainer.cpp
description: Created these two files and moved all codec-related code in
account.h/account.cpp to these respective files, creating
the CodecContainer class
in the process
Migrated code was cleaned up a bit - references to getSystemCodecContainer()
changed to already existing member systemCodecContainer\_
MINOR CHANGES:
src/Makefile.am
description: Updated automake makefile to compile the new codeccontainer.\* files
src/client/configurationmanager.cpp
description: Updated references to codec-calling functions
src/media/video/video\_sender.cpp
description: Added \#include "media\_codec.h" that was implicitly included in account.h
but removed due to codec separation
src/sip/sipaccount.cpp
description: Updated references to codec-calling functions
src/sip/sipcall.cpp
description: Updated references to codec-calling functions
src/sip/sipvoiplink.cpp
description: Updated references to codec-calling functions
src/ringdht/ringaccount.cpp
description: Updated references to codec-calling functions
\* Was only tested on Mint
[RingChanges.zip](/uploads/035972cc8864c9cbc735f2829d219685/RingChanges.zip)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/186SIP proxy field is not used correctly2020-12-13T23:57:25ZJami BotSIP proxy field is not used correctlyIssue generated from Tuleap's migration script.
**Originally submitted by: Raman Gupta (rocketraman)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Ring v1.0.0 on Linux Fedora 25 ...Issue generated from Tuleap's migration script.
**Originally submitted by: Raman Gupta (rocketraman)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
Ring v1.0.0 on Linux Fedora 25
\* Reproduce steps:
Using the hostname and proxy fields to connect to a domain mydomain.com and proxy server proxy.versature.com. The configuration should set up Ring to connect to proxy.versature.com, passing the mydomain.com in the subsequent SIP request(s).
\* Expected result:
I would expect ring to connect successfully using this configuration. As a point of comparison, Zoiper will connect successfully.
\* Actual result:
The actual result is that Ring attempts to make a SIP connection to the hostname, ignoring the proxy field. The debug logs at SIPLOGLEVEL=4 are:
```
[1496261573.159|18869|sipaccount.cpp:698 ] doRegister mydomain.com
[1496261573.159|18869|sipvoiplink.cpp:1220 ] try to resolve 'mydomain.com' (port: 0)
16:12:53.159 resolver.c Transmitting 38 bytes to NS 0 (127.0.0.1:53): DNS SRV query for \_sip.\_udp.mydomain.com: Success
16:12:53.190 \_sip.\_udp.redo DNS SRV resolution failed for \_sip.\_udp.mydomain.com: DNS "Name Error" (PJLIB\_UTIL\_EDNS\_NXDOMAIN)
16:12:53.190 \_sip.\_udp.redo DNS SRV resolution failed for \_sip.\_udp.mydomain.com, trying resolving A/AAAA record for mydomain.com
16:12:53.190 resolver.c Transmitting 28 bytes to NS 0 (127.0.0.1:53): DNS A query for mydomain.com: Success
16:12:53.190 resolver.c Transmitting 28 bytes to NS 0 (127.0.0.1:53): DNS AAAA query for mydomain.com: Success
[1496261573.220|18869|sipaccount.cpp:815 ] Creating transport
16:12:53.220 udp0x18cc530 SIP UDP transport started, published address is 192.168.1.6:5062
[1496261573.220|18869|siptransport.cpp:357 ] Created UDP transport on default : 0.0.0.0:5062
[1496261573.221|18869|siptransport.cpp:82 ] SipTransport@0x190acc0 {tr=0x1919ec8 {rc=2}}
[1496261573.221|18869|sip\_utils.cpp:87 ] Adding route proxy.versature.com
[1496261605.223|18869|sipaccount.cpp:1033 ] SIP registration failed, status=408 (Request Timeout)
[1496261605.223|18869|sipaccount.cpp:2018 ] Scheduling re-registration retry in 53 seconds..
[1496261658.316|18869|sip\_utils.cpp:87 ] Adding route proxy.versature.com
[1496261690.321|18869|sipaccount.cpp:1033 ] SIP registration failed, status=408 (Request Timeout)
[1496261690.321|18869|sipaccount.cpp:2018 ] Scheduling re-registration retry in 302 seconds..
```
IF the system is configured with \_sip.\_udp SRV records on the domain provided in the hostname to point to the proxy, and the proxy field is left blank, then Ring successfully looks up the SRV record and connects to the proxy given there. Explicitly providing the proxy does not work as shown above.
The way I think it should work (and the way I think Zoiper works) is that you have a "domain/hostname" [1] setting and a "proxy" setting. The logic would be:
1) If proxy is set, Ring connects to the proxy and then passes username@domain in the SIP header.
2) If proxy is not set, then Ring looks for the proxy in the DNS SRV records for domain and if it exists, Ring connects to it and then passes username@domain to it.
3) Lastly, if the DNS SRV record does not exist, Ring attempts to connect to the A record of the domain/hostname setting, and again passes username@domain to it.
That way the auth information is completely configurable (username + domain) and the server that handles the request is completely configurable (proxy). The server to physically connect to is configurable either by DNS record on the domain, OR by explicit configuration in the proxy field.
[1] The "domain/hostname" config value would replace the current "hostname" config value.
The codepath to make the SIP connection as described above already exists -- its just that its impossible to configure the UI currently to trigger it. Given an SRV record of \_sip.\_udp.mydomain.com pointing to proxy.versature.com port 5060, Ring makes a connection to proxy.versature.com and passes all information with domain @mydomain.com. Here is a trace https://pastebin.com/raw/5z39MRu8.Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/24Please support the current pjsip version2022-11-14T21:52:31ZJami BotPlease support the current pjsip versionIssue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Build with the current pjsip-2.6 fails with missing pjsip\_dlg\_create\_uas which is deprecated. You require pjsip-2.4. But this poses a proble...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Build with the current pjsip-2.6 fails with missing pjsip\_dlg\_create\_uas which is deprecated. You require pjsip-2.4. But this poses a problem for packaging systems because this requires the custom build and installation of older versions.
ring-daemon-2.2.0https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/316Support message edition/deletion2022-10-31T16:10:01ZJami BotSupport message edition/deletionbe able to edit/remove a message from a swarmbe able to edit/remove a message from a swarmSwarm-chatSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/26New Ring users from different timezone can't chat2022-11-14T21:52:31ZJami BotNew Ring users from different timezone can't chatIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
2 users from 2 timezones ...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
A detailed description of the bug. Use following fields for description field:
\* Environment:
2 users from 2 timezones
\* Reproduce steps:
1) create 1 ring account in Canada
2) create 1 ring account in France (or fake the timezone)
3) Try to send a chat message
\* Expected result:
1) Being able to chat
\* Actual result:
One of the peer will reject the other with a GNUTLS\_CERT\_NOT\_ACTIVATED error.Hugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/29Temporary IPv6 addresses can cause PJSIP to fail2022-11-14T21:52:31ZJami BotTemporary IPv6 addresses can cause PJSIP to failIssue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
\* Environment:
This problem seems to affect mostly GNU/Linux and macOS systems configured to change their iPv6 address often, a...Issue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
\* Environment:
This problem seems to affect mostly GNU/Linux and macOS systems configured to change their iPv6 address often, as a privacy measure. It would affect any platform that gathers a sufficient number of temporary IPv6 addresses.
\* Reproduce steps:
1. Register multiple IPv6 addresses:
A script used to generate those temporary IPv6 addresses can be found here: https://gitlab.savoirfairelinux.com/snippets/116
That script and the accompanying 'gen-random-ipv6.sh' should be placed in the same directory. The IFDEV and IPV6\_PREFIX should be adjusted to match your network device and IPv6 prefix, respectively. It is important that the IFDEV environment matches the \*currently\* used network interface if you have many, otherwise the problem will not be triggered.
Run the script like this: sudo ./add-ipv6-addresses.sh
2. Launch Ring and try to place a call.
\* Expected result:
The call should succeed.
\* Actual result (as seen in the daemon's debug output):
[1513801602.823|14926|ice\_transport.cpp :429 ] [ice:0x2fa48b0] initialization success
[1513801602.823|14926|ice\_transport.cpp :482 ] ICE as master
[1513801602.829|14926|ice\_transport.cpp :576 ] [ice:0x2fa48b0] (local) ufrag=2567c1bd, pwd=51e44a5d
[1513801602.829|12099|sipcall.cpp :776 ] [call:10040259774347710226] fill SDP with ICE transport 0x2d97040
dring: ../src/pjmedia/sdp.c:187: pjmedia\_sdp\_attr\_add: Assertion `\*count < (32\*2 + 4)' failed.
Abandon (core dumped)
A patch addressing the issue is in review here: https://gerrit-ring.savoirfairelinux.com/\#/c/8462/Next major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/25ring-daemon breaks: no member named 'raw\_chain' in 'pj\_ssl\_cert\_info'2022-11-14T21:52:31ZJami Botring-daemon breaks: no member named 'raw\_chain' in 'pj\_ssl\_cert\_info'Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Getting this in the FreeBSD port.
It also expects a missing symbol PJSIP\_TRANSPORT\_DTLS6.
You provide patches for pjsip. However, it isn'...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Getting this in the FreeBSD port.
It also expects a missing symbol PJSIP\_TRANSPORT\_DTLS6.
You provide patches for pjsip. However, it isn't easy to build pjsip. This is done by its own port. Ring port can't just easily repeat what the other port is doing.
Please merge your patches into the pjsip upstream, so that there will be no need to keep any patches.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/179[GNOME] Dialpad2021-03-10T17:54:39ZJami Bot[GNOME] DialpadIssue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
Please add a Dialpad which has numbers (0,1,2,3,4,5,6,7,8,9) and star/asterisk (\*) and hash (\#).
https://support.skype.com/en/faq/FA22/how...Issue generated from Tuleap's migration script.
**Originally submitted by: Óvári (ovari)**
Please add a Dialpad which has numbers (0,1,2,3,4,5,6,7,8,9) and star/asterisk (\*) and hash (\#).
https://support.skype.com/en/faq/FA22/how-do-i-dial-an-extension-during-a-call
Thank you
ring-gnome 2018-03-23 23:25:11 UTC
Linux Mint 18.3 Cinnamon 64-bitMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/6[GNOME] Sound applications should only show ‘Jami Daemon’ once and 'Unknown' ...2024-03-08T19:26:14Zovari[GNOME] Sound applications should only show ‘Jami Daemon’ once and 'Unknown' should be renamed 'Jami'Environment:<br>
Linux Mint 18.3 Cinnamon 3.6.7 64-bit
Reproduce steps:<br>
Make an Audio Call with Ring.
Expected result:<br>
In ‘System Settings’ → ‘Sound’ → ‘Applications’ tab, the ‘Ring Daemon’ should only show once.
Actual result...Environment:<br>
Linux Mint 18.3 Cinnamon 3.6.7 64-bit
Reproduce steps:<br>
Make an Audio Call with Ring.
Expected result:<br>
In ‘System Settings’ → ‘Sound’ → ‘Applications’ tab, the ‘Ring Daemon’ should only show once.
Actual result:<br>
In ‘System Settings’ → ‘Sound’ → ‘Applications’ tab, the ‘Ring Daemon’ shows twice. Please see attached image.
![RingDaemon](/uploads/4f2ea954c6a246cb3a0065473224c600/RingDaemon.png)
When Ring is not open:
```
$ ps aux | grep dring
ovari 4013 0.0 0.0 26708 948 pts/0 S+ 08:19 0:00 grep --color=auto dring
```
When Ring is open (no call has been made):
```
$ ps aux | grep dring
ovari 4029 12.2 1.6 1219232 31688 ? Sl 08:19 0:00 /usr/lib/ring/dring
ovari 4122 0.0 0.0 26708 1016 pts/0 S+ 08:19 0:00 grep --color=auto dring
```
Cross-reference:<br>
https://tuleap.ring.cx/plugins/tracker/?aid=1881
Thank youhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/7PIN should not contain confusing characters2024-03-08T19:26:14ZPhilippe GorleyPIN should not contain confusing charactersSome fonts can make '1' and 'I' or '0' and 'O' hard to tell apart. Ring should not generate a PIN with these characters.
These characters could be replaced with others (such as '-' or '_') to keep the entropy level.Some fonts can make '1' and 'I' or '0' and 'O' hard to tell apart. Ring should not generate a PIN with these characters.
These characters could be replaced with others (such as '-' or '_') to keep the entropy level.Adrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/8Invalid conversation state2024-03-08T19:26:14ZPierre DucheminInvalid conversation state## Environment
- Ring version: 20180511
- Device model: Nvidia Shield Pro, LG G3
- Android version: 7 (shield), 6 (LG)
- What build you are using: debug build on 636a065f603447f6c8472befd93c6b52e74ebfe3
## Steps to reproduce
-...## Environment
- Ring version: 20180511
- Device model: Nvidia Shield Pro, LG G3
- Android version: 7 (shield), 6 (LG)
- What build you are using: debug build on 636a065f603447f6c8472befd93c6b52e74ebfe3
## Steps to reproduce
- I reproduce the bug: at will
- Steps:
1. Call a contact that is only connected with an Android Phone device
2. The call is establishing
3. At the same time,
- on AndroidTV: hang up call
- on Android Phone: pick up call
- Actual result: on AndroidTV, everything is fine: the conversation hanged up and smartlist is displayed, but on the phone, a call is ongoing with a black screen instead of the video from the Shield. Video from phone displays normally on phone.
- Expected result: both devices should hang up.
## Additional information
Tried to reproduce the other way: phone calling TV, but everything went fine.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/10Crash when recording in full screen then recording2024-03-08T19:26:14ZAdministratorCrash when recording in full screen then recordingHow to reproduce:
1. Call someone
2. Set the call in fullscreen
3. Record
4. Hang up without stop recording
5. Re-call this person
6. Crash!
```
Thread 1 "lt-dring" received signal SIGSEGV, Segmentation fault.
ring::AudioReceiveThread::...How to reproduce:
1. Call someone
2. Set the call in fullscreen
3. Record
4. Hang up without stop recording
5. Re-call this person
6. Crash!
```
Thread 1 "lt-dring" received signal SIGSEGV, Segmentation fault.
ring::AudioReceiveThread::startRecorder (this=0x0, rec=std::shared_ptr<ring::MediaRecorder> (use count 1, weak count 0) = {...}) at audio_rtp_session.cpp:386
386 audioDecoder_->startRecorder(rec);
Missing separate debuginfos, use: dnf debuginfo-install alsa-lib-1.1.6-2.fc28.x86_64 alsa-plugins-pulseaudio-1.1.6-3.fc28.x86_64 bzip2-libs-1.0.6-26.fc28.x86_64 dbus-libs-1.12.8-1.fc28.x86_64 flac-libs-1.3.2-7.fc28.x86_64 gmp-6.1.2-7.fc28.x86_64 gnutls-3.6.2-1.fc28.x86_64 gsm-1.0.17-5.fc28.x86_64 jsoncpp-1.8.4-3.fc28.x86_64 libICE-1.0.9-12.fc28.x86_64 libSM-1.2.2-8.fc28.x86_64 libX11-1.6.5-7.fc28.x86_64 libX11-xcb-1.6.5-7.fc28.x86_64 libXau-1.0.8-11.fc28.x86_64 libXext-1.3.3-8.fc28.x86_64 libXfixes-5.0.3-5.fc28.x86_64 libXi-1.7.9-6.fc28.x86_64 libXtst-1.2.3-5.fc28.x86_64 libasyncns-0.8-14.fc28.x86_64 libblkid-2.32-2.fc28.x86_64 libcap-2.25-9.fc28.x86_64 libdrm-2.4.92-1.fc28.x86_64 libffi-3.1-16.fc28.x86_64 libgcc-8.1.1-1.fc28.x86_64 libgcrypt-1.8.2-2.fc28.x86_64 libgpg-error-1.29-1.fc28.x86_64 libidn2-2.0.5-1.fc28.x86_64 libmount-2.32-2.fc28.x86_64 libogg-1.3.2-10.fc28.x86_64 libpciaccess-0.13.4-8.fc28.x86_64 libsamplerate-0.1.9-1.fc28.x86_64 libselinux-2.7-13.fc28.x86_64 libsndfile-1.0.28-7.fc28.x86_64 libstdc++-8.1.1-1.fc28.x86_64 libtasn1-4.13-2.fc28.x86_64 libunistring-0.9.9-1.fc28.x86_64 libuuid-2.32-2.fc28.x86_64 libva-2.1.0-1.fc28.x86_64 libva-intel-driver-2.1.0-2.fc28.x86_64 libvdpau-1.1.1-7.fc28.x86_64 libvorbis-1.3.6-1.fc28.x86_64 libxcb-1.13-1.fc28.x86_64 lz4-libs-1.8.1.2-4.fc28.x86_64 nettle-3.4-2.fc28.x86_64 nss-mdns-0.14.1-1.fc28.x86_64 openssl-libs-1.1.0h-3.fc28.x86_64 opus-1.3-0.4.beta.fc28.x86_64 p11-kit-0.23.10-1.fc28.x86_64 pcre-8.42-1.fc28.x86_64 pcre2-10.31-4.fc28.x86_64 pulseaudio-libs-11.1-18.fc28.1.x86_64 speex-1.2.0-1.fc28.x86_64 speexdsp-1.2-0.13.rc3.fc28.x86_64 systemd-libs-238-8.git0e0aa59.fc28.x86_64 xz-libs-5.2.4-2.fc28.x86_64 yaml-cpp-0.6.1-2.fc28.x86_64 zlib-1.2.11-8.fc28.x86_64
(gdb) bt
#0 ring::AudioReceiveThread::startRecorder (this=0x0, rec=std::shared_ptr<ring::MediaRecorder> (use count 1, weak count 0) = {...}) at audio_rtp_session.cpp:386
#1 0x00007ffff69f4538 in ring::AudioRtpSession::startRecorder (this=0x2632100, rec=std::shared_ptr<ring::MediaRecorder> (use count 1, weak count 0) = {...}) at audio_rtp_session.cpp:520
#2 0x00007ffff69bde46 in ring::SIPCall::toggleRecording (this=0x7fffc00b72b0) at sipcall.cpp:1157
#3 0x00007ffff69580dc in ring::Manager::toggleRecordingCall(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () at manager.cpp:2408
#4 0x0000000000436954 in DBusCallManager::toggleRecording (callID="17475899643809895462", this=<optimized out>) at dbuscallmanager.cpp:219
#5 cx::ring::Ring::CallManager_adaptor::_toggleRecording_stub (this=0x6c8080, call=...) at dbuscallmanager.adaptor.h:997
#6 0x0000000000435fb7 in DBus::Callback<cx::ring::Ring::CallManager_adaptor, DBus::Message, DBus::CallMessage const&>::call (this=<optimized out>, param=...) at /home/AmarOk/Projets/ring-project/daemon/contrib/x86_64-redhat-linux/include/dbus-c++-1/dbus-c++/util.h:281
#7 0x0000000000458f1e in DBus::Slot<DBus::Message, DBus::CallMessage const&>::call(DBus::CallMessage const&) const ()
#8 0x0000000000457fd9 in DBus::InterfaceAdaptor::dispatch_method(DBus::CallMessage const&) ()
#9 0x0000000000460f0c in DBus::ObjectAdaptor::handle_message(DBus::Message const&) ()
#10 0x00000000004605a1 in DBus::ObjectAdaptor::Private::message_function_stub(DBusConnection*, DBusMessage*, void*) ()
#11 0x00007ffff7babeb8 in ?? () from /lib64/libdbus-1.so.3
#12 0x00007ffff7b9c604 in dbus_connection_dispatch () from /lib64/libdbus-1.so.3
#13 0x000000000044f2e6 in DBus::Connection::Private::do_dispatch() ()
#14 0x0000000000452872 in DBus::Dispatcher::dispatch_pending(std::__cxx11::list<DBus::Connection::Private*, std::allocator<DBus::Connection::Private*> >&) ()
#15 0x00000000004526a2 in DBus::Dispatcher::dispatch_pending() ()
#16 0x00000000004564d8 in DBus::BusDispatcher::do_iteration() ()
#17 0x000000000045620b in DBus::BusDispatcher::enter() ()
#18 0x000000000041bf2f in DBusClient::event_loop() () at dbusclient.cpp:250
#19 0x000000000041b719 in main () at main.cpp:236
#20 0x00007ffff101d18b in __libc_start_main () from /lib64/libc.so.6
#21 0x000000000041ba0a in _start () at main.cpp:241
```https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/11[GNOME] Camera2024-03-08T19:26:15Zovari[GNOME] CameraGNU Ring "In varietate concordia" built on 2018-06-08 16:34:45 UTC.
1. Settings → Media → Camera Setting → Device: →<br>
Synaptics RMI4 Touch Sensor<br>
HP Truevision HD: HP Truevision
Should the first option “Synaptics RMI4 Touch Sens...GNU Ring "In varietate concordia" built on 2018-06-08 16:34:45 UTC.
1. Settings → Media → Camera Setting → Device: →<br>
Synaptics RMI4 Touch Sensor<br>
HP Truevision HD: HP Truevision
Should the first option “Synaptics RMI4 Touch Sensor” be showing? It does not seem to be a camera?
Thank you
![Camera](/uploads/0d024bdb38214a91914d5b1c50ab6561/Camera.png)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/12[GNOME] Small screen (eg. 5 inch)2024-03-08T19:26:15Zovari[GNOME] Small screen (eg. 5 inch)GNU Ring "In varietate concordia" built on 2018-06-08 16:34:45 UTC.
# Notifications
Please enable the notifications, i.e. icons and descriptions, to extend to both sides of the messaging area. Thank you
![SmallScreen](/uploads/df12410...GNU Ring "In varietate concordia" built on 2018-06-08 16:34:45 UTC.
# Notifications
Please enable the notifications, i.e. icons and descriptions, to extend to both sides of the messaging area. Thank you
![SmallScreen](/uploads/df124105326accaf4db0edaa2f959196/SmallScreen.png)
# Settings
Please enable the Settings to be narrower. Image below shows the smallest width. Thank you
![Settings](/uploads/8a99f7161ea46742bb84ab1f595c806f/Settings.png)Sébastien BlinSébastien Blin