#StackBounty: #18.04 #systemd systemd user service not found after reboot

Bounty: 50

I set up syncthing as a systemd user service on a 16.04 computer. Worked fine. Since I upgraded to 18.04 the service disappears upon reboot.

After rebooting, I see:

$ systemctl --user status syncthing.service 
Unit syncthing.service could not be found.

And syncthing is indeed not running.

Here is ~/.config/systemd/user/syncthing.service (following the example, but note the binary is under my home dir):

[Unit]
Description=Syncthing - Open Source Continuous File Synchronization
Documentation=man:syncthing(1)

[Service]
ExecStart=/home/user/syncthing-prefix/syncthing -no-browser -no-restart -logflags=0
Restart=on-failure
SuccessExitStatus=3 4
RestartForceExitStatus=3 4

[Install]
WantedBy=default.target

I then run this:

$ systemctl --user enable syncthing.service
$ systemctl --user start syncthing.service

Following the setup instructions I used to install the user service originally.

After running the above two commands, I see:

$ systemctl --user status syncthing.service
● syncthing.service - Syncthing - Open Source Continuous File Synchronization
  Loaded: loaded (/home/user/.config/systemd/user/syncthing.service; enabled; 
  Active: active (running) since Tue 2018-11-06 15:28:16 PST; 4s ago
    Docs: man:syncthing(1)
Main PID: 4221 (syncthing)
  CGroup: /user.slice/user-1000.slice/user@1000.service/syncthing.service
          └─4221 /home/user/syncthing-prefix/syncthing -no-b

Nov 06 15:28:18 kind syncthing[4221]: [XXXXX] INFO: Device XXXXXXX-XXXXXXX-XXXXX
Nov 06 15:28:18 kind syncthing[4221]: [XXXXX] INFO: Device XXXXXXX-XXXXXXX-XXXXX
Nov 06 15:28:18 kind syncthing[4221]: [XXXXX] INFO: Device XXXXXXX-XXXXXXX-XXXXX
Nov 06 15:28:18 kind syncthing[4221]: [XXXXX] INFO: GUI and API listening on 127
Nov 06 15:28:18 kind syncthing[4221]: [XXXXX] INFO: Access the GUI via the follo
Nov 06 15:28:18 kind syncthing[4221]: [XXXXX] INFO: Completed initial scan of se
Nov 06 15:28:18 kind syncthing[4221]: [XXXXX] INFO: Completed initial scan of se
Nov 06 15:28:18 kind syncthing[4221]: [XXXXX] INFO: Completed initial scan of se
Nov 06 15:28:19 kind syncthing[4221]: [XXXXX] INFO: Completed initial scan of se
Nov 06 15:28:20 kind syncthing[4221]: [XXXXX] INFO: Completed initial scan of se

as expected. And syncthing then works, as expected, until the next reboot.

Note that I have an encrypted home dir. This was the case when I was using 16.04, too.


Get this bounty!!!

#StackBounty: #18.04 #network-manager #mate #widgets nm-applet – (dynamically) expand menu size

Bounty: 50

When having many WiFi SSIDs available, I need to scroll through the right-click menu of nm-applet widget menu by hovering over the arrow (see first screenshot below), yet the menu only spreads to a maximum of half my desktops height. Sometimes the size even shrinks in what I can currently only perceive as a random pattern (second screenshot).

How to set the size of this menu and make it use the whole desktop height as maximum before offering to scroll?

Running mate as desktop environment in18.04 LTS.

enter image description here

enter image description here


Get this bounty!!!

#StackBounty: #18.04 #ntp How to get logging on ntpd changing the clock

Bounty: 50

While debugging a client device using ntp client to get it’s time from our ntp server, it was shown that the server sometimes ‘hickups’ it’s clock with an offset of 20 seconds or such. The ntpd adjusts within 10-30 minutes, but of course we want to know why this needed and are looking for the cause.

Digging through the logs and documentation, we found out that the logging is at such a level that these time changing events are not reported.

Various settings were attempted: setting

logconfig =all

in /etc/ntp.conf and setting the debug option -d in /etc/default/ntp.conf did not have any effect.

Worse: with the last option the ntpd fails at a restart after a timeout of three minutes:

systemd[1]: ntp.service: Failed with result 'timeout'.

I) How can we raise the debug level without failing to start the service?
II) What is the best way of the ntpd reporting about it changing the clock and the reason it does?

The first question is worth 50 from my reputation. If the second is answered I’ll raise the bonus to 100 before approving the answer.


Get this bounty!!!

