New version? #170
Comments
|
New versions in systemd 246 compared to elogind 243.7 are (sorted by version) Do you think it is enough to just return |
|
Hey @markhindley and @Salz ! Originally I wanted to upgrade to v245, but then read that there are people sticking to v244 of systemd due to stability reasons. However, I have to plea for some patience. Although elogind is on top of my todo list, it is number 1 in fact, Corona Killed My Spare Time. At least I finally got my new laptop, and it is almost fully operational now. Hopefully I can get through upgrading elogind during the next week. And sorry for the long wait! |
|
Sven Eden dixit:
However, I have to plea for some patience. Although elogind is on top
of my todo list, it is number 1 in fact, [Corona Killed My Spare
Time](https://forums.prydeworx.com/showthread.php?tid=103).
OT, but that page doesn’t show. Screenshot:
# PrydeWorX Forums - Password Required
#[1]Latest Threads (RSS 2.0) [2]Latest Threads (Atom 1.0)
[3]____________________ [4]____________________ [5][X] [6]Login [7]Lost Password? [8]Register
Or login with a social network below
[9]Login with GitHub [10]Login with GitLab
[11]PrydeWorX Forums
* [12]Forum
* [13]Portal
* [14]Members
* [15]Calendar
* [16]Help
* [17]Search
* PrydeWorX Forums
Password Required
The administrator has required it so that a password is required for access to this forum.
Please enter the password below:
[18]______________________________________________
[19]Verify Forum Password
[20]Contact Us | [21]PrydeWorX | [22]Return to Top | [23]Lite (Archive) Mode | [24]RSS Syndication |
[25][(3)__ English (American)______] [26]Go
[27][(1)__Default_____] [28]Go
Designed by [29]Joseahfer. Powered By [30]MyBB, © 2002-2020 [31]MyBB Group.
|
|
Strange... Only banned users aren't allowed to view the forum. @mirabilos : Found it. Whenever I edit a forum, my brwoser thinks the "password" field is something to log into the admin area and writes my password into it. So I must not forget to remove that whenever I edit something, or boards end up fully password protected. 🙄 |
|
Sven Eden dixit:
Strange... Only banned users aren't allowed to view the forum.
I’ve never seen the site before… but it wouldn’t surprise me
if they considered the standard webbrowser lynx “banned” as
many idiots do…
bye,
//mirabilos
--
> Why don't you use JavaScript? I also don't like enabling JavaScript in
Because I use lynx as browser.
+1
-- Octavio Alvarez, me and ⡍⠁⠗⠊⠕ (Mario Lang) on debian-devel
|
|
@mirabilos Thanks for the hatred. Users get banned, not browsers. |
|
Just to add some feedback, elogind master is now at the level of systemd-v245. It compiles fine, but I neither checked Travis nor tested it in action, as we need v246 anyway. |
|
Folks, I am at systemd/systemd Tag v246 now. I have not pushed to elogind/master, yet, because there is plenty of stuff to do until that compiles. The systemd devs have (again) shuffled many functions around, adding new source files and renaming/moving others. |
|
Hey all, the master branch is now at level with systemd-v246 However, this is only the "it compiles" status, there is a lot of testing and cleaning up to do. Someone really bold could try it out, but I wouldn't advise it, as I haven't even run the test suite, which too needs a good look at it. If anybody wants to help, you could do either of the following tasks while I am working on cleaning up the sources:
Here's the plan:
This is a bit more work than in previous releases. But there have been quite some changes under the hood, and I'd like to be careful about those. |
|
A v246-rc1 is almost done. I am mainly battling with travis, it failed on stuff systemd upstream has forgotten. The last issue seem to be some c-ansi errors in testing. |
|
https://travis-ci.org/github/elogind/elogind/branches starts looking good again, so with any luck I'll push out the v246-rc1 pre-release in a few hours. |
|
https://github.com/elogind/elogind/releases/tag/v246.0-rc1 can be tested now! 🥳 |
|
I tried doing a simple revbump: 11c11
< SRC_URI="https://github.com/${PN}/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
---
> SRC_URI="https://github.com/${PN}/${PN}/archive/v246.0-rc1.tar.gz -> ${P}.tar.gz"
51c51
< "${FILESDIR}/${P}-nodocs.patch"
---
> "${FILESDIR}/elogind-246_rc1-nodocs.patch"
53a54,55
>
> S="${WORKDIR}/elogind-246.0-rc1"and it builds fine, but doesn't seem to work. After a reboot |
Try merging with USE="debug". You should then see at least something in /var/log/messages. Edit: But only if you start elogind without daemonizing it. |
|
Sven,
On Tue, Nov 10, 2020 at 10:48:39AM -0800, Sven Eden wrote:
https://github.com/elogind/elogind/releases/tag/v246.0-rc1 can be
tested now! 🥳
Thanks.
I needed the attached patch to fix a mismerge in src/test/test-fs-util.c.
With it the experimental Devuan package builds. Now some testing...
Mark
|
|
On Wed, Nov 11, 2020 at 06:10:09PM +0000, Mark Hindley wrote:
I needed the attached patch to fix a mismerge in src/test/test-fs-util.c.
Github seems to have swallowed the attachment.
Here again, inline.
Mark
From 3de3983cfdca4fbbf34ed9909137e029b64efd3d Mon Sep 17 00:00:00 2001
From: Mark Hindley <mark@hindley.org.uk>
Date: Wed, 11 Nov 2020 17:56:04 +0000
Subject: [PATCH] Fix test-fs-util.c.
There appears to be a mismerge here. The /var/lib/dbus/machine-id/foo path
should be check after /etc/machine-id/foo has failed.
---
src/test/test-fs-util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/test/test-fs-util.c b/src/test/test-fs-util.c
index e0f691c1c..415fad0ee 100644
--- a/src/test/test-fs-util.c
+++ b/src/test/test-fs-util.c
@@ -211,13 +211,13 @@ static void test_chase_symlinks(void) {
assert_se(streq(result, "/test-chase.fsldajfl"));
result = mfree(result);
+ r = chase_symlinks("/etc/machine-id/foo", NULL, 0, &result, NULL);
#if 1 /// elogind supports setups, where the machine-id is in the dbus default path
if (r != -ENOTDIR) {
result = mfree(result);
r = chase_symlinks("/var/lib/dbus/machine-id/foo", NULL, 0, &result, NULL);
}
#endif // 1
- r = chase_symlinks("/etc/machine-id/foo", NULL, 0, &result, NULL);
assert_se(r == -ENOTDIR);
result = mfree(result);
…--
2.20.1
|
|
246.9999 ie git |
|
I will put out rc2 in a few minutes, because: It works now! 😄 Edit: done 😉 |
|
I installed rc2 with portage but |
|
the same |
|
Sounds like the wrong PID is written to the pidfile. I know where and how to fix that.
|
|
Fixed with 7db52c0 Hmmm... I think I'll take a look at what the |
|
Sven,
Pretty good feedback from Devuan/Debian testers for 246.0 rc2. No missing
functionality or regressions so far.
The only comment/query is:
* no longer sends log to the kernel ring buffer (#964006)
However in the log I see
�/etc/elogind/logind.conf:14: Unknown section 'Login'. Ignoring.
�/etc/elogind/logind.conf:38: Unknown section 'Sleep'. Ignoring.
Not sure if it's really ignoring the conf file or what..
What is the significance of that?
Thanks.
Mark
|
|
I am not quite sure yet, but will investigate. Thanks for the feedback! |
Configuration loading has been enhanced to additionally search for configuration files (*.conf) in: * /etc/elogind/logind.conf.d * /run/elogind/logind.conf.d * /usr/local/lib/elogind/logind.conf.d * /usr/lib/elogind/logind.conf.d * /lib/elogind/logind.conf.d (if split-usr is set) Additionally elogind now looks into the following paths for configuration files with [Sleep] configurations: * /etc/elogind/sleep.conf.d * /run/elogind/sleep.conf.d * /usr/local/lib/elogind/sleep.conf.d * /usr/lib/elogind/sleep.conf.d * /lib/elogind/sleep.conf.d (if split-usr is set) Closes: #172 This also fixes the log messages about unknown Sections in Bug: #170 Signed-off-by: Sven Eden <sven.eden@prydeworx.com>
|
@markhindley : The "Unknown section" issue is probably fixed in dd77166 |
Configuration loading has been enhanced to additionally search for configuration files (*.conf) in: * /etc/elogind/logind.conf.d * /run/elogind/logind.conf.d * /usr/local/lib/elogind/logind.conf.d * /usr/lib/elogind/logind.conf.d * /lib/elogind/logind.conf.d (if split-usr is set) Additionally elogind now looks into the following paths for configuration files with [Sleep] configurations: * /etc/elogind/sleep.conf.d * /run/elogind/sleep.conf.d * /usr/local/lib/elogind/sleep.conf.d * /usr/lib/elogind/sleep.conf.d * /lib/elogind/sleep.conf.d (if split-usr is set) Closes: #172 This also fixes the log messages about unknown Sections in Bug: #170 Signed-off-by: Sven Eden <sven.eden@prydeworx.com> (cherry picked from commit dd77166)
|
there are still problems with 246.9999 So, cannot log in Plasma X-Session, downgrading to 243 resolves it. |
|
The same problem with Wayland session. |
|
@perfect7gentleman : I finally found the issue that made rc2 horrible. |
|
seems to work again. |
|
Although I am waiting for answers on the other issues, I will release the new elogind version tomorrow. Whatever pops up then, can be fixed. 😉 |
This is the first release of the new version 246 series. We start with 246.9 to be in sync with upstream systemd tagging. The latest upstream commit this version is synced to is systemd-stable/v246-stable:90f7f6c577 One important note: If you have a localized Linux with translated man pages installed, you have to use `LC_ALL=C` when calling `man` for elogind manuals about `logind.conf` or `loginctl`. Otherwise you will see the translated pages for the systemd versions. Changes and Additions --------------------- * Removed unused source files and headers. * pam_elogind: Do not ask for 'elogind-user-record', nothing sets that up. * suspend/hibernate: Read current config before acting. This way users can change their configurations and have them applied without the need to restart or SIGHUP elogind. * Enable checking for BTRFS before calculating an offset to a swap_file before hibernating. * Makefile: Allow parallel debug and release builds. * cgroup controller detection has been enhanced to be more reliable. * Makefile: Fully wrap meson/ninja to be compatible with JetBrains CLion IDE. * Support config files in .d directories: (#170, #172) Configuration loading has been enhanced to additionally search for configuration files (*.conf) in: * /etc/elogind/logind.conf.d * /run/elogind/logind.conf.d * /usr/local/lib/elogind/logind.conf.d * /usr/lib/elogind/logind.conf.d * /lib/elogind/logind.conf.d (if split-usr is set) Additionally elogind now looks into the following paths for configuration files with [Sleep] configurations: * /etc/elogind/sleep.conf.d * /run/elogind/sleep.conf.d * /usr/local/lib/elogind/sleep.conf.d * /usr/lib/elogind/sleep.conf.d * /lib/elogind/sleep.conf.d (if split-usr is set) Additional to the system shutdown skript directory, elogind will now also look into `/etc/elogind/system-shutdown` for shutdown hook skripts. * Add functionality to try to lay present nvidia cards to sleep when suspending/hibernating (#140) New logind.conf entry: `HandleNvidiaSleep` default: `no` * Actually heed SuspendMode= settings in logind.conf * Prefer syslog over kmsg, elogind is a daemon, not a kernel module. * Make broadcasting of PowerOff/Suspend cancellation optional. (#175) New logind.conf entryies: * `BroadcastPowerOffInterrupts` default: `yes` * `BroadcastSuspendInterrupts` default: `yes` Fixed Bugs ---------- * Fix two potential NULL pointer issues. * Execute wakeup skripts in serial order. (#72) * Fix creation of user runtime directories. * Fix elogind double fork, so logging works as expected. * Make privilege check on suspend/hibernate optional. (#167) * `man logind.conf`: Document sleep modes/states (#180) (You might need to use `LC_ALL=C` to actually see this, as translations installed are for systemd logind.conf.) Signed-off-by: Sven Eden <sven.eden@prydeworx.com>
|
Done. 😉 |
* README: add related projects Closes: https://github.com/nsxiv/nsxiv/issues/169 * fix readme feature section correct animations part (we support webp animation as well) and mention key-handler * remove duplicate Contribution Guideline heading
Sven,
I completely understand that keeping in sync with systemd updates is time consuming. However, Debian bug #968379 appears to be caused by a breakage in the libelogind0/libsystemd0 compatibility with wireshark now using libsystemd0 symbols only present in version 246.
Are you working on a new version of elogind?
Many thanks
Mark
The text was updated successfully, but these errors were encountered: