savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-01-29T18:23:20Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/408Jami not longer installable in Debian testing/bullseye2021-01-29T18:23:20ZJürgen LütersJami not longer installable in Debian testing/bullseyeHi,
I will let you know, that jami is not longer installable in debian testing.
apt-get install jami
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed....Hi,
I will let you know, that jami is not longer installable in debian testing.
apt-get install jami
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
jami : Depends: libappindicator3-1 (>= 0.4.90) but it is not installable
Depends: jami-daemon (= 20210125.1.8b9138c~dfsg1-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@nuc:~# apt-get install libappindicator3-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libappindicator3-1 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'libappindicator3-1' has no installation candidate
root@nuc:~#
root@nuc:~# apt-get install jami-daemon
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
jami-daemon : Depends: libjsoncpp1 (>= 1.7.4) but it is not installable
E: Unable to correct problems, you have held broken packages.
root@nuc:~#https://git.jami.net/savoirfairelinux/jami-project/-/issues/859Jami not starting any longer2020-03-28T18:00:55ZHans MeiserJami not starting any longerJami is not starting any longer on Windows 10 Pro Version 10.0.18363.752.
The eventlog logs an Qt5WebEngineCode.dll error
The log (in german):
Name der fehlerhaften Anwendung: Jami.exe, Version: 0.0.0.0, Zeitstempel: 0x5e7bdc00
Name de...Jami is not starting any longer on Windows 10 Pro Version 10.0.18363.752.
The eventlog logs an Qt5WebEngineCode.dll error
The log (in german):
Name der fehlerhaften Anwendung: Jami.exe, Version: 0.0.0.0, Zeitstempel: 0x5e7bdc00
Name des fehlerhaften Moduls: Qt5WebEngineCore.dll, Version: 5.9.4.0, Zeitstempel: 0x5a607dfa
Ausnahmecode: 0x80000003
Fehleroffset: 0x00000000008fd269
ID des fehlerhaften Prozesses: 0x33d8
Startzeit der fehlerhaften Anwendung: 0x01d6052946ab19af
Pfad der fehlerhaften Anwendung: C:\Program Files\Savoir-Faire Linux\Jami\Jami.exe
Pfad des fehlerhaften Moduls: C:\Program Files\Savoir-Faire Linux\Jami\Qt5WebEngineCore.dll
Berichtskennung: e1702529-53d3-489e-a56a-b1254d74e1bb
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1095Jami on Android, cannot receive calls2022-10-23T21:31:31ZTechno GrooveJami on Android, cannot receive callsPlease specify the following:
- Ring version: 20220311-01
- Device model: Poco F1
- Android version: 11
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will.
- Steps:
1. Open Jami...Please specify the following:
- Ring version: 20220311-01
- Device model: Poco F1
- Android version: 11
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will.
- Steps:
1. Open Jami, ensure it is online. Make a VOIP call, even.
2. Try to call voip number.
- Actual result: call not received.
- Expected result: call received.
## Additional information
The voip provider ran a trace. They said “Your device is not responding to the “INVITE” of our server.”
I last tested inbound calls a few months ago, and it worked. I rarely receive calls, but now I need it to work again.
PS: Thanks for all the great work so far.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/560Jami on Android consumes too much battery2020-01-16T22:56:36ZNokia808Jami on Android consumes too much batteryHi. I test Jami on my Honor 8X mobile (model JSN-L22) with Android 8.1.0 (EMUI 8.2.0).
I noticed that Jami eats the battery very hanger way !Hi. I test Jami on my Honor 8X mobile (model JSN-L22) with Android 8.1.0 (EMUI 8.2.0).
I noticed that Jami eats the battery very hanger way !Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1098Jami on Android F-Edroid version does not access account settings2022-08-30T15:55:38ZnardotesterJami on Android F-Edroid version does not access account settingsThe new version of Jami always crashes and closes when I try to enter the account settings on all my devices.The new version of Jami always crashes and closes when I try to enter the account settings on all my devices.https://git.jami.net/savoirfairelinux/jami-project/-/issues/833Jami on Librem 13 and fairphone2020-06-30T19:52:38ZFelicia Müller-PelzerJami on Librem 13 and fairphoneI've installed Jami both on my Librem 13 (Linux, debian-based) and my fairphone 2, but it's not yet working. When I call myself on the other device (tried it in both directions), the connection is breaking down ("missed outgoing call"). ...I've installed Jami both on my Librem 13 (Linux, debian-based) and my fairphone 2, but it's not yet working. When I call myself on the other device (tried it in both directions), the connection is breaking down ("missed outgoing call"). I can see on the fairphone that the window for the call opens, but it looks a bit such as frozen, and I cannot click anything (e.g. mike). Chat works. Any idea how I could make it work?https://git.jami.net/savoirfairelinux/jami-project/-/issues/998jami on linux laptop cant find camera and doesn't safe documents?2020-06-23T17:12:46ZGitLabboy1jami on linux laptop cant find camera and doesn't safe documents?Hello
i have tried newest version of Jami on my linux laptop for video calling but jami cant find my camera.
i got a black screen and also the led indicator doesn't go on.
Microphone work good
i also discovered that if someone send a...Hello
i have tried newest version of Jami on my linux laptop for video calling but jami cant find my camera.
i got a black screen and also the led indicator doesn't go on.
Microphone work good
i also discovered that if someone send a document or pictures to me i can't open it.
i also i don't have a clue where jami saving these documents (not in download or home folder anyway)https://git.jami.net/savoirfairelinux/jami-project/-/issues/603Jami on Local Network2019-12-03T20:52:30ZKleperJami on Local NetworkWhy does Jami need internet to work? I have been testing the application on a community network that has no internet access but the application does not allow registration, what should I do to make it work without internet access?
Thank youWhy does Jami need internet to work? I have been testing the application on a community network that has no internet access but the application does not allow registration, what should I do to make it work without internet access?
Thank youIteration 8https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/72Jami on Manjaro linux2020-11-14T14:35:00ZAlex77282Jami on Manjaro linuxI installed Jami via pamac and it installs old version of Jami (Live Free or Die - built on 2019-08-31) I look at snap version and it is same and then I look offical site of Jami, I don't see any download option for Manjaro/Arch linux.I installed Jami via pamac and it installs old version of Jami (Live Free or Die - built on 2019-08-31) I look at snap version and it is same and then I look offical site of Jami, I don't see any download option for Manjaro/Arch linux.https://git.jami.net/savoirfairelinux/jami-project/-/issues/933Jami on Manjaro linux2020-04-14T12:16:31ZAlex77282Jami on Manjaro linuxI installed Jami via pamac and it installs old version of Jami (Live Free or Die - built on 2019-08-31) I look at snap version and it is same and then I look offical site of Jami, I don't see any download option for Manjaro/Arch linux.I installed Jami via pamac and it installs old version of Jami (Live Free or Die - built on 2019-08-31) I look at snap version and it is same and then I look offical site of Jami, I don't see any download option for Manjaro/Arch linux.https://git.jami.net/savoirfairelinux/jami-project/-/issues/946Jami on openSUSE Tumbleweed2020-10-23T15:04:39ZenoJami on openSUSE TumbleweedHello
do you have any idea how to run Jami on openSUSE Tumbleweed with Gnome?
In the best installation performed Jami crashes on the home screen with the following error:
**"Could not re-connect to the Jami deamon (dring). Jami will now ...Hello
do you have any idea how to run Jami on openSUSE Tumbleweed with Gnome?
In the best installation performed Jami crashes on the home screen with the following error:
**"Could not re-connect to the Jami deamon (dring). Jami will now quit"**
Do you have any suggestions?https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/836Jami opens incorrectly in restored state, not maximized state2024-02-21T22:03:28ZovariJami opens incorrectly in restored state, not maximized state1. Settings > General > Launch at startup = TRUE
2. Maximize Jami
3. Restart computer
4. Jami incorrectly opens in restored state, not maximized state
Seems to be a regression as Jami used to open maximized when the computer was turned ...1. Settings > General > Launch at startup = TRUE
2. Maximize Jami
3. Restart computer
4. Jami incorrectly opens in restored state, not maximized state
Seems to be a regression as Jami used to open maximized when the computer was turned on.
Thank you
Linux Mint 21 Cinnamon<br>
Jami Version: 202209091508https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/256Jami OSX (Apple) can't do outgoing calls or texts2021-08-19T20:43:47ZArnold BurkesJami OSX (Apple) can't do outgoing calls or textsI am currently using Jami version 1.81 on MacOS Mojave and am recently trying it out.
One thing I just cannot seem to get past is how voice calls can't send out to other people, and even my texts can't send without hanging for minutes on...I am currently using Jami version 1.81 on MacOS Mojave and am recently trying it out.
One thing I just cannot seem to get past is how voice calls can't send out to other people, and even my texts can't send without hanging for minutes on endhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1065Jami OSX (Apple) can't do outgoing calls or texts2020-10-14T23:34:04ZArnold BurkesJami OSX (Apple) can't do outgoing calls or textsI am currently using Jami version 1.81 on MacOS Mojave and am recently trying it out.
One thing I just cannot seem to get past is how voice calls can't send out to other people, and even my texts can't send without hanging for minutes on...I am currently using Jami version 1.81 on MacOS Mojave and am recently trying it out.
One thing I just cannot seem to get past is how voice calls can't send out to other people, and even my texts can't send without hanging for minutes on endhttps://git.jami.net/savoirfairelinux/jami-docs/-/issues/19Jami Plugins certification2023-11-23T16:15:10ZXavier Jouslin de NorayJami Plugins certificationProvide a Jami certificate plugins architecture to be able to verify the authenticity of plugin available in the plugins store.
The documentation have to specified the description of certificate, the certificate chain and the certificate...Provide a Jami certificate plugins architecture to be able to verify the authenticity of plugin available in the plugins store.
The documentation have to specified the description of certificate, the certificate chain and the certificate constraint.Xavier Jouslin de NorayXavier Jouslin de Norayhttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/2Jami Plugin SDK2020-12-11T15:44:13ZAdrien BéraudJami Plugin SDKAllows to create custom Jami plugins, including:
* [x] Documentation about how to create plugins and what they can do
* [x] The build environment and tools to build plugins independently from source
* [x] Tools to build and manipul...Allows to create custom Jami plugins, including:
* [x] Documentation about how to create plugins and what they can do
* [x] The build environment and tools to build plugins independently from source
* [x] Tools to build and manipulate .jpl filesIteration 25Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1448`Jami Privacy Policy` webpage translation2023-12-04T18:10:51Zovari`Jami Privacy Policy` webpage translationAt the [Jami Privacy Policy](https://jami.net/privacy-policy/?lang=fr) webpage, please allow the following to be translated:
1. The webpage title: `Jami Privacy Policy`
2. The paragraph: `Jami offers you a secure and private communicatio...At the [Jami Privacy Policy](https://jami.net/privacy-policy/?lang=fr) webpage, please allow the following to be translated:
1. The webpage title: `Jami Privacy Policy`
2. The paragraph: `Jami offers you a secure and private communication environment. All connections are end-to-end encrypted. We use state of the art end-to-end encryption with perfect forward secrecy for all communications and comply with the X.509 standard. We use TLS/SRTP to secure connection and communications over the network.`
![Jami Privacy Policy webpage](/uploads/aabc0783a6030c866e9a2f2ba8a46abe/image.png)
Thank youAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/908Jami protocols, please2021-08-20T21:03:43ZZulJami protocols, pleaseI am now using Jami, but it's not perfect yet. I am not sure Jami is yet easy-use and easy-maintenance enough for me to ask some of my friends to install it, though I hope it will get there. I also, oddly, feel that it is too centralized...I am now using Jami, but it's not perfect yet. I am not sure Jami is yet easy-use and easy-maintenance enough for me to ask some of my friends to install it, though I hope it will get there. I also, oddly, feel that it is too centralized!
In order to use Jami, [I had to](https://git.jami.net/savoirfairelinux/ring-project/issues/844#note_18790) add the Savoir-faire repository, and download the latest version directly from there. All my friends will have to do the same to keep their versions in sync.
In some ways, this is more centralized than Mumble, which is not peer-to-peer, but has [multiple third-party applications](https://wiki.mumble.info/wiki/3rd_Party_Applications) for both server and client *(Mumble also has [no end-to-end encryption](https://github.com/mumble-voip/mumble/issues/1813); the server operator is a de-facto party to all group calls, so you have to run your own server)*.
A Jami protocol would fix, allowing different versions and implementations to interoperate. It's hard to write a protocol without first writing a prototype implementation. I very much hope that Jami will, like Mediagoblin, eventually spawn a protocol.
Then Jami will be like a peer-to-peer Mumble; we can use different versions, and if a Jami becomes not quite what we want we can seamlessly switch to another program, keeping our contact list and histories. Free as in freedom.
A protocol just for account data storage/import/export would be a good first step; a protocol for the actual messages could come later.https://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/743Jami-qt built with QT6 has some problem on NixOS2022-08-31T01:24:44ZlinsuiJami-qt built with QT6 has some problem on NixOSI'm packaging the new version of jami-qt with QT6. I got some problems.
1. The window's titlebar doesn't follow system theme.
1. The window can't be resized.
1. The wnclass of the window is `net.jami.`.
Could you please help?I'm packaging the new version of jami-qt with QT6. I got some problems.
1. The window's titlebar doesn't follow system theme.
1. The window can't be resized.
1. The wnclass of the window is `net.jami.`.
Could you please help?