Public bug reported:
I use usbmux for my iphone so I can access my photos via shotwell and
move files around. I have to start the service manually via systemd.
When I try to enable I get the following.
hhernandez@hhernandez-Precision-M4800:~$ sudo systemctl enable usbmuxd
[sudo] password for hhernandez:
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: usbmuxd 1.1.0-2build1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Oct 22 13:04:24 2018
SourcePackage: usbmuxd
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: usbmuxd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to usbmuxd in Ubuntu.
https://bugs.launchpad.net/bugs/1799287
Title:
usbmud service will not load on boot
Status in usbmuxd package in Ubuntu:
New
Bug description:
I use usbmux for my iphone so I can access my photos via shotwell and
move files around. I have to start the service manually via systemd.
When I try to enable I get the following.
hhernandez@hhernandez-Precision-M4800:~$ sudo systemctl enable usbmuxd
[sudo] password for hhernandez:
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: usbmuxd 1.1.0-2build1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Oct 22 13:04:24 2018
SourcePackage: usbmuxd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1799287/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
