jami-client-gnome issueshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues2021-06-10T16:33:20Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1267Cannot create account: bignum-random-prime.c:345: nettle generate pocklington...2021-06-10T16:33:20ZJanice JaniceCannot create account: bignum-random-prime.c:345: nettle generate pocklington prime: Assertion bits > p0_bits failedBug report form
---------------
## OS
Linux Flatpak v20210426.1.5597275e
## Jami daemon version:
built on 2021-04-30 14:31:08 UTC
## Where did you get Jami?
<!-- (add an x in between the square brackets to select an option) -->
- ...Bug report form
---------------
## OS
Linux Flatpak v20210426.1.5597275e
## Jami daemon version:
built on 2021-04-30 14:31:08 UTC
## Where did you get Jami?
<!-- (add an x in between the square brackets to select an option) -->
- [ ] My OS package manager (e.g. apt, yum, pacman)
- [ ] I downloaded it from jami.net
- [ ] I built it from source using the make-ring.py script
- [X] I built it from source manually or other (please explain):
Flathub.org
https://flathub.org/apps/details/net.jami.Jami
## Steps to reproduce bug
<!-- The better your scenario is, the better we will be able to help
you. Please try to describe only one bug here. Open multiple issues
for multiple bugs -->
Steps:
1. Start Jami
2. Create Jami account or rendezvous poing
3. Enter information.
4. Click Next button.
## What happens instead:
Jami application crashes.
## Logs
jami-gnome: bignum-random-prime.c:345: _nettle_generate_pocklington_prime: Assertion bits > p0_bits’ failed.`https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1266[libwrap] Show advanced information overlay: FPS for myself (You) stuck at 0....2023-05-26T13:59:18ZMaxim Cournoyer[libwrap] Show advanced information overlay: FPS for myself (You) stuck at 0.000000Bug report form
---------------
## OS
Guix System
## Jami daemon version:
20211223.2.37be4c3
## Jami GNOME client version:
20211223.2.37be4c3
## Where did you get Jami?
GNU Guix, commit 175915bb4417e198f6b500901dcef710a0011be9.
...Bug report form
---------------
## OS
Guix System
## Jami daemon version:
20211223.2.37be4c3
## Jami GNOME client version:
20211223.2.37be4c3
## Where did you get Jami?
GNU Guix, commit 175915bb4417e198f6b500901dcef710a0011be9.
## Steps to reproduce bug
Steps:
1. Place a video call.
2. Right click, select "Show advanced information".
## What you expect to happen:
Advanced information overlay is shown correctly.
## What happens instead:
The FPS count for You appears static at 0.000000.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1265Frequent crashes on video recording (clutter, cogl)2022-01-14T17:27:59ZMaxim CournoyerFrequent crashes on video recording (clutter, cogl)## OS
GNU Guix, commit fa43419a0ffef8f6da3663a5953946762b2e6665 + 1 commit to build the libringclient (LRC) package with `-DLIBWRAP=true`.
## Jami daemon version:
```
$ guix show libringclient
name: libring
version: 20210606.1.e2f9490...## OS
GNU Guix, commit fa43419a0ffef8f6da3663a5953946762b2e6665 + 1 commit to build the libringclient (LRC) package with `-DLIBWRAP=true`.
## Jami daemon version:
```
$ guix show libringclient
name: libring
version: 20210606.1.e2f9490
outputs: out debug
systems: x86_64-linux
dependencies: alsa-lib@1.2.4 asio@1.18.1 autoconf@2.69 automake@1.16.2 dbus-c++@0.9.0 eudev@3.2.9
+ ffmpeg-jami@4.4 gcc@8.5.0 jack@0.125.0 jsoncpp@1.9.2 libarchive@3.4.2 libgit2@1.1.0 libnatpmp@20150609
+ libsecp256k1@20200615-1.dbd41db libtool@2.4.6 libupnp@1.14.7 opendht@2.2.0rc7-1.c8a0b44 openssl@1.1.1j
+ perl@5.30.2 pjproject-jami@2.10 pkg-config@0.29.2 pulseaudio@14.0 speex@1.2.0 speexdsp@1.2.0
+ webrtc-audio-processing@0.3.1 which@2.21 yaml-cpp@0.6.3
```
## Jami GNOME client version:
```
$ guix show jami-gnome
name: jami-gnome
version: 20210606.1.e2f9490
outputs: out debug
systems: x86_64-linux
dependencies: adwaita-icon-theme@3.34.3 clutter-gtk@1.8.4 clutter@1.26.2 gettext-minimal@0.20.1
+ glib@2.62.6 gtk+@3.24.24 libappindicator@12.10.0 libcanberra@0.30 libnotify@0.7.9
+ libring@20210606.1.e2f9490 libringclient@20210606.1.e2f9490 network-manager@1.24.0 pkg-config@0.29.2
+ qrencode@4.1.1 sqlite@3.31.1 webkitgtk@2.32.1
[...]
```
## Where did you get Jami?
GNU Guix
## Steps to reproduce bug
Steps:
1. Place a video call.
2. Start recording.
## What you expect to happen:
Recording proceeds and upon completion a video file is saved.
## What happens instead:
A segfault. See backtrace below.
## Logs
```
[...]
"slotCallStateChanged (call: 8487520819298161), from Calling to Talking"
[1623168714.021|31613|manager.cpp :2154 ] [call:8487520819298161] Peer answered
[1623168714.021|31613|manager.cpp :1817 ] Add audio to call 8487520819298161
[1623168714.021|31613|manager.cpp :1830 ] [call:8487520819298161] Attach audio
[1623168714.021|31613|ringbufferpool.cpp:174 ] Bind call 8487520819298161 to call audiolayer_id
[1623168714.021|31613|ringbufferpool.cpp:155 ] Bind rbuf '8487520819298161' to callid 'audiolayer_id'
[1623168714.021|31613|ringbufferpool.cpp:155 ] Bind rbuf 'audiolayer_id' to callid '8487520819298161'
[1623168714.021|31613|audiostream.cpp :52 ] Playback: Creating stream with device (44100Hz, 2 channels)
[1623168714.021|31613|audiostream.cpp :173 ] Stream is creating...
[1623168714.022|31613|sipcall.cpp :1355 ] [call:4330930242882059] removeCall()
[1623168714.022|31613|call_factory.cpp :89 ] Removing call 4330930242882059
[1623168714.022|31613|call_factory.cpp :92 ] Remaining 1 call
[1623168714.022|31613|call.cpp :250 ] [call:4330930242882059] state change 1/6, cnx 4/4, code 0
[1623168714.022|31632|audiostream.cpp :181 ] Stream successfully created, connected to alsa_output.pci-0000_00_1b.0.analog-stereo
[1623168714.022|31632|pulselayer.cpp :364 ] All streams ready, starting audio
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:54.061: unwatch_fast: "/net/jami/JamiGnome/" (active: 8, establishing: 0)
(.jami-gnome-real:31601): GLib-DEBUG: 12:11:54.064: posix_spawn avoided (child_setup specified)
[Detaching after fork from child process 31749]
[1623168714.095|31748|ice_transport.cpp :571 ] [ice:0x7fff64329970] UDP negotiation success
[1623168714.096|31748|ice_transport.cpp :603 ] [ice:0x7fff64329970] UDP connection pairs ([comp id] local [type] <-> remote [type]):
[1] 192.168.10.15:32892 [host] <-> 192.168.10.185:37956 [host]
[2] 192.168.10.15:40763 [host] <-> 192.168.10.185:40086 [host]
[1] 192.168.10.15:32892 [host] <-> 192.168.10.185:37956 [host]
[2] 192.168.10.15:40763 [host] <-> 192.168.10.185:40086 [host]
[1623168714.099|31613|sipcall.cpp :1795 ] [call:8487520819298161] stopping all medias
[1623168714.100|31613|sipcall.cpp :1650 ] [call:8487520819298161] startAllMedia()
[1623168714.103|31613|audio_rtp_session.cpp:73 ] Start audio RTP sender: input [camera://046d_HD_Pro_Webcam_C920_79D3DE2F] - muted [NO]
[1623168714.104|31613|audio_input.cpp :54 ] Creating audio input with id: 8487520819298161
[1623168714.104|31613|audio_input.cpp :387 ] Audio Input muted [NO]
[1623168714.104|31613|audio_input.cpp :274 ] Switching audio source to match 'camera://046d_HD_Pro_Webcam_C920_79D3DE2F'
[1623168714.105|31613|audiostream.cpp :52 ] Record: Creating stream with device (44100Hz, 2 channels)
[1623168714.106|31613|audiostream.cpp :173 ] Stream is creating...
(.jami-gnome-real:31601): Gtk-WARNING **: 12:11:54.109: Theme parsing error: <data>:1:79: Not using units is deprecated. Assuming 'px'.
[New Thread 0x7ffeee74f700 (LWP 31750)]
[1623168714.111|31750|audio_input.cpp :78 ] Switching audio input to '046d_HD_Pro_Webcam_C920_79D3DE2F'
[1623168714.111|31613|audio_sender.cpp :67 ] audioEncoder_->openOutput rtp://192.168.10.185:23210
[1623168714.111|31613|media_encoder.cpp :273 ] QObject::connect: No such signal CallManagerInterface::SmartInfo(MapStringString)
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:54.128: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 7)
** (.jami-gnome-real:31601): DEBUG: 12:11:54.128: call has status Talking, hiding
Not using hardware encoding for opus
[1623168714.153|31613|media_encoder.cpp :547 ] [libopus] Using 4 threads
[1623168714.153|31613|media_encoder.cpp :597 ] [libopus] Frame size 960
[libopus @ 0x7fff9c123880] No bit rate set. Defaulting to 96000 bps.
[New Thread 0x7ffeedf4e700 (LWP 31751)]
[New Thread 0x7ffeed74d700 (LWP 31752)]
[1623168714.154|31613|video_rtp_session.cpp:101 ] Start video RTP sender: input [camera://046d_HD_Pro_Webcam_C920_79D3DE2F] - muted [NO]
[1623168714.154|31613|video_input.cpp :521 ] MRL: 'camera://046d_HD_Pro_Webcam_C920_79D3DE2F'
[1623168714.155|31752|media_decoder.cpp :133 ] Trying to open device dummyFilename with format sdp, pixel format , size 0x0, rate 0.000000
[New Thread 0x7ffeecf4c700 (LWP 31753)]
[1623168714.155|31752|media_decoder.cpp :145 ] Using format sdp
[1623168714.155|31753|sinkclient.cpp :191 ] ShmHolder[Jami Daemon_shm_31601_0]: new sizes: f=0, a=103
[1623168714.155|31753|sinkclient.cpp :158 ] ShmHolder: new holder 'Jami Daemon_shm_31601_0'
[1623168714.155|31753|video_input.cpp :170 ] VideoInput ready to capture
[1623168714.155|31753|media_decoder.cpp :133 ] Trying to open device /dev/video0 with format video4linux2, pixel format mjpeg, size 1280x720, rate 30.000000
[New Thread 0x7ffeec74b700 (LWP 31754)]
[New Thread 0x7ffeebf4a700 (LWP 31755)]
[1623168714.161|31755|media_decoder.cpp :133 ] Trying to open device dummyFilename with format sdp, pixel format , size 0x0, rate 0.000000
[1623168714.161|31755|media_decoder.cpp :145 ] Using format sdp
[1623168714.210|31632|audiostream.cpp :163 ] Stream 661 to alsa_output.pci-0000_00_1b.0.analog-stereo.echo-cancel
[1623168714.210|31632|audiostream.cpp :181 ] Stream successfully created, connected to alsa_input.pci-0000_00_1b.0.analog-stereo.echo-cancel
[1623168714.210|31632|pulselayer.cpp :364 ] All streams ready, starting audio
[1623168714.210|31632|pulselayer.cpp :192 ] Updating PulseAudio source list
[1623168714.210|31632|pulselayer.cpp :209 ] Updating PulseAudio server infos
[New Thread 0x7fff927fc700 (LWP 31757)]
[1623168714.211|31632|pulselayer.cpp :175 ] Updating PulseAudio sink list
[1623168714.212|31632|pulselayer.cpp :657 ] PulseAudio server info:
Server name: pulseaudio
Server version: 14.0
Default Sink alsa_output.pci-0000_00_1b.0.analog-stereo.echo-cancel
Default Source alsa_input.pci-0000_00_1b.0.analog-stereo
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
[1623168714.212|31632|audiolayer.cpp :64 ] Hardware audio format available : {s16, 2 channels, 44100Hz} 0
[Thread 0x7fff927fc700 (LWP 31757) exited]
[1623168714.288|31750|sip_utils.cpp :251 ] Registered thread 0x7ffeee74e028 (0x7B71)
[1623168714.312|31747|sipvoiplink.cpp :1295 ] [INVITE:0x7fff9c0e5628] RX SIP method 6 (MESSAGE)
** (.jami-gnome-real:31601): DEBUG: 12:11:54.391: call has status Talking, hiding
[1623168714.399|31753|media_decoder.cpp :145 ] Using format video4linux2
[1623168714.508|31753|media_decoder.cpp :495 ] Decoding video using MJPEG (Motion JPEG) (mjpeg)
[1623168714.509|31753|media_decoder.cpp :505 ] Not using hardware decoding for mjpeg
[1623168714.521|31752|media_decoder.cpp :495 ] Decoding audio using Opus (opus)
[1623168714.521|31752|media_decoder.cpp :505 ] Not using hardware decoding for opus
[1623168714.527|31753|sinkclient.cpp :429 ] Start sink <local / Jami Daemon_shm_31601_0>, size=1280x720, mixer=0
[1623168714.527|31753|sinkclient.cpp :191 ] ShmHolder[Jami Daemon_shm_31601_0]: new sizes: f=3686400, a=7372903
[1623168714.533|31613|sipcall.cpp :1317 ] Sending device orientation via SIP INFO
[1623168714.533|31753|media_encoder.cpp :273 ] Not using hardware encoding for h264
[1623168714.533|31753|media_encoder.cpp :734 ] Hardware encoding disabled
[1623168714.534|31753|media_encoder.cpp :547 ] [libx264] Using 4 threads
[1623168714.534|31753|media_encoder.cpp :876 ] H264 encoder setup: crf=33, maxrate=800 kbit/s, bufsize=400 kbit
[libx264 @ 0x7fffcc202200] frame MB size (80x45) > level limit (396)
[libx264 @ 0x7fffcc202200] DPB size (1 frames, 3600 mbs) > level limit (0 frames, 2376 mbs)
[libx264 @ 0x7fffcc202200] MB rate (108000) > level limit (11880)
[New Thread 0x7ffee7d46700 (LWP 31761)]
[New Thread 0x7ffee7545700 (LWP 31762)]
[New Thread 0x7ffee6d44700 (LWP 31763)]
[New Thread 0x7ffee6543700 (LWP 31764)]
[New Thread 0x7ffee5d42700 (LWP 31765)]
[New Thread 0x7ffee5541700 (LWP 31766)]
[New Thread 0x7ffee4d40700 (LWP 31767)]
[New Thread 0x7ffee453f700 (LWP 31768)]
[1623168714.609|31753|sip_utils.cpp :251 ] Registered thread 0x7ffeecf4b028 (0x7B71)
[1623168714.610|31753|video_input.cpp :337 ] created decoder with video params : size=1280X720, fps=30.000000 pix=yuvj422p
[1623168714.610|31753|sinkclient.cpp :429 ] Start sink <local / Jami Daemon_shm_31601_0>, size=1280x720, mixer=0
** (.jami-gnome-real:31601): DEBUG: 12:11:54.676: Inhibition was activated.
vCard image loading failed
[New Thread 0x7ffee3d3e700 (LWP 31769)]
[New Thread 0x7ffee353d700 (LWP 31770)]
[Thread 0x7fff3bfff700 (LWP 31721) exited]
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:55.103: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 8)
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:55.103: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:55.104: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:55.104: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:55.104: change_notify: /net/jami/JamiGnome/window-height
[1623168715.312|31754|media_encoder.cpp :876 ] H264 encoder setup: crf=33, maxrate=839 kbit/s, bufsize=419 kbit
[1623168715.407|31747|sipvoiplink.cpp :1295 ] [INVITE:0x7fff9c0e5628] RX SIP method 6 (INFO)
[1623168715.409|31747|sipvoiplink.cpp :1141 ] Rotate video 90 deg.
[1623168715.441|31755|sip_utils.cpp :251 ] Registered thread 0x7ffeebf49028 (0x7B71)
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:55.632: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:55.632: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:55.632: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:55.633: change_notify: /net/jami/JamiGnome/window-height
[1623168715.889|31755|accel.cpp :206 ] -- Starting decoding init for vaapi with default device.
[New Thread 0x7fff3bfff700 (LWP 31774)]
[New Thread 0x7ffef17d4700 (LWP 31775)]
[New Thread 0x7ffef0fd3700 (LWP 31776)]
[New Thread 0x7ffee1f3c700 (LWP 31777)]
[1623168716.126|31755|accel.cpp :180 ] Device type vaapi successfully created.
[1623168716.126|31755|accel.cpp :213 ] -- Init passed for vaapi with default device.
[1623168716.128|31755|media_decoder.cpp :488 ] Using hardware decoding for h264 with vaapi
[1623168716.128|31755|media_decoder.cpp :495 ] Decoding video using H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (h264)
[1623168716.128|31755|sinkclient.cpp :191 ] ShmHolder[Jami Daemon_shm_31601_1]: new sizes: f=0, a=103
[1623168716.128|31755|sinkclient.cpp :158 ] ShmHolder: new holder 'Jami Daemon_shm_31601_1'
[1623168716.128|31755|sinkclient.cpp :429 ] Start sink <8487520819298161 / Jami Daemon_shm_31601_1>, size=640x480, mixer=0
[1623168716.128|31755|accel.cpp :151 ] Found compatible hardware format for h264 decoder with vaapi
[h264 @ 0x7fffd81d9640] No support for codec h264 profile 66.
[h264 @ 0x7fffd81d9640] Failed setup for format vaapi_vld: hwaccel initialisation returned error.
[h264 @ 0x7fffd81d9640] decode_slice_header error
[h264 @ 0x7fffd81d9640] no frame!
[1623168716.129|31755|media_decoder.cpp :567 ] Decoding error falling back to software
[1623168716.177|31755|media_decoder.cpp :495 ] Decoding video using H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (h264)
[1623168716.177|31755|media_decoder.cpp :505 ] Not using hardware decoding for h264
[Thread 0x7ffee1f3c700 (LWP 31777) exited]
[Thread 0x7ffef0fd3700 (LWP 31776) exited]
[Thread 0x7ffef17d4700 (LWP 31775) exited]
[Thread 0x7fff3bfff700 (LWP 31774) exited]
[New Thread 0x7ffee1f3c700 (LWP 31778)]
[New Thread 0x7ffef0fd3700 (LWP 31779)]
[1623168716.183|31613|sipcall.cpp :597 ] Sending video keyframe request via SIP INFO
[New Thread 0x7ffef17d4700 (LWP 31780)]
[1623168716.195|31755|filter_transpose.cpp:31 ] Rotation set to 90
[New Thread 0x7fff3bfff700 (LWP 31782)]
[1623168716.199|31755|media_filter.cpp :109 ] Filter graph initialized with: [in] transpose=2
[Thread 0x7fff3bfff700 (LWP 31782) exited]
[New Thread 0x7fff3bfff700 (LWP 31783)]
[1623168716.200|31755|media_filter.cpp :109 ] Filter graph initialized with: [in] transpose=2
[1623168716.200|31755|media_filter.cpp :326 ] Filter graph reinitialized
[1623168716.202|31755|sinkclient.cpp :433 ] Stop sink <8487520819298161 / Jami Daemon_shm_31601_1>, mixer=0
[1623168716.202|31755|sinkclient.cpp :429 ] Start sink <8487520819298161 / Jami Daemon_shm_31601_1>, size=480x640, mixer=0
[1623168716.202|31755|sinkclient.cpp :191 ] ShmHolder[Jami Daemon_shm_31601_1]: new sizes: f=1228800, a=2457703
(WebKitWebProcess:31749): GLib-GIO-DEBUG: 12:11:56.206: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[New Thread 0x7ffee0ae2700 (LWP 31784)]
[Thread 0x7ffef17d4700 (LWP 31780) exited]
** (.jami-gnome-real:31601): CRITICAL **: 12:11:56.213: void video_widget_add_renderer(VideoWidget*, VideoWidgetRenderer*): assertion 'new_video_renderer->v_renderer' failed
** (.jami-gnome-real:31601): DEBUG: 12:11:56.618: call has status Talking, hiding
[1623168716.672|31754|media_encoder.cpp :876 ] H264 encoder setup: crf=33, maxrate=880 kbit/s, bufsize=440 kbit
[1623168717.203|31613|sipcall.cpp :597 ] Sending video keyframe request via SIP INFO
[sdp @ 0x7fffd801f1c0] max delay reached. need to consume packet
[sdp @ 0x7fffd801f1c0] RTP: missed 1 packets
[h264 @ 0x7fffd804f140] negative number of zero coeffs at 16 28
[h264 @ 0x7fffd804f140] error while decoding MB 16 28
[1623168717.702|31754|media_encoder.cpp :876 ] H264 encoder setup: crf=32, maxrate=923 kbit/s, bufsize=461 kbit
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.448: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.449: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.449: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.449: change_notify: /net/jami/JamiGnome/window-height
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.465: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.465: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.465: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.465: change_notify: /net/jami/JamiGnome/window-height
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.491: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.492: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.492: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.492: change_notify: /net/jami/JamiGnome/window-height
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.527: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.527: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.527: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.527: change_notify: /net/jami/JamiGnome/window-height
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.579: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.579: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.579: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.579: change_notify: /net/jami/JamiGnome/window-height
[1623168718.601|31613|sipcall.cpp :597 ] Sending video keyframe request via SIP INFO
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.622: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.623: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.623: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.623: change_notify: /net/jami/JamiGnome/window-height
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.641: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.643: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.643: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.643: change_notify: /net/jami/JamiGnome/window-height
[sdp @ 0x7fffd801f1c0] max delay reached. need to consume packet
[sdp @ 0x7fffd801f1c0] RTP: missed 1 packets
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.676: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.678: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.678: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.679: change_notify: /net/jami/JamiGnome/window-height
[h264 @ 0x7fffd804f140] corrupted macroblock 0 25 (total_coeff=-1)
[h264 @ 0x7fffd804f140] error while decoding MB 0 25
[1623168718.714|31754|media_encoder.cpp :876 ] H264 encoder setup: crf=32, maxrate=969 kbit/s, bufsize=484 kbit
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.745: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.745: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.748: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.750: change_notify: /net/jami/JamiGnome/window-height
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.775: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.776: change_notify: /net/jami/JamiGnome/window-width
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.776: change_fast
(.jami-gnome-real:31601): dconf-DEBUG: 12:11:58.777: change_notify: /net/jami/JamiGnome/window-height
[1623168719.747|31754|media_encoder.cpp :876 ] H264 encoder setup: crf=32, maxrate=1017 kbit/s, bufsize=508 kbit
[1623168720.478|31601|manager.cpp :2536 ] toggle recording for call 8487520819298161
[1623168720.478|31601|sipcall.cpp :576 ] Sending recording state via SIP INFO
[1623168720.478|31601|media_recorder.cpp:232 ] Recorder input #1: a:remote: fltp audio, 2 channel(s), 48000 Hz (1/48000), 0 samples per frame, start: 285835
[1623168720.478|31601|media_recorder.cpp:232 ] Recorder input #2: a:local: s16 audio, 2 channel(s), 48000 Hz (1/48000), 960 samples per frame, start: 297600
[1623168720.478|31601|media_recorder.cpp:232 ] Recorder input #3: v:remote: yuv420p video, 640x480, 30/1 fps (1/60), start: 257
[1623168720.478|31601|media_recorder.cpp:232 ] Recorder input #4: v:local: yuvj422p video, 1280x720, 30/1 fps (1/30), start: 179
[1623168720.492|31601|media_recorder.cpp:168 ] Start recording '/home/maxim/Downloads/Jami/20210608-121200.webm'
[New Thread 0x7ffef17d4700 (LWP 31792)]
[swscaler @ 0x4126680] deprecated pixel format used, make sure you did set range correctly
[1623168720.496|31601|media_filter.cpp :109 ] Filter graph initialized with: [v:remote] fps=30/1, scale=-2:720 [v:m]; [v:local] fps=30/1, scale=-2:144 [v:o]; [v:m] [v:o] overlay=main_w-overlay_w:main_h-overlay_h, format=pix_fmts=yuv420p
[1623168720.496|31601|media_recorder.cpp:437 ] Recorder output: videoOutput: yuv420p video, 960x720, 30/1 fps (1/30)
[New Thread 0x7ffee02e1700 (LWP 31793)]
[1623168720.497|31601|media_filter.cpp :109 ] Filter graph initialized with: [a:local] [a:remote] amix=inputs=2, aresample=osr=48000:ocl=stereo:osf=s16
[1623168720.497|31601|media_recorder.cpp:537 ] Recorder output: audioOutput: s16 audio, 2 channel(s), 48000 Hz (1/48000), 0 samples per frame
[1623168720.497|31601|media_encoder.cpp :273 ] Not using hardware encoding for opus
[1623168720.497|31601|media_encoder.cpp :547 ] [libopus] Using 4 threads
[1623168720.497|31601|media_encoder.cpp :599 ] [libopus] Frame size not set
[libopus @ 0x4179080] No bit rate set. Defaulting to 96000 bps.
[1623168720.497|31601|media_recorder.cpp:376 ] Recording initialized
[1623168720.505|31755|filter_transpose.cpp:31 ] Rotation set to 90
[New Thread 0x7ffedfae0700 (LWP 31794)]
[1623168720.508|31755|media_filter.cpp :109 ] Filter graph initialized with: [in] transpose=2, scale=w=-1:h=480, pad=640:480:(ow-iw)/2
[swscaler @ 0x7fffd809b800] Warning: data is not aligned! This can lead to a speed loss
[Thread 0x7ffef17d4700 (LWP 31792) exited]
[New Thread 0x7ffef17d4700 (LWP 31795)]
[1623168720.514|31753|media_filter.cpp :109 ] Filter graph initialized with: [v:remote] fps=30/1, scale=-2:720 [v:m]; [v:local] fps=30/1, scale=-2:144 [v:o]; [v:m] [v:o] overlay=main_w-overlay_w:main_h-overlay_h, format=pix_fmts=yuv420p
[1623168720.514|31753|media_filter.cpp :326 ] Filter graph reinitialized
[1623168720.526|31754|media_encoder.cpp :876 ] H264 encoder setup: crf=33, maxrate=864 kbit/s, bufsize=432 kbit
[1623168720.643|31617|media_encoder.cpp :273 ] Not using hardware encoding for vp8
[1623168720.643|31617|media_encoder.cpp :734 ] Hardware encoding disabled
[1623168720.643|31617|media_encoder.cpp :547 ] [libvpx] Using 4 threads
[1623168720.643|31617|media_encoder.cpp :931 ] VP8 encoder setup: crf=18
[libvpx @ 0x7fffb473f300] Bitrate not specified for constrained quality mode, using default of 256kbit/sec
[New Thread 0x7ffeddf88700 (LWP 31796)]
[New Thread 0x7ffedd787700 (LWP 31797)]
[New Thread 0x7ffedcf86700 (LWP 31798)]
[New Thread 0x7ffedc785700 (LWP 31799)]
[1623168720.779|31752|sip_utils.cpp :251 ] Registered thread 0x7ffeed74c028 (0x7B71)
[1623168721.618|31754|media_encoder.cpp :876 ] H264 encoder setup: crf=32, maxrate=907 kbit/s, bufsize=453 kbit
[1623168721.706|31621|nat_pmp.cpp :78 ] NAT-PMP: Trying to initialize IGD
[1623168721.706|31621|nat_pmp.cpp :106 ] NAT-PMP: Initialized on gateway 192.168.10.1
[1623168721.707|31621|nat_pmp.cpp :557 ] NAT-PMP: read response on IGD 192.168.10.1 failed with error NOGATEWAYSUPPORT
[1623168721.707|31621|nat_pmp.cpp :227 ] NAT-PMP: Start search for IGDs. Attempt 3
[sdp @ 0x7fffc40012c0] max delay reached. need to consume packet
[sdp @ 0x7fffc40012c0] RTP: missed 1 packets
[sdp @ 0x7fffc40012c0] max delay reached. need to consume packet
[sdp @ 0x7fffc40012c0] RTP: missed 1 packets
--Type <RET> for more, q to quit, c to continue without paging--c
Thread 1 ".jami-gnome-rea" received signal SIGSEGV, Segmentation fault.
0x00007ffff1354d90 in __memcpy_ssse3 () from /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6
(gdb) bt -full
#0 0x00007ffff1354d90 in __memcpy_ssse3 () from /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6
No symbol table info available.
#1 0x00007ffff67cc7fe in _cogl_bitmap_copy_subregion (src=src@entry=0x476ac40, dst=dst@entry=0x476ad40, src_x=src_x@entry=0, src_y=src_y@entry=0, dst_x=dst_x@entry=0, dst_y=dst_y@entry=0, width=1280,
height=720, error=0x7fffffffcf38) at cogl-bitmap.c:154
srcdata = 0x7ffed4000030 <error: Cannot access memory at address 0x7ffed4000030>
dstdata = <optimized out>
bpp = <optimized out>
line = 0
succeeded = 0
__func__ = "_cogl_bitmap_copy_subregion"
#2 0x00007ffff67cec9e in _cogl_bitmap_convert_into_bitmap (src_bmp=src_bmp@entry=0x476ac40, dst_bmp=dst_bmp@entry=0x476ad40, error=error@entry=0x7fffffffcf38) at cogl-bitmap-conversion.c:402
src_data = <optimized out>
dst_data = <optimized out>
src = <optimized out>
dst = <optimized out>
tmp_row = <optimized out>
src_rowstride = 5120
dst_rowstride = 5120
y = <optimized out>
width = <optimized out>
height = 720
src_format = COGL_PIXEL_FORMAT_BGRA_8888
dst_format = COGL_PIXEL_FORMAT_BGRA_8888_PRE
use_16 = <optimized out>
need_premult = 1
__func__ = "_cogl_bitmap_convert_into_bitmap"
#3 0x00007ffff67d039c in _cogl_bitmap_convert (src_bmp=0x476ac40, dst_format=COGL_PIXEL_FORMAT_BGRA_8888_PRE, error=0x7fffffffcf38) at cogl-bitmap-conversion.c:509
dst_bmp = 0x476ad40
width = 1280
height = <optimized out>
ctx = <optimized out>
#4 0x00007ffff67d04e7 in _cogl_bitmap_convert_for_upload (src_bmp=src_bmp@entry=0x476ac40, internal_format=internal_format@entry=COGL_PIXEL_FORMAT_BGRA_8888_PRE,
can_convert_in_place=can_convert_in_place@entry=0, error=error@entry=0x7fffffffcf38) at cogl-bitmap-conversion.c:610
closest_format = <optimized out>
ctx = <optimized out>
src_format = <optimized out>
dst_bmp = <optimized out>
__func__ = "_cogl_bitmap_convert_for_upload"
#5 0x00007ffff67b9197 in allocate_from_bitmap (loader=<optimized out>, loader=<optimized out>, error=0x7fffffffcf38, tex_2d=0x2e0f400) at driver/gl/cogl-texture-2d-gl.c:206
ctx = 0x7f2ab0
width = <optimized out>
height = 720
gl_format = 184
tex = 0x2e0f400
internal_format = COGL_PIXEL_FORMAT_BGRA_8888_PRE
upload_bmp = <optimized out>
gl_intformat = 0
gl_type = 0
bmp = 0x476ac40
can_convert_in_place = 0
tex = <optimized out>
bmp = <optimized out>
ctx = <optimized out>
internal_format = <optimized out>
width = <optimized out>
height = <optimized out>
can_convert_in_place = <optimized out>
upload_bmp = <optimized out>
--Type <RET> for more, q to quit, c to continue without paging--c
gl_intformat = <optimized out>
gl_format = <optimized out>
gl_type = <optimized out>
ignore = <optimized out>
data = <optimized out>
format = <optimized out>
#6 _cogl_texture_2d_gl_allocate (tex=0x2e0f400, error=0x7fffffffcf38) at driver/gl/cogl-texture-2d-gl.c:462
tex_2d = 0x2e0f400
loader = <optimized out>
__func__ = "_cogl_texture_2d_gl_allocate"
#7 0x00007ffff67ecef6 in cogl_texture_allocate (texture=texture@entry=0x2e0f400, error=error@entry=0x7fffffffcf38) at cogl-texture.c:1398
error = 0x7fffffffcf38
texture = 0x2e0f400
#8 0x00007ffff6807e44 in _cogl_texture_new_from_bitmap (bitmap=bitmap@entry=0x476ac40, flags=flags@entry=COGL_TEXTURE_NO_ATLAS, internal_format=internal_format@entry=COGL_PIXEL_FORMAT_ANY, can_convert_in_place=can_convert_in_place@entry=0, error=error@entry=0x7fffffffcf98) at deprecated/cogl-auto-texture.c:246
ctx = 0x7f2ab0
tex = 0x2e0f400
internal_error = 0x0
#9 0x00007ffff68081d3 in _cogl_texture_new_from_data (error=0x7fffffffcf98, data=0x7ffed4000030 <error: Cannot access memory at address 0x7ffed4000030>, rowstride=5120, internal_format=COGL_PIXEL_FORMAT_ANY, format=COGL_PIXEL_FORMAT_BGRA_8888, flags=COGL_TEXTURE_NO_ATLAS, height=720, width=1280, ctx=<optimized out>) at deprecated/cogl-auto-texture.c:168
bmp = 0x476ac40
tex = <optimized out>
bmp = <optimized out>
tex = <optimized out>
_g_boolean_var_ = <optimized out>
_g_boolean_var_ = <optimized out>
#10 cogl_texture_new_from_data (width=width@entry=1280, height=height@entry=720, flags=COGL_TEXTURE_NO_ATLAS, format=format@entry=COGL_PIXEL_FORMAT_BGRA_8888, internal_format=internal_format@entry=COGL_PIXEL_FORMAT_ANY, rowstride=rowstride@entry=5120, data=0x7ffed4000030 <error: Cannot access memory at address 0x7ffed4000030>) at deprecated/cogl-auto-texture.c:193
ignore_error = 0x0
tex = <optimized out>
ctx = <optimized out>
#11 0x00007ffff68fa19f in clutter_image_set_data (image=0x7fffdc007870, data=0x7ffed4000030 <error: Cannot access memory at address 0x7ffed4000030>, pixel_format=COGL_PIXEL_FORMAT_BGRA_8888, width=1280, height=720, row_stride=5120, error=0x7fffffffd060) at clutter-image.c:228
priv = 0x7fffdc007860
flags = <optimized out>
__func__ = "clutter_image_set_data"
#12 0x00000000004c6011 in clutter_render_image(_VideoWidgetRenderer*) ()
No symbol table info available.
#13 0x00000000004c63a3 in check_frame_queue(_VideoWidget*) ()
No symbol table info available.
#14 0x00007ffff6faa9a3 in g_timeout_dispatch (source=source@entry=0x591a360, callback=<optimized out>, user_data=<optimized out>) at ../glib-2.62.6/glib/gmain.c:4705
timeout_source = 0x591a360
again = <optimized out>
#15 0x00007ffff6fa9f14 in g_main_dispatch (context=0x728ae0) at ../glib-2.62.6/glib/gmain.c:3216
dispatch = 0x7ffff6faa990 <g_timeout_dispatch>
prev_source = 0x0
was_in_call = 0
user_data = 0x5912250
callback = 0x4c62a7 <check_frame_queue(_VideoWidget*)>
cb_funcs = 0x7ffff707c920 <g_source_callback_funcs>
cb_data = 0x30ac4f0
need_destroy = <optimized out>
source = 0x591a360
current = 0x747240
i = 0
current = <optimized out>
i = <optimized out>
source = <optimized out>
_g_boolean_var_ = <optimized out>
was_in_call = <optimized out>
user_data = <optimized out>
callback = <optimized out>
cb_funcs = <optimized out>
cb_data = <optimized out>
need_destroy = <optimized out>
dispatch = <optimized out>
prev_source = <optimized out>
_g_boolean_var_ = <optimized out>
#16 g_main_context_dispatch (context=context@entry=0x728ae0) at ../glib-2.62.6/glib/gmain.c:3881
No locals.
#17 0x00007ffff6faa288 in g_main_context_iterate (context=context@entry=0x728ae0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib-2.62.6/glib/gmain.c:3954
max_priority = 2147483647
timeout = 3
some_ready = 1
nfds = <optimized out>
allocated_nfds = 4
fds = 0x73d270
#18 0x00007ffff6faa30c in g_main_context_iteration (context=context@entry=0x728ae0, may_block=may_block@entry=1) at ../glib-2.62.6/glib/gmain.c:4015
retval = <optimized out>
#19 0x00007ffff71b4a3d in g_application_run (application=0x6fb210, argc=<optimized out>, argv=<optimized out>) at ../glib-2.62.6/gio/gapplication.c:2559
arguments = 0x732a90
status = 0
context = 0x728ae0
acquired_context = <optimized out>
__FUNCTION__ = "g_application_run"
#20 0x000000000047b47c in main ()
No symbol table info available.
```https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1264jami-gnome crashes on exit if a call is ongoing (now hangs with LIBWRAP=true ...2023-05-26T13:59:15ZMaxim Cournoyerjami-gnome crashes on exit if a call is ongoing (now hangs with LIBWRAP=true builds)```
$ guix show jami-gnome
name: jami-gnome
version: 20210606.1.e2f9490
outputs: out debug
systems: x86_64-linux
dependencies: adwaita-icon-theme@3.34.3 clutter-gtk@1.8.4 clutter@1.26.2 gettext-minimal@0.20.1
+ glib@2.62.6 gtk+@3.24.24 l...```
$ guix show jami-gnome
name: jami-gnome
version: 20210606.1.e2f9490
outputs: out debug
systems: x86_64-linux
dependencies: adwaita-icon-theme@3.34.3 clutter-gtk@1.8.4 clutter@1.26.2 gettext-minimal@0.20.1
+ glib@2.62.6 gtk+@3.24.24 libappindicator@12.10.0 libcanberra@0.30 libnotify@0.7.9
+ libring@20210606.1.e2f9490 libringclient@20210606.1.e2f9490 network-manager@1.24.0 pkg-config@0.29.2
+ qrencode@4.1.1 sqlite@3.31.1 webkitgtk@2.32.1
[...]
```
Reproduction steps
1. Open jami-gnome.
2. Make a video call.
3. Click the top-left menu, select quit.
4. Observe the unclean return status (143) and GTK error message:
```
(jami-gnome:23770): dconf-DEBUG: 10:06:12.339: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:23770): dconf-DEBUG: 10:06:13.882: unwatch_fast: "/net/jami/JamiGnome/" (active: 6, establishing: 0)
(jami-gnome:23770): Gtk-CRITICAL **: 10:06:13.884: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
Terminated
$ echo $?
143
```
Rarely, the daemon would also fail to release the camera.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1263Jami does not follow the system's icons In the systray2023-05-26T13:59:14ZHojjat Ali MohammadiJami does not follow the system's icons In the systrayHi,
It seems Jami does not follow the system's icons in the systray.
![image](/uploads/d416eb6d67fad5f38c9468c32b4181af/image.png)
I can confirm the system icons has icons for Jami
```
./Gruvbox-Material-Dark/16x16/apps/jami.svg
./Gr...Hi,
It seems Jami does not follow the system's icons in the systray.
![image](/uploads/d416eb6d67fad5f38c9468c32b4181af/image.png)
I can confirm the system icons has icons for Jami
```
./Gruvbox-Material-Dark/16x16/apps/jami.svg
./Gruvbox-Material-Dark/16x16/apps/net.jami.Jami.svg
./Gruvbox-Material-Dark/22x22/apps/jami.svg
./Gruvbox-Material-Dark/22x22/apps/net.jami.Jami.svg
./Gruvbox-Material-Dark/24x24/apps/jami.svg
./Gruvbox-Material-Dark/24x24/apps/net.jami.Jami.svg
./Gruvbox-Material-Dark/32x32/apps/jami.svg
./Gruvbox-Material-Dark/32x32/apps/net.jami.Jami.svg
./Gruvbox-Material-Dark/48x48/apps/jami.svg
./Gruvbox-Material-Dark/48x48/apps/net.jami.Jami.svg
./Gruvbox-Material-Dark/64x64/apps/jami.svg
./Gruvbox-Material-Dark/64x64/apps/net.jami.Jami.svg
```
OS: Archlinux
Jami Version: jami-gnome 20210308-1
Thanks a lothttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1262Issue when pressing Enter after selecting emoji2023-05-26T13:59:18ZHai78Issue when pressing Enter after selecting emojiBug report form
---------------
## OS
Trisquel GNU/Linux 9 Etiona
## Jami daemon version:
Jami Daemon 10.0.0
## Jami GNOME client version:
181627cc726a44597f4ccc533f184928d0a3a612 - unknown
## Where did you get Jami?
- [ ] My OS ...Bug report form
---------------
## OS
Trisquel GNU/Linux 9 Etiona
## Jami daemon version:
Jami Daemon 10.0.0
## Jami GNOME client version:
181627cc726a44597f4ccc533f184928d0a3a612 - unknown
## Where did you get Jami?
- [ ] My OS package manager (e.g. apt, yum, pacman)
- [x] I downloaded it from jami.net
- [ ] I built it from source using the make-ring.py script
- [ ] I built it from source manually or other (please explain):
## Steps to reproduce bug
Steps:
1. Select emoji
2. Press Enter in the keyboard
## What you expect to happen:
The expected behavior is when i select an emoji and press Enter the emoji should be send (or the message with emoji).
## What happens instead:
When is select an emoji and they i press Enter, the emoji is selected again every time i press Enter.
![image](/uploads/e7ff388430ba5f462e6b6b44131e8be0/image.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1261fix chatview icons in dark themes2021-05-04T14:03:47ZAmin Bandalifix chatview icons in dark themesAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1260add emoji picker2021-05-04T14:03:25ZAmin Bandaliadd emoji pickerAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1259re-register to late2023-05-26T13:59:13ZLukas Wallischre-register to lateAs the logs suggests the re-register timer is to long... as far as i know the reregister should come before the old register expires, not 10s after...
```
[1618330072.037|43625|sipaccount.cpp :958 ] Start keep alive timer for accoun...As the logs suggests the re-register timer is to long... as far as i know the reregister should come before the old register expires, not 10s after...
```
[1618330072.037|43625|sipaccount.cpp :958 ] Start keep alive timer for account 7e9411aaf521bc4b
[1618330072.037|43625|sipaccount.cpp :977 ] Registration Expire: 119
[1618330072.037|43625|sipvoiplink.cpp :776 ] Register new keep alive timer 2099486383 with delay 129
```
OS : Ubuntu 20.04
Version: snap ( downloaded today)
`jami -v` gives:
```
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...and using ALSA.
Jami Daemon 9.8.0-a6d5ad32d7-dirty, by Savoir-faire Linux 2004-2019
https://jami.net/
[Video support enabled]
[Plugins support enabled]
```
i can only find the settings for the expire-timer, but the not the reregister-timer. am I missing something?
I'm using this client behind a Hardware-PBX, because of the late reregister my calls keep getting abortedhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1258Invalid dbus answer. Daemon not running2021-04-13T16:07:33ZLukas WallischInvalid dbus answer. Daemon not runningBug report form
---------------
## OS Ubuntu 20.04
<!-- e.g. Debian, Ubuntu, etc. -->
## Jami daemon version:
not under the given path `/usr/lib/ring/dring`
instead under `snap/jami/132/usr/lib/ring/dring`
Jami Daemon 9.8.0-a6d5ad32d...Bug report form
---------------
## OS Ubuntu 20.04
<!-- e.g. Debian, Ubuntu, etc. -->
## Jami daemon version:
not under the given path `/usr/lib/ring/dring`
instead under `snap/jami/132/usr/lib/ring/dring`
Jami Daemon 9.8.0-a6d5ad32d7-dirty, by Savoir-faire Linux 2004-2019
<!-- type `/usr/lib/ring/dring -h` into your terminal -->
## Jami GNOME client version:
<!-- type `jami-gnome -v` into your terminal -->
not from 'jami-gnome' instead only 'jami'
Jami Daemon 9.8.0-a6d5ad32d7-dirty, by Savoir-faire Linux 2004-2019
## Where did you get Jami?
<!-- (add an x in between the square brackets to select an option) -->
- [ ] My OS package manager (e.g. apt, yum, pacman)
- [x] snap package manager
- [ ] I downloaded it from jami.net
- [ ] I built it from source using the make-ring.py script
- [ ] I built it from source manually or other (please explain):
## Steps to reproduce bug
<!-- The better your scenario is, the better we will be able to help
you. Please try to describe only one bug here. Open multiple issues
for multiple bugs -->
this is where i'm not sure -.-
## What you expect to happen:
-Able to change Account Settings.
-on fresh install setup a SIP-Account
## What happens instead:
-Account settings open very very slow (~1m)
-after click on create Account ( in Advanced/create SIP Account) nothing happens
## Logs
### Console Output
```
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...and using ALSA.
Jami Daemon 9.8.0-a6d5ad32d7-dirty, by Savoir-faire Linux 2004-2019
https://jami.net/
[Video support enabled]
[Plugins support enabled]
One does not simply initialize the client: Another daemon is detected
** (jami-gnome:14285): DEBUG: 11:52:00.893: debug enabled
** Message: 11:52:00.895: Jami GNOME client version: f6d50ba8bd027d9d02964f0954b40275c472267b
** Message: 11:52:00.895: git ref: eb9b95966519bb90e07d040a22c464c7c85bd918
** (jami-gnome:14285): DEBUG: 11:52:00.895: enabling autostart
** (jami-gnome:14285): DEBUG: 11:52:00.895: checking /usr/share/jami-gnome/jami-gnome.desktop
** (jami-gnome:14285): DEBUG: 11:52:00.895: checking /usr/local/share/jami-gnome/jami-gnome.desktop
** (jami-gnome:14285): DEBUG: 11:52:00.895: '/home/wallisch/snap/jami/132/.config/autostart/jami-gnome.desktop' is already a symlink to '/usr/local/share/jami-gnome/jami-gnome.desktop'
(jami-gnome:14285): Gtk-WARNING **: 11:52:00.909: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:00.913: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:00.914: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:01.117: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:01.120: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-WARNING **: 11:52:01.121: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-DEBUG: 11:52:01.144: Connecting to session manager
Invalid dbus answer. Daemon not running
** (jami-gnome:14285): DEBUG: 11:52:01.182: notify server name: gnome-shell, vendor: GNOME, version: 3.36.7, spec: 1.2
** (jami-gnome:14285): DEBUG: 11:52:01.185: building conversationsview for inexistant account (just removed ?)
** (jami-gnome:14285): DEBUG: 11:52:01.185: building conversationsview for inexistant account (just removed ?)
** (jami-gnome:14285): WARNING **: 11:52:01.212: drawChannels out_of_range exception
(jami-gnome:14285): Gtk-CRITICAL **: 11:52:01.395: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.457: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.461: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.462: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name
** (jami-gnome:14285): DEBUG: 11:52:01.473: real_name = Wallisch Lukas
** (jami-gnome:14285): DEBUG: 11:52:01.473: user_name = wallisch
(jami-gnome:14285): Gtk-WARNING **: 11:52:01.474: Theme parsing error: <data>:1:270: not a number
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.603: Theme parsing error: gtk.css:1566:23: 'font-feature-settings' is not a valid property name
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.607: Theme parsing error: gtk.css:3616:25: 'font-feature-settings' is not a valid property name
(WebKitWebProcess:14397): Gtk-WARNING **: 11:52:01.608: Theme parsing error: gtk.css:4078:23: 'font-feature-settings' is not a valid property name
(jami-gnome:14285): Gtk-CRITICAL **: 12:01:03.124: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:14285): Gtk-CRITICAL **: 12:01:03.125: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:14285): Gtk-CRITICAL **: 12:01:03.125: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:14285): Gtk-CRITICAL **: 12:01:03.125: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
```
<!-- run
journalctl --since "24h ago" | grep dring
in your terminal -->
### journalctl:
```
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: [XFER] facade created, pimpl @0x55b1168ec7a0
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Default video settings: 800x600, 30 FPS
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Manager not initialized yet
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Not initialized
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Not initialized
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Encoders found: H264 VP8 MP4V-ES H263-1998 opus G722 speex speex speex PCMA PCMU
Apr 13 08:22:06 wallisch-TERRA-PC dring[2715]: Decoders found: H264 VP8 MP4V-ES H263-1998 opus G722 speex speex speex PCMA PCMU
Apr 13 08:22:07 wallisch-TERRA-PC dring[2715]: UPnP: check for valid IGD timeout
Apr 13 11:48:54 wallisch-TERRA-PC dring[2715]: NAT-PMP: can't send request
```
## Additional information
**After terminating `dring` via `htop` it seems to work just fine now ¯\\\_(ツ)\_/¯**https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1257Outgoing SIP calls drop after 32s2021-06-25T19:17:17ZDavid LecompteOutgoing SIP calls drop after 32sI am using an OVH SIP account. Outgoing calls to a landline or to another OVH SIP account drop after 32s, this is 100% reproducible.
I am using Trisquel 9 on a desktop PC and added Jami repository, the version of jami is 2021-03-08 21:4...I am using an OVH SIP account. Outgoing calls to a landline or to another OVH SIP account drop after 32s, this is 100% reproducible.
I am using Trisquel 9 on a desktop PC and added Jami repository, the version of jami is 2021-03-08 21:43:25 UTC . The network connection is via ethernet, my ISP is SFR in Paris France, fiber connection.
The attached log was obtained with
/usr/lib/ring/dring -d -c 2>&1 | tee dring5.log
The image is a screen capture taken immediately after the call drop (less than 1s after) in order to show what was visible in the log. The big seqence of consecutive "underrun occured" was during the call but it paused more than 10s before the call drop.
[dring5.log](/uploads/13531e3ba91c41ce9edd1c87531a616b/dring5.log)
![right_after_drop](/uploads/32eccf95fdc4c7191b6c18ae7bab4d45/right_after_drop.png)Ming Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1255[GNOME] Dialpad2023-05-26T13:59:32ZJami 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-client-gnome/-/issues/1254TRANSFERT DE FICHIERS2021-08-16T20:46:22ZVERO JEAN-LUCveroniquejeanluc@lilo.orgTRANSFERT DE FICHIERSBonjour,
Pourquoi ce message : "juste maintenant - Impossible de contacter l'interlocuteur" s'affiche et que le transfert de fichier échoue, alors que je suis connecté à l'appareil de mon interlocuteur, puisque nous sommes en cours de co...Bonjour,
Pourquoi ce message : "juste maintenant - Impossible de contacter l'interlocuteur" s'affiche et que le transfert de fichier échoue, alors que je suis connecté à l'appareil de mon interlocuteur, puisque nous sommes en cours de conversation audio et vidéo et que les messages textes sont également envoyés et reçues sans soucis ?
J'ai réalisé les essais de mon appareil ubuntu du compte jami 553dec1f75758ef6eaecdd1c027bf397f3062700 vers mon appareil android sur un autre compte jami c5c5f8..................................
Merci pour votre aide à la compréhension de ce phénomène et comment résoudre ce problème.
Librementhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1253Jami doesn't honor GTK Theming on Arch KDE2023-05-26T13:59:16ZKreestoballJami doesn't honor GTK Theming on Arch KDEI'm on Arch and installed Jami 20201217-1 from the community repo.
KDE has a specific GTK theming section in its appearance settings, but Jami doesn't seem to fully follow the dark theme I have applied, it's called sweet.
It seems to t...I'm on Arch and installed Jami 20201217-1 from the community repo.
KDE has a specific GTK theming section in its appearance settings, but Jami doesn't seem to fully follow the dark theme I have applied, it's called sweet.
It seems to try, as the window close/minimize/maximize buttons are colored according to my theme:
![2021-02-28_00-56](/uploads/96618071ed62540844359c45a8d53141/2021-02-28_00-56.png)
But it should look like this:
![2021-02-28_00-57](/uploads/123ed85b245376515d7e5b2a1130ba71/2021-02-28_00-57.png)
I've tried launching from the CLI with `GTK_THEME=sweet jami-gnome`, but that doesn't make a difference.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1252Conference: Host should be able to mute video & mic2021-12-29T19:08:40ZSébastien BlinConference: Host should be able to mute video & micBackloghttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1251The camera shows the opposite side2023-05-26T13:59:14ZSallyThe camera shows the opposite sideBug report form
---------------
## OS
Fedora 33
I am usng jami-gnome
## Where did you get Jami?
- [x] My OS package manager (e.g. apt, yum, pacman) dnf
- [ ] I downloaded it from jami.net
- [ ] I built it from source using the make-...Bug report form
---------------
## OS
Fedora 33
I am usng jami-gnome
## Where did you get Jami?
- [x] My OS package manager (e.g. apt, yum, pacman) dnf
- [ ] I downloaded it from jami.net
- [ ] I built it from source using the make-ring.py script
- [ ] I built it from source manually or other (please explain):
## Steps to reproduce bug
Steps:
1. Open settings
2. Go to Media >> The camera show right side on the left one and vise versa.
By the way this issue is there with cheese app in gnome as well, unless I change its effects to 'flip'
But there's no issue with skype or zoom apps.
Thank you.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1250HELP S.O.S. JAMI UBUNTU 20.102021-02-13T11:56:46ZVERO JEAN-LUCveroniquejeanluc@lilo.orgHELP S.O.S. JAMI UBUNTU 20.10![JAMI_OLD_BOG_INSTALLATION](/uploads/7b021704e90f57375ca8db4de87cacae/JAMI_OLD_BOG_INSTALLATION.png)
Impossible de mettre à jour ni même d’installer à nouveau jami à partir de jami.net ?
Quelqu’un aurait-il une solution ? Merci
Voici ce...![JAMI_OLD_BOG_INSTALLATION](/uploads/7b021704e90f57375ca8db4de87cacae/JAMI_OLD_BOG_INSTALLATION.png)
Impossible de mettre à jour ni même d’installer à nouveau jami à partir de jami.net ?
Quelqu’un aurait-il une solution ? Merci
Voici ce que dit le terminal :
verojean@verojean:~$ sudo apt-get update && sudo apt-get install jami
Atteint :1 http://archive.ubuntu.com/ubuntu focal InRelease
Atteint :2 http://fr.archive.ubuntu.com/ubuntu focal InRelease
Atteint :3 http://fr.archive.ubuntu.com/ubuntu focal-updates InRelease
Atteint :4 http://fr.archive.ubuntu.com/ubuntu focal-backports InRelease
Réception de :5 http://security.ubuntu.com/ubuntu focal-security InRelease [109 kB]
Atteint :6 https://dl.jami.net/nightly/ubuntu_20.10 ring InRelease
109 ko réceptionnés en 2s (47,9 ko/s)
Lecture des listes de paquets… Fait
Lecture des listes de paquets… Fait
Construction de l’arbre des dépendances
Lecture des informations d’état… Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l’impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n’ont pas encore
été créés ou ne sont pas sortis d’Incoming.
**L’information suivante devrait vous aider à résoudre la situation : **
Les paquets suivants contiennent des dépendances non satisfaites :
** jami : Dépend: libqt5core5a (>= 5.14.1) mais 5.12.8+dfsg-0ubuntu1 devra être installé**
** Dépend: jami-daemon (= 20210205.3.176eed9~dfsg1-1) mais ne sera pas installé**
E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l’état ».
verojean@verojean:~$
Pour l’instant seul JAMI 20210105 est installé en secours, mais je ne vois que les identifiants et pas les noms d’utilisateurs…https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1249Header bar Visuals2021-04-21T13:01:52ZMartin MayerHeader bar VisualsHi all,
I would like to propose some visual adjustments to the header bar to make the jami-gnome-client fit more to the standard arrangement of other GNOME apps.
* Move the `Main Menu` to the right next to the close button
* Repla...Hi all,
I would like to propose some visual adjustments to the header bar to make the jami-gnome-client fit more to the standard arrangement of other GNOME apps.
* Move the `Main Menu` to the right next to the close button
* Replace the `Main Menu` icon with a hamburger menu icon
* Move the `Account Selector` dropdown menu to the center
* Move the `Secondary Menu`, the on with the wheel icon to the utmost left.
* Replace the wheel icon of the `Secondary Menu` with a three-vertica-dot icon.
---
Rational
* Since the `Header Bar` is not split, the main menu should go to the utmost right next to the `Close Button`
* Visually we should have **something** on the left then. The `Secondary Menu` in the middle makes no sense, so move it to the left
* Remains to position the `Account Selector` - I think the middle would look best.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1248Outgoing audio and video calls often fail2021-02-01T19:29:56ZLuis FelipeOutgoing audio and video calls often fail**Jami**: (GTK) 20200710.1.6bd18d2 (from official OS repository)
**Daemon**: Jami Daemon 9.3.0, by Savoir-faire Linux 2004-2019
**OS**: Guix System 681af17
-----
## Steps to reproduce bug
Assuming Jami has been already started:
1...**Jami**: (GTK) 20200710.1.6bd18d2 (from official OS repository)
**Daemon**: Jami Daemon 9.3.0, by Savoir-faire Linux 2004-2019
**OS**: Guix System 681af17
-----
## Steps to reproduce bug
Assuming Jami has been already started:
1. Click on a contact in the left pane
2. Click on the video camera icon to place a video call **or**
click the phone icon to place and audio call
## What you expect to happen:
+ I see a visual indicator that Jami is making the call
+ The person I'm calling notices I'm calling and answers the call
+ We can talk to each other
## What happens instead:
+ A new pane opens, telling me the following information about the call, which seems fine to me:
```
CONTACT_AVATAR
CONTACT_NAME
CONTACT_USER_NAME
Spinner spinning
Searching
Hang up icon
```
But this is unexpected:
+ The pane disappears after a minute of displaying the same state: spinner spinning and the state "Searching".
+ The messages history displays a new entry that says: Missed outgoing call
+ My contact never notices I'm calling
+ So we can't talk to each other
## Logs
There is no `journalctl --since "24h ago" | grep dring` in my system. It doesn't use `systemd` and `dring` runs at user-level.
I'd be happy to provide additional information with some additional guidance.
## Additional information
I tried the same steps indicated above several times with two different contacts, both using Android clients:
**OS**: Android 5.1 and Android 9
**Jami**: 20201222-01 (from F-Droid)
Note that we can text to each other, although not without problems (see #1243).https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1247Long text messages overflow their container box2023-05-26T13:59:12ZLuis FelipeLong text messages overflow their container boxBug report form
---------------
## OS
Guix System 681af17
## Jami daemon version:
Jami Daemon 9.3.0, by Savoir-faire Linux 2004-2019
## Jami GNOME client version:
4703bf11348170da151c62a6a3ae54f83a7d866e - unknown
## Where did ...Bug report form
---------------
## OS
Guix System 681af17
## Jami daemon version:
Jami Daemon 9.3.0, by Savoir-faire Linux 2004-2019
## Jami GNOME client version:
4703bf11348170da151c62a6a3ae54f83a7d866e - unknown
## Where did you get Jami?
- [x] My OS package manager (e.g. apt, yum, pacman)
- [ ] I downloaded it from jami.net
- [ ] I built it from source using the make-ring.py script
- [ ] I built it from source manually or other (please explain):
## Steps to reproduce bug
Steps:
1. Select one of you contacts to send a message
2. Type the following text:
```
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
```
3. Send the message
## What you expect to happen:
The message should be contained by its bounding box.
## What happens instead:
The message overflows its bounding box.
## Logs
I couldn't figure out how to get logs in my system.
## Additional information
![gnu-jami-text-message-overflow--2021-01-30](/uploads/2f286d2e70819a49e04eb6037534b4d1/gnu-jami-text-message-overflow--2021-01-30.png)