622808 – dev-libs/sway-0.13.0 fails to launch: cmd_permit:Unable to resolve IPC permit target '/usr/bin/swaylock'

Bug 622808 - dev-libs/sway-0.13.0 fails to launch: cmd_permit:Unable to resolve IPC permit target '/usr/bin/swaylock'

Summary: dev-libs/sway-0.13.0 fails to launch: cmd_permit:Unable to resolve IPC permit...

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Mykyta Holubakha

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2017-06-27 08:47 UTC by fuse809
Modified:	2017-07-03 10:52 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Adding sway strace log (sway.log,100.20 KB, text/x-log) 2017-06-27 08:48 UTC, fuse809	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description fuse809 2017-06-27 08:47:35 UTC

Whenever I launch dev-libs/sway-0.13.0 from SDDM or the command-line it fails. The error I get when I launch it from the command-line (as I am unaware of ways to get the error when launched from SDDM) is:

06/27/17 18:30:00 - [permit.c:62] cmd_permit:Unable to resolve IPC permit target '/usr/bin/swaylock'. will issue empty policy
06/27/17 18:30:00 - [security.c:156] Unable to allocate security policy
[1]    10226 segmentation fault (core dumped)  sway

I will try to attach the strace.log (which may fail due to attachment.cgi issues I've had) I got from:

strace -o strace.log sway

but if it doesn't work here is the pastebined log: 

https://paste.pound-python.org/show/CNAi7636FcVNGguFqd9Q/

I tried following the "Debugging with GDB" Gentoo Wiki guide, here is the run output:

Starting program: /usr/bin/sway AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[Inferior 1 (process 32401) exited with code 01]

bt returns:

"No stack."

emerge -pqv '=dev-libs/sway-0.13.0' returns:

[ebuild   R   ] dev-libs/sway-0.13.0  USE="gdk-pixbuf swaybar swaybg swaymsg systemd -swaygrab -swaylock -wallpapers -zsh-completion"

If there is any further information you's need just ask.

Comment 1 fuse809 2017-06-27 08:48:53 UTC

Created attachment 478156 [details]
Adding sway strace log

Comment 2 fuse809 2017-06-27 09:02:23 UTC

Emerging with the swaylock USE flag causes it to launch properly. So maybe the swaylock USE flag needs to be made mandatory.

Comment 3 Mykyta Holubakha 2017-07-01 11:46:31 UTC

This is a known issue, which already is (or will be) fixed in the 0.14 release cycle.

Comment 4 Mykyta Holubakha 2017-07-01 11:52:56 UTC

Can you reproduce with sway-9999[-swaylock]?

Comment 5 fuse809 2017-07-01 12:16:08 UTC

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.

Comment 6 Mykyta Holubakha 2017-07-01 18:50:50 UTC

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.

Comment 7 fuse809 2017-07-03 10:36:02 UTC

Then why doesn't sway-9999[-swaylock] run properly? Surely it'd include that commit?

Comment 8 fuse809 2017-07-03 10:52:07 UTC

Then why doesn't sway-9999[-swaylock] run properly? Surely it'd include that commit?

Comment 9 fuse809 2017-07-03 10:52:28 UTC

Oops sorry for repeat comment didn't realize the first one got through.