Skip to content
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

haskellPackages.dbus: multiple addresses patch #68529

Closed
wants to merge 1 commit into from

Conversation

averelld
Copy link
Contributor

@averelld averelld commented Sep 11, 2019

Motivation for this change

xmonad breaks for me because of #68498. This reintroduces an old patch removed in 87ec7bb (While multiple addresses was upstreamed as parseAddresses, that function is not actually used for the env variables, so the issue remains).

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @

@srhb
Copy link
Contributor

srhb commented Sep 11, 2019

Can you justify this patch a bit? I'm still not convinced that applications should survive this change trivially. And if they should, it sounds more like an upstream issue. :)

@averelld
Copy link
Contributor Author

I'm not certain either, so I opened rblaze/haskell-dbus#37 :)
Anyway, they have basically getenv "DBUS_SESSION_BUS_ADDRESS" >>= parseAddress, and at the same time they bundle a parseAddresses (which this patch uses) which is for some reason used nowhere internally.
So if that address format is legal, it should be properly supported (and probably not like in this patch, but by trying each of them in sequence on failure).

@lheckemann lheckemann added this to the 19.09 milestone Sep 12, 2019
@turboMaCk
Copy link
Member

I can't log into none + xmonad at all after update to latest nixos-unstable and reboot. I'm using dbus in my xmonad config as well. Is this the same issue?

@averelld
Copy link
Contributor Author

That is likely. You could start an xterm or i3 session and run it manually, then you should see some related error message. Or apply the patch locally and don't forget xmonad --recompile.

@turboMaCk
Copy link
Member

so far I tried to use gnome + xorg and tried to run xmonad from terminal there. I can confirm I see error related to dbus. When I rollback to the generation where xmonad works for me and try to run it under gnome I don't see this error but expected BadAccess one so I think this is indeed the cause.

@turboMaCk
Copy link
Member

Now I can fully confirm that this turboMaCk/Dotfiles#19 resolved all issues for me.

@peti
Copy link
Member

peti commented Sep 19, 2019

This sounds like an issue that upstream should make a decision about -- not we.

@averelld
Copy link
Contributor Author

Looks like they will, or they would also accept this patch, see linked issue above.
Meanwhile we should still merge this until an upgrade is in place (since the multiple addresses are probably here to stay?).

@peti
Copy link
Member

peti commented Sep 19, 2019

Looks like they will, or they would also accept this patch, see linked issue above.

Once they have accepted this patch, I'll be perfectly happy to apply it to our package, too.

@RubenAstudillo
Copy link
Contributor

Once they have accepted this patch, I'll be perfectly happy to apply it to our package, too.

I've submitted a PR on that repo based on the post patch of @averelld . If that is accepted when can either use that version of dbus or ship the patch on nixos and apply it locally.

@RubenAstudillo
Copy link
Contributor

RubenAstudillo commented Oct 5, 2019

The PR was accepted and merged, haskell-dbus v1.2.11 was published. We should use that.

@peti
Copy link
Member

peti commented Oct 6, 2019

We have dbus-1.2.11 in haskell-updates already. It's not used by default yet, because LTS Haskell still recommends the 1.2.7 version. I suppose that would change with the next release.

@averelld
Copy link
Contributor Author

Closing, this will be solved by an upstream update with this change instead.

@averelld averelld closed this Oct 15, 2019
@averelld averelld deleted the haskell-dbus-multi branch October 15, 2019 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants