You are not logged in.
After today's cinnamon updates
[2024-11-27T06:42:23+0100] [ALPM] upgraded cinnamon-menus (6.2.0-1 -> 6.4.0-1)
[2024-11-27T06:42:23+0100] [ALPM] upgraded cinnamon-desktop (6.2.0-1 -> 6.4.0-1)
[2024-11-27T06:42:23+0100] [ALPM] upgraded cinnamon-control-center (6.2.0-1 -> 6.4.0-1)
[2024-11-27T06:42:23+0100] [ALPM] upgraded xapp (2.8.5-1 -> 2.8.6-1)
[2024-11-27T06:42:23+0100] [ALPM] upgraded cinnamon-screensaver (6.2.1-1 -> 6.4.0-1)
[2024-11-27T06:42:23+0100] [ALPM] upgraded cjs (6.2.0-1 -> 6.4.0-1)
[2024-11-27T06:42:23+0100] [ALPM] upgraded muffin (6.2.0-2 -> 6.4.0-1)
the sound applet no longer works:
error t=2024-11-27T09:52:12Z
[sound@cinnamon.org]: GSettings key maximum-volume not found in schema org.cinnamon.desktop.sound
[sound@cinnamon.org]: Failed to evaluate 'main' function on applet: sound@cinnamon.org/11
error t=2024-11-27T09:52:12Z
[sound@cinnamon.org]: Applet sound@cinnamon.org: Could not create applet object.
[sound@cinnamon.org]: Error importing applet.js from sound@cinnamon.org
Workaround: Downgrade the packages.
Mint thread on github:
https://github.com/linuxmint/cinnamon/issues/12522
Last edited by -thc (2024-11-28 21:20:19)
Offline
Same issue.
For laptops, the power manager applet is also broken.
[jerry@archlinux ~]$ cinnamon-settings power
/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py:458: DeprecationWarning: Gtk.Window.set_wmclass is deprecated
self.window.set_wmclass(wm_class, wm_class)
Loading Power module
Traceback (most recent call last):
File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 811, in <module>
window = MainWindow()
^^^^^^^^^^^^
File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 330, in __init__
if self.load_sidepage_as_standalone():
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 464, in load_sidepage_as_standalone
self.go_to_sidepage(sp_data.sp, user_action=False)
File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 185, in go_to_sidepage
sidePage.build()
File "/usr/share/cinnamon/cinnamon-settings/bin/SettingsWidgets.py", line 212, in build
self.module.on_module_selected()
File "/usr/share/cinnamon/cinnamon-settings/modules/cs_power.py", line 132, in on_module_selected
device_types = [x[UP_TYPE] for x in self.csd_power_proxy.GetDevices()]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/gi/overrides/Gio.py", line 374, in __call__
result = self.dbus_proxy.call_sync(self.method_name, arg_variant,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable (2)
Last edited by Jerry241127 (2024-11-27 13:14:01)
Offline
The Cinnamon update not only Broke the sound control app that sits in the system trey but also if you go to cinnamon settings, the power management application doesn't load and now my monitor is going to sleep every 10 minutes when there is no computer use and this was not the case prior to the update.
It looks like the Cinnamon guys are fixing stuff but my question is, how does incomplete projects aka cinnamon 6.4 even land in the arch repo to start with? that then gets downloaded and breaks things? The Cinnamon guys are saying wait for the fully baked 6.4 but isn't that what should have been there in the first place before people download it?
It would seem to me there shouldn't even be a cinnamon 6.4 release on there unless its complete.
I have been running a bare bones Arch / Cinnamon install since 2023 and this is the first time i have seen a major screw up like this when it comes to updating.
Offline
It would seem to me there shouldn't even be a cinnamon 6.4 release on there unless its complete.
Absolutely! For people wanting to play around with new releases there's the AUR. Software available over the official repos shoud just work - full stop.
Offline
I'm using Arch for 8 years now and have had some problems caused by updates.
But look at the numbers for my system: 8834 updates in 1.5 years (last full install) and 8 such problems (including this one) in 8 years.
(The full update count for 8 years will probably exceed 30,000 updates)
So - from this point of view Arch's performance is actually quite brilliant.
Offline
I'm using Arch for 8 years now and have had some problems caused by updates.
But look at the numbers for my system: 8834 updates in 1.5 years (last full install) and 8 such problems (including this one) in 8 years.
(The full update count for 8 years will probably exceed 30,000 updates)So - from this point of view Arch's performance is actually quite brilliant.
Overall I haven't had many issues with the updates but i keep the base install that was built from the ground up to only have what was needed application wise and that was done to minimize any sort of chance of an updates causing issues aka the less stuff installed the better. Previous to running stock Arch i ran Manjaro for over 4 years and that had way more stuff installed by default and even that only had maybe 3 issues with updates in all those years.
Also, i have been running Windows as well since windows 3.11 up to current day and there wasn't a single time that a system update borked the machine or the software on it so how many updates would that amount to lol?. Now before you comment, I have heard of windows system updates causing issues for some people, it just hasn't happen to me in all these years.
To be honest, this update nonsense is one of the reasons i didn't move to Arch sooner i read about the updates breaking shit all the time and anyone who was an Arch user would always be going on about how an update messed up their install or a program etc. Its good to see over the last few years it has gotten better but it still needs to be even better to the point your not worried if your machine will reboot after you install 200 updates.
I just don't think incomplete Desktop Environments should be sucked down in a update when your not in a Testing channel or the AUR for that matter. A stable channel should be just that, stable..
Offline
I completely agree: in case of Cinnamon single packages updates shouldn't be pushed and made available right away via pacman.
Please, consider putting them to "testing" instead.
TL;DR
I've switched to Cinnamon quite recently, but it's already clear to me that Linux Mint/Cinnamon developers make their whole ecosystem a product, not just a single part of it (git repo/project)!
So if someone updates just a single package from their ecosystem - they won't bother helping fixing dependency issues if the product is not ready. That's basically why the upstream ticket was commented and closed directly:
https://github.com/linuxmint/cinnamon/issues/12522
Now when we have this issue - I don't even know which Arch Linux project should should I report the issue to - cinnamon, cinnamon-desktop or some other?
Last edited by stas-t (2024-11-28 10:33:27)
Offline
With the release of the last 6.4.0 package today (cinnamon) the issue is resolved.
Offline