Bug#850602: systemd: Suspending the system takes long (>10sec)

Package: systemd Version: 232-8 Severity: normal Dear Maintainer, on my new laptop, suspending the machine takes pretty long (>10sec) compared to what I got sued to on my old machine (<3sec). I am not sure where the cuplrit is. Here's what the journal has to say for these 10 seconds: Jan 08 12

Bug#805498: systemd: Systemd errors in syslog: Failed to set cpu.cfs_{period, quota}_us

Hi, > It's not really a bug in the logging. The log messages seem correct to me. Then I don't understand... how can it be, just because docker needs some cgroups (or whatever) for its operation that have not been enabled, that systemd suddenly tries (and fails) to use those cgroups on completely

Bug#805498: systemd: Systemd errors in syslog: Failed to set cpu.cfs_{period, quota}_us

Hi, > Afaics, docker is using one of CPU* resource control features. This > requires a kernel that supports it. > You can either try to convince the kernel maintainers to enable that > support, compile a kernel on your own, or fix docker, to not make use of > that feature in jessie. I don't think

Bug#805498: systemd: Systemd errors in syslog: Failed to set cpu.cfs_{period, quota}_us

Hi, >> I see the following errors frequently pop up in the syslog: >> >> Nov 18 18:30:21 bridge systemd[1]: Failed to set cpu.cfs_period_us on >> /system.slice/systemd-tmpfiles-clean.service: Permission denied >> Nov 18 18:30:21 bridge systemd[1]: Failed to set cpu.cfs_quota_us on >> /system.sli

Bug#779412: Bug#725284: proper resume hooks

Hi, >> I should add that there already is a bug open against udev for this: >> > > That links to a systemd bug, not a udev bug about async supend/resume, > as I had expected from your messages. Did I misunderstood you? udev is part of sy

Bug#779412: proper resume hooks

>> And in >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780956 >> the dev showed that udev already has proper hooks for resume events. >> >> So these may be proper mechanisms for packages to ship with a >> resume hook. And the last one is already tried and proven by >> laptop-mode-tools. >

Re: [Pkg-xfce-devel] Bug#782456: plymouth: With plymouth installed, starting the DM sometimes fails

Hi, > it doesn't look related to lightdm. At least other daemons seems to fail > to start as well. From the initial report, virtualbox and postfix have > issues as well. I don't think these errors come from postfix or VirtualBox. I rather think that immediately after printing "Apr 12 13:48:56 r-s

Re: Bug#782456: plymouth: With plymouth installed, starting the DM sometimes fails

Hi all, I finally had the time to experiment a bit more. Here are my latest findings: I removed all non-Debian kernels, just to be sure. Immediately after enabling "splash" in grub again, the behavior of "lightdm always fails to start" reappeared. Then I changed plymouth to text mode, re-generate

Bug#772131: systemd: Suspending by closing the lid opens Polkit dialogue after resume

Hi, > postinst has: > > if [ -n "$2" ]; then > systemctl daemon-reexec || true > systemctl try-restart systemd-logind.service || true > systemctl try-restart systemd-networkd.service || true > systemctl try-restart systemd-resolved.service || true > systemctl try-restart syste

Bug#772131: systemd: Suspending by closing the lid opens Polkit dialogue after resume

Hi, >> This behavior only started recently, about the same time as the upgrade to >> systemd 215-7. >> KDE has not seen updates in 2 weeks. That's why I reported this against >> systemd. > > Is this behaviour reproducible after a reboot? Indeed it is not, though I was sure I saw this not just

Bug#771947: systemd: Desktop services not working after systemd upgrade, until a reboot is done: enabling WiFi in NetworkManager, reboot

Package: systemd Version: 215-7 Severity: important Dear Maintainer, after upgrading the systemd package, some things stop working (at least after a suspend-resume cycle): * Clicking the WiFi checkbox in NetworkManager to enable WiFi has no effect (I am using the KDE frontend). I tried "rfkil

Bug#760458: Please add an alternative to 'init' which is satisfiable on stable

Hi, >> see for a bug >> I reported earlier today, suggesting another way to solve the issue at hand. > > If people don't have backports enabled, I don't see how your proposal > would help. I think it's reasonable to expect people mixing

Bug#760458: Please add an alternative to 'init' which is satisfiable on stable

Hi, see for a bug I reported earlier today, suggesting another way to solve the issue at hand. Kind regards Ralf ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.de

Bug#755722: systemd: Warning on each reboot: Superblock last write time is in the future

Hi, > Ralf Jung writes: >> $ sudo hwclock -r ; date >> >> >> Tue 22 Jul 20