[Bug]: Code - OSS turns full red after successful extension install with wallbashcode.sh --reset. Problems with Wallbash. #1781
Comments
|
Besides these issues, everything works perfectly fine. |
selselse
changed the title
|
Those color errors might be because you lack some cache. You can use the CLI to regenerate the cache My guess is the installation did not finish correctly so you can use the cli to install it. |
|
I have installed it again through Hyde-install. Even after rebuilding the cache and reloading there doesn't seem to be any noticable changes. At least the mouse icon has changed. |
|
|
the fix I recommend above is for this. Did it kill hyprland? |
|
for code-oss, Maybe it is running on Xwayland Also play around with flags when running code-oss. try to run |
--reset flag for wallbashcode is not a thing. |
|
Sadly, wallbash is still broken:
I have already unquoted the argument, but the two launch arguments still keep appearing as files. I have deemed this to be not the issue, as someone mentioned they still have their vscode synced, even though the launch arguments appear to be files.
Also: Applying |
|
Vscode failed to amuse too...: |
|
@selselse As this repo is recommended to be installed on fresh minimimal arch. And everything leaves unexpected results. Can you make another User? and in that user you can do a fresh installation using This might be inconvenient but at least we get to know if this is something to do with your device, Hyprland or HyDE. |
|
Vscode still got that red tint? |
I will once I get back to home again. |
I have tried the usual installation with Hyde-insall on a new user. It seems vscode (not code - oss) still has the same theme, whereas spotify is just a blank window. |
I still have the same issue with wallbash, I am not able to change the wallbash from "theme" to "light" or "dark." So the blank Hyprland seems to not be the issue. At the very least the "--disable-gpu" etc. flags are gone. It is to be deduced that this issue does not concern the .config files. Where else doee wallbash depend on? Does it have its own .config files? |
It is blank like the one in this issue: |
|
Okay let's fix the wallbash for now. Can you run this |
|
I will! Also quick side note: After switching themes now even vscode has that red tint, not only Code- OSS. |
|
do you have errors after running that command? |
|
Sorry for the late response, it seems I am not getting any fatal errors: |
|
Good news, theme applies to LibreOffice correctly! |
|
I have also updated the dotfiles, nothing seems to change... |
|
The warnings indicate that some of the themes are not installed successfully. This is actually a serious issue, as the script cannot genearte correct color scheme. You can reinstall those missing wallpapers using |
|
There is no Hyde theme import. `❯ Hyde theme import |
|
Moreover, the .config files of Cava are also broken. I tried to fix them, but whenever I change themes the broken files are restored again: |
|
Here are the log files for [cache] generating cache files... |
|
Can you update your cli Also please share your version of magick |
|
We should fix the file caching first before tackling about cava, code-oss as those errors are more likely caching issues.
The minimal arch intallation ? |
|
Deleting the broken theme files and updating hyde-cli-git fixed the issue of the command I had to run it again because the theme Sci-fi was being difficult:
|
|
@selselse The log tells me that you got a broken wallpaper. Can you try to use another wallpaper? change |
|
Even changing the wallpaper doesn't fix or differentiate anything. The newly generated .dcol file still lacks the rgb values. I have synced magick with yay but that doesn't seem to change anything either... |
|
|
|
TBH, I needed more time to check the wallbash script as I only knew how this works but not the entire thing. It uses too many arrays that debugging it might be hard. Lol BTW question did you try using the realpath of the wallpaper instead of the symlink ./wall.set? |
|
I tried it with a couple of images 1920x1080 found on my pictures folder. But I am yet to try it with the real path of the wallpaper. (No idea where they are stored either) |
Try to use a clean image. It's not required to be from the repo. |
|
also I did not auto delete some cache so can you run this
This is the command that breaks in yout end |
|
Funnily enough that command seems to work no problem: |
|
Is it possibility for locale to break the bash script? Should I temporarily change it and then run wallbash? |
|
@selselse It should return a value without it, you'll get errors .
Not a good fix, but It happened a while back on the HyDE CLI. Something to do with parsing, but I'm not really convinced BTW I updated the gist can you try it . you can send with "-x" for full debug but I think without -x is enough |
|
❯ wallbash.sh ~/Pictures/Screenshots/240908_19h16m38s_screenshot.png |
|
I doubt it. as there is more error earlier Just for benefit of the doubt, can you add this to that function . If it did not receive a correct value, it would tell us. |
|
Error started here
Mine It failed on this part It should return this |
|
If it returns nothing, let's try to generate a mock value, then check if the script will work. |
|
Hello,I get your point. The function at hand returns no value, how should I generate a mock value? Should I just put random colour inputs? |
|
Btw, I have to state that the file path $HOME/.cache/hyde/wall.set.mpc is seen as a sound file instead of an image. Here is the window that pops when I try to run it: |
|
|
|
Yo! It seems magick does its job, but fails to output anything: |
|
I had a file called histogram:info:, the second pic refers to that. |
|
Let's hope we hit the correct problematic line. BTW, the " *.mpc " is use something like a binary that is being read in this script to extract the primary colors If so, maybe the owner of the repo uses " .mpc " and did not know about musepack that is also .mpc which causes conflicts? Lol Let's try to give a mock value and try to see if the script will stop giving errors let me formulate it. |
|
Thank you kindly |
|
@selselse can you test it now? Already updated the script in gist https://gist.github.com/kRHYME7/0ddd01a92a6b7c3ae773deb0fed65ab2 BTW remove first the .mpc file (This is remove by the script at the end but I remove the rm part for debugging. ) |
|
BTW what is your bash version (funny enough maybe there we have different syntax handling )
|
|
Here is my bash version: |
|
wait lemme change the script first you can DM me in discord BTW |
|
I tried running it, here is the result:
|
Cool I replicated the same output
Try the latest revision |
|
You are right, we are debugging in the issue tab. |
Bug Report
Code - OSS ui is unusable and blood red. Spotify theme sync errors.
Steps to Reproduce
Expected Behavior
For Code - OSS and spotify to sync with the theme
Actual Behavior
Neither of them sync, although wallbashspotify.sh --reset and wallbashcode.sh --reset were successful. Spotify changes its color to red and pink but that is always the case regardless of theme I am using.
Screenshots
Additional Information
Also, changing Wallbash from theme or auto to dark or light completely breaks hyprland, with multiple errors in color.conf.
The text was updated successfully, but these errors were encountered: