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

VibrantLinux Stopped Working On Arch Linux #50

Open
ghost opened this issue Nov 28, 2022 · 9 comments
Open

VibrantLinux Stopped Working On Arch Linux #50

ghost opened this issue Nov 28, 2022 · 9 comments

Comments

@ghost
Copy link

ghost commented Nov 28, 2022

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

@Scrumplex
Copy link
Member

Is it possible that you have switched to a Wayland session?

@ghost
Copy link
Author

ghost commented Nov 28, 2022

[a@PC ~]$ loginctl
SESSION UID USER SEAT TTY
2 1000 a seat0

1 sessions listed.
[a@PC ~]$ loginctl show-session 2 -p Type
Type=x11

So, I assume not.

I did this aswell:
[a@PC ~]$ loginctl show-session $(loginctl | grep $(whoami) | awk '{print $1}') -p Type
Type=x11

@ghost
Copy link
Author

ghost commented Nov 28, 2022

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.
I guess it's something to do with Arch packages.

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:

3 aur/vibrantlinux-git 2.1.10.r0.g5877b71-1 (+2 0.00) (zainstalowano)
    vibranceGUI replacement for Linux
2 aur/vibrantlinux 2.1.10-1 (+3 0.00) 
    A tool to automate managing your screen's saturation depending on what programs are running
1 chaotic-aur/vibrantlinux 2.1.10-1.1 (272.5 KiB 559.5 KiB) 
    A tool to automate managing your screen's saturation depending on what programs are running

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...
I've tried:

sudo downgrade vibrantlinux

But there is only one package, I cannot downgrade.

@ghost
Copy link
Author

ghost commented Dec 8, 2022

I also installed it via Flatpak and it's not working:

[a@PC ~]$ flatpak run io.github.libvibrant.vibrantLinux 
Gtk-Message: 07:27:31.472: Failed to load module "xapp-gtk3-module"
Gtk-Message: 07:27:31.472: Failed to load module "xapp-gtk3-module"
Gtk-Message: 07:27:31.472: Failed to load module "canberra-gtk-module"
Gtk-Message: 07:27:31.472: Failed to load module "canberra-gtk-module"
Qt: Session management error: Could not open network socket
QApplication: invalid style override 'kvantum' passed, ignoring it.
	Available styles: Breeze, Windows, Fusion
terminate called after throwing an instance of 'std::runtime_error'
  what():  this system has no supported displays

Any news? It's been a while and no response...

@Scrumplex
Copy link
Member

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

@ghost
Copy link
Author

ghost commented Dec 8, 2022

Yes, you were right.

sudo pacman -R xf86-video-amdgpu

Solved the issue. I wonder why xf86-video-amdgpu is recommended when installing vulkan driver for AMD cards...

@EXtremeExploit
Copy link

its also recommended for 2d hw acceleration https://wiki.archlinux.org/title/AMDGPU
without the package my xorg session refuses to start, so its not really a solution

@ghost
Copy link
Author

ghost commented Mar 13, 2023

I have two desktop environments, Plasma and Xfce4.
Both are working without this package.
Also, on Xfce4 settings I can disable compositing, so I don't have any effects, and it's still good after restart.

Plasma runs with X11, not with Wayland session. The same is with XFCE4.

@nickkstuff
Copy link

Same issue on Fedora 38 X11 Session.
I wonder if there is a way to make it work without removing xorg-x11-drv-amdgpu.x86_64

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

No branches or pull requests

3 participants