IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
(cherry picked from commit d6d06616319ef41ae2f6fcc4812764de2295cd7e)
(cherry picked from commit 4c65c644d6227dadedb317ae500a929e92f365fd)
(cherry picked from commit 1f8ec0ed38405367e8d79f715aad6b0b24775989)
(cherry picked from commit f8d527aa9a9c724199aeafab45714a94eea2caf3)
(cherry picked from commit fca5a45a59a8e4707a92c52bb55c37b2fdd0da7e)
(cherry picked from commit e1a7f29467501ade88abfc17b762fc43c53e6864)
After manually editing /etc/locale.gen, calling localectl set-locale
sometimes fails. When it fails, the systemd journal shows:
systemd-localed: free() / invalid pointer.
It turned out that it only fails if some of the uncommented lines in
/etc/locale.gen have leading spaces, as in:
* C.UTF-8 <= OK
* en_US.UTF-8 <= OK
* fr_FR.UTF-8 <= NOK
After parsing a line from /etc/locale.gen, we use strstrip() to obtain
the "trimmed" line (without leading or trailing spaces).
However, we store the result of strstrip() in the original pointer
containing the untrimmed line. This pointer is later passed to free
(this is done automatically using _cleanup_free_).
This is a problem because if any leading space is present, the pointer
will essentially be shifted from its original value. This will result in
an invalid free upon cleanup.
The same issue is present in the locale_gen_locale_supported function.
Fixed by storing the result of strstrip() in a different pointer.
(cherry picked from commit b24b10592d74b73529817813ff33f7e28e79ca41)
(cherry picked from commit d18037b8ff43a1d7310708a50786f92c1291ce80)
(cherry picked from commit fcd9ec3effc9cad63f73cba024697011c5963766)
When Ubuntu CI is oversaturated, 60s doesn't seem to be enough.
(cherry picked from commit cb58571a1193122a5c20e8f6587115382d281002)
(cherry picked from commit 93ac024b7e568fe65b2e8f55ef13a32880239e95)
(cherry picked from commit 59982fbe8d7e4e8c906e4909f2b1b766f323dd6e)
The documentation suggests that the mount point (i.e. the directory
where the device is mounted) is removed when the device vanishes.
However only stopping of the automount unit is implemented.
So adapt the documentation to reality.
(cherry picked from commit 381ccb424643acd8bf99e5db16ad96b64996e4e9)
(cherry picked from commit 617914112467ea75c7f33c4415e307d26fc1e242)
(cherry picked from commit 56c756b183d14245fc6f0d17b18b37202a0d8429)
The old common default was 4096, until 2020 on which all DNS servers (verified
on BIND9, NSD, Unbound, dnsmasq) switched to 1232 as an agreed max size [1].
[1] https://www.dnsflagday.net/2020/#message-size-considerations
(cherry picked from commit e144a26306dbe07fe37f294301421a938b781247)
(cherry picked from commit b2e1dabbeb020e06ecaecedc05187b60f78669c8)
(cherry picked from commit 9b832c44577f57fdc1fce1f66774c1c33e7f6d4d)
(cherry picked from commit 744b04c5571eb1518e686dce505357aa3fb94ce8)
(cherry picked from commit 16dc17d68c9b56e464fdad258623cebe26b3fcd6)
(cherry picked from commit 6e02302292c2382c412ecdcaa20e9083bf0a9079)
We have some missing coverage in the CI, all builds enable these features,
but there are often changes and they cover a lot of code. Do one build
without them to ensure we don't break builds.
(cherry picked from commit b7b48b389c5e68154f72133ec5d12ca2412aa406)
(cherry picked from commit 64ef6ccd4fc161159720b5e8db0ba54557df313d)
(cherry picked from commit 01ca822462e8ce6a0fc27c3eebcd509ab5ad8641)
(cherry picked from commit bc729e81f2622961ef8428df46bb000197706f70)
(cherry picked from commit 018461aaf0e93d22d0e171e97452d545c8d1d86c)
(cherry picked from commit 483048e42961bc43b011f1156df61acaf8ca6b7f)
I was testing transient units and user@.service crashed. I restarted it, and
tried to create a transient unit. It failed because
/run/user/1000/systemd/transient/ remained after the previous aborted run:
Failed to start transient service unit: Unit run-u0.service was already loaded or has a fragment file.
Remove the directory during initial startup so we don't get confused by our own
files.
(cherry picked from commit 45f540a2974dc732820d20a0e73cfffc94766a70)
(cherry picked from commit 31c7f6d0d18b16fa19a95953938aeed1baee7aff)
(cherry picked from commit 691d173cb21caeaae9b32e558378ff19e9a00e3f)
I was changing how some properties are appended to the StartTransientUnit call
and messed up the message contents. When something is wrong with how the
message is structed, we would return a very generic
"Failed to start transient service unit: No such device or address".
Mention that it was property setting that failed, and translate ENXIO to a
different message. bus_unit_set_properties() or any of the children it calls
may also return other errors, in particular EBADMSG or ENOMEM, but the error
message that is generated for those is understandable, so we don't need to
"translate" them explicitly.
bus_unit_set_properties() is called from two places, so it seems nicer to
generate the message internally, rather than ask the caller to do that. Also,
now bus_unit_set_properties() always sets <error>, which is nicer for the
callers.
(cherry picked from commit 44d82df46e38c5bc36ed3722301eeae15df29763)
(cherry picked from commit 49c6965946b2a0a6504e03ae59160eb7311f123c)
(cherry picked from commit 4f4621893c924ff4f3269c21e06d8cc98d6b7ee2)
(cherry picked from commit 01aa59979bc61125f599a5b8a6c911fff5daaee7)
(cherry picked from commit 649e335bc160c014712afb02a04846a1072b1b32)
(cherry picked from commit 7f961939757d4f9cdfeea8fc4cbe5017a3e0dda7)
tests: add test for strv_env_name_is_valid function listed in env-util.c
(cherry picked from commit 6cc19afac1332d070d203e12c4f5039c5ea8ae8c)
(cherry picked from commit eda7bf237f0305162b59bb1d77df732580b3bdf2)
(cherry picked from commit b7210ffcd331a02dd87cd6cfd663a24b39db146a)
I noticed missing coverage in the reports and turns out this has been
broken since forever (i.e. 2016 - 9f7672b3bc), whoopsie.
(cherry picked from commit 1d6052ba5c9533227bdcc3d3368392726981abaf)
(cherry picked from commit 786649c90459f7374819c2ee10008cb0767afec2)
(cherry picked from commit 0be850bd72ba8efdd40660437bc5343be215236e)
gcov provides wrappers for the exec*() calls but there's none for execveat(),
which means we lose all coverage prior to the call. To mitigate this, let's
add a simple execveat() wrapper in gcov's style[0], which dumps and resets
the coverage data when needed.
This applies only when we're built with -Dfexecve=true.
[0] https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libgcc/libgcov-interface.c;h=b2ee930864183b78c8826255183ca86e15e21ded;hb=HEAD
(cherry picked from commit 4388541237e3cdab6821c1b626bb6314027277b4)
(cherry picked from commit 5e3ac730174a11684c9dab7d50010b0264b4d492)
(cherry picked from commit b0561b51a9023bcfd975cefa6ac68ae2f89a8d60)
(cherry picked from commit ce199d12e9a88286271dec6f22cd2c61f1cd7f54)
(cherry picked from commit 8b1cc644c5c80b85d170cbb7c6745cf75915ad2f)
(cherry picked from commit 75ee851a416caae424b3c3c37f399138f8044d20)
(cherry picked from commit bba6046b241c0e073a6f70ef1f418434c72d3161)
(cherry picked from commit 960f05945c98bf965d8e7642fec2c8c9d8b6d5b7)
(cherry picked from commit 14a5056e5c68a410047cfad443ea223cdea6c82d)
Otherwise, if getopt() and friends are used before parse_argv(), then
the GNU extensions may be ignored.
This should not change any behavior at least now, as we usually use
getopt_long() only once per invocation. But in the next commit,
getopt_long() will be used for other arrays, hence this change will
become necessary.
(cherry picked from commit ef9c12b157a50d63e8a8eb710c013d16c2cea319)
(cherry picked from commit edfca36727c54a3dc1b77a25db436db25a63beee)
(cherry picked from commit 215d16a53534eb9c54cbe585c99e7349b1e1d6a3)
It's a bit nicer if we only write the sysctl core_pattern once the
coredump socket is established, since it's the backend for the handler.
Given the systemd-coredump.socket basically has no dependencies that run
before it this should not really make things slower or so, it just
removes the tiny window where core pattern is in effect that wants to
connect to the backend socket but cannot.
The status quo isn't terrible, and not too different in effect: either
way, until the socket unit is up we won't process coredumps. It's mostly
what kind of behaviour you get then: an error due to /bin/false being
invoked, or an error because systemd-coredump can't connect to its
socket. After this patch we'll exclusively see the former.
(cherry picked from commit 62c72c60b5e6c0712a45b1feccc6cc18151efa9c)
(cherry picked from commit 9943f2af3d46ae730443065aa781bbe04ee524ed)
(cherry picked from commit 9e4507c311ada9c78d2b6407ef40d2a0c70b2bab)
The test log is in the state directory, and we want to keep it around
when a test fails.
Follow-up for: 256a835f1c6c646a55039659aa2db186fbeb5c5d
(cherry picked from commit 49e8342965649503a537beacb77dd0fafc71debe)
(cherry picked from commit dbb1b9c2c8419490b48a3a0aeb69bacbda232043)
(cherry picked from commit 8ae4fd84416ec907eaa6d7cf9258445e0c2a9d5e)
SC2015: Note that A && B || C is not if-then-else. C may run when A is true.
(cherry picked from commit a5979f0bd50234ff9cad47f160d121628e0e3bbe)
(cherry picked from commit 18afac6e9086fd92835b0695ac1981149ef6ed32)
(cherry picked from commit cde5615a444bd52e235dfcbfe1e64f7b1ff7a139)
If people grep the output, it probably shouldn't be ellipsized.
(cherry picked from commit f735076c548abe9878e98c2da044458dd0e684f3)
(cherry picked from commit ff7040b19370d3572c4c84123103234e98e09c1f)
(cherry picked from commit f533407976f49f2afc0696ceb5a6327abdee1105)
Also reduce the scope of variables.
(cherry picked from commit bc1f1eba776434f84f082bf4935b736c94dbb0f1)
(cherry picked from commit 00977a8e74e8fafd0f81356ca1f608766af00047)
(cherry picked from commit a7dee1da0cb50513f6a8488b66e1f18c1a62ac42)
(cherry picked from commit d82267e567698e23e8fd915f057d5d67c912aa09)
(cherry picked from commit 802fded9a577a7284fb90baef0c2305157f0db2c)
(cherry picked from commit 1b05d5132ffd75831b522aa9f29f141699f01795)
(cherry picked from commit ebfb601945b564142d6471fc10aa611c26dbd8b7)
(cherry picked from commit e400a62a92c5aa23094e0ecefcfca9e349168b6e)
(cherry picked from commit 6b4835805b0d0d7fc9d5f2c4f078eb5ae8f6e88e)
(cherry picked from commit 0278b1c80101cc0d857c1becd0c3a51b2eb14a44)
(cherry picked from commit 4067ec52f42a6f81e42e7fc66e92d0ee230b4978)
(cherry picked from commit b91e37e323fa236a1e9e439173112a4a0668235b)
Otherwise, directory with zero access mode cannot be removed.
(cherry picked from commit 808c8b25eece33c503430151641f5f77676af38c)
(cherry picked from commit 201830df218b08bb06e1ecbf43bc5987e77e0235)
(cherry picked from commit ba4ea68e819ba43cac613717d240e4144ac8b933)
No functional change hopefully, just for safety.
(cherry picked from commit da19c07198167946d35be9fdf908bb683da49cfe)
(cherry picked from commit d91f7eb0fb5839d6fc52ec74aca7c3aa44e3b5db)
(cherry picked from commit 9851867e0be8bc3a6ec5b58285e0244dccd93ec8)
(cherry picked from commit cd2cd095db6f26bf9889ef26f1b105843220b803)
(cherry picked from commit 80417f90b03707a873bbff89f246ece3fb9f2c95)
(cherry picked from commit 25a8b163be1558cc837af68baefac3c8f1ba3497)
For future-proof reasons, in case we will add
another option that starts with --deserialize.
Addresses 4f44d2c4f7 (r107285603)
(cherry picked from commit 09567df7db75824f1b8bf0b5cc721febda03cb56)
(cherry picked from commit ed18c2ab79e8b94182d5dcf31d58457763f3e3e1)
(cherry picked from commit f3678358a4ff03e0b9fc9d3c69c1eddead989b2a)
Follow-up for d2ebd50d7f9740dcf30e84efc75610af173967d2
We now modify our cmdline to use '=' for all arguments,
but didn't change early setup check to work with that.
So every daemon-reexec does a full setup, thus breaking
running user sessions.
Fixes#27106
(cherry picked from commit 4f44d2c4f76922a4f48dd4473e6abaca40d7e555)
(cherry picked from commit 4f4e0bab0d66ca6501432854aa3d3fcb53887796)
(cherry picked from commit b1ce97cffbfe688b5d1b082cdb715f0a0d612223)
make a github release for every tag that starts with `v*`,
and a pre-release if the tag contains "-rc".
on the 'systemd/systemd' repo, the "Release" will be draft, so that the
release manager can fill up the notes manually.
on 'systemd/systemd-stable' the release will be created immediately.
info about the action used:
https://github.com/softprops/action-gh-release
(cherry picked from commit 86c20937c29da637878a1282444b057bc1a519fb)
(cherry picked from commit a3f2884ef29dee2ace12afe74b9d8d539237a10a)
(cherry picked from commit eae1851b12b727149362570b3d0e62250c59419b)
We shouldn't report that the file is empty if the stating fails. Let's do the
same as in other places, and just ignore the error and let the subsequent
operation fail.
(cherry picked from commit 7d0c47dad0d4282c3924a654a8fe18fc5d7766f8)
(cherry picked from commit bfc03cae41ae051c9eedcb48f66b3266346719aa)
(cherry picked from commit 48e03955356c5095553ac9c26e4fea83af3814ee)
Unit names can be 255 characters long, not 256.
We first say "name prefix" and then continue with "unit prefix".
Confusing. Couldn't figure out which term is better hence settled on
"unit name prefix".
(cherry picked from commit 75f7e5e54704e643aa9b50ce03ed02a49e75333f)
(cherry picked from commit a2ef3c97bd38d189a4b2cb5c6248f01558c7c9d8)
(cherry picked from commit 34e83c24a7bb3da69676b18dcfe39fb0fbfe6729)
Currently, active journal files are excluded, which means that vacuuming
may not remove anything even if *MaxUse= has been exceeded.
(cherry picked from commit 9ea46af4f2368b41d57705bac09774778126507f)
(cherry picked from commit e4c7553874e86ada52545e26aafb318ca91e9545)
(cherry picked from commit 760059bd6494ef1dbbac2dbd65c82b453efd563e)
(cherry picked from commit 93fe228bb16afdb7c450af26b4d2e5771016a833)
(cherry picked from commit e1ddc48ff934209db70d4de0f3fa6fcf5225b359)
(cherry picked from commit 7eca133c1d60b8823ecb49d1cef9943006a70b80)
(cherry picked from commit 8f572d0d82f2f8bb3995faa569da5af1ef7a427d)
(cherry picked from commit 5d2588b5940b03c72371ec2af84dc79ed5703e85)
(cherry picked from commit 50a9e9a5b00198fef046fac4078ebd3b5ab27d18)
(cherry picked from commit eedd1da9f992f9b9d38e298207428500b745156b)
(cherry picked from commit 1185e7f9d3730c6bf3ab0b537b9e811e12aa8ed0)
(cherry picked from commit a13bd7deb5dcabbf04495e42e1f3062e62e11c93)
It's a sycall group of our own definition, and the output is erroneous
to claim otherwise. Let's hide it.
This adds syscall_set_add() which is nicely symmetric to the existing
syscall_set_remove().
Follow-up for: 6d6a08547c03f96dc798cda1ef4a8d3013d292d5
(cherry picked from commit 950c0ed38935198a67a57c645e499555eaf006eb)
(cherry picked from commit 7822ae021b795f55f84499d00763e112229ac6b4)
(cherry picked from commit f76e47b81030d19e09b07669b5a5590eb59d7957)
These three new syscalls are mostly just new flavours or extensions of
existing syscalls, hence add them to the same groups.
(cherry picked from commit 76e86b8dd8cca9f9fee120289945b29e1dbbe215)
(cherry picked from commit 54f97c0ae5ca3e8560fabcfacc1687715e64477e)
(cherry picked from commit 4b0ae9d4183daa448086bdaca0044e841300fae1)
My user manager says:
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.gnome.Terminal.desktop:256: Unknown key name 'Actions' in section 'Desktop Entry', ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.gnome.Terminal.desktop:258: Unknown section 'Desktop Action new-window'. Ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.gnome.Terminal.desktop:343: Unknown section 'Desktop Action preferences'. Ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.telegram.desktop.desktop:12: Unknown key name 'Actions' in section 'Desktop Entry', ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.telegram.desktop.desktop:13: Unknown key name 'SingleMainWindow' in section 'Desktop Entry', ignoring.
systemd-xdg-autostart-generator[2933]: /home/zbyszek/.config/autostart/org.telegram.desktop.desktop:19: Unknown section 'Desktop Action Quit'. Ignoring.
This is not useful. Those are externally-provided files, and they are likely to
have entries which we know nothing about.
(cherry picked from commit b5a70eeecdb593f8498c0bc163d5a12297cfb55d)
(cherry picked from commit 90ba721560b67e329fff4f2c4e59f5c578d8f440)
(cherry picked from commit c71bd9c5359ba40c136494586b548831f0a69f74)
Whenever we're going to close all file descriptors, we tend to close
the log and set it into open when needed mode. When this is done with
the logging target set to LOG_TARGET_AUTO, we run into issues because
for every logging call, we'll check if stderr is connected to the
journal to determine where to send the logging message. This check
obviously stops working when we close stderr, so we settle the log
target before we do that so that we keep using the same logging
target even after stderr is closed.
(cherry picked from commit a3b00f91bb985fa10bc33db5c7883e33dbdf83d0)
(cherry picked from commit 22c47d24a447112bbf8022a79d9c3940a2f04316)
(cherry picked from commit dc92016bd7d58a0f264323d1150fdc9253888418)
Suppress errors when creating/writing EFI variables during 'bootctl update' if
'--graceful' mode is active (as the documentation indicates).
Closes#26773.
(cherry picked from commit 06d104d58ffa23c958b9b2a2809c61fb25e6f762)
(cherry picked from commit b041337a7a5219398cb304e6cb31456327a7e371)
(cherry picked from commit 769d65988d9d450b358314bc4918865800c8afd7)
`dracut.kernel.7` is just a symlink to `dracut.cmdline.7`, so the web reference
points to a non-existent URL
(https://man7.org/linux/man-pages/man7/dracut.kernel.7.html).
(cherry picked from commit 9baeb58fcdcd3b8893fc485bb33726820ce46e94)
(cherry picked from commit 2a8c1168b11f7144d98fa126bc9a06a2bc92383d)
(cherry picked from commit 357a3f1d2b65b5ed9472e33849e644d790ca928a)
(cherry picked from commit dd23292c080f6e8b972c63b025ad3997972bc9e4)
(cherry picked from commit ad2d77b8994a336643114627e327fc5426f1d335)
(cherry picked from commit 5e5aacd16f96d617526074a15074517efb194be9)
