SystemD's default TimeoutStart and TimeoutStop are too long for Desktop

Bug #1787853 reported by Damiön la Bagh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

On Ubuntu 18.04LTS starting and stopping the computer is extremely slow.

SystemD defaults to a start time timeout of 90seconds and a stop time timeout of 90seconds
in the file

/etc/systemd/system.conf

This is great for huge databased raid systems in some cloud datacenter but is very inappropriate for desktop computing where there is a human waiting for the process.

Ubuntu Desktops need to have the
/etc/systemd/system.conf

Set to timeout in less than <10 seconds (the magic computer irritation moment for humans) out of the box, default

for example:
DefaultTimeoutStartSec=9s
DefaultTimeoutStopSec=9s

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 23:12:49 2018
InstallationDate: Installed on 2015-11-15 (1008 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/vg0-root ro noprompt persistent quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago)
dmi.bios.date: 08/15/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.30
dmi.board.name: X99 Extreme11
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme11:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
mtime.conffile..etc.systemd.system.conf: 2018-08-19T23:11:55.785333

Revision history for this message
Damiön la Bagh (kat-amsterdam) wrote :
Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.