After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 787512 - copy-worker: Don't start if gnome-initial-setup-done was touched
copy-worker: Don't start if gnome-initial-setup-done was touched
Status: RESOLVED FIXED
Product: gnome-initial-setup
Classification: Applications
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: GNOME Initial Setup maintainer(s)
GNOME Initial Setup maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-09-10 17:09 UTC by Cosimo Cecchi
Modified: 2017-10-26 07:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
copy-worker: Don't start if gnome-initial-setup-done was touched (1.04 KB, patch)
2017-09-10 17:09 UTC, Cosimo Cecchi 		committed Details | Review

Description Cosimo Cecchi 2017-09-10 17:09:00 UTC 
Right now we're starting the g-i-s copy worker at every login. See patch.
Comment 1 Cosimo Cecchi 2017-09-10 17:09:02 UTC 
Created attachment 359471 [details] [review]
copy-worker: Don't start if gnome-initial-setup-done was touched

Currently we start the copy worker during every login, which won't do
anything since gnome-initial-setup home directory won't be present;
but we can avoid this entirely and simply not spawn the worker unless
this is the first login.
Comment 2 Rui Matos 2017-10-25 15:39:48 UTC 
Review of attachment 359471 [details] [review]:

indeed, thank you
Comment 3 Cosimo Cecchi 2017-10-26 07:59:23 UTC 
Attachment 359471 [details] pushed as a8551a4 - copy-worker: Don't start if gnome-initial-setup-done was touched

Pushed to master, thanks.