doc/RELEASE.md: document hwdb update step

Not properties.

docs/RELEASE.md

@@ -9,14 +9,15 @@ layout: default
 1. Add all items to NEWS
 2. Update the contributors list in NEWS (`meson compile -C build git-contrib`)
 3. Update the time and place in NEWS
-4. [RC1] Update version and library numbers in `meson.build`
+4. Update hwb (`meson compile -C build update-hwdb update-hwdb-autosuspend`)
-5. Check dbus docs with `meson compile -C build update-dbus-docs`
+5. [RC1] Update version and library numbers in `meson.build`
-6. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"`
+6. Check dbus docs with `meson compile -C build update-dbus-docs`
-7. Do `meson compile -C build`
+7. Tag the release: `version=vXXX-rcY && git tag -s "${version}" -m "systemd ${version}"`
-8. Make sure that the version string and package string match: `build/systemctl --version`
+8. Do `meson compile -C build`
-9. Upload the documentation: `meson compile -C build doc-sync`
+9. Make sure that the version string and package string match: `build/systemctl --version`
-10. [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
+10. Upload the documentation: `meson compile -C build doc-sync`
-11. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
+11. [FINAL] Close the github milestone and open a new one (https://github.com/systemd/systemd/milestones)
-12. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
+12. "Draft" a new release on github (https://github.com/systemd/systemd/releases/new), mark "This is a pre-release" if appropriate.
-13. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)
+13. Check that announcement to systemd-devel, with a copy&paste from NEWS, was sent. This should happen automatically.
-14. [FINAL] Push commits to stable, create an empty -stable branch: `git push systemd-stable origin/master:master origin/master:refs/heads/${version}-stable`, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).
+14. Update IRC topic (`/msg chanserv TOPIC #systemd Version NNN released`)
+15. [FINAL] Push commits to stable, create an empty -stable branch: `git push systemd-stable origin/master:master origin/master:refs/heads/${version}-stable`, and change the default branch to latest release (https://github.com/systemd/systemd-stable/settings/branches).

hwdb.d/70-mouse.hwdb

@@ -491,7 +491,9 @@ mouse:bluetooth:v046dpb019:name:MX Master 2S Mouse:*
  MOUSE_WHEEL_CLICK_COUNT=24
  MOUSE_WHEEL_CLICK_COUNT_HORIZONTAL=14
 
-# Logitech MX Ergo (via Bluetooth)
+# Logitech MX Ergo
+mouse:usb:v046dp406f:name:Logitech MX Ergo:*
+mouse:usb:v046dpc52b:name:Logitech Unifying Device. Wireless PID:406f:*
 mouse:bluetooth:v046dpb01d:name:MX Ergo Mouse:*
  ID_INPUT_TRACKBALL=1
 

man/sd_bus_add_object.xml

@@ -294,11 +294,12 @@
     returns zero, an error reply is sent back to the caller indicating no matching object for the
     request was found.</para>
 
-    <para>Note that you can return a positive integer from a callback without
+    <para>Note that you can return a positive integer from a <parameter>method</parameter> callback without
     immediately sending a reply. This informs sd-bus this callback will take responsibility for
     replying to the request without forcing the callback to produce a reply immediately. This allows
     a callback to perform any number of asynchronous operations required to construct a reply.
-    However, if producing a reply takes too long, the method call will time out at the caller.</para>
+    However, if producing a reply takes too long, the method call will time out at the caller. This is
+    only available to methods and not properties.</para>
 
     <para>If a callback was invoked to handle a request that expects a reply and the callback
     returns a negative value, the value is interpreted as a negative errno-style error code and sent

src/basic/cgroup-util.c

@@ -2052,8 +2052,14 @@ int cg_unified_cached(bool flush) {
                         unified_cache = CGROUP_UNIFIED_SYSTEMD;
                         unified_systemd_v232 = false;
                 } else {
-                        if (statfs("/sys/fs/cgroup/systemd/", &fs) < 0)
+                        if (statfs("/sys/fs/cgroup/systemd/", &fs) < 0) {
+                                if (errno == ENOENT) {
+                                        /* Some other software may have set up /sys/fs/cgroup in a configuration we do not recognize. */
+                                        log_debug_errno(errno, "Unsupported cgroupsv1 setup detected: name=systemd hierarchy not found.");
+                                        return -ENOMEDIUM;
+                                }
                                 return log_debug_errno(errno, "statfs(\"/sys/fs/cgroup/systemd\" failed: %m");
+                        }
 
                         if (F_TYPE_EQUAL(fs.f_type, CGROUP2_SUPER_MAGIC)) {
                                 log_debug("Found cgroup2 on /sys/fs/cgroup/systemd, unified hierarchy for systemd controller (v232 variant)");