You are not logged in.
Here also to confirm that @BaNks workaround did the trick for me.
Thank you @BaNks
Offline
banks script worked for me as well. I am using xinitrc to start cinnamon
Scooty Puff Jr. suuuuuuuuuuuuuuuuuccccckkkkkkkkkksssssssss!!!!!!!!!!
Offline
Don't we have an unstable gnome repo for this very reason? Why is this unstable gnome garbage been moved into a stable repo when it clearly isn't stable? <sigh> I thought that when Arch added the unstable repo for Gnome, this kind of Cinnamon breakage would come to an end. I guess I was wrong. What a shame.
For the record, the script posted did allow cinnamon to start again (GDM is my display manager) but half of my themes no longer work.
Last edited by jaylittle (2015-04-11 20:24:15)
Offline
If I understand things correctly in this case not gnome is unstable. It is cinnamon that was not yet supporting the newest version of gnome.
The problems are fixed in their git repo therefore nothing is wrong here.
There was a gnome update. cinnamon was not ready to work with the new version. They fixed the issue in a couple of days.
We have to use workarounds until the upstream fixes arrive in our repo.
These things happen with a rolling release / bleeding edge distro
I put at button on it. Yes. I wish to press it, but I'm not sure what will happen if I do. (Gune | Titan A.E.)
Offline
I think the new Gnome version sought to remain in the unstable repo until cinnamon is updated to work with it. People who want the new version of Gnome and actually use it can still get it from the unstable repo and the cinnamon users don't have to pay the price. Is there a particular reason why this isn't the policy?
EDIT: To be fair, I'm more than annoyed that cinnamon continues to rely upon any part of Gnome. If it was up to me I wouldn't keep it installed at all. Every new version of Gnome is nothing less than a regression in my eyes.
Last edited by jaylittle (2015-04-11 20:55:14)
Offline
I only noticed this problem after updating to 2.4.8-1. BaNkS workaround works for me. I don't see any issues after applying the temporary fix.
Thank you BaNkS.
Offline
Cinnamon fix with update
cinnamon-session 2.4.3-2 i686/x86_64
muffin 2.4.5-2 i686/x86_6
Offline
Confirm that everything is fixed with the latest update.
No need anymore to enforce the clutter to use x11 with the scripts ...
広島のお好み焼きおたくです
Offline
I think the new Gnome version sought to remain in the unstable repo until cinnamon is updated to work with it. People who want the new version of Gnome and actually use it can still get it from the unstable repo and the cinnamon users don't have to pay the price. Is there a particular reason why this isn't the policy?
EDIT: To be fair, I'm more than annoyed that cinnamon continues to rely upon any part of Gnome. If it was up to me I wouldn't keep it installed at all. Every new version of Gnome is nothing less than a regression in my eyes.
I don't think arch works like that. If something not is keeping up with the latest changes (like the catalyst driver) it is usually removed from the repos. I don't think they usually freeze the software system so X software should be able to be functional. If you want that, use a distro with stable releases, Fedora is a good choice with reasonably updated "stable" releases.
Offline
They don't usually do it, but it has happened. As I recall bluez5 was held back for a very long time because nothing else would've worked with it and pushing it would've effectively broken bluetooth for everybody as a result. In any event, I'm clearly on the wrong side of this issue so I'll concede.
I'm also happy to report that the latest cinnamon revisions seem to take care of the issue and that I no longer have to use the script work-around as a result.
Offline
No problem people. Glad I could help with my little workaround, but all is good now since they pushed new cinnamon-session and muffin updates.
Last edited by BaNkS (2015-04-12 13:37:01)
Offline
Indeed. This is true on my system.
Confirm that everything is fixed with the latest update.
No need anymore to enforce the clutter to use x11 with the scripts ...
Offline