Bug 1459517 - Chromium does not "run in the background".
Chromium does not "run in the background".
Status: NEW
Product: Fedora
Classification: Fedora
Component: chromium (Show other bugs)
26
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Tom "spot" Callaway
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-07 06:55 EDT by Diogo Campos
Modified: 2017-06-14 12:30 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screencast (36.45 KB, application/octet-stream)
2017-06-07 10:13 EDT, Diogo Campos
no flags Details

  None (edit)
Description Diogo Campos 2017-06-07 06:55:39 EDT
At "chrome://settings/", under "Show advanced options", in the "System" category, there is an option called "Continue running background apps when Chromium is closed".

It does not work.

Chromium 58.0.3029.110-2.fc26
Comment 1 Tom "spot" Callaway 2017-06-07 09:37:32 EDT
What app are you testing with?
Comment 2 Diogo Campos 2017-06-07 10:12:36 EDT
www.messenger.com & mail.google.com

But I think the main issue is that no Chromium processes are keeping around when its window is closed.

So, as a result, (in my use case) I do not receive push notifications (of new messages, new emails) anymore.

As a side note, trying "chromium-browser --no-startup-window" (which, supposedly, should mimic this "no-window" behavior/setting) spawns processes which are killed after a second or two (as shown in the following screencast).
Comment 3 Diogo Campos 2017-06-07 10:13 EDT
Created attachment 1285810 [details]
Screencast
Comment 4 Tom "spot" Callaway 2017-06-14 12:30:10 EDT
I don't think this works on google-chrome on Fedora either. Can you file a bug in the upstream tracker?

Note You need to log in before you can comment on or make changes to this bug.