system-config-printer gives different results in template and VM

Franz

unread,

Jan 19, 2021, 9:26:03 AM1/19/21

to qubes-users

Hello,

if I write system-config-printer in the debian template I get the expected GUI to config the printer and everything works as expected.

If I write the same in the VM depending from the template, I get:

Printing service not available. Start the service on this computer or connect to another server.

If I click on start the service, nothing happens.

After many years using Qubes, the template and the VM depending from the template always behaved in the same way. I cannot understand why the template works and the VM does not.

To be sure, I tried on two different VMs depending from the same template an none works

Best

Franz

unman

unread,

Jan 19, 2021, 9:20:34 PM1/19/21

to Franz, qubes-users

You don't have cups/cupsd enabled in the qube: enable it on Services tab
of GUI or using `qvm-service`

Franz

unread,

Jan 20, 2021, 9:04:00 AM1/20/21

to unman, Franz, qubes-users

Many thanks Unman, but why does the template not give the same error?

I understand this kind of problem should be fixed in the template, not in the VM that depends on the template.

But if the template works, how may I fix something that already works?

best

Franz

unman

unread,

Jan 20, 2021, 9:43:52 AM1/20/21

to Franz, qubes-users

By default Debian will enable services (and start them) after
installation. This is a problem for templates, which is why there is
specific advice about installing services in to Debian templates.
By contrast Fedora does not automatically start services.

There are many services which can be enabled or disabled in an template
based qube. cups is just one of them.
That said, I'm puzzled as to why cups *is* running in your template - it
doesn't seem to be in my Debian 10.

Franz

unread,

Jan 20, 2021, 10:20:18 AM1/20/21

to unman, Franz, qubes-users

Many thanks Unman, I tried to start cups using Qubes manager GUI and now even the VM works and this survives reboot. No way I could have thought it alone.

There are many services which can be enabled or disabled in an template
based qube. cups is just one of them.
That said, I'm puzzled as to why cups *is* running in your template - it
doesn't seem to be in my Debian 10.

Well I suspect that cups is running in my template Debian 10. In fact if I digit system-config-printer it starts the printer GUI without errors.

Reply all

Reply to author

Forward