savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2024-02-21T20:59:54Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1573Cannot revoke device with password2024-02-21T20:59:54ZSébastien BlinCannot revoke device with password# Scenario
+ Create an account with password
+ Link a new account
+ Try to revoke second device
# Current result
```
default [1708445694959][WRN]: file:qrc:/settingsview/components/RevokeDevicePasswordDialog.qml:39 qrc:/settingsview/c...# Scenario
+ Create an account with password
+ Link a new account
+ Try to revoke second device
# Current result
```
default [1708445694959][WRN]: file:qrc:/settingsview/components/RevokeDevicePasswordDialog.qml:39 qrc:/settingsview/components/RevokeDevicePasswordDialog.qml:39: ReferenceError: passwordEdit is not defined
```
# Expected
Revocation MUST workSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1572Can't accept contact request after removing contact (on same device); Invitat...2024-02-19T18:52:02ZElysCan't accept contact request after removing contact (on same device); Invitation remains even if you select "Block"reproduced using the newest beta version of Jami (desktop and android)
maybe related: https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/855
1:1-Swarm
---
First step:
Desktop: You've removed (NOT blocked) a contact before (s...reproduced using the newest beta version of Jami (desktop and android)
maybe related: https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/855
1:1-Swarm
---
First step:
Desktop: You've removed (NOT blocked) a contact before (so the desktop user won't see contact B (the android user) in the contact anymore).
HOWEVER:
The Android user (=contact B) can still view see the desktop user (=contact A) in the contact list
---
The desktop user has always "Allow calls from unknown contacts" enabled
* Now make a call Android (contact B)-\> Desktop (contact A) and accept the call
* After the call you might have the same invitation twice (only reproduced once)
* but you won't get the username "username1" but an ID like "abcdef12345..."
Now you have mutliple possiblities:
1) The desktop user can't accept the contact request and nothing will happen if you click on "Accept"
2) If the desktop user "blocks" the contact request
a) you (desktop user) won't view any contact request anymore but you will have an invitation forever
b) if you unblock the Android user he will be in your contact list again with the username like "username 1"
3) I think if you decline the next calls you always get an ID like "abcdef12345..." if you accept the next call again
---
The desktop user can only accept the conversation request
* if he blocks the Android user using the conversation request and then unblocks the Android user
OR
* if the Android user (also) removes the desktop user from his contact list and the Android user sends a contact request that can be accepted by the desktop user nowhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1611call notifications: use CallStyle2024-02-28T15:09:30ZAdrien Béraudcall notifications: use CallStyleImplement CallStyle notifications as documented here:
https://developer.android.com/develop/ui/views/notifications/call-styleImplement CallStyle notifications as documented here:
https://developer.android.com/develop/ui/views/notifications/call-styleAdrien BéraudAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1626Android app does not uninstall2024-02-19T15:14:00Zaka. BKMS Data EngineerAndroid app does not uninstallHi,
on Samsung A12 with Android 13 the Jami app can not be removed.
The delete function simply does nothing and the app is still there.
I tried via the delete function when long pressing the apps icon and via the delete function in the a...Hi,
on Samsung A12 with Android 13 the Jami app can not be removed.
The delete function simply does nothing and the app is still there.
I tried via the delete function when long pressing the apps icon and via the delete function in the apps list from the android settings.
Data and cache of the app can be removed but the 102MB app itself is resisting to vanish.
I tried to install Android studio and connected over debug mode. But not having the device rooted I can only see where the apk may be located under the name cx.ring but there are no permissions to actually change something.
On another android device remove works as it should, so there is no general issue, only on that Samsung A12.
So how can I get the app off the device?
Thank you in advance for any help on this.
---
Below some errors from logcat when hitting the uninstall button in android settings apps jami:
I also have an unfiltered log file if you like, but I see no way to attach a file here...
024-02-18 17:40:06.946 966-4428 UserRestrictionsUtils system_server E Unknown restriction queried by uid 1000 (com.samsung.android.svcagent et al): cx.ring
2024-02-18 17:40:06.965 2514-2514 pageboostd pageboostd E Received HALT command code 2
2024-02-18 17:40:07.007 21499-21499 ackageinstaller pid-21499 E Not starting debugger since process cannot load the jdwp agent.
2024-02-18 17:40:07.160 21499-21499 AndroidRuntime pid-21499 E FATAL EXCEPTION: main
Process: com.google.android.packageinstaller, PID: 21499
java.lang.RuntimeException: Unable to start activity
ComponentInfo{com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity}: java.lang.SecurityException: Package
com.google.android.packageinstaller from UID 10084 blocked by mode 1
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4169)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4325)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2574)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8762)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
Caused by: java.lang.SecurityException: Package com.google.android.packageinstaller from UID 10084 blocked by mode 1
at android.os.Parcel.createExceptionOrNull(Parcel.java:3023)
at android.os.Parcel.createException(Parcel.java:3007)
at android.os.Parcel.readException(Parcel.java:2990)
at android.os.Parcel.readException(Parcel.java:2932)
at android.app.usage.IStorageStatsManager$Stub$Proxy.queryStatsForPackage(IStorageStatsManager.java:504)
at android.app.usage.StorageStatsManager.queryStatsForPackage(StorageStatsManager.java:213)
at com.android.packageinstaller.handheld.UninstallAlertDialogFragment.getAppDataSizeForUser(UninstallAlertDialogFragment.java:68)
at com.android.packageinstaller.handheld.UninstallAlertDialogFragment.getAppDataSize(UninstallAlertDialogFragment.java:101)
at com.android.packageinstaller.handheld.UninstallAlertDialogFragment.onCreateDialog(UninstallAlertDialogFragment.java:174)
at android.app.DialogFragment.onGetLayoutInflater(DialogFragment.java:418)
at android.app.Fragment.performGetLayoutInflater(Fragment.java:1322)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1303)
at android.app.FragmentManagerImpl.addAddedFragments(FragmentManager.java:2431)
at android.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2210)
at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2166)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2067)
at android.app.FragmentManagerImpl.dispatchMoveToState(FragmentManager.java:3057)
at android.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java:3004)
at android.app.FragmentController.dispatchActivityCreated(FragmentController.java:185)
at android.app.Activity.performCreate(Activity.java:8599)
at android.app.Activity.performCreate(Activity.java:8570)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1384)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4150)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4325)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2574)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8762)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.usage.StorageStatsService.enforceStatsPermission(StorageStatsService.java:210)
at com.android.server.usage.StorageStatsService.queryStatsForPackage(StorageStatsService.java:350)
at android.app.usage.IStorageStatsManager$Stub.onTransact(IStorageStatsManager.java:264)
at android.os.Binder.execTransactInternal(Binder.java:1316)
at android.os.Binder.execTransact(Binder.java:1280)
2024-02-18 17:40:07.264 21373-21410 [WEATHER]StoreEntity com.sec.android.daemonapp E {[4D63BA3A7171858DA5D3F9375C43492DDF25E5A1AD7D8FEF26A2A3C27FCA533645F81B5C97AD32F6DE1997D8427A3FBD7EE391994595DCDB9D5908B6D97E8DA4]}
2024-02-18 17:40:08.284 966-3583 TaskPersister system_server E File error accessing recents directory (directory doesn't exist?).
2024-02-18 17:40:08.284 966-3583 TaskPersister system_server E File error accessing recents directory (directory doesn't exist?).
2024-02-18 17:40:16.326 632-632 sehhealth-service ven...msung.hardware.health-service E Could not open /sys/class/power_supply/battery/lrp
2024-02-18 17:40:16.335 1319-2303 SecPowerUI.Notification com.android.systemui E no saved value, so we do nothing !!
2024-02-18 17:40:17.000 966-992 Watchdog system_server E !@Sync: 356 heap: 99 / 112 FD: 953 [2024-02-18 17:40:16.999]
2024-02-18 17:40:23.172 966-1103 CAE system_server E parse(SensorHubModeHandler.java:72) - ERROR : Service is not registered
2024-02-18 17:40:23.173 966-1103 CAE system_server E onGetSensorHubData(SensorHubParserProvider.java:112) - ERROR : Data field parsing errorhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/347account could receive notifications for conversation with blocked contacts2024-02-16T14:52:23ZKateryna Kostiukaccount could receive notifications for conversation with blocked contactshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1571Wrong date for conversation requests2024-02-21T21:00:00ZSébastien BlinWrong date for conversation requests# Scenario
Receive an invite
# Current result
Date is UNIX timestamp 0 (so 31-12-1969)
## Expected
A fake interaction should be added with received date for the contact request# Scenario
Receive an invite
# Current result
Date is UNIX timestamp 0 (so 31-12-1969)
## Expected
A fake interaction should be added with received date for the contact requesthttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1610Implement navigation component2024-02-15T18:17:34ZPierre NicolasImplement navigation componentIn my opinion, best way to manage navigation between screens:
https://medium.com/@jimohzainab4753/the-navigation-component-not-that-hard-ca705cf4326
https://developer.android.com/guide/navigationIn my opinion, best way to manage navigation between screens:
https://medium.com/@jimohzainab4753/the-navigation-component-not-that-hard-ca705cf4326
https://developer.android.com/guide/navigationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1609Delete account doesn't exit setting page2024-02-27T13:32:35ZPierre NicolasDelete account doesn't exit setting page## Describe your environment
Please specify the following:
- Jami version: 404
![Screen_recording_20240215_120525](/uploads/4618a9185f99c31a056ab2ab9dd005e3/Screen_recording_20240215_120525.mp4)## Describe your environment
Please specify the following:
- Jami version: 404
![Screen_recording_20240215_120525](/uploads/4618a9185f99c31a056ab2ab9dd005e3/Screen_recording_20240215_120525.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1608About Jami - credit section discussion2024-02-15T16:54:12ZPierre NicolasAbout Jami - credit section discussionShould we regroup everyone under "developed by" section or should we have specific section such as:
* Ringtones
* Design
* ... ?
![image](/uploads/1d77a1ea591c46c2127b0fb33771819a/image.png)
![image](/uploads/3f1e15cf95c2dd089fc3b646d...Should we regroup everyone under "developed by" section or should we have specific section such as:
* Ringtones
* Design
* ... ?
![image](/uploads/1d77a1ea591c46c2127b0fb33771819a/image.png)
![image](/uploads/3f1e15cf95c2dd089fc3b646d0f67081/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1570Smartlist: Last interaction should include peer name for swarms2024-02-21T20:13:04ZAndreas TraczykSmartlist: Last interaction should include peer name for swarmsCurrently the snippet is preceded by a time value:
![image](/uploads/40be20ca26d0059578529f5554161cc7/image.png)Currently the snippet is preceded by a time value:
![image](/uploads/40be20ca26d0059578529f5554161cc7/image.png)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/950--disable-natpmp doesn't work anymore2024-02-15T14:34:27ZSébastien Blin--disable-natpmp doesn't work anymoreprobably since it's done in dhtnetprobably since it's done in dhtnethttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1569Conference: local preview doesn't show when a conference is reduced to a 1:1 ...2024-02-15T09:09:32ZAndreas TraczykConference: local preview doesn't show when a conference is reduced to a 1:1 call- Jami version: master
## Steps to reproduce
- Steps:
1. start a conference of 3 (local video)
2. 1 participant leaves
- Actual result: no local preview is shown
- Expected result: the floating local preview should show- Jami version: master
## Steps to reproduce
- Steps:
1. start a conference of 3 (local video)
2. 1 participant leaves
- Actual result: no local preview is shown
- Expected result: the floating local preview should showhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1568Application remains hidden when open conversation called from notification.2024-02-21T20:23:08ZKessler DuPont-TeevinApplication remains hidden when open conversation called from notification.How to report a bug
-------------------
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update...How to report a bug
-------------------
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue instead of creating new one.
Bug report form
---------------
## Describe your environment
Please specify the following:
- OS: Fedora Asahi Remix
- Jami version: Elutheria (202402141206)
- What build you are using: client-qt compiled from source on 14-02-2024 [jami.net | A store | your own (please specify commit for daemon/lrc/client-qt)...]
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: [at will | occasionally | not at all]
- Steps:
1. Launch Jami
2. Minimize Jami or move to another virtual desktop
3. Receive notification that has 'Open conversation'
4. Click 'Open conversation' button
...
- Actual result: tray icon flashes
- Expected result: application should present itself and navigate to conversation of the notification
## Additional information
![screenshot of notification with open conversation button](https://drive.proton.me/urls/6J9025JF3C#zPaDjYozIumF)
Screenshots/videos/logs/etc
For retrieving logs, cf [this page](https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs).Kessler DuPont-TeevinKessler DuPont-Teevinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1567Can't run Jami on aarch64 Linux2024-02-21T20:13:20ZKessler DuPont-TeevinCan't run Jami on aarch64 LinuxHow to report a bug
-------------------
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update...How to report a bug
-------------------
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue instead of creating new one.
Bug report form
---------------
## Describe your environment
Please specify the following:
- OS: GNU/Linux
- Jami version:
- What build you are using: [jami.net | A store | your own (please specify commit for daemon/lrc/client-qt)...]
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: [at will | occasionally | not at all]
- Steps:
1. log in
2. compile Jami from source
3. run Jami
...
- Actual result: `Error creating shared memory: "QSharedMemory::attach (shmget): doesn't exist"` & StartUri is null
- Expected result: Jami runs
## Additional information
Screenshots/videos/logs/etc
For retrieving logs, cf [this page](https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs).Kessler DuPont-TeevinAndreas TraczykKessler DuPont-Teevinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1606Again, the message is not sent2024-03-19T13:53:01ZFairKingAgain, the message is not sent## Describe your environment
Please specify the following:
- Jami version: 20240206-01
- Device model: Motorola Macro
- Android version: Android 10
- What build you are using: F-droid
## Steps to reproduce
- Can you reprodu...## Describe your environment
Please specify the following:
- Jami version: 20240206-01
- Device model: Motorola Macro
- Android version: Android 10
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. Send a text message to a contact
2. That contact shown as online (green dot)
3. That contact does not receive the message
## Additional information
I could not understand what is the purpose of Online dot. Does it mean that the contact has Jami running and reachable? If yes why the contact does not receive my message? Also my local desktop version does not show that that message was sent from Android, there is not history.
Desktop:
Contact shown as online:
![image](/uploads/5933817c088e2fd43c03766d23918fdf/image.png)
![image](/uploads/15a7dd6ef5b455de583b0551a8e08d4f/image.png)
Android:
Contact shown as online:
![image](/uploads/7ccedb48de43285d12ab7e72c81efe3b/image.png)
The contact didn't receive that last message. He is using Android.
Is there any way to produce a bug report? What is going on with that message?
It is no first time. It is happening constantly and it is so annoying.
Please fix it.
Related issues: #1379, #1378https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1566Input box UI display fault2024-03-13T15:23:28Zsession 21Input box UI display fault![image.png](/uploads/394ef834a18d9ffe987bfe15378f8835/image.png)![image](/uploads/2b6b520e3b83681792578e6bd5e51823/image.png)
Version: 202402091720
Win10
As shown in the picture, this UI is too strange.
When we input a long piece of...![image.png](/uploads/394ef834a18d9ffe987bfe15378f8835/image.png)![image](/uploads/2b6b520e3b83681792578e6bd5e51823/image.png)
Version: 202402091720
Win10
As shown in the picture, this UI is too strange.
When we input a long piece of text, the input box expands, which is reasonable.
However, after expansion, the input box was not restored to its original state in a timely manner, resulting in some flaws in the UI.
According to our habit, the input box should be restored to its original state after we send the message.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1605Jami404 version cannot modify contact note names2024-02-16T02:35:09Zsession 21Jami404 version cannot modify contact note namesJami on Android is unable to modify the note names of contacts. When there are too many contacts, it may cause significant inconvenience for our use.Jami on Android is unable to modify the note names of contacts. When there are too many contacts, it may cause significant inconvenience for our use.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1604404 version cannot open links and videos by clicking2024-02-14T15:27:04Zsession 21404 version cannot open links and videos by clickingThe 404 version cannot open links and videos by clicking, which makes the videos appear too small. I think any version after 399 can reproduce this issue.The 404 version cannot open links and videos by clicking, which makes the videos appear too small. I think any version after 399 can reproduce this issue.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1565webm malformed? Record seems stuck on video2024-02-12T14:05:17ZSébastien Blinwebm malformed? Record seems stuck on video# Scenario
+ Record a video message and send it
+ Video will stuck after a few seconds.
Original post:
Bon soir everybody,
maybe someone has an idea of what could be wrong with my video messages in jami, thanks in advance:
+ Start J...# Scenario
+ Record a video message and send it
+ Video will stuck after a few seconds.
Original post:
Bon soir everybody,
maybe someone has an idea of what could be wrong with my video messages in jami, thanks in advance:
+ Start Jami by clicking on the desktop icon
+ Start a new chat conversation with anyone
+ Click the plus icon near the chat/text field
+ Choose “video message”
+ Start recording video message
+ While recording the cam is totally fine and active (moving webcam image)
+ Click Send-Button and the webm video got send
Expected results: That it works like the simple Audio Message also work.
Actual results: The receiving chat partner (Android Client from F-Droid) and myself are not capable to view the whole video, the video image hooks up in about a few seconds. For example a 10 second video stops at about 2 seconds (reproducible). A 30 second video stops at about 6 seconds (reproducible). The audio is still hearable till the end of the recorded file, but the video image hooked up.
+ I saved the webm file on the home folder and tried to play it with for example VLC player, but the file acts like IN jami, the audio in it works well but the video image hooked up at the same position.
+ Then i tried the app Cheese (linux webcam viewer) and created and tested a webm file there => works well, no problems.
+ Everything tested with a fresh bootet linux mint, no other programs startet (like firefox or other apps that could probably use the webcam or a video encoder)
```
OS: Linux Mint 21.1 x86_64
Host: 23257BG ThinkPad X230
Kernel: 5.15.0-92-generic
DE: Cinnamon 5.6.8
jami -v
Jami 202401241338
```
(deb file downloaded from the jami.net website)
I searched the logs for “webm” and this is what i get (maybe it helps but looks not so harmful to me):
```
jami[35206]: Start recording '/home/xxxxxx/.local/share/jami//sent_data/20240208-165320-1148464275.webm'
jami[35206]: Stop recording '/home/xxxxxx/.local/share/jami//sent_data/20240208-165320-1148464275.webm'
jami[35206]: [Account 801a08d745a01b38] New channel asked with name data-transfer://50dacd71f053d0dee4db4cc2ec990dcaccf8da57/a9a49d3c9d003873b7cafb23e20a1756afd0cf5f9f80ceb7416f2f19cbde1a88/1ff9baefb9626a8c451f35c4095582229964c2a9_977636178449915.webm?start=1769445&end=0
jami[35206]: [Account 801a08d745a01b38] New channel asked with name data-transfer://50dacd71f053d0dee4db4cc2ec990dcaccf8da57/f97b33ba3d7403065b203a88ff1a7295c2805ae36838db2696dcffe84945355d/1ff9baefb9626a8c451f35c4095582229964c2a9_977636178449915.webm?start=1572840&end=0
jami[35206]: [Account 801a08d745a01b38] New channel asked with name data-transfer://50dacd71f053d0dee4db4cc2ec990dcaccf8da57/a9a49d3c9d003873b7cafb23e20a1756afd0cf5f9f80ceb7416f2f19cbde1a88/0fda3f1d436e41253f0a3024484700b4e3f67a77_4046139996379326.webm
jami[35206]: [Account 801a08d745a01b38] New channel asked with name data-transfer://50dacd71f053d0dee4db4cc2ec990dcaccf8da57/f97b33ba3d7403065b203a88ff1a7295c2805ae36838db2696dcffe84945355d/0fda3f1d436e41253f0a3024484700b4e3f67a77_4046139996379326.webm
jami[35206]: New file received: /home/xxxxxx/.local/share/jami/801a08d745a01b38/conversation_data/50dacd71f053d0dee4db4cc2ec990dcaccf8da57/402318ad71c7015ccbc6d281a31ada5917c1fd52_1389764186412915.webm
jami[35206]: [Account 801a08d745a01b38] New channel asked with name data-transfer://50dacd71f053d0dee4db4cc2ec990dcaccf8da57/f97b33ba3d7403065b203a88ff1a7295c2805ae36838db2696dcffe84945355d/0fda3f1d436e41253f0a3024484700b4e3f67a77_4046139996379326.webm
jami[35206]: [Account 801a08d745a01b38] New channel asked with name data-transfer://50dacd71f053d0dee4db4cc2ec990dcaccf8da57/f97b33ba3d7403065b203a88ff1a7295c2805ae36838db2696dcffe84945355d/0fda3f1d436e41253f0a3024484700b4e3f67a77_4046139996379326.webm
jami[35206]: [Account 801a08d745a01b38] New channel asked with name data-transfer://50dacd71f053d0dee4db4cc2ec990dcaccf8da57/f97b33ba3d7403065b203a88ff1a7295c2805ae36838db2696dcffe84945355d/1ff9baefb9626a8c451f35c4095582229964c2a9_977636178449915.webm
```
PS: I tried also to check the log function out of jami, but this seems to be a bit buggy and hook up all the time after some seconds.
Merci beaucoup, muito obrigado, thanks so much, vielen Dank.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1564Jami quits when closed on KDE2024-02-21T20:57:51ZPierre MétrasJami quits when closed on KDE## Describe your environment
Please specify the following:
- OS: Debian 12.5 bookworm using KDE Plasma desktop
- Jami version: Eleutheria Version: 202311232042
- What build you are using: Package from jami.net repository
```
$ dpkg -l ...## Describe your environment
Please specify the following:
- OS: Debian 12.5 bookworm using KDE Plasma desktop
- Jami version: Eleutheria Version: 202311232042
- What build you are using: Package from jami.net repository
```
$ dpkg -l | grep jami
ii jami 20231123.0~dfsg1-1 amd64 Secure and distributed voice, video and chat platform - desktop client
ii jami-daemon 20231123.0~dfsg1-1 amd64 Secure and distributed voice, video and chat platform - daemon
ii libqt-jami 6.4.3-3 amd64 Custom build of Qt framework used by the Jami Qt client.
```
## Steps to reproduce
Note: Better the scenario is, better we will be able to reproduce and debug.
- Can you reproduce the bug: at will
- Steps:
1. Start Jami or have it auto-launched at system startup
2. Jami window opens and Jami appears in the status area ![image](/uploads/8e885b38add54f5c397de79fb301bc94/image.png)
2. Close Jami window.
3. Jami does not stay active and its icon disappears from the status area. The device is no more reachable because Jami has quit.
- Actual result: Jami does not stay active
- Expected result: With a Gnome desktop, Jamy stay active and can receive calls.
## Additional information
It could be a KDE bug as some other applications exhibit strange behaviours regarding the status area too:
* Anydesk icon is visible but the application can't be lanched from the icon.
* Vorta backup does not stay active too.
I can provide a log if necessary.