Hi
I just downloaded the greenscreen.jpl plugin, but when I try o install it the app crashes and closes down. I tried several downloads, but still same every time. It fails. Watermark plugin works
I am running the snapversion of Jami and Ubuntu 22.04.1. Is this a known issue?
Hello jaxilian,
It isn’t a known issue, i myself use the greenscreen plugin in ubuntu 22.04 without that crash… could you share your log for more details? You can do so by running jami like jami -d -f <name-your-log>
[1666328552.855|5327|ringbuffer.cpp :55 ] Create new RingBuffer audiolayer_id
[1666328552.856|5327|video_device_monitor_impl.cpp:150 ] udev: adding device with id CN0NVH0JLOG0081A00ACA00_Integrated_Webcam_HD_200901010001
[1666328552.972|5327|video_device.h :133 ] Default video settings: 960x540, 30 FPS
[1666328552.973|5327|video_device_monitor_impl.cpp:150 ] udev: adding device with id CN0NVH0JLOG0081A00ACA00_Integrated_Webcam_HD_200901010001
[1666328552.974|5327|video_device_monitor_impl.cpp:150 ] udev: adding device with id CN0NVH0JLOG0081A00ACA00_Integrated_Webcam_HD_200901010001
[1666328552.974|5327|video_device_monitor_impl.cpp:150 ] udev: adding device with id CN0NVH0JLOG0081A00ACA00_Integrated_Webcam_HD_200901010001
[1666328552.975|5327|manager.cpp :721 ] Not initialized
[1666328552.976|5327|manager.cpp :721 ] Not initialized
[1666328552.976|5327|manager.cpp :791 ] Using PJSIP version 2.12.1 for x86_64-pc-linux-gnu
[1666328552.976|5327|manager.cpp :792 ] Using GnuTLS version 3.7.3
[1666328552.976|5327|manager.cpp :793 ] Using OpenDHT version 2.4.9
[1666328552.977|5327|manager.cpp :794 ] Using FFmpeg version 5.0
[1666328552.977|5327|manager.cpp :797 ] Using Libgit2 version 1.1.0
[1666328552.977|5327|sipvoiplink.cpp :648 ] Using SIP nameserver: 127.0.0.53
[1666328552.978|5327|sipvoiplink.cpp :742 ] SIPVoIPLink@0x555eb0da8ad0
[1666328552.978|5327|manager.cpp :813 ] Configuration file path: /home/user/snap/jami/248/.config/jami/dring.yml
[1666328552.984|5467|accel.cpp :206 ] -- Starting encoding init for cuda with default device.
[1666328552.984|5467|accel.cpp :171 ] Failed to create cuda device: -1.
[1666328552.985|5467|accel.cpp :221 ] -- Init failed for cuda with default device.
[1666328552.985|5467|accel.cpp :228 ] -- Init encoding for cuda with device 1.
[1666328552.985|5467|accel.cpp :171 ] Failed to create cuda device: -1.
[1666328552.985|5467|accel.cpp :240 ] -- Init failed for cuda with device 1.
[1666328552.985|5467|accel.cpp :228 ] -- Init encoding for cuda with device 2.
[1666328552.986|5467|accel.cpp :171 ] Failed to create cuda device: -1.
[1666328552.986|5467|accel.cpp :240 ] -- Init failed for cuda with device 2.
[1666328553.000|5467|accel.cpp :206 ] -- Starting encoding init for vaapi with default device.
[1666328553.700|5467|accel.cpp :182 ] Device type vaapi successfully created.
[1666328553.700|5467|accel.cpp :215 ] -- Init passed for vaapi with default device.
[1666328553.100|5467|media_encoder.cpp :1236] Fail to open hardware encoder H265 with vaapi
[1666328553.110|5467|system_codec_container.cpp:220 ] Can't find a usable accelerated H265/HEVC codec, disabling.
[1666328553.110|5467|system_codec_container.cpp:250 ] Encoders found: H264 VP8 MP4V-ES H263-1998 opus G722 G726-32 speex speex speex PCMA PCMU
[1666328553.120|5467|system_codec_container.cpp:251 ] Decoders found: H264 VP8 MP4V-ES H263-1998 opus G722 G726-32 speex speex speex PCMA PCMU
[1666328553.120|5467|jamiaccount.cpp :325 ] [Account 9b691218293998f9] Can't load proxy URL from cache: Can't check write time for: /home/user/snap/jami/common/.cache/9b691218293998f9/dhtproxy
[1666328553.140|5467|account.cpp :293 ] Ringtone /usr/share/jami/ringtones/default.opus is not a valid file
[1666328553.140|5467|upnp_context.cpp :39 ] Creating UPnPContext instance [0x7f26c001f330]
[1666328553.140|5467|upnp_control.cpp :39 ] Controller@0x7f26c003df20: Created UPnP Controller session
[1666328553.140|5461|pupnp.cpp :113 ] PUPnP: Creating instance [0x7f26a8000b80] ...
[1666328553.140|5461|upnp_context.cpp :409 ] Successfully registered controller 0x7f26c003df20
[1666328553.140|5461|upnp_context.cpp :131 ] Starting UPNP context
[1666328553.140|5470|pupnp.cpp :116 ] PUPnP: Instance [0x7f26a8000b80] created
[1666328553.140|5467|jamiaccount.cpp :1113] [Account 9b691218293998f9] loading account
[1666328553.150|5470|pupnp.cpp :218 ] PUPnP: Setting observer to 0x7f26c001f330
[1666328553.150|5467|namedirectory.cpp :493 ] Loaded 1 name-address mappings
[1666328553.150|5470|pupnp.cpp :366 ] PUPnP: Start search for IGD: attempt 1
[1666328553.150|5467|account_manager.cpp :57 ] Loading certificate from 'ring_device.crt' and key from 'ring_device.key' at /home/user/snap/jami/248/.local/share/jami/9b691218293998f9
[1666328553.180|5467|certstore.cpp :89 ] CertificateStore: loaded 3 local certificates.
[1666328553.200|5467|account_manager.cpp :143 ] [Auth] checking device receipt for cfaba2451365229c66b9bde8c41ecf160d46df7b
[1666328553.220|5467|contact_list.cpp :508 ] [Contacts] Found account device: ALM-7N1R8L2D e7e7a5c8d295f5ebfe72da9c5dce671a9c36a24a16553709f2e2e7aac9554490
[1666328553.230|5467|account_manager.cpp :193 ] [Auth] Device e7e7a5c8d295f5ebfe72da9c5dce671a9c36a24a16553709f2e2e7aac9554490 receipt checked successfully for account cfaba2451365229c66b9bde8c41ecf160d46df7b
[1666328553.230|5467|jamiaccount.cpp :1229] [Account 9b691218293998f9] loaded account identity
[1666328553.230|5467|conversation_module.cpp :889 ] [Account 9b691218293998f9] Start loading conversations…
[1666328553.230|5467|conversation_module.cpp :944 ] [Account 9b691218293998f9] Conversations loaded!
[1666328553.230|5467|conversation_module.cpp :889 ] [Account 9b691218293998f9] Start loading conversations…
[1666328553.230|5467|conversation_module.cpp :944 ] [Account 9b691218293998f9] Conversations loaded!
[1666328553.310|5327|jamipluginmanager.cpp :187 ] PLUGIN: load status - 1
[1666328553.320|5327|ringbuffer.cpp :55 ] Create new RingBuffer urgentRingBuffer_id
[1666328553.320|5327|audiolayer.cpp :61 ] [audiolayer] AGC: 0, noiseReduce: 0, VAD: 1, echoCancel: auto, audioProcessor: webrtc
[1666328553.320|5327|pulselayer.cpp :70 ] [audiolayer] created pulseaudio layer
[1666328553.320|5327|pulselayer.cpp :145 ] Waiting....
[1666328553.330|5480|pulselayer.cpp :145 ] Waiting....
[1666328553.330|5480|pulselayer.cpp :145 ] Waiting....
[1666328553.330|5480|pulselayer.cpp :149 ] Connection to PulseAudio server established
[1666328553.330|5480|pulselayer.cpp :179 ] Updating PulseAudio sink list
[1666328553.330|5480|pulselayer.cpp :196 ] Updating PulseAudio source list
[1666328553.340|5480|pulselayer.cpp :213 ] Updating PulseAudio server infos
[1666328553.340|5480|pulselayer.cpp :680 ] PulseAudio server info:
Server name: pulseaudio
Server version: 15.99.1
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: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
[1666328553.340|5480|audiolayer.cpp :74 ] Hardware audio format available : {s16, 2 channels, 44100Hz} 0
[1666328553.340|5480|manager.cpp :2602] Audio format changed: {s16, 1 channels, 16000Hz} -> {s16, 2 channels, 44100Hz}
[1666328553.680|5470|pupnp.cpp :161 ] PUPnP: Initialized on 192.168.32.13:0
[1666328553.680|5470|pupnp.cpp :201 ] PUPnP: Successfully registered client
[1666328553.680|5470|pupnp.cpp :275 ] PUPnP: Send IGD search request
[1666328553.720|5327|jamiaccount.cpp :1730] [Account 9b691218293998f9] Starting account..
[1666328553.720|5327|jamiaccount.cpp :2491] [Account 9b691218293998f9] connecting…
[1666328553.720|5327|jamiaccount.cpp :1638] UPnP: Attempting to map ports for Jami account
[1666328553.720|5468|jamiaccount.cpp :2672] Loading DhParams from file '/home/user/snap/jami/common/.cache/9b691218293998f9/dhParams'
[1666328553.720|5327|upnp_context.cpp :306 ] Desired port is not set, will provide the first available port for [UDP]
[1666328553.720|5327|upnp_context.cpp :341 ] Did not find any available mapping. Will request one now
[1666328553.720|5327|upnp_context.cpp :1110] Port number not set. Will set a random port number
[1666328553.740|5327|upnp_context.cpp :1137] No IGD available. Mapping will be requested when an IGD becomes available
[1666328553.740|5327|mapping.cpp :86 ] Changing mapping JAMI-UDP:24405 state from AVAILABLE to UNAVAILABLE
[1666328553.740|5327|jamiaccount.cpp :1656] [Account 9b691218293998f9] DHT UPNP mapping changed to JAMI-UDP:24405 (state=PENDING, auto-update=YES)
[1666328553.740|5327|jamiaccount.cpp :1694] [Account 9b691218293998f9] Mapping request is in PENDING state: starting the DHT anyway
[1666328553.740|5461|jamiaccount.cpp :1920] [Account 9b691218293998f9] Starting account...
[1666328553.740|5461|jamiaccount.cpp :2576] Could not load /home/user/snap/jami/common/.cache/9b691218293998f9/treatedMessages
[1666328553.740|5461|jamiaccount.cpp :2576] Could not load /home/user/snap/jami/common/.cache/9b691218293998f9/treatedMessages
[1666328553.780|5461|jamiaccount.cpp :1761] [Account 9b691218293998f9] Bootstrap node: bootstrap.jami.net
[1666328553.780|5483|jamiaccount.cpp :2045] [Account 9b691218293998f9] Dht status: IPv4 connecting; IPv6 disconnected
[1666328553.780|5461|upnp_context.cpp :622 ] UPNP/NAT-PMP enabled, but no valid IGDs available
[1666328553.790|5327|manager.cpp :2616] Set accounts order : 9b691218293998f9/
[1666328553.790|5327|manager.cpp :1710] Saving Configuration to XDG directory /home/user/snap/jami/248/.config/jami/dring.yml
[1666328554.140|5483|jamiaccount.cpp :2045] [Account 9b691218293998f9] Dht status: IPv4 connected; IPv6 connecting
[1666328554.140|5483|jamiaccount.cpp :2487] [Account 9b691218293998f9] connected
[1666328554.140|5483|jamiaccount.cpp :3444] [Account 9b691218293998f9] Store DHT public IPv4 address :
[1666328554.140|5494|jamiaccount.cpp :3766] [Account 9b691218293998f9] Refresh cache for TURN server resolution
[1666328554.141|5483|upnp_context.cpp :278 ] Setting the known public address to 95.192.58.92
[1666328554.141|5494|jamiaccount.cpp :3838] [Account 9b691218293998f9] Cache refreshed for TURN resolution
[1666328555.472|5470|pupnp.cpp :827 ] PUPnP: Discovered a new IGD [uuid:4e8a6908-9d4d-48c6-b16a-1ecd89dd87e2 url: http://192.168.32.1:10010/rootDesc.xml]
[1666328555.472|5470|pupnp.cpp :827 ] PUPnP: Discovered a new IGD [uuid:4e8a6908-9d4d-48c6-b16a-1ecd89dd87e4 url: http://192.168.32.1:10010/rootDesc.xml]
[1666328555.480|5494|pupnp.cpp :862 ] PUPnP: Succeeded to download device XML document from http://192.168.32.1:10010/rootDesc.xml
[1666328555.480|5470|pupnp.cpp :1100] PUPnP: Found new device [uuid:4e8a6908-9d4d-48c6-b16a-1ecd89dd87e2]
[1666328555.480|5470|pupnp.cpp :496 ] PUPnP: Validating the IGD candidate [UDN: uuid:4e8a6908-9d4d-48c6-b16a-1ecd89dd87e2]
Name : ZTE UPnP
Service Type : urn:schemas-upnp-org:service:WANIPConnection:1
Service ID : urn:upnp-org:serviceId:WANIPConn1
Base URL : http://192.168.32.1:10010/rootDesc.xml
Location URL : http://192.168.32.1:10010/rootDesc.xml
control URL : http://192.168.32.1:10010/ctl/IPConn
Event URL : http://192.168.32.1:10010/evt/IPConn
[1666328555.481|5509|pupnp.cpp :862 ] PUPnP: Succeeded to download device XML document from http://192.168.32.1:10010/rootDesc.xml
[1666328555.490|5470|pupnp.cpp :568 ] PUPnP: Added a new IGD [uuid:4e8a6908-9d4d-48c6-b16a-1ecd89dd87e2] to the list of valid IGDs
[1666328555.490|5470|pupnp.cpp :571 ] PUPnP: New IGD addresses [int: http://192.168.32.1:10010/ctl/IPConn - ext: 95.192.58.92]
[1666328555.490|5470|pupnp.cpp :588 ] PUPnP: Successfully subscribed to IGD uuid:4e8a6908-9d4d-48c6-b16a-1ecd89dd87e2
[1666328555.490|5461|upnp_context.cpp :932 ] New event for IGD [uuid:4e8a6908-9d4d-48c6-b16a-1ecd89dd87e2 http://192.168.32.1:10010/ctl/IPConn] [UPNP]: [ADDED]
[1666328555.490|5461|upnp_context.cpp :977 ] IGD [UPNP] on address 192.168.32.1:0 was added. Will process any pending requests
[1666328555.490|5461|upnp_context.cpp :581 ] Preferred IGD updated to [UPNP] IGD [uuid:4e8a6908-9d4d-48c6-b16a-1ecd89dd87e2 http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :853 ] Send pending request for mapping JAMI-UDP:24405 to IGD http://192.168.32.1:10010/ctl/IPConn
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-UDP:24405 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|jamiaccount.cpp :1656] [Account 9b691218293998f9] DHT UPNP mapping changed to JAMI-UDP:24405 (state=IN_PROGRESS, auto-update=YES)
[1666328555.490|5461|upnp_context.cpp :645 ] Mapping status [TCP] - overall 0: 0 open (0 ready + 0 in use), 0 pending, 0 in-progress, 0 failed
[1666328555.490|5461|upnp_context.cpp :491 ] Provision 4 new mappings of type [TCP]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-TCP:11178 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-TCP:13545 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-TCP:10634 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-TCP:11457 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :645 ] Mapping status [UDP] - overall 1: 0 open (0 ready + 0 in use), 0 pending, 1 in-progress, 0 failed
[1666328555.490|5461|upnp_context.cpp :491 ] Provision 7 new mappings of type [UDP]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-UDP:20220 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-UDP:23200 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-UDP:23087 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-UDP:21011 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-UDP:20066 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.490|5461|upnp_context.cpp :476 ] Request mapping JAMI-UDP:24201 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.491|5461|upnp_context.cpp :476 ] Request mapping JAMI-UDP:24468 using protocol [UPNP] IGD [http://192.168.32.1:10010/ctl/IPConn]
[1666328555.498|5461|jamiaccount.cpp :1656] [Account 9b691218293998f9] DHT UPNP mapping changed to JAMI-UDP:24405 (state=OPEN, auto-update=YES)
[1666328555.498|5461|jamiaccount.cpp :1673] [Account 9b691218293998f9] Allocated port changed to 24405. Restarting the registration
[1666328555.498|5461|upnp_context.cpp :1017] Mapping JAMI-UDP:24405 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.499|5483|jamiaccount.cpp :2045] [Account 9b691218293998f9] Dht status: IPv4 connecting; IPv6 connecting
[1666328555.499|5483|jamiaccount.cpp :2491] [Account 9b691218293998f9] connecting…
[1666328555.505|5461|upnp_context.cpp :1017] Mapping JAMI-TCP:11178 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.512|5461|upnp_context.cpp :1017] Mapping JAMI-TCP:13545 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.519|5461|upnp_context.cpp :1017] Mapping JAMI-TCP:10634 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.525|5461|upnp_context.cpp :1017] Mapping JAMI-TCP:11457 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.534|5461|upnp_context.cpp :1017] Mapping JAMI-UDP:20220 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.542|5461|upnp_context.cpp :1017] Mapping JAMI-UDP:23200 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.551|5461|upnp_context.cpp :1017] Mapping JAMI-UDP:23087 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.559|5461|upnp_context.cpp :1017] Mapping JAMI-UDP:21011 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.568|5461|upnp_context.cpp :1017] Mapping JAMI-UDP:20066 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.579|5483|jamiaccount.cpp :2045] [Account 9b691218293998f9] Dht status: IPv4 connected; IPv6 connecting
[1666328555.579|5483|jamiaccount.cpp :2487] [Account 9b691218293998f9] connected
[1666328555.579|5461|upnp_context.cpp :1017] Mapping JAMI-UDP:24201 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
[1666328555.579|5494|jamiaccount.cpp :3766] [Account 9b691218293998f9] Refresh cache for TURN server resolution
[1666328555.579|5483|jamiaccount.cpp :3444] [Account 9b691218293998f9] Store DHT public IPv4 address :
[1666328555.580|5494|jamiaccount.cpp :3838] [Account 9b691218293998f9] Cache refreshed for TURN resolution
[1666328555.587|5461|upnp_context.cpp :1017] Mapping JAMI-UDP:24468 (on IGD http://192.168.32.1:10010/ctl/IPConn [PUPNP]) successfully performed
@bandali Can you check the plugin with the snap store version of Jami?
With that log I cannot see anything wrong on the plugin system that would make jami crash.
Also, in both logs the plugins loaded correctly. PLUGIN: load status - 1 is a good log.
but as soon as I activate the plugin, the whole app disappears and closes down. It is the snap version I use
I tried reinstall it from the official repo, but I cannot login…cause there is no login. How do I login with the accout I created?
Hello jaxilian,
We investigated the GreenScreen vs Jami snap version. It seems to be a permission related problem that you can solve by manually giving process-control permission to Jami. Another way to not have this problem is to use Jami from the official repo as you have done.
As per the login, the answer is a bit more complicated.
Jami does not possess a central server, it is a distributed network and your account, once created is not stored anywhere else than in the device you are using Jami. If you uninstalled Jami and wants the account to be back to your original device after reinstalling Jami you must have done an account backup on your own computer (Jami interfaces states it while creating a new account and you always have the option to create this backup from the account settings). If that is not done i regret to inform you that you will not be able to recover this particular account.
Note: if you have the same account in two different devices you can still recover it from the device where Jami is still in use.
You can find a FAQ in FAQ — Jami documentation .