Jump to content

Talk:Sway: Difference between revisions

483 bytes added ,  2 January 2022
Fixing the systemd scripts
imported>Rasmus-kirk
m (title)
imported>Rasmus-kirk
(Fixing the systemd scripts)
Line 2: Line 2:
== Issues with the kanshi service ==
== Issues with the kanshi service ==


Using the systemd service configuration from this page, does anyone else get a "failed to connect to display" on the kanshi.service? I didn't used to get this, months ago, so it at least ''used'' to work, and I don't think I fucked anything up. Also note that starting kanshi in a terminal emulator in sway still works just fine.
''Using the systemd service configuration from this page, does anyone else get a "failed to connect to display" on the kanshi.service? I didn't used to get this, months ago, so it at least ''used'' to work, and I don't think I fucked anything up. Also note that starting kanshi in a terminal emulator in sway still works just fine.''
 
Okay, I figured out how to fix it at least, you have to start sway using systemd at the "end" of the sway configuration file like so:
 
<code>
exec "systemctl --user import-environment; systemctl --user start sway-session.target"
</code>
This is instead of running the startsway script provided in the wiki. I'll do a proper write up when I have more time and update the wiki page.
 
--[[User:Rasmus-kirk|Rasmus-kirk]] ([[User talk:Rasmus-kirk|talk]]) 14:54, 2 January 2022 (UTC)
Anonymous user