briar issueshttps://code.briarproject.org/groups/briar/-/issues2023-02-13T17:06:57Zhttps://code.briarproject.org/briar/briar-desktop/-/issues/482Test builds can't be closed after enabling mailbox flag2023-02-13T17:06:57ZTorsten GroteTest builds can't be closed after enabling mailbox flagThe following discussion from !302 should be addressed:
- [ ] @sebkur started a [discussion](https://code.briarproject.org/briar/briar-desktop/-/merge_requests/302#note_74977): (+4 comments)
> maybe I was a bit too quick with this...The following discussion from !302 should be addressed:
- [ ] @sebkur started a [discussion](https://code.briarproject.org/briar/briar-desktop/-/merge_requests/302#note_74977): (+4 comments)
> maybe I was a bit too quick with this one. I just ran the app to see if groups also appear in the UI. They do, which is fine, but I also noticed the app does no longer shut down properly using the X window icon. Maybe the mailbox enabled does something unexpected. First we should find out if it's related to mailbox enabling or groups I guess.
This does not happen for release builds it seems. So a test specific issue.https://code.briarproject.org/briar/briar-mailbox/-/issues/187Add cancel button in STARTING state2023-03-13T14:23:03ZTorsten GroteAdd cancel button in STARTING stateTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2412Research UWB integration2023-03-15T12:30:45ZVladislavResearch UWB integrationResearch possibility of integration Ultra-Wideband technology.
Find out its strengths and the opportunities it can provide.
Possibilities of combining Bluetooth and UWB.Research possibility of integration Ultra-Wideband technology.
Find out its strengths and the opportunities it can provide.
Possibilities of combining Bluetooth and UWB.https://code.briarproject.org/briar/briar-desktop/-/issues/479Forum: Allow copying of message text2023-02-13T13:35:38ZMikolai GütschowForum: Allow copying of message textSimilar to what's possible for private chats.
Slightly related to (might run into same issues as) #355Similar to what's possible for private chats.
Slightly related to (might run into same issues as) #355Desktop 0.4.1Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/477Second login attempt after failed startup results in infinite loading screen2023-02-24T13:50:45ZMikolai GütschowSecond login attempt after failed startup results in infinite loading screenExperienced with the known database migration issue and version 0.4.0 on an old database.
The error screen is correctly shown, but allows to go back:
![image](/uploads/205466faf066bf4afc031ccca4d12137/image.png)
After entering the pas...Experienced with the known database migration issue and version 0.4.0 on an old database.
The error screen is correctly shown, but allows to go back:
![image](/uploads/205466faf066bf4afc031ccca4d12137/image.png)
After entering the password again, the loading screen stays forever and logs show:
```
14:44:19.987 [pool-1-thread-1] WARN o.b.b.desktop.login.StartupViewModel - Startup failed: SERVICE_ERROR
14:45:05.036 [pool-1-thread-1] WARN o.b.b.lifecycle.LifecycleManagerImpl - Already running
14:45:05.037 [pool-1-thread-1] INFO o.b.b.desktop.login.StartupViewModel - Already running
```Desktop 0.4.1SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/474Missing padding in introduction contact list2023-01-31T12:06:52ZMikolai GütschowMissing padding in introduction contact list![image](/uploads/aa16f4cf1323736a9133d76222834f5f/image.png)![image](/uploads/aa16f4cf1323736a9133d76222834f5f/image.png)Desktop 0.4.0Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/473Issues with MAX_INVITATION_TEXT_LENGTH2023-01-31T12:50:16ZMikolai GütschowIssues with MAX_INVITATION_TEXT_LENGTHAlthough we check for and trim (forum) invitation messages to MAX_INVITATION_TEXT_LENGTH, I am able to trigger a `FormatException` when using text copied from https://gutenberg.ca/ebooks/huxleya-bravenewworld/huxleya-bravenewworld-00-h.h...Although we check for and trim (forum) invitation messages to MAX_INVITATION_TEXT_LENGTH, I am able to trigger a `FormatException` when using text copied from https://gutenberg.ca/ebooks/huxleya-bravenewworld/huxleya-bravenewworld-00-h.html, with the text provided to Briar core being too long:
```
12:06:53.175 [pool-1-thread-55] INFO o.b.b.s.v.ValidationManagerImpl - org.briarproject.bramble.api.sync.InvalidMessageException: org.briarproject.bramble.api.FormatException
org.briarproject.bramble.api.sync.InvalidMessageException: org.briarproject.bramble.api.FormatException
at org.briarproject.bramble.api.client.BdfMessageValidator.validateMessage(BdfMessageValidator.java:57)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl.validateMessage(ValidationManagerImpl.java:240)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl.lambda$validateMessageAsync$4(ValidationManagerImpl.java:225)
at org.briarproject.bramble.PoliteExecutor.lambda$execute$0(PoliteExecutor.java:57)
at org.briarproject.bramble.TimeLoggingExecutor.lambda$execute$0(TimeLoggingExecutor.java:38)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.briarproject.bramble.api.FormatException: null
at org.briarproject.bramble.util.ValidationUtils.checkLength(ValidationUtils.java:20)
at org.briarproject.briar.sharing.SharingValidator.validateInviteMessage(SharingValidator.java:70)
at org.briarproject.briar.sharing.SharingValidator.validateMessage(SharingValidator.java:46)
at org.briarproject.bramble.api.client.BdfMessageValidator.validateMessage(BdfMessageValidator.java:53)
... 7 common frames omitted
```
This error is not visible to the user, **but the message is still added to the local database**.
Using text from https://ctext.org/huainanzi/dao-ying-xun with Chinese characters, I was able to trigger a different error:
```
12:05:20.359 [pool-2-thread-54] WARN o.b.b.d.threading.BriarExecutorsImpl - Unhandled exception in database executor
java.lang.IllegalArgumentException: null
at org.briarproject.bramble.sync.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:41)
at org.briarproject.briar.sharing.MessageEncoderImpl.encodeInviteMessage(MessageEncoderImpl.java:120)
at org.briarproject.briar.sharing.ProtocolEngineImpl.sendInviteMessage(ProtocolEngineImpl.java:143)
at org.briarproject.briar.sharing.ProtocolEngineImpl.onLocalInvite(ProtocolEngineImpl.java:113)
at org.briarproject.briar.sharing.ProtocolEngineImpl.onInviteAction(ProtocolEngineImpl.java:98)
at org.briarproject.briar.sharing.SharingManagerImpl.sendInvitation(SharingManagerImpl.java:298)
at org.briarproject.briar.desktop.forums.sharing.ForumSharingViewModel$shareForum$1.invoke(ForumSharingViewModel.kt:146)
at org.briarproject.briar.desktop.forums.sharing.ForumSharingViewModel$shareForum$1.invoke(ForumSharingViewModel.kt:142)
at org.briarproject.briar.desktop.threading.BriarExecutorsImpl.onDbThreadWithTransaction$lambda$1(BriarExecutorsImpl.kt:68)
at org.briarproject.bramble.TimeLoggingExecutor.lambda$execute$0(TimeLoggingExecutor.java:38)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
```
In that case, the message was neither sent not added to the local database.
The issue might be related to the fact that briar core checks the message length on utf8 bytes, while the UI trims according to `String::length`.Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/472NoticeMessageItem is not added to open contact list after sharing forum2023-03-10T08:54:48ZMikolai GütschowNoticeMessageItem is not added to open contact list after sharing forumTo reproduce:
1. Open chat with contact A
2. Switch to forums in the sidebar
3. share a forum with contact A
4. switch back to private messages
5. notice that the chat with contact A is still open, but the info message, that the forum h...To reproduce:
1. Open chat with contact A
2. Switch to forums in the sidebar
3. share a forum with contact A
4. switch back to private messages
5. notice that the chat with contact A is still open, but the info message, that the forum has been shared, is not shown
6. switch to another contact B and back to contact A, see the info messageDesktop 0.4.1https://code.briarproject.org/briar/briar-desktop/-/issues/471windows download broken2023-02-01T13:48:36ZMeow Geffenwindows download brokenhttps://code.briarproject.org/briar/briar-mailbox/-/issues/186Add support for Snowflake2023-03-29T13:41:38ZakwizgranAdd support for SnowflakeTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/185Add Gradle task for verifying translations2023-04-20T09:36:48ZakwizgranAdd Gradle task for verifying translationsAdd a Gradle task for verifying the translations, similar to the one we have for Briar.Add a Gradle task for verifying the translations, similar to the one we have for Briar.Mailbox: ReleaseTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/184Add Mailbox strings to Transifex2023-02-07T13:24:02ZakwizgranAdd Mailbox strings to TransifexMailbox: ReleaseTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/183ContactsManagerIntegrationTest is flaky2023-04-20T09:39:50ZSebastianContactsManagerIntegrationTest is flakySometimes, these checks fail on the CI:
* `ContactsManagerIntegrationTest > get contacts is initially empty() FAILED`
* `ContactsManagerIntegrationTest > owner can add contacts() FAILED`
Usually, a restart of the pipeline has fixed this...Sometimes, these checks fail on the CI:
* `ContactsManagerIntegrationTest > get contacts is initially empty() FAILED`
* `ContactsManagerIntegrationTest > owner can add contacts() FAILED`
Usually, a restart of the pipeline has fixed this.
Examples:
* https://code.briarproject.org/briar/briar-mailbox/-/jobs/25250
* https://code.briarproject.org/briar/briar-mailbox/-/jobs/24937
* https://code.briarproject.org/briar/briar-mailbox/-/jobs/25241
I have not been able to reproduce this locally yet.Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/182No logs on Android since minification is enabled2023-01-27T11:40:24ZSebastianNo logs on Android since minification is enabledMailbox: ReleaseSebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/465Enable forum feature flag for release build2023-01-31T09:04:48ZMikolai GütschowEnable forum feature flag for release buildDesktop 0.4.0Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-desktop/-/issues/464Differing UI for ContactListItemView and ForumItemView2023-01-31T08:52:28ZMikolai GütschowDiffering UI for ContactListItemView and ForumItemViewPadding around the items and verticalAlignment of the circles are different. We should probably decide on one and use that style consistently.
![image](/uploads/725fdaa23479b9f60f2d1a58fec6a4bd/image.png)
![image](/uploads/2f174f636bff9...Padding around the items and verticalAlignment of the circles are different. We should probably decide on one and use that style consistently.
![image](/uploads/725fdaa23479b9f60f2d1a58fec6a4bd/image.png)
![image](/uploads/2f174f636bff9525e77bc421e1e2c70a/image.png)Desktop 0.4.0Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/457Remove open option for answered forum invitations2023-01-23T13:23:37ZMikolai GütschowRemove open option for answered forum invitationsAs a fix for #453 until we decide on some support for navigating from one screen to another.As a fix for #453 until we decide on some support for navigating from one screen to another.Desktop 0.4.0Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/456Consistent naming "Briar" throughout app2023-02-05T22:26:35ZMikolai GütschowConsistent naming "Briar" throughout appThe following discussion from !274 should be addressed:
- [ ] @ialokim started a [discussion](https://code.briarproject.org/briar/briar-desktop/-/merge_requests/274#note_73755): (+3 comments)
> While trying out the installer gener...The following discussion from !274 should be addressed:
- [ ] @ialokim started a [discussion](https://code.briarproject.org/briar/briar-desktop/-/merge_requests/274#note_73755): (+3 comments)
> While trying out the installer generated by the CI, I noticed we use "Briar" as the application name during installation and also for the `.desktop` file for Linux, but the title of the main window is "Briar Desktop". Not sure if we should instead be consistent.
TL;DR: We probably want to use "Briar" everywhere instead of "Briar Desktop".Desktop 0.4.1SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/455Upgrade Compose to 1.3.02023-02-17T17:19:03ZMikolai GütschowUpgrade Compose to 1.3.0see https://github.com/JetBrains/compose-jb/releases/tag/v1.3.0see https://github.com/JetBrains/compose-jb/releases/tag/v1.3.0Mikolai GütschowMikolai Gütschowhttps://code.briarproject.org/briar/briar-desktop/-/issues/454Consider building for Raspberry Pi (arm64)2023-04-15T18:55:29ZMikolai GütschowConsider building for Raspberry Pi (arm64)We got the following mail some time back. I guess this should be quite easy when using pinpit after !274 is merged, @sebkur?
---
Dear Briar team,
for some time I have been following the development of the Briar app. First it was th...We got the following mail some time back. I guess this should be quite easy when using pinpit after !274 is merged, @sebkur?
---
Dear Briar team,
for some time I have been following the development of the Briar app. First it was the Android app only, which I use on a regular basis for some time now. Recently I'm trying to include the Linux desktop into my Briar environment. My intention was to run the desktop version of the Briar app on a Raspberry Pi system.
But the app crashes right at the start during initialization. After some searching the net I think the issue may be minor and could (possibly, hopefully) be easily fixed. (If not, please excuse my ignorance, I'm not a programmer).
There are two links with hints to a possible resolve for the issue:
- https://github.com/JetBrains/compose-jb/issues/1170
- https://stackoverflow.com/questions/70150052/org-jetbrains-skiko-libraryloadexception-cannot-find-libskiko-macos-arm64-dylib
According to these links, somewhere in the sources a call like this may be present:
`implementation(compose.desktop.currentOs)`
It may help to replace it with:
`implementation(compose.desktop.linux_arm64)`
Or with some kind of dynamic reference to the OS it is run on.
As can be seen with `uname -a` (see below) the architecture seems to identify itself as `aarch64`, not as `arm64` as seen in the exception error text.
Here is what I get when I try to start the app:
----------------------------------------------------------------------
```
> java -jar Briar-Desktop.jar
22:32:18.679 [main] INFO org.briarproject.briar.desktop.Main - This is briar-desktop version 0.3.0-beta
22:32:18.690 [main] INFO org.briarproject.briar.desktop.Main - Build info:
22:32:18.692 [main] INFO org.briarproject.briar.desktop.Main - Git hash 0a8c574cdd0942bee6fe709e0987a56c0360d349
22:32:18.697 [main] INFO org.briarproject.briar.desktop.Main - Commit time 2022-09-30 13:50:28
22:32:18.700 [main] INFO org.briarproject.briar.desktop.Main - Tag 0.3.0-beta
Exception in thread "main" java.lang.ExceptionInInitializerError
at androidx.compose.ui.awt.ComposeLayer.<init>(ComposeLayer.desktop.kt:72)
at androidx.compose.ui.awt.ComposeWindowDelegate.<init>(ComposeWindowDelegate.desktop.kt:50)
at androidx.compose.ui.awt.ComposeWindow.<init>(ComposeWindow.desktop.kt:43)
at androidx.compose.ui.awt.ComposeWindow.<init>(ComposeWindow.desktop.kt:40)
at androidx.compose.ui.window.Window_desktopKt$Window$3.invoke(Window.desktop.kt:161)
at androidx.compose.ui.window.Window_desktopKt$Window$3.invoke(Window.desktop.kt:156)
at androidx.compose.ui.window.Window_desktopKt$Window$10$1.invoke(Window.desktop.kt:367)
at androidx.compose.ui.window.Window_desktopKt$Window$10$1.invoke(Window.desktop.kt:366)
at androidx.compose.ui.window.AwtWindow_desktopKt$AwtWindow$2.invoke(AwtWindow.desktop.kt:75)
at androidx.compose.ui.window.AwtWindow_desktopKt$AwtWindow$2.invoke(AwtWindow.desktop.kt:74)
at androidx.compose.runtime.DisposableEffectImpl.onRemembered(Effects.kt:81)
at androidx.compose.runtime.CompositionImpl$RememberEventDispatcher.dispatchRememberObservers(Composition.kt:801)
at androidx.compose.runtime.CompositionImpl.applyChanges(Composition.kt:647)
at androidx.compose.runtime.Recomposer.composeInitial$runtime(Recomposer.kt:763)
at androidx.compose.runtime.CompositionImpl.setContent(Composition.kt:433)
at androidx.compose.ui.window.Application_desktopKt$awaitApplication$2$1$2.invokeSuspend(Application.desktop.kt:220)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:771)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:716)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:741)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Caused by: org.jetbrains.skiko.LibraryLoadException: Cannot find libskiko-linux-arm64.so.sha256, proper native dependency missing.
at org.jetbrains.skiko.Library.findAndLoad(Library.kt:105)
at org.jetbrains.skiko.Library.load(Library.kt:59)
at org.jetbrains.skiko.SkiaLayer.<clinit>(SkiaLayer.awt.kt:27)
```
----------------------------------------------------------------------
The java archive file used is the current beta version (101M):
`briar-desktop-linux-0.3.0-beta.jar`
The above mentioned jar file works fine on a AMD64 Linux system (Debian testing). No issue with the file, then. By the way, the same error occurred with the older version 0.2.1-beta as well.
The system the app was crashing on is a Raspberry Pi with current stable 64 bit PiOS. The hardware is a Raspberry Pi 4 with 4 GB of RAM and plenty of it is free.
Some other Java applications like MediathekView run without issues.
This leads me to the conclusion that the error is somewhere in the code.
I hope the information provided helps to get Briar running on a Raspberry Pi with a future release of the desktop app.
----------------------------------------------------------------------
```
> cat /etc/issue
Debian GNU/Linux 11 \n \l
```
----------------------------------------------------------------------
```
> uname -a
Linux myhost 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux
```
----------------------------------------------------------------------
```
> java --version
openjdk 17.0.4 2022-07-19
OpenJDK Runtime Environment (build 17.0.4+8-Debian-1deb11u1)
OpenJDK 64-Bit Server VM (build 17.0.4+8-Debian-1deb11u1, mixed mode, sharing)
```