-
Notifications
You must be signed in to change notification settings - Fork 7
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
VibrantLinux Stopped Working On Arch Linux #50
Comments
Is it possible that you have switched to a Wayland session? |
[a@PC ~]$ loginctl 1 sessions listed. So, I assume not. I did this aswell: |
I have two disks, so I booted to Arch Craft Linux and without updates it worked. But after I updated, it stopped working again. This ArchCraft system was not updated for a week or so. On my main system I have Arco Linux, and I'm updating more frequently, that's why VibrantLinux stopped working sooner. What should I do, so it's working again? I have searched for find /home/ -name vibrant*In my home directory, but there is no config that I can reset. Is there any config to your program so I can try to reset it? I've tried to install 3 different packages via yay:
And it's the same problem. I will try to install older version of it and see what happens. ... and there is no older versions...
But there is only one package, I cannot downgrade. |
I also installed it via Flatpak and it's not working:
Any news? It's been a while and no response... |
I only know that people often have issues with their X11 driver. What GPUs have you tried? If both were Intel you might need a different X11 driver. See #39 |
Yes, you were right.
Solved the issue. I wonder why xf86-video-amdgpu is recommended when installing vulkan driver for AMD cards... |
its also recommended for 2d hw acceleration https://wiki.archlinux.org/title/AMDGPU |
I have two desktop environments, Plasma and Xfce4. Plasma runs with X11, not with Wayland session. The same is with XFCE4. |
Same issue on Fedora 38 X11 Session. |
It stopped working. Tested on two GPU's, and it's the same.
terminate called after throwing an instance of 'std::runtime_error'
what(): this system has no supported displays
The text was updated successfully, but these errors were encountered: