Processed: Re: Bug#775265: unblock: systemd/215-9
Processing control commands: > tag 775404 patch Bug #775404 [systemd] [systemd] networking.service does not start Bug #775692 [systemd] [systemd] keymap.service does not start Added tag(s) patch. Added tag(s) patch. -- 775265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775265 775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404 775692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775692 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
Processed: Re: Bug#775265: unblock: systemd/215-9
Processing control commands: > tag 775404 patch Bug #775404 [systemd] [systemd] networking.service does not start Bug #775692 [systemd] [systemd] keymap.service does not start Ignoring request to alter tags of bug #775404 to the same tags previously set Ignoring request to alter tags of bug #775692 to the same tags previously set -- 775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404 775692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775692 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#775404: Bug#775265: unblock: systemd/215-9
Control: tag 775404 patch Michael Biebl [2015-01-20 17:56 +0100]: > I looked into this a bit more myself. Unfortunately, those .sh suffixes > are not the only ways to trigger this particular bug. > > As can be seen in [1], this can also be caused by backup/temporary > files, i.e. the name of the sysv init script no longer matches the name > in the Provides: field, and therefor we create a symlink and subsequent > creation of the real unit file fails. It can also happen if a script Provides: the name of another script. I think I caught all these cases now in tests, and proposed a patch upstream: http://lists.freedesktop.org/archives/systemd-devel/2015-January/027249.html It's not exactly "nice", but I can't think of a better/robust solution. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: 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#739676: systemd-user PAM config breaks some libpam-* modules
Hey Christian, Christian Kastner [2014-12-28 21:55 +0100]: > Trying to run as a user instance, but $XDG_RUNTIME_DIR is not set. > > I assume that this is because common-session also includes > pam_systemd.so, whereas -noninteractive does not, so switching to the > latter drops it from systemd-user's config. Right, libpam_systemd is responsible for both starting a logind session for it as well as setting up the per-user runtime dir and env variables like the above. > 2. Re-add pam_systemd.so to systemd-user's config. > > The attached, updated patch implements 2. I tested it locally, and all > issues raised so far were resolved. Thanks for this! On both my Debian sid and my Ubuntu system, the only difference between common-session and common-session-noninteractive is that the latter does not include libpam-systemd. Thus on a system which does *not* use any additional pam module, this should effectively be a no-op change and thus quite safe. Indeed installing libpam-mount only adds itself to common-session, not to common-session-noninteractive. So with this change we would get the desired effect. login, ssh, lightdm etc. all include common-session, so this should be fine. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: 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: tagging 739676
Processing commands for cont...@bugs.debian.org: > tags 739676 + pending Bug #739676 [systemd] systemd-user PAM config breaks some libpam-* modules Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 739676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739676 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#775903: systemd: 'service initscript start' starts initscript.dpkg-dist under systemd
Package: systemd Version: 215-9 Severity: serious Tags: security Dear maintainer, I tried systemd after a wheezy → sid upgrade and encountered an annoying problem: after modifying a file related to my /etc/init.d/fetchmail script[1], I decided to start the fetchmail service with 'service fetchmail start'[2]. To my great surprise, this did not start my /etc/init.d/fetchmail script but /etc/init.d/fetchmail.dpkg-dist, i.e., the script I had explicitely told dpkg to disable when doing the wheezy to sid upgrade. [1] Apparently run with 'set -e' under systemd, but that is another issue. [2] Being new to systemd, I didn't know the systemd idiom for this, but my reading of /usr/sbin/service leads me to think that 'systemctl start fetchmail.service' would have done exactly the same, hence the report to systemd as opposed to sysvinit-utils. Apparently, systemd somehow kept thinking that the fetchmail service corresponded to that .dpkg-dist script until I ran 'systemctl daemon-reload'. This behavior has the adverse effect of running a service the administrator explicitely disabled, or of running it with completely different options from those he configured, etc. This is why I set the security tag on this bug. Maybe the severity should be raised too. Here is a transcript of the commands I ran to trigger and work around the bug: # service fetchmail start # systemctl status -l fetchmail ● fetchmail.dpkg-dist.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail.dpkg-dist) Active: active (exited) since Mon 2015-01-19 10:26:35 CET; 51min ago Jan 19 10:26:35 zita fetchmail.dpkg-dist[3090]: Not starting fetchmail daemon, disabled via /etc/default/fetchmail. Jan 19 10:26:35 zita systemd[1]: Started LSB: init-Script for system wide fetchmail daemon. # find /etc/rc*.d /etc/init.d |grep fetchmail /etc/rc0.d/K01fetchmail /etc/rc1.d/K01fetchmail /etc/rc2.d/S01local-rotate-fetchmail-logfiles /etc/rc2.d/S04fetchmail /etc/rc3.d/S01local-rotate-fetchmail-logfiles /etc/rc3.d/S04fetchmail /etc/rc4.d/S01local-rotate-fetchmail-logfiles /etc/rc4.d/S04fetchmail /etc/rc5.d/S01local-rotate-fetchmail-logfiles /etc/rc5.d/S04fetchmail /etc/rc6.d/K01fetchmail /etc/init.d/fetchmail.dpkg-dist /etc/init.d/fetchmail /etc/init.d/local-rotate-fetchmail-logfiles # mv fetchmail.dpkg-dist /root/tmp # service fetchmail start Warning: Unit file of fetchmail.service changed on disk, 'systemctl daemon-reload' recommended. Job for fetchmail.dpkg-dist.service failed. See 'systemctl status fetchmail.dpkg-dist.service' and 'journalctl -xn' for details. # systemctl status -l fetchmail ● fetchmail.dpkg-dist.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail.dpkg-dist) Active: failed (Result: exit-code) since Mon 2015-01-19 11:25:15 CET; 36s ago Process: 13937 ExecStart=/etc/init.d/fetchmail.dpkg-dist start (code=exited, status=203/EXEC) Jan 19 11:25:15 zita systemd[1]: fetchmail.dpkg-dist.service: control process exited, code=exited status=203 Jan 19 11:25:15 zita systemd[1]: Failed to start LSB: init-Script for system wide fetchmail daemon. Jan 19 11:25:15 zita systemd[1]: Unit fetchmail.dpkg-dist.service entered failed state. Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended. # systemctl daemon-reload # service fetchmail start # systemctl status -l fetchmail ● fetchmail.service - LSB: init script for per-user fetchmail daemons Loaded: loaded (/etc/init.d/fetchmail) Active: active (exited) since Mon 2015-01-19 11:26:28 CET; 6s ago Process: 13983 ExecStart=/etc/init.d/fetchmail start (code=exited, status=0/SUCCESS) Jan 19 11:26:27 zita fetchmail[13983]: Starting mail retrieval agent: fetchmail. Jan 19 11:26:28 zita fetchmail[13983]: Waiting for a Mail Transport Agent lising on the SMTP port...done. Jan 19 11:26:28 zita su[13992]: Successful su for flo by root Jan 19 11:26:28 zita su[13992]: + ??? root:flo Jan 19 11:26:28 zita su[13992]: pam_unix(su:session): session opened for usero by (uid=0) Jan 19 11:26:28 zita fetchmail[13983]: Starting fetchmail for user flo...done Jan 19 11:26:28 zita systemd[1]: Started LSB: init script for per-user fetchm daemons. # Thanks for considering, have a nice day. :-) (the 'Init: sysvinit (via /sbin/init)' bit below is misleading, I am running systemd via the 'init' kernel command line parameter) -- Package-specific info: -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-4.1 i
Processed: tagging 775889
Processing commands for cont...@bugs.debian.org: > tags 775889 + pending Bug #775889 [systemd] breaks init scripts with .sh suffix Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 775889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775889 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#775903: systemd: 'service initscript start' starts initscript.dpkg-dist under systemd
Control: forcemerge 775404 775903 Hey Florent, Florent Rougon [2015-01-21 12:05 +0100]: > I tried systemd after a wheezy → sid upgrade and encountered an annoying > problem: after modifying a file related to my /etc/init.d/fetchmail script[1], > I decided to start the fetchmail service with 'service fetchmail start'[2]. To > my great surprise, this did not start my /etc/init.d/fetchmail script but > /etc/init.d/fetchmail.dpkg-dist, i.e., the script I had explicitely told dpkg > to disable when doing the wheezy to sid upgrade. I'm 99% sure that this is another duplicate of https://bugs.debian.org/775404 I take it you have a /run/systemd/generator.late/fetchmail.service symlink which points to fetchmail.dpkg-dist.service? I'm going to upload 215-10 with the fix for this in a few hours; it would be nice if you could report back with either confirming that it fixes the issue, or is something else (then I'll unduplicate this bug report). Thanks! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.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
Processed: Re: Bug#775903: systemd: 'service initscript start' starts initscript.dpkg-dist under systemd
Processing control commands: > forcemerge 775404 775903 Bug #775404 [systemd] [systemd] networking.service does not start Bug #775692 [systemd] [systemd] keymap.service does not start Bug #775903 [systemd] systemd: 'service initscript start' starts initscript.dpkg-dist under systemd Added tag(s) confirmed and patch. Bug #775404 [systemd] [systemd] networking.service does not start Added tag(s) security. Added tag(s) security. Bug #775692 [systemd] [systemd] keymap.service does not start Merged 775404 775692 775903 -- 775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404 775692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775692 775903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775903 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
Processed: tagging 775404
Processing commands for cont...@bugs.debian.org: > tags 775404 + pending Bug #775404 [systemd] [systemd] networking.service does not start Bug #775692 [systemd] [systemd] keymap.service does not start Bug #775903 [systemd] systemd: 'service initscript start' starts initscript.dpkg-dist under systemd Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404 775692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775692 775903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775903 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
Processed: tagging 775067
Processing commands for cont...@bugs.debian.org: > tags 775067 + pending Bug #775067 [systemd] systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 775067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775067 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
Processed: Re: Bug#774020: systemd: black screen with backlight on start. rescue mode plus Ctrl-D allows normal boot
Processing control commands: > severity -1 important Bug #774020 [systemd] systemd: black screen with backlight on start. rescue mode plus Ctrl-D allows normal boot Severity set to 'important' from 'critical' -- 774020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774020 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#774020: systemd: black screen with backlight on start. rescue mode plus Ctrl-D allows normal boot
Control: severity -1 important This is still unreproducible, has no confirmations from other reporters, does not cause actual damage or data loss, and does not make the package completely unusable for everyone. Thus as per https://www.debian.org/Bugs/Developer#severities I'm downgrading this to important. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.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
Processing of systemd_215-10_amd64.changes
systemd_215-10_amd64.changes uploaded successfully to localhost along with the files: systemd_215-10.dsc systemd_215-10.debian.tar.xz systemd_215-10_amd64.deb systemd-sysv_215-10_amd64.deb libpam-systemd_215-10_amd64.deb libsystemd0_215-10_amd64.deb libsystemd-dev_215-10_amd64.deb libsystemd-login0_215-10_amd64.deb libsystemd-login-dev_215-10_amd64.deb libsystemd-daemon0_215-10_amd64.deb libsystemd-daemon-dev_215-10_amd64.deb libsystemd-journal0_215-10_amd64.deb libsystemd-journal-dev_215-10_amd64.deb libsystemd-id128-0_215-10_amd64.deb libsystemd-id128-dev_215-10_amd64.deb udev_215-10_amd64.deb libudev1_215-10_amd64.deb libudev-dev_215-10_amd64.deb udev-udeb_215-10_amd64.udeb libudev1-udeb_215-10_amd64.udeb libgudev-1.0-0_215-10_amd64.deb gir1.2-gudev-1.0_215-10_amd64.deb libgudev-1.0-dev_215-10_amd64.deb python3-systemd_215-10_amd64.deb systemd-dbg_215-10_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.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
systemd_215-10_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 13:18:05 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 215-10 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility library - development files libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated) libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-journal0 - systemd journal utility library (deprecated) libsystemd-login-dev - systemd login utility library (transitional package) libsystemd-login0 - systemd login utility library (deprecated) libsystemd0 - systemd utility library libudev-dev - libudev development files libudev1 - libudev shared library libudev1-udeb - libudev shared library (udeb) python3-systemd - Python 3 bindings for systemd systemd- system and service manager systemd-dbg - system and service manager (debug symbols) systemd-sysv - system and service manager - SysV links udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 739676 775067 775404 775889 Changes: systemd (215-10) unstable; urgency=medium . [ Martin Pitt ] * sysv-generator: Handle .sh suffixes when translating Provides:. (Closes: #775889) * sysv-generator: Make real units overwrite symlinks generated by Provides: from other units. Fixes failures due to presence of backup or old init.d scripts. (Closes: #775404) * Fix journal forwarding to syslog in containers without CAP_SYS_ADMIN. (Closes: #775067) . [ Christian Kastner ] * Use common-session-noninteractive in systemd-user's PAM config, instead of common-session. The latter can include PAM modules like libpam-mount which expect to be called just once and/or interactively, which already happens for login, ssh, or the display-manager. Add pam_systemd.so explicitly, as it's not included in -noninteractive, but is always required (and idempotent). There is no net change on systemd which don't use manually installed PAM modules. (Closes: #739676) Checksums-Sha1: 9728db7422ab8c5f90211b5f16a505c39acac0c9 4107 systemd_215-10.dsc 7189cb4ae61cb837c6006bb6278875c793b48bae 190964 systemd_215-10.debian.tar.xz 94c5983a77b329d945f0cc7a74fdd449edd39dd6 2534470 systemd_215-10_amd64.deb 7d7fa5176b40c61f66b5821d48e0fe03e621a3a2 31514 systemd-sysv_215-10_amd64.deb 0ce0ccfb6d4bc1332968585026928f0013549ac9 120882 libpam-systemd_215-10_amd64.deb 295ad6d052b8d2ec1b0db9cdc197c7533d87992a 84284 libsystemd0_215-10_amd64.deb b2eac8955b9fde19024f2f08233dea8440a54ad6 90466 libsystemd-dev_215-10_amd64.deb 1bfd5b82c5dc2efc8e8557b1deeb6fe05ab65a6a 44642 libsystemd-login0_215-10_amd64.deb 1399c9d9bd0565f13bc83f0e7d96d6737ea29324 27148 libsystemd-login-dev_215-10_amd64.deb 055260d5f28f1769ff1b73414bfdb74bd5308f3f 33752 libsystemd-daemon0_215-10_amd64.deb 099244fb2e710e5413188ac76a6d6bf3d27f0042 27162 libsystemd-daemon-dev_215-10_amd64.deb 4e941efe7c206338bb5c81471e907e143b0d1564 69840 libsystemd-journal0_215-10_amd64.deb 16fbf48e4e98792e5e388a4be6d399bd3dc51f92 27136 libsystemd-journal-dev_215-10_amd64.deb 8befc7723efb82efcbaca49ec4264ae19e7cbbe7 32728 libsystemd-id128-0_215-10_amd64.deb 4cb34c5e643c8a36e66e1cf5d43aa48ffa2abd16 27124 libsystemd-id128-dev_215-10_amd64.deb 653c238e15d1ea5208b53de19ab70f95bb3f5665 873308 udev_215-10_amd64.deb d85bbcfcdad56a5e2885126572edf88169e02502 51646 libudev1_215-10_amd64.deb 5149d1ba422708b71c893f9210de76327f51c9d4 23112 libudev-dev_215-10_amd64.deb 59e9e11dcf109de56080152f2c566a002717c822 195164 udev-udeb_215-10_amd64.udeb 6af8b6ba9ee1e0bdfc592d2fcf1195efd23378a9 24724 libudev1-udeb_215-10_amd64.udeb 3d49dc576d13f8eddd581dff972fd63e69611742 37476 libgudev-1.0-0_215-10_amd64.deb f4ba7f8f89786dfde93227842b04b63ec827b938 2830 gir1.2-gudev-1.0_215-10_amd64.deb 0bc82dd52d617a1b6d4d669a2f1dc2dbf9f52964 24530 libgudev-1.0-dev_215-10_amd64.deb 9cd92ef7f08f30a25c10c246c32d596923ed4abf 56944 python3-systemd_215-10_amd64.deb 1cb4e4fe2ae1e1ee9f07185f09c4dd7d00d1d
Bug#739676: marked as done (systemd-user PAM config breaks some libpam-* modules)
Your message dated Wed, 21 Jan 2015 13:04:39 + with message-id and subject line Bug#739676: fixed in systemd 215-10 has caused the Debian Bug report #739676, regarding systemd-user PAM config breaks some libpam-* modules 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 ow...@bugs.debian.org immediately.) -- 739676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-mount Version: 2.14-1 Severity: important Dear Maintainer, On a brand-new debian installation, I modified /etc/security/pam_mount.conf.xml to automatically mount a luks-encrypted home partition when I logged in. However, when I tested this out, I found that it worked properly when i logged into the virtual terminal (CTRL ALT F1), but when I logged into xfce using lightdm, it would properly mount my home directory, but failed to unmount it when I logged out. This is a security issue, as it leaves encrypted drives vulnerable. The /var/log/auth log indicates that it still thinks I have an open session when I log out. Here is the relevant section Feb 21 01:48:47 jeremy-laptop lightdm: pam_unix(lightdm:session): session closed for user jeremy Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:706): received order to close things Feb 21 01:48:47 jeremy-laptop lightdm: command: 'pmvarrun' '-u' 'jeremy' '-o' '-1' Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:441): pmvarrun says login count is 1 Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:735): jeremy seems to have other remaining open sessions Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:743): pam_mount execution complete Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:116): Clean global config (0) Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:133): clean system authtok=0x7fda75bba760 (0) Feb 21 01:48:47 jeremy-laptop polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name :1.40, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.utf8) (disconnected from bus) -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam-mount depends on: ii base-files 7.2 ii libc6 2.17-97 ii libcryptsetup4 2:1.6.1-1 ii libhx28 3.18-1 ii libmount1 2.20.1-5.6 ii libpam-runtime 1.1.8-2 ii libpam0g1.1.8-2 ii libpcre31:8.31-2 ii libssl1.0.0 1.0.1f-1 ii libxml2 2.9.1+dfsg1-3 ii mount 2.20.1-5.6 libpam-mount recommends no packages. Versions of packages libpam-mount suggests: pn cifs-utils pn davfs2 ii fuse2.9.2-4 ii lsof4.86+dfsg-1 pn ncpfs ii openssl 1.0.1f-1 ii psmisc 22.20-1 pn sshfs pn tc-utils pn xfsprogs -- Configuration Files: /etc/security/pam_mount.conf.xml changed: -- no debconf information --- End Message --- --- Begin Message --- Source: systemd Source-Version: 215-10 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 739...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 13:18:05 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 215-10 Distribution: unstable Urgency: medium Maintainer: Deb
Bug#775067: marked as done (systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC))
Your message dated Wed, 21 Jan 2015 13:04:39 +
with message-id
and subject line Bug#775067: fixed in systemd 215-10
has caused the Debian Bug report #775067,
regarding systemd: journald doesn't forward messages to syslog w/o
CAP_SYS_ADMIN (LXC)
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 ow...@bugs.debian.org
immediately.)
--
775067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-8
Severity: grave
Tags: upstream patch
Justification: causes non-serious data loss
Dear Maintainer,
when using LXC containers without CAP_SYS_ADMIN, journald fails to
forward any messages to syslog by default. Since the journal is not
persistent by default, no logs are stored at all, hence the
classification as 'data loss'. Also, this is a regression from Wheezy,
where a container without CAP_SYS_ADMIN and syslog did indeed store
persistent logs in /var/log/{syslog,messages,...}.
Note that there is NO other problem with systemd related to missing
CAP_SYS_ADMIN in a container (that I have found so far), provided all
required (pseudo-) file systems are mounted beforehand (which can be
done by configuration with Jessie's LXC version). I do know that
upstream claims that CAP_SYS_ADMIN-less containers are currently not
really supported, but they do intend to work towards that, and, from
what I can tell, apart from this journald problem, I have found no
issue whatsoever with a missing CAP_SYS_ADMIN (it actually works even
better than under sysvinit because it doesn't try to do some stuff
it's not supposed to do in containers that cause error messages with
sysvinit) - and since these kinds of containers were working in
Wheezy with its default init, I think this should be supported in
Jessie, too, especially if the fix is really easy, see below.
This bug is independent of the syslog implementation used, because no
syslog implementation in Jessie supports reading directly from the
journal, as far as I can tell (syslog-ng is too old, rsyslog is built
without imjournal support), so all rely on ForwardToSyslog=yes.
The reason why this problem occurs is that journald tries to fake
SCM_CREDENTIALS before sending a packet to the syslog daemon. With
CAP_SETUID and CAP_SETGID, faking uid/gid is not a problem, but to fake
the pid in struct ucred, one needs CAP_SYS_ADMIN (according to current
kernel source).
Also note that without activating debugging in journald, this problem
can not be diagnosed easily (it took me a while with strace to find the
problem).
Note, however, two things:
- journald does (and can) not guarantee that it can fake the pid,
because the process could have already exited. If you look at the
source, in case ESRCH is returned, it just fakes uid/gid and uses
its own pid
- both rsyslog and syslog-ng (haven't tried anything else yet) don't
rely on SCM_CREDENTIAL's pid anyway in their default configuration,
so at least in the default configuration there's no reason to fail
in that case.
I have created (and tested) an absolutely trivial patch that fixes this
by not only checking for ESRCH but also EPERM and then avoid faking the
pid.
I have tested this with both rsyslog and syslog-ng and it works and
both store (the same ;-)) persistent log messages in
/var/log/{messages,syslog,...}.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-58
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-4
ii libc6 2.19-13
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-4
ii libgcrypt20 1.6.2-4+b1
ii libkmod218-3
ii liblzma55.1.1alpha+20120614-2+b3
ii libpam0g1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-8
ii mount 2.25.2-4
ii sysv-rc 2.88dsf-58
ii udev215-8
ii util-linux 2.25.2-4
Versions of packages systemd recommends:
ii dbus1.8.12-3
ii libpam-systemd 215-8
Versions of packages systemd suggests:
pn systemd-ui
-- no debconf information
Description: Make journald syslog fwd'ing work w/o CAP_SYS_ADMIN
In case CAP_SYS_ADMIN is missing, one cannot fake pid in struct ucred
Bug#775903: marked as done (systemd: 'service initscript start' starts initscript.dpkg-dist under systemd)
Your message dated Wed, 21 Jan 2015 13:04:39 + with message-id and subject line Bug#775404: fixed in systemd 215-10 has caused the Debian Bug report #775404, regarding systemd: 'service initscript start' starts initscript.dpkg-dist under systemd 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 ow...@bugs.debian.org immediately.) -- 775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-9 Severity: serious Tags: security Dear maintainer, I tried systemd after a wheezy → sid upgrade and encountered an annoying problem: after modifying a file related to my /etc/init.d/fetchmail script[1], I decided to start the fetchmail service with 'service fetchmail start'[2]. To my great surprise, this did not start my /etc/init.d/fetchmail script but /etc/init.d/fetchmail.dpkg-dist, i.e., the script I had explicitely told dpkg to disable when doing the wheezy to sid upgrade. [1] Apparently run with 'set -e' under systemd, but that is another issue. [2] Being new to systemd, I didn't know the systemd idiom for this, but my reading of /usr/sbin/service leads me to think that 'systemctl start fetchmail.service' would have done exactly the same, hence the report to systemd as opposed to sysvinit-utils. Apparently, systemd somehow kept thinking that the fetchmail service corresponded to that .dpkg-dist script until I ran 'systemctl daemon-reload'. This behavior has the adverse effect of running a service the administrator explicitely disabled, or of running it with completely different options from those he configured, etc. This is why I set the security tag on this bug. Maybe the severity should be raised too. Here is a transcript of the commands I ran to trigger and work around the bug: # service fetchmail start # systemctl status -l fetchmail ● fetchmail.dpkg-dist.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail.dpkg-dist) Active: active (exited) since Mon 2015-01-19 10:26:35 CET; 51min ago Jan 19 10:26:35 zita fetchmail.dpkg-dist[3090]: Not starting fetchmail daemon, disabled via /etc/default/fetchmail. Jan 19 10:26:35 zita systemd[1]: Started LSB: init-Script for system wide fetchmail daemon. # find /etc/rc*.d /etc/init.d |grep fetchmail /etc/rc0.d/K01fetchmail /etc/rc1.d/K01fetchmail /etc/rc2.d/S01local-rotate-fetchmail-logfiles /etc/rc2.d/S04fetchmail /etc/rc3.d/S01local-rotate-fetchmail-logfiles /etc/rc3.d/S04fetchmail /etc/rc4.d/S01local-rotate-fetchmail-logfiles /etc/rc4.d/S04fetchmail /etc/rc5.d/S01local-rotate-fetchmail-logfiles /etc/rc5.d/S04fetchmail /etc/rc6.d/K01fetchmail /etc/init.d/fetchmail.dpkg-dist /etc/init.d/fetchmail /etc/init.d/local-rotate-fetchmail-logfiles # mv fetchmail.dpkg-dist /root/tmp # service fetchmail start Warning: Unit file of fetchmail.service changed on disk, 'systemctl daemon-reload' recommended. Job for fetchmail.dpkg-dist.service failed. See 'systemctl status fetchmail.dpkg-dist.service' and 'journalctl -xn' for details. # systemctl status -l fetchmail ● fetchmail.dpkg-dist.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail.dpkg-dist) Active: failed (Result: exit-code) since Mon 2015-01-19 11:25:15 CET; 36s ago Process: 13937 ExecStart=/etc/init.d/fetchmail.dpkg-dist start (code=exited, status=203/EXEC) Jan 19 11:25:15 zita systemd[1]: fetchmail.dpkg-dist.service: control process exited, code=exited status=203 Jan 19 11:25:15 zita systemd[1]: Failed to start LSB: init-Script for system wide fetchmail daemon. Jan 19 11:25:15 zita systemd[1]: Unit fetchmail.dpkg-dist.service entered failed state. Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended. # systemctl daemon-reload # service fetchmail start # systemctl status -l fetchmail ● fetchmail.service - LSB: init script for per-user fetchmail daemons Loaded: loaded (/etc/init.d/fetchmail) Active: active (exited) since Mon 2015-01-19 11:26:28 CET; 6s ago Process: 13983 ExecStart=/etc/init.d/fetchmail start (code=exited, status=0/SUCCESS) Jan 19 11:26:27 zita fetchmail[13983]: Starting mail retrieval agent: fetchmail. Jan 19 11:26:28 zita fetchmail[13983]: Waiting for a Mail Transport Agent lising on the SMTP port...done. Jan 19 11:26:28 zita su[13992]: Successful su for flo by root Jan 19 11:26:28 zita su[13992]: + ??? root:flo Jan 19 11:26:28 zita su[13992]: pam_unix(su:session): session opened for usero by (uid=0) Jan 19 11:26:28 zita fetchmail[13983]: Starting fetchmail for user
Bug#775692: marked as done ([systemd] keymap.service does not start)
Your message dated Wed, 21 Jan 2015 13:04:39 + with message-id and subject line Bug#775404: fixed in systemd 215-10 has caused the Debian Bug report #775404, regarding [systemd] keymap.service does not start 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 ow...@bugs.debian.org immediately.) -- 775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-9 Severity: normal --- Please enter the report below this line. --- journalctl -b -p err yields systemd-sysv-generator[175]: Failed to create unit file /run/systemd/generator.late/keymap.service: File exists No files containing # Provides: keymap in /etc/init.d aside from /etc/init.d/keymap.sh. After downgrading all relevant packages to release=215-8 (testing) this error message does not show up. --- System information. --- Architecture: amd64 Kernel: Linux 3.18-2.towo-siduction-amd64 Debian Release: 8.0 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-== libacl1 (>= 2.2.51-8) | 2.2.52-2 libaudit1(>= 1:2.2.1) | 1:2.4-1+b1 libblkid1 (>= 2.17.2) | 2.25.2-4.1 libcap2 (>= 1:2.10) | 1:2.24-6 libcryptsetup4 (>= 2:1.4.3) | 2:1.6.6-4 libdbus-1-3(>= 1.1.1) | 1.8.14-1 libkmod2 (>= 5~) | 18-3 libpam0g(>= 0.99.7.1) | 1.1.8-3.1 libselinux1(>= 2.1.9) | 2.3-2 libsystemd-journal0 (= 208-7) | libudev1 (>= 189) | 215-9 libwrap0 (>= 7.6-4~) | 7.6.q-25 libsystemd-login0 (= 208-7) | util-linux (>= 2.19.1-2) | 2.25.2-4.1 initscripts (>= 2.88dsf-53.2) | 2.88dsf-58 sysv-rc | 2.88dsf-58 udev | 215-9 acl | 2.2.52-2 adduser | 3.113+nmu3 libcap2-bin | 1:2.24-6 Recommends (Version) | Installed =-+-=== libpam-systemd| 215-9 Suggests(Version) | Installed =-+-=== systemd-ui| 3-2 --- Output from package bug script --- --- End Message --- --- Begin Message --- Source: systemd Source-Version: 215-10 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 13:18:05 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 215-10 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility library - development files libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated) libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-jou
Bug#775404: marked as done ([systemd] networking.service does not start)
Your message dated Wed, 21 Jan 2015 13:04:39 + with message-id and subject line Bug#775404: fixed in systemd 215-10 has caused the Debian Bug report #775404, regarding [systemd] networking.service does not start 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 ow...@bugs.debian.org immediately.) -- 775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-9 Severity: important --- Please enter the report below this line. --- journalctl -b -p -err yields systemd-sysv-generator[7306]: Failed to create unit file /run/systemd/generator.late/networking.service: File exists systemd-sysv-generator[7306]: Failed to create unit file /run/systemd/generator.late/keymap.service: File exists Downgrading all relevant packages to release=215-8 (testing) restores the service. --- System information. --- Architecture: amd64 Kernel: Linux 3.18-2.towo-siduction-amd64 Debian Release: 8.0 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-== libacl1 (>= 2.2.51-8) | 2.2.52-2 libaudit1(>= 1:2.2.1) | 1:2.4-1+b1 libblkid1 (>= 2.17.2) | 2.25.2-4 libcap2 (>= 1:2.10) | 1:2.24-6 libcryptsetup4 (>= 2:1.4.3) | 2:1.6.6-4 libdbus-1-3(>= 1.1.1) | 1.8.14-1 libkmod2 (>= 5~) | 18-3 libpam0g(>= 0.99.7.1) | 1.1.8-3.1 libselinux1(>= 2.1.9) | 2.3-2 libsystemd-journal0 (= 208-7) | libudev1 (>= 189) | 215-9 libwrap0 (>= 7.6-4~) | 7.6.q-25 libsystemd-login0 (= 208-7) | util-linux (>= 2.19.1-2) | 2.25.2-4 initscripts (>= 2.88dsf-53.2) | 2.88dsf-58 sysv-rc | 2.88dsf-58 udev | 215-9 acl | 2.2.52-2 adduser | 3.113+nmu3 libcap2-bin | 1:2.24-6 Recommends (Version) | Installed =-+-=== libpam-systemd| 215-8 Suggests(Version) | Installed =-+-=== systemd-ui| 3-2 --- Output from package bug script --- --- End Message --- --- Begin Message --- Source: systemd Source-Version: 215-10 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 13:18:05 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 215-10 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility library - development files libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated) libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) li
Bug#775903: systemd: 'service initscript start' starts initscript.dpkg-dist under systemd
Hi Am 21.01.2015 um 12:30 schrieb Martin Pitt: > Florent Rougon [2015-01-21 12:05 +0100]: >> I tried systemd after a wheezy → sid upgrade and encountered an annoying >> problem: after modifying a file related to my /etc/init.d/fetchmail >> script[1], >> I decided to start the fetchmail service with 'service fetchmail start'[2]. >> To >> my great surprise, this did not start my /etc/init.d/fetchmail script but >> /etc/init.d/fetchmail.dpkg-dist, i.e., the script I had explicitely told dpkg >> to disable when doing the wheezy to sid upgrade. > > I'm 99% sure that this is another duplicate of https://bugs.debian.org/775404 > > I take it you have a /run/systemd/generator.late/fetchmail.service > symlink which points to fetchmail.dpkg-dist.service? > > I'm going to upload 215-10 with the fix for this in a few hours; it > would be nice if you could report back with either confirming that it > fixes the issue, or is something else (then I'll unduplicate this bug > report). This bug is related, but might be considered a bug on its own, regarding handling of temporary/backup conffiles. See my comments in [1]. I guess we should track this as a separate bug report. Michael [1] http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/2015-January/005613.html -- 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#775889: marked as done (breaks init scripts with .sh suffix)
Your message dated Wed, 21 Jan 2015 13:04:39 + with message-id and subject line Bug#775889: fixed in systemd 215-10 has caused the Debian Bug report #775889, regarding breaks init scripts with .sh suffix 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 ow...@bugs.debian.org immediately.) -- 775889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-9 Severity: serious Tags: upstream confirmed patch Michael points out a regression in 215-9 wrt. handling init scripts with a .sh suffix. This is closely related, but not identical to #775404, so let's track it as a separate bug. I posted a fix with a test case to the upstream ML: http://lists.freedesktop.org/archives/systemd-devel/2015-January/027245.html Martin - Forwarded message from Michael Biebl - Date: Thu, 15 Jan 2015 01:25:34 +0100 From: Michael Biebl To: Niels Thykier , 775...@bugs.debian.org, Martin Pitt CC: Cyril Brulebois , pkg-systemd-maintainers@lists.alioth.debian.org Subject: Re: Bug#775265: unblock: systemd/215-9 X-Spam-Status: No, score=0.8 required=3.4 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, T_RP_MATCHES_RCVD autolearn=no version=3.3.2 Am 13.01.2015 um 17:04 schrieb Niels Thykier: > Control: tags -1 d-i > > Ok from RT, CC'ing KiBi for d-i ACK. > > Original message quoted below for KiBi's convenience. :) > > ~Niels > > On 2015-01-13 12:07, Martin Pitt wrote: >> | [ Michael Biebl ] >> | * sysv-generator: handle Provides: for non-virtual facility names. >> | (Closes: #774335) >> >> RC bug. >> >> http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=7024b5117a A user reported a nasty regression via IRC regarding this patch. For SysV init scripts having a .sh extension, we create a foo.service -> foo.service symlink, and subsequently, systemctl start/stop/restart foo.service will fail: # apt-get install console-common Setting up console-common (0.7.88) ... Looking for keymap to install: NONE update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Failed to start keymap.service: Unit keymap.service failed to load: Too many levels of symbolic links. invoke-rc.d: initscript keymap.sh, action "start" failed. dpkg: error processing package console-common (--configure): subprocess installed post-installation script returned error exit status 6 Errors were encountered while processing: console-common Will need to fix that in a follow-up upload. Sorry for this. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? - End forwarded message - -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: systemd Source-Version: 215-10 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 13:18:05 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 215-10 Distribution: unstable Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-dae
Bug#775404: Bug#775265: unblock: systemd/215-9
Hi, Am 21.01.2015 um 10:52 schrieb Martin Pitt: > Control: tag 775404 patch > > Michael Biebl [2015-01-20 17:56 +0100]: >> I looked into this a bit more myself. Unfortunately, those .sh suffixes >> are not the only ways to trigger this particular bug. >> >> As can be seen in [1], this can also be caused by backup/temporary >> files, i.e. the name of the sysv init script no longer matches the name >> in the Provides: field, and therefor we create a symlink and subsequent >> creation of the real unit file fails. > > It can also happen if a script Provides: the name of another script. Correct. See my analysis in [1] under "*** conflicting Provides/Names ***" If two of those such packages are installed at the same time, first one wins with the current logic we have in the generator. The list is not very long, so I don't expect this to be huge issue in practice. As a side note, postfix and xmail using mail-transport-agent seems wrong, they should provide a insserv snippet for $mail-transport-agent. Same for busybox-syslogd and dsyslog, the correct facility here would be $syslog. I > think I caught all these cases now in tests, and proposed a patch > upstream: > http://lists.freedesktop.org/archives/systemd-devel/2015-January/027249.html > > It's not exactly "nice", but I can't think of a better/robust > solution. An alternative idea of mine, was to create the symlinks *after* the unit files have been written. In the end, it won't make a huge difference I guess. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774335#57 -- 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#775903: systemd: 'service initscript start' starts initscript.dpkg-dist under systemd
Control: unmerge -1 Control: severity -1 normal Control: retitle -1 sysv-generator: Do not create units for .dpkg-* files Hey Michael, Michael Biebl [2015-01-21 14:05 +0100]: > This bug is related, but might be considered a bug on its own, regarding > handling of temporary/backup conffiles. > > See my comments in [1]. I guess we should track this as a separate bug > report. Ah indeed, adding more backup suffixes seems appropriate, also for other things. With the fix in -10 this should at least not have such disastrous effects any more, but creating units for .dpkg-foo scripts is of course still wrong. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: 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#775903: systemd: 'service initscript start' starts initscript.dpkg-dist under systemd
Processing control commands:
> unmerge -1
Bug #775903 {Done: Martin Pitt } [systemd] systemd: 'service
initscript start' starts initscript.dpkg-dist under systemd
Bug #775404 {Done: Martin Pitt } [systemd] [systemd]
networking.service does not start
Bug #775692 {Done: Martin Pitt } [systemd] [systemd]
keymap.service does not start
Disconnected #775903 from all other report(s).
> severity -1 normal
Bug #775903 {Done: Martin Pitt } [systemd] systemd: 'service
initscript start' starts initscript.dpkg-dist under systemd
Severity set to 'normal' from 'serious'
> retitle -1 sysv-generator: Do not create units for .dpkg-* files
Bug #775903 {Done: Martin Pitt } [systemd] systemd: 'service
initscript start' starts initscript.dpkg-dist under systemd
Changed Bug title to 'sysv-generator: Do not create units for .dpkg-* files'
from 'systemd: 'service initscript start' starts initscript.dpkg-dist under
systemd'
--
775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404
775692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775692
775903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775903
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
Processed: reopening 775903
Processing commands for cont...@bugs.debian.org:
> reopen 775903
Bug #775903 {Done: Martin Pitt } [systemd] sysv-generator: Do
not create units for .dpkg-* files
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions systemd/215-10.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
775903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775903
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#739676: systemd-user PAM config breaks some libpam-* modules
Hi Martin, On 2015-01-21 11:35, Martin Pitt wrote: > On both my Debian sid and my Ubuntu system, the only difference > between common-session and common-session-noninteractive is that the > latter does not include libpam-systemd. Generally speaking, I believe (but haven't verified) that this will be the case for all packages where the Debian PAM meta-config sets the following flag: Session-Interactive-Only: yes I found that in src:systemd/debian/pam-configs/systemd. At least, that would explain the difference you observed. > Thus on a system which does *not* use any additional pam module, this > should effectively be a no-op change and thus quite safe. Yep! For the "systemd-user" PAM config, the move to -noninteractive only does one thing, namely to drop the implied pam_systemd. By re-adding it explicitly to the config (patch v2), the result on such systems must be a no-op. > Indeed installing libpam-mount only adds itself to common-session, not > to common-session-noninteractive. So with this change we would get the > desired effect. Yep. Rephrased, this means that on systems that *do* use additional PAM modules, this change would drop ops, but those ops shouldn't have been there in the first place. "systemd-user" should not call pam_mount, pam_script, etc. This does not affect the user; the "frontend" PAM sessions started by login, lightdm, and so on all @include common-session. This is only about "systemd-user" session triggered in the background. So it really should be safe. Regards, Christian ___ 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: tagging 775903
Processing commands for cont...@bugs.debian.org: > tags 775903 - security Bug #775903 [systemd] sysv-generator: Do not create units for .dpkg-* files Removed tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 775903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775903 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
Processed: Re: mate-settings-daemon: Massive memory leak
Processing commands for cont...@bugs.debian.org: > reassign 772910 libpam-systemd 215-8 Bug #772910 [mate-settings-daemon] mate-settings-daemon: Massive memory leak Bug reassigned from package 'mate-settings-daemon' to 'libpam-systemd'. No longer marked as found in versions mate-settings-daemon/1.8.2-1. Ignoring request to alter fixed versions of bug #772910 to the same values previously set Bug #772910 [libpam-systemd] mate-settings-daemon: Massive memory leak Marked as found in versions systemd/215-8. > forcemerge 732209 772910 Bug #732209 [libpam-systemd] unable to create file '/run/user/1000/dconf/user': Permission denied Bug #766464 [libpam-systemd] gksu pluma sets the ownership of /run/user/1000/dconf/user to root:root Bug #769889 [libpam-systemd] dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Bug #766464 [libpam-systemd] gksu pluma sets the ownership of /run/user/1000/dconf/user to root:root Marked as found in versions systemd/215-8. Marked as found in versions systemd/215-8. Marked as found in versions systemd/215-8. Bug #772910 [libpam-systemd] mate-settings-daemon: Massive memory leak Marked as found in versions systemd/215-7, systemd/215-6, and systemd/217-3. Added tag(s) unreproducible and moreinfo. Bug #769889 [libpam-systemd] dconf-CRITICAL: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. Merged 732209 766464 769889 772910 > thanks Stopping processing here. Please contact me if you need assistance. -- 732209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732209 766464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766464 769889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769889 772910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772910 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#732209: unable to create file '/run/user/1000/dconf/user': Permission denied
> 1. Init system installed on my system is systemd. > root@localhost:~# ps -p1 f > PID TTY STAT TIME COMMAND > 1 ?Ss 0:03 /sbin/init Well, that's a bit weird. On my systemd system, it looks like this. glaubitz@z6:~> ps -p1 f PID TTY STAT TIME COMMAND 1 ?Ss 0:54 /lib/systemd/systemd --system --deserialize 20 glaubitz@z6:~> What does systemctl | head say? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 ___ 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#772910: mate-settings-daemon: Massive memory leak
On 01/21/2015 03:03 PM, Vlad Orlov wrote: > Well, looking at the description, I see this is the same bug that has been > found in various situations before [1][2][3]. Just out of curiosity, what init system are you using? Usually, these weird bugs only occur when using something like systemd-shim and any other of these hacky systemd work arounds. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 ___ 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: tagging 775903
Processing commands for cont...@bugs.debian.org: > tags 775903 + pending Bug #775903 [systemd] sysv-generator: Do not create units for .dpkg-* files Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 775903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775903 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#772910: mate-settings-daemon: Massive memory leak
Hi, > Just out of curiosity, what init system are you using? Usually, these > weird bugs only occur when using something like systemd-shim and any > other of these hacky systemd work arounds. Well, I have one system with systemd-shim + sysvinit-core and a few ones with systemd as init. I can reproduce the issue (as I described in [1] ) in all of them. [1] https://bugs.debian.org/766464 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processing of systemd_218-4_amd64.changes
systemd_218-4_amd64.changes uploaded successfully to localhost along with the files: systemd_218-4.dsc systemd_218-4.debian.tar.xz systemd_218-4_amd64.deb systemd-sysv_218-4_amd64.deb libpam-systemd_218-4_amd64.deb libsystemd0_218-4_amd64.deb libsystemd-dev_218-4_amd64.deb libsystemd-login0_218-4_amd64.deb libsystemd-login-dev_218-4_amd64.deb libsystemd-daemon0_218-4_amd64.deb libsystemd-daemon-dev_218-4_amd64.deb libsystemd-journal0_218-4_amd64.deb libsystemd-journal-dev_218-4_amd64.deb libsystemd-id128-0_218-4_amd64.deb libsystemd-id128-dev_218-4_amd64.deb udev_218-4_amd64.deb libudev1_218-4_amd64.deb libudev-dev_218-4_amd64.deb udev-udeb_218-4_amd64.udeb libudev1-udeb_218-4_amd64.udeb libgudev-1.0-0_218-4_amd64.deb gir1.2-gudev-1.0_218-4_amd64.deb libgudev-1.0-dev_218-4_amd64.deb python3-systemd_218-4_amd64.deb systemd-dbg_218-4_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.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
systemd_218-4_amd64.changes ACCEPTED into experimental
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 21 Jan 2015 15:57:50 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev
libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0
libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb
libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg
Architecture: source amd64
Version: 218-4
Distribution: experimental
Urgency: medium
Maintainer: Debian systemd Maintainers
Changed-By: Martin Pitt
Description:
gir1.2-gudev-1.0 - libgudev-1.0 introspection data
libgudev-1.0-0 - GObject-based wrapper library for libudev
libgudev-1.0-dev - libgudev-1.0 development files
libpam-systemd - system and service manager - PAM module
libsystemd-daemon-dev - systemd utility library (transitional package)
libsystemd-daemon0 - systemd utility library (deprecated)
libsystemd-dev - systemd utility library - development files
libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated)
libsystemd-id128-dev - systemd 128 bit ID utility library (transitional
package)
libsystemd-journal-dev - systemd journal utility library (transitional package)
libsystemd-journal0 - systemd journal utility library (deprecated)
libsystemd-login-dev - systemd login utility library (transitional package)
libsystemd-login0 - systemd login utility library (deprecated)
libsystemd0 - systemd utility library
libudev-dev - libudev development files
libudev1 - libudev shared library
libudev1-udeb - libudev shared library (udeb)
python3-systemd - Python 3 bindings for systemd
systemd- system and service manager
systemd-dbg - system and service manager (debug symbols)
systemd-sysv - system and service manager - SysV links
udev - /dev/ and hotplug management daemon
udev-udeb - /dev/ and hotplug management daemon (udeb)
Closes: 739676 742048 768644 774335 775067 775331 775404 775889 775903
Changes:
systemd (218-4) experimental; urgency=medium
.
[ Michael Biebl ]
* sysv-generator: handle Provides: for non-virtual facility names.
(Closes: #774335)
* Fix systemd-remount-fs.service to not fail on remounting /usr if /usr
isn't mounted yet. This happens with initramfs-tools < 0.118 which we
might not get into Jessie any more. (Closes: #742048)
.
[ Martin Pitt ]
* fstab-generator: Handle mountall's non-standard "nobootwait" and
"optional" options. ("bootwait" is already the systemd default behaviour,
and "showthrough" is irrelevant here, so both can be ignored).
* Add autopkgtest for one-time boot with upstart when systemd-sysv is
installed. This test only works under Ubuntu which has a split out
upstart-bin package, and will be skipped under Debian.
* debian/ifup@.service: Check if ifup succeeds by calling ifquery, to
work around ifup not failing on invalid interfaces (see #773539)
* debian/ifup@.service: Set proper service type (oneshot).
* sysv-generator: Handle .sh suffixes when translating Provides:.
(Closes: #775889)
* sysv-generator: Make real units overwrite symlinks generated by Provides:
from other units. Fixes failures due to presence of backup or old init.d
scripts. (Closes: #775404)
* Fix journal forwarding to syslog in containers without CAP_SYS_ADMIN.
(Closes: #775067)
* Re-enable AppArmor support, now that libapparmor1 moved to /lib. Add
versioned dependency as long as this is still only in experimental.
(Closes: #775331)
* Add some missing dpkg and ucf temp files to the "hidden file" filter, to
e. g. avoid creating units for them through the sysv-generator.
(Closes: #775903)
* Silence useless warning about /etc/localtime not being a symlink. This is
deliberate in Debian with /usr (possibly) being on a separate partition.
(LP: #1409594)
.
[ Christian Kastner ]
* Use common-session-noninteractive in systemd-user's PAM config, instead of
common-session. The latter can include PAM modules like libpam-mount which
expect to be called just once and/or interactively, which already happens
for login, ssh, or the display-manager. Add pam_systemd.so explicitly, as
it's not included in -noninteractive, but is always required (and
idempotent). There is no net change on systemd which don't use manually
installed PAM modules. (Closes: #739676)
.
[ Michael Biebl ]
* Make sure we run debian-fixup.service after /var has been mounted if /var
is on a separate partition. Otherwise we might end up creating the
/var/lock and /var/run symlink in the underlying root filesystem.
(Closes: #768644)
Checksums-Sha1:
f1529f55ba86808889ae79da53bba5da76c8a166 4144 systemd_218-4.dsc
250a163535fbfbc7548b8096391973aad094ec88 132664 systemd_218-4.debian.tar.xz
55752877daa436c3368e5cc03988bb27f71026df 3095
Bug#763327: marked as done ([systemd] FAILED to remount /)
Your message dated Wed, 21 Jan 2015 15:22:03 + with message-id and subject line Bug#742048: fixed in systemd 218-4 has caused the Debian Bug report #742048, regarding [systemd] FAILED to remount / 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 ow...@bugs.debian.org immediately.) -- 742048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-5 Severity: normal --- Please enter the report below this line. --- Since recent upgrade to 215-5 (maybe previous as well), get one or two FAILED to remount / message at the very startup. At this point, boot leaves the silent mode, shows all the messages, proceeds without any problems. System is running normally. Note: Had this on the 3.16 kernel. Tried 3.14 to see if the problem is with initramfs-tools which only updated 3.16. Error occurs here as well. --- System information. --- Architecture: amd64 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends(Version) | Installed -+-= libacl1(>= 2.2.51-8) | 2.2.52-2 libaudit1 (>= 1:2.2.1) | 1:2.4-1 libc6 (>= 2.17) | libcap2(>= 2.10) | libcryptsetup4 (>= 2:1.4.3) | libdbus-1-3 (>= 1.1.1) | libgcrypt11 (>= 1.5.1) | libkmod2 (>= 5~) | liblzma5(>= 5.1.1alpha+20120614) | libpam0g (>= 0.99.7.1) | libselinux1 (>= 2.1.9) | libsystemd-daemon0(= 204-14) | libsystemd-journal0 (= 204-14) | libudev1(>= 189) | libwrap0 (>= 7.6-4~) | libsystemd-login0 (= 204-14) | util-linux (>= 2.19.1-2) | initscripts (>= 2.88dsf-17) | sysv-rc | udev | acl | adduser | libcap2-bin | Recommends (Version) | Installed =-+-=== libpam-systemd| 215-5 Suggests(Version) | Installed =-+-=== systemd-ui| 3-2 --- Output from package bug script --- --- End Message --- --- Begin Message --- Source: systemd Source-Version: 218-4 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 742...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 15:57:50 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 218-4 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility l
Bug#739676: marked as done (systemd-user PAM config breaks some libpam-* modules)
Your message dated Wed, 21 Jan 2015 15:22:02 + with message-id and subject line Bug#739676: fixed in systemd 218-4 has caused the Debian Bug report #739676, regarding systemd-user PAM config breaks some libpam-* modules 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 ow...@bugs.debian.org immediately.) -- 739676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-mount Version: 2.14-1 Severity: important Dear Maintainer, On a brand-new debian installation, I modified /etc/security/pam_mount.conf.xml to automatically mount a luks-encrypted home partition when I logged in. However, when I tested this out, I found that it worked properly when i logged into the virtual terminal (CTRL ALT F1), but when I logged into xfce using lightdm, it would properly mount my home directory, but failed to unmount it when I logged out. This is a security issue, as it leaves encrypted drives vulnerable. The /var/log/auth log indicates that it still thinks I have an open session when I log out. Here is the relevant section Feb 21 01:48:47 jeremy-laptop lightdm: pam_unix(lightdm:session): session closed for user jeremy Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:706): received order to close things Feb 21 01:48:47 jeremy-laptop lightdm: command: 'pmvarrun' '-u' 'jeremy' '-o' '-1' Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:441): pmvarrun says login count is 1 Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:735): jeremy seems to have other remaining open sessions Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:743): pam_mount execution complete Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:116): Clean global config (0) Feb 21 01:48:47 jeremy-laptop lightdm: (pam_mount.c:133): clean system authtok=0x7fda75bba760 (0) Feb 21 01:48:47 jeremy-laptop polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name :1.40, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.utf8) (disconnected from bus) -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam-mount depends on: ii base-files 7.2 ii libc6 2.17-97 ii libcryptsetup4 2:1.6.1-1 ii libhx28 3.18-1 ii libmount1 2.20.1-5.6 ii libpam-runtime 1.1.8-2 ii libpam0g1.1.8-2 ii libpcre31:8.31-2 ii libssl1.0.0 1.0.1f-1 ii libxml2 2.9.1+dfsg1-3 ii mount 2.20.1-5.6 libpam-mount recommends no packages. Versions of packages libpam-mount suggests: pn cifs-utils pn davfs2 ii fuse2.9.2-4 ii lsof4.86+dfsg-1 pn ncpfs ii openssl 1.0.1f-1 ii psmisc 22.20-1 pn sshfs pn tc-utils pn xfsprogs -- Configuration Files: /etc/security/pam_mount.conf.xml changed: -- no debconf information --- End Message --- --- Begin Message --- Source: systemd Source-Version: 218-4 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 739...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 15:57:50 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 218-4 Distribution: experimental Urgency: medium Maintainer: De
Bug#775067: marked as done (systemd: journald doesn't forward messages to syslog w/o CAP_SYS_ADMIN (LXC))
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
and subject line Bug#775067: fixed in systemd 218-4
has caused the Debian Bug report #775067,
regarding systemd: journald doesn't forward messages to syslog w/o
CAP_SYS_ADMIN (LXC)
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 ow...@bugs.debian.org
immediately.)
--
775067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-8
Severity: grave
Tags: upstream patch
Justification: causes non-serious data loss
Dear Maintainer,
when using LXC containers without CAP_SYS_ADMIN, journald fails to
forward any messages to syslog by default. Since the journal is not
persistent by default, no logs are stored at all, hence the
classification as 'data loss'. Also, this is a regression from Wheezy,
where a container without CAP_SYS_ADMIN and syslog did indeed store
persistent logs in /var/log/{syslog,messages,...}.
Note that there is NO other problem with systemd related to missing
CAP_SYS_ADMIN in a container (that I have found so far), provided all
required (pseudo-) file systems are mounted beforehand (which can be
done by configuration with Jessie's LXC version). I do know that
upstream claims that CAP_SYS_ADMIN-less containers are currently not
really supported, but they do intend to work towards that, and, from
what I can tell, apart from this journald problem, I have found no
issue whatsoever with a missing CAP_SYS_ADMIN (it actually works even
better than under sysvinit because it doesn't try to do some stuff
it's not supposed to do in containers that cause error messages with
sysvinit) - and since these kinds of containers were working in
Wheezy with its default init, I think this should be supported in
Jessie, too, especially if the fix is really easy, see below.
This bug is independent of the syslog implementation used, because no
syslog implementation in Jessie supports reading directly from the
journal, as far as I can tell (syslog-ng is too old, rsyslog is built
without imjournal support), so all rely on ForwardToSyslog=yes.
The reason why this problem occurs is that journald tries to fake
SCM_CREDENTIALS before sending a packet to the syslog daemon. With
CAP_SETUID and CAP_SETGID, faking uid/gid is not a problem, but to fake
the pid in struct ucred, one needs CAP_SYS_ADMIN (according to current
kernel source).
Also note that without activating debugging in journald, this problem
can not be diagnosed easily (it took me a while with strace to find the
problem).
Note, however, two things:
- journald does (and can) not guarantee that it can fake the pid,
because the process could have already exited. If you look at the
source, in case ESRCH is returned, it just fakes uid/gid and uses
its own pid
- both rsyslog and syslog-ng (haven't tried anything else yet) don't
rely on SCM_CREDENTIAL's pid anyway in their default configuration,
so at least in the default configuration there's no reason to fail
in that case.
I have created (and tested) an absolutely trivial patch that fixes this
by not only checking for ESRCH but also EPERM and then avoid faking the
pid.
I have tested this with both rsyslog and syslog-ng and it works and
both store (the same ;-)) persistent log messages in
/var/log/{messages,syslog,...}.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-58
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-4
ii libc6 2.19-13
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-4
ii libgcrypt20 1.6.2-4+b1
ii libkmod218-3
ii liblzma55.1.1alpha+20120614-2+b3
ii libpam0g1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-8
ii mount 2.25.2-4
ii sysv-rc 2.88dsf-58
ii udev215-8
ii util-linux 2.25.2-4
Versions of packages systemd recommends:
ii dbus1.8.12-3
ii libpam-systemd 215-8
Versions of packages systemd suggests:
pn systemd-ui
-- no debconf information
Description: Make journald syslog fwd'ing work w/o CAP_SYS_ADMIN
In case CAP_SYS_ADMIN is missing, one cannot fake pid in struct ucred
Bug#775692: marked as done ([systemd] keymap.service does not start)
Your message dated Wed, 21 Jan 2015 15:22:03 + with message-id and subject line Bug#775404: fixed in systemd 218-4 has caused the Debian Bug report #775404, regarding [systemd] keymap.service does not start 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 ow...@bugs.debian.org immediately.) -- 775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-9 Severity: normal --- Please enter the report below this line. --- journalctl -b -p err yields systemd-sysv-generator[175]: Failed to create unit file /run/systemd/generator.late/keymap.service: File exists No files containing # Provides: keymap in /etc/init.d aside from /etc/init.d/keymap.sh. After downgrading all relevant packages to release=215-8 (testing) this error message does not show up. --- System information. --- Architecture: amd64 Kernel: Linux 3.18-2.towo-siduction-amd64 Debian Release: 8.0 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-== libacl1 (>= 2.2.51-8) | 2.2.52-2 libaudit1(>= 1:2.2.1) | 1:2.4-1+b1 libblkid1 (>= 2.17.2) | 2.25.2-4.1 libcap2 (>= 1:2.10) | 1:2.24-6 libcryptsetup4 (>= 2:1.4.3) | 2:1.6.6-4 libdbus-1-3(>= 1.1.1) | 1.8.14-1 libkmod2 (>= 5~) | 18-3 libpam0g(>= 0.99.7.1) | 1.1.8-3.1 libselinux1(>= 2.1.9) | 2.3-2 libsystemd-journal0 (= 208-7) | libudev1 (>= 189) | 215-9 libwrap0 (>= 7.6-4~) | 7.6.q-25 libsystemd-login0 (= 208-7) | util-linux (>= 2.19.1-2) | 2.25.2-4.1 initscripts (>= 2.88dsf-53.2) | 2.88dsf-58 sysv-rc | 2.88dsf-58 udev | 215-9 acl | 2.2.52-2 adduser | 3.113+nmu3 libcap2-bin | 1:2.24-6 Recommends (Version) | Installed =-+-=== libpam-systemd| 215-9 Suggests(Version) | Installed =-+-=== systemd-ui| 3-2 --- Output from package bug script --- --- End Message --- --- Begin Message --- Source: systemd Source-Version: 218-4 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 15:57:50 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 218-4 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility library - development files libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated) libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-jo
Bug#775889: marked as done (breaks init scripts with .sh suffix)
Your message dated Wed, 21 Jan 2015 15:22:03 + with message-id and subject line Bug#775889: fixed in systemd 218-4 has caused the Debian Bug report #775889, regarding breaks init scripts with .sh suffix 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 ow...@bugs.debian.org immediately.) -- 775889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-9 Severity: serious Tags: upstream confirmed patch Michael points out a regression in 215-9 wrt. handling init scripts with a .sh suffix. This is closely related, but not identical to #775404, so let's track it as a separate bug. I posted a fix with a test case to the upstream ML: http://lists.freedesktop.org/archives/systemd-devel/2015-January/027245.html Martin - Forwarded message from Michael Biebl - Date: Thu, 15 Jan 2015 01:25:34 +0100 From: Michael Biebl To: Niels Thykier , 775...@bugs.debian.org, Martin Pitt CC: Cyril Brulebois , pkg-systemd-maintainers@lists.alioth.debian.org Subject: Re: Bug#775265: unblock: systemd/215-9 X-Spam-Status: No, score=0.8 required=3.4 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, T_RP_MATCHES_RCVD autolearn=no version=3.3.2 Am 13.01.2015 um 17:04 schrieb Niels Thykier: > Control: tags -1 d-i > > Ok from RT, CC'ing KiBi for d-i ACK. > > Original message quoted below for KiBi's convenience. :) > > ~Niels > > On 2015-01-13 12:07, Martin Pitt wrote: >> | [ Michael Biebl ] >> | * sysv-generator: handle Provides: for non-virtual facility names. >> | (Closes: #774335) >> >> RC bug. >> >> http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=7024b5117a A user reported a nasty regression via IRC regarding this patch. For SysV init scripts having a .sh extension, we create a foo.service -> foo.service symlink, and subsequently, systemctl start/stop/restart foo.service will fail: # apt-get install console-common Setting up console-common (0.7.88) ... Looking for keymap to install: NONE update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Failed to start keymap.service: Unit keymap.service failed to load: Too many levels of symbolic links. invoke-rc.d: initscript keymap.sh, action "start" failed. dpkg: error processing package console-common (--configure): subprocess installed post-installation script returned error exit status 6 Errors were encountered while processing: console-common Will need to fix that in a follow-up upload. Sorry for this. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? - End forwarded message - -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: systemd Source-Version: 218-4 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 15:57:50 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 218-4 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-da
Bug#775903: marked as done (sysv-generator: Do not create units for .dpkg-* files)
Your message dated Wed, 21 Jan 2015 15:22:03 + with message-id and subject line Bug#775903: fixed in systemd 218-4 has caused the Debian Bug report #775903, regarding sysv-generator: Do not create units for .dpkg-* files 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 ow...@bugs.debian.org immediately.) -- 775903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-9 Severity: serious Tags: security Dear maintainer, I tried systemd after a wheezy → sid upgrade and encountered an annoying problem: after modifying a file related to my /etc/init.d/fetchmail script[1], I decided to start the fetchmail service with 'service fetchmail start'[2]. To my great surprise, this did not start my /etc/init.d/fetchmail script but /etc/init.d/fetchmail.dpkg-dist, i.e., the script I had explicitely told dpkg to disable when doing the wheezy to sid upgrade. [1] Apparently run with 'set -e' under systemd, but that is another issue. [2] Being new to systemd, I didn't know the systemd idiom for this, but my reading of /usr/sbin/service leads me to think that 'systemctl start fetchmail.service' would have done exactly the same, hence the report to systemd as opposed to sysvinit-utils. Apparently, systemd somehow kept thinking that the fetchmail service corresponded to that .dpkg-dist script until I ran 'systemctl daemon-reload'. This behavior has the adverse effect of running a service the administrator explicitely disabled, or of running it with completely different options from those he configured, etc. This is why I set the security tag on this bug. Maybe the severity should be raised too. Here is a transcript of the commands I ran to trigger and work around the bug: # service fetchmail start # systemctl status -l fetchmail ● fetchmail.dpkg-dist.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail.dpkg-dist) Active: active (exited) since Mon 2015-01-19 10:26:35 CET; 51min ago Jan 19 10:26:35 zita fetchmail.dpkg-dist[3090]: Not starting fetchmail daemon, disabled via /etc/default/fetchmail. Jan 19 10:26:35 zita systemd[1]: Started LSB: init-Script for system wide fetchmail daemon. # find /etc/rc*.d /etc/init.d |grep fetchmail /etc/rc0.d/K01fetchmail /etc/rc1.d/K01fetchmail /etc/rc2.d/S01local-rotate-fetchmail-logfiles /etc/rc2.d/S04fetchmail /etc/rc3.d/S01local-rotate-fetchmail-logfiles /etc/rc3.d/S04fetchmail /etc/rc4.d/S01local-rotate-fetchmail-logfiles /etc/rc4.d/S04fetchmail /etc/rc5.d/S01local-rotate-fetchmail-logfiles /etc/rc5.d/S04fetchmail /etc/rc6.d/K01fetchmail /etc/init.d/fetchmail.dpkg-dist /etc/init.d/fetchmail /etc/init.d/local-rotate-fetchmail-logfiles # mv fetchmail.dpkg-dist /root/tmp # service fetchmail start Warning: Unit file of fetchmail.service changed on disk, 'systemctl daemon-reload' recommended. Job for fetchmail.dpkg-dist.service failed. See 'systemctl status fetchmail.dpkg-dist.service' and 'journalctl -xn' for details. # systemctl status -l fetchmail ● fetchmail.dpkg-dist.service - LSB: init-Script for system wide fetchmail daemon Loaded: loaded (/etc/init.d/fetchmail.dpkg-dist) Active: failed (Result: exit-code) since Mon 2015-01-19 11:25:15 CET; 36s ago Process: 13937 ExecStart=/etc/init.d/fetchmail.dpkg-dist start (code=exited, status=203/EXEC) Jan 19 11:25:15 zita systemd[1]: fetchmail.dpkg-dist.service: control process exited, code=exited status=203 Jan 19 11:25:15 zita systemd[1]: Failed to start LSB: init-Script for system wide fetchmail daemon. Jan 19 11:25:15 zita systemd[1]: Unit fetchmail.dpkg-dist.service entered failed state. Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended. # systemctl daemon-reload # service fetchmail start # systemctl status -l fetchmail ● fetchmail.service - LSB: init script for per-user fetchmail daemons Loaded: loaded (/etc/init.d/fetchmail) Active: active (exited) since Mon 2015-01-19 11:26:28 CET; 6s ago Process: 13983 ExecStart=/etc/init.d/fetchmail start (code=exited, status=0/SUCCESS) Jan 19 11:26:27 zita fetchmail[13983]: Starting mail retrieval agent: fetchmail. Jan 19 11:26:28 zita fetchmail[13983]: Waiting for a Mail Transport Agent lising on the SMTP port...done. Jan 19 11:26:28 zita su[13992]: Successful su for flo by root Jan 19 11:26:28 zita su[13992]: + ??? root:flo Jan 19 11:26:28 zita su[13992]: pam_unix(su:session): session opened for usero by (uid=0) Jan 19 11:26:28 zita fetchmail[13983]: Starting fetchmail for user flo...done Jan 19 11:26:2
Bug#772910: mate-settings-daemon: Massive memory leak
On 01/21/2015 04:03 PM, Vlad Orlov wrote: > Well, I have one system with systemd-shim + sysvinit-core and a few ones > with systemd as init. I can reproduce the issue (as I described in [1] ) in > all > of them. Ok, I just followed your steps to reproduce on a clean Jessie installation and I couldn't actually reproduce it. The file /run/user/1000/dconf/user keeps the ownership of the original, non-root owner. On the other hand, I fully agree with Lennart's statement here [1]. Modern desktop applications aren't really designed anymore to run in an "su -" environment since there are too many other interdependencies like dbus that cannot dynamically change the session. I really wouldn't advise running any desktop applications using "su -" for that matter. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 ___ 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#774335: marked as done (Provides: in SysV init scripts are not handled correctly, leading to wrong orderings)
Your message dated Wed, 21 Jan 2015 15:22:03 + with message-id and subject line Bug#774335: fixed in systemd 218-4 has caused the Debian Bug report #774335, regarding Provides: in SysV init scripts are not handled correctly, leading to wrong orderings 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 ow...@bugs.debian.org immediately.) -- 774335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774335 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-sysv Version: 218-3 Severity: important Tags: upstream Dear Maintainer, I'm finding that autofs mounts which come from NIS maps don't show up when using systemd. I have a VM with an amd64 install of Jessie which uses autofs with a NIS map. Booting up, and the autofs mount points do not show up. If I restart autofs manually they then start working properly. I have an almost identical VM which has sysvinit instead of systemd where autofs works just fine. Looking at the logging in journalctl, it looks like autofs is being started before NIS (or possibly at exactly the same time). Jan 01 00:49:41 jessie-test systemd[1]: Inserted module 'autofs4' Jan 01 00:49:43 jessie-test nis[435]: Setting NIS domainname to: local.diamand.org. Jan 01 00:49:43 jessie-test autofs[436]: Starting automount Jan 01 00:49:44 jessie-test nis[435]: Starting NIS services: ypbind. sysv-generator seems to correctly generate an autofs.service file which has a dependency on NIS, specifically, ypbind: $ grep "After" autofs.service After=network-online.target remote-fs.target systemd-journald-dev-log.socket ypbind.service nslcd.service slapd.service But nothing in the nis.service file mentions ypbind, and so the dependency never gets setup, and the ordering isn't reliable. $ grep ypbind nis.service -- nothing -- Probably this means that if you're lucky, the timing will work out, and if you're not, it won't! I'm using systemd-syv version 218-3 from experimental on top of Jessie. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-sysv depends on: ii systemd 218-3 systemd-sysv recommends no packages. systemd-sysv suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: systemd Source-Version: 218-4 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 774...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 15:57:50 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 218-4 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility library - development files libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated) libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) libsystemd-journal0 - systemd journ
Bug#775331: marked as done (systemd: Please enable AppArmor support again)
Your message dated Wed, 21 Jan 2015 15:22:03 +
with message-id
and subject line Bug#775331: fixed in systemd 218-4
has caused the Debian Bug report #775331,
regarding systemd: Please enable AppArmor support again
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 ow...@bugs.debian.org
immediately.)
--
775331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 218-3
Severity: wishlist
User: pkg-apparmor-t...@lists.alioth.debian.org
Usertags: platform
Hi,
as proposed on #760526, AppArmor support was enabled in 217-1,
but then it was disabled again in 217-2 (commit 48375254)
since it first required moving libapparmor to /lib (#771667).
The apparmor package in experimental now has moved libapparmor to
/lib, thanks to Martin's patch, so I believe that AppArmor support can
now be re-enabled in systemd/experimental.
Thanks in advance!
Cheers,
--
intrigeri
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 218-4
We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 775...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Pitt (supplier of updated systemd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 21 Jan 2015 15:57:50 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev
libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0
libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb
libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg
Architecture: source amd64
Version: 218-4
Distribution: experimental
Urgency: medium
Maintainer: Debian systemd Maintainers
Changed-By: Martin Pitt
Description:
gir1.2-gudev-1.0 - libgudev-1.0 introspection data
libgudev-1.0-0 - GObject-based wrapper library for libudev
libgudev-1.0-dev - libgudev-1.0 development files
libpam-systemd - system and service manager - PAM module
libsystemd-daemon-dev - systemd utility library (transitional package)
libsystemd-daemon0 - systemd utility library (deprecated)
libsystemd-dev - systemd utility library - development files
libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated)
libsystemd-id128-dev - systemd 128 bit ID utility library (transitional
package)
libsystemd-journal-dev - systemd journal utility library (transitional package)
libsystemd-journal0 - systemd journal utility library (deprecated)
libsystemd-login-dev - systemd login utility library (transitional package)
libsystemd-login0 - systemd login utility library (deprecated)
libsystemd0 - systemd utility library
libudev-dev - libudev development files
libudev1 - libudev shared library
libudev1-udeb - libudev shared library (udeb)
python3-systemd - Python 3 bindings for systemd
systemd- system and service manager
systemd-dbg - system and service manager (debug symbols)
systemd-sysv - system and service manager - SysV links
udev - /dev/ and hotplug management daemon
udev-udeb - /dev/ and hotplug management daemon (udeb)
Closes: 739676 742048 768644 774335 775067 775331 775404 775889 775903
Changes:
systemd (218-4) experimental; urgency=medium
.
[ Michael Biebl ]
* sysv-generator: handle Provides: for non-virtual facility names.
(Closes: #774335)
* Fix systemd-remount-fs.service to not fail on remounting /usr if /usr
isn't mounted yet. This happens with initramfs-tools < 0.118 which we
might not get into Jessie any more. (Closes: #742048)
.
[ Martin Pitt ]
* fstab-generator: Handle mountall's non-standard "nobootwait" and
"optional" options. ("bootwait" is already the systemd default behaviour,
and "showthrough" is irrelevant here, so both can be ignored).
* Add autopkgtest for one-time boot with upstart when systemd-sysv is
installed. This test only works under Ubuntu which has a split out
upstart-bin package, and will be skipped under Debian.
Bug#775404: marked as done ([systemd] networking.service does not start)
Your message dated Wed, 21 Jan 2015 15:22:03 + with message-id and subject line Bug#775404: fixed in systemd 218-4 has caused the Debian Bug report #775404, regarding [systemd] networking.service does not start 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 ow...@bugs.debian.org immediately.) -- 775404: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-9 Severity: important --- Please enter the report below this line. --- journalctl -b -p -err yields systemd-sysv-generator[7306]: Failed to create unit file /run/systemd/generator.late/networking.service: File exists systemd-sysv-generator[7306]: Failed to create unit file /run/systemd/generator.late/keymap.service: File exists Downgrading all relevant packages to release=215-8 (testing) restores the service. --- System information. --- Architecture: amd64 Kernel: Linux 3.18-2.towo-siduction-amd64 Debian Release: 8.0 500 unstableftp.de.debian.org 500 testing ftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-== libacl1 (>= 2.2.51-8) | 2.2.52-2 libaudit1(>= 1:2.2.1) | 1:2.4-1+b1 libblkid1 (>= 2.17.2) | 2.25.2-4 libcap2 (>= 1:2.10) | 1:2.24-6 libcryptsetup4 (>= 2:1.4.3) | 2:1.6.6-4 libdbus-1-3(>= 1.1.1) | 1.8.14-1 libkmod2 (>= 5~) | 18-3 libpam0g(>= 0.99.7.1) | 1.1.8-3.1 libselinux1(>= 2.1.9) | 2.3-2 libsystemd-journal0 (= 208-7) | libudev1 (>= 189) | 215-9 libwrap0 (>= 7.6-4~) | 7.6.q-25 libsystemd-login0 (= 208-7) | util-linux (>= 2.19.1-2) | 2.25.2-4 initscripts (>= 2.88dsf-53.2) | 2.88dsf-58 sysv-rc | 2.88dsf-58 udev | 215-9 acl | 2.2.52-2 adduser | 3.113+nmu3 libcap2-bin | 1:2.24-6 Recommends (Version) | Installed =-+-=== libpam-systemd| 215-8 Suggests(Version) | Installed =-+-=== systemd-ui| 3-2 --- Output from package bug script --- --- End Message --- --- Begin Message --- Source: systemd Source-Version: 218-4 We believe that the bug you reported is fixed in the latest version of systemd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 775...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Pitt (supplier of updated systemd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jan 2015 15:57:50 +0100 Source: systemd Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg Architecture: source amd64 Version: 218-4 Distribution: experimental Urgency: medium Maintainer: Debian systemd Maintainers Changed-By: Martin Pitt Description: gir1.2-gudev-1.0 - libgudev-1.0 introspection data libgudev-1.0-0 - GObject-based wrapper library for libudev libgudev-1.0-dev - libgudev-1.0 development files libpam-systemd - system and service manager - PAM module libsystemd-daemon-dev - systemd utility library (transitional package) libsystemd-daemon0 - systemd utility library (deprecated) libsystemd-dev - systemd utility library - development files libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated) libsystemd-id128-dev - systemd 128 bit ID utility library (transitional package) libsystemd-journal-dev - systemd journal utility library (transitional package) l
Bug#775903: systemd: 'service initscript start' starts initscript.dpkg-dist under systemd
Hi Martin, hi Michael, Martin Pitt wrote: > I'm 99% sure that this is another duplicate of https://bugs.debian.org/775404 > > I take it you have a /run/systemd/generator.late/fetchmail.service > symlink which points to fetchmail.dpkg-dist.service? Well, I have this file but it is a regular file starting with: # Automatically generated by systemd-sysv-generator [Unit] SourcePath=/etc/init.d/fetchmail Description=LSB: init script for per-user fetchmail daemons Before=runlevel2.target runlevel3.target runlevel4.target runlevel5.target shutdown.target After=network-online.target mail-transport-agent.service local-fs.target remote-fs.target local-rotate-fetchmail-logfiles.service Wants=network-online.target Conflicts=shutdown.target This shows that it was generated from my own fetchmail script, not from fetchmail.dpkg-dist. But as explained in my previous message, I fixed my system by running 'systemctl daemon-reload'. Maybe it had the symlink you mentioned when the bug was triggered, I can't say for sure now. > I'm going to upload 215-10 with the fix for this in a few hours; it > would be nice if you could report back with either confirming that it > fixes the issue, or is something else (then I'll unduplicate this bug > report). I can test things if you want, but I have no idea of systemd things such as automatic unit creation from init scripts, therefore I am not sure I can restore the conditions in which I encountered the bug (I suspect just recreating the .dpkg-dist file won't be enough). However, if you give me precise instructions, I can try to reproduce the bug and see if your new package fixes it. Thank you! -- Florent ___ 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#772856: marked as done (Please backport .conf.d configuration directory support from 218)
Your message dated Wed, 21 Jan 2015 16:53:13 +0100 with message-id <54bfcb69.2090...@debian.org> and subject line Re: Bug#772856: Please backport .conf.d configuration directory support from 218 has caused the Debian Bug report #772856, regarding Please backport .conf.d configuration directory support from 218 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 ow...@bugs.debian.org immediately.) -- 772856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 215-8 Severity: wishlist Please consider backporting the patches in systemd 218 that implement ..conf.d configuration directories for each existing .conf file. In particular, I'd really like to have logind.conf.d and journald.conf.d support for jessie. - Josh Triplett --- End Message --- --- Begin Message --- Am 05.01.2015 um 01:12 schrieb Josh Triplett: > On Sun, Jan 04, 2015 at 08:15:27PM +0100, Michael Biebl wrote: >> Am 12.12.2014 um 13:53 schrieb Josh Triplett: >>> On Fri, Dec 12, 2014 at 09:34:37AM +0100, Michael Biebl wrote: >> Afaics, this hasn't happened yet. Since we are rather late in the >> release cycle, and from now on, only release critical bugs will be >> accepted by the release team, I'm going to reject/close this bug report >> as it is a rather large patch. > > I was going to suggest that myself, actually; AFAICT the freeze policy > was *already* "important severity or higher" a month ago, so it wasn't > an option then either. > >> What seems more feasible to me, is that we provide a newer version via >> backports, which will already include that functionality. > > Sounds reasonable to me. Ok, closing the bug report then. Michael -- 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 --- End Message --- ___ 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#771980: systemd: /var/run/log/journal is not readable by the adm group
controle: retitle -1 systemd: /run/log/journal is not readable by the adm group Am 04.12.2014 um 14:00 schrieb Felipe Sateler: > > I'm sorry I was unclear. The instructions in README.Debian are > perfectly fine. The problem is when persistent logging is not enabled, > as /run/log/journal does not have the adm ACL set. Ok, so it's about /run/log/journal. Retitling the bug report accordingly. -- 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#770734: systemd: FTBFS in environment with all packages rebuilt locally
Hi Daniel, Am 23.11.2014 um 19:02 schrieb Daniel Schepler: > I can't reproduce this with a vanilla pbuilder setup, so I'm not sure what's > causing the difference between the two builds. Can you provide any steps how we can reproduce the issue? Does this problem happen with a fresh checkout of the sources, i.e. when you run "apt-get source -b systemd"? -- 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#775437: systemd: systemctl reboot just shuts down under OpenVZ (kernel 2.6.32-042stab093.4)
Hi Daniel, Am 15.01.2015 um 18:53 schrieb Daniel Edwards: > > I am running a Debian Wheezy system in a OpenVZ container and found that > systemd just shuts down when "systemctl reboot" is run. The container then > has to be started again via the control panel. A OpenVZ developer had posted > a patch to the systemd-devel mailinglist in August 2012 but the systemd > version in wheezy iss too old to include the patch. This is the post: > > > http://lists.freedesktop.org/archives/systemd-devel/2012-August/006379.html > > I have applied the patch to the sources of the systemd debian package and > attached the diff to this report. The problem seems to be that OpenVZ needs > the reboot systemcall to be issued in the container to reboot. Version 44-11 > just exits inside of a container. > > It would be great if the package in wheezy could be fixed, as the systemd > version from wheezy-backports (204) is not compatible with the OpenVZ kernel > (systemd 204 needs a kernel >= 2.6.39 and OVZ only has kernels up to 2.6.32). > It is unfortunately not possible to use SysVInit in OVZ, because this hangs > when init starts up. Please ask the stable release managers, if they would accept such a patch. I don't think we really support such inofficial kernels or mixing squeeze kernels with wheezy userland. So I'm inclined to reject this bug report, especially since the Debian kernel maintainers decided to drop OpenVZ support for the Debian kernel. Michael -- 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#775437: systemd: systemctl reboot just shuts down under OpenVZ (kernel 2.6.32-042stab093.4)
Am 21.01.2015 um 17:13 schrieb Michael Biebl: > Am 15.01.2015 um 18:53 schrieb Daniel Edwards: >> I am running a Debian Wheezy system in a OpenVZ container and found that >> systemd just shuts down when "systemctl reboot" is run. The container then >> has to be started again via the control panel. A OpenVZ developer had posted >> a patch to the systemd-devel mailinglist in August 2012 but the systemd >> version in wheezy iss too old to include the patch. This is the post: >> >> >> http://lists.freedesktop.org/archives/systemd-devel/2012-August/006379.html It was pointed out to me, that this patch was not accepted upstream. >> It would be great if the package in wheezy could be fixed, as the systemd >> version from wheezy-backports (204) is not compatible with the OpenVZ kernel >> (systemd 204 needs a kernel >= 2.6.39 and OVZ only has kernels up to 2.6.32). >> It is unfortunately not possible to use SysVInit in OVZ, because this hangs >> when init starts up. > > Please ask the stable release managers, if they would accept such a > patch. I don't think we really support such inofficial kernels or mixing > squeeze kernels with wheezy userland. > > So I'm inclined to reject this bug report, especially since the Debian > kernel maintainers decided to drop OpenVZ support for the Debian kernel. Reading the openvz bug report [1], it seems there exists a workaround now in vzctl 4.1. Jessie is shipping a recent enough version, unfortunately, wheezy only has 3.0. You might ask the vzctl maintainers for a backport of the jessie version. Michael [1] https://bugzilla.openvz.org/show_bug.cgi?id=2336#c7 -- 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#775437: systemd: systemctl reboot just shuts down under OpenVZ (kernel 2.6.32-042stab093.4)
Hi Michael, On Wed, Jan 21, 2015 at 06:56:50PM +0100, Michael Biebl wrote: >Am 21.01.2015 um 17:13 schrieb Michael Biebl: >> Am 15.01.2015 um 18:53 schrieb Daniel Edwards: >>> It would be great if the package in wheezy could be fixed, as the systemd >>> version from wheezy-backports (204) is not compatible with the OpenVZ kernel >>> (systemd 204 needs a kernel >= 2.6.39 and OVZ only has kernels up to >>> 2.6.32). >>> It is unfortunately not possible to use SysVInit in OVZ, because this hangs >>> when init starts up. >> >> Please ask the stable release managers, if they would accept such a >> patch. I don't think we really support such inofficial kernels or mixing >> squeeze kernels with wheezy userland. >> >> So I'm inclined to reject this bug report, especially since the Debian >> kernel maintainers decided to drop OpenVZ support for the Debian kernel. I absolutely understand that you don't support third-party kernels or mixing different distributions. >Reading the openvz bug report [1], it seems there exists a workaround >now in vzctl 4.1. Jessie is shipping a recent enough version, >unfortunately, wheezy only has 3.0. You might ask the vzctl maintainers >for a backport of the jessie version. Thank you Michael for your help and your work! I will contact the company running the OVZ host if they can update their systems to use a more recent vzctl. In the meantime I'll just use my own build of systemd or maybe change the hosting company. Daniel ___ 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#760916: brltty interferes with getty autostart
Do either of you know how often systemd-login retries, and how many times it tries before giving up? What we could do is open the vt on demand, and then close it after a timeout of non use. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.com/ ___ 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#760916: brltty interferes with getty autostart
Dave Mielke, le Wed 21 Jan 2015 17:08:00 -0500, a écrit : > Do either of you know how often systemd-login retries, and how many times it > tries before giving up? I don't think it retries. Samuel ___ 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#760916: brltty interferes with getty autostart
There's another case where brltty needs to "see" a vt when it isn't open. For example, a command can be run asynchronously in a free vt via the openvt command. After the command finishes, the output remains on the vt's screen even though the vt itself has been closed. The user needs to still be able to switch to that vt and read it. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.com/ ___ 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#760916: brltty interferes with getty autostart
Dave Mielke, le Wed 21 Jan 2015 18:43:09 -0500, a écrit : > There's another case where brltty needs to "see" a vt when it isn't open. For > example, a command can be run asynchronously in a free vt via the openvt > command. After the command finishes, the output remains on the vt's screen > even > though the vt itself has been closed. The user needs to still be able to > switch > to that vt and read it. Reading is fine, since it's done through /dev/vcsa, which doesn't count in VT_GETSTATE. Samuel ___ 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#760916: brltty interferes with getty autostart
[quoted lines by Samuel Thibault on 2015/01/22 at 00:46 +0100] >Reading is fine, since it's done through /dev/vcsa, which doesn't count >in VT_GETSTATE. Not exactly. The tty device still needs to be opened in order to do things like fetch the Unicode map. It's possible, of course, that things like the Unicode map, the screen font map, the character translation table, etc are common to all vts, in which case they could be fetched from tty1. I'm not familiar enough with the internals to know for sure. I noticed a comment in the source for systemd-logind stating that tty1 is special, so using it would seem to be okay. We still need to be sure that all of what we need for mapping the font positions returned by the vcs devices back to the original characters is common to all ttys so that fetching them from tty1 would be valid for other ttys. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.com/ ___ 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#760916: brltty interferes with getty autostart
Dave Mielke, le Wed 21 Jan 2015 18:56:42 -0500, a écrit : > It's possible, of course, that things like the Unicode map, the screen font > map, the character translation table, etc are common to all vts, They are not :/ Samel ___ 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#775971: systemd-logind is installed on minimal install, but dbus which is required is not.
Package: systemd Version: 215-8 First time reporting a bug to a core package, so I hope I've got everything write. When performing a new installation of Jessie using the current installer, but without selecting anything on the tasksel screen (not even basic system libraries), systemd-logind will error and fail to start on boot. This is a result of dbus having only a priority of recommends. Given how central dbus is to functionality of systemd, I think a prudent option would be to make it a depend. Thanks ___ 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#775971: systemd-logind is installed on minimal install, but dbus which is required is not.
Processing control commands: > forcemerge 769728 -1 Bug #769728 [systemd] Logind does not start properly on freshly installed minimal systems Bug #772700 [systemd] systemd-logind.service fails to start if dbus is missing Bug #775971 [systemd] systemd-logind is installed on minimal install, but dbus which is required is not. Severity set to 'important' from 'normal' Added tag(s) patch. Bug #772700 [systemd] systemd-logind.service fails to start if dbus is missing Merged 769728 772700 775971 -- 769728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769728 772700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772700 775971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775971 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#775971: systemd-logind is installed on minimal install, but dbus which is required is not.
Control: forcemerge 769728 -1 Hey Michael, Michael D [2015-01-22 5:29 +]: > When performing a new installation of Jessie using the current installer, > but without selecting anything on the tasksel screen (not even basic system > libraries), systemd-logind will error and fail to start on boot. This is a > result of dbus having only a priority of recommends. Given how central dbus > is to functionality of systemd, I think a prudent option would be to make > it a depend. This is still under debate, as we don't necessarily want to bring D-BUS into every minimal install. Quite obviously we have to install the "systemd" package for booting, but IMHO it would be better to make that fail quietly instead of adding a D-BUS dep. Duplicating with existing report. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.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#775971: systemd-logind is installed on minimal install, but dbus which is required is not.
Didn't spot that dupe on the bug page, thanks for merging. What exactly does systemd-logind do and why do I get the feeling it isn't the only thing broken by lack of dbus? Roll on kdbus I guess, Michael On Jan 22, 2015 5:32 PM, "Martin Pitt" wrote: > Control: forcemerge 769728 -1 > > Hey Michael, > > Michael D [2015-01-22 5:29 +]: > > When performing a new installation of Jessie using the current installer, > > but without selecting anything on the tasksel screen (not even basic > system > > libraries), systemd-logind will error and fail to start on boot. This is > a > > result of dbus having only a priority of recommends. Given how central > dbus > > is to functionality of systemd, I think a prudent option would be to make > > it a depend. > > This is still under debate, as we don't necessarily want to bring > D-BUS into every minimal install. Quite obviously we have to install > the "systemd" package for booting, but IMHO it would be better to make > that fail quietly instead of adding a D-BUS dep. > > Duplicating with existing report. > > Thanks, > > Martin > > -- > Martin Pitt| http://www.piware.de > Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.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#775971: systemd-logind is installed on minimal install, but dbus which is required is not.
Michael D [2015-01-22 6:36 +]: > What exactly does systemd-logind do See man systemd-logind(8) for a description. It also has some URLs at the bottom for further docs. > and why do I get the feeling it isn't the only thing broken by lack > of dbus? Could be; on a desktop you always want/need it, but D-BUS is rather uncommon in the server world (and a bit frowned upon, too). Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.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#775971: systemd-logind is installed on minimal install, but dbus which is required is not.
> > but D-BUS is rather > uncommon in the server world (and a bit frowned upon, too). I was just trying to figure out why some of my servers have it, and it turns out openjdk-7-jdk depends on the non-headless JRE, which in turn recommends some packages that depend on dbus. I might open a bug for that shortly. Thanks On 22 January 2015 at 18:09, Martin Pitt wrote: > Michael D [2015-01-22 6:36 +]: > > What exactly does systemd-logind do > > See man systemd-logind(8) for a description. It also has some URLs at > the bottom for further docs. > > > and why do I get the feeling it isn't the only thing broken by lack > > of dbus? > > Could be; on a desktop you always want/need it, but D-BUS is rather > uncommon in the server world (and a bit frowned upon, too). > > Martin > -- > Martin Pitt| http://www.piware.de > Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.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
