Skip to content
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

Closed
1 task done
mhantsch opened this issue May 11, 2018 · 17 comments
Closed
1 task done

Signal.exe --start-in-tray option does not carry across updates #2368

mhantsch opened this issue May 11, 2018 · 17 comments

Comments

@mhantsch
Copy link

mhantsch commented May 11, 2018

  • I have searched open and closed issues for duplicates

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

  1. Use Windows 10
  2. Create a shortcut to run "Signal.exe --start-in-tray"
  3. Put the shortcut in shell:startup (= Press Win-R, type shell:startup, press Enter, then put your shortcut into that folder)
  4. Start Windows and login and note Signal is now running in a tray icon. Click the tray icon to open/close the Signal main window.
  5. Receive a notification that a newer version of Signal is available. Click to auto-update.
  6. When the updated Signal restarts, your tray icon is gone. You have to quit Signal, then open shell:startup and run your shortcut manually to regain your tray icon.

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)

@scottnonnenberg-signal
Copy link
Contributor

In your step #2, did you create your own shortcut? Or did you modify the shortcut that the installer made for you?

@ProactiveServices
Copy link

ProactiveServices commented May 11, 2018

I've come across this bug too; in my case I created a new shortcut using --use-tray-icon --start-in-tray

@mhantsch
Copy link
Author

mhantsch commented May 13, 2018

@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:

  • Press Windows key and type "signal"
  • right click on the "signal" that was found and select "open file location"
  • realized a shortcut is there (was probably created by the installer)
  • copy that shortcut to shell:startup
  • edit the shortcut in shell:startup to add the --start-in-tray option

@scottnonnenberg-signal
Copy link
Contributor

@mhantsch So that shortcut copy is edited by the installer? That's definitely surprising.

@mhantsch
Copy link
Author

@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.

@scottnonnenberg-signal
Copy link
Contributor

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..

@mhantsch
Copy link
Author

@scottnonnenberg Yes, that is what is happening. Glad I was finally able to get the point across :)

@aaronshaver
Copy link

What's worse, in the latest version 1.32.2 on Windows, it's actually crashing on startup if you have --start-in-tray

@mhantsch
Copy link
Author

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.

@aaronshaver
Copy link

aaronshaver commented Mar 27, 2020 via email

@drupol
Copy link

drupol commented Jun 17, 2021

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.

@scottnonnenberg-signal
Copy link
Contributor

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.

@drupol
Copy link

drupol commented Aug 26, 2021

AFAIK, there are standard spec for this, no ?

@hiqua
Copy link
Contributor

hiqua commented Aug 26, 2021

@drupol do you know which window managers implement this spec and which don't?

What about Wayland?

@drupol
Copy link

drupol commented Aug 27, 2021

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.

@hiqua
Copy link
Contributor

hiqua commented Aug 27, 2021

there is a standard

My question was whether this is an actual standard or not. I'm not sure it actually is in practice. See also #5377.

@EvanHahn-Signal
Copy link
Contributor

The original issue was about the --start-in-tray option persisting across updates on Windows. It has been addressed with official support. See Signal's Preferences to enable this. You no longer need the command line flag.

On Linux, it's a different story. Let's move discussion to #5377.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

7 participants