New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Add: dunst service #11167
[WIP] Add: dunst service #11167
Conversation
Tests added. They do not really test the dunst service by now, but as you can see the dunstrc is not found. I do not know why. |
''; | ||
}; | ||
|
||
dmenu = mkOption { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the use case for configuring this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not even sure why there is such an option. I only "ported" the configuration file to a nix expression without thinking too much about the settings.
I've tried using this on top of the current I get failures in documentation generation
|
@bendlas : Afaik, this is not yet merged, right? Anyhow, how is the trace you provided related to what I've done in this PR? And how to reproduce? I will work on this asap, though atm I have not that much time. |
@matthiasbeyer I included your commits in my system, because a) I use dunst and b) I wanted to help you test. When I saw those failures, I bisected them back to your commits. For your convenience (and reference), I linked the current unstable channel branch + your 2 commits in my comment. The current unstable builds fine. |
You can build just the manual from the nixpkgs source root with: |
ac187fc
to
01fc873
Compare
What's the status of this PR ? |
@zimbatm I will have a closer look on what's missing tomorrow. I will then either close this PR unmerged or push it to be ready, though I cannot promise anything here! |
Wah, took me a bit longer than 1 days, I'm sorry. I have no longer any interest in this, feel free to reuse commits. |
01fc873
to
ccfdd2d
Compare
I'm interested again. I rebased to latest master and will now start working on this, but based on unstable, so I'm able to test it in a VM. |
This reverts commit 2c2437bd2432537f3b6da3749e35d0cbb130c326.
ccfdd2d
to
cb9be85
Compare
So here we go. The failure @bendlas reported was indeed caused by this PR, it was the descriptions where the markup was wrong. I simply removed the descriptions (they should be added later, as soon as this is working). What's working by now: dunst gets started by systemd. Anyways, dunst does not find the configuration file written via the config, though. For people testing this: Put this in your services.dunst = {
enable = true;
global = {
transparency = 50;
padding = 18;
horizontalPadding = 18;
};
frame = {
width = 8;
color = ''#FF0000'';
};
}; Dunst should then put the notifications on the right side of the screen and they should be styled rather ugly. The default config shows the notifications on the left side in light blue (when sending Here is help wanted ... I don't know why dunst does not find the configuration file and I really do not know why systemd reports it crashed when it is actually running. |
Is dunst forking itself by any chance? That would explain why maybe the parent would segfault but the child is still active. |
@zimbatm Dunst seems to be forking, yes. But I also set the |
If you can avoid the fork it generally is a good idea. Maybe there is a command-line option for that. |
nope, there is not, sadly. |
Weird, I just ran dunst from the command-line and it's running as foreground process. |
Yeah, it is really weird ... maybe you (or someone else who knows how services on nixos work) can find the problem... but I'm at my wits end. |
|
||
serviceConfig = { | ||
ExecStart = "${pkgs.dunst}/bin/dunst -config ${dunstConf} "; | ||
Type = "forking"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you try just removing this line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had it without this line before. Didn't help, though.
Is this still being worked on? |
@joachifm I'm still waiting for review here and suggestions what could fix the problem. |
Okay, but this is a lot of code that could be replaced simply by adding |
Looks like upstream has a pretty strange systemd service which is the basis for this AUR package. Could that hold the key to dunst not dying? |
@@ -270,6 +270,7 @@ | |||
toxvpn = 247; | |||
squeezelite = 248; | |||
turnserver = 249; | |||
dunst = 250; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't look like these are ever used in the configuration, am I missing something?
@siddharthist that is not a systemd service file. I'm dubious that the aur package actually does anything helpful. See https://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services for details. |
That said, using a dbus service instead of a systemd service might make sense anyhow. |
I would favor the new pull request (#19183) |
Service defintion for dunst.
Somehow I cannot build my system with this (
nixos-rebuild build -I nixpkgs=...
gives meerror: The option
services.dunst' defined in/nix/store/.../dunst.nix' does not exist
).Maybe someone can investigate?
Tests will follow...