This reverts commit c5d0d5e837.
By starting i3 in a systemd unit, the user’s environment is lost.
This breaks too many workflows.
Blanket-importing the environment using systemctl import-environment
(without arguments) is explicitly discouraged in the systemctl man page.
It’s not clear how to fix this issue cleanly, so revert to unblock the release.
related to https://github.com/i3/i3/issues/5186
On Linux systems using systemd, we should activate graphical-session.target.
We conceptually need our i3.desktop file to do a
blockingly-run-via-systemd action (this is what scopes the activation of
graphical-session.target to the X session), and shipping an i3.service
is the best way to define the systemd unit we use for that.
Based on https://github.com/i3/i3/pull/5591 by David Sansome.
fixes https://github.com/i3/i3/issues/5186
This fixes issues with display link displays not working on i3 and
should not affect any other features from my testing.
Co-authored-by: FedGuy699 <bytebustersco@gmail.com>
