hrdwrrsk / adementary-theme

A theme for GNOME/Budgie/Xfce/Cinnamon desktop with elementary-ish aesthetics.
GNU General Public License v3.0
149 stars 9 forks source link

Assets rendered as red squares. #3

Closed ghost closed 6 years ago

ghost commented 6 years ago

As the title says, assets in this theme are not being rendered correctly, mostly as red squares.

It is strange since I meet the requirements to build it from git.

I use Debian 9.5 with MATE 1.20.x (which uses GTK 3.22), and I also possess the required dependencies mentioned in the building part of the main readme.md file.

Here I attach pics for further details: seleccion_005 menu_006

hrdwrrsk commented 6 years ago

it seems like assets files got locked permission, try to install it in ~/.themes or ~/.local/share/themes folder (without sudo or superuser) !

and it's strange why in my machine/OS installing this theme on /usr/share/themes (system-wide) worked perfectly with no issue anyway :\

Another try is fix permission with chmod or chown, but not tested

ghost commented 6 years ago

It would be useful to see the permissions placed in your usr/share/themes, it is weird to see such permission issue since I checked the install.sh script and it doesn't mess with permissions at all. :confused:

hrdwrrsk commented 6 years ago

In my investigations, this is caused by ALL files are owned by dnsmasq group instead of users, but I'm sure this is maybe unrelated with this issue (in my workspace)

And I switched back again to Ubuntu 18.04 (bionic), seems in F29 beta they messed up file permissions, In Ubuntu/Arch everything is fine :\

offtopic: In Arch Linux w/GNOME 3.30 I can't take screenshot (gnome-shell segfault) because missing dependencies I believe?? in Fedora 29 beta I can take screenshot but Arch w/GNOME 3.30 gnome-shell segfault??

ghost commented 6 years ago

Trying to breakpoint the script suggests that the problem with the permissions is in the cp commands under the .sh installation. Apparently in other distros (Tried it on Mageia & Osuse) this issue happens as well, since the cp command transfers the theme with root ownership, maybe I could try to chown / chmod the themes after the whole script installs the theme just for global usability (?)