Thanks, Andreas, that clears up that side confusion.

The command suggested by https://github.com/KDE/drkonqi,

systemctl is-enabled drkonqi-coredump-processor@.service

does work, and shows it to be disabled, despite that page suggesting it should be enabled.

I could of course just enable it, but I'm trying to understand whether it being disabled is some intentional openSUSE decision that I might want to go along with, especially in light of messages during my update and
Lassi's journalctl that suggest either that it may have previously been enabled, or doesn't need to be enabled to be activated during a crash or some such. I hope someone can clear that up.

Cheers,
Eric


On 7/2/24 4:07 AM, Andreas Schwab wrote:
On Jun 30 2024, Eric Schwarzenbach wrote:


Failed to stop drkonqi-coredump-processor@.service: Unit name
drkonqi-coredump-processor@.service is missing the instance name.

This is a limitation of the systemd-update-helper script, it cannot cope
properly with parameterized units.


systemctl status drkonqi-coredump-processor.service

gives

Unit drkonqi-coredump-processor.service could not be found.

nor do I find it with list-units. Web searches don't give me any sense
that KDE has moved away from using it...has openSUSE for some reason?

See systemd.unit(5):

       Unit names can be parameterized by a single argument called the
       "instance name". The unit is then constructed based on a "template file"
       which serves as the definition of multiple services or other units. A
       template unit must have a single "@" at the end of the unit name prefix
       (right before the type suffix). The name of the full unit is formed by
       inserting the instance name between "@" and the unit type suffix. In the
       unit file itself, the instance parameter may be referred to using "%i"
       and other specifiers, see below.