savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-12-05T18:57:55Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1273Segfault - error 4 in libring.so.0.0.02022-12-05T18:57:55ZHenrik JohnsenSegfault - error 4 in libring.so.0.0.0Hi!
After installing jami-gnome via snap I encounter a software error.
When trying to enter the `Media` tab within the GUI, the app crashes.
Running `dmesg | grep jami` shows:
````
[ 2691.292322] audit: type=1400 audit(1631183195.431:5...Hi!
After installing jami-gnome via snap I encounter a software error.
When trying to enter the `Media` tab within the GUI, the app crashes.
Running `dmesg | grep jami` shows:
````
[ 2691.292322] audit: type=1400 audit(1631183195.431:529): apparmor="DENIED" operation="open" profile="snap.jami-gnome.jami" name="/run/mount/utab" pid=13596 comm="jami-gnome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 2693.972799] audit: type=1400 audit(1631183198.111:530): apparmor="DENIED" operation="open" profile="snap.jami-gnome.jami" name="/proc/zoneinfo" pid=13596 comm="PressureMonitor" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 2694.221005] audit: type=1400 audit(1631183198.359:531): apparmor="DENIED" operation="mknod" profile="snap.jami-gnome.jami" name=2F6465762F73686D2F736E61702E6A616D692E4A616D69204461656D6F6E5F73686D5F31333539365F30 pid=13596 comm="jami-gnome" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[ 2694.746037] jami-gnome[14102]: segfault at 0 ip 00007fd581e61c23 sp 00007fd4aaff97d0 error 4 in libring.so.0.0.0[7fd58185a000+18e7000]
````
There is a lot of apparmor=denied.
Relevant versions of software:
````
snap 2.51.7-1
snapd 2.51.7-1
series 16
kernel 5.10.0-kali9-amd64
snapd 2.51.4 12883 latest/stable canonical✓ snapd
jami-gnome 20210513.4.d69ac0a 1 latest/stable sfljami -
````
After running `jami-gnome.jami` in the terminal, following is displayed:
````
[1631189468.276|25359|upnp_context.cpp :1019 ] Mapping JAMI-UDP:20404 (on IGD http://192.168.1.1:1780/control?WANIPConnection [PUPNP]) successfully performed
[1631189468.350|25367|pupnp.cpp :1496 ] PUPnP: Sent request to open port JAMI-UDP:23868
[1631189468.350|25367|mapping.cpp :107 ] Changed mapping JAMI-UDP:23868 state from IN_PROGRESS to OPEN
[1631189468.350|25359|pupnp.cpp :666 ] PUPnP: Opened mapping JAMI-UDP:23868
[1631189468.350|25359|mapping.cpp :107 ] Changed mapping JAMI-UDP:23868 state from IN_PROGRESS to OPEN
[1631189468.350|25359|upnp_context.cpp :1019 ] Mapping JAMI-UDP:23868 (on IGD http://IP-REMOVED:1780/control?WANIPConnection [PUPNP]) successfully performed
[1631189469.830|25381|archive_account_manager.cpp:488 ] [Contacts] received device sync data (2 devices, 0 contacts)
[1631189482.688|25367|pupnp.cpp :341 ] PUPnP: Already have a valid IGD. Skip the search request
[1631189484.482|25255|manager.cpp :2379 ] Audio device already selected ; doing nothing.
[1631189484.482|25255|manager.cpp :2379 ] Audio device already selected ; doing nothing.
[1631189484.482|25255|manager.cpp :2379 ] Audio device already selected ; doing nothing.
(jami-gnome:25255): Gtk-WARNING **: 14:11:24.484: Theme parsing error: <data>:1:79: Not using units is deprecated. Assuming 'px'.
[1631189484.485|25255|video_input.cpp :521 ] MRL: 'camera://Apple_Inc._FaceTime_HD_Camera__Built-in__CCG8123032XH34FF8'
[1631189484.485|25255|audio_input.cpp :54 ] Creating audio input with id: audiolayer_id
[1631189484.485|25255|audio_input.cpp :274 ] Switching audio source to match ''
[1631189484.485|25255|audiostream.cpp :52 ] Record: Creating stream with device (44100Hz, 2 channels)
[1631189484.485|25481|sinkclient.cpp :279 ] SHMHolder ctor failure: ShmHolder[snap.jami.Jami Daemon_shm_25255_0]: shm_open failed, errno=13
[1631189484.485|25481|video_input.cpp :168 ] start sink failed
[1631189484.485|25481|video_input.cpp :170 ] VideoInput ready to capture
[1631189484.485|25255|audiostream.cpp :173 ] Stream is creating...
[1631189484.485|25481|media_decoder.cpp :133 ] Trying to open device /dev/video0 with format video4linux2, pixel format mjpeg, size 1024x576, rate 29.970000
[1631189484.487|25482|audio_input.cpp :76 ] Switching to default audio input
[1631189484.526|25377|audiostream.cpp :181 ] Stream successfully created, connected to alsa_input.pci-0000_00_1f.3.analog-stereo
[1631189484.526|25377|pulselayer.cpp :364 ] All streams ready, starting audio
[1631189484.647|25481|media_decoder.cpp :145 ] Using format video4linux2
[1631189484.975|25481|accel.cpp :206 ] -- Starting decoding init for cuda with default device.
[AVHWDeviceContext @ 0x7f7c14004e80] Cannot load libcuda.so.1
[AVHWDeviceContext @ 0x7f7c14004e80] Could not dynamically load CUDA
[1631189484.975|25481|accel.cpp :169 ] Failed to create cuda device: -1313558101.
[1631189484.975|25481|accel.cpp :219 ] -- Init failed for cuda with default device.
[1631189484.975|25481|accel.cpp :229 ] -- Init decoding for cuda with device 1.
[AVHWDeviceContext @ 0x7f7c14005ec0] Cannot load libcuda.so.1
[AVHWDeviceContext @ 0x7f7c14005ec0] Could not dynamically load CUDA
[1631189484.975|25481|accel.cpp :169 ] Failed to create cuda device: -1313558101.
[1631189484.975|25481|accel.cpp :238 ] -- Init failed for cuda with device 1.
[1631189484.975|25481|accel.cpp :229 ] -- Init decoding for cuda with device 2.
[AVHWDeviceContext @ 0x7f7c14006400] Cannot load libcuda.so.1
[AVHWDeviceContext @ 0x7f7c14006400] Could not dynamically load CUDA
[1631189484.975|25481|accel.cpp :169 ] Failed to create cuda device: -1313558101.
[1631189484.975|25481|accel.cpp :238 ] -- Init failed for cuda with device 2.
[1631189484.975|25481|media_decoder.cpp :495 ] Decoding video using MJPEG (Motion JPEG) (mjpeg)
[1631189484.975|25481|media_decoder.cpp :505 ] Not using hardware decoding for mjpeg
[1631189484.979|25481|video_input.cpp :337 ] created decoder with video params : size=1024X576, fps=29.970000 pix=yuvj422p
[1631189484.979|25481|sinkclient.cpp :429 ] Start sink <local / >, size=1024x576, mixer=0
Segmentation fault
````https://git.jami.net/savoirfairelinux/jami-project/-/issues/1297Jami snap crashes on Archlinux+snapd after fresh install2022-04-29T15:43:12ZPatrice LacoutureJami snap crashes on Archlinux+snapd after fresh installOn an Archlinux box updated on 2021-09-09, after a fresh install of the Jami snap package:
```
patricel@plamobile ~> snap list jami
Name Version Rev Tracking Publisher Notes
jami 20210601.2.891dad0 197 latest/sta...On an Archlinux box updated on 2021-09-09, after a fresh install of the Jami snap package:
```
patricel@plamobile ~> snap list jami
Name Version Rev Tracking Publisher Notes
jami 20210601.2.891dad0 197 latest/stable sfljami -
patricel@plamobile ~> snap version
snap 2.52-1
snapd 2.52-1
series 16
arch -
kernel 5.13.13-zen1-1-zen
```
The first and subsequent launches of the Jami snap fail with the following output:
```
patricel@plamobile ~> snap run jami
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...defaulting to using PulseAudio.
Gtk-Message: 10:42:43.697: Failed to load module "colorreload-gtk-module"
Gtk-Message: 10:42:43.702: Failed to load module "window-decorations-gtk-module"
(jami-qt:4177): dbind-WARNING **: 10:42:43.758: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-FSbEJk2mSR: No such file or directory
"notify server name: Plasma, vendor: KDE, version: 5.22.5, spec: 1.2"
[1631176964.528| 4177|ringbuffer.cpp :55 ] Create new RingBuffer audiolayer_id
[1631176964.533| 4177|video_device_monitor_impl.cpp:150 ] udev: adding device with id CNFGH19O203400010D72_Integrated_Webcam_HD
[1631176964.640| 4177|video_device.h :134 ] Default video settings: 960x540, 30 FPS
[1631176964.641| 4177|video_device_monitor_impl.cpp:150 ] udev: adding device with id CNFGH19O203400010D72_Integrated_Webcam_HD
[1631176964.664| 4177|manager.cpp :716 ] Not initialized
[1631176964.667| 4177|manager.cpp :716 ] Not initialized
10:42:44.699 os_core_unix.c !pjlib 2.10 for POSIX initialized
[1631176964.706| 4177|manager.cpp :788 ] Using PJSIP version 2.10 for x86_64-pc-linux-gnu
[1631176964.706| 4177|manager.cpp :789 ] Using GnuTLS version 3.7.1
[1631176964.706| 4177|manager.cpp :790 ] Using OpenDHT version 2.2.0
[1631176964.707| 4177|manager.cpp :791 ] Using FFmpeg version 4.0.0-2152-ge4eb13038
[1631176964.707| 4177|manager.cpp :794 ] Using Libgit2 version 1.1.0
[1631176964.707| 4177|sipvoiplink.cpp :651 ] Using SIP nameserver: 172.16.26.1
[1631176964.707| 4177|sipvoiplink.cpp :651 ] Using SIP nameserver: 172.16.26.2
[1631176964.707| 4177|sipvoiplink.cpp :746 ] SIPVoIPLink@0x55d2bf6dd640
[1631176964.707| 4400|sip_utils.cpp :251 ] Registered thread 0x7f6614ff7fa8 (0x1051)
[1631176964.708| 4177|manager.cpp :810 ] Configuration file path: /home/patricel/snap/jami/197/.config/jami/dring.yml
[1631176964.724| 4177|manager.cpp :3068 ] invalid node; first invalid key: "preferences": Preferences node unserialize error:
[1631176964.724| 4177|manager.cpp :483 ] Errors while parsing /home/patricel/snap/jami/197/.config/jami/dring.yml
[1631176964.725| 4177|manager.cpp :835 ] Restoring last working configuration
[1631176964.725| 4177|manager.cpp :3068 ] invalid node; first invalid key: "preferences": Preferences node unserialize error:
[1631176964.725| 4177|manager.cpp :483 ] Errors while parsing /home/patricel/snap/jami/197/.config/jami/dring.yml
[1631176964.725| 4177|ringbuffer.cpp :55 ] Create new RingBuffer urgentRingBuffer_id
[1631176964.745| 4177|pulselayer.cpp :141 ] Waiting....
[1631176964.746| 4401|pulselayer.cpp :141 ] Waiting....
[1631176964.746| 4401|pulselayer.cpp :141 ] Waiting....
[1631176964.750| 4401|pulselayer.cpp :145 ] Connection to PulseAudio server established
[1631176964.750| 4401|pulselayer.cpp :175 ] Updating PulseAudio sink list
[1631176964.750| 4401|pulselayer.cpp :192 ] Updating PulseAudio source list
[1631176964.750| 4401|pulselayer.cpp :209 ] Updating PulseAudio server infos
[1631176964.751| 4401|pulselayer.cpp :657 ] PulseAudio server info:
Server name: PulseAudio (on PipeWire 0.3.34)
Server version: 15.0.0
Default Sink alsa_output.pci-0000_00_1f.3.analog-stereo
Default Source alsa_input.pci-0000_00_1f.3.analog-stereo
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
[1631176964.751| 4401|audiolayer.cpp :64 ] Hardware audio format available : {s16, 2 channels, 48000Hz} 0
[1631176964.751| 4401|manager.cpp :2859 ] Audio format changed: {s16, 1 channels, 16000Hz} -> {s16, 2 channels, 48000Hz}
Daemon is running
No accounts to migrate
Screen saver dbus interface: "org.freedesktop.ScreenSaver"
QObject::connect(lrc::api::NewCallModel, Unknown): invalid nullptr parameter
QObject::connect(lrc::api::NewCallModel, PendingConferenceesListModel): invalid nullptr parameter
QObject::connect(lrc::api::NewCallModel, PendingConferenceesListModel): invalid nullptr parameter
QObject::connect(lrc::api::NewCallModel, PendingConferenceesListModel): invalid nullptr parameter
QObject::connect(lrc::api::NewCallModel, PendingConferenceesListModel): invalid nullptr parameter
Fontconfig warning: FcPattern object weight does not accept value [40 210)
fish: Job 1, 'snap run jami' terminated by signal SIGSEGV (Erreur de frontière d'adresse)
patricel@plamobile ~ [SIGSEGV]>
```
This was the first install of the Jami snap on this machine, and ~/snap/jami was empty before this install.
On the output above, the following lines are highlighted:
```
[1631176964.708| 4177|manager.cpp :810 ] Configuration file path: /home/patricel/snap/jami/197/.config/jami/dring.yml
[1631176964.724| 4177|manager.cpp :3068 ] invalid node; first invalid key: "preferences": Preferences node unserialize error:
[1631176964.724| 4177|manager.cpp :483 ] Errors while parsing /home/patricel/snap/jami/197/.config/jami/dring.yml
```
The file `/home/patricel/snap/jami/197/.config/jami/dring.yml` is empty (0 bytes).https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/519Dark mode issue on Jami-Qt2021-10-01T19:37:26ZMaxime CalletDark mode issue on Jami-Qt## Describe your environment
Please specify the following:
- Ring version: latest jami-qt internal build
- Device model: Ubuntu 20.04
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: a...## Describe your environment
Please specify the following:
- Ring version: latest jami-qt internal build
- Device model: Ubuntu 20.04
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Set dark mode
2. try to delete a synchronized device for an account with password
- Actual result: Wrong color scheme for dark mode
![dqrk_mode_bug](/uploads/2e2c048871add2111dd457425468ade6/dqrk_mode_bug.png)
- Expected result: Dark background color
## Additional informationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/991Dark mode issue on Jami-Qt2021-09-08T14:54:36ZMaxime CalletDark mode issue on Jami-Qt## Describe your environment
Please specify the following:
- Ring version: latest jami-qt internal build
- Device model: Ubuntu 20.04
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: a...## Describe your environment
Please specify the following:
- Ring version: latest jami-qt internal build
- Device model: Ubuntu 20.04
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Set dark mode
2. try to delete a synchronized device
- Actual result: Wrong color scheme for dark mode
![dqrk_mode_bug](/uploads/26951bb96824ed576904f1bad6c57a8f/dqrk_mode_bug.png)
- Expected result: Dark background color
## Additional informationhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/624Unable to revoke a device/remove a device from the list of linked devices2021-09-14T20:08:47ZovariUnable to revoke a device/remove a device from the list of linked devicesUnable to revoke a device.
client-android shows a message with title `Can't revoke device` with message `Unknown device.`
If the device is unknown, how can the device be removed from the list?
client-qt does not revoke the device and ...Unable to revoke a device.
client-android shows a message with title `Can't revoke device` with message `Unknown device.`
If the device is unknown, how can the device be removed from the list?
client-qt does not revoke the device and provides no feedback.
Can client-qt please show a message if it was unable to revoke a device like Android does?
Please advise if you need a screenshot from the Android device.
Thank you
client-andriod 20210812-01
Linux Mint 20.2 Cinnamon<br>
client-qt 202108172029Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/623AudioLayer - Deadlock between audio loop and main thread2021-09-13T17:02:45ZMohamed ChibaniAudioLayer - Deadlock between audio loop and main threadA deadlock may occur between the pulse audio thread and daemon main thread because of the lock inversion of callMutex_ (call class) and pa_threaded_mainloop private mutex. See backtrace in the comments.A deadlock may occur between the pulse audio thread and daemon main thread because of the lock inversion of callMutex_ (call class) and pa_threaded_mainloop private mutex. See backtrace in the comments.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/518`Incoming call answered with device: <deviceName>`2021-09-06T20:53:40Zovari`Incoming call answered with device: <deviceName>`When a device answers an incoming call where there are multiple linked devices online, all the devices which did not answer the call state, in Hungarian, `Nem fogadott bejövő hívás` (something like `Missed incoming call`). This is not re...When a device answers an incoming call where there are multiple linked devices online, all the devices which did not answer the call state, in Hungarian, `Nem fogadott bejövő hívás` (something like `Missed incoming call`). This is not really correct as the call was answered a different device.
When the call was answered on a linked device, could the devices which did not answer the call please state:
`Incoming call answered with device: <deviceName>`
If the `deviceName` has not been set, then fallback to the `deviceCode`, i.e.
`Incoming call answered with device: <deviceCode>`
This may help users as they won’t call people back when they look at there other device which states there `Missed incoming call` when they have answered the call on a different device.
This may help with synchronization across linked devices as an answered call on one devices can be linked to the unanswered call on the other devices.
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/517[Share screen] `Cancel` button and green box with larger thickness2022-05-21T00:48:05Zovari[Share screen] `Cancel` button and green box with larger thickness1. Should a `Cancel` button be added next to the `Share screen` button in the image below?<br>
![Share_screen_1_button](/uploads/dfe14b876c9f5988d4ab6cf704504478/Share_screen_1_button.png)
2. Should the green box around the `Screen 2` ha...1. Should a `Cancel` button be added next to the `Share screen` button in the image below?<br>
![Share_screen_1_button](/uploads/dfe14b876c9f5988d4ab6cf704504478/Share_screen_1_button.png)
2. Should the green box around the `Screen 2` have a larger thickness to enable it to be seen by people with vision impairment?
3. Should a `Cancel` button be added in the image below?<br>
![Share_screen_No_button](/uploads/6867ef19936a42a4ea72b48a0385d350/Share_screen_No_button.png)
4. In the image without the `Screen share` button, should a message be shown to select the screen to share?
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/622ICE/PJANTH - issue with nomination of triggered checks2021-09-08T21:12:16ZMohamed ChibaniICE/PJANTH - issue with nomination of triggered checksThere is an issue with the nomination of triggered checks in ICE that causes ICE negotiation to conclude on sub-optimal pairs.
The issue has been reported to PJSIP maintainers (https://github.com/pjsip/pjproject/issues/2812), and a patch...There is an issue with the nomination of triggered checks in ICE that causes ICE negotiation to conclude on sub-optimal pairs.
The issue has been reported to PJSIP maintainers (https://github.com/pjsip/pjproject/issues/2812), and a patch was provided.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/516[Screen share] Ending `screen share` should not start the `camera`2021-12-13T16:04:53Zovari[Screen share] Ending `screen share` should not start the `camera`1. Place an intercom audio call
2. Workaround for https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/499 (thanks to @sblin), click `Resume video`
3. Click `Share screen`
4. Select `Screen 2` (for 2 physical monitors)
5. Click ...1. Place an intercom audio call
2. Workaround for https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/499 (thanks to @sblin), click `Resume video`
3. Click `Share screen`
4. Select `Screen 2` (for 2 physical monitors)
5. Click `Share screen`
6. End screen share
Jami turns on the camera. Please do not turn on the camera automatically when the screen share is turned off.
Perhaps in the future, Jami can provide 2 video streams, i.e. a camera (or multiple cameras) and screen share (or multiple screen shares for multi-displays).
While it is understood that screen share and camera are both video, can turning off screen share please not start the camera.
If starting a camera should be default, could an option be added in the settings to start camera when screen share is ended, with the default setting being off.
What do you think?
Thank you
Linux Mint 20.2 Cinnamon<br>
client-qt Version: 202108261858 deb editionhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/107Jenkinsfile: commit/tag and publish source tarball for releases2022-02-01T20:52:56ZMaxim CournoyerJenkinsfile: commit/tag and publish source tarball for releasesThe Jenkinsfile must gain the following features before it can be used to publish official releases:
1. Commit/tag the release on the corresponding branch
2. Publish the release source tarballThe Jenkinsfile must gain the following features before it can be used to publish official releases:
1. Commit/tag the release on the corresponding branch
2. Publish the release source tarballhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1296Disable ICE by default2021-10-29T02:35:49ZBrightson JupiriDisable ICE by defaultIs there a config file where I changed the ICE Settings to Fall Back to SDP by default?Is there a config file where I changed the ICE Settings to Fall Back to SDP by default?https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/619SIPCall/ICE - Share unique ICE instance bettween subcalls2021-10-04T18:07:23ZMohamed ChibaniSIPCall/ICE - Share unique ICE instance bettween subcallsCurrently, when making an outgoing call to a Jami account with multiple registered devices, a new ice media instance is created for each subcall. This is not necessary, because all ice instances will be similar until the peer answers (an...Currently, when making an outgoing call to a Jami account with multiple registered devices, a new ice media instance is created for each subcall. This is not necessary, because all ice instances will be similar until the peer answers (and provide its candidates). But when the answer is received from the peer, all ice instances are destroyed except the instance of the successful subcall, which will be used to negotiate the media path.
Instead, only one instance should be created for the parent call, and shared amongst the attached subcalls.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/515`overwrite` always on. Please enable `insert` to be available too. Please ena...2021-09-02T03:26:18Zovari`overwrite` always on. Please enable `insert` to be available too. Please enable `overwrite`/`insert` to follow the current setting of the system.In the chat box:
1. write `morning`
2. press the `HOME` button
3. write `good `
Bug: The chat box shows `good ng` when it should show `good morning`
Are you able to reproduce and please fix?
Note 1: Typing this in LibreOffice Writer or...In the chat box:
1. write `morning`
2. press the `HOME` button
3. write `good `
Bug: The chat box shows `good ng` when it should show `good morning`
Are you able to reproduce and please fix?
Note 1: Typing this in LibreOffice Writer or the Firefox address bar produces `good morning`, indicating that `INS` (insert) is selected not `OVERWRITE`.
Note 2: If `OVERWRITE` is enabled, please enable Jami to then exhibit this behavior.
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/514Desktop sharing frame rate2021-12-03T16:49:57ZovariDesktop sharing frame rateJitsi Meet → `…` (More actions) → `Settings` → `More` → `Desktop sharing frame rate`
There is a drop-down with options:
* 5 frames per second
* 15 frames per second
* 30 frames per second
![image](/uploads/210d8471640235b78bc83df2c9482...Jitsi Meet → `…` (More actions) → `Settings` → `More` → `Desktop sharing frame rate`
There is a drop-down with options:
* 5 frames per second
* 15 frames per second
* 30 frames per second
![image](/uploads/210d8471640235b78bc83df2c9482aaf/image.png)
`Desktop sharing frame rate` could be called `Screen sharing frame rate`?
Can this feature be available as it could help with:
1. reducing data consumption
2. reducing video lag
https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/403
https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/375
https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/892
https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/922
What do you think?
Thank youJami for educationAndreas TraczykAline Gondim SantosAndreas Traczyk2021-11-09https://git.jami.net/savoirfairelinux/jami-project/-/issues/1295STUN server data in SIP account arbitrarily wiped2022-11-03T02:37:04ZAxel KirchSTUN server data in SIP account arbitrarily wiped**Client:** Jami v2.04 (20210601) “Maloya”
**OS:** macOS v11.5.2 Big Sur
I have two SIP accounts configured but they regularly go offline because the STUN server data gets reset for some reason after a while every time I enter it. What ...**Client:** Jami v2.04 (20210601) “Maloya”
**OS:** macOS v11.5.2 Big Sur
I have two SIP accounts configured but they regularly go offline because the STUN server data gets reset for some reason after a while every time I enter it. What can I do to help get to the bottom of the problem?https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/513[Screen share] Select an application `window` to share2021-09-01T20:25:09Zovari[Screen share] Select an application `window` to shareIn Jitsi Meet, you can share a `screen`. In addition you can also share an application `window`.
It is understood that OBS Studio can be used to share a `window`; however, from reading other issues, OBS has some user limitations such as...In Jitsi Meet, you can share a `screen`. In addition you can also share an application `window`.
It is understood that OBS Studio can be used to share a `window`; however, from reading other issues, OBS has some user limitations such as:
* lag issues
* requiring another piece of software to be installed
* not as user friendly as there are more steps to be done to share a window
Could Jami please also enable sharing an `application` window from the screen share button?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/511Issues with ending audio call (and dialpad)2021-12-16T20:50:20ZAmin BandaliIssues with ending audio call (and dialpad)Received via email:
```
I clicked right on the phone number I was calling
and it offered me "End Call". I clicked on that, and the call ended.
So far, so good.
I wanted to call the same number again, but the menu only offered me
"End ...Received via email:
```
I clicked right on the phone number I was calling
and it offered me "End Call". I clicked on that, and the call ended.
So far, so good.
I wanted to call the same number again, but the menu only offered me
"End Call". It remained that was as I tried several times. That was
frustrating.
Eventually I called a different number, hung up before it answered,
then tried the first number again. That time, it worked.
```
```
I had the dialpad displayed (Jami has a flaw that it won't
send touchtone tones unless the dialpad is displayed!)
and the other side hung up.
The window changed to show what it usually shows
when there is no call -- but that was grayed out
and the dialpad was still on top of it.
```
I believe @sblin tried to, but could not reproduce the isuse. I myself have not tried.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/509Problem adding default moderators2021-08-30T20:27:00ZMing Rui ZhangProblem adding default moderatorsContact list does not show anythingContact list does not show anythingMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/508Unable to `Edit device name` on Linux Mint 20.2 client-qt deb version2021-09-15T17:51:34ZovariUnable to `Edit device name` on Linux Mint 20.2 client-qt deb version1. Click `Open settings`
2. Click `Account`
3. In `Linked Devices`, click on the pencil to the right `Edit device name` (perhaps this should always be the first in the list?)
4. Change the name to `Linux Mint`
5. Click on the button to t...1. Click `Open settings`
2. Click `Account`
3. In `Linked Devices`, click on the pencil to the right `Edit device name` (perhaps this should always be the first in the list?)
4. Change the name to `Linux Mint`
5. Click on the button to the right `Save new device name`<br>
Looks like it is saved
6. Click `Close settings`
7. Click `Open settings`<br>
The device name is now what it was before being changed to `Linux Mint`
Also tried `LinuxMint`, i.e. without a space and that didn't work either.
Are you able to reproduce and please fix?
Thank you
Linux Mint 20.2 Cinnamon<br>
client-qt Version: 202108261858