You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I did stupid thing when adjusting my system-monitor-next, trying what every setting do etc. and I checked the show all cores separately box. Now my GNOME bar is broken, I can't hit preferences window again, I can't open quick menu for power or network/bluetooth.
So I am asking, is there any way of changing this via terminal and if is, can you add it to readme?
If this don't belongs here, feel free to delete, I guess this will be OK after disabling hyperthreading and unchecking the box. EDIT: disabling hyperthreading helped, but if someone do this with 32+ cores it could be problem.
The text was updated successfully, but these errors were encountered:
How dare you use the available settings! 😜 Haha this is definitely an issue with the extension, you didn't do anything stupid.
In terms of a fix, the only thing I can think of is a best-effort estimate of the height of our popup. When it gets too tall (> 80% of the user's screen height?) we start eliding cores. I don't think any other setting is capable of exploding the height of the popup like this.
I'll leave this issue open since we should fix this. In the meantime, in case anyone else has this issue before we get it fixed, you should be able to reset the "Display Individual Cores" setting from the command line with:
I did stupid thing when adjusting my system-monitor-next, trying what every setting do etc. and I checked the show all cores separately box. Now my GNOME bar is broken, I can't hit preferences window again, I can't open quick menu for power or network/bluetooth.
So I am asking, is there any way of changing this via terminal and if is, can you add it to readme?
If this don't belongs here, feel free to delete, I guess this will be OK after disabling hyperthreading and unchecking the box. EDIT: disabling hyperthreading helped, but if someone do this with 32+ cores it could be problem.
The text was updated successfully, but these errors were encountered: