On Tue, Aug 31, 2021 at 07:54:43PM +0100, Brian wrote: > On Tue 31 Aug 2021 at 14:48:02 -0400, Greg Wooledge wrote: > > > On Tue, Aug 31, 2021 at 07:31:22PM +0100, mick crane wrote: > > > On 2021-08-31 18:49, john doe wrote: > > > > You can simply 'unmask' it and see how it goes. > > > > > > Is there a way to find out why it is masked ? > > > > Starting from a point of zero context? Probably not. > > > > You MIGHT be able to scroll back through your terminal history and > > see what happened when you installed whatever package contains this > > mystery service. Maybe there will be informative output. > > > > If there's no terminal still containing the session where you installed > > the package, you can check /var/log/apt/term.log* and maybe one of those > > will have a copy of the session and its output. Again, maybe there will > > be informative output in the session's output. Maybe there won't. > > > > Maybe there will be documentation under /usr/share/doc/PKGNAME that > > tells you why the service is masked, and that you need to perform steps > > X, Y, Z to be able to use the service. Maybe there won't. Hard to tell > > without knowing the name of the package and the name of the service. > > The OP doesn't say whether he can scan or or not. > > He could give the name of the scanner he is using and what is given > by > > scanimage -L
It would also be nice to see "systemctl status <servicename>".
