-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signal.exe --start-in-tray option does not carry across updates #2368
Comments
In your step #2, did you create your own shortcut? Or did you modify the shortcut that the installer made for you? |
I've come across this bug too; in my case I created a new shortcut using |
@scottnonnenberg I think (IIRC) after installing Signal using the installer and learning that I need to use --start-in-tray option to make it run in the tray, I did the following:
|
@mhantsch So that shortcut copy is edited by the installer? That's definitely surprising. |
@scottnonnenberg No, the shortcut is not modified by the installer. (That would indeed by strange.) The shortcut stays the same. But still, when it restarts after the auto-update, it does not start in the tray. My guess is that after the update it re-starts its own .exe directly instead of through the shortcut, thus loosing the parameters that were added in the shortcut. Or maybe it restarts itself through the originally installed shortcut instead of through the shortcut that I had copied in shell:startup and edited to include the --start-in-tray parameter. |
Oh, I see. The installer process itself restarts the app, and doesn't use our command-line argument. Now I understand. The good news is that this will go away once this feature comes out of beta and is controlled by settings that live inside the app.. |
@scottnonnenberg Yes, that is what is happening. Glad I was finally able to get the point across :) |
What's worse, in the latest version 1.32.2 on Windows, it's actually crashing on startup if you have --start-in-tray |
Update to v1.32.3. It's just been fixed. See #4085. |
Yep, I did so and can confirm that fixes it.
…On Fri, Mar 27, 2020 at 3:13 AM Maximilian Hantsch ***@***.***> wrote:
latest version 1.32.2 on Windows, it's actually crashing on startup if you
have --start-in-tray
Update to v1.32.3. It's just been fixed. See #4085
<#4085>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2368 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPGTMZ4WXB5PV2V2PL3S7TRJR36FANCNFSM4E7OGCNQ>
.
|
Hi! I'm wondering why is this option not available in the preferences of the application? It would be so much easier for all the distributions and packagers around here. There will be no need to alter the files (.desktop file for example) after installation of the package. |
The option is in app preferences on Linux for beta users only. feature is in beta only because tray icon support is so unpredictable across all the various linux window managers and distributions. |
AFAIK, there are standard spec for this, no ? |
@drupol do you know which window managers implement this spec and which don't? What about Wayland? |
I'm sorry I don't know that. But if there is a standard for that, why not implement it? Many Electron based apps are available and they are handling this feature properly, except Signal. |
My question was whether this is an actual standard or not. I'm not sure it actually is in practice. See also #5377. |
The original issue was about the On Linux, it's a different story. Let's move discussion to #5377. |
Bug description
When Signal is run in a tray icon under Windows, when it auto-updates itself it restarts without the tray icon.
Steps to reproduce
Actual result:
Tray Icon is gone after the auto-update.
Expected result:
Signal should remember the commandline options (--start-in-tray) and after an auto-update, restart itself using the same options.
Screenshots
Platform info
Signal version:
Signal Desktop v1.10.0
Operating System:
Windows 10 64-bit
Linked device version:
Does not matter, but Android Signal 4.19.3
Link to debug log
(not applicable)
The text was updated successfully, but these errors were encountered: