You are not logged in.
I'm new to Arch and sway (though I'm a Linux veteran).
I have this all running with no problem on my pi5 with aarch, but it's so good I've decided to run it now on my intel laptop. So, yesterday, I slapped in a new nvme drive and got to work. Arch x86 is installed, with a working network.
But, when I start sway it shows a grey screen with a 1 in the top left and the date and time in the top right. I have a dual screen configured so I can see a 2 on the second screen. The whole thing is then almost completely unresponsive, and I have to cycle the machine power. The keyboard elicits almost no response, but windows+1 or 2 does change the number that's highlighted.
How do I proceed to diagnose this?
Last edited by SoftwareEngineer (2024-08-21 13:30:14)
Offline
Can you switch VT? (Ctrl+Alt+F2..F3 or so?), post
sudo journalctl -b | curl -F 'file=@-' 0x0.st
if you can't, enable https://wiki.archlinux.org/title/Keyboa … el_(SysRq) and check whether you can reboot safely with the REISUB sequence instead of powercycling and upon reboot into a terminal session post
sudo journalctl -b-1 | curl -F 'file=@-' 0x0.st
instead,
Offline
Switching to vt works of course, and I can kill sway that way too. Interestingly, the error that causes complains that it cannot start xwayland because it can't find the binary, but pacman reports that wayland is installed and up to date.
I'm using this forum on my phone until I get a browser running (I've never been good at lynx), so sorry for any typos.
Offline
xwayland would be in the xorg-xwayland package. There's also a nvidia Pascal GPU getting driven by nouveau which might lead to issues, though there's no direct indication of that in the log
Offline
Yeah, the machine also has an old Nvidia GPU installed but I never use it and haven't installed the drivers for it.
Any clues on how to proceed?
Offline
I suppose you already installed xorg-xwayland as suggested, right?
Offline
I've largely solved most of the issues I was having by wiping the whole drive and starting again. It all worked the second time through. Sorry I can't offer much insight into what the root cause was, but starting again and making sure that you follow the instructions does seem to be a successful approach So, as usual, it seems it was just user error.
In fact, I'm now writing this reply in a firefox browser all cuddled up nicely against my terminal on my laptop screen, while my big monitor is running VIM (that's normal vim, but on a 42" 4k monitor). And magically, my aging xps is fast and useful again.
Now all I have left to do work out how to mark this thread as solved
Thanks for the help.
Offline
Now all I have left to do work out how to mark this thread as solved
That is indeed not that clear: click the "edit" link on your first post in the thread and you will get the option to edit the title. Then just prepend "[SOLVED]" to the title.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Got it, thanks
Offline