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

Segmentation fault after changing text scaling factor in arch (hyprland) #74

Open
TahsinAyman opened this issue Sep 20, 2024 · 4 comments

Comments

@TahsinAyman
Copy link

I changed the text scalling factor using nwg-look (gtk settings) in arch (hyprland) but after that my browser (chromium based) crashed and rofi stopped working even after reverting it still is the same. i check the console and it says segmentation fault (core dumped). but i can use alacritty, firefox etc.

I tried reverting but it didnt work

@nwg-piotr
Copy link
Owner

Well, what can I say? Nothing like this happens on my side. I can change text scaling factor freely back and forth. I'm on Arch/Hyprland as well.

@hey-adora
Copy link

hey-adora commented Oct 1, 2024

this might be related, a lot of apps such as sudo pacman -S code segfault after setting a theme using this. (selecting "Prefer dark" and clicking apply)
(also steam supposedly fails to launch according to my friends tests, but i ran out of disk space to confirm)

image
image

removing this file fixes everything tho
rm ~/.local/share/icons/default/index.theme

reproduction, this is how discovered it
create fresh arch install with hyprland, code and nwg-look
mkdir ~/local/share/icons
nwg-look - selecting "Prefer dark" and clicking apply
then run code - it should crash and close
and in journalctl -b 0 scroll down with page-down key, will see bunch of segfaults

@SolMill
Copy link

SolMill commented Oct 2, 2024

Removing ~/local/share/icons/default/index.theme solved the issue for me. Thank you!
All electron applications (spotify-launcher, discord, steam) got segfault before.

@harshil21
Copy link

Completely found this issue by accident. Had been plauging me for days. Thanks @hey-adora for the fix!

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

5 participants