Summary: | dev-libs/sway-0.13.0 fails to launch: cmd_permit:Unable to resolve IPC permit target '/usr/bin/swaylock' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | fuse809 |
Component: | Current packages | Assignee: | Mykyta Holubakha <hilobakho> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | proxy-maint, tsmksubc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Adding sway strace log |
Description
fuse809
2017-06-27 08:47:35 UTC
Created attachment 478156 [details]
Adding sway strace log
Emerging with the swaylock USE flag causes it to launch properly. So maybe the swaylock USE flag needs to be made mandatory. This is a known issue, which already is (or will be) fixed in the 0.14 release cycle. Can you reproduce with sway-9999[-swaylock]? Well I'll be it does also occur with dev-libs/sway-9999. So it can't be on the out with the upcoming release of Sway 0.14.0, unless, of course, someone requests this issue be fixed upstream. Here is the commit which fixes it: https://github.com/SirCmpwn/sway/commit/f745a3b3ef0b575d9a3ea802c338a003b0cc6af5\ Don't plan backport it to 0.13 (and revbump) though, as o.14 is coming really soon. Then why doesn't sway-9999[-swaylock] run properly? Surely it'd include that commit? Then why doesn't sway-9999[-swaylock] run properly? Surely it'd include that commit? Oops sorry for repeat comment didn't realize the first one got through. |