summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* hwdb: Also mark lis3lv02d sensors in "HP" laptops as being in the basewip/hadess/lis3lv02d-rule-hpBastien Nocera2019-09-121-0/+1
| | | | | | | | | We matched "*Hewlett-Packard*" laptops but not "*HP*" laptops, which caused a regression for the HP Elite Book 850 G3. Fixes: 4247938ee13e23eae1afcecbe646de5283b7afc2 Closes: #13543
* Merge pull request #13500 from yuwata/udev-fix-static_nodeZbigniew Jędrzejewski-Szmek2019-09-121-1/+4
|\ | | | | udev: add missing flag for OPTIONS=static_node
| * udev: also logs file permissionYu Watanabe2019-09-091-1/+1
| |
| * udev: add missing flag for OPTIONS=static_nodeYu Watanabe2019-09-091-0/+3
| | | | | | | | Fixes RHBZ#1740664.
* | fuzzit: export the API key instead of using `auth`Evgeny Vereshchagin2019-09-121-3/+1
| | | | | | | | "We removed some cahing related code that auth used and caused problems"
* | Merge pull request #13526 from yuwata/network-check-access-mode-of-key-fileYu Watanabe2019-09-125-4/+8
|\ \ | | | | | | network: check access mode of key file
| * | network: do not abort execution when a config file cannot be loadedYu Watanabe2019-09-112-2/+2
| | | | | | | | | | | | Closes #13516.
| * | fileio: update warning messageYu Watanabe2019-09-111-2/+2
| | |
| * | network: also check the permission of key fileYu Watanabe2019-09-112-0/+4
| | |
* | | hwdb: axis override for Dell 9360 touchpadbaybal2019-09-111-0/+7
| | | | | | | | | and possibly other XPS models sharing the touchpad (#13472)
* | | oss-fuzz.sh: stop downloading the skia seed corpusEvgeny Vereshchagin2019-09-111-1/+0
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the fuzz target was integrated, it was added as a stopgap to get fuzz-json up and running. It served its purpose and can safely be removed to prevent tools/oss-fuzz.sh from failing with ``` +wget -O /home/travis/build/systemd/systemd/out/fuzz-json_seed_corpus.zip https://storage.googleapis.com/skia-fuzzer/oss-fuzz/skjson_seed_corpus.zip --2019-09-10 22:40:44-- https://storage.googleapis.com/skia-fuzzer/oss-fuzz/skjson_seed_corpus.zip Resolving storage.googleapis.com (storage.googleapis.com)... 74.125.70.128, 2607:f8b0:4001:c05::80 Connecting to storage.googleapis.com (storage.googleapis.com)|74.125.70.128|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2019-09-10 22:40:44 ERROR 403: Forbidden. ``` Ideally we should put our seed corpus somewhere and download it from there but I haven't got round to it.
* | Merge pull request #13511 from ssahani/networkctl-dhcpYu Watanabe2019-09-103-0/+20
|\ \ | |/ |/| networkctl Improve display of address . Show it's dhcp
| * networkctl: Display address is a DHCP4 addressSusant Sahani2019-09-091-0/+12
| | | | | | | | CLoses https://github.com/systemd/systemd/issues/10839
| * sd-network: add support to get DHCP4 addressSusant Sahani2019-09-092-0/+8
|/
* travis: skip the right stageEvgeny Vereshchagin2019-09-071-1/+1
| | | | | It's just a follow-up to https://github.com/systemd/systemd/pull/13493. The stage is called "Fuzzit-Regression" now.
* travis: switch to the latest version of the fuzzit CLIEvgeny Vereshchagin2019-09-072-9/+9
| | | | | | | I was informed that fuzzit-1.1 is going to be deprecated soon. Generally the latest version isn't recommened because it's still in beta and theoretically might be backwards incompatible but let's try rolling forward to avoid PRs like this going forward. We can always roll it back :-)
* udev: Add id program and rule for FIDO security tokensFabian Henneke2019-09-0715-0/+333
| | | | | | | | | | | | | | Add a fido_id program meant to be run for devices in the hidraw subsystem via an IMPORT directive. The program parses the HID report descriptor and assigns the ID_SECURITY_TOKEN environment variable if a declared usage matches the FIDO_CTAPHID_USAGE declared in the FIDO CTAP specification. This replaces the previous approach of whitelisting all known security token models manually. This commit is accompanied by a test suite and a fuzzer target for the descriptor parsing routine. Fixes: #11996.
* pstore: fix use after freeMichael Olbrich2019-09-071-1/+1
| | | | The memory is still needed in the sd_journal_sendv() after the 'if' block.
* semaphore: switch to another keyserverEvgeny Vereshchagin2019-09-061-1/+1
| | | | | | | | | | | | lxc-create has been failing to download the image today with ``` + sudo lxc-create -n buster-amd64 -t download -- -d debian -r buster -a amd64 Setting up the GPG keyring ERROR: Unable to fetch GPG key from keyserver lxc-create: buster-amd64: lxccontainer.c: create_run_template: 1617 Failed to create container from template lxc-create: buster-amd64: tools/lxc_create.c: main: 327 Failed to create container buster-amd64 ``` Let's try another keyserver.
* journal: Make the output of --update-catalog deterministicDaniel Edgecumbe2019-09-064-30/+30
| | | | | | | | | | | | | The use of an unordered hashmap means that the output of 'journalctl --update-catalog' differs between runs despite there being no changes in the input files. By changing all instances of Hashmap to OrderedHashmap we fix this, and now the catalog is reproducible. Motivation: https://reproducible-builds.org Signed-off-by: Daniel Edgecumbe <git@esotericnonsense.com>
* Merge pull request #13484 from evverx/look-at-repo-slugZbigniew Jędrzejewski-Szmek2019-09-061-1/+5
|\ | | | | travis: protect the systemd organization on Fuzzit from forks
| * 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
| | | |
View Lorry Controller Status