linux 6.9 breaks at least messaging

I thought I had experienced some Jami regression after I upgraded from jami-all_20240430.0~dfsg1-1_amd64.deb to newer versions a couple of weeks ago on Trisquel 11: I could no longer receive text messages, and those I tried to send no longer made it to recipients. Today, I tried to downgrade Jami to the working version I had on another computer, and I found out it didn't make any difference. What did make a difference was booting on Linux-libre 6.8.8-gnu or 6.8.12-gnu, rather than 6.9.2-gnu or 6.9.3-gnu. ISTM that 6.6.32-gnu ran into the same problem, but I'm not entirely sure.

I noticed, and it might be related, that, on problematic kernel versions, attempting to disable a Jami account, or trying to change advanced settings for that account (say, enabling or disabling the use of a DHT proxy) would freeze jami hard, the window became unresponsive and the process had to be killed. Upon restart, disabling an account had taken effect, but advanced settings changes didn't. It smelled like some deadlock in processing configuration requests. It might be related with the inability to send or receive messages, though I suspect that would likely be a different deadlock.

mentioned in issue #1635 (moved)

This sounds more like a libjami issue. I've added some bug report style sections here and will categorize the issue.

Steps to Reproduce:

1. Upgrade Jami to a newer version on Trisquel 11.
2. Try sending and receiving text messages.
3. Downgrade Jami to jami-all_20240430.0~dfsg1-1_amd64.deb.
4. Test messaging functionality again.
5. Boot into different Linux-libre kernel versions (6.8.8-gnu or 6.8.12-gnu vs. 6.9.2-gnu or 6.9.3-gnu).
6. Try disabling a Jami account or changing advanced settings.

Expected Results:

• Jami should send and receive text messages without issues.
• Disabling accounts and changing advanced settings should not cause the application to freeze.

Actual Results:

• Messaging functionality is broken in newer Jami versions.
• Application freezes when attempting to disable accounts or change advanced settings on problematic kernel versions.

Additional Information:

• The issue might be linked to kernel versions, as the problem persists with 6.9.2-gnu and 6.9.3-gnu, but not with 6.8.8-gnu or 6.8.12-gnu.
• Potential deadlock in processing configuration requests suspected.

added BacklogMedium bug labels

added platformlinux label

closed

moved to jami-daemon#1006 (closed)

mentioned in issue jami-daemon#1007