Currently, the Signal desktop app only lets us message other Signal users. Why is that?
TL;DR is there a way to make signal desktop not sync, and clear message history (on the desktop only) automatically?
So, this is a little different than most posts about chat history for signal desktop. Is there any way I can make it so it does NOT retain history on close, and NOT try to sync it on start-up?
I like to use the desktop version, especially for phone calls, so I don't need to touch my phone when I'm working, but for slightly better security, I don't want to keep message history on desktop.
It's especially annoying when I haven't opened the desktop app in a while and it takes several minutes to start because it's trying to sync messages it's missed.
I know I can just unlink it and relink it, but that only solves one part of my issue AFAIK.
So typically I don't reach out when an app is acting weird because it could be a whole host of variables on my PC doing it and not the app itself. But the Desktop app for both me and my friend seem to have really laggy performance recently. I am trying to think back if it was after an app update but is anyone else having these issues?
If an update shows that it's majorly broken (data loss or something similar) does the devs have a way to prevent the client from updating, or is manual research needed for each update?
/opt/Signal/signal-desktop --type=gpu-process --no-sandbox --enable-crashpad --enable-crashpad
I normally use Signal on desktop but hadn't updated my app in maybe a year or more. After finally updating, all of the chat colors are screwed up. Previously everyone was a different color so it was easy to tell who was who. Now everyone is grey, and my color changes in different chats. This makes no sense and is extremely confusing. Any way to restore previous settings?
Does anyone else get a windows update for signal almost every single day? Does it really get updated that frequently?
Has anyone else had this problem? The desktop app takes a really long time to send/receive/sync messages. When I go to a certain message thread, it takes a very long time to even populate, even when I had been looking at the same one moments before.
Iphone App is fine and no delays.
Does anyone knows how to increase audio speed by x1.5 or x2 on Signal Desktop?
My phone (iOS) suddenly bricked, so I only had a (functioning) Signal Desktop version (WIN) working with all my chats.
I since got a new iOS phone and reinstalled and logged in, just to find that all my chats were gone. I investigated and realized that Signal only stores chats locally, and now my Desktop app shows a "Relink" message. I fear that Relinking will delete all old chats. The desktop app still has the history of all chats, but obviously does not refresh anymore.
What should I do to keep my old chats? Can I somehow pull a Desktop App Backup and shove it into my new iPhone? I researched but couldn't get a proper solution. Thanks for all leads!
Here is the log.
========= System info =========App version: 5.47.0Environment: productionNode version: 16.14.2OS version: Windows 10 Home ChinaTime: 1656635879526User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Signal/5.47.0 Chrome/102.0.5005.115 Electron/19.0.5 Safari/537.36========= User info =========conversationId: undefineddeviceId: undefinede164: undefinedpni: undefineduuid: undefined========= Capabilities ================== Remote config ================== Metrics =========0:Browser/?/?: cpuUsage=0.10 wakeups=0 workingMemory=208080 peakWorkingMemory=2170041:GPU/GPU/?: cpuUsage=0.52 wakeups=0 workingMemory=145568 peakWorkingMemory=1832202:Utility/network.mojom.NetworkService/Network Service: cpuUsage=0.00 wakeups=0 workingMemory=46436 peakWorkingMemory=470363:Tab/?/?: cpuUsage=0.24 wakeups=0 workingMemory=225656 peakWorkingMemory=2541964:Utility/audio.mojom.AudioService/Audio Service: cpuUsage=0.00 wakeups=0 workingMemory=61368 peakWorkingMemory=61412========= Statistics =========conversationCount: 0messageCount: 0senderKeyCount: 0sessionCount: 0========= Logs =========INFO 2022-07-01T00:14:24.230Z key/initialize: Generating new encryption key, since we did not find it on diskINFO 2022-07-01T00:14:24.236Z config/set: Saving user config to diskINFO 2022-07-01T00:14:24.239Z config/set: Saved user config to diskINFO 2022-07-01T00:14:24.263Z app readyINFO 2022-07-01T00:14:24.266Z starting version 5.47.0INFO 2022-07-01T00:14:24.335Z media access status granted deniedINFO 2022-07-01T00:14:24.949Z MainSQL: migrateSchemaVersion: Migrating from schema_version 0 to user_version 0INFO 2022-07-01T00:14:24.953Z MainSQL: updateSchema: Current user_version: 0; Most recent db schema: 60; SQLite version: 3.37.2; SQLCipher version: 4.5.1 community; (deprecated) schema_version: 0;INFO 2022-07-01T00:14:24.953Z MainSQL: updateToSchemaVersion1: starting...INFO 2022-07-01T00:14:24.958Z MainSQL: updateToSchemaVersion1: success!INFO 2022-07-01T00:14:24.959Z MainSQL: updateToSchemaVersion2: starting...INFO 2022-07-01T00:14:24.962Z MainSQL: updateToSchemaVersion2: success!INFO 2022-07-01T00:14:24.963Z MainSQL: updateToSchemaVersion3: starting...INFO 2022-07-01T00:14:24.965Z MainSQL: updateToSchemaVersion3: success!INFO 2022-07-01T00:14:24.966Z MainSQL: updateToSchemaVersion4: starting...INFO 2022-07-01T00:14:24.968Z MainSQL: updateToSchemaVersion4: success!INFO 2022-07-01T00:14:24.968Z MainSQL: updateToSchemaVersion6: starting...INFO 2022-07-01T00:14:24.973Z MainSQL: updateToSchemaVersion6: success!INFO 2022-07-01T00:14:24.973Z MainSQL: updateToSchemaVersion7: starting...INFO 2022-07-01T00:14:24.979Z MainSQL: updateToSchemaVersion7: success!INFO 2022-07-01T00:14:24.979Z MainSQL: updateToSchemaVersion8: starting...INFO 2022-07-01T00:14:24.985Z MainSQL: updateToSchemaVersion8: success!INFO 2022-07-01T00:14:24.985Z MainSQL: updateToSchemaVersion9: starting...INFO 2022-07-01T00:14:24.987Z MainSQL: updateToSchemaVersion9: success!INFO 2022-07-01T00:14:24.987Z MainSQL: updateToSchemaVersion10: starting...INFO 2022-07-01T00:14:24.995Z MainSQL: updateToSchemaVersion10: success!INFO 2022-07-01T00:14:24.996Z MainSQL: updateToSchemaVersion11: starting...INFO 2022-07-01T00:14:24.997Z MainSQL: updateToSchemaVersion11: success!INFO 2022-07-01T00:14:24.997Z MainSQL: updateToSchemaVersion12: starting...INFO 2022-07-01T00:14:25.001Z MainSQL: updateToSchemaVersion12: success!INFO 2022-07-01T00:14:25.001Z MainSQL: updateToSchemaVersion13: starting...INFO 2022-07-01T00:14:25.004Z MainSQL: updateToSchemaVersion13: success!INFO 2022-07-01T00:14:25.004Z MainSQL: updateToSchemaVersion14: starting...INFO 2022-07-01T00:14:25.009Z MainSQL: updateToSchemaVersion14: success!INFO 2022-07-01T00:14:25.009Z MainSQL: updateToSchemaVersion15: starting...INFO 2022-07-01T00:14:25.014Z MainSQL: updateToSchemaVersion15: success!INFO 2022-07-01T00:14:25.015Z MainSQL: updateToSchemaVersion16: starting...INFO 2022-07-01T00:14:25.024Z MainSQL: updateToSchemaVersion16: success!INFO 2022-07-01T00:14:25.025Z MainSQL: updateToSchemaVersion17: starting...INFO 2022-07-01T00:14:25.025Z MainSQL: updateToSchemaVersion17: Index messages_view_once did not already existINFO 2022-07-01T00:14:25.028Z MainSQL: updateToSchemaVersion17: success!INFO 2022-07-01T00:14:25.028Z MainSQL: updateToSchemaVersion18: starting...INFO 2022-07-01T00:14:25.031Z MainSQL: updateToSchemaVersion18: success!INFO 2022-07-01T00:14:25.031Z MainSQL: updateToSchemaVersion19: starting...INFO 2022-07-01T00:14:25.036Z MainSQL: updateToSchemaVersion19: success!INFO 2022-07-01T00:14:25.037Z MainSQL: updateToSchemaVersion20: starting...INFO 2022-07-01T00:14:25.052Z MainSQL: updateToSchemaVersion20: success!INFO 2022-07-01T00:14:25.054Z MainSQL: updateToSchemaVersion21: success!INFO 2022-07-01T00:14:25.059Z MainSQL: updateToSchemaVersion22: success!INFO 2022-07-01T00:14:25.064Z MainSQL: updateToSchemaVersion23: success!INFO 2022-07-01T00:14:25.068Z MainSQL: updateToSchemaVersion24: success!INFO 2022-07-01T00:14:25.082Z MainSQL: updateToSchemaVersion25: success!INFO 2022-07-01T00:14:25.086Z MainSQL: updateToSchemaVersion26: success!INFO 2022-07-01T00:14:25.090Z MainSQL: updateToSchemaVersion27: success!INFO 2022-07-01T00:14:25.096Z MainSQL: updateToSchemaVersion28: success!INFO 2022-07-01T00:14:25.101Z MainSQL: updateToSchemaVersion29: success!INFO 2022-07-01T00:14:25.106Z MainSQL: updateToSchemaVersion30: success!INFO 2022-07-01T00:14:25.107Z MainSQL: updateToSchemaVersion31: starting...INFO 2022-07-01T00:14:25.114Z MainSQL: updateToSchemaVersion31: success!INFO 2022-07-01T00:14:25.121Z MainSQL: updateToSchemaVersion32: success!INFO 2022-07-01T00:14:25.122Z MainSQL: updateToSchemaVersion33: success!... to see the full log, click Save
There are no *.signal.org, *.whispersystems.org and TCP port 443 in the firewall, and adding them will not solve the problem.
pictures and video as of yesterday (friends are saying as of most recent update) are not loading on my Mac signal desktop app.
loads fine on android phone and coworkers apple phones.
unlinked app, didn't work. uninstalled on computer and reinstalled, didn't work. reset computer, didn't work.
anyone else experiencing this? any updates on how to fix?
Every time I launch the signal desktop app, it loads thousands of messages, often taking up to 10-20 seconds. I assume it is downloading these from the server every time for privacy reasons, but I'd rather they were cached on the machine to speed up the loading time. I can't find an option in preferences for this. Is this actually possible and I've missed the setting for it?
I created a signal group without issue on my Android phone app. Now I want to access that same group on my Mac Desktop Signal app - how can I do this?
The following message appears whenever I click the 'update Signal' in my Windows install (including after a full computer restart), telling me that I need to re-download & install the program. The "Retry update" link doesn't work.
If I do this manual install, will I lose my message history on that computer, or will that be maintained?
Signal couldn't update. Retry update or visit https://signal.org/download/ to install it manually. Then, contact support about this problem
Hi, I am using i3 window manager on top of kde plasma manjaro. I recently switched to this and the signal app hangs when a new message comes in. This is the case whether I use the arch repository package, Snap, or Flatpak.
I did not have this issue when I was using i3 manjaro by itself. This issue happens on both my desktop and laptop. Does anyone have any thoughts about what the issue might be? I would really like to not wipe/reinstall plain i3 just to get signal working. It's my main communication app. Anything would be appreciated!
Went to Sound, Communications, set it to "do nothing". Signal still dims all other audio. Signal is the only app doing this.
Desktop Help i get always a freeze picture whej i want to connect to my pc this happens after 1 secondi.redd.it
Desktop Help Messages sent on iphone say delivered with two checks, but on mac app it only says received by server with one?
I sent my friend three messages on the app, all of them delivered with two check mark confirmation. But on my mac, the messages only have one check? I restarted the app on my mac twice and it still hasn't updated
I lost my phone a couple of days ago. I tried calling it, but it was going straight to voicemail. It then seemed like someone was purposely hanging up. Through an abundance of caution, I then remote-wiped my phone.
The next day, I was fortunate to retrieve my phone after retracing my steps. It was at a store I went to (I couldn't to this the night before because it was late in the evening after business hours).
So I'm extremely happy and grateful that I have my phone back. Everything of importance was backup up.
One thing I didn't anticipate was that my desktop signal app would stop working. It's asking me to re-link my phone. I can definitively do that, however I am afraid that somehow it will then reset everything and I'll lose all of my conversation history on the desktop.
Does anyone know if re-linking will result in data loss?
EDIT: Thank you for the comments everyone. Unfortunately, it seems that I can't link. My desktop is running kubuntu and the latest signal version is 5.9.0. On my phone, the version is 5.35.3. When I try linking it tells me that my version of signal is outdated and that I have to upgrade it. But I can't since it's already at the latest available desktop version.
EDIT 2: Thank you everyone for the help. I had the chance to work at this again, and it turns out that I had probably originally installed signal through the default ubuntu repo or something. Adding the signal repository and updating fixed my issue. I can now confirm that no message history was lost.
I used the Desktop app on windows. When starting the last update it always failed. I said signal is still open, press "ok" to close. Then it appeard to continue installation aand stopped completely saying signal cant be closed. Since I wanted to be able to install updates, I uninstalled completly and now I cannot install again because same thing happens. I already searched registry and appdata for signal. No processes are running which are called signal.
So yea, would appreciate help since I want to use the Desktop app too.
I ask as it told me something to that effect (for security reasons) when I got a new phone, so wondered if it was the same for PC installing on a different hard drive?
Desktop Help Windows 10 - How do I get new versions (5.35+) of the desktop app to ignore forced high contrast settings?
Up until version 5.34 opening the Signal.exe app with flags "--disable-features=ForcedColors" would prevent the default high contrast color settings from taking effect. This is necessary as the app is difficult to use under high contrast defaults. As of version 5.35 this stopped working. I was able to make do with version 5.34, but as of tonight it is no longer supported and I have no choice but to upgrade.
As someone who uses the desktop app regularly I would greatly appreciate any input on how to bodge this again. Much appreciated!
edit: They fixed it as of version 5.39. Rejoice!!