SWAY version stuck on first start - no ideas left

[rico1]

Hi

I downloaded the latest ARM SWAY image from the website and flashed to USB.

On starting, the screen displays

discover_other_daemon:1

then goes to a splash screen showing ‘ARM’

and freezes.

From TTY2 I can log in as root, with no pw, and have updated

pacman -Syu

reboot

No change.

During the update process the message

systemd could not get information firstboot.service

was displayed.

systemctl list-unit-files

showed firstboot.service as static.

systemctl status firstboot

returned

unit not found.

nano /usr/lib/systemd/system/systemd-firstboot.service

returned the contents of the unit file.

The ArchWiki on GNOME/Keyring at para 6.17 states that the ‘discover_other_daemon:1’ message is returned if the gnome keyring daemon is started twice and recommends disabling it and the associated socket.

systemctl --user list-unit-files

showed gnome-keyring-daemon.service as ‘disabled’
and gnome-keyring-daemon.socket as ‘enabled’

systemctl --user enable gnome-keyring-daemon.service

reboot

Did not work.

systemctl --user disable gnome-keyring-daemon.service gnome-keyring-daemon.socket

reboot

Did not work either.

Out of ideas, other than to set user, pw, locale, timezone and keyboard via the terminal. Have not done that yet.

Cannot ssh into this machine at present because a pw (not yet set) is required for root. ‘root’ and ‘alarm’ do not work. So cannot post any extended output.

Any help gratefully recieved, and prps any changes can be folded into the distro.

Tks

R

[rico1]

Nobody able to help?

Tks R

[rico1]

Done some more digging and found these two posts:

An question about starting gnome-keyring-daemon in sway profile

Hello. I hope, I’m in right place. If not, please guide me where should I ask this question. I have pinebook, with swaywm (20.06) installed. I’m trying to understand how the manjaro with sway works. I have a question about a line in an overlay file for sway profile. Concretely /etc/sway/config.d/99-autostart-applications. There is a line that suppose to start gnome-keyring-daemon. # enable gnome-keyring daemon exec systemctl --user import-environment && gnome-keyring-daemon --components=ssh\,…

2 gnome-keyring-daemon instances after enabling unlocking keyring after login?

Hi. I’ve switched from Manjaro Gnome to Manjaro Sway. I’ve followed GNOME/Keyring - ArchWiki to initialize and unlock gnome-keyring at login. So far that seems to be working. But I now seem to have 2 instances of gnome-keyring-daemon running: 1645 1 0 10:29 ? 00:00:00 /usr/bin/gnome-keyring-daemon --daemonize --login 1894 1635 0 10:29 ? 00:00:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets The second one was already present before I enabled…

Both these posts relate to running instances with proper user credentials assigned.

I think that firstboot itself must be running - /etc/-machine-id is populated and if I delete it and reboot it is repopulated, which may indicate that at least part of firstboot is working.

I have had no luck with disabling the keyring daemon and socket in systemctl as suggested by the ArchWiki. Don’t know if this is because I can’t get a user specific session.

Given that I have to amend files either by mounting the image and working on a non-running instance, or by using TTY2 on a running instance as root, how can I proceed?

Any help greatly appreciated.

Tks
R