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

List of Effects to add is unreadable (white on white) #3372

Open
LxGuru opened this issue Sep 10, 2024 · 4 comments
Open

List of Effects to add is unreadable (white on white) #3372

LxGuru opened this issue Sep 10, 2024 · 4 comments

Comments

@LxGuru
Copy link

LxGuru commented Sep 10, 2024

The List is unreadable

Selection_003

Same problem for newly created user.
It works in VirtualBox Leap 15.5 and 15.6

How can I make it readable?

OpenSuse Leap 15.5
X11 Plasma
Nvidia GPU

@violetmage
Copy link
Contributor

This is not enough information. In the future, you should follow the issue template (when one is provided) for a project. Please provide the needed information:

Does the same behaviour happen in other menus?

Does it also happen in other gtk4 apps, like gedit?

Are you using the flatpak or a native easyeffects package?

@LxGuru
Copy link
Author

LxGuru commented Sep 10, 2024

Sorry, I didn't see the issue template.

All other menus are OK. I think, "Add Effect" menu is more dynamic that others.
gedit menus are OK.
I'm using the flatpak package (7.1.8)

Why does it work within VirtualBox at the same host?
What else can I tell?

@wwmm
Copy link
Owner

wwmm commented Sep 10, 2024

Why does it work within VirtualBox at the same host?
What else can I tell?

We do not apply customization to those labels. This feels like an issue in gtk4 or libadwaita. Specially considering that one of the horizontal lines is also missing.

Maybe the machine that has the problem is doing something to the libadwaita theme?

@violetmage
Copy link
Contributor

I think this is an nvidia proprietary driver thing, since OP mentioned nvidia+X11. The VM would of course be using a software virtual GPU, so it makes sense the issue would not occur there.

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