Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#45174 - [cinnamon-desktop] 2.6.4-1 Cinnamon should be set to use systemd

Attached to Project: Community Packages
Opened by dalcde (dalcde) - Tuesday, 02 June 2015, 15:37 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 09 June 2015, 03:39 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alexandre Filgueira (faidoc)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description: In Cinnamon 2.4, systemd vs non-systemd settings were set during compile time as a compilation option. In 2.6, it is now determined in run time via the gsettings options

org.cinnamon.desktop.session session-manager-uses-logind
org.cinnamon.desktop.session settings-daemon-uses-logind
org.cinnamon.desktop.session screensaver-uses-logind

In Arch linux, all three settings should be set to "true", but the default value in upstream is "false".

This should be fixed by either supplying a distro gsetting override file, or running sed 's/false/true/' on schemas/org.cinnamon.desktop.session.gschema.xml.in.in

This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 09 June 2015, 03:39 GMT
Reason for closing:  Fixed
Comment by dalcde (dalcde) - Tuesday, 02 June 2015, 15:39 GMT
Also the --enable-systemd compile options need not be set in other packages as they do nothing.
Comment by dalcde (dalcde) - Wednesday, 03 June 2015, 05:28 GMT
Everyone who have already upgraded Cinnamon should run the commands

gsettings set org.cinnamon.desktop.session session-manager-uses-logind true
gsettings set org.cinnamon.desktop.session settings-daemon-uses-logind true
gsettings set org.cinnamon.desktop.session screensaver-uses-logind true

even if the packaging is fixed, since the user setting is already set during installation and subsequent updates to the schema will only affect newly created users.

EDIT: turns out that is incorrect. The settings will update automatically if you have never fiddled with them. But if you have done something with it (ie. the item is displayed in bold in dconf-editor), you will have to run those commands.

Loading...