Mako module stopped work

[timsofteng]

Hello. I find mako notification module stopped work. Daemon doesn't start. I can't see it in my processes and notifications doen't work. Is it knowing issue?

[sumnerevans]

I have the following in my config to fix the issues with dbus: https://git.sr.ht/~sumner/home-manager-config/tree/master/item/modules/window-manager/wayland.nix#L64

[berbiche]

This might be of interest: https://github.com/alebastr/sway-systemd

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information.

Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[asymmetric]

Can we reopen this issue? As it is, the mako module is broken.

@sumnerevans could you point a permalink to the relevant portion of your config?

[berbiche]

@asymmetric hi, do you have multiple notification daemons on your system? They are likely fighting to register for the notification daemon.

If you run the following command, you should get whether a notification daemon (mako or something else) is receiving notifications: dbus-send --print-reply --dest=org.freedesktop.DBus /org/freekdesktop/DBus org.freedesktop.DBus.ListNames | grep Notifications

[asymmetric]

@berbiche I don't have any notification daemon running, actually. Running that snippet returns empty.

To fix the issue, I now run mako explicitly in my sway config with exec mako, but this wasn't necessary before.

Can you instead confirm that just having programs.mako.enable = true in your config gives a different result?

[sumnerevans]

Not sure if this actually fixes people's problems, but I see this in my git commit log, which means that it maybe is necessary? https://github.com/sumnerevans/home-manager-config/commit/f82aacb32cb25145b614bc1d4fd907617c416b6e

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[samhh]

Is the mako module as currently defined supposed to start it as a daemon? I've had to define my own systemd unit instead:

{
  systemd.user.services.mako = {
    Install.WantedBy = [ "sway-session.target" ];
    Service.ExecStart = "${pkgs.mako}/bin/mako";
  };
}

Edit: Fixed for me at least as of https://github.com/nix-community/home-manager/pull/3265 (https://github.com/samhh/dotfiles/commit/af070b79e9b89c5e41232f52f60abce0de9003ed#diff-7536197b458a062a5438cefcc8295345b714338c10b88d708fcca0e6a0ba0f81).

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.