Bug#892360: Bug #892360 in systemd marked as pending

On Sat, 10 Mar 2018 00:14:40 + aga...@siduction.org wrote: Bug #892360 in systemd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: Confirmed fixed on my two machines. Thanks for

Bug#892360: systemd: No problem on my amd64 systems

On Thu, 08 Mar 2018 20:29:49 +0100 Diederik de Haas wrote: CONFIG_CGROUP_CPUACCT=y As the bug is triggered if this config is not set, no surprise. --eric ___ Pkg-systemd-maintainers mailing list

Bug#892360: systemd: Breaks also all my tested amd64 machines

On 3/8/18 7:26 PM, Eric Valette wrote: On 3/8/18 7:13 PM, Elimar Riesebieter wrote: I do have CONFIG_CGROUP_CPUACCT=y on my amd64 kernels and systemd runs fine... Ok. So still in line with hypothesis... ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's wait and see

Bug#892360: systemd: Breaks also all my tested amd64 machines

On 3/8/18 7:13 PM, Elimar Riesebieter wrote: I do have CONFIG_CGROUP_CPUACCT=y on my amd64 kernels and systemd runs fine... Ok. So still in line with hypothesis... ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's wait and see And I'm rebuilding my failing kernel

Bug#892360: systemd: Breaks also all my tested amd64 machines

On 3/8/18 7:03 PM, Elimar Riesebieter wrote: * Michael Biebl [2018-03-08 18:54 +0100]: [...] Can you check your custom kernel config, specifically if CONFIG_CGROUP_CPUACCT=y I do have CONFIG_CGROUP_CPUACCT=y Well, but why does 237 works with the very same kernel? In my

Bug#892360: systemd: Breaks also all my tested amd64 machines

Can you check your custom kernel config, specifically if CONFIG_CGROUP_CPUACCT=y Probably easiest if you just use grep grep CGROUP /boot/config-$(uname -r) Done in another private email. Can copy here: diff config-4.14.0-3-amd64 config-4.14.23 | grep CGROUP < CONFIG_BLK_CGROUP=y < #

Bug#892360: systemd: Breaks also all my tested amd64 machines

Package: systemd Version: 238-1 Followup-For: Bug #892360 I also get a sigsegv on two diferent machines after today upgrade. You can reboot and use sysvinit mode => bug is realy in systemd. Kernel and packages uptodate -- Package-specific info: -- System Information: Debian Release:

Bug#892360: same here on amd64 system

I also have a system crash at init, witha sigsegv that points in libc. I use unstable today (8 march). --eric ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30/06/2016 21:32, Felipe Sateler wrote: On 30 June 2016 at 15:20, Eric Valette <eric.vale...@free.fr> wrote: On 30/06/2016 21:18, Martin Pitt wrote: Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 Hello Eric, This has never been a supported configuration, and just b

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30/06/2016 21:20, Eric Valette wrote: On 30/06/2016 21:18, Martin Pitt wrote: Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 I martin I have an initrd on this machine so this is something else I was lucky to see at the top of the screen something about shared object

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

On 30/06/2016 21:18, Martin Pitt wrote: Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 Hello Eric, This has never been a supported configuration, and just because it happend to mostly work once it doesn't mean that it can be guaranteed forever, sorry. I have an initrd on this

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

