![](https://lemmy.ml/pictrs/image/423f5b48-cef0-4630-9dce-bcbce7397956.jpeg)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Glad that it works for you. I may have to switch over to the flatpak then.
Glad that it works for you. I may have to switch over to the flatpak then.
Nope, I’m on KDE.
I don’t do temporary conversations, but this is the open issue on the flatpak https://github.com/flathub/org.signal.Signal/issues/454. The thing is, I’m having the same issue as the flatpak even though I’m not using the flatpak.
Nope, its basically the same issue that the flatpak is happening, but I’m not using the flatpak. https://github.com/flathub/org.signal.Signal/issues/454
I have a couple problems with it aside from being electron.
On linux, whether it is a native package or flatpak. I have to launch it twice for it to open.
I can’t restore chats from my phone to the desktop application which frankly sucks. It makes sense if they don’t wanna have to store extra data on their servers, but at least let the backups that I manually take on my phone be usable on the desktop. Not having the majority of your conversations from before you linked the desktop app is a pain in the arse.
My only problem with Signal is the inability to manually sync conversations. Even if I have backups from my phone. They can’t be used on the desktop. I have seen some third party tools, but even those state that they might not work.
I swear when it comes to forced updates of any kind it seems like this kind of outcome is always inevitable. There will at some point always be a bad update.
That would certainly be a weird one.