So some genius thought it a good idea to rename tracker3 to tinysparql(at least that’s what my google search turned up, not that I understand any of this) and I tried to update without changing it but it wouldn’t let me so in the end I answered yes and now stuff doesn’t work.
When I say “stuff” it’s just easyeffects for the moment that doesn’t launch anymore, but I expect to find more in time.
If I try to launch it from the console I get:
[vikings@VIKINGSKINGDOM ~]$ easyeffects
(easyeffects:5436): Gtk-WARNING **: 09:31:35.093: Unknown key gtk-modules in /home/vikings/.config/gtk-4.0/settings.ini
WARNING: radv is not a conformant Vulkan implementation, testing use only.
[2024-09-23 09:31:35.505] [MANGOHUD] [error] [overlay_params.cpp:647] Unknown option 'io_stats'
Gdk-Message: 09:31:35.752: Error 71 (Protocol error) dispatching to Wayland display.
[vikings@VIKINGSKINGDOM ~]$
Tried to reinstall it didn’t help, suggestions?
LE2: And to be more clear in case it helps, I just noticed when I put on my headphones, it’s not just that easyeffects won’t launch but at least it’s still working and doing it’s stuff in the background. Nope, the effects that I had applied in it aren’t working anymore, so I’m guessing the apps aren’t working at all anymore, not just not launching.
Thank you.
P.S. If you want the full output of the update I saved it and guess I could try to upload it somewhere, though I don’t think it will tell you anymore more then I already did, but what do I know…
LE: Yeap, add 2 more, pavucontrol and mission-center don’t launch anymore eighter, basically I don’t think anything below/under gtk4 works anymore(but I’m not gonna try everything since I don’t know what some of those are/do)
Unknown key gtk-modules in /home/vikings/.config/gtk-4.0/settings.ini
WARNING: radv is not a conformant Vulkan implementation, testing use only.
Start by opening and looking at it, and comparing it to the error message. Nothing you have done so far matters, you did not start with the error message. Work you way through the errors.
Also share your inxi -Fzxc0 . You are asking for help and literally no one but you has any context for what is going on.
Sorry, that’s because I am a newb and thusly I have no idea what is important to share and what isn’t. Plus I figured(judging by my google seach) that I wasn’t the only one this is happening to, so I hoped people with more experience that are also having issues after the update will let me know what’s what.
Point in fact here’s the contents of that settings.ini file you mentioned. I can open it, and look at it sure, but I don’t see the words radv or vulkan anywhere inside it. At that point, that’s where my ability to understand/debug this ends, sad to say…
I would start by hashing everything out in the config file and see if it works. If it does you know it is one of the items in the file breaking things. Then reintroduce things line by line until you discover the blocking element.
Ummm, that is way beyond me as I didn’t understand half of what you said…
Good news at least is that with a forum search I discovered the eos-shifttime command and reverted back one week and now things work again. Hopefully whatever is wrong will get fixed soon so I can update again to current versions. Specially since after a google search apparently single program(or package, whatever you call it) updates are not recommended it seems on arch linux…
LE: If someone reading this happens to already have a Gitlab account could you pretty please create a new issue here and link them to this thread, hopefully it will help them fix the problem sooner. Thank you.
(cause it won’t let me log in eighter with my github or google accounts without creating an gitlab one first, and I am sick and tired of creating a billion different accounts for something I am probably gonna use just once in my life…)
I think what they are saying is to look at the file mentioned and hash out things 1 at a time (keep a backup/snapshot whilst doing so). I’m way too tired to go through the thread but if you don’t understand still wait and hopefully one of these peoples get back to ya
Oh, now I see, maybe it’s just too early in the morning…
Ok and going back and forth, back and forth with updating and eos-shifttime so I can test this is not gonna cause problems, right?
Remember what I advised in the other thread, if it is doing your head in or too much and not 100% needed sit back and rest and when ready try.
Another thing you could try is maybe setup a virtualmachine and mess around (here any screw ups won’t touch your system and you can experiment with little stress, there is something in the wiki I’m pretty sure that can talk you through setting up a VM)
Yeap, good advice, and VM’s are already on my party list but for the future, cause atm I literally don’t have enough space(and maybe other resources like ram?) to set one up and start learning about them.
And with my recent health issues my money is gonna have to go to that for the next few months. Instead of buying the cpu(the last piece I need) this month like that plan was, now that is gonna have to wait until december best case scenario or maybe even early next year…
LE: So given that, again I ask, do I keep messing with updates and shiftime, or would it be better/wiser to wait for someone else to figure this out?
I totally get this, have been having a few issues myself with stuff
I would honestly wait. In the meantime back your important files up externally and that way if something does screw up you can easlily revert. I only back up my projects as themes etc can screw up (rarely) things.
(PS bit out of it but will try clarify things if I can)
Ok, well today I tried to update again see if anything was fixed and nope, gtk4 apps such as easyeffects and mission center still don’t work after the update.
So I did what @nadb suggested and hashed out every line in that settings.ini file one by one untill the entired thing was full of #'s and the apps still didn’t work. Then I figured maybe I have to hash out a line then restart so the changes get applied, try to see if stuff works, hash out another line, restart again, etc.
But that doesn’t work because after I restart the changes I made to the document dissapear…
So any suggestions what else I should try before I’m forced to eos-timeshift back again?
Install a wm like i3 or openbox so when the major DEs have bugs you still have somewhere to acess things, these break a lot less and have never interferd with my plasma install as I only use them as a just in case (plasma/i3) think I’ve used the i3 evriment onve maybe twice inthe last few years and pretty sure one was aciddent
I don’t get it, lool…