! valette@tri-yann4:~$ ldd /lib/systemd/systemd linux-vdso.so.1 (0x7ffc639f4000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.s

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 01:30 PM, Michael Biebl wrote: Am 16.06.2015 um 13:18 schrieb eric2.vale...@orange.com: On 06/16/2015 11:58 AM, Michael Biebl wrote: My suggestion would be, to fix your setup to either use an initramfs like initramfs-tools or dracut, which mounts your /usr partition, or use no

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 11:58 AM, Michael Biebl wrote: My suggestion would be, to fix your setup to either use an initramfs like initramfs-tools or dracut, which mounts your /usr partition, or use no separate /usr partition at all. There is just to much stuff that is (silently) broken by this. I just

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

Package: systemd Version: 220-6 Severity: critical Justification: breaks the whole system After yesterday upgrade to systemd 220.6, my system no longer boot. It reports a kernel panic witha attempting to kill init. I guess a kind of fault occurs in the daemon but I cannot easilly find traces.

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was working. I rather suspect the /tmp change as I do have this line in my /etc/fstab LABEL=TMP /tmp ext2defaults0 2 -- eric

Bug#788913: Fwd: Re: Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 10:20 AM, VALETTE Eric OLNC/OLPS wrote: On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was working. I rather suspect the /tmp change as I do have this line in my /etc/fstab LABEL=TMP /tmp ext2defaults

Bug#788913: systemd prevents to boot with a kernel panic. Boot in systemv mode is ok

On 06/16/2015 11:40 AM, Michael Biebl wrote: Am 16.06.2015 um 10:42 schrieb eric2.vale...@orange.com: On 06/16/2015 10:17 AM, Michael Biebl wrote: Separate /usr and no initramfs to mount it? yes but 220-5 was

Bug#782077: systemd: /etc/systemd/logind.conf HandleLidSwitchDocked not honred

On 04/07/2015 09:25 PM, Michael Biebl wrote: and it does check for the ev.code == SW_DOCK event: http://cgit.freedesktop.org/systemd/systemd/tree/src/login/logind-button.c#n203 Is is the event you get when docking? I boot with the laptop already

Bug#782077: systemd: /etc/systemd/logind.conf HandleLidSwitchDocked not honred

Package: systemd Version: 219-6 Severity: important Dear Maintainer, When upgrading to the latests version of systemd, I was asked if I wanted to keep my own modified version of /etc/systemd/logind.conf were I had been forced to add HandleLidSwitch=ignore To be eable to work with my laptop

Re: [Pkg-utopia-maintainers] Bug#778970: dbus: Blocks systemd boot frequently

On 22/02/2015 20:34, Michael Biebl wrote: Am 22.02.2015 um 20:30 schrieb Eric Valette: seems close. And yes I have no login. Once I had the graphic start but no kdm... Could try to extract journald from 218 and see if the bug vanishes. Martin identified [1] commit 13790add4bf64

Bug#778970: [Pkg-utopia-maintainers] Bug#778970: Bug#778970: dbus: Blocks systemd boot frequently

On 23/02/2015 01:03, Michael Biebl wrote: Am 23.02.2015 um 00:16 schrieb Eric Valette: Thanks for the tips. I had the same failure in tests, removed the overide for test and got the -3 versions. Will report results. There's a simpler way. Run # export DEB_BUILD_OPTIONS=nocheck do your usual

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

On 02/12/2014 08:55, Didier Roche wrote: This isn't the logs we asked for though to debug your issue. Can you paste them please? (after running as root): systemctl status kdm.service systemctl status display-manager.service Here they are (making them from console :-() -- eric ●

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

On 02/12/2014 09:01, Eric Valette wrote: On 02/12/2014 08:55, Didier Roche wrote: This isn't the logs we asked for though to debug your issue. Can you paste them please? (after running as root): systemctl status kdm.service systemctl status display-manager.service Here they are (making them

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

On 02/12/2014 09:13, Didier Roche wrote: anks! Are you really sure that /etc/X11/default-display-manager exists on this machine (you didn't paste from any other) and points to a kdm binary? Yes. Double checked! cat /etc/X11/default-display-manager /usr/bin/kdm valette@tri-yann4:~$ type /usr

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

On 12/02/2014 09:32 AM, Didier Roche wrote: Ok, everything looks fine. I doubt about the /usr separation to be the cause for that one as the generator doesn't use any file there. Last try before sending you a debug binary: cat -e /etc/X11/default-display-manager (even if I treat trailing

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

--r-- 1 root root 376 déc. 2 18:52 home-valette-local.mount drwxr-xr-x 2 root root 60 déc. 2 18:52 hwclock.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 kdm.service.d drwxr-xr-x 2 root root 200 déc. 2 18:52 local-fs.target.requires drwxr-xr-x 2 root root 60 déc. 2 18:52 local

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

On 03/12/2014 07:41, Didier Roche wrote: However, I've committed a patch with 217-3 which incidentally will fix as well your issue (which is basically don't touch if the default dm != systemd native services. Keep me posted once you download that one which should land shortly in experimental.

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

On 12/01/2014 11:47 AM, intrigeri wrote: Control: tag -1 + moreinfo Hi, Eric Valette wrote (01 Dec 2014 09:11:32 GMT) : After fixing the libapparmor in /usr bug, I managed to boot but kdm was not started. loging as root and using startx lauch a session without problem where I have mouse

Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)

On 12/01/2014 12:58 PM, Martin Pitt wrote: Hello Eric, Eric Valette [2014-12-01 10:11 +0100]: After fixing the libapparmor in /usr bug, I managed to boot but kdm was not started. loging as root and using startx lauch a session without problem where I have mouse. Loggin as a normal user via

Bug#771652: systemd: system 217 breaks config not using initrd and /usr and / different

On 12/01/2014 12:55 PM, Martin Pitt wrote: Hello Eric, Eric Valette [2014-12-01 10:06 +0100]: After upgrading to 217, I had a crash because init was unable to load libapparmor1. After seraching it is located in /usr that in my system is not yet mounted. copying manually libraries to /lib

Re: More info for pulseaudio bug

On 07/02/2014 06:32 PM, Michael Biebl wrote: Am 02.07.2014 17:23, schrieb VALETTE Eric OLNC/OLPS: On 07/02/2014 05:01 PM, Michael Biebl wrote: Never saw a warning and never failed to install anything! I checked the test is there in 208 too

Re: More info for pulseaudio bug

On 07/02/2014 05:01 PM, Michael Biebl wrote: Thanks Eric, keep us posted. We already have a list of required kernel features we check for in udev.preinst [1]. We do have a check for open_by_handle_at(2) (CONFIG_FHANDLE). So I'm surprised this check didn't work for you. Which version of