You mean for services.teamviewer.enable = true; ? No, you should not need any reboot: when you set services.teamviewer.enable = true; NixOs is clever enough to start/stop/restart the good services. If you set services.teamviewer.enable = false;, it will completely uninstall teamviewer, so sudo systemctl start teamviewerd.service will not work. You can however disable the daemon if you don’t want it to start by default, I guess:
OK, without reboot it won’t work. Can later try after reboot…
[wolf@daw:~]$ sudo systemctl start teamviewerd
Failed to start teamviewerd.service: Unit teamviewerd.service has a bad unit file setting.
See system logs and ‘systemctl status teamviewerd.service’ for details.
[wolf@daw:~]$ sudo systemctl status teamviewerd
○ teamviewerd.service
Loaded: bad-setting (Reason: Unit teamviewerd.service has a bad unit file setting.)
Active: inactive (dead)
Jan 11 15:53:11 daw systemd[1]: teamviewerd.service: Service has no ExecStart=, ExecStop=, or SuccessAction=.>
Jan 11 15:53:22 daw systemd[1]: teamviewerd.service: Service has no ExecStart=, ExecStop=, or SuccessAction=.>
Jan 11 15:53:33 daw systemd[1]: teamviewerd.service: Service has no ExecStart=, ExecStop=, or SuccessAction=.>
lines 1-7/7 (END)
Oh, you need both: the first line just tells “please install teamviewer and create a new service called teamviewerd”, the second line just says “in the teamviewerd service, remove the line wantedBy, i.e. do not start it automatically”.
The ${placeholder "out"}/bin should be removed to keep the path relative, as advised here What is the recommended use of makeDesktopItem? How to setup the icon correctly? - #6 by zarel as it allows better theming, wrappers by users etc. Right now, the issue is that makeDesktopItem will create first a different derivation, as seen in your screenshot, that contains wnly the desktop file, so the placeholder will point to this nearly empty directory.
I don’t have a computer with me right now, but it can be a nice simple first pull request for you if you want to get involved in nixpkgs. If not, just create a new issue in github with the maintainers of the package (cf names at the end of the above link) and me in mention, explaining what I just explained above.
And right now, you can temporarily fix your issue by using overrideAttrs, like replace anydesk.in your configuration with something like
Oh, that’s very simple. Some 48V powered condenser microphones, a mixer with usb audio interface and the software “butt” to stream the audio to an icecast server, the studio is playing out the stream to put it on the air.
[wolf@schwoon-desktop:~/APP]$ ./MQTT-Explorer-0.4.0-beta1.AppImage
Could not start dynamically linked executable: ./MQTT-Explorer-0.4.0-beta1.AppImage
NixOS cannot run dynamically linked executables intended for generic
linux environments out of the box. For more information, see: Frequently Asked Questions — nix.dev documentation
For App images, you can sometimes use appimage-run ./yourimage.AppImage, but sometimes it fails without obvious error message if a lib is missing. Enabling:
programs.nix-ld.enable = true;
will save you quite some headacke, especially if you develop/use nodejs applications that love to include pre-build binaries. Of course, you can also package the application yourself and submit it in nixpkgs, either from source (for Electron app it might be less obvious than for usual apps), or directly by wrapping the app image, apparently someone already tried to do that here for your program mqtt-explorer.nix · GitHub.
And it will automatically build it, and put you in a shell with the binary installed. Run it: if it works, comment that it works for you in the above github PR link