savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-04-12T18:06:44Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/720dl.jami.net package problem2022-04-12T18:06:44Zw5pnydl.jami.net package problemThe file https://dl.jami.net/nightly/ubuntu_20.04/dists/jami/main/binary-amd64/Packages seems to contain
"Version: 20220407.1934.924b928~dfsg1-1" everywhere which apparently results in updates not picking up
202204111847 .... With it thi...The file https://dl.jami.net/nightly/ubuntu_20.04/dists/jami/main/binary-amd64/Packages seems to contain
"Version: 20220407.1934.924b928~dfsg1-1" everywhere which apparently results in updates not picking up
202204111847 .... With it this way, one must uninstall jami and reinstall it to be able to get the latest version.https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/307Rendering links a possible security hole2022-04-12T11:49:14ZthoranRendering links a possible security holeSuppose someone shares a link with me that I want to click on for rendering in my default browser, say Tor Browser. Meantime, the Jami client, in this case the macOS Jami client, has already retrieved that link insecurely or without anon...Suppose someone shares a link with me that I want to click on for rendering in my default browser, say Tor Browser. Meantime, the Jami client, in this case the macOS Jami client, has already retrieved that link insecurely or without anonymity directly on the internet, assuming I'm not running a system-wide proxy. Why bother with Tor Browser at this point? I would like to turn off that new mis-feature please!https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/719crash in VideoProvider2022-04-13T12:58:01ZMohamed Chibanicrash in VideoProvider## Describe your environment
Please specify the following:
- OS: Linux
- Jami version: client-qt commit ID 252bc8488c10b72a9652744e2be5f3bc32abbe66
## Steps to reproduce
- Can you reproduce the bug: only once so far
- Steps:
1. Call...## Describe your environment
Please specify the following:
- OS: Linux
- Jami version: client-qt commit ID 252bc8488c10b72a9652744e2be5f3bc32abbe66
## Steps to reproduce
- Can you reproduce the bug: only once so far
- Steps:
1. Call a RDV point
2. Maximize any participant video (may need to be done multiple times)
- Actual result: crash
- Expected result: no crash
## Additional information
[bt.txt](/uploads/de91545dd055bbdd9738908384075b3f/bt.txt) \
[bt2.txt](/uploads/33121da62a0c995a1d2359ad600c9872/bt2.txt) \
[bt3.txt](/uploads/be750d6b8a4445caca4f8bed1d89096d/bt3.txt)
**[Update]**\
Seems to have been fixed by https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/731 patchhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/718Jami-qt 20220407.1934 hangs with Ubuntu 20.04 on some platforms2022-04-11T20:09:54Zw5pnyJami-qt 20220407.1934 hangs with Ubuntu 20.04 on some platformsjami-qt 20220407.1934 hangs on Ubuntu 20.04 with Dell Precision 4700.
Jami loads, but the window freezes. A gdb trace to the freeze, then
gdb ctrl-c to do a trace yields the following:
=================================================...jami-qt 20220407.1934 hangs on Ubuntu 20.04 with Dell Precision 4700.
Jami loads, but the window freezes. A gdb trace to the freeze, then
gdb ctrl-c to do a trace yields the following:
=========================================================
Jami version: 20220407.1934
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/jami-qt...
(No debugging symbols found in /usr/bin/jami-qt)
(gdb) run
Starting program: /usr/bin/jami-qt
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe2855700 (LWP 1741277)]
[New Thread 0x7fffe0cff700 (LWP 1741280)]
[New Thread 0x7fffd4a41700 (LWP 1741281)]
[New Thread 0x7fffcffff700 (LWP 1741282)]
[New Thread 0x7fffcf7fe700 (LWP 1741283)]
[New Thread 0x7fffceffd700 (LWP 1741284)]
[New Thread 0x7fffcd93d700 (LWP 1741285)]
[New Thread 0x7fffcd13c700 (LWP 1741286)]
[New Thread 0x7fffcc93b700 (LWP 1741287)]
[New Thread 0x7fffb3fff700 (LWP 1741288)]
[New Thread 0x7fffb37fe700 (LWP 1741289)]
[New Thread 0x7fffb2ffd700 (LWP 1741290)]
[New Thread 0x7fffb27fc700 (LWP 1741291)]
[New Thread 0x7fffb1ffb700 (LWP 1741292)]
[New Thread 0x7fffb17fa700 (LWP 1741293)]
[New Thread 0x7fffb0ff9700 (LWP 1741294)]
[New Thread 0x7fffa7fff700 (LWP 1741295)]
[New Thread 0x7fffa77fe700 (LWP 1741296)]
[New Thread 0x7fffa6ffd700 (LWP 1741297)]
[New Thread 0x7fffa67fc700 (LWP 1741298)]
[New Thread 0x7fffa5ffb700 (LWP 1741299)]
[New Thread 0x7fffa57fa700 (LWP 1741300)]
[New Thread 0x7fffa4ff9700 (LWP 1741301)]
[New Thread 0x7fff5ffff700 (LWP 1741302)]
[New Thread 0x7fff5f7fe700 (LWP 1741303)]
[New Thread 0x7fff5effd700 (LWP 1741304)]
[New Thread 0x7fff5e7fc700 (LWP 1741305)]
[New Thread 0x7fff5dffb700 (LWP 1741306)]
[New Thread 0x7fff5d7fa700 (LWP 1741307)]
[New Thread 0x7fff5cff9700 (LWP 1741308)]
[New Thread 0x7fff47fff700 (LWP 1741309)]
[New Thread 0x7fff477fe700 (LWP 1741310)]
[New Thread 0x7fff46ffd700 (LWP 1741311)]
[New Thread 0x7fff467fc700 (LWP 1741312)]
[New Thread 0x7fff45ffb700 (LWP 1741313)]
[New Thread 0x7fff457fa700 (LWP 1741314)]
[New Thread 0x7fff44ff9700 (LWP 1741315)]
[New Thread 0x7fff37fff700 (LWP 1741316)]
[New Thread 0x7fff377fe700 (LWP 1741317)]
[New Thread 0x7fff36ffd700 (LWP 1741318)]
[New Thread 0x7fff367fc700 (LWP 1741319)]
[New Thread 0x7fff35ffb700 (LWP 1741320)]
[New Thread 0x7fff357fa700 (LWP 1741321)]
[New Thread 0x7fff34ff9700 (LWP 1741322)]
[New Thread 0x7fff347f8700 (LWP 1741323)]
[New Thread 0x7fff33ff7700 (LWP 1741324)]
[New Thread 0x7fff337f6700 (LWP 1741325)]
[New Thread 0x7fff32ff5700 (LWP 1741326)]
[New Thread 0x7fff327f4700 (LWP 1741327)]
[New Thread 0x7fff21ff3700 (LWP 1741328)]
[New Thread 0x7fff217f2700 (LWP 1741329)]
[New Thread 0x7fff20ff1700 (LWP 1741330)]
[New Thread 0x7fff207f0700 (LWP 1741331)]
[New Thread 0x7fff1ffef700 (LWP 1741332)]
[New Thread 0x7fff1f7ee700 (LWP 1741333)]
[Thread 0x7fff21ff3700 (LWP 1741328) exited]
[New Thread 0x7fff1efed700 (LWP 1741334)]
[New Thread 0x7fff1e7ec700 (LWP 1741335)]
[New Thread 0x7fff1dfeb700 (LWP 1741336)]
[New Thread 0x7fff1d7ea700 (LWP 1741337)]
[New Thread 0x7fff0cfe9700 (LWP 1741338)]
[New Thread 0x7fff0c7e8700 (LWP 1741339)]
[New Thread 0x7fff0bfe7700 (LWP 1741340)]
[New Thread 0x7fff0a2ab700 (LWP 1741341)]
[New Thread 0x7fff09aaa700 (LWP 1741342)]
[Thread 0x7fff35ffb700 (LWP 1741320) exited]
[Thread 0x7fff33ff7700 (LWP 1741324) exited]
[New Thread 0x7fff33ff7700 (LWP 1741349)]
[New Thread 0x7fff35ffb700 (LWP 1741350)]
[Thread 0x7fffcffff700 (LWP 1741282) exited]
Thread 1 "jami-qt" received signal SIGINT, Interrupt.
futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5555591d0dc4)
at ../sysdeps/nptl/futex-internal.h:183
(gdb) where
#0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5555591d0dc4)
at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common
(abstime=0x0, clockid=0, mutex=0x5555591d0d70, cond=0x5555591d0d98)
at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5555591d0d98, mutex=0x5555591d0d70) at pthread_cond_wait.c:638
#3 0x00007fffea6615ab in QWaitCondition::wait(QMutex*, QDeadlineTimer) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#4 0x00007fffec4de83d in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#5 0x00007fffec4df455 in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#6 0x00007fffeafa2d4b in QWindow::event(QEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#7 0x00007fffec4cc77d in QQuickWindow::event(QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#8 0x00007fffeb963e96 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#9 0x00007fffeb97d268 in QApplication::notify(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#10 0x00007fffea655cea in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#11 0x00007fffeae28ca7 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#12 0x00007fffeafc47b0 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#13 0x00007fffeafc49dc in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#14 0x00007fffe2dc200e in ()
at /usr/lib/libqt-jami/plugins/platforms/../../lib/libQt6XcbQpa.so.6
#15 0x00007ffff754f17d in g_main_context_dispatch ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff754f400 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff754f4a3 in g_main_context_iteration ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fffea704298 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#19 0x00007fffea654b8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#20 0x00007fffea794d83 in QCoreApplication::exec() ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#21 0x00005555555ac79c in main ()
(gdb)
#0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5555591d0dc4)
at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common
(abstime=0x0, clockid=0, mutex=0x5555591d0d70, cond=0x5555591d0d98)
at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5555591d0d98, mutex=0x5555591d0d70) at pthread_cond_wait.c:638
#3 0x00007fffea6615ab in QWaitCondition::wait(QMutex*, QDeadlineTimer) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#4 0x00007fffec4de83d in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#5 0x00007fffec4df455 in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#6 0x00007fffeafa2d4b in QWindow::event(QEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#7 0x00007fffec4cc77d in QQuickWindow::event(QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#8 0x00007fffeb963e96 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#9 0x00007fffeb97d268 in QApplication::notify(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#10 0x00007fffea655cea in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#11 0x00007fffeae28ca7 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#12 0x00007fffeafc47b0 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#13 0x00007fffeafc49dc in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#14 0x00007fffe2dc200e in ()
at /usr/lib/libqt-jami/plugins/platforms/../../lib/libQt6XcbQpa.so.6
#15 0x00007ffff754f17d in g_main_context_dispatch ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff754f400 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff754f4a3 in g_main_context_iteration ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fffea704298 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#19 0x00007fffea654b8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#20 0x00007fffea794d83 in QCoreApplication::exec() ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#21 0x00005555555ac79c in main ()
(gdb)
#0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5555591d0dc4)
at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common
(abstime=0x0, clockid=0, mutex=0x5555591d0d70, cond=0x5555591d0d98)
at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5555591d0d98, mutex=0x5555591d0d70) at pthread_cond_wait.c:638
#3 0x00007fffea6615ab in QWaitCondition::wait(QMutex*, QDeadlineTimer) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#4 0x00007fffec4de83d in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#5 0x00007fffec4df455 in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#6 0x00007fffeafa2d4b in QWindow::event(QEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#7 0x00007fffec4cc77d in QQuickWindow::event(QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#8 0x00007fffeb963e96 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#9 0x00007fffeb97d268 in QApplication::notify(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#10 0x00007fffea655cea in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#11 0x00007fffeae28ca7 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#12 0x00007fffeafc47b0 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#13 0x00007fffeafc49dc in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#14 0x00007fffe2dc200e in ()
at /usr/lib/libqt-jami/plugins/platforms/../../lib/libQt6XcbQpa.so.6
#15 0x00007ffff754f17d in g_main_context_dispatch ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff754f400 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff754f4a3 in g_main_context_iteration ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fffea704298 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#19 0x00007fffea654b8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#20 0x00007fffea794d83 in QCoreApplication::exec() ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#21 0x00005555555ac79c in main ()
(gdb)
#0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5555591d0dc4)
at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common
(abstime=0x0, clockid=0, mutex=0x5555591d0d70, cond=0x5555591d0d98)
at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5555591d0d98, mutex=0x5555591d0d70) at pthread_cond_wait.c:638
#3 0x00007fffea6615ab in QWaitCondition::wait(QMutex*, QDeadlineTimer) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#4 0x00007fffec4de83d in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#5 0x00007fffec4df455 in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#6 0x00007fffeafa2d4b in QWindow::event(QEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#7 0x00007fffec4cc77d in QQuickWindow::event(QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#8 0x00007fffeb963e96 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#9 0x00007fffeb97d268 in QApplication::notify(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#10 0x00007fffea655cea in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#11 0x00007fffeae28ca7 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#12 0x00007fffeafc47b0 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#13 0x00007fffeafc49dc in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#14 0x00007fffe2dc200e in ()
at /usr/lib/libqt-jami/plugins/platforms/../../lib/libQt6XcbQpa.so.6
#15 0x00007ffff754f17d in g_main_context_dispatch ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff754f400 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff754f4a3 in g_main_context_iteration ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fffea704298 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#19 0x00007fffea654b8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#20 0x00007fffea794d83 in QCoreApplication::exec() ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#21 0x00005555555ac79c in main ()
(gdb)
#0 futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x5555591d0dc4)
at ../sysdeps/nptl/futex-internal.h:183
#1 __pthread_cond_wait_common
(abstime=0x0, clockid=0, mutex=0x5555591d0d70, cond=0x5555591d0d98)
at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5555591d0d98, mutex=0x5555591d0d70) at pthread_cond_wait.c:638
#3 0x00007fffea6615ab in QWaitCondition::wait(QMutex*, QDeadlineTimer) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#4 0x00007fffec4de83d in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#5 0x00007fffec4df455 in () at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#6 0x00007fffeafa2d4b in QWindow::event(QEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#7 0x00007fffec4cc77d in QQuickWindow::event(QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Quick.so.6
#8 0x00007fffeb963e96 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#9 0x00007fffeb97d268 in QApplication::notify(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Widgets.so.6
#10 0x00007fffea655cea in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#11 0x00007fffeae28ca7 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#12 0x00007fffeafc47b0 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#13 0x00007fffeafc49dc in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Gui.so.6
#14 0x00007fffe2dc200e in ()
at /usr/lib/libqt-jami/plugins/platforms/../../lib/libQt6XcbQpa.so.6
#15 0x00007ffff754f17d in g_main_context_dispatch ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ffff754f400 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff754f4a3 in g_main_context_iteration ()
at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fffea704298 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#19 0x00007fffea654b8a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#20 0x00007fffea794d83 in QCoreApplication::exec() ()
at /usr/lib/libqt-jami/lib/libQt6Core.so.6
#21 0x00005555555ac79c in main ()
(gdb) quit
A debugging session is active.
Inferior 1 [process 1741273] will be killed.
Quit anyway? (y or n) ySébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/717crash in CallAdapter2022-12-17T02:34:49ZMohamed Chibanicrash in CallAdapter## Describe your environment
Please specify the following:
- OS: Linux
- Jami version: client-qt commit ID 252bc8488c10b72a9652744e2be5f3bc32abbe66
## Steps to reproduce
- Can you reproduce the bug: only once so far
- Steps:
1. Call...## Describe your environment
Please specify the following:
- OS: Linux
- Jami version: client-qt commit ID 252bc8488c10b72a9652744e2be5f3bc32abbe66
## Steps to reproduce
- Can you reproduce the bug: only once so far
- Steps:
1. Call a RDV point
2. Maximize any participant video
- Actual result: crash
- Expected result: no crash
## Additional information
Quick investigation shows that the index provided to CallAdapter::onParticipantUpdated() method is out of range:
```
ASSERT failure in QList::operator[]: "index out of range", file /opt/Qt/6.2.3/gcc_64/include/QtCore/qlist.h, line 412
```
I also noticed that the RDV point continued to display a participant that had previously left the conf (in fact, the participant crashed, so maybe the conf did not update correctly)
[bt.log](/uploads/2263b26416a4211fb3415db92902e355/bt.log)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/716[Question] Do all members of a swarm need to enable small group support or ju...2022-04-08T09:13:11Zovari[Question] Do all members of a swarm need to enable small group support or just the Administrator?Do all members of a small group swarm need to `Enable small group support for Swarm` or just the Administrator?
![image](/uploads/082520ab749b00a5a0bb0efd5b5b29e3/image.png)
Perhaps details like this will be covered in a blog article o...Do all members of a small group swarm need to `Enable small group support for Swarm` or just the Administrator?
![image](/uploads/082520ab749b00a5a0bb0efd5b5b29e3/image.png)
Perhaps details like this will be covered in a blog article on small group support.
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/715[Group swarm] Audio and video call buttons2022-04-08T13:23:46Zovari[Group swarm] Audio and video call buttons![Place audio/video call buttons](/uploads/fa2dcc58d8e7d4b00b11155b43872d49/image.png)
Are the `Place audio call` and `Place video call` buttons planned to be available in a group swarm next to the `Add participants` and `Details` butto...![Place audio/video call buttons](/uploads/fa2dcc58d8e7d4b00b11155b43872d49/image.png)
Are the `Place audio call` and `Place video call` buttons planned to be available in a group swarm next to the `Add participants` and `Details` buttons?
![Group swarm](/uploads/00c9fc1af57a831e86c095ccd4d8d19a/image.png)
`Start video call` and `Start audio call` are available in the contextual menu (by right clicking) of the group swarm; however, nothing seems to happen when clicking on `Start video/audio call`
![Group swarm contextual menu](/uploads/6896ae9209d3e88e2932e4a817bd9ac3/image.png)
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/714The aplication will not start under windows 72022-05-25T20:42:38ZAndrei MikheevThe aplication will not start under windows 7Hello.
Is jami client still supported on windows 7?
Yesterday I have downloaded it from jami.net using the usual windows-release link and tried to start it on several windows 7x64 machines but the error is the same:
"The application was ...Hello.
Is jami client still supported on windows 7?
Yesterday I have downloaded it from jami.net using the usual windows-release link and tried to start it on several windows 7x64 machines but the error is the same:
"The application was unable to start correctly (0xc0000005). Click OK to close the application."
I did not have any issues with older releases. It was working fine until april.
Is it worth of a try to build it from sources using an older visual studio release?https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1299Should ` (deprecated)` be added to this repository?2022-05-13T15:11:46ZovariShould ` (deprecated)` be added to this repository?1. Should ` (deprecated)` be added to this repository?<br>
https://review.jami.net/c/jami-project/+/21349<br>
![image](/uploads/399058da50084b70c37ea2b7798fa4d8/image.png)
2. Should https://jami.net/contributions/ be updated?
Thank you1. Should ` (deprecated)` be added to this repository?<br>
https://review.jami.net/c/jami-project/+/21349<br>
![image](/uploads/399058da50084b70c37ea2b7798fa4d8/image.png)
2. Should https://jami.net/contributions/ be updated?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/713Create a swarm Pencil (or X) not showing with Light theme2022-04-08T13:06:16ZovariCreate a swarm Pencil (or X) not showing with Light themeWith light theme, pencil (or X) not showing for:
1. `Edit title`
2. `Edit description`
![image](/uploads/b1cbe3f82a715f6170ecf911fa194e95/image.png)
Works for dark theme:
![image](/uploads/fc7555c786da787c8709d7ecc4d6b11f/image.png)
...With light theme, pencil (or X) not showing for:
1. `Edit title`
2. `Edit description`
![image](/uploads/b1cbe3f82a715f6170ecf911fa194e95/image.png)
Works for dark theme:
![image](/uploads/fc7555c786da787c8709d7ecc4d6b11f/image.png)
Thank you
Linux Mint 20.3 Cinnamon<br>
Jami-client-qt Version: 202204072338https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/712Distorted video for conferences on video-split2022-04-07T15:35:24ZSébastien BlinDistorted video for conferences on video-split# Scenario
+ Build with --no-libwrap
+ Do a conference, go in one big with small layout
# Expected
Video should be ok
# Current result
video is distorted# Scenario
+ Build with --no-libwrap
+ Do a conference, go in one big with small layout
# Expected
Video should be ok
# Current result
video is distortedhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/730Android: Calling a device around 10 times result in daemon not responding any...2022-08-04T19:21:09ZOlivier DionAndroid: Calling a device around 10 times result in daemon not responding anymore# Devices
- Caller (linux)
- Callee (Android)
# Network topology
Anything. Can be reproduce if both devices are on the same network.
By default, the scenario is run with UPNP and TURN disabled on both devices.
# Symptoms
If y...# Devices
- Caller (linux)
- Callee (Android)
# Network topology
Anything. Can be reproduce if both devices are on the same network.
By default, the scenario is run with UPNP and TURN disabled on both devices.
# Symptoms
If you have any of the following symptoms, it's probably it.
- After around 10 successful calls, the Android device will stop receiving any new call from any peer.
- Toggling the Android account status (online/offline) will keep the green `online` label.
- No peer discovery on the DHT.
# Scenario
1. Call an Android device (can be put in auto-answer mode)
2. Wait a few seconds after picking up the call.
3. Hang up.
4. Reset the connection between the peers by disabling the **caller's** account.
5. Wait a few moment (around 5 seconds) for sockets to be released.
6. Re-enable the caller's account.
7. Jump 1.
There's a [scenario.scm](/uploads/b06305eb52ea5623575f62dd43038ab8/scenario.scm) that automated this process
- You can parameterize the waiting period for the call with `GRACE-PERIOD`
- You can parameterize duration of the call with `MEDIA-FLOW`
- To run the test, call `(run-scenario "result.txt")`.
# Edit 1
From my debugging:
- There's no leak of any file descriptor
- Memory usage is okay and does not seem to have any leak
- Logging continue (for example changing account's preferences)
# Edit 2
Other symptoms:
- Calling a peer from the Android device result in a gray screen (no red hang up button)
- Sending messages to a peer does not show in the conversation history
- In the above case, the peer is never joinedMohamed ChibaniOlivier DionMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/729video-split: remove dummyrtpsession2022-04-07T20:26:42ZAline Gondim Santosvideo-split: remove dummyrtpsessionBefore Video-split we needed a dummy rtp session in order to show audio only participants in the conference ui.
With the mentioned change, we can now remove this dummy session.Before Video-split we needed a dummy rtp session in order to show audio only participants in the conference ui.
With the mentioned change, we can now remove this dummy session.Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/164Is there anybody who could help me to create an SDK for last version of swift...2022-04-07T08:08:21ZAdrian TabIs there anybody who could help me to create an SDK for last version of swift to be able to run openDHT in my application?Is there anybody who could help me to create an SDK for last version of swift to be able to run openDHT in my application?
I'm trying to build using current build scripts and cannot build project.Is there anybody who could help me to create an SDK for last version of swift to be able to run openDHT in my application?
I'm trying to build using current build scripts and cannot build project.https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/163Is there any instructions how to run locally?2022-12-29T16:49:56ZAdrian TabIs there any instructions how to run locally?Is there any instructions how to run locally?
Do you guys have a chat to discuss on iOS current problems?
I would like to helpIs there any instructions how to run locally?
Do you guys have a chat to discuss on iOS current problems?
I would like to helphttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/83Add conversationId2023-03-15T18:37:41ZLarbi GharibAdd conversationIdhttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/82JAMS CA Auto Refresh2023-09-18T19:33:57ZLarbi GharibJAMS CA Auto RefreshLéo Banno-CloutierLéo Banno-Cloutierhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/711Easy to mistakenly delete multiple accounts2022-04-07T16:54:20ZAmin BandaliEasy to mistakenly delete multiple accountsThe account deletion confirmation popup has a serious usability issue, where it's possible to easily mistakenly delete multiple accounts at once: when the delete confirmation dialog is shown and the user clicks on `Delete` to confirm the...The account deletion confirmation popup has a serious usability issue, where it's possible to easily mistakenly delete multiple accounts at once: when the delete confirmation dialog is shown and the user clicks on `Delete` to confirm the deletion, the next account is automatically selected **and** the deletion confirmation dialog **stays open** (at least for a brief period of time), and if the user clicks `Delete` again in that time then that next account will be deleted as well, and so on.
Ways to remedy/fix this:
- disable the `Delete` button immediately after it's clicked (so that it can't be mistakenly clicked again); and
- make sure the popup is closed immediately after `Delete` is clicked, before the deletion is initiated and the next account is selected.Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1093When phone is on silent, jami on android still rings2023-06-16T17:47:05ZAnjandev MomiWhen phone is on silent, jami on android still ringsCurrently, when the phone is on silent, jami still rings and makes noise on incoming call.
If the android phone is silent, jami should respect that and not ring on incoming call. Jami should check whether the system is on vibrate, silen...Currently, when the phone is on silent, jami still rings and makes noise on incoming call.
If the android phone is silent, jami should respect that and not ring on incoming call. Jami should check whether the system is on vibrate, silent, or ringer on and act accordingly.
I can reproduce this bug anytime.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1428jami-qt-mobile client (Qt client for gnu+linux phones)2022-04-04T00:45:56ZJavierjami-qt-mobile client (Qt client for gnu+linux phones)Hi !
For GNU+Linux desktop there's the jami-qt client, but I'm wondering if a GNU+Linux mobile Qt client can be developed. They're not precisely the same, given on desktop the interaction is with mouse and keyboard, whereas on a phone ...Hi !
For GNU+Linux desktop there's the jami-qt client, but I'm wondering if a GNU+Linux mobile Qt client can be developed. They're not precisely the same, given on desktop the interaction is with mouse and keyboard, whereas on a phone it's with touching and tapping, and the phone UI of course is way smaller and vertical (portrait) on phone vs. horizontal (landscape) on the desktop, so I guess the client might have differences...
The focus is on phones like pinephone (pine64) or other GNU+Linux ones.
If the Qt client wroks and adapts well to both desktop and phone, please let me know.
I'm planning on getting a pinephone soon, so it becomes my main phone, so that's why I'm asking.
Thanks !