Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: After installation, the SDDM window doesn't go any further than that #1667

Open
DigiRon4ik opened this issue Jul 6, 2024 · 14 comments
Labels
enhancement New feature or request

Comments

@DigiRon4ik
Copy link

Feature Request

Description

Authorization just won't go through.

Additional Information

I installed Arch Linux on a virtual machine using archinstall where I specified the type as "minimal", created a user and changed the password for root. After the Arch Linux installation was complete, I followed the installation instructions of this repository.

pacman -Sy git
git clone --depth 1 https....
cd ~/HyDE/Scripts
./install.sh

I selected Y everywhere and only in the flatpacks installation selection did I do N. After that SDDM authorization window appeared, but I rebooted the system immediately. Everything works, the authorization window appears again. I try to authorize through the created user and nothing happens.

video

@DigiRon4ik DigiRon4ik added the enhancement New feature or request label Jul 6, 2024
@kRHYME7
Copy link
Collaborator

kRHYME7 commented Jul 6, 2024

maybe an upstream Hyprland bug.Please change to another TTY ,ctrl alt f3 .

Login, then run Hyprland

@aivx
Copy link

aivx commented Jul 23, 2024

I also have a GPU crash in virtualbox when I log in, if I enable 3D acceleration in the virtualbox settings, then the problem is solved, but the mouse cursor is also completely missing

@kRHYME7
Copy link
Collaborator

kRHYME7 commented Jul 23, 2024

@DigiRon4ik
Copy link
Author

maybe an upstream Hyprland bug.Please change to another TTY ,ctrl alt f3 .

Login, then run Hyprland

I tried it that way, but it didn't work.

@DigiRon4ik
Copy link
Author

I also have a GPU crash in virtualbox when I log in, if I enable 3D acceleration in the virtualbox settings, then the problem is solved, but the mouse cursor is also completely missing

I should try it, but I sat on fedora for a while, then went back to Windows. Fedora is buggy on my laptop. R5 4600U 16Gb RAM 512 SSD NVMe

@kRHYME7
Copy link
Collaborator

kRHYME7 commented Sep 11, 2024

I tried it that way, but it didn't work.

yeah I realized late that you're on a VM.

check hyprland wiki for running on a VM

@kRHYME7
Copy link
Collaborator

kRHYME7 commented Sep 11, 2024

but the mouse cursor is also completely missing

add to the config

cursor:no_hardware_cursors=true

check faq on hyprland wiki.

1 similar comment
@kRHYME7
Copy link
Collaborator

kRHYME7 commented Sep 11, 2024

but the mouse cursor is also completely missing

add to the config

cursor:no_hardware_cursors=true

check faq on hyprland wiki.

@XSebastian-GimenezX
Copy link

Does anyone know how to fix this problem if it's not a virtual machine? Because the same thing is happening to me but on my PC and it's giving me a lot of problems.

@kRHYME7
Copy link
Collaborator

kRHYME7 commented Sep 12, 2024

Does anyone know how to fix this problem if it's not a virtual machine? Because the same thing is happening to me but on my PC and it's giving me a lot of problems.

Depends Hyprland always breaks as it is constantly changing. Some old issues are now irrelevant.

@DigiRon4ik
Copy link
Author

Depends Hyprland always breaks as it is constantly changing. Some old issues are now irrelevant.

Can you elaborate on that? I didn't quite get it. I was wondering if I might have the same problem on my desktop PC.

@abenezerw
Copy link
Contributor

Black screen after sddm especially on vms are normal. But what he was saying is old problems get resolved and new problems might occur.
anyway can you mark this as resolved if fixed. @DigiRon4ik

@YuanziX
Copy link
Contributor

YuanziX commented Nov 14, 2024

I was facing this and found a "fix", basically there were two entries for hyprland, hyprland and hyprland (systemd service something); by default sddm was trying to open the systemd service one, just changed it to hyprland and it worked.

@XSebastian-GimenezX

@CodyNotFound
Copy link

I was facing this and found a "fix", basically there were two entries for hyprland, hyprland and hyprland (systemd service something); by default sddm was trying to open the systemd service one, just changed it to hyprland and it worked.

@XSebastian-GimenezX

That works on my new installed Arch. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

7 participants