systemd_217-3_amd64.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 02 Dec 2014 16:53:36 +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: 217-3 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: 771498 771739 Changes: systemd (217-3) experimental; urgency=medium . [ Martin Pitt ] * systemd.bug-script: Really capture stderr of systemd-delta. (Closes: #771498) * boot-and-services autopkgtest: Give test apparmor job some time to actually finish. . [ Didier Roche ] * updated debian/patches/insserv.conf-generator.patch: - if /etc/X11/default-display-manager doesn't match a systemd unit (or doesn't exist), be less agressive about what to mask: we let all sysvinit-only display-manager units enabled to fallback to previous behavior and let them starting. (Closes: #771739) Checksums-Sha1: ab65791e6bb28d194124948f8edfb9154c786473 4103 systemd_217-3.dsc 90f674413b3cc2e049ed669a9c8535809df75312 138460 systemd_217-3.debian.tar.xz eddd3713290a4a63aa720f92d1e5d01848d3dc6f 2898800 systemd_217-3_amd64.deb 43c337780cf81974a182dddb0e4d0bc0b037ef0e 31174 systemd-sysv_217-3_amd64.deb 7456fe898b6ca20b96dc8f479aa3c9ab7d3d01c7 121734 libpam-systemd_217-3_amd64.deb 891c3eec012c6f292a2a522ac183be26291f5b03 85040 libsystemd0_217-3_amd64.deb e3e5f4b59934861ff60c8d8fba6b5b7fe34cb8fa 91792 libsystemd-dev_217-3_amd64.deb fd6e66997a33081c33012435d7e7e425537aec58 44352 libsystemd-login0_217-3_amd64.deb b4858b186b506dcdd057591a6f86430bc61d838c 26788 libsystemd-login-dev_217-3_amd64.deb 81e409b745bf57cc9fba4ad9129d5b94e5b9f0df 33392 libsystemd-daemon0_217-3_amd64.deb 28dd28a79698af2b9015cf90019593b598f5fc92 26794 libsystemd-daemon-dev_217-3_amd64.deb 865635afa3641510f21570d585bfbff08f8a9ceb 69608 libsystemd-journal0_217-3_amd64.deb 4baa765f5cd805d18906c80250e1f39ed4605162 26774 libsystemd-journal-dev_217-3_amd64.deb 4045413c61846b9694bcf6c13aa7beae8264a245 32358 libsystemd-id128-0_217-3_amd64.deb d1f89f2b4b68bbe1ce8f7d4f67e4041f663223c6 26760 libsystemd-id128-dev_217-3_amd64.deb d09d32c6ed203929d2c7ec30895867a498f05588 895602 udev_217-3_amd64.deb 6327d314f0349bcb523cd8d136621f722e7a6d22 51694 libudev1_217-3_amd64.deb 29cbcf8b3696048b8079ae4b0ab641326c127c3e 23084 libudev-dev_217-3_amd64.deb c3c9be7b52b66b66057af889b9ee959f67a2cffe 208874 udev-udeb_217-3_amd64.udeb b392550437298fe0936c1a641819825c3fd11280 25164 libudev1-udeb_217-3_amd64.udeb 0458b1216fe37b3262a0159ba54d991ab2890c3f 37094 libgudev-1.0-0_217-3_amd64.deb b0ce1ea97be61b45ed6dd2599207ac429e91b000 2826 gir1.2-gudev-1.0_217-3_amd64.deb 95fef830f87cedc8a8907101a220e10f00656bad 24474 libgudev-1.0-dev_217-3_amd64.deb bdda623b89b0bd6b4e738b8119bb123f40964eca 56464 python3-systemd_217-3_amd64.deb ddefd0d282f68200b08e39427ef3265d16332f9b 19223466 systemd-dbg_217-3_amd64.deb Checksums-Sha256: f018745cd818751d55b7c5c791bef2515b1b2e6d18559d85760f24f536580330 4103 systemd_217-3.dsc c35f30f66bb2d76f5cf3e27c10ba04f36ffa35babc0c1112b3e3764e32f3809f 138460 systemd_217-3.debian.tar.xz 98308ca9299bdb2458db50e4248c35c807fcc8e078ea27eecb4a07cb9b0e62d0 2898800 systemd_217-3_amd64.deb 983289ccd3f49a2a2fa29a97eca2996732bb4ca81bfc0eb39d8de047d2
Bug#771739: marked as done (could not start nodm with systemd 217-1 or 217-2)
Your message dated Tue, 02 Dec 2014 16:19:59 + with message-id and subject line Bug#771739: fixed in systemd 217-3 has caused the Debian Bug report #771739, regarding could not start nodm with systemd 217-1 or 217-2 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.) -- 771739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 217-2 Severity: grave Could not start nodm with systemd 217-1 or 217-2. --- End Message --- --- Begin Message --- Source: systemd Source-Version: 217-3 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 771...@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: Tue, 02 Dec 2014 16:53:36 +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: 217-3 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: 771498 771739 Changes: systemd (217-3) experimental; urgency=medium . [ Martin Pitt ] * systemd.bug-script: Really capture stderr of systemd-delta. (Closes: #771498) * boot-and-services autopkgtest: Give test apparmor job some time to actually finish. . [ Didier Roche ] * updated debian/patches/insserv.conf-generator.patch: - if /etc/X11/default-display-manager doesn't match a systemd unit (or doesn't exist), be less agressive about what to mask: we let all sysvinit-only display-manager units enabled to fallback to previous behavior and let them starting. (Closes: #771739) Checksums-Sha1: ab65791e6bb28d194124948f8edfb9154c786473 4103 systemd_217-3.dsc 90f674413b3cc2e049ed669a9c8535809df75312 138460 systemd_217-3.debian.tar.xz eddd3713290a4a63aa720f92d1e5d01848d3dc6f 2898800 systemd_217-3_amd64.deb 43c337780cf81974a182dddb0e4d0bc0b037ef0e 31174 systemd-sysv_217-3_amd64.deb 7456fe898b6ca20b96dc8f479aa3c9ab7d3d01c7 121734 libpam-systemd_217-3_amd64.deb 891c3eec012c6f292a2a522ac183be26291f5b03 85040 libsystemd0_217-3_amd64.deb e3e5f4b59934861ff60c8d8fba6b5b7fe34cb8fa 91792 libsystemd-dev_217-3_amd64.deb fd6e66997a33081c33012435d7e7e425537aec58 44352 libsystemd-login0_217-3_amd64.deb b4858b186b506dcdd057591a6f86430bc61d838c 26788 libsys
Bug#771739: could not start nodm with systemd 217-1 or 217-2
Michael Biebl [2014-12-02 14:33 +0100]: > Those are bugs in the lxdm and slim packages and need to be fixed there. That'd be my preference too, TBH, but it was already n'acked by the RT. Maybe we can reopen this, though. > Trying to workaround that in systemd looks like the wrong approach. The whole "configure your default DM" has become horribly complicated in Debian :-( sysvinit and systemd both have their own ways of enabling/disabling services, and on top of that we still have this /etc/X11/default-display-manager thing which potentially collides/disagrees with those, so I don't think there ever is a way to get this right. But with the current situation of having to support multiple inits and multiple DMs, I think that /etc/X11/default-display-manager should be the configuration which trumps systemctl enable/update-rc.d disable/enable, and thus we need some central place to tell how to translate that file to a particular boot sequence. So while the DM packages certainly should be fixed to get a proper unit, that still wouldn't completely fix the problems here -- we still need something to sync /e/X/d-d-m with the init system specific enabling/disabling. So the idea of that generator isn't too bad or only a workaround IMHO. However, it's been shown to be quite complex, so before we land this in jessie I'd like to give it some more maturing in experimental. If it turns out to cause more damage than good, we can rip it out again and say "*sigh* don't do that then", if people try to be too clever with configuring their DMs.. But Michael, I don't want to go over your head here. If you don't like this at all, then let's stop this right away instead of risking more debugging/work on this? 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
Processing of systemd_217-3_amd64.changes
systemd_217-3_amd64.changes uploaded successfully to localhost along with the files: systemd_217-3.dsc systemd_217-3.debian.tar.xz systemd_217-3_amd64.deb systemd-sysv_217-3_amd64.deb libpam-systemd_217-3_amd64.deb libsystemd0_217-3_amd64.deb libsystemd-dev_217-3_amd64.deb libsystemd-login0_217-3_amd64.deb libsystemd-login-dev_217-3_amd64.deb libsystemd-daemon0_217-3_amd64.deb libsystemd-daemon-dev_217-3_amd64.deb libsystemd-journal0_217-3_amd64.deb libsystemd-journal-dev_217-3_amd64.deb libsystemd-id128-0_217-3_amd64.deb libsystemd-id128-dev_217-3_amd64.deb udev_217-3_amd64.deb libudev1_217-3_amd64.deb libudev-dev_217-3_amd64.deb udev-udeb_217-3_amd64.udeb libudev1-udeb_217-3_amd64.udeb libgudev-1.0-0_217-3_amd64.deb gir1.2-gudev-1.0_217-3_amd64.deb libgudev-1.0-dev_217-3_amd64.deb python3-systemd_217-3_amd64.deb systemd-dbg_217-3_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
Bug#771830: Fails to execute at all
Package: systemd-cron Version: 1.3.1+ds1-2 Severity: grave Here are relevant lines from output of dmesg-command: [ 21.059257] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 21.520730] systemd[1]: /usr appears to be on its own filesytem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. *[ 21.577570] systemd[123]: Failed to execute /lib/systemd/system-generators/systemd-crontab-generator: No such file or directory *[ 21.578059] systemd[122]: /lib/systemd/system-generators/systemd-crontab-generator failed with error code 1. [ 22.225613] fuse init (API version 7.23) Maybe problem is this: /usr is not mounted when it tries to run that command. That command is actually python script. Its shebang line is this: #!/usr/bin/python Is it really so necessary to run that /lib/systemd/system-generators/systemd-crontab-generator when /usr is not mounted yet? How about running that command by hand after boot?: -=*[ROOT ZSH]*=- root@juhtolv | Tue 02 Dec 2014 19:43:37 | 8404 | pts/1.1 /root # /lib/systemd/system-generators/systemd-crontab-generator Traceback (most recent call last): File "/lib/systemd/system-generators/systemd-crontab-generator", line 19, in TARGER_DIR = sys.argv[1] IndexError: list index out of range [1]6032 exit 1 /lib/systemd/system-generators/systemd-crontab-generator -=*[ROOT ZSH]*=- root@juhtolv | Tue 02 Dec 2014 19:43:59 | 8405 | pts/1.1 /root # /lib/systemd/system-generators/systemd-crontab-generator /etc/crontab Traceback (most recent call last): File "/lib/systemd/system-generators/systemd-crontab-generator", line 32, in os.makedirs(TIMERS_DIR) File "/usr/lib/python2.7/os.py", line 157, in makedirs mkdir(name, mode) OSError: [Errno 20] Not a directory: '/etc/crontab/cron.target.wants' [1]6094 exit 1 /lib/systemd/system-generators/systemd-crontab-generator /etc/crontab Is that command really so stupid, that it only accepts folders and not files? If so, why /etc/crontab is menationed in FILES-section of man page of systemd-crontab-generator ? -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-cron depends on: ii init-system-helpers 1.22 ii python 2.7.8-2 pn python:any ii systemd-sysv 215-6 systemd-cron recommends no packages. systemd-cron suggests no packages. -- Configuration Files: /etc/crontab changed: SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin @reboot /usr/bin/screen -wipe > /dev/null 2>&1 ; /usr/bin/screen -U -d -m 01 04 * * * /root/scripts/emptypartial.sh 01 05 * * * /root/scripts/emptypartial.sh 01 06 * * * /root/scripts/emptypartial.sh 01 07 * * * /root/scripts/emptypartial.sh 01 12 * * * /root/scripts/emptypartial.sh 01 01 * * 1 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 1 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 2 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 2 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 3 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 3 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 4 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 4 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 5 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 5 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 6 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 6 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch 01 01 * * 7 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup.sh' | batch 01 02 * * 7 /bin/echo '/usr/bin/time -v /usr/bin/nice -n 20 /usr/local/sbin/juhtolv-backup2.sh' | batch -- no debconf information -- Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv "Quidquid Latine dictum sit altum videtur."
Bug#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 02/12/2014 09:32, Didier Roche wrote: Ok, everything looks fine. I doubt about the /usr separation to be the cause for that one as the generator doesn't use any file there. Last try before sending you a debug binary: cat -e /etc/X11/default-display-manager (even if I treat trailing spaces, \n and so on, let's see…) and: ls -l /etc/systemd/system/ ls -l /run/systemd/generator* Find attached. Note you don't see the command only the result. Tell me if you want something else/more --eric /usr/bin/kdm$ total 28 lrwxrwxrwx 1 root root 40 déc. 8 2013 dbus-org.freedesktop.Avahi.service -> /lib/systemd/system/avahi-daemon.service drwxr-xr-x 2 root root 4096 août 25 08:57 getty.target.wants drwxr-xr-x 2 root root 4096 mars 20 2014 local-fs.target.wants drwxr-xr-x 2 root root 4096 nov. 17 19:27 multi-user.target.wants drwxr-xr-x 2 root root 4096 nov. 9 11:03 paths.target.wants drwxr-xr-x 2 root root 4096 févr. 25 2014 printer.target.wants drwxr-xr-x 2 root root 4096 oct. 18 10:29 shutdown.target.wants drwxr-xr-x 2 root root 4096 août 29 17:21 sockets.target.wants lrwxrwxrwx 1 root root 31 mars 6 2014 sshd.service -> /lib/systemd/system/ssh.service lrwxrwxrwx 1 root root 35 juin 28 2013 syslog.service -> /lib/systemd/system/rsyslog.service /run/systemd/generator: total 52 -rw-r--r-- 1 root root 220 déc. 2 18:52 dev-disk-by\x2duuid-b27f8ff4\x2dab80\x2d459b\x2dadc4\x2df4b3aae3ad0f.swap -rw-r--r-- 1 root root 388 déc. 2 18:52 home.mount -rw-r--r-- 1 root root 376 déc. 2 18:52 home-valette-local.mount drwxr-xr-x 2 root root 60 déc. 2 18:52 hwclock.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 kdm.service.d drwxr-xr-x 2 root root 200 déc. 2 18:52 local-fs.target.requires drwxr-xr-x 2 root root 60 déc. 2 18:52 local-fs.target.wants -rw-r--r-- 1 root root 236 déc. 2 18:52 media-backup.mount -rw-r--r-- 1 root root 221 déc. 2 18:52 media-cdrom0.mount -rw-r--r-- 1 root root 268 déc. 2 18:52 -.mount drwxr-xr-x 2 root root 60 déc. 2 18:52 mountall-bootclean.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 mountall.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 mountnfs-bootclean.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 mountnfs.service.d -rw-r--r-- 1 root root 289 déc. 2 18:52 multimedia.mount drwxr-xr-x 2 root root 60 déc. 2 18:52 multi-user.target.wants drwxr-xr-x 2 root root 60 déc. 2 18:52 networking.service.d drwxr-xr-x 2 root root 40 déc. 2 18:52 openvpn.service.wants drwxr-xr-x 2 root root 60 déc. 2 18:52 remote-fs.target.d drwxr-xr-x 2 root root 60 déc. 2 18:52 rpcbind.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 rpcbind.target.d drwxr-xr-x 2 root root 60 déc. 2 18:52 sendsigs.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 swap.target.wants drwxr-xr-x 2 root root 60 déc. 2 18:52 umountfs.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 umountnfs.service.d -rw-r--r-- 1 root root 408 déc. 2 18:52 usr-local.mount -rw-r--r-- 1 root root 384 déc. 2 18:52 usr.mount -rw-r--r-- 1 root root 408 déc. 2 18:52 var-cache.mount -rw-r--r-- 1 root root 384 déc. 2 18:52 var.mount -rw-r--r-- 1 root root 273 déc. 2 18:52 windowsData.mount -rw-r--r-- 1 root root 268 déc. 2 18:52 windows.mount drwxr-xr-x 2 root root 80 déc. 2 18:52 x-display-manager.target.d drwxr-xr-x 2 root root 60 déc. 2 18:52 xdm.service.d drwxr-xr-x 2 root root 80 déc. 2 18:52 x-font-server.target.d drwxr-xr-x 2 root root 60 déc. 2 18:52 xfs.service.d drwxr-xr-x 2 root root 60 déc. 2 18:52 xfstt.service.d /run/systemd/generator.early: total 0 lrwxrwxrwx 1 root root 9 déc. 2 18:52 kdm.service -> /dev/null lrwxrwxrwx 1 root root 9 déc. 2 18:52 xdm.service -> /dev/null /run/systemd/generator.late: total 180 -rw-r--r-- 1 root root 632 déc. 2 18:52 apache2.service -rw-r--r-- 1 root root 447 déc. 2 18:52 console-screen.service -rw-r--r-- 1 root root 510 déc. 2 18:52 console-setup.service -rw-r--r-- 1 root root 525 déc. 2 18:52 cpufrequtils.service -rw-r--r-- 1 root root 483 déc. 2 18:52 etc-setserial.service -rw-r--r-- 1 root root 725 déc. 2 18:52 exim4.service -rw-r--r-- 1 root root 532 déc. 2 18:52 gdomap.service -rw-r--r-- 1 root root 500 déc. 2 18:52 gpm.service -rw-r--r-- 1 root root 456 déc. 2 18:52 hdparm.service -rw-r--r-- 1 root root 389 déc. 2 18:52 kbd.service -rw-r--r-- 1 root root 601 déc. 2 18:52 kdm.service -rw-r--r-- 1 root root 531 déc. 2 18:52 keyboard-setup.service -rw-r--r-- 1 root root 446 déc. 2 18:52 keymap.service -rw-r--r-- 1 root root 537 déc. 2 18:52 lirc.service -rw-r--r-- 1 root root 514 déc. 2 18:52 loadcpufreq.service -rw-r--r-- 1 root root 503 déc. 2 18:52 lpd.service -rw-r--r-- 1 root root 449 déc. 2 18:52 minidlna.dpkg-dist.service -rw-r--r-- 1 root root 636 déc. 2 18:52 mysql.service -rw-r--r-- 1 root root 538 déc. 2 18:52 networking.service -rw-r--r-- 1 root root 497 déc. 2 18:52 nfs-common.service -rw-r--r-- 1 root root 633 déc. 2 18:52 nf
Processed: Re: Bug#771830: Fails to execute at all
Processing control commands: > tag -1 + wontfix Bug #771830 [systemd-cron] Fails to execute at all Added tag(s) wontfix. > severity -1 normal Bug #771830 [systemd-cron] Fails to execute at all Severity set to 'normal' from 'grave' -- 771830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771830 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#771830: Fails to execute at all
control: tag -1 + wontfix control: severity -1 normal Hi, The generator must follow a special set of rules defined here: http://www.freedesktop.org/wiki/Software/systemd/Generators/ One of those is that they are the first thing run by systemd; even before /usr is mounted. This can't be changed. By runnning, you can see the generator as the blue spot: $ systemd-analyze plot > /tmp/boot.svg $ xdg-open /tmp/boot.svg One workaround to your problem would be to replace /lib/systemd/system-generators/systemd-crontab-generator by a shell script that calls the real generator (move it to /lib/systemd/systemd-cron/ ) only if /usr is mounted and python avaible + do a systemctl daemon-reload && systemctl restart cron.target in /etc/rc.local I could even publish this script in our 'contrib' folder https://github.com/systemd-cron/systemd-cron/tree/master/contrib but wouldn't made it the default. > [ 21.520730] systemd[1]: /usr appears to be on its own filesytem > and is not already mounted. This is not a supported setup. systemd warned you :-| > /usr is not mounted when it tries to run that command. That command is > actually python script. Its shebang line is this: > > #!/usr/bin/python > > Is it really so necessary to run that > /lib/systemd/system-generators/systemd-crontab-generator when /usr is > not mounted yet? The first run is unconditional; the generator schedules a second run of itself if /var is a separate partition (I use this setup). > How about running that command by hand after boot?: This should never run by hand; It should allways be called by systemctl daemon-reload Alexandre Detiste ___ 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#771830: Fails to execute at all
>[ 21.520730] systemd[1]: /usr appears to be on its own filesytem > and is not already mounted. This is not a supported setup. You could maybe also mount /usr in your initramfs, before systemd is started. ___ 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#754218: boot hangs forever on LSB job "raise network interfaces"
On 2014-12-01 16:32, Michael Biebl wrote: Does the system itself boot correctly? Yes. How does your /etc/network/interfaces look like? Default configuration. Like Stefano Zacchiroli's, without last two IPv6 lines: https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=interfaces;att=1;bug=754218 After reading further explanations, I understand this workaround for broken software is unpleasant but necessary for Jessie release. ___ 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#771795: systemd keep starting a service disabled with "disable" and even "mask"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/12/2014 15:11, Michael Biebl wrote: > Am 02.12.2014 um 14:58 schrieb Vincent Danjean: >> If you need more information, please ask. > > wicd seems to ship SysV init script only. I assume you haven't created your > own native wicd.service file in /etc/systemd/system? No, I did not create any service file for now. > What's the output of systemctl status wicd.service currently : root@eyak:/home/vdanjean# systemctl status wicd.service ● wicd.service Loaded: masked (/dev/null) Active: inactive (dead) > and > > ls -la /etc/rc?.d/???wicd root@eyak:/home/vdanjean# ls -la /etc/rc?.d/???wicd lrwxrwxrwx 1 root root 14 nov. 23 2011 /etc/rc0.d/K01wicd -> ../init.d/wicd lrwxrwxrwx 1 root root 14 nov. 23 2011 /etc/rc1.d/K01wicd -> ../init.d/wicd lrwxrwxrwx 1 root root 14 nov. 23 16:34 /etc/rc2.d/K01wicd -> ../init.d/wicd lrwxrwxrwx 1 root root 14 nov. 23 16:34 /etc/rc3.d/K01wicd -> ../init.d/wicd lrwxrwxrwx 1 root root 14 nov. 23 16:34 /etc/rc4.d/K01wicd -> ../init.d/wicd lrwxrwxrwx 1 root root 14 nov. 23 16:34 /etc/rc5.d/K01wicd -> ../init.d/wicd lrwxrwxrwx 1 root root 14 nov. 23 2011 /etc/rc6.d/K01wicd -> ../init.d/wicd > The systemd-analyze dump which is attached to this bug report doesn't contain > any information about wicd, so I assume you filed the bug report on a > different machine. No, it was done on the same machine. And I did not remove anything in the generated reportbug template. Regards, Vincent PS: I will upgrade to the lattest systemd version in experimental to see if it fixes my problem. - -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVH46hJZH3mN+x7dRAQh8HQ//eLtuO2at+csdzT4lmvPd02DHL1kIeCL5 f8Q8+3EjKrRo0A4Ux86MdeZJicUxP901Xj4EFXK2+3SuXgLXIzxfRxgwf1Ovjggr iSL8SwcqzfeenKr/v/+ZRVI4SNUqvxNNki7+4SBPmInJxRqa45U1IDFvFI286aoQ r0VuPMPTeB+Coh8SL+Cd6Ihmyk43kyONZAejFCEDawgx9sxsZbjcBV1NX0qPzEpt xbBdCGrnR3bqHjAUjY/P9+o1LaljiFepaMTkRc6u05cJQj50UyINm8Ik+mmX5L0q r4JA7xrFx8elLDp6cu3prMFM2xGUZ7xV0XTQPbFJ8hzxIuAwEKtYko/U0fs2TWFy jOZmEfxzCFBTfJDxOWLc8RPMajaj2Q/hb8xjazBzjpswOCJ5IpUyvn6I/cGtYLhy Kdlulftm/T6fBGDyeAwleCacuDrqml90O96Cduk6AnwUrwfFjuGXoYTXencTo5/n DwOJoiihMT7y2HVuk6pW4njVlJn5e/Lde4gSQHZD8GXyTtsHEb3H3yf5BJvvK+NQ i4zJUYZgGepzUEw8kvy/N9qh/WMmbU7+4E4EKapUHiZDtDCfAgIDQskEWYpUpGVA mo4c0sBM82KC9e8D2Y7tJ8SYbhPH5oAUIK5N1lLLrxYtBbAuQMROMnuq5oN8G8rk GlMHfhBuI4U= =iJ3c -END PGP SIGNATURE- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: retitle 771830 to generator doesn't find python at boot if /usr is a separate mount
Processing commands for cont...@bugs.debian.org: > retitle 771830 generator doesn't find python at boot if /usr is a separate > mount Bug #771830 [systemd-cron] Fails to execute at all Changed Bug title to 'generator doesn't find python at boot if /usr is a separate mount' from 'Fails to execute at all' > thanks Stopping processing here. Please contact me if you need assistance. -- 771830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771830 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
Le 02/12/2014 19:03, Eric Valette a écrit : On 02/12/2014 09:32, Didier Roche wrote: Ok, everything looks fine. I doubt about the /usr separation to be the cause for that one as the generator doesn't use any file there. Last try before sending you a debug binary: cat -e /etc/X11/default-display-manager (even if I treat trailing spaces, \n and so on, let's see…) and: ls -l /etc/systemd/system/ ls -l /run/systemd/generator* Find attached. Note you don't see the command only the result. Tell me if you want something else/more Thanks a lot! Ok, I'm unsure why you have lrwxrwxrwx 1 root root 9 déc. 2 18:52 kdm.service -> /dev/null in generator.early where your kdm binary matches in /etc/X11/default-display-manager, this is weird. However, I've committed a patch with 217-3 which incidentally will fix as well your issue (which is basically "don't touch if the default dm != systemd native services". Keep me posted once you download that one which should land shortly in experimental. Cheers, Didier ___ 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 03/12/2014 07:41, Didier Roche wrote: However, I've committed a patch with 217-3 which incidentally will fix as well your issue (which is basically "don't touch if the default dm != systemd native services". Keep me posted once you download that one which should land shortly in experimental. Confirmed fixed. Thanks for your time and work. --eric ___ 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
Control: close -1 Control: forcemerge 771739 -1 Eric Valette [2014-12-03 8:40 +0100]: > Confirmed fixed. Thanks for your time and work. Thanks for confirming! Duplicating to #771739 then. 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
Processing control commands:
> close -1
Bug #771653 [systemd] systemd 217 breaks X11 (not more kdm and loggin and using
startx gives me no mouse)
Marked Bug as done
> forcemerge 771739 -1
Bug #771739 {Done: Martin Pitt } [systemd] could not start
nodm with systemd 217-1 or 217-2
Bug #771653 {Done: Martin Pitt } [systemd] systemd 217 breaks
X11 (not more kdm and loggin and using startx gives me no mouse)
Severity set to 'grave' from 'important'
Marked as fixed in versions systemd/217-3.
Marked as found in versions systemd/217-2.
Bug #771739 {Done: Martin Pitt } [systemd] could not start
nodm with systemd 217-1 or 217-2
Marked as found in versions systemd/217-1.
Added tag(s) moreinfo.
Merged 771653 771739
--
771653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771653
771739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771739
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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 02/12/2014 08:55, Didier Roche wrote: This isn't the logs we asked for though to debug your issue. Can you paste them please? (after running as root): systemctl status kdm.service systemctl status display-manager.service Here they are (making them from console :-() -- eric ● kdm.service Loaded: masked (/dev/null) Active: inactive (dead) Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended. ● display-manager.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) ___ 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 02/12/2014 09:01, Eric Valette wrote: On 02/12/2014 08:55, Didier Roche wrote: This isn't the logs we asked for though to debug your issue. Can you paste them please? (after running as root): systemctl status kdm.service systemctl status display-manager.service Here they are (making them from console :-() -- eric The reload message seems to imply that the kdm.service is generated too late for the system (my system is high end quadri core (8 cpus) I7 16G RAM, fast ssd). For the display-manager.service not found, I have no clue except if you gave me a wrong name. -- eric ___ 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
Le 02/12/2014 09:01, Eric Valette a écrit : On 02/12/2014 08:55, Didier Roche wrote: This isn't the logs we asked for though to debug your issue. Can you paste them please? (after running as root): systemctl status kdm.service systemctl status display-manager.service Here they are (making them from console :-() -- eric Thanks! Are you really sure that /etc/X11/default-display-manager exists on this machine (you didn't paste from any other) and points to a kdm binary? If so, do you mind if I give you a debug version of a binary (you can revert to previous systemd meanwhile), so that I can get the needed informations to know what happens (I would need to know your machine architecture then). Cheers, Didier ___ 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 02/12/2014 09:13, Didier Roche wrote: anks! Are you really sure that /etc/X11/default-display-manager exists on this machine (you didn't paste from any other) and points to a kdm binary? Yes. Double checked! cat /etc/X11/default-display-manager /usr/bin/kdm valette@tri-yann4:~$ type /usr/bin/kdm /usr/bin/kdm est /usr/bin/kdm valette@tri-yann4:~$ file /usr/bin/kdm /usr/bin/kdm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=e0e10507ede6d64eab115388829af4e23f8938c5, stripped If so, do you mind if I give you a debug version of a binary (you can revert to previous systemd meanwhile), so that I can get the needed informations to know what happens (I would need to know your machine architecture then). Note that /usr is not mounted at the beginning of the boot for me (no initrd, and / and /usr on a diffrent file system) -- eric ___ 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
Le 02/12/2014 09:13, Eric Valette a écrit : On 02/12/2014 09:01, Eric Valette wrote: On 02/12/2014 08:55, Didier Roche wrote: This isn't the logs we asked for though to debug your issue. Can you paste them please? (after running as root): systemctl status kdm.service systemctl status display-manager.service Here they are (making them from console :-() -- eric The reload message seems to imply that the kdm.service is generated too late for the system (my system is high end quadri core (8 cpus) I7 16G RAM, fast ssd). There is a bug in systemd when pointing in generators to mask an unit, but it's just a cosmetic one (the proof is that the unit isn't started and you don't have kdm ;)) For the display-manager.service not found, I have no clue except if you gave me a wrong name. No, that's expected in your case. I guess you don't have a display-manager like gdm, lightdm, and so on… which have a systemd unit file. ___ 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
Le 02/12/2014 09:17, Eric Valette a écrit : On 02/12/2014 09:13, Didier Roche wrote: anks! Are you really sure that /etc/X11/default-display-manager exists on this machine (you didn't paste from any other) and points to a kdm binary? Yes. Double checked! cat /etc/X11/default-display-manager /usr/bin/kdm valette@tri-yann4:~$ type /usr/bin/kdm /usr/bin/kdm est /usr/bin/kdm valette@tri-yann4:~$ file /usr/bin/kdm /usr/bin/kdm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=e0e10507ede6d64eab115388829af4e23f8938c5, stripped Ok, everything looks fine. I doubt about the /usr separation to be the cause for that one as the generator doesn't use any file there. Last try before sending you a debug binary: cat -e /etc/X11/default-display-manager (even if I treat trailing spaces, \n and so on, let's see…) and: ls -l /etc/systemd/system/ ls -l /run/systemd/generator* Didier ___ 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#771653: systemd 217 breaks X11 (not more kdm and loggin and using startx gives me no mouse)
On 12/02/2014 09:32 AM, Didier Roche wrote: > Ok, everything looks fine. I doubt about the /usr separation to be the > cause for that one as the generator doesn't use any file there. > > Last try before sending you a debug binary: > cat -e /etc/X11/default-display-manager > > (even if I treat trailing spaces, \n and so on, let's see…) > > and: > ls -l /etc/systemd/system/ > ls -l /run/systemd/generator* Will do but must wait until I'm back home. -- eric ___ 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: notfound 771739 in 215-7
Processing commands for cont...@bugs.debian.org: > notfound 771739 215-7 Bug #771739 [systemd] could not start nodm with systemd 217-1 or 217-2 Ignoring request to alter found versions of bug #771739 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 771739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771739 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#771726: systemd: Needs kmod that has static-nodes command
Am 01.12.2014 um 23:10 schrieb Felipe Sateler:
>> I'm interested how you managed to install kmod < 14, given that udev has
>> a Breaks: kmod < 14.
>
> Turns out udev was not upgraded alongside systemd:
>
> % apt-cache policy udev
> udev:
> Installed: 175-7.2
> Candidate: 175-7.2
> Version table:
> 215-6 0
> 200 http://http.debian.net/debian/ jessie/main i386 Packages
> 204-14~bpo70+1 0
> 300 http://http.debian.net/debian/ wheezy-backports/main i386 Packages
> *** 175-7.2 0
> 990 http://http.debian.net/debian/ wheezy/main i386 Packages
> 100 /var/lib/dpkg/status
>
>
> The Depends from systemd to udev is not versioned. Maybe it should be?
I guess we should, yes. All the relevant bits regarding kmod landed in
systemd/udev 208-8, so we could make systemd Depends: udev (>= 208-8).
We already have a Breaks: systemd (<< 208) in udev to avoid a partial
upgrade in the other direction.
An alternative would be, to have systemd depend on udev which is
strictly versioned like Depends: udev (= ${binary:Version}) or
udev (>= ${source:Version}).
Sometimes it's quite helpful though, being able to test combinations of
udev and systemd with different versions. So not having it strictly
versioned could be useful for debugging.
Marco, any preference?
--
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#771739: could not start nodm with systemd 217-1 or 217-2
Am 02.12.2014 um 06:48 schrieb Martin Pitt: > 積丹尼 Dan Jacobson [2014-12-02 13:36 +0800]: >> # cat /etc/X11/default-display-manager >> cat: /etc/X11/default-display-manager: No such file or directory > > Indeed, nodm doesn't use this file at all, nor does it conflict with > any other window manager. So installing nodm together with gdm, > lightdm, kdm, etc. will just result in a disaster :-( > > Didier, I'm afraid we have to exclude nodm from your DM masking -- I > don't see a way how we can fix this without actually fixing nodm. I'm not sure if the generator is a good idea. I played around with that idea a long time ago but discarded it again. It also changes the behaviour of the insserv generator, which no longer generates dependencies if native units exist. At the current stage, I don't think these patches should be merged as is for master. Didier, Martin: could you elaborate what those patches try to fix? -- 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#771739: could not start nodm with systemd 217-1 or 217-2
Le 02/12/2014 12:28, Michael Biebl a écrit : Am 02.12.2014 um 06:48 schrieb Martin Pitt: 積丹尼 Dan Jacobson [2014-12-02 13:36 +0800]: # cat /etc/X11/default-display-manager cat: /etc/X11/default-display-manager: No such file or directory Indeed, nodm doesn't use this file at all, nor does it conflict with any other window manager. So installing nodm together with gdm, lightdm, kdm, etc. will just result in a disaster :-( Didier, I'm afraid we have to exclude nodm from your DM masking -- I don't see a way how we can fix this without actually fixing nodm. I'm not sure if the generator is a good idea. I played around with that idea a long time ago but discarded it again. It seems the way Lennart advertised the use of a default configuration (like in /e/X/d-d-m) keeping in sync with Aliases like display-manager.service. It also changes the behaviour of the insserv generator, which no longer generates dependencies if native units exist. systemd does that itself as well anyway (I didn't put that on the overriding stack on purpose). I can condition that masking for display-manager only if you feel more comfortable that way. Note that this patch modification is for jessie-only and should be removed as being useless as soon as all dms ship systemd units. At the current stage, I don't think these patches should be merged as is for master. Didier, Martin: could you elaborate what those patches try to fix? This is to fix multiple bug reports where people don't have (or have multiple) dm services starting. Also, it enables people changing manually /e/X/d-d-m to not reboot in a state where no dm is started. The use case is to ensure that display-manager.service will always points to a systemd service that will be runnable (if any). Meaning that we won't have failing units due to ExecStartPre failing and having that shell execution, or disable them if there is an init dm matching. It's going to enable us as well to migrate to Alias=display-manager.service one dm service after another instead in jessie+1 than doing the transition in a batch. Precise behavior in coordination to the 2 generators is: - if /etc/X11/default-display-manager matches a systemd unit and matches display-manager.service: -> noop on the systemd side, mask all dms sysvinit not matching a systemd unit - if /etc/X11/default-display-manager matches systemd unit and but doesn't match what's pointed by display-manager.service: -> we ensure display-manager.service transiantly points to correct systemd unit, we mask all dms sysvinit not matching a systemd unit - if /etc/X11/default-display-manager matches a non systemd unit: -> we transiently mask display-manager.service (so no systemd unit startup) and mask all sysvinit dm scripts, but the one matching /etc/X11/default-display-manager - if no /etc/X11/default-display-manager: -> we even don't look at the systemd side (we hope there will be one display-manager.service matching at least one), we mask all sysvinit dm scripts The last case is what is at fault here. I would suggest that we change the patch: - if /etc/X11/default-display-manager matches anything at all or doesn't exist, we avoid masking any sysvinit dm script if there is no display-manager.service matching a real service file. Didier ___ 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#771739: could not start nodm with systemd 217-1 or 217-2
Am 02.12.2014 um 13:06 schrieb Didier Roche: > This is to fix multiple bug reports where people don't have (or have > multiple) dm services starting. Can you provide links to such bug reports so we have a bit of a context? -- 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#771739: could not start nodm with systemd 217-1 or 217-2
Le 02/12/2014 13:44, Michael Biebl a écrit : Am 02.12.2014 um 13:06 schrieb Didier Roche: This is to fix multiple bug reports where people don't have (or have multiple) dm services starting. Can you provide links to such bug reports so we have a bit of a context? Sure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748668 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770404 in particular. Those generators will enable in jessie+1 to implement something like in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764607 without needing all DM to transition to this scheme. ___ 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#771739: could not start nodm with systemd 217-1 or 217-2
Am 02.12.2014 um 14:17 schrieb Didier Roche: > Le 02/12/2014 13:44, Michael Biebl a écrit : >> Am 02.12.2014 um 13:06 schrieb Didier Roche: >>> This is to fix multiple bug reports where people don't have (or have >>> multiple) dm services starting. >> Can you provide links to such bug reports so we have a bit of a context? >> > Sure: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748668 > and > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770404 > in particular. Those are bugs in the lxdm and slim packages and need to be fixed there. Trying to workaround that in systemd looks like the wrong approach. > Those generators will enable in jessie+1 to implement something like in > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764607 without needing > all DM to transition to this scheme. What exactly do you mean with "this scheme"? Are you referring to having native .service files ship an Alias=display-manager.service in their [Install] section? -- 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#771739: could not start nodm with systemd 217-1 or 217-2
Le 02/12/2014 14:33, Michael Biebl a écrit : Am 02.12.2014 um 14:17 schrieb Didier Roche: Le 02/12/2014 13:44, Michael Biebl a écrit : Am 02.12.2014 um 13:06 schrieb Didier Roche: This is to fix multiple bug reports where people don't have (or have multiple) dm services starting. Can you provide links to such bug reports so we have a bit of a context? Sure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748668 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770404 in particular. Those are bugs in the lxdm and slim packages and need to be fixed there. Trying to workaround that in systemd looks like the wrong approach. Hence my first patch about it, however, bigon asked the release team which nacked doing this for jessie. That's why I'm telling this patch is intended to be a bandaid until we get there. Those generators will enable in jessie+1 to implement something like in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764607 without needing all DM to transition to this scheme. What exactly do you mean with "this scheme"? Are you referring to having native .service files ship an Alias=display-manager.service in their [Install] section? Exactly, as intended upstream and done in other distributions. ___ 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#771795: systemd keep starting a service disabled with "disable" and even "mask"
Am 02.12.2014 um 14:58 schrieb Vincent Danjean: > Package: systemd > Version: 215-6 > Severity: important > > On my laptop, I've both network-manager and wicd installed. > I know that both cannot be used at the same time. I've both installed > because, in one environment (in the house of my parents), network-manager > does not succeed to keep the network (whereas it is a simple WEP), so I must > use wicd. That said, on every other environment, I use only network-manager. > > So, I do want wicd installed (to start it manually when I need it) but I do > not want to have it started at boot time. > My problem is that, dispite trying to apply all information I found about > disabling the start of a service, I did not succeeded since systemd is used. > In particular, I tried > sudo systemctl disable wicd > sudo systemctl mask wicd > but that is not enough (wicd still start at boot time). > > I've no idea (nothing found in the doc for now) what to do. I do not even > know why the service is started, by whom and how to find these informations. > > Of course, booting with init=/bin/bash and manually starting /etc/init.d/* > scripts does not work any more with systemd... > > If you need more information, please ask. wicd seems to ship SysV init script only. I assume you haven't created your own native wicd.service file in /etc/systemd/system? What's the output of systemctl status wicd.service and ls -la /etc/rc?.d/???wicd The systemd-analyze dump which is attached to this bug report doesn't contain any information about wicd, so I assume you filed the bug report on a different machine. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: tagging 771739
Processing commands for cont...@bugs.debian.org: > tags 771739 + pending Bug #771739 [systemd] could not start nodm with systemd 217-1 or 217-2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 771739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771739 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
pkg-systemd-maintainers@lists.alioth.debian.org
Your message dated Tue, 02 Dec 2014 16:19:59 + with message-id and subject line Bug#771498: fixed in systemd 217-3 has caused the Debian Bug report #771498, regarding systemd: please sprinkle debian/systemd.bug-script with "2>&1"s 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.) -- 771498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 217-1 Severity: minor Dear Maintainer, This is split from 771397 for clarity. This was an upstream bug, this is a Debian bug. Please add some "2>&1" in debian/systemd.bug-script. I had systemd-delta failing and the stderr was not in reportbug report. (twice) -systemd-delta --no-pager|sed "s%\x1b[^m]*m%%g" >$DIR/systemd-delta.txt +systemd-delta --no-pager 2>&1|sed "s%\x1b[^m]*m%%g" >$DIR/systemd- delta.txt (twice) -systemd-analyze --no-pager dump >$DIR/systemd-analyze-dump.txt +systemd-analyze --no-pager dump >$DIR/systemd-analyze-dump.txt 2>&1 I guess you could have a look at udev.bug-script too. Alexandre Detiste -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash 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 libapparmor12.9.0-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.2-3 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libgcrypt20 1.6.2-4 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b2 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 217-1 ii mount 2.25.2-3 ii sysv-rc 2.88dsf-58 ii udev217-1 ii util-linux 2.25.2-3 Versions of packages systemd recommends: ii dbus1.8.12-1 ii libpam-systemd 217-1 Versions of packages systemd suggests: pn systemd-ui -- Configuration Files: /etc/systemd/resolved.conf 886b81674c4697d8949d0fba0e21907d [Errno 2] Aucun fichier ou dossier de ce type: u'/etc/systemd/resolved.conf 886b81674c4697d8949d0fba0e21907d' -- no debconf information --- End Message --- --- Begin Message --- Source: systemd Source-Version: 217-3 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 771...@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: Tue, 02 Dec 2014 16:53:36 +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: 217-3 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-
