icedman / custom-window-controls

GNU General Public License v3.0
13 stars 0 forks source link

Unable to install on Tumbleweed, GNOME 45 #3

Open RedBearAK opened 11 months ago

RedBearAK commented 11 months ago

@icedman

Getting this error shown in Extension Manager when installing on an openSUSE Tumbleweed system, where they jumped on GNOME 45 about two weeks ago.


Unable to load file from: file:///home/username/.local/share/gnome-shell/extensions/custom-window-controls@icedman.github.com/style.js (Error opening file /home/username/.local/share/gnome-shell/extensions/custom-window-controls@icedman.github.com/style.js: No such file or directory)


(I made "username" generic, but it shows my actual user name on this machine.)

Tried logging out and back in, and removing and attempting the install again. Same issue, the extension won't activate.

The instructions on the README for installing manually are missing the cd custom-window-controls step before running make. I know there's a way to enable the extension without logging out. The current instructions don't cause it to appear in Extension Manager.

RedBearAK commented 11 months ago

@icedman

So it worked with the manual method, after logging out. But then Extension Manager immediately says there is an update. The extension version installed is 3, and the extension version installed from the website was 5, so it will always be telling me that there is an update.

But custom buttons show up, and I used Tweaks to make sure they are on the left. But in GNOME Terminal, the red and yellow buttons show a tooltip that says "Files" and will open a Nautilus window for some reason. That's with the Terminal window maximized. If it's not maximized, the red/yellow buttons seem to do what they are supposed to.

When the window is maximized, the green button does nothing. If not maximized, the green button will maximize.

So at least with this particular app, the buttons only do what they should if the window is not maximized.

The custom buttons don't show up in Firefox, which is normal.

Works as expected in GNOME Text Editor, even when the window is maximized. The GTK4 replacement for Gedit.

Works in the GNOME Settings app window. GNOME Tweaks window. YaST Control Center window.

Not sure what causes that odd behavior in GNOME Terminal. (Maybe because I didn't have the maximize and minimize buttons explicitly enabled in Tweaks? But all three of the custom buttons were appearing at first, even though those were both disabled in Tweaks until now. After disabling them again, only the red button appears.)

After flipping those settings in Tweaks, the odd behavior in GNOME Terminal went away. There will probably be some sort of need to check whether those other buttons are enabled or disabled when installing or enabling the extension, or there may be weird behavior like this.

Problem: The custom controls don't seem to want to return to normal after disabling the extension and restarting app windows.

This is pretty neat when it works. Looks like some basic checks of the user's button settings should help a lot.

matyugovich commented 10 months ago

Had to delete ~/.config/gtk-3.0 and ~/.config/gtk-4.0 to revert

icedman commented 10 months ago

Thank you for your feedback. I've disabled global skinning for now. And skin only gnome/gtk apps. This will still work with most chrome based browsers - if the use GTK for titlebars under settings.

0Raik commented 10 months ago

Same problem as OP when installing from the Gnome extensions page. Using latest Manjaro stable Gnome 45.

drmmwlt commented 10 months ago

same as @0Raik , on manjaro-gnome45 too