There’s a couple ways you could go about it. With something like this, it’s okay to downgrade the package, and hold off any updating of your system until a fix is released, which generally speaking may take a day to a few short days to be fixed. This is just a general rule of course. If there’s no fix released after a week or more, then you start to run into partial updates if you exclude the package and decide to start updating your system. Since the package is a dependency of a lot of other useful software, I would suggest to just wait at most a couple of days to see if it gets resolved. I’ll be monitoring any process, so I’ll post back here on any updates if there are any to share.
As for myself, I’m just running the updates to the latest, so currently a few of my applications are broken, but since this is a known issue that affects quite a bit, I’d imagine a fix should be not too far off. Time will tell of course.
@Shjim thanks very much for your report, it’s good to know as well
Just update myself, Inkscape and Gparted now launch again. Gotta love to see upstream devs and Arch get a fixed packaged out in less than 24 hours! Amazing work for sure and happy things are working again
No need to thank me, just doing my job Watson, the devs and maintainers are the real heroes here
@Pudge well you see not many users know how to do it properly, but I don’t mind sharing my knowledge! Now the first thing you do is take your fist and hold it up to you and make sure you clench it real tight and then ever so very carefully and gracefully extend your middle finger straight up high into the sky and poof!! Go update yourself!
I’ve got boxes full of depends…dencies! Always make sure you check your depend***dencies daily, swap them out for new dependencies as needed and you should be better off. Just note, it’s not any more helpful to wear…err I mean use two dependencies at the same time
Just a quick update, as someone pointed out to me on GitLab, the v2.66.3-3 update that does fix this issue in Arch was actually a downstream patch with a revert implemented from the issue, so technically it still hasn’t been solved upstream, even though the revert is working fine on Arch systems. In any case, being up to date should fix the issue regardless for now.
Less than 24hrs, a downstream patch was out, and within less than 48hrs, upstream released a fix for the issue. Not a bad turn around if you ask me! Glad everything is back into working order again
