summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* travis: protect the systemd organization on Fuzzit from forksv243.1Evgeny Vereshchagin2019-09-061-1/+5
| | | | | | | | Now that v243 is out, the script has been pulled by forks that are activated on Travis CI. As a result, all those forks have started to send their fuzzers to Fuzzit inadvertantly consuming our CPUs along the way. Let's prevent this by bailing out early if the script is run outside of the systemd repository.
* hwdb: Mark lis3lv02d sensors in HP laptops as being in the baseHans de Goede2019-09-051-15/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The lis3lv02d sensor used in many HP laptops is (almost) always intented primarily for freefall detection / HDD protection and (almost) always is located in the base of a classic clamshell laptop Before we had the ACCEL_LOCATION udev property the issues this caused with screen-rotation were fixed by applying a mount-matrix which translates base-coordinates to display-coordinates assuming the display is at an angle of exact 90 degrees to the base (swap Y and Z axis). The comment calls this translate "from "can play neverball" to "matches Windows 8 orientation"" but what it really does is translate base accel-axis to display accel-axis. Thus allows rotating the screen if you put the laptop on its side, but no-one normally does that with a 2Kg clamshell laptop. The obviously correct thing to do on classic clamshell laptops (not 2-in-1s) is to disable automatic screen rotation. This commit marks the accelerometer in these laptops as being part of the base, which will make iio-sensor-proxy disable automatic screen rotation. This commit also removes the orientation-matrix since the unmodified coordinates coming from the sensor are oriented correctly for a sensor in the base. Also see the "Bad accelerometer values cause incorrect screen rotation" systemd-devel mail-thread from September 2019.
* po: update Japanese translationYu Watanabe2019-09-051-1/+25
|
* docs: fix push recipe in RELEASE.mdZbigniew Jędrzejewski-Szmek2019-09-051-1/+1
|
* man/systemctl.xml: fix missing "not"Carlo Teubner2019-09-051-1/+1
|
* docs: fix typo in boot loader docnikolas2019-09-051-1/+1
|
* pstore: fix typo in error message - directoy -> directorynikolas2019-09-051-1/+1
|
* Fix typo in comment: overide -> overridenikolas2019-09-051-1/+1
|
* po: update Polish translationPiotr Drąg2019-09-041-2/+27
|
* Update NEWS for v243v243Zbigniew Jędrzejewski-Szmek2019-09-031-2/+12
|
* NEWS: update contributors listZbigniew Jędrzejewski-Szmek2019-09-031-10/+11
|
* Merge pull request #13457 from keszybz/resolved-issueZbigniew Jędrzejewski-Szmek2019-09-037-51/+251
|\
| * resolved: query polkit only after parsing the dataZbigniew Jędrzejewski-Szmek2019-08-271-9/+9
| | | | | | | | That's what we do everywhere else because it leads to nicer user experience.
| * resolved: allow access to Set*Link and Revert methods through polkitZbigniew Jędrzejewski-Szmek2019-08-273-23/+206
| | | | | | | | | | | | | | | | | | This matches what is done in networkd very closely. In fact even the policy descriptions are all identical (with s/network/resolve), except for the last one: resolved has org.freedesktop.resolve1.revert while networkd has org.freedesktop.network1.revert-ntp and org.freedesktop.network1.revert-dns so the description is a bit different.
| * resolved: do not run loop twiceZbigniew Jędrzejewski-Szmek2019-08-271-7/+6
| | | | | | | | | | | | This doesn't matter much, but let's just do the loop once and allocate the populate the result set on the fly. If we find an error, it'll get cleaned up automatically.
| * sd-bus: adjust indentation of commentsZbigniew Jędrzejewski-Szmek2019-08-272-5/+5
| |
| * test-bus-vtable: also print introspection for the fallback vtableZbigniew Jędrzejewski-Szmek2019-08-272-3/+25
| | | | | | | | | | This doesn't really test anything, it's just a trivial test that we get the expected output for a fallback vtable.
| * shared/but-util: drop trusted annotation from ↵Zbigniew Jędrzejewski-Szmek2019-08-271-4/+0
| | | | | | | | | | | | | | | | | | | | | | bus_open_system_watch_bind_with_description() https://bugzilla.redhat.com/show_bug.cgi?id=1746057 This only affects systemd-resolved. bus_open_system_watch_bind_with_description() is also used in timesyncd, but it has no methods, only read-only properties, and in networkd, but it annotates all methods with SD_BUS_VTABLE_UNPRIVILEGED and does polkit checks.
* | Merge pull request #13440 from keszybz/failing-condtion-checkZbigniew Jędrzejewski-Szmek2019-09-031-19/+1
|\ \ | | | | | | Revert "core: check start limit on condition checks too"
| * | Revert "core: check start limit on condition checks too"Zbigniew Jędrzejewski-Szmek2019-08-301-19/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 2de9b9793b91f492141f090dcc89445511e94bd4. This check causes regressions, in particular our own units fail. Apparently, it is enough for the unit to be referenced enough times: $ journalctl -b -u systemd-ask-password-console.path Aug 30 12:08:14 krowka systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Aug 30 12:08:33 krowka systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Aug 30 12:08:33 krowka systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Aug 30 12:08:33 krowka systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Aug 30 12:08:33 krowka systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Aug 30 12:08:33 krowka systemd[1]: systemd-ask-password-console.path: Start request repeated too quickly. Aug 30 12:08:33 krowka systemd[1]: Failed to start Dispatch Password Requests to Console Directory Watch. $ journalctl -b -u systemd-firstboot.service -- Logs begin at Sun 2019-04-21 12:39:21 CEST, end at Fri 2019-08-30 12:23:06 CEST. -- Aug 30 12:08:33 krowka systemd[1]: Condition check resulted in First Boot Wizard being skipped. Aug 30 12:08:33 krowka systemd[1]: Condition check resulted in First Boot Wizard being skipped. Aug 30 12:08:33 krowka systemd[1]: Condition check resulted in First Boot Wizard being skipped. Aug 30 12:08:33 krowka systemd[1]: Condition check resulted in First Boot Wizard being skipped. Aug 30 12:08:33 krowka systemd[1]: systemd-firstboot.service: Start request repeated too quickly. Aug 30 12:08:33 krowka systemd[1]: Failed to start First Boot Wizard. And the same for other units. Fixes #13434. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935829
* | | logind: fix property emission on SessionsYour Name2019-09-032-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We would not send the property because we'd call sd_bus_get_current_message() which would return NULL. If there is no message, we cannot support /self or /auto, but things are still OK if a path with a session name is given. Traceback when the issue is triggered: #2 we'd call sd_bus_get_current_message() here, which would return NULL, and session_object_find() would immediately return 0. #3 0x00000000004289b7 in session_object_find (bus=0x9f1110, path=0xa160b0 "/org/freedesktop/login1/session/c2", interface=0x9efda0 "org.freedesktop.login1.Session", userdata=0x9852f0, found=0x7ffe3e975fe8, error=0x7ffe3e9760b0) at ../src/login/logind-session-dbus.c:620 #4 0x00007ff74bfdde39 in node_vtable_get_userdata (bus=0x9f1110, path=0xa160b0 "/org/freedesktop/login1/session/c2", c=0x9f6d58, userdata=0x7ffe3e976070, error=0x7ffe3e9760b0) at ../src/libsystemd/sd-bus/bus-objects.c:37 #5 0x00007ff74bfe49af in emit_properties_changed_on_interface (bus=0x9f1110, prefix=0xa133a0 "/org/freedesktop/login1/session", path=0xa160b0 "/org/freedesktop/login1/session/c2", interface=0x43f9f8 "org.freedesktop.login1.Session", require_fallback=true, found_interface=0x7ffe3e976163, names=0x7ffe3e9761b0) at ../src/libsystemd/sd-bus/bus-objects.c:2088 #6 0x00007ff74bfe56a4 in sd_bus_emit_properties_changed_strv (bus=0x9f1110, path=0xa160b0 "/org/freedesktop/login1/session/c2", interface=0x43f9f8 "org.freedesktop.login1.Session", names=0x7ffe3e9761b0) at ../src/libsystemd/sd-bus/bus-objects.c:2291 #7 0x00000000004292ea in session_send_changed (s=0xa16e10, properties=0x43ee27 "Active") at ../src/login/logind-session-dbus.c:730 #8 0x0000000000424cd7 in seat_set_active (s=0x9ee280, session=0xa16e10) at ../src/login/logind-seat.c:249 #9 0x00000000004251cf in seat_active_vt_changed (s=0x9ee280, vtnr=3) at ../src/login/logind-seat.c:361 #10 0x000000000042547b in seat_read_active_vt (s=0x9ee280) at ../src/login/logind-seat.c:395 #11 0x000000000040ab5c in manager_dispatch_console (s=0x9f0320, fd=8, revents=8, userdata=0x9852f0) at ../src/login/logind.c:588 #12 0x00007ff74c042d5f in source_dispatch (s=0x9f0320) at ../src/libsystemd/sd-event/sd-event.c:2828 #13 0x00007ff74c04469f in sd_event_dispatch (e=0x9ef340) at ../src/libsystemd/sd-event/sd-event.c:3241 #14 0x00007ff74c044b58 in sd_event_run (e=0x9ef340, timeout=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:3299 #15 0x000000000040d7e8 in manager_run (m=0x9852f0) at ../src/login/logind.c:1186 #16 0x000000000040db58 in run (argc=1, argv=0x7ffe3e976728) at ../src/login/logind.c:1234 #17 0x000000000040dc30 in main (argc=1, argv=0x7ffe3e976728) at ../src/login/logind.c:1244 Fixes #13437. Bug introduced in 3b92c086a8d5338e2164ffa0ae48b3d03d10cfb5.
* | | login: fix use after freeYu Watanabe2019-09-031-2/+2
| | | | | | | | | | | | id is basename(state_file)
* | | hwdb: Add HP Elitebook 850 G3 laptop accelerometer location quirkJan-Michael Brummer2019-09-031-0/+3
| | |
* | | shell-completion: do not truncate suggestionsYu Watanabe2019-09-011-1/+1
| | |
* | | network: adjust log level when DHCPv4 lease lostYu Watanabe2019-08-311-1/+1
| | |
* | | Generate stable machine-id and DHCP client ID on POWER KVM.Dimitri John Ledkov2019-08-313-2/+9
| | |
* | | Merge pull request #13385 from yuwata/core-remove-private-directories-13355Zbigniew Jędrzejewski-Szmek2019-08-318-24/+142
|\ \ \ | | | | | | | | core: also remove private directories by systemctl clean
| * | | core: move timeout_clean_usec from Service to ExecContextYu Watanabe2019-08-287-11/+12
| | | |
| * | | test: add tests for systemctl clean with DynamicUser=yesYu Watanabe2019-08-281-0/+95
| | | |
| * | | core: also remove private directories by systemctl cleanYu Watanabe2019-08-281-0/+11
| | | | | | | | | | | | | | | | Fixes #13355.
| * | | core: introduce exec_directory_is_private() helper functionYu Watanabe2019-08-251-13/+24
| | | | | | | | | | | | | | | | Also, this follows up 40cd2ecc26b776ef085fd0fd29e8e96f6422a0d3.
* | | | man: list possible action string and default valueYu Watanabe2019-08-311-2/+5
| | | | | | | | | | | | | | | | Closes #13442.
* | | | Add HP Elite x2 1013 G3 touchpad as externalRussianNeuroMancer2019-08-301-0/+6
| | | | | | | | | | | | | | | | | | | | HP Elite x2 1013 G3 have external touchpad: http://h10032.www1.hp.com/ctg/Manual/c06077534 (page 12) Marking it as external resolve this issue: https://gitlab.freedesktop.org/libinput/libinput/issues/351
* | | | Merge pull request #13436 from systemd/hidden-units-are-good-unitsYu Watanabe2019-08-304-12/+44
|\ \ \ \ | | | | | | | | | | Hidden units are good units
| * | | | shared/unit-files: only put valid unit paths and dropin dirs in the cacheZbigniew Jędrzejewski-Szmek2019-08-302-1/+22
| | | | |
| * | | | shared/unit-files: we must not filter out names starting with a dotZbigniew Jędrzejewski-Szmek2019-08-301-1/+1
| | | | | | | | | | | | | | | | | | | | Fixes #13380.
| * | | | docs: describe valid unit names in systemd.unit(5)Zbigniew Jędrzejewski-Szmek2019-08-302-10/+21
| | | | |
* | | | | Drop dbus activation stub serviceMichael Biebl2019-08-304-21/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes the following problem: > At the very end of the boot, just after the first user logs in > (usually using sddm / X) I get the following messages in my logs: > Nov 18 07:02:33 samd dbus-daemon[2879]: [session uid=1000 pid=2877] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 > Nov 18 07:02:33 samd dbus-daemon[2879]: [session uid=1000 pid=2877] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 These messages are caused by the "stub" service files that systemd installs. It installed them because early versions of systemd activation required them to exist. Since dbus 1.11.0, a dbus-daemon that is run with --systemd-activation automatically assumes that o.fd.systemd1 is an activatable service. As a result, with a new enough dbus version, /usr/share/dbus-1/services/org.freedesktop.systemd1.service and /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service should become unnecessary, and they can be removed. dbus 1.11.0 was released 2015-12-02. Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914015
* | | | | shared/virt: update link to vmware articleZbigniew Jędrzejewski-Szmek2019-08-301-3/+2
| |_|/ / |/| | | | | | | As suggested in https://github.com/systemd/systemd/pull/13430#issuecomment-526551085.
* | | | environment-d-generator: output logs in debug modeZbigniew Jędrzejewski-Szmek2019-08-302-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Those codepaths is only used by that generator, so simply adding a few debug log lines should be OK. Fixes #12259.
* | | | Merge pull request #13384 from yuwata/core-runtime-directory-preserveZbigniew Jędrzejewski-Szmek2019-08-309-12/+95
|\ \ \ \ | | | | | | | | | | core: make RuntimeDirectoryPreserve= works with non-service units
| * | | | test: add tests for RuntimeDirectoryPreserve=yesYu Watanabe2019-08-223-0/+64
| | | | |
| * | | | core: make RuntimeDirectoryPreserve= works with non-service unitsYu Watanabe2019-08-226-8/+22
| | | | |
| * | | | core: introduce unit_destroy_runtime_directory()Yu Watanabe2019-08-223-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | Currently `unit_will_restart()` can return true only when the unit is service. Hence, should not change anything.
* | | | | Add System76 touchpad toggle supportJeremy Soller2019-08-301-0/+8
| | | | |
* | | | | Merge pull request #13433 from keszybz/new-security-mailing-listZbigniew Jędrzejewski-Szmek2019-08-303-2/+13
|\ \ \ \ \ | | |/ / / | |/| | | docs: new systemd-security mailing list
| * | | | docs: create new SECURITY.md pageZbigniew Jędrzejewski-Szmek2019-08-302-2/+9
| | | | | | | | | | | | | | | | | | | | | | | | | github has special support for that name: https://help.github.com/en/articles/adding-a-security-policy-to-your-repository.
| * | | | docs: new systemd-security mailing listZbigniew Jędrzejewski-Szmek2019-08-302-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the past, we asked people to open a security bug on one of the "big" distros. This worked OK as far as getting bugs reported and notifying some upstream developers went. But we always had trouble getting information to all the appropriate parties, because each time a bug was reported, a big thread was created, with a growing CC list. People who were not CCed early enough were missing some information, etc. To clean this up, we decided to create a private mailing list. The natural place would be freedesktop.org, but unfortunately the request to create a mailing list wasn't handled (https://gitlab.freedesktop.org/freedesktop/freedesktop/issues/134). And even if it was, at this point, if there was ever another administrative issue, it seems likely it could take months to resolve. So instead, we asked for a list to be created on the redhat mailservers. Please consider the previous security issue reporting mechanisms rescinded, and send any senstive bugs to systemd-security@redhat.com.
* | | | | basic/virt: Fix current virtualbox detectionJan Losinski2019-08-301-9/+10
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In a current VirtualBox installation the board_vendor is set to "Oracle Corporation". So we need to add this to the dmi_vendor_table for a relieable detection. This fixes #13429 Signed-off-by: Jan Losinski <losinski@wh2.tu-dresden.de>
* | | | man: install runlevel.8 unconditionallyJan Chren2019-08-291-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | systemctl supports runlevel invocation name without utmp. The runlevel symlink is installed unconditionally. So it's reasonable to install runlevel manpage with it as well. Signed-off-by: Jan Chren (rindeal) <dev.rindeal@gmail.com>
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-18 13:32:40 +0100