Hello, total newbie here to endeavouros and every time i log in with sway my pc just shows me the number 1 on the top left and the time on the top right. i am currently following a tutorial and currently nothing is working to replicate the results of the tutorial at 10:20. for context this is the tutorial that i followed to a T. this is the video: https://youtu.be/jFz5gLqv-FM. the only other time i have seen this problem exist online the user wiped their disk to fix it which is entirely out of the question for me. I would appreciate any and all help.
How did you install Sway? Here is a link that may be helpful to install Sway on EndeavourOS.
Welcome to the forum @apopi !
I do not want to feel the pain of following this superfluously long installation and tinkering procedure..
The reason you get this result: sway directory (at least) was missing.
git clone https://github.com/diinki/diinki-retrofuture.git
and move the directories from below his/her config
to ~/.condig with a file manager you prefer.
What video card do you have?
I reproduced the procedure OP used. It has nothing to do with video card.
1 Like
Hello! Thanks so much for your reply. do i replace the directories?
Re sway waybar kitty I think so. But you may rename the old ones.
It won’t solve all your problems. Edit sway config as the default keyboard is Swedish.
IMHO the ‘official’ Community version of sway Rick suggested above is a far better starting point for Sway
and you may replace some elements step-by-ster from those of diinki-retrofutu later.
While this method worked perfectly for me to install sway it created another issue:
I can’t start i3-wm (with which i had installed the System) anymore with the new greeter…
And sadly the gaming performance with sway is VERY bad for me!
(While i had 0 issues with i3 on X11)
I also already tried running the EndeavorOS install script for i3 (found that in another Thread)
But i still have the same issue:
i3 comes up and loads up to the point where i have a desktop and a bar but then it gets stuck (curser becomes a watch symbol)
And i can’t launch any Apps when in that state..
@joekamprad the i3-wm fix is almost perfect. A big thank for all of you.
After login the cursor becomes a watch symbol for 60 seconds
Not a blocking obstacle but not nice.
journalctl -f
márc 19 19:19:14 a-83k7 at-spi2-registryd[22052]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
márc 19 19:19:14 a-83k7 systemd[21847]: Starting Virtual filesystem metadata service...
márc 19 19:19:14 a-83k7 systemd[21847]: Started Virtual filesystem metadata service.
márc 19 19:19:15 a-83k7 NetworkManager[902]: <info> [1773944355.0205] agent-manager: agent[46130337de7b34c0,:1.461/org.freedesktop.nm-applet/1000]: agent registered
márc 19 19:19:15 a-83k7 wireplumber[21946]: spa.bluez5: BlueZ system service is not available
márc 19 19:19:15 a-83k7 wireplumber[21946]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
márc 19 19:19:15 a-83k7 wireplumber[21946]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
márc 19 19:19:16 a-83k7 wireplumber[21946]: m-portal-permissionstore: <WpPortalPermissionStorePlugin:0x563854ccfef0> Lookup: The name is not activatable (org.freedesktop.DBus.Error.ServiceUnknown)
márc 19 19:19:17 a-83k7 systemd[21847]: Starting Xfce configuration service...
márc 19 19:19:17 a-83k7 systemd[21847]: Started Xfce configuration service.
márc 19 19:19:24 a-83k7 systemd[1]: Stopping User Manager for UID 965...
márc 19 19:19:24 a-83k7 systemd[21610]: Activating special unit Exit the Session...
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped target Main User Target.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped target Sound Card.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopping Accessibility services bus...
márc 19 19:19:24 a-83k7 dbus-broker[21659]: Dispatched 20 messages @ 9(±11)μs / message.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopping dbus-:1.6-org.a11y.atspi.Registry@0.service...
márc 19 19:19:24 a-83k7 systemd[21610]: Stopping User preferences database...
márc 19 19:19:24 a-83k7 systemd[21610]: Stopping Virtual filesystem service...
márc 19 19:19:24 a-83k7 systemd[21610]: Stopping Virtual filesystem metadata service...
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped User preferences database.
márc 19 19:19:24 a-83k7 systemd[1]: run-user-965-gvfs.mount: Deactivated successfully.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped Accessibility services bus.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped Virtual filesystem service.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped Virtual filesystem metadata service.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped dbus-:1.6-org.a11y.atspi.Registry@0.service.
márc 19 19:19:24 a-83k7 systemd[21610]: Removed slice Slice /app/dbus-:1.6-org.a11y.atspi.Registry.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped target Basic System.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped target Paths.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped target Sockets.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped target Timers.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed GnuPG network certificate management daemon.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
márc 19 19:19:24 a-83k7 systemd[21610]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
márc 19 19:19:24 a-83k7 systemd[21610]: Closed GnuPG cryptographic agent (ssh-agent emulation).
márc 19 19:19:24 a-83k7 systemd[21610]: Closed GnuPG cryptographic agent and passphrase cache.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed GnuPG public key management service.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed p11-kit server.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed PipeWire PulseAudio.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed PipeWire Multimedia System Sockets.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed Query the User Interactively for a Password.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed Disk Image Download Service Socket.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed Virtual Machine and Container Registration Service Socket.
márc 19 19:19:24 a-83k7 dbus-broker[21625]: Dispatched 787 messages @ 4(±5)μs / message.
márc 19 19:19:24 a-83k7 systemd[21610]: Stopping D-Bus User Message Bus...
márc 19 19:19:24 a-83k7 systemd[21610]: Stopped D-Bus User Message Bus.
márc 19 19:19:24 a-83k7 systemd[21610]: Removed slice User Core Session Slice.
márc 19 19:19:24 a-83k7 systemd[21610]: Closed D-Bus User Message Bus Socket.
márc 19 19:19:24 a-83k7 systemd[21610]: Removed slice User Application Slice.
márc 19 19:19:24 a-83k7 systemd[21610]: Reached target Shutdown.
márc 19 19:19:24 a-83k7 systemd[21610]: Finished Exit the Session.
márc 19 19:19:24 a-83k7 systemd[21610]: Reached target Exit the Session.
márc 19 19:19:24 a-83k7 systemd-logind[815]: Removed session 12.
márc 19 19:19:24 a-83k7 (sd-pam)[21612]: pam_unix(systemd-user:session): session closed for user lightdm
márc 19 19:19:24 a-83k7 systemd[1]: user@965.service: Deactivated successfully.
márc 19 19:19:24 a-83k7 systemd[1]: Stopped User Manager for UID 965.
márc 19 19:19:24 a-83k7 systemd[1]: Stopping User Runtime Directory /run/user/965...
márc 19 19:19:24 a-83k7 systemd[1]: run-user-965.mount: Deactivated successfully.
márc 19 19:19:24 a-83k7 systemd[1]: user-runtime-dir@965.service: Deactivated successfully.
márc 19 19:19:24 a-83k7 systemd[1]: Stopped User Runtime Directory /run/user/965.
márc 19 19:19:24 a-83k7 systemd[1]: Removed slice User Slice of UID 965.
márc 19 19:19:24 a-83k7 systemd[1]: user-965.slice: Consumed 2.803s CPU time over 23.086s wall clock time, 109.5M memory peak.
márc 19 19:19:24 a-83k7 accounts-daemon[940]: couldn't list homed users: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.home1': activation request failed: unknown unit
what exactly?
missing user config from skel issue from yesterday.
It means config file contains lines which do not match the installed packages.
Check the exec lines first of all.
Or log in with log mode and
i3-dump-log | less
helps you to find the lines causing time-outs (60 sec here).