Bug#742322: [Pkg-systemd-maintainers] Bug#742322: backtrace for systemd crash
severity 742322 important forwarded 742322 https://bugs.freedesktop.org/show_bug.cgi?id=76899 thanks Am 31.03.2014 08:24, schrieb Didier 'OdyX' Raboud: Le jeudi, 27 mars 2014, 02.32:58 Michael Biebl a écrit : OdyX, I took the liberty to CC you. So this issue is indeed triggered by CUPS and the way it sets up the socket configuration. Yay, thanks. I suspected that this was causing the problem but couldn't reproduce it, now we do have a trail. It's certainly a bug in systemd and it shouldn't crash, but maybe you can fix cups-daemon to not trigger this issue by not creating a time window where /etc/systemd/system/cups.socket.d/cupsd-listen.conf is a dangling symlink I'll move the cupsd-listen.conf file creation to preinst, aka before the symlink is unpacked, in the next CUPS upload due very soon. OdyX was so kind to update cups in the mean time. It now no longer creates a dangling symlink. While this is still a valid and bad bug in systemd, I'm nonetheless downgrade it to important, since the circumstances to trigger it are pretty special. So neither critical nor grave really qualifies. I've forwarded the bug upstream. Michael [0] http://lists.freedesktop.org/archives/systemd-devel/2014-March/018253.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
Bug#742322: backtrace for systemd crash
Le jeudi, 27 mars 2014, 02.32:58 Michael Biebl a écrit : OdyX, I took the liberty to CC you. So this issue is indeed triggered by CUPS and the way it sets up the socket configuration. Yay, thanks. I suspected that this was causing the problem but couldn't reproduce it, now we do have a trail. It's certainly a bug in systemd and it shouldn't crash, but maybe you can fix cups-daemon to not trigger this issue by not creating a time window where /etc/systemd/system/cups.socket.d/cupsd-listen.conf is a dangling symlink I'll move the cupsd-listen.conf file creation to preinst, aka before the symlink is unpacked, in the next CUPS upload due very soon. Thanks for the investigation! Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742322: backtrace for systemd crash
Hi, On 27.03.2014 02:29, Michael Biebl wrote: Thanks a lot for the back trace! I'm glad I could help. This helped me to reproduce the sequence of events which need to happen to trigger the abort. So this is good news (well sort of). This is great news, at least for me, as I now can reboot this machine. Andreas, you mentioned: 'Freezing execution' sounds as bad as crashing. Actually it isn't. Would systemd symply crash, your kernel would freeze. With systemd catching the SIGABRT you can at least still stop your service (even if you need to do that via kill), you can sync and unmount your fs besides / and do a half-way decent reboot. You're right, I can still make a half-way decent reboot, and that's what I'm going to do now. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742322: also affects me
Control: reopen -1 Control: tags -1 - unreproducible moreinfo Control: severity -1 critical Justification: breaks many packages, even shutdown/reboot Dear systemd maintainers, I'm also hitting this bug. I upgraded systemd to 204-8 yesterday and now upgrading cups-daemon to 1.7.1-10 failed, apparently crashing systemd. I don't know if cups-daemon is broken somehow (see #742668 for a report of this bug against cups), but it should not be able to crash systemd. I still have the system running, so I can supply more information, but I couldn't find here, what information you need. Thus I can just give some general information. The relevant part from the journal seems to be: systemd[1]: Stopping CUPS Printer Service Spool. systemd[1]: Stopped CUPS Printer Service Spool. systemd[1]: Reloading. systemd[1]: Stopping CUPS Printing Service... systemd[1]: Stopped CUPS Printing Service. colord[2239]: Automatic remove of LaserJet-CM1415fn-Gray.. from cups-LaserJet-CM1415fn colord[2239]: Profile removed: LaserJet-CM1415fn-Gray.. colord[2239]: Automatic remove of LaserJet-CM1415fn-RGB.. from cups-LaserJet-CM1415fn colord[2239]: Profile removed: LaserJet-CM1415fn-RGB.. colord[2239]: device removed: cups-LaserJet-CM1415fn colord[2239]: Automatic remove of Officejet_6500_E710n-z-Gray.. from cups-Officejet_6500_E710n-z colord[2239]: Profile removed: Officejet_6500_E710n-z-Gray.. colord[2239]: Automatic remove of Officejet_6500_E710n-z-RGB.. from cups-Officejet_6500_E710n-z colord[2239]: Profile removed: Officejet_6500_E710n-z-RGB.. colord[2239]: device removed: cups-Officejet_6500_E710n-z systemd[1]: Reloading. systemd[1]: Failed to open configuration file '/etc/systemd/system/cups.socket.d/cupsd-listen.conf': No such file or directory systemd[1]: Reloading. systemd[1]: Failed to open configuration file '/etc/systemd/system/cups.socket.d/cupsd-listen.conf': No such file or directory org.gtk.Private.GPhoto2VolumeMonitor[2521]: ### debug: Name owner ':1.156' vanished org.gtk.Private.MTPVolumeMonitor[2521]: ### debug: Name owner ':1.156' vanished org.gtk.Private.GoaVolumeMonitor[2521]: ### debug: Name owner ':1.156' vanished org.gtk.Private.UDisks2VolumeMonitor[2521]: ### debug: Name owner ':1.156' vanished org.gtk.Private.AfcVolumeMonitor[2521]: ### debug: Name owner ':1.156' vanished systemd[1]: Assertion 'unit' failed at ../src/core/manager.c:882, function manager_add_job(). Aborting. systemd[1]: Caught ABRT, dumped core as pid 8502. systemd[1]: Freezing execution. 'Freezing execution' sounds as bad as crashing. Note that the configuration file exists, but is a link: $ file /etc/systemd/system/cups.socket.d/cupsd-listen.conf /etc/systemd/system/cups.socket.d/cupsd-listen.conf: symbolic link to `../../../cups/cupsd-systemd-listen.conf' $ file /etc/cups/cupsd-systemd-listen.conf /etc/cups/cupsd-systemd-listen.conf: ASCII text If you need further information, please let me know soon, as I'm going to forcefully reboot this machine sooner or later. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742322: backtrace for systemd crash
Hi, I build systemd with debugging symbols and extracted a backtrace from the core dump: #0 0x7f1a0b51a75b in raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 #1 0x0040ca85 in crash (sig=6) at ../src/core/main.c:142 #2 signal handler called #3 0x7f1a0b1973a9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #4 0x7f1a0b19a4c8 in __GI_abort () at abort.c:89 #5 0x004614e3 in log_assert (text=text@entry=0x48778a unit, file=file@entry=0x4858f2 ../src/core/manager.c, line=line@entry=882, func=func@entry=0x4874b0 __PRETTY_FUNCTION__.13067 manager_add_job, format=format@entry=0x4b7e80 Assertion '%s' failed at %s:%u, function %s(). Aborting.) at ../src/shared/log.c:695 #6 0x00461d80 in log_assert_failed (text=text@entry=0x48778a unit, file=file@entry=0x4858f2 ../src/core/manager.c, line=line@entry=882, func=func@entry=0x4874b0 __PRETTY_FUNCTION__.13067 manager_add_job) at ../src/shared/log.c:700 #7 0x0040ecd8 in manager_add_job (m=0x15fa910, type=type@entry=JOB_START, unit=0x0, mode=mode@entry=JOB_REPLACE, override=override@entry=true, e=e@entry=0x7fff904923c0, _ret=_ret@entry=0x0) at ../src/core/manager.c:882 #8 0x0042fce7 in socket_enter_running (s=0x1620620, cfd=-1) at ../src/core/socket.c:1487 #9 0x00412c6c in process_event (ev=0x7fff90492670, m=0x15fa910) at ../src/core/manager.c:1628 #10 manager_loop (m=0x15fa910) at ../src/core/manager.c:1795 #11 0x0040a468 in main (argc=optimized out, argv=0x7fff90492ed8) at ../src/core/main.c:1734 I hope this helps to fix the problem. Best regards, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742322: backtrace for systemd crash
Am 26.03.2014 17:39, schrieb Andreas Cadhalpun: Hi, I build systemd with debugging symbols and extracted a backtrace from the core dump: Thanks a lot for the back trace! This helped me to reproduce the sequence of events which need to happen to trigger the abort. So this is good news (well sort of). The sequence of events is a/ make sure cups.socket is running and correctly setup b/ make sure cups.service is not running c/ make /etc/systemd/system/cups.socket.d/cupsd-listen.conf a dangling symlink d/ trigger a daemon-reload e/ trigger activity on the cups socket, e.g. via lpq → You get the abort At this point, systemd catches the SIGABRT and freezes, i.e. no longer responds to any requests. Andreas, you mentioned: 'Freezing execution' sounds as bad as crashing. Actually it isn't. Would systemd symply crash, your kernel would freeze. With systemd catching the SIGABRT you can at least still stop your service (even if you need to do that via kill), you can sync and unmount your fs besides / and do a half-way decent 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
Bug#742322: backtrace for systemd crash
Am 27.03.2014 02:29, schrieb Michael Biebl: Am 26.03.2014 17:39, schrieb Andreas Cadhalpun: The sequence of events is a/ make sure cups.socket is running and correctly setup b/ make sure cups.service is not running c/ make /etc/systemd/system/cups.socket.d/cupsd-listen.conf a dangling symlink d/ trigger a daemon-reload e/ trigger activity on the cups socket, e.g. via lpq → You get the abort OdyX, I took the liberty to CC you. So this issue is indeed triggered by CUPS and the way it sets up the socket configuration. It's certainly a bug in systemd and it shouldn't crash, but maybe you can fix cups-daemon to not trigger this issue by not creating a time window where /etc/systemd/system/cups.socket.d/cupsd-listen.conf is a dangling symlink -- 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
Bug#742322: backtrace for systemd crash
Am 27.03.2014 02:29, schrieb Michael Biebl: Am 26.03.2014 17:39, schrieb Andreas Cadhalpun: The sequence of events is a/ make sure cups.socket is running and correctly setup b/ make sure cups.service is not running c/ make /etc/systemd/system/cups.socket.d/cupsd-listen.conf a dangling symlink d/ trigger a daemon-reload e/ trigger activity on the cups socket, e.g. via lpq → You get the abort As mentioned on IRC, the problem is triggered in src/core/socket.c: socket_enter_running(), when the incoming request causes the start of the corresponding service unit via r = manager_add_job(UNIT(s)-manager, JOB_START, UNIT_DEREF(s-service), JOB_REPLACE, true, error, NULL); I think after the socket configuration has been messed up and the daemon-reload, UNIT_DEREF(s-service) does no longer point to a valid unit, and so the assert in manager_add_job() kicks in. Ideas how to address this? Should we just stop a socket if we detect on daemon-reload that the socket configuration has been messed up? Or should we do some sanity-checking of the unit in socket_enter_running before we pass it on to manager_add_job()? -- 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
Bug#742322: systemd: Breasks other services to be restarted/ installed during apt-get dist-upgrade
Package: systemd Version: 204-8 Severity: grave Justification: breaks other packages -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I just upgraded from 204-7 to 204-8 and during the process all services which needs to get restared fails to restart: NOTE: I did *not* yet reboot; will check if after filing this bug and add infos too. Also, a manual retry to restart services fails with the same error. (every service I tried failed so far with the same error. I tried gpsd, cups, samba, bluetooth) Please let me know if you need further details. - -- Best regards, Tobias Frost Example below: LANG=C apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 20 not upgraded. 4 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up cups-daemon (1.7.1-10) ... Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused invoke-rc.d: initscript cups, action start failed. dpkg: error processing package cups-daemon (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of cups-core-drivers: cups-core-drivers depends on cups-daemon (= 1.7.1-10); however: Package cups-daemon is not configured yet. dpkg: error processing package cups-core-drivers (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of cups: cups depends on cups-core-drivers (= 1.7.1-10); however: Package cups-core-drivers is not configured yet. cups depends on cups-daemon (= 1.7.1-10); however: Package cups-daemon is not configured yet. dpkg: error processing package cups (--configure): dependency problems - leaving unconfigured Setting up gpsd (3.10+dev1~a33bfd44-2) ... Creating/updating gpsd user account... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused invoke-rc.d: initscript gpsd, action start failed. dpkg: error processing package gpsd (--configure): subprocess installed post-installation script returned error exit status 1 Error: Timeout was reached /etc/init.d/gpsd restart Restarting gpsd (via systemctl): gpsd.serviceFailed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Verbindungsaufbau abgelehnt failed! - -- Package-specific info: - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-51 ii libacl1 2.2.52-1 ii libaudit11:2.3.4-1 ii libc62.18-4 ii libcap2 1:2.22-1.2 ii libcap2-bin 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.0-2 ii libgcrypt11 1.5.3-4 ii libkmod2 16-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-2 ii libselinux1 2.2.2-1 ii libsystemd-daemon0 204-8 ii libsystemd-journal0 204-8 ii libsystemd-login0204-8 ii libudev1 204-8 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-51 ii udev 204-8 ii util-linux 2.20.1-5.6 Versions of packages systemd recommends: ii libpam-systemd 204-8 Versions of packages systemd suggests: pn systemd-ui none - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTLXV0AAoJEJFk+h0XvV02y+gP/2mJ8TVlARSaoMWYISFm7o65 AkoAokYuQLp2qAnb65NIKDUhNoQ0rTFsXh1YZmBhr0kvw3X9Zokxx551F0bPSpp9 zWVvpBW71Il84GH230hOi7KDOmN6ojydQnr/ahWUObxm7kqOSB4Mwjq4HyJXNzom GPpydKBNWnUukhzv13xwDpa7w+XZxL5lcW3ODW2tmdVakCMh3v2J0eXR8Rus08B9 nw25dvy4qtx7P+LD8B73xkL12sf8bV+L/l8iUDhkcfv/XvQrCvIsQ9Pppi3cB5Vu uKDc9WuMyiwuyI7+DGbosbNf1B101OJTonRBG9ioqxVtfo0lx7Jk/L3l2ZPaYEjq tPR6RrMtQtD8Onj0pvW3f6u094nqQfHhfSouEkHI3/ZQMPIZtxDBFkpUzDgLFgLR nmteHVxXPTAjSyxMWerTPyKr/LgKVOYRN+As3iCx2WEC5KZWzf2WP7b4OKoIttca 2eM5zrs+cufxuaWhZOkMSm4ej6kyRJGQRuk6Lb4nevDIyfYQxTT1TW/EY9aDTn7X cfI7uK/SVt6pPCP4i7vsPjWFRvxCDddDJT97viyg0VeVfwtERI7T2qsYmQrbGhDJ 1YC7Sx4CrF4cHYJoCAjqoIYwnpH+g9HKgibphP0pG3Kftuv1kHXLbmGA2u5zSaFr I1bdy4tvDPKxW+fLp9fD =lvqA -END PGP SIGNATURE- 0 overridden configuration files found. systemctl-dump.txt Description: inode/empty ==
Bug#742322:
PS: Can't reboot by normal means: LANG=C reboot Failed to open /dev/initctl: No such device or address Failed to talk to init daemon. current systemd status: ps x | grep systemd 1 ?Ss 0:06 /lib/systemd/systemd --system --deserialize 17 558 pts/0S+ 0:00 grep systemd 6545 ?Ss 0:00 /lib/systemd/systemd-udevd 6577 ?Ss 0:00 /lib/systemd/systemd-journald 6583 ?Ss 0:00 /lib/systemd/systemd-logind 20611 ?S 0:00 systemd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742322:
Update: After rebooting using Magic SysReq, system boots and apt-get install -f completes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742322: systemd: Breasks other services to be restarted/ installed during apt-get dist-upgrade
Am 22.03.2014 12:35, schrieb coldtobi: Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused This is an indication that systemd crashed. If you can reproduce the sequence of events to trigger this crash, please let us know and we'll reopen the bug report. Thanks, 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
Bug#742322: systemd: Breasks other services to be restarted/ installed during apt-get dist-upgrade
Am 22.03.2014 13:45, schrieb Michael Biebl: Am 22.03.2014 12:35, schrieb coldtobi: Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused This is an indication that systemd crashed. If you can reproduce the sequence of events to trigger this crash, please let us know Like for example you have a backup of your system from before the upgrade and you can trigger this issue again with apt-get dist-upgrade. -- 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
Bug#742322: systemd: breaks other service / makes restart via /sbin/reboot impossible
Package: systemd Followup-For: Bug #742322 Control: -1 tags moreinfo -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Is this the way systemd people generally respond to problem reports? Just closing bugs and hide (possible) problems? I'm very disappointed. You know, in Debian we do not hide problems. Back to the topic No, I do not have a system backup. However, I just in the progress to downgrade all systemd packages to 204-7 and see if I can reproduce. In the meantime please send me a list what I should check *if* I am be able to reproduce, since I will not invest the whole afternoon on systemd and I need the PC in a working state. Until then I took myself freedom to reopen, because I did not see any resoning why it is not a valid bug. If I can not reproduce, I suggest tagging it as not reproducable and reduce severity. Best regards. - -- Tobias Frost - -- Package-specific info: - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-51 ii libacl1 2.2.52-1 ii libaudit11:2.3.4-1 ii libc62.18-4 ii libcap2 1:2.22-1.2 ii libcryptsetup4 2:1.6.4-4 ii libdbus-1-3 1.8.0-2 ii libgcrypt11 1.5.3-4 ii libkmod2 16-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-2 ii libselinux1 2.2.2-1 ii libsystemd-daemon0 204-7 ii libsystemd-journal0 204-7 ii libsystemd-login0204-7 ii libudev1 204-8 ii libwrap0 7.6.q-25 ii udev 204-8 ii util-linux 2.20.1-5.6 Versions of packages systemd recommends: pn libpam-systemd none Versions of packages systemd suggests: pn systemd-ui none - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTLZ7QAAoJEJFk+h0XvV02ISoP/AjMzFrGsSH22HI/FFxUeMfR AnvvbEmsmpn0hsd0b23c9C744Z3ubWQXj3sOKORBol82K2FHnw1nxf+uDMx/Dp1t RLSP8G5WvH1/pLlYbA54DhPxClkKBlwybosbms8+DAMRagubaJVB+42zHp3lPk3L CvmeFkM7hA/qMXO85KLQTKiPZEAQmQ9cLaRakNXVhSfPrrYEjm2Fg3JUReeDCFDr XlMMTsCi/oskrWhoRIzqbi89NaywJxu4RIoHU5ldoQ1YJrjSsNCiCFfT869PMEKG 66Qwsk6vFyTpNlafq6uxMz9c1K68odSkSEr3brYOz5ZSshxo7e9Kdh8fgYGbFRzy VOPbcRsFUb8gBfj9PF7UNOmVIW/l7GgOT/Moq6cJhlDvs9rR5gUYoTYRLij39NTs UT7cEQp13G5bHiT+U1oaDB5V7SzUW4/MEYq7yMP1zuW6qwkePPOi8GWzr82e8emd hfCOQ+eduEXDQQvPW7CSoiwsV6RBeFQ/0lAIB94rjERHu4xlEOxaQxI6e2VbKyl0 cdqDnEZHdNdiN0Z2hzh3LrPqknXtvqQICKtzrMBn2L9mnlG1WvS5A391bDhxsS9r 7qPzE7S/lQtLlj3VJ9ImTefKQKdulT20wEz4Z4XOM9+cyf3NfzkMzRd6Yw8l54P/ UBMY73bvNBClEhkp+TZB =ou4U -END PGP SIGNATURE- 0 overridden configuration files found. systemctl-dump.txt Description: inode/empty == /var/lib/systemd/deb-systemd-helper-enabled/libvirt-guests.service.dsh-also == /etc/systemd/system/multi-user.target.wants/libvirt-guests.service /etc/systemd/system/multi-user.target.wants/libvirt-guests.service == /var/lib/systemd/deb-systemd-helper-enabled/gpsd.service.dsh-also == /etc/systemd/system/sockets.target.wants/gpsd.socket == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/gpsd.socket == == /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket == == /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.bluez.service == == /var/lib/systemd/deb-systemd-helper-enabled/cups.socket.dsh-also == /etc/systemd/system/sockets.target.wants/cups.socket == /var/lib/systemd/deb-systemd-helper-enabled/gpsd.socket.dsh-also == /etc/systemd/system/sockets.target.wants/gpsd.socket == /var/lib/systemd/deb-systemd-helper-enabled/libvirt-bin.service.dsh-also == /etc/systemd/system/multi-user.target.wants/libvirt-bin.service /etc/systemd/system/multi-user.target.wants/libvirt-bin.service == /var/lib/systemd/deb-systemd-helper-enabled/binfmt-support.service.dsh-also == /etc/systemd/system/multi-user.target.wants/binfmt-support.service == /var/lib/systemd/deb-systemd-helper-enabled/cups-browsed.service.dsh-also == /etc/systemd/system/multi-user.target.wants/cups-browsed.service == /var/lib/systemd/deb-systemd-helper-enabled/cups.path.dsh-also == /etc/systemd/system/multi-user.target.wants/cups.path == /var/lib/systemd/deb-systemd-helper-enabled/syslog.service == == /var/lib/systemd/deb-systemd-helper-enabled/printer.target.wants/cups.service == == /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also == /etc/systemd/system/multi-user.target.wants/rsyslog.service /etc/systemd/system/syslog.service /etc/systemd/system/multi-user.target.wants/rsyslog.service
Bug#742322: (no subject)
Can't reproduce by downgrading and re-upgrading. Stopping here putting effort into systemd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742322: [Pkg-systemd-maintainers] Bug#742322: systemd: breaks other service / makes restart via /sbin/reboot impossible
Hi coldtobi, coldtobi t...@coldtobi.de writes: Is this the way systemd people generally respond to problem reports? Just closing bugs and hide (possible) problems? I'm very disappointed. You know, in Debian we do not hide problems. Typically I wouldn’t even respond to this, but your last sentence strikes me as pretty arrogant¹, and the second sentence is a baseless accusation, so here goes: Closing a bug is not “hiding problems”. We (the systemd maintainers in Debian) generally tend to close bugs early (and reopen on demand) to keep the amount of bugs manageable. We think this is good for us, since it makes our work possible in the first place, it’s good for new contributors who see a well-tended buglist and it’s good for users who don’t have to scroll through pages of non-issues, wishlist items that noone will ever fix and other reports like that. IMO, the Debian bugtracker severely lacks a good way of displaying/filtering bugs. In case we had that, I wouldn’t have any problem with leaving bugs like this open forever. Also, I’d like to point out that we actually _do_ respond in the first place, and that within one hour (!) of your report. That’s a kick-ass response time, and having responses at all is something that enough other Debian packages don’t even achieve, unfortunately. ① You are trying to lecture us about how Debian works, while there is no agreed-upon set of rules that backs up your particular interpretation of how Debian should work. This comes across as you imposing your will onto us. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
