Open BruceWayne-Linux opened 1 month ago
I think this issue is not specific to just Fedora 41 but rather Fedora in general. I came across this issue while i was looking for a fix: https://github.com/avanisubbiah/material-you-theme/issues/71 Could be related.
Have you tried using the python backend in Fedora?
yea, but that totally removes the material you colors and gives the default gnome theme.
Try installing the sass package on Fedora and running the python backend
Also, if you still have issue with python backend, go into
~/.local/share/gnome-shell/extensions/material-you-colors@francescocaracciolo.github.io/adwaita-materialu
, run ./run_integration.sh
and send the output here
Try installing the sass package on Fedora and running the python backend
Okay. Installed sass from npm and also R-sass(from fedora offical repositories). Didn't work. still it's using default gnome theme.
Also, if you still have issue with python backend, go into
~/.local/share/gnome-shell/extensions/material-you-colors@francescocaracciolo.github.io/adwaita-materialu
, run./run_integration.sh
and send the output here
It's giving a error.
Also, while i was turning off and on the extension after logout, this error came. It's not happening always but came 2 or 3 time now. Could this be a cause for the malfunction of the extension? (turned off the python backend here)
Also, if you still have issue with python backend, go into
~/.local/share/gnome-shell/extensions/material-you-colors@francescocaracciolo.github.io/adwaita-materialu
, run./run_integration.sh
and send the output hereIt's giving a error.
For now let's solve this issue. Try running ./local-install.sh in the same folder and then try running that command again
Getting an error.
Collecting rich (from -r requirements.txt (line 1))
Using cached rich-13.9.3-py3-none-any.whl.metadata (18 kB)
Collecting pillow (from -r requirements.txt (line 2))
Using cached pillow-11.0.0-cp313-cp313-manylinux_2_28_x86_64.whl.metadata (9.1 kB)
Collecting pygobject (from -r requirements.txt (line 3))
Using cached pygobject-3.50.0.tar.gz (1.1 MB)
Installing build dependencies ... error
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [75 lines of output]
Collecting meson-python>=0.12.1
Using cached meson_python-0.17.1-py3-none-any.whl.metadata (4.1 kB)
Collecting pycairo>=1.16
Using cached pycairo-1.27.0.tar.gz (661 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Installing backend dependencies: started
Installing backend dependencies: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'error'
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [48 lines of output]
+ meson setup /tmp/pip-install-tw8dj5cn/pycairo_03c0def5edfc40ee9d4235b213c4a82f /tmp/pip-install-tw8dj5cn/pycairo_03c0def5edfc40ee9d4235b213c4a82f/.mesonpy-243nssi0 -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md -Dwheel=true -Dtests=false --native-file=/tmp/pip-install-tw8dj5cn/pycairo_03c0def5edfc40ee9d4235b213c4a82f/.mesonpy-243nssi0/meson-python-native-file.ini
The Meson build system
Version: 1.6.0
Source dir: /tmp/pip-install-tw8dj5cn/pycairo_03c0def5edfc40ee9d4235b213c4a82f
Build dir: /tmp/pip-install-tw8dj5cn/pycairo_03c0def5edfc40ee9d4235b213c4a82f/.mesonpy-243nssi0
Build type: native build
Project name: pycairo
Project version: 1.27.0
C compiler for the host machine: cc (gcc 14.2.1 "cc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)")
C linker for the host machine: cc ld.bfd 2.43.1-2
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program python3 found: YES (/home/peter/.local/share/gnome-shell/extensions/material-you-colors@francescocaracciolo.github.io/adwaita-material-you/venv/bin/python3)
Compiler for C supports arguments -Wall: YES
Compiler for C supports arguments -Warray-bounds: YES
Compiler for C supports arguments -Wcast-align: YES
Compiler for C supports arguments -Wconversion: YES
Compiler for C supports arguments -Wextra: YES
Compiler for C supports arguments -Wformat=2: YES
Compiler for C supports arguments -Wformat-nonliteral: YES
Compiler for C supports arguments -Wformat-security: YES
Compiler for C supports arguments -Wimplicit-function-declaration: YES
Compiler for C supports arguments -Winit-self: YES
Compiler for C supports arguments -Winline: YES
Compiler for C supports arguments -Wmissing-format-attribute: YES
Compiler for C supports arguments -Wmissing-noreturn: YES
Compiler for C supports arguments -Wnested-externs: YES
Compiler for C supports arguments -Wold-style-definition: YES
Compiler for C supports arguments -Wpacked: YES
Compiler for C supports arguments -Wpointer-arith: YES
Compiler for C supports arguments -Wreturn-type: YES
Compiler for C supports arguments -Wshadow: YES
Compiler for C supports arguments -Wsign-compare: YES
Compiler for C supports arguments -Wstrict-aliasing: YES
Compiler for C supports arguments -Wundef: YES
Compiler for C supports arguments -Wunused-but-set-variable: YES
Compiler for C supports arguments -Wswitch-default: YES
Compiler for C supports arguments -Wno-missing-field-initializers: YES
Compiler for C supports arguments -Wno-unused-parameter: YES
Compiler for C supports arguments -fno-strict-aliasing: YES
Compiler for C supports arguments -fvisibility=hidden: YES
Found pkg-config: YES (/usr/bin/pkg-config) 2.3.0
Found CMake: /usr/bin/cmake (3.28.3)
Run-time dependency cairo found: NO (tried pkgconfig and cmake)
../cairo/meson.build:31:12: ERROR: Dependency "cairo" not found, tried pkgconfig and cmake
A full log can be found at /tmp/pip-install-tw8dj5cn/pycairo_03c0def5edfc40ee9d4235b213c4a82f/.mesonpy-243nssi0/meson-logs/meson-log.txt
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: pip install --upgrade pip
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Just ran the things you said in the above comments on arch linux. No errors whatsoever. Python backend seems to be the issue. With it disabled, even on arch, the colors are loading wrongly like on fedora.
Ti fix the python issue above try removing pygoobject from requirements.txt and run it again, maybe il will work
Mmm. Not sure what made it work but i tried installing materialyoucolor manually, since when i ran local-install.sh it kept showing errors. so installed python3-devel package from fedora repository and then it got installed. (Without python3-devel on fedora, materialyoucolor won't install; it gives a g++ error). then removed pygobject from the requirements.txt. It's working now.
Hi. First of all, thanks a lot for reviving this extension. It's really a huge plus for customizing gnome.
I'm on Fedora 41, upgraded from beta to stable yesterday. I came to know about the extension day before yesterday and installed it that day. The colors were not applying properly but if i check with pywal(from terminal) the color schemes are correct, but the extension is not picking it on fedora. Yesterday, I installed the same extension and tried it on arch(endeavouros). It worked flawlessly. Here are some screenshots of the coloring in fedora and arch for the same wallpapers: