Bug#888126: [patch] Please enable systemd-sysusers unit
Hello all,
Michael Vogt [2018-02-01 7:39 +0100]:
> just a small update on this. systemd git master has the needed support
> to reproduce the base-passwd passwd and group files now.
Many thanks for driving this! Now that 238 is released and has all the
necessary support, I've done another attempt at this:
https://salsa.debian.org/systemd-team/systemd/merge_requests/4
This generates the files from base-file's {passwd,group}.master.
I tested this on a Debian sid container in LXC - pretty cool to see the
container boot with a completely absent /etc! I diffed the original and
sysusers-generated passwd/group/shadow files and they are sufficiently similar.
>
> https://github.com/systemd/systemd/blob/master/test/TEST-21-SYSUSERS/test-5.input
Nice that there is an upstream test for this now!
> The only remaining problem is that it generates /sbin/nologin which we
> do not have (we use /usr/sbin/nologin).
As sysusers.d now supports specifying a shell, the above just uses the value
from the *.master file, so this isn't a problem.
Martin
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Bug #888126 in systemd marked as pending
Processing control commands: > tag -1 pending Bug #888126 [systemd] [patch] Please enable systemd-sysusers unit Added tag(s) pending. -- 888126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2
Control: tags -1 moreinfo Am 11.03.2018 um 03:34 schrieb johnw: > Package: systemd > Version: 238-2 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > I noticed, my system(xfce4, slim) can not create user.slice / > user session, > > and start-pulseaudio-x11 can not start > (start-pulseaudio-x11 error message: >Connection failure: Connection refused >pa_context_connect() failed: Connection refuse) > and the system become no sound > > systemctl --user status > Failed to read server status: Process org.freedesktop.systemd1 exited > with status 1 > > All work well before systemd =< 237-4 > > Please help, thanks. > Please provide the output of systemctl status journalctl -alb (as root) Have you rebooted after the upgrade? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Starting powertop --auto-tune from systemd
Am 10.03.2018 um 18:55 schrieb Rainer Dorsch: > [Please follow-up to debian-user] > > Hello, > > I run > > /usr/bin/powertop --auto-tune > > to optimize the power consumption of my system. Running it manually works > nicely. When I try to run from systemd, I see no effect :-/ > > I followed > > https://wiki.archlinux.org/index.php/Powertop#Apply_settings > > added > > root@master:~# cat /etc/systemd/system/powertop.service > [Unit] > Description=Powertop tunings > > [Service] > ExecStart=/usr/bin/powertop --auto-tune > RemainAfterExit=true > > [Install] > WantedBy=multi-user.target > root@master:~# > > enabled it for systemd and got > > root@master:~# systemctl status powertop.service > ● powertop.service - Powertop tunings >Loaded: loaded (/etc/systemd/system/powertop.service; enabled; vendor > preset: enabled) >Active: active (exited) (Result: exit-code) since Sat 2018-03-10 18:29:53 > CET; 22min ago > Process: 642 ExecStart=/usr/bin/powertop --auto-tune (code=exited, > status=203/EXEC) > Main PID: 642 (code=exited, status=203/EXEC) systemct tells you there was a problem trying to execute the binary. Possibly because it's the wrong path? $ whereis powertop powertop: /usr/sbin/powertop /usr/share/man/man8/powertop.8.gz (note bin vs sbin) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2
Processing control commands: > tags -1 moreinfo Bug #892585 [systemd] systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2 Added tag(s) moreinfo. -- 892585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!
Am 11.03.2018 um 19:12 schrieb Francesco Poli: > My ~/.bash_logout is attached, but it's nothing special: it should be > identical to the one provided by the bash package in /etc/skel/ Can you comment out / remove the following three lines: if [ "$SHLVL" = 1 ]; then [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q fi and then test again, if you still encounter the problem. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#869995: Still present in stretch versions, patch attached
found #869995 232-25+deb9u1
found #869995 232-25+deb9u2
tags #869995 patch stretch
thanks
Hi,
I have missed that this bug was actually closed for good. I can confirm
that the issue is fixed in sid and buster, but is is still a crippling
bug in stretch.
I can confirm that the two attached patches fix the issue in 232-25.
Please consider adding those patches for one of the next point releases.
Greetings
Marc
--- a/src/network/networkd-address.c
+++ b/src/network/networkd-address.c
@@ -918,5 +918,8 @@ int config_parse_address_flags(const cha
bool address_is_ready(const Address *a) {
assert(a);
-return !(a->flags & (IFA_F_TENTATIVE | IFA_F_DEPRECATED));
+ if (a->family == AF_INET6)
+ return !(a->flags & (IFA_F_TENTATIVE));
+ else
+ return !(a->flags & (IFA_F_TENTATIVE | IFA_F_DEPRECATED));
}
--- a/src/network/networkd-ndisc.c
+++ b/src/network/networkd-ndisc.c
@@ -165,6 +165,10 @@ static void ndisc_router_process_autonom
return;
}
+/* The preferred lifetime is never greater than the valid lifetime */
+if (lifetime_preferred > lifetime_valid)
+return;
+
r = address_new();
if (r < 0) {
log_link_error_errno(link, r, "Could not allocate address:
%m");
--- a/src/network/networkd-link.c
+++ b/src/network/networkd-link.c
@@ -91,6 +91,10 @@ static bool link_ipv4ll_enabled(Link *li
}
static bool link_ipv6ll_enabled(Link *link) {
+_cleanup_free_ char *disable_ipv6 = NULL;
+const char *p = NULL;
+int r;
+
assert(link);
if (!socket_ipv6_is_supported())
@@ -101,6 +105,12 @@ static bool link_ipv6ll_enabled(Link *li
if (!link->network)
return false;
+p = strjoina("/proc/sys/net/ipv6/conf/", link->ifname,
"/disable_ipv6");
+r = read_one_line_file(p, _ipv6);
+if (r >= 0) {
+if (streq(disable_ipv6, "1"))
+return false;
+}
return link->network->link_local & ADDRESS_FAMILY_IPV6;
}
@@ -1636,6 +1646,9 @@ static int link_up_handler(sd_netlink *r
brought up later */
log_link_warning_errno(link, r, "Could not bring up interface:
%m");
+printf("link_up_handler= %s\n", link->ifname);
+link_check_ready(link);
+
return 1;
}
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed (with 1 error): Still present in stretch versions, patch attached
Processing commands for cont...@bugs.debian.org:
> unarchive #869995
> found #869995 232-25+deb9u1
Bug #869995 {Done: Michael Biebl } [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Ignoring request to alter found versions of bug #869995 to the same values
previously set
> found #869995 232-25+deb9u2
Bug #869995 {Done: Michael Biebl } [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Ignoring request to alter found versions of bug #869995 to the same values
previously set
> tags #869995 patch stretch
Bug #869995 {Done: Michael Biebl } [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Ignoring request to alter tags of bug #869995 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
869995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#869995: Still present in stretch versions, patch attached
unarchive #869995
found #869995 232-25+deb9u1
found #869995 232-25+deb9u2
tags #869995 patch stretch
thanks
Hi,
I have missed that this bug was actually closed for good. I can confirm
that the issue is fixed in sid and buster, but is is still a crippling
bug in stretch.
I can confirm that the two attached patches fix the issue in 232-25.
Please consider adding those patches for one of the next point releases.
Greetings
Marc
--- a/src/network/networkd-address.c
+++ b/src/network/networkd-address.c
@@ -918,5 +918,8 @@ int config_parse_address_flags(const cha
bool address_is_ready(const Address *a) {
assert(a);
-return !(a->flags & (IFA_F_TENTATIVE | IFA_F_DEPRECATED));
+ if (a->family == AF_INET6)
+ return !(a->flags & (IFA_F_TENTATIVE));
+ else
+ return !(a->flags & (IFA_F_TENTATIVE | IFA_F_DEPRECATED));
}
--- a/src/network/networkd-ndisc.c
+++ b/src/network/networkd-ndisc.c
@@ -165,6 +165,10 @@ static void ndisc_router_process_autonom
return;
}
+/* The preferred lifetime is never greater than the valid lifetime */
+if (lifetime_preferred > lifetime_valid)
+return;
+
r = address_new();
if (r < 0) {
log_link_error_errno(link, r, "Could not allocate address:
%m");
--- a/src/network/networkd-link.c
+++ b/src/network/networkd-link.c
@@ -91,6 +91,10 @@ static bool link_ipv4ll_enabled(Link *li
}
static bool link_ipv6ll_enabled(Link *link) {
+_cleanup_free_ char *disable_ipv6 = NULL;
+const char *p = NULL;
+int r;
+
assert(link);
if (!socket_ipv6_is_supported())
@@ -101,6 +105,12 @@ static bool link_ipv6ll_enabled(Link *li
if (!link->network)
return false;
+p = strjoina("/proc/sys/net/ipv6/conf/", link->ifname,
"/disable_ipv6");
+r = read_one_line_file(p, _ipv6);
+if (r >= 0) {
+if (streq(disable_ipv6, "1"))
+return false;
+}
return link->network->link_local & ADDRESS_FAMILY_IPV6;
}
@@ -1636,6 +1646,9 @@ static int link_up_handler(sd_netlink *r
brought up later */
log_link_warning_errno(link, r, "Could not bring up interface:
%m");
+printf("link_up_handler= %s\n", link->ifname);
+link_check_ready(link);
+
return 1;
}
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#869995: fixed in systemd 235-1
Processing commands for cont...@bugs.debian.org:
> unarchive #869995
Bug #869995 {Done: Michael Biebl } [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Unarchived Bug 869995
> found #869995 232-25+deb9u1
Bug #869995 {Done: Michael Biebl } [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Marked as found in versions systemd/232-25+deb9u1.
> found #869995 232-25+deb9u2
Bug #869995 {Done: Michael Biebl } [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Marked as found in versions systemd/232-25+deb9u2.
> tags #869995 patch stretch
Bug #869995 {Done: Michael Biebl } [systemd] interface stuck
in "configuring" if SLAAC prefix announced with preferred lifetime zero
Added tag(s) stretch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
869995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!
Control: found -1 systemd/237-4 On Wed, 7 Mar 2018 23:55:06 +0100 Michael Biebl wrote: > Am 25.11.2015 um 22:20 schrieb Francesco Poli (wintermute): > > Package: libpam-systemd > > Version: 228-2 > > Severity: normal > > > > Hello, > > I noticed a weird bug that is possibly caused by libpam-systemd. > > > > Steps to reproduce (on a box with systemd as PID 1 process): > > > > 0) login on TTY1 (virtual terminal 1) as a regular user > > > > 1) start an X session with > > > > $ startx > > > > 2) press [Ctrl+Alt+F2], in order to switch to TTY2 > > > > 3) login on TTY2 as the same user > > > > 4) logout by pressing [Ctrl+D] on the empty command prompt > > > > 5) awkwardly the screen goes automatically back to the X session > > (rather than showing a fresh new TTY2 login prompt) > > > > 6) even more awkwardly, any keyboard and mouse input is ignored > > except for [Ctrl+Alt+F1], which however causes the screen to > > go blank and immediately enter sleep mode > > > > 7) the only way out seems to be a poweroff command, issued by > > pressing the power button (which is handled by acpid) > > > > I didn't try to SSH into the box and take a look at the system... > > > > > > I suspect that this bug is caused by libpam-systemd, since starting > > an X session on a box with systemd as PID 1 process, but without > > libpam-systemd installed, causes the same inability to use X input > > devices. > > > > I noticed this bug some days ago with libpam-systemd/227-2: I waited > > for version 228-2 to migrate to testing, before reporting the bug. > > After reproducing the same exact misbehavior with libpam-systemd/228-2, > > I decided that it is time to report it. > > > > Could you please investigate this bug and fix it and/or forward it > > upstream, as appropriate? > > As the original bug reporter, can you still reproduce the issue, and if > so, could you share your ~/.bash_logout file. Hello Michael, thanks for following up on this bug report. I have just reproduced the bug on an up-to-date Debian testing box, with a slight difference. Steps to reproduce are now (on a box with systemd as PID 1 process): 0) login on TTY1 (virtual terminal 1) as a regular user 1) start an X session with $ startx 2) press [Ctrl+Alt+F2], in order to switch to TTY2 3) login on TTY2 as the same user 4) logout by pressing [Ctrl+D] on the empty command prompt 5) awkwardly the screen goes automatically back to the X session (rather than showing a fresh new TTY2 login prompt) 6) even more awkwardly, any keyboard and mouse input is ignored except for [Ctrl+Alt+F1], which however causes the X server to crash 7) the screen shows the TTY1 bash with the latest error messages from the crashed X server and a prompt ready to accept new commands My ~/.bash_logout is attached, but it's nothing special: it should be identical to the one provided by the bash package in /etc/skel/ I am also attaching the Xorg.0.log produced by the crashed X server. I hope this additional information will help to pinpoint the issue... Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE .bash_logout Description: Binary data Xorg.0.log Description: Binary data pgpq7j2Ejvd2H.pgp Description: PGP signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!
Processing control commands: > found -1 systemd/237-4 Bug #806256 [libpam-systemd] libpam-systemd: log out from a TTY and your X input devices get lost! Bug #867745 [libpam-systemd] libpam-systemd: log out from a TTY and your X input devices get lost! Bug #877571 [libpam-systemd] xserver-xorg-core: lockup on exiting another virtual terminal Marked as found in versions systemd/237-4. Marked as found in versions systemd/237-4. Marked as found in versions systemd/237-4. -- 806256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806256 867745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867745 877571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#878162: fixed in systemd 232-25+deb9u2
The fix for this bug broke the IPv6 networking on one of my systems. When the RA does not include any MTU information, this patch causes no IPv6 default route to be added at all, leaving the system without IPv6 connectivity. The journal in this case shows: systemd-networkd[397]: eno1: Failed to get default router MTU from RA: No data available A workaround is to add MTU information to the RA from the router, but I don’t think this should be necessary. -- Rob Leslie r...@mars.org ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#892585: Fwd: Bug#892585: Acknowledgement (systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2)
If I replace (version 238-2) /lib/systemd/systemd-logind to old version(237-4) /lib/systemd/systemd-logind, and ln -s /lib/systemd/libsystemd-shared-238.so /lib/systemd/libsystemd-shared-237.so All the problem gone, everything work again, Please help, thanks. -- Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