#StackBounty: #gnome #18.04 #nautilus Can't move/snap Nautilus window to occupy left or right half of the 1366×768 screen – is it j…

Bounty: 50

I’m running Ubuntu 18.04 LTS with GNOME Shell.
Nautilus does not want to occupy 50% (left or right) of the screen sized at 1366×768.

Snapping Nautilus in 18.04 LTS

Other applications (such as GNOME Terminal, Eye of GNOME, Gedit) are normally snapping to the left/right half of the screen.

But Nautilus can be resized to the width lower than half of screen (I can get 650 px, which is smaller than 1366/2 = 683 px).

The first usable screen resolution seems to be 1400×1050, then goes 1440×900. But large amount of current devices are still using 1366×768.

Is it just me?


Get this bounty!!!

#StackBounty: #gnome #18.04 #nautilus Can't move/snap Nautilus window to occupy left or right half of the 1366×768 screen – is it j…

Bounty: 50

I’m running Ubuntu 18.04 LTS with GNOME Shell.
Nautilus does not want to occupy 50% (left or right) of the screen sized at 1366×768.

Snapping Nautilus in 18.04 LTS

Other applications (such as GNOME Terminal, Eye of GNOME, Gedit) are normally snapping to the left/right half of the screen.

But Nautilus can be resized to the width lower than half of screen (I can get 650 px, which is smaller than 1366/2 = 683 px).

The first usable screen resolution seems to be 1400×1050, then goes 1440×900. But large amount of current devices are still using 1366×768.

Is it just me?


Get this bounty!!!

#StackBounty: #gnome #18.04 #nautilus Can't move/snap Nautilus window to occupy left or right half of the 1366×768 screen – is it j…

Bounty: 50

I’m running Ubuntu 18.04 LTS with GNOME Shell.
Nautilus does not want to occupy 50% (left or right) of the screen sized at 1366×768.

Snapping Nautilus in 18.04 LTS

Other applications (such as GNOME Terminal, Eye of GNOME, Gedit) are normally snapping to the left/right half of the screen.

But Nautilus can be resized to the width lower than half of screen (I can get 650 px, which is smaller than 1366/2 = 683 px).

The first usable screen resolution seems to be 1400×1050, then goes 1440×900. But large amount of current devices are still using 1366×768.

Is it just me?


Get this bounty!!!

#StackBounty: #gnome #18.04 #nautilus Can't move/snap Nautilus window to occupy left or right half of the 1366×768 screen – is it j…

Bounty: 50

I’m running Ubuntu 18.04 LTS with GNOME Shell.
Nautilus does not want to occupy 50% (left or right) of the screen sized at 1366×768.

Snapping Nautilus in 18.04 LTS

Other applications (such as GNOME Terminal, Eye of GNOME, Gedit) are normally snapping to the left/right half of the screen.

But Nautilus can be resized to the width lower than half of screen (I can get 650 px, which is smaller than 1366/2 = 683 px).

The first usable screen resolution seems to be 1400×1050, then goes 1440×900. But large amount of current devices are still using 1366×768.

Is it just me?


Get this bounty!!!

#StackBounty: #gnome #18.04 #nautilus Can't move/snap Nautilus window to occupy left or right half of the 1366×768 screen – is it j…

Bounty: 50

I’m running Ubuntu 18.04 LTS with GNOME Shell.
Nautilus does not want to occupy 50% (left or right) of the screen sized at 1366×768.

Snapping Nautilus in 18.04 LTS

Other applications (such as GNOME Terminal, Eye of GNOME, Gedit) are normally snapping to the left/right half of the screen.

But Nautilus can be resized to the width lower than half of screen (I can get 650 px, which is smaller than 1366/2 = 683 px).

The first usable screen resolution seems to be 1400×1050, then goes 1440×900. But large amount of current devices are still using 1366×768.

Is it just me?


Get this bounty!!!

#StackBounty: #gnome #18.04 #nautilus Can't move/snap Nautilus window to occupy left or right half of the 1366×768 screen – is it j…

Bounty: 50

I’m running Ubuntu 18.04 LTS with GNOME Shell.
Nautilus does not want to occupy 50% (left or right) of the screen sized at 1366×768.

Snapping Nautilus in 18.04 LTS

Other applications (such as GNOME Terminal, Eye of GNOME, Gedit) are normally snapping to the left/right half of the screen.

But Nautilus can be resized to the width lower than half of screen (I can get 650 px, which is smaller than 1366/2 = 683 px).

The first usable screen resolution seems to be 1400×1050, then goes 1440×900. But large amount of current devices are still using 1366×768.

Is it just me?


Get this bounty!!!