Processing of systemd_204-14~bpo70+1_amd64.changes
systemd_204-14~bpo70+1_amd64.changes uploaded successfully to localhost along with the files: systemd_204-14~bpo70+1.dsc systemd_204-14~bpo70+1.debian.tar.gz systemd_204-14~bpo70+1_amd64.deb systemd-sysv_204-14~bpo70+1_amd64.deb libpam-systemd_204-14~bpo70+1_amd64.deb libsystemd-login0_204-14~bpo70+1_amd64.deb libsystemd-login-dev_204-14~bpo70+1_amd64.deb libsystemd-daemon0_204-14~bpo70+1_amd64.deb libsystemd-daemon-dev_204-14~bpo70+1_amd64.deb libsystemd-journal0_204-14~bpo70+1_amd64.deb libsystemd-journal-dev_204-14~bpo70+1_amd64.deb libsystemd-id128-0_204-14~bpo70+1_amd64.deb libsystemd-id128-dev_204-14~bpo70+1_amd64.deb udev_204-14~bpo70+1_amd64.deb libudev1_204-14~bpo70+1_amd64.deb libudev-dev_204-14~bpo70+1_amd64.deb udev-udeb_204-14~bpo70+1_amd64.udeb libudev1-udeb_204-14~bpo70+1_amd64.udeb libgudev-1.0-0_204-14~bpo70+1_amd64.deb gir1.2-gudev-1.0_204-14~bpo70+1_amd64.deb libgudev-1.0-dev_204-14~bpo70+1_amd64.deb python-systemd_204-14~bpo70+1_amd64.deb systemd-dbg_204-14~bpo70+1_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#753816: [systemd] Broken audio
El 05/07/14 13:33, Michael Biebl escribió: Am 05.07.2014 14:16, schrieb Antonio Marcos López Alonso: Package: systemd Version: 204-14 Severity: important --- Please enter the report below this line. --- After upgrading to systemd and rebooting, audio has dissappeared from my box. Here are the lines I found in dmesg output: [ 10.812065] cannot find the slot for index 0 (range 0-0), error: -16 [ 10.812119] hda-intel: Error creating card! [ 10.812170] snd_hda_intel: probe of :00:14.2 failed with error -16 [ 10.812193] cannot find the slot for index 0 (range 0-0), error: -16 [ 10.812243] hda-intel: Error creating card! [ 10.812291] snd_hda_intel: probe of :01:00.1 failed with error -16 What kind of hardware do you have? Could you attach your /etc/modules file, please? Sure. Attaching file. # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with # are ignored. # Parameters can be specified after the module name. loop snd-aloop # Generated by sensors-detect on Mon Jun 18 22:30:23 2012 # Chip drivers it87 ___ 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#753816: [systemd] Broken audio
Am 05.07.2014 15:57, schrieb Michael Biebl: Can you also attach the output of grep snd_hda /etc/modprobe.d/* /lib/modprobe.d/* and a complete make that grep snd /etc/modprobe.d/* /lib/modprobe.d/* -- 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#753816: [systemd] Broken audio
Am 05.07.2014 15:47, schrieb Antonio Marcos López Alonso: El 05/07/14 13:33, Michael Biebl escribió: Am 05.07.2014 14:16, schrieb Antonio Marcos López Alonso: Package: systemd Version: 204-14 Severity: important --- Please enter the report below this line. --- After upgrading to systemd and rebooting, audio has dissappeared from my box. Here are the lines I found in dmesg output: [ 10.812065] cannot find the slot for index 0 (range 0-0), error: -16 [ 10.812119] hda-intel: Error creating card! [ 10.812170] snd_hda_intel: probe of :00:14.2 failed with error -16 [ 10.812193] cannot find the slot for index 0 (range 0-0), error: -16 [ 10.812243] hda-intel: Error creating card! [ 10.812291] snd_hda_intel: probe of :01:00.1 failed with error -16 What kind of hardware do you have? Could you attach your /etc/modules file, please? Can you also attach the output of grep snd_hda /etc/modprobe.d/* /lib/modprobe.d/* and a complete journalctl -b log. https://bugzilla.redhat.com/show_bug.cgi?id=229227 suggests there is a race when initializing the sound card. So this might not be a systemd bug per se, just something that is triggered because the timing has changed. 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#753816: [systemd] Broken audio
Am 05.07.2014 16:09, schrieb Antonio Marcos López Alonso: Attaching. grep_snd.log /etc/modprobe.d/alsa-base-blacklist.conf:# blacklist snd-atiixp-modem /etc/modprobe.d/alsa-base-blacklist.conf:# blacklist snd-intel8x0m /etc/modprobe.d/alsa-base-blacklist.conf:# blacklist snd-via82xx-modem /etc/modprobe.d/alsa-base-blacklist.conf:# Comment this entry in order to load snd-pcsp driver /etc/modprobe.d/alsa-base-blacklist.conf:blacklist snd-pcsp /etc/modprobe.d/alsa-base.conf:install sound-slot-0 /sbin/modprobe snd-card-0 /etc/modprobe.d/alsa-base.conf:install sound-slot-1 /sbin/modprobe snd-card-1 /etc/modprobe.d/alsa-base.conf:install sound-slot-2 /sbin/modprobe snd-card-2 For testing purposes, could you (temporarily) move /etc/modprobe.d/alsa-base.conf and /etc/modprobe.d/oss-compat.conf away, run update-initramfs -u and reboot. -- 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#728959: [Pkg-systemd-maintainers] Bug#728959: libsystemd-login0:amd64: logins are delayed for a very long time
Am 07.11.2013 12:08, schrieb Emmanuel Hainry: Package: libsystemd-login0 Version: 204-5 Severity: important Dear Maintainer, Login is taking something like 20 seconds (while the rest of the boot was done after 9 seconds). Looking into dmesg, it does not report anything being done before systemd-login reports the new seat. [9.817328] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx [9.817450] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [9.817505] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 33.275975] systemd-logind[2789]: New seat seat0. [ 33.277445] systemd-logind[2789]: Watching system buttons on /dev/input/event15 (Video Bus) [ 33.277641] systemd-logind[2789]: Watching system buttons on /dev/input/event9 (Power Button) [ 33.277823] systemd-logind[2789]: Watching system buttons on /dev/input/event3 (Lid Switch) [ 33.278009] systemd-logind[2789]: Watching system buttons on /dev/input/event10 (Sleep Button) [ 33.279761] systemd-logind[2789]: New session c1 of user manu. TRying with two differents DMs and without DM got similar results: The above timing is with lightdm. With lightdm, after 9 seconds, black screen appears and only 20 seconds later does the login window appear. With slim, the login screen appears fast but login never ends. Without a dm, loging in in a console goes OK but blocks at the MOTD for a long time before I get a prompt. The bug may not be with systemd-login but I do not know better! Can you send us a full debug log of the boot. For that, add systemd.log_level=debug to the kernel command line and then run journalctl -alb (as root) and attach the output. 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#739721: [Pkg-systemd-maintainers] Bug#739721: Bug#739721: Bug#739721: systemd: NFS shares are not automatically mounted during boot
Am 22.02.2014 00:16, schrieb John Paul Adrian Glaubitz: On 02/22/2014 12:10 AM, Michael Biebl wrote: Just tried again (with two VMs): The NFS server being a wheezy system, the client system is an up-to-date SID system. Worked like a charm. Ok, it seems to be a local configuration issue then. I will try to pin point the problem and hopefully post the reason and solution soon. Any news? -- 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#753816: [systemd] Broken audio
El 05/07/14 17:06, Michael Biebl escribió: Am 05.07.2014 17:56, schrieb Antonio Marcos López Alonso: Just in case, have you noticed I'm using an ALSA-Jack loopback setting for audio? Under sysvinit, udev (including udevadm settle) is started before the kmod init script, which loads snd_aloop. That means, snd_aloop is loaded after snd_hda_intel. Under systemd, it looks like the snd_aloop module is loaded about the same time systemd-udevd is started. There might be a race here and snd_aloop is loaded before snd_hda_intel. This *might* be the reason, but I'm no expert on this matter. Can you try removing snd_aloop from /etc/modules and test if that makes a difference. OK removed snd_aloop and audio is back. Then reloaded the module, restarted JACK and audio is still fine. So as you said there must be some race condition in there. Should I keep this ticket opened? Thanks for your debugging suggestions, Antonio ___ 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#753108: marked as done (dh-systemd does not seem to properly handle services when using --name)
Your message dated Sat, 05 Jul 2014 21:02:11 +0200 with message-id x6ha2v4ojw@midna.zekjur.net and subject line Re: Bug#753108: Fwd: Re: Bug#753108: dh-systemd does not seem to properly handle services when using --name has caused the Debian Bug report #753108, regarding dh-systemd does not seem to properly handle services when using --name 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.) -- 753108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dh-systemd Version: 1.19 Am 29.06.2014 11:49, schrieb Michael Biebl: So quotarpc.service is only supposed to run if rpcbind is installed? I think what you want here then is Wants/After + a Condition [1]. i.e. [Unit] Wants=rpcbind.service After=rpcbind.service ConditionFileIsExecutable=/sbin/rpcbind Btw, I noticed that quotarpc is not enabled by default. Instead dh_systemd creates two sections for quota.service # ls debian/*.service debian/quota.quotarpc.service debian/quota.service # debian/rules dh_systemd_enable dh_systemd_enable --name=quotarpc.service The start section for quotarpc is completely missing. This might be a bug in dh_systemd in how --name= is handled. Michael Stapelberg, could you look into this? 3 Michaels now, I feel like talking to myself :-) Cheers, 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--- ---BeginMessage--- Hi Michael, You used “dh_systemd_enable --name=quotarpc.service”, but I think you are confusing two things here: 1) For deciding which service file dh_systemd_enable should install (like dh_installinit), you should specify --name=quotarpc, i.e. without the .service prefix. This is the handling that is common to debhelper and specifies the per-package files. dh_systemd_enable --name=quotarpc install -p -m644 debian/quota.quotarpc.service debian/quota/lib/systemd/system/quotarpc.service 2) For only generating blocks for specific service files, you need to pass them as arguments: “dh_systemd_enable quota.service” and “dh_systemd_enable --name=quotarpc quotarpc.service”. Likewise for dh_systemd_start. When I use these commands in debian/rules, the package is built correctly for me. Hence, I’m closing this bugreport. Feel free to reopen and explain in detail in case you still have doubts. -- Best regards, Michael---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#674755: systemd should respect settings in /etc/default/tmpfs
Josh Triplett j...@joshtriplett.org writes: On Fri, Jul 04, 2014 at 03:34:50PM +0200, Jens Thiele wrote: i also would expect systemd to respect settings in /etc/default/tmpfs systemd does respect the settings in /etc/default/tmpfs; see the systemd postinst, which explicitly checks those settings and creates corresponding configuration for systemd, as a one-time migration. yes, saw that after commenting on #674755 (After that initial migration, you can edit the resulting systemd configuration further if you want to change it.) i would have expected the settings in /etc/default/tmpfs would be respected afterwards, too In any case, that doesn't relate to bug 674755. don't undertand that one. The default Debian init mounts several tmpfs as indicated by the config file /etc/default/tmpfs: - /run - /run/lock - /run/shm - /tmp I read that like exactly the same expectation? see also man tmpfs ___ 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#753816: [systemd] Broken audio
On Sat, 2014-07-05 at 18:58 +0200, Michael Biebl wrote: Am 05.07.2014 18:38, schrieb Antonio Marcos López Alonso: El 05/07/14 17:06, Michael Biebl escribió: Am 05.07.2014 17:56, schrieb Antonio Marcos López Alonso: Just in case, have you noticed I'm using an ALSA-Jack loopback setting for audio? Under sysvinit, udev (including udevadm settle) is started before the kmod init script, which loads snd_aloop. That means, snd_aloop is loaded after snd_hda_intel. Under systemd, it looks like the snd_aloop module is loaded about the same time systemd-udevd is started. There might be a race here and snd_aloop is loaded before snd_hda_intel. This *might* be the reason, but I'm no expert on this matter. Can you try removing snd_aloop from /etc/modules and test if that makes a difference. OK removed snd_aloop and audio is back. Then reloaded the module, restarted JACK and audio is still fine. So as you said there must be some race condition in there. Should I keep this ticket opened? Hm, not sure what to do about this. We could order systemd-load-modules.service after systemd-udevd.service. But that doesn't guarantee the loading order of the modules and it feels like papering over the underlying issue. I'm no sound expert, but I'd say that the loading order should not matter. Maybe we need some input from the kernel team or some alsa experts here. I think this is due to ALSA userland (or maybe higher levels) being stupid about device selection. I think the default is to use sound device 0, which can be whichever driver won the race. I took the liberty to CC the Debian kernel team and the maintainer of the snd_aloop module. I hope they can help us here. For reference the complete bug report is at [1] Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753816 I think the usual workaround is to add 'index=1' to the snd-aloop line in /etc/modules. It is probably possible to do something more sophisticated in an ALSA configuration file. Ben. -- Ben Hutchings The most exhausting thing in life is being insincere. - Anne Morrow Lindberg signature.asc Description: This is a digitally signed message part ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
