It's not some random page, it's the KDE drkonqi github README. Of course this doesn't mean they can't wrong or misguided. If so, the output from these commands is certainly misleading:
❯ systemctl is-enabled drkonqi-coredump-processor@.service
disabled
  ~/stuff/work/code/wrycan/xms-8.0-branch ❯ sudo systemctl enable drkonqi-coredump-processor@.service 
Created symlink /etc/systemd/system/systemd-coredump@.service.wants/drkonqi-coredump-processor@.service → /usr/lib/systemd/system/drkonqi-coredump-processor@.service.
❯ systemctl is-enabled drkonqi-coredump-processor@.service enabled
❯ sudo systemctl is-enabled drkonqi-coredump-processor@.service
enabled

On 7/2/24 11:33 AM, Andrei Borzenkov wrote:
On 02.07.2024 18:06, Eric Schwarzenbach wrote:
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 disable|d|, despite that page suggesting
it should be enabled.


You cannot enable template unit. Period. Whatever is written on some random page in Internet.

You can have DefaultInstance=xxx property in template unit which will get enabled when you try to enable template itself. This property is not present in drkonqi-coredump-processor@.service.

I could of course just enable it,

You cannot.

but I'm trying to understand whether
it being disabled is some intentional openSUSE decision that I might

It is not. The drkonqi-coredump-processor@.service is even explicitly enabled in presets shipped by openSUSE. It just cannot work with the current unit definition.

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 stopdrkonqi-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.


Well, as mentioned template@.service can provide default instance which then can be implicitly enabled through "systemctl enable template@.service". May be it was there is the past but got lost. I have no idea what is expected as an instance here.

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.