Your message dated Sat, 28 Nov 2015 21:57:23 +0100
with message-id <[email protected]>
and subject line Re: Bug#806407: systemd: session limited to 512 tasks after 
upgrade
has caused the Debian Bug report #806407,
regarding systemd: session limited to 512 tasks after upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
806407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806407
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 228-2
Severity: important

After upgrading from systemd 227-2 to 228-2, my session became unusable as it
had more than 512 tasks and all of user.slice, user-1000.slice and
session-cNN.scope had TasksMax=512. Restarting systemd-logind.service _and_
logging off and on did solve the problem, but that's hardly acceptable, is it?

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (980, 'testing'), (980, 'stable'), (500, 'unstable'), (500, 
'stable'), (200, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.3.0-lis64+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser         3.113+nmu3
ii  libacl1         2.2.52-2
ii  libapparmor1    2.10-2+b1
ii  libaudit1       1:2.4.4-4
ii  libblkid1       2.27.1-1
ii  libc6           2.19-22
ii  libcap2         1:2.24-12
ii  libcap2-bin     1:2.24-12
ii  libcryptsetup4  2:1.6.6-5
ii  libgcc1         1:5.2.1-23
ii  libgcrypt20     1.6.4-3
pn  libkmod2        <none>
ii  liblzma5        5.1.1alpha+20120614-2.1
ii  libmount1       2.27.1-1
ii  libpam0g        1.1.8-3.1
ii  libseccomp2     2.2.3-2
ii  libselinux1     2.4-3
ii  libsystemd0     228-2
ii  mount           2.27.1-1
ii  sysv-rc         2.88dsf-59.2
ii  util-linux      2.27.1-1

Versions of packages systemd recommends:
ii  dbus            1.10.4-1
ii  libpam-systemd  228-2

Versions of packages systemd suggests:
ii  systemd-container  228-2
ii  systemd-ui         3-4

Versions of packages systemd is related to:
ii  udev  228-2

-- Configuration Files:
/etc/systemd/logind.conf changed [not included]

-- no debconf information

-- 
Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/

--- End Message ---
--- Begin Message ---
Hello,

as discussed, there really isn't much we can do here, I'm afraid.
Eventually, for a jessie → stretch upgrade you will need to reboot,
but that's already the case for a dist-upgrade.

Thus I'm closing this. Sorry for the bad news!

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to