To be able to search for them if you have a lot of them

Is your feature request related to a problem? Please describe.
Now that the extension has been removed from the gnome extensions, it has broken the update process in NixOS.

Describe the solution you'd like
I know this repository has nothing to do with NixOS, but I am wondering if you all would like to make a
a PR in Nixpkgs to make systemd-manager its own package in NixOS?

That might be a big ask, but I thought I would try.

This relates to this issue in Nixpkgs:

NixOS/nixpkgs#279638

Thanks so much!

@hashworks

@jonian

If I select "mpd.service user" from the list and add it: the system service has been added to the table. The expected behavior would be for the user service to be added.

Hello,

Many thanks for this extension, this is very useful to me. Consider you to port Systemd Manager to G.S 45 in a near future?

Thanks again for your work.

Regards

I'm using systemd to mount network mounts, for that I have to start/stop mnt-path.mount units. Currently, this isn't possible with the extension.

When a systemd service has a long-running ExecStartPre script, its toggle isn't being switched on, so it looks like the service failed to start.
Would be good to add some indication that a service is being started.

Is your feature request related to a problem? Please describe.
I would like to quickly pull up a running log of a service

Describe the solution you'd like
A button next to each service that opens a terminal with a command like this journalctl --user -u <service> -b -e -f, specifically with -b meaning logs from this boot, and -e -f meaning follow from the end of the log like tail -f.

Describe alternatives you've considered
Opening the terminal and typing the command manually (inconvenient)

Additional context
N/A

After toggling a service, the menu is hidden.
Sometimes I have to toggle several services in a row, that makes me click again on the extension to show the menu again, before toggling the next service.
I think systemd-manager's menu should remain on screen after toggling a service (until the user closes explicitly the menu by hitting or clicking somewhere else on the screen).
And even when toggling a single service, IMO the menu should remain. I think it's reassuring to see the toggling applied (but maybe that's just me)

Quoting from the website at https://extensions.gnome.org/extension/4174/systemd-manager/ :

New versions are available on github at https://github.com/hardpixel/systemd-manager/releases. This extension will not publish new versions here any more.

Why? And if so, could you please delete the links in the README?

Works for me on Gnome46:

-    this.add_actor(icon)
+    this.add_child(icon)

Thanks!

When I try to add services, I get the following error message:

`The settings of extension [email protected] had an error:

TypeError: Gtk.StyleContext.add_provider_for_display is not a function

Stack trace:

_init@/home/abc/.local/share/gnome-shell/extensions/[email protected]/prefs.js:28:24
buildPrefsWidget@/home/abc/.local/share/gnome-shell/extensions/[email protected]/prefs.js:262:18
_init@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:207:40
OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:122:28
asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:22
run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:177:20
main@resource:///org/gnome/Shell/Extensions/js/main.js:19:13
run@resource:///org/gnome/gjs/modules/script/package.js:206:19
start@resource:///org/gnome/gjs/modules/script/package.js:190:8
@/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17

`
System:
Manjaro Linux
Gnome Shell 3.38

Hello there,

Extension not working popos 21.04. Giving the error Tried to construct an object without a GType

Hi! I'd like to suggest an improvement where the extensions don't ask for permission/password for commands that is already allowed by sudo.

I know there is a way to achieve that by pkexec and the policy file org.freedesktop.policykit.pkexec.systemctl.policy, but I think there is a couple of reasons to allow the same behaviour using sudo.

First is verbosity. The file used to config pkexec is a huge and verbose xml. Second is granularity. As far as I know, there is no way to specify which services is allowed to change without password.

The same behaviour can be achieved putting this small piece of code in /etc/sudoers.d/systemctl, for exemple. It's clear, concise and it has exactly the commands it's allowed.

username ALL=NOPASSWD: /usr/bin/systemctl start docker.service --system
username ALL=NOPASSWD: /usr/bin/systemctl stop docker.service --system
username ALL=NOPASSWD: /usr/bin/systemctl restart docker.service --system

Thank you for all the work done. I'm using this extension and it's great!

When I try to use this with parameterized services like [email protected] and pass a parameter (e.g. [email protected]), it says that it could not find the service.

edit: fix the service names being recognized as e-mail addresses.

Is it possible to add support to mask and stop a service, instead of just stopping it ?

I sometimes mask the avahi-daemon service on some Wi-Fi networks, because I don't want any Wi-Fi printers popping up. Just stopping avahi-daemon is of no use, because it is automatically restarded. You need also to mask it.

It would be great if your extension would allow to mask and stop a service instead of just stopping it. Ideally this should be done on a per-service basis, allowing for each service to choose if toggling the switch just stops the service or also masks it.