user18130814200115-2 / riverbed

My river configuration
10 stars 0 forks source link

Install instructions unclear #2

Open user18130814200115-2 opened 1 week ago

MNkoder commented 1 week ago

so i started the script and then i got some key error, so i did what it said and fixed it, then some abuild error, fixed it and then when i ran it for the 3rd time came another abuild-apk error, i think it was regarding my user not in abuild group or something. So i added my user to the abuild group but still the same error showed up, tried multiple times, still showed that my user was not in the abuild group. Then i rebooted and now cant login, its showing a "-sh: exec: line 4: /home/em-en/.config/river/launch: Permission denied"

user18130814200115-2 commented 1 week ago

Okay I will automate the abuild stuff, for now, this command should fix the permission denied stuff

chmod +x ~/.config/river/init ~/.config/river/keybinds ~/.config/river/launch ~/.gnupg/pinentry-tofi ~/.local/bin/*

I will look into this issue. Also, please update to the latest version, I just pushed some patches that will smoothe over your process.

user18130814200115-2 commented 1 week ago

Also if you switch to tty2 with ctrl alt 2 you can login to the console like normal

MNkoder commented 1 week ago

alright now its showing "doas: usermod: command not found" , also you dont need to fix it right away, take your own time. I dont wanna trouble you lol

user18130814200115-2 commented 1 week ago

Mmm okay, i’ll fix that later for real. For now, i think ‘apk add shadow’ should fix this issue.

Also don't worry about wasting my time, I am really happy to have someone interested who is willing to do some trial and error. It greatly helps the development process.

MNkoder commented 1 week ago

Mmm okay, i’ll fix that later for real. For now, i think ‘apk add shadow’ should fix this issue.

Also don't worry about wasting my time, I am really happy to have someone interested who is willing to do some trial and error. It greatly helps the development process.

glad you're taking it that way :)

user18130814200115-2 commented 19 hours ago

The latest verion of the install script should prevent the softlock you experienced. Did you manage to get things working in the meantime?

MNkoder commented 14 hours ago

IMG20240917193113 Hey really sorry for the late reply.. I've attached a picture, this is as far I could get. Please do lmk if it's not clear

user18130814200115-2 commented 14 hours ago

Okay that’s actually very close it seems. River is crashing somehow, and from this picture I can’t tell why.

If you login to tty2 with ctrl alt 2, please try running: ‘seatd-launch river’

if that still crashes, try installing a terminal emulator like foot and then running: ‘seatd-launch river -c foot’

If that still crashes, then you can try running without seatd-launch by first running ‘rc-service seatd start’ and then ‘river’ or ‘river -c foot’

Please let me know what happens with these. Then I can troubleshoot what exactly is going wrong :)

MNkoder commented 14 hours ago

Okay that’s actually very close it seems. River is crashing somehow, and from this picture I can’t tell why.

If you login to tty2 with ctrl alt 2, please try running: ‘seatd-launch river’

if that still crashes, try installing a terminal emulator like foot and then running: ‘seatd-launch river -c foot’

If that still crashes, then you can try running without seatd-launch by first running ‘rc-service seatd start’ and then ‘river’ or ‘river -c foot’

Please let me know what happens with these. Then I can troubleshoot what exactly is going wrong :)

IMG20240917195334

user18130814200115-2 commented 14 hours ago

Right. Please run ‘adduser $USER seat’ then log out and back in. then please try again :)

MNkoder commented 14 hours ago

Right. Please run ‘adduser $USER seat’ then log out and back in. then please try again :)

IMG20240917200428

nope still the same :(

user18130814200115-2 commented 14 hours ago

This failure is understandable with the auto launch for now (enabling seatd system service does not pay nicely with seatd-launch) What is the output of running river on tty2?

MNkoder commented 14 hours ago

This failure is understandable with the auto launch for now (enabling seatd system service does not pay nicely with seatd-launch) What is the output of running river on tty2?

IMG20240917201126

user18130814200115-2 commented 14 hours ago

Sorry for being unclear ‘rc-service seatd start’ and then ‘river’

MNkoder commented 13 hours ago

Sorry for being unclear ‘rc-service seatd start’ and then ‘river’

IMG20240917201834

MNkoder commented 13 hours ago

hey I forgot to mention it is a vm, that day when I tested it, it was on my laptop, but today I'm doing it in a vm, would that be the problem?

user18130814200115-2 commented 13 hours ago

I doing think running in a vm should be a problem, though i never tested it.

We are making good progress though, seatd is not the problem. To resolve the error on screen now, run:

‘rc-service seatd start’ ‘export XDG_RUNTIME_DIR=$(mkrundir)’ ‘river’

MNkoder commented 13 hours ago

Screenshot from 2024-09-17 21-04-31

user18130814200115-2 commented 12 hours ago

Perfect, this is the error message i was actually trying to see (: Good thing is, the errors are no longer my fault :) rather they are a problem with river, more specifically wlroots.

So, the problem is that wlroots (the library used by river) fails to create a display environment. This problem could occur for several reasons, though i suspect the vm might be to blame. It could however also be a graphics driver issue, especially if you are using NVIDIA graphics.

I recommend trying to run river on the laptop, make sure you are in the seat group (useradd $USER seat) as before.

If you only have NVIDIA graphics, consider using the open source drivers https://github.com/swaywm/sway/wiki#nvidia-users If you have Nvidia Graphics and integrated ones, try switching to integrated graphics only https://github.com/swaywm/sway/wiki#i-have-a-multi-gpu-setup-like-intelnvidia-or-intelamd-and-sway-does-not-start--some-video-cards-cannot-display--full-screen-images-etc-will-be-corrupted

If you are really committed to the VM, then it is probably possible to setup GPU passthrough, though this is hard and I can’t really help you with it, since i have never done this.

I really wish i could help you more though this issue is a little out of my hands.

MNkoder commented 12 hours ago

Perfect, this is the error message i was actually trying to see (: Good thing is, the errors are no longer my fault :) rather they are a problem with river, more specifically wlroots.

So, the problem is that wlroots (the library used by river) fails to create a display environment. This problem could occur for several reasons, though i suspect the vm might be to blame. It could however also be a graphics driver issue, especially if you are using NVIDIA graphics.

I recommend trying to run river on the laptop, make sure you are in the seat group (useradd $USER seat) as before.

If you only have NVIDIA graphics, consider using the open source drivers https://github.com/swaywm/sway/wiki#nvidia-users

If you are really committed to the VM, then it is probably possible to setup GPU passthrough, though this is hard and I can’t really help you with it, since i have never done this.

I really wish i could help you more though this issue is a little out of my hands.

nah man thats alright, its probably something up with the vm. But my gpu is not nvidia, i have an amd gpu and yes i'll try to run it on my laptop