Processed: severity of 835590 is serious
Processing commands for cont...@bugs.debian.org: > severity 835590 serious Bug #835590 [libsoundio1] libsoundio1: Missing hard dependency on libjack-jackd2-0 Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 835590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915146: ioprocess: FTBFS with ld --as-needed
Package: ioprocess Version: 0.15.1-3 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu disco ubuntu-patch Dear Maintainer, ioprocess fails to build from source when the ld linker is configured to use the --as-needed option, which requires that libraries be in a certain order. This is the default in Ubuntu. While this isn't strictly necessary in Debian, it puts the libraries in the right place and will let us avoid having to maintain a delta. In Ubuntu, the attached patch was applied to achieve the following: * Merge from Debian unstable. Remaining changes: - Use LDADD instead of LDFLAGS to fix FTBFS with ld --as-needed. Thanks for considering the patch. Logan -- System Information: Debian Release: buster/sid APT prefers cosmic-updates APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-11-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru ioprocess-0.15.1/debian/patches/ld-as-needed.patch ioprocess-0.15.1/debian/patches/ld-as-needed.patch --- ioprocess-0.15.1/debian/patches/ld-as-needed.patch 1969-12-31 19:00:00.0 -0500 +++ ioprocess-0.15.1/debian/patches/ld-as-needed.patch 2016-01-31 23:54:06.0 -0500 @@ -0,0 +1,17 @@ +Description: use LDADD instead of LDFLAGS to fix FTBFS with ld --as-needed +Author: Logan Rosen +Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1304958 +Last-Update: 2016-02-05 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/src/Makefile.am b/src/Makefile.am +@@ -14,7 +14,7 @@ + $(IOPROCESS_CFLAGS) \ + $(AM_CFLAGS) \ + $(NULL) +-ioprocess_LDFLAGS = $(GLIB2_LIBS) \ ++ioprocess_LDADD = $(GLIB2_LIBS) \ + $(GTHREAD2_LIBS) \ + $(YAJL_LIBS) \ + $(AM_LDFLAGS) \ diff -Nru ioprocess-0.15.1/debian/patches/series ioprocess-0.15.1/debian/patches/series --- ioprocess-0.15.1/debian/patches/series 2016-01-18 10:37:22.0 -0500 +++ ioprocess-0.15.1/debian/patches/series 2018-07-11 12:57:55.0 -0400 @@ -1 +1,2 @@ paths.patch +ld-as-needed.patch
Bug#760070: marked as done (logind : error at login and logout)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #748648, regarding logind : error at login and logout 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.) -- 748648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 208-8 Severity: normal When I login I get following messages [ 21.563380] systemd-logind[2908]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 21.563408] systemd-logind[2908]: Failed to start user service: Unknown unit: user@1000.service When I logout I get the following ones [ 329.910312] systemd-logind[2908]: Failed to abandon scope session-2.scope [ 329.910345] systemd-logind[2908]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unid/session_2d2_2escope Those messages are in no log file. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing-proposed-updates APT policy: (900, 'testing-proposed-updates'), (900, 'testing'), (700, 'proposed-updates'), (600, 'stable'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.3 ii libacl1 2.2.52-1 ii libaudit11:2.3.7-1 ii libblkid12.20.1-5.8 ii libc62.19-9 ii libcap2 1:2.24-4 ii libcap2-bin 1:2.24-4 ii libcryptsetup4 2:1.6.6-1 ii libdbus-1-3 1.8.6-2 ii libgcrypt11 1.5.4-2 ii libkmod2 18-1 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-1 ii libsystemd-daemon0 208-8 ii libsystemd-journal0 208-8 ii libsystemd-login0208-8 ii libudev1 208-8 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53.3 ii udev 208-8 ii util-linux 2.20.1-5.8 Versions of packages systemd recommends: ii libpam-systemd 208-8 Versions of packages systemd suggests: pn systemd-ui -- no debconf information [EXTENDED] /lib/systemd/system/cups.socket -> /etc/systemd/system/cups.socket.d/cupsd-listen.conf 1 overridden configuration files found. ==> /var/lib/systemd/deb-systemd-helper-enabled/acpi-fakekey.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/acpi-fakekey.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.bluez.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/cups.service.dsh-also <== /etc/systemd/system/sockets.target.wants/cups.socket /etc/systemd/system/paths.target.wants/cups.path /etc/systemd/system/printer.target.wants/cups.service ==> /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/cron.service ==> /var/lib/systemd/deb-systemd-helper-enabled/bluetooth.target.wants/bluetooth.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/ssh.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/pppd-dns.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/NetworkManager.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cron.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/cgproxy.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/cgproxy.service ==> /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-wait-online.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/NetworkManager-wait-online.service ==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <== ==>
Bug#756247: marked as done (Failed to start unit user@1000.service: Unknown unit: user@1000.service)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #748648, regarding Failed to start unit user@1000.service: Unknown unit: user@1000.service 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.) -- 748648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 6-4 Severity: normal When running logind v205+ under systemd-shim 6-4 / cgmanager, I get this error message: Failed to start unit user@0.service: Unknown unit: user@0.service Failed to start user service: Unknown unit: user@0.service This is particularly visible on the console, where the error message is shown on the users console upon login. Ther user@.service provides a per user session which is started by the pam_systemd module. [1] has a few more details. [1] https://wiki.archlinux.org/index.php/Systemd/User -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-shim depends on: pn cgmanager ii libc6 2.19-7 ii libglib2.0-0 2.40.0-3 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: ii pm-utils 1.4.1-15 --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#846661: marked as done (light-locker: screen remains black after unlock)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #846661, regarding light-locker: screen remains black after unlock 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.) -- 846661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846661 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: light-locker Version: 1.7.0-3 Severity: important After pulling a bunch of new packages from sid - xorg-server-core, mesa, and dbus, light-locker stopped working. When unlocking, after putting in my credentials the screen remains black. Killing the process brings the desktop back. Attaching debug output. I'm using XFCE. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages light-locker depends on: ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2 ii libc62.24-7 ii libcairo21.14.6-1.1 ii libdbus-1-3 1.10.14-1 ii libdbus-glib-1-2 0.108-1 ii libglib2.0-0 2.50.2-2 ii libgtk-3-0 3.22.4-1 ii libpango-1.0-0 1.40.3-3 ii libpangocairo-1.0-0 1.40.3-3 ii libsystemd0 232-6 ii libx11-6 2:1.6.3-1 ii libxext6 2:1.3.3-1 ii libxss1 1:1.2.2-1 ii lightdm 1.18.2-3 light-locker recommends no packages. light-locker suggests no packages. -- no debconf information $ light-locker --debug [gs_debug_init] gs-debug.c:106 (00:20:03): Debugging enabled [main] light-locker.c:142 (00:20:03):initializing light-locker 1.7.0 [main] light-locker.c:144 (00:20:03):lock after screensaver 5 [main] light-locker.c:145 (00:20:03):late locking 0 [main] light-locker.c:146 (00:20:03):lock on suspend 1 [main] light-locker.c:147 (00:20:03):lock on lid 0 [main] light-locker.c:148 (00:20:03):idle hint 0 [query_session_id] gs-listener-dbus.c:2088 (00:20:03): org.freedesktop.login1.NoSessionForPID raised: PID 8711 does not belong to any known session [init_session_id] gs-listener-dbus.c:2180 (00:20:03):Got session-id: (null) [query_sd_session_id] gs-listener-dbus.c:2164 (00:20:03):Couldn't determine our own sd session id: No such file or directory [init_session_id] gs-listener-dbus.c:2185 (00:20:03):Got sd-session-id: (null) [init_seat_path] gs-listener-dbus.c:2262 (00:20:03): Got seat: /org/freedesktop/DisplayManager/Seat0 [gs_listener_delay_suspend] gs-listener-dbus.c:449 (00:20:03): Delay suspend [gs_listener_x11_acquire] gs-listener-x11.c:172 (00:20:03): ScreenSaver Registered [listener_dbus_handle_system_message] gs-listener-dbus.c:1330 (00:20:03): obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameAcquired destination=:1.127 [gs_grab_grab_root] gs-grab-x11.c:647 (00:20:09):Grabbing the root window [gs_grab_get_keyboard] gs-grab-x11.c:153 (00:20:09): Grabbing keyboard widget=4B5 [gs_grab_get_mouse] gs-grab-x11.c:213 (00:20:09):Grabbing mouse widget=4B5 [gs_manager_create_windows_for_screen] gs-manager.c:548 (00:20:09): Creating 1 windows for screen 0 [gs_manager_create_window_for_monitor] gs-manager.c:324 (00:20:09): Creating window for monitor 0 [0,0] (1920x1080) [update_geometry] gs-window-x11.c:197 (00:20:09):got geometry for monitor 0: x=0 y=0 w=1920 h=1080 [update_geometry] gs-window-x11.c:210 (00:20:09):using geometry for monitor 0: x=0 y=0 w=1920 h=1080 [update_geometry] gs-window-x11.c:197 (00:20:09):got geometry for monitor 0: x=0 y=0 w=1920 h=1080 [update_geometry] gs-window-x11.c:210 (00:20:09):using geometry for monitor 0: x=0 y=0 w=1920 h=1080 [gs_window_move_resize_window] gs-window-x11.c:243 (00:20:09): Move and/or resize window on monitor 0: x=0 y=0 w=1920 h=1080 [update_geometry] gs-window-x11.c:197 (00:20:09):got geometry for monitor 0: x=0 y=0 w=1920 h=1080 [update
Bug#895292: marked as done (Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #895292, regarding Restart, Suspend, Hibernate, Shut Down all greyed out in lightdm 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.) -- 895292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: policykit-1 Version: 0.105-20 Severity: important After the upgrade to policykit-1 0.105-20, the Restart, Suspend, Hibernate, Shut Down menu entries are all greyed out. Note: lightdm and lightdm-gtk-greeter have not changed. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages policykit-1 depends on: ii dbus 1.12.6-2 ii libc6 2.27-3 ii libglib2.0-0 2.56.0-6 ii libpam-systemd 238-4 ii libpam0g 1.1.8-3.7 ii libpolkit-agent-1-00.105-20 ii libpolkit-backend-1-0 0.105-20 ii libpolkit-gobject-1-0 0.105-20 policykit-1 recommends no packages. policykit-1 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#915038: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: systemd-shim | 10-3 | source, amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; unmaintained; dead upstream; broken -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 915...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/915038 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#915038: Removed package(s) from unstable
Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#757696: marked as done (systemd-logind logging to dmesg under sysvinit)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #748648, regarding systemd-logind logging to dmesg under sysvinit 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.) -- 748648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 208-7 Severity: normal --- Please enter the report below this line. --- systemd is writing messages to kmsg: $ dmesg -x auth :err : [ 27.565727] systemd-logind[3382]: Failed to enable subscription: No such method 'Subscribe' auth :info : [ 27.566597] systemd-logind[3382]: New seat seat0. auth :info : [ 27.567357] systemd-logind[3382]: Watching system buttons on /dev/input/event1 (Power Button) auth :info : [ 27.567475] systemd-logind[3382]: Watching system buttons on /dev/input/event0 (Power Button) auth :err : [ 27.570542] systemd-logind[3382]: Failed to start unit user@1000.service: Unknown unit: user@1000.service auth :err : [ 27.570555] systemd-logind[3382]: Failed to start user service: Unknown unit: user@1000.service auth :info : [ 27.572213] systemd-logind[3382]: New session 2 of user edwin. auth :info : [ 27.572249] systemd-logind[3382]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. auth :err : [ 841.498260] systemd-logind[3382]: Failed to start unit user@65534.service: Unknown unit: user@65534.service auth :err : [ 841.498272] systemd-logind[3382]: Failed to start user service: Unknown unit: user@65534.service auth :info : [ 841.499580] systemd-logind[3382]: New session c1 of user nobody. auth :err : [ 841.517534] systemd-logind[3382]: Failed to abandon scope session-c1.scope auth :err : [ 841.517542] systemd-logind[3382]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope auth :info : [ 841.524278] systemd-logind[3382]: New session c2 of user nobody. auth :err : [ 841.537574] systemd-logind[3382]: Failed to abandon scope session-c2.scope auth :err : [ 841.537583] systemd-logind[3382]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope auth :info : [ 841.545551] systemd-logind[3382]: New session c3 of user nobody. auth :err : [ 900.432607] systemd-logind[3382]: Failed to abandon scope session-c3.scope auth :err : [ 900.432618] systemd-logind[3382]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope There are several things wrong here: - it is the only userspace application that does that on a regular basis - the :info messages have nothing to do in kmsg. They are not something that you should act on, so why spam kmsg with useless messages like that? Write them to syslog where they belong - I might understand the :err messages if they would really indicate a serious error. But IMHO these messages should be :warn, or something less severe. Is there something that I should do based on those messages? Is something broken now? (well Networkmanager is, but thats a separate bug) - more importantly the :err messages are NOT logged to syslog at all. grep /var/log/* for 'Failed to abandon scope session-c2.scope' comes up empty. So I'm really confused on the purpose of these messages: on one hand they are logged to a place usually reserved for things like networking messages, coredumps, yet it is not logged in any persistent place, so they would go unnoticed by logwatch probably, etc. - if systemd would at some point log an important message it'd probably go unnoticed since I'd be used to ignoring messages from systemd in dmesg, and they are not in /var/log/* The code that logs to kmsg seems to be write_to_kmsg in src/shared/log.c. FWIW I have sysvinit-core and systemd-shim installed (I don't see that info appended by the bug script). --- System information. --- Architecture: amd64 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 500 unstableftp.ro.debian.org 500 testing ftp.ro.debian.org 1 experimentalftp.ro.debian.org --- Package information. --- Depends (Version) | Installed =-+-== libacl1 (>= 2.2.51-8) | 2.2
Bug#794052: marked as done (systemd: logging to host via ssh with systemd but not using itself)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #748648, regarding systemd: logging to host via ssh with systemd but not using itself 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.) -- 748648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 222-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 4.0.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages systemd depends on: ii adduser 3.113+nmu3 ii libacl1 2.2.52-2 ii libapparmor12.9.2-3 ii libaudit1 1:2.4.2-1 ii libblkid1 2.26.2-6 ii libc6 2.19-19 ii libcap2 1:2.24-9 ii libcap2-bin 1:2.24-9 ii libcryptsetup4 2:1.6.6-5 ii libgcc1 1:5.1.1-14 ii libgcrypt20 1.6.3-2 ii libkmod221-1 ii liblzma55.1.1alpha+20120614-2.1 ii libmount1 2.26.2-6 ii libpam0g1.1.8-3.1 ii libseccomp2 2.2.1-2 ii libselinux1 2.3-2+b1 ii libsystemd0 222-2 ii mount 2.26.2-6 ii sysv-rc 2.88dsf-59.2 ii udev222-2 ii util-linux 2.26.2-6 Versions of packages systemd recommends: ii dbus1.8.20-1 ii libpam-systemd 222-2 Versions of packages systemd suggests: pn systemd-ui -- no debconf information 9398 login: [ 223.579151] systemd-logind[4102]: Failed to start user service: Unknown unit: user@0.service ? [EXTENDED] /lib/systemd/system/rc-local.service -> /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. ==> /var/lib/systemd/deb-systemd-helper-enabled/acpid.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/acpid.service ==> /var/lib/systemd/deb-systemd-helper-enabled/acpid.path.dsh-also <== /etc/systemd/system/paths.target.wants/acpid.path ==> /var/lib/systemd/deb-systemd-helper-enabled/hybrid-sleep.target.wants/anacron-resume.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/openvpn.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/openvpn.service ==> /var/lib/systemd/deb-systemd-helper-enabled/acpid.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/acpid.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-wait-online.service.dsh-also <== /etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service ==> /var/lib/systemd/deb-systemd-helper-enabled/postgresql.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/postgresql.service ==> /var/lib/systemd/deb-systemd-helper-enabled/cups.path.dsh-also <== /etc/systemd/system/paths.target.wants/cups.path /etc/systemd/system/multi-user.target.wants/cups.path ==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/avahi-daemon.service /etc/systemd/system/sockets.target.wants/avahi-daemon.socket /etc/systemd/system/dbus-org.freedesktop.Avahi.service ==> /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/NetworkManager.service /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service ==> /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.Avahi.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/acpid.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/avahi-daemon.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/uuidd.socket <== ==> /va
Bug#747821: marked as done (systemd-logind doesn't create session for users logged in via GDM)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #747821, regarding systemd-logind doesn't create session for users logged in via GDM 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.) -- 747821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 204-10 Severity: normal Dear Maintainer, I've got problems with systemd-logind. It doesn't register user's session (loginctl displays empty list) which has severe implications for other applications (it's impossible to power off computer via gnome menu, user has no privileges to use NetworkManager applet thus is unable to controll networking etc.). The behaviour is a bit strange because if user logs in via ssh or console, his session is registered. If he logs in via gdm or uses su, it isn't. I don't use systemd as my init system, systemd-shim is installed. I've tried to increase pam_systemd debug level (setting debug=yes in /etc/pam.d/common-session at pam_systemd entry) but the output was the same as without it and auth.log contains line: May 5 08:32:59 xxx gdm3][8444]: pam_systemd(gdm3:session): Failed to create session: No such file or directory -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53 ii libacl1 2.2.52-1 ii libaudit11:2.3.6-1 ii libc62.18-5 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.2-1 ii libgcrypt11 1.5.3-4 ii libkmod2 17-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.2.2-2 ii libsystemd-daemon0 204-10 ii libsystemd-journal0 204-10 ii libsystemd-login0204-10 ii libudev1 204-10 ii libwrap0 7.6.q-25 ii sysv-rc 2.88dsf-53 ii udev 204-10 ii util-linux 2.20.1-5.7 Versions of packages systemd recommends: ii libpam-systemd 204-10 Versions of packages systemd suggests: pn systemd-ui -- no debconf information [OVERRIDDEN] /etc/systemd/system/vsftpd.service → /lib/systemd/system/vsftpd.service Files /lib/systemd/system/vsftpd.service and /etc/systemd/system/vsftpd.service are identical 1 overridden configuration files found. ==> /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.ModemManager1.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation.service.dsh-also <== /etc/systemd/system/local-fs.target.wants/lvm2-activation.service ==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/avahi-daemon.service /etc/systemd/system/sockets.target.wants/avahi-daemon.socket /etc/systemd/system/dbus-org.freedesktop.Avahi.service ==> /var/lib/systemd/deb-systemd-helper-enabled/plymouth.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation-early.service.dsh-also <== /etc/systemd/system/local-fs.target.wants/lvm2-activation-early.service ==> /var/lib/systemd/deb-systemd-helper-enabled/vsftpd.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/vsftpd.service ==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/ssh.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-lvmetad.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/lvm2-lvmetad.socket ==> /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 /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/dbus-org.freedesktop.Avahi.service <== ==> /var/lib/systemd/deb-systemd-help
Bug#748648: marked as done (systemd-logind logging to dmesg under sysvinit)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #748648, regarding systemd-logind logging to dmesg under sysvinit 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.) -- 748648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 204-8 Severity: normal systemd-logind writes logs in dmesg, making it rapidly unusable to get boot messages. logs should be sent elsewhere. -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing-proposed-updates APT policy: (900, 'testing-proposed-updates'), (900, 'testing'), (700, 'proposed-updates'), (600, 'stable'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-1 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53 ii libacl1 2.2.52-1 ii libaudit11:2.3.6-1 ii libc62.18-5 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.2-1 ii libgcrypt11 1.5.3-4 ii libkmod2 16-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.8-3 ii libselinux1 2.2.2-2 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-53 ii udev 204-8 ii util-linux 2.20.1-5.7 Versions of packages systemd recommends: ii libpam-systemd 204-8 Versions of packages systemd suggests: pn systemd-ui -- no debconf information 0 overridden configuration files found. ==> /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.bluez.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/cups.service.dsh-also <== /etc/systemd/system/sockets.target.wants/cups.socket /etc/systemd/system/multi-user.target.wants/cups.path /etc/systemd/system/printer.target.wants/cups.service ==> /var/lib/systemd/deb-systemd-helper-enabled/bluetooth.target.wants/bluetooth.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/ssh.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/pppd-dns.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/NetworkManager.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/anacron.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/atd.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/NetworkManager-wait-online.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/NetworkManager-wait-online.service ==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket <== ==> /var/lib/systemd/deb-systemd-helper-enabled/pppd-dns.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/pppd-dns.service ==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/ssh.service /etc/systemd/system/sshd.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/syslog.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/anacron.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/anacron.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 /etc/systemd/system/syslog.service ==> /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.freedesktop.NetworkManager.service <== ==> /var/lib/syst
Bug#776606: marked as done (systemd-shim is frequently running pm-suspend for no good reason.)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #776606, regarding systemd-shim is frequently running pm-suspend for no good reason. 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.) -- 776606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 9-1 Severity: important Dear Maintainer, I'm seeing systemd-shim run pm-suspend, causing my machine to suspend, when there is no reason for it to do so. It often happens when starting or stopping large applications (e.g. iceweasel), but also happens when nothing special is going on. To avoid this occuring, i replaced /usr/sbin/pm-suspend with a simple script that did nothing except log to a file info on the date/time it was called, and the output of 'ps ax -H'. Each time it is called, i'm seeing a process tree like this 22005 ?Sl 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim 22021 ?S 0:00 sh -c /usr/sbin/pm-suspend 22023 ?S 0:00 /bin/sh /usr/sbin/pm-suspend 22069 ?R 0:00 ps ax -H When running on battery only, i'm seeing this happen one or two times minute. When running on mains power, it's less frequent, e.g. once or twice a day. My machine is a Lenovo X220 laptop. The problem started a month or so ago, after running 'apt upgrade'. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages systemd-shim depends on: ii cgmanager 0.33-2 ii libc6 2.19-13 ii libglib2.0-0 2.42.1-1 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: ii pm-utils 1.4.1-15 -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#768026: marked as done (systemd-logind: logging noise in the kernel log)
Your message dated Sat, 01 Dec 2018 03:05:54 +
with message-id
and subject line Bug#915038: Removed package(s) from unstable
has caused the Debian Bug report #748648,
regarding systemd-logind: logging noise in the kernel log
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.)
--
748648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-5+b1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
systemd-logind puts what seems like debugging messages in the kernel
log. Examples:
systemd-logind[2790]: Failed to start user service: Unknown unit:
user@106.service
systemd-logind[2790]: New session c1 of user lightdm.
systemd-logind[2790]: Failed to start user service: Unknown unit:
user@1000.service
systemd-logind[2790]: New session c2 of user bjorn.
Please remove this log noise. Use a debug log somewhere for this kind
of useless cruft. It's not like I need to know any of the above, and it
takes precious buffer space from the driver messages I'd like to see.
Bjørn
- -- Package-specific info:
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable'), (500, 'testing-updates'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.18.0-rc3 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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-53.4
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1
ii libblkid1 2.25.2-2
ii libc6 2.19-12
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
ii libpam0g1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-5+b1
ii sysv-rc 2.88dsf-53.4
ii udev215-5+b1
ii util-linux 2.25.2-2
Versions of packages systemd recommends:
ii dbus1.8.8-2
ii libpam-systemd 215-5+b1
Versions of packages systemd suggests:
pn systemd-ui
- -- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlRYosEACgkQ10rqkowbIsl6bACeIo9puIOLVRy+crVZ4inJUCq/
CH4An2FWC/DIFFo/HNhBUKDFcjuQ/X1V
=y4Ph
-END PGP SIGNATURE-
[OVERRIDDEN] /etc/udev/rules.d/40-usb_modeswitch.rules -> /lib/udev/rules.d/40-usb_modeswitch.rules
--- /lib/udev/rules.d/40-usb_modeswitch.rules 2014-06-09 11:21:49.0 +0200
+++ /etc/udev/rules.d/40-usb_modeswitch.rules 2012-11-10 21:18:02.0 +0100
@@ -1,12 +1,13 @@
-# Part of usb-modeswitch-data, version 20140529
+# Part of usb-modeswitch-data, version 20121109
#
-# Works with usb_modeswitch versions >= 2.2.0 (introduction of HuaweiNewMode)
+# Recommended use with USB_ModeSwitch >= 1.2.5, works with versions >= 1.0.3
+# (New style, interface class check moved to dispatcher)
#
ACTION!="add|change", GOTO="modeswitch_rules_end"
# Adds a symlink "gsmmodem[n]" to the lowest ttyUSB port with interrupt
# transfer; checked against a list of known modems, or else no action
-KERNEL=="ttyUSB*", ATTRS{bNumConfigurations}=="*", PROGRAM="usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}", SYMLINK+="%c"
+KERNEL=="ttyUSB*", ATTRS{bNumConfigurations}=="*", PROGRAM="usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}", SYMLINK="%c"
SUBSYSTEM!="usb", GOTO="modeswitch_rules_end"
@@ -20,36 +21,18 @@
ACTION!="add", GOTO="modeswitch_rules_end"
-# Generic entry for all Huawei devices
-ATTRS{idVendor}=="12d1", ATTR{bInterfaceNumber}=="00", ATTR{bInterfaceClass}=="08", RUN+="usb_modeswitch '%b/%k'"
-
# HP LaserJet Professional P1102
ATTR{idVendor}=="03f0", ATTR{idProduct}=="002a", RUN+="usb_modeswitch '%b/%k'"
-# Quanta 1KR / USB-lte 7410
-ATTR{idVendor}=="0408", ATTR{idProduct}=="ea17", RUN+="usb_modeswitch '%b/%k'"
-
-# Quanta 1K3 LTE
-ATTR{idVendor}=="0408", ATTR{idProduct}=="ea25", RUN+="usb_modeswitch '%b/%k'"
-
-# Quanta MobileGenie 4G lte
-ATTR{idVendor}=="0408", ATTR{idProduct}=="ea43", RUN+="usb_modeswitch '%b/%k'"
-
# Yota Router (Quanta 1QDLZZZ0ST2)
ATTR{idVendor}=="0408", ATTR{idProduct}=="f000", RUN+="usb_modeswitch '%b/%k'"
-# SpeedUp SU-8500U
-AT
Bug#794492: marked as done (systemd: Loginctl displays no sessions after waking up from suspend.)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #794492, regarding systemd: Loginctl displays no sessions after waking up from suspend. 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.) -- 794492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd Version: 222-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Waking-up from a suspend. * What exactly did you do (or not do) that was effective (or ineffective)? Reboot is effective. And useless - I want a suspend, not a power off. Reproducing is simple - suspend, and wake up. Nothing in the "loginctl list-sessions", so no suspend from GUI possible any more. * What was the outcome of this action? Of the reboot? Well - running system, what else? * What outcome did you expect instead? Before someone improves systemd even more - no, no, I wanted my system to tun after the reboot. Correct this utter c.r.a.p. some other way, possibly just mv it to /dev/null, please. *** End of the template - remove these template lines *** -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages systemd depends on: ii adduser 3.113+nmu3 ii libacl1 2.2.52-2 ii libapparmor12.9.2-3 ii libaudit1 1:2.4.2-1 ii libblkid1 2.26.2-6 ii libc6 2.19-19 ii libcap2 1:2.24-9 ii libcap2-bin 1:2.24-9 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod221-1 ii liblzma55.1.1alpha+20120614-2.1 ii libmount1 2.26.2-6 ii libpam0g1.1.8-3.1 ii libseccomp2 2.2.1-2 ii libselinux1 2.3-2+b1 ii libsystemd0 222-2 ii mount 2.26.2-6 ii sysv-rc 2.88dsf-59.2 ii udev222-2 ii util-linux 2.26.2-6 Versions of packages systemd recommends: ii dbus1.8.20-1 ii libpam-systemd 222-2 Versions of packages systemd suggests: ii systemd-ui 3-4 -- Configuration Files: /etc/systemd/logind.conf changed: [Login] HandleLidSwitch=ignore -- no debconf information [EXTENDED] /lib/systemd/system/rc-local.service -> /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/clamav-daemon.socket -> /etc/systemd/system/clamav-daemon.socket.d/extend.conf [EQUIVALENT] /etc/systemd/system/ipsec.service -> /lib/systemd/system/ipsec.service 4 overridden configuration files found. ==> /var/lib/systemd/deb-systemd-helper-enabled/openvpn.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/openvpn.service ==> /var/lib/systemd/deb-systemd-helper-enabled/acpid.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/acpid.service ==> /var/lib/systemd/deb-systemd-helper-enabled/uuidd.service.dsh-also <== /etc/systemd/system/sockets.target.wants/uuidd.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/uuidd.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/uuidd.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/cron.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/cron.service ==> /var/lib/systemd/deb-systemd-helper-enabled/acpid.socket.dsh-also <== /etc/systemd/system/sockets.target.wants/acpid.socket ==> /var/lib/systemd/deb-systemd-helper-enabled/ipsec.service <== ==> /var/lib/systemd/deb-systemd-helper-enabled/netfilter-persistent.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/netfilter-persistent.service ==> /var/lib/systemd/deb-systemd-helper-enabled/gfmd.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/gfmd.service ==> /var/lib/systemd/deb-systemd-helper-enabled/clamav-freshclam.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/clamav-freshclam.service ==> /var/lib/systemd/deb-systemd-helper-enabled/mcstrans.service.dsh-also <== /etc/systemd/system/multi-user.target.wants/mcstrans.service ==> /var/lib/systemd/deb-syste
Bug#771429: marked as done (systemd-shim: XFCE file manager can't mount removable SD devices)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #771429, regarding systemd-shim: XFCE file manager can't mount removable SD devices 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.) -- 771429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 9-1 Severity: important I have two systems on which I've seen this issue. I can click on the SD drive icon, and get: Unable to access "devicename" Not authorized to perform operation I switched one of my systems to using systemd as init, which cured this problem, so I am led to believe that the issue is in systemd-shim. John -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-shim depends on: ii cgmanager 0.33-2 ii libc6 2.19-13 ii libglib2.0-0 2.42.0-2 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: ii pm-utils 1.4.1-15 -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#811501: marked as done (systemd-shim process is not stopped on remove)
Your message dated Sat, 01 Dec 2018 03:05:54 +
with message-id
and subject line Bug#915038: Removed package(s) from unstable
has caused the Debian Bug report #811501,
regarding systemd-shim process is not stopped on remove
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.)
--
811501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-sysv
Version: 228-4
Severity: important
If sysvinit-core is the active PID 1 and systemd-shim is installed and
running, installing systemd-sysv will lead to an unclean shutdown and a
dirty file system on the next boot.
Afaics, the problem is, that /sbin/{reboot,poweroff,shutdown} as shipped
by systemd-sysv does not talk to PID 1 via /run/initctl but uses D-Bus
if the org.freedesktop.systemd1 D-Bus name is taken, which is the case
if systemd-shim is installed.
Purging systemd-shim and stopping the systemd-shim process leads to
clean shutdown.
One could argue, that this is a bug in systemd-shim, which should be
able to shutdown/reboot the system cleanly when requested by tools
provided by systemd-sysv.
I'm filing this against systemd-sysv for now though, Maybe there is a
way how we can workaround this in systemctl, like say in
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl.c#L7425
add a check for sd_booted before trying to talk to systemd via D-Bus.
Michael
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-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
Init: systemd (via /run/systemd/system)
Versions of packages systemd-sysv depends on:
ii systemd 228-4
systemd-sysv recommends no packages.
systemd-sysv suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 10-3+rm
Dear submitter,
as the package systemd-shim has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/915038
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#811502: marked as done (systemd-shim fails to shutdown after switch to systemd-sysv)
Your message dated Sat, 01 Dec 2018 03:05:54 +
with message-id
and subject line Bug#915038: Removed package(s) from unstable
has caused the Debian Bug report #811502,
regarding systemd-shim fails to shutdown after switch to systemd-sysv
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.)
--
811502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-sysv
Version: 228-4
Severity: important
If sysvinit-core is the active PID 1 and systemd-shim is installed and
running, installing systemd-sysv will lead to an unclean shutdown and a
dirty file system on the next boot.
Afaics, the problem is, that /sbin/{reboot,poweroff,shutdown} as shipped
by systemd-sysv does not talk to PID 1 via /run/initctl but uses D-Bus
if the org.freedesktop.systemd1 D-Bus name is taken, which is the case
if systemd-shim is installed.
Purging systemd-shim and stopping the systemd-shim process leads to
clean shutdown.
One could argue, that this is a bug in systemd-shim, which should be
able to shutdown/reboot the system cleanly when requested by tools
provided by systemd-sysv.
I'm filing this against systemd-sysv for now though, Maybe there is a
way how we can workaround this in systemctl, like say in
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl.c#L7425
add a check for sd_booted before trying to talk to systemd via D-Bus.
Michael
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-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
Init: systemd (via /run/systemd/system)
Versions of packages systemd-sysv depends on:
ii systemd 228-4
systemd-sysv recommends no packages.
systemd-sysv suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 10-3+rm
Dear submitter,
as the package systemd-shim has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/915038
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#838525: marked as done (systemd-shim error prevents login to desktop on ppc)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #838525, regarding systemd-shim error prevents login to desktop on ppc 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.) -- 838525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-2 If systemd-shim and sysvinit-core are installed on PPC970MP (PPC64) system running Stretch Alpha 7 (bug also appears in Jessie 8.6 with systemd-shim 9-1), the system will not boot to desktop and the below error message is generated after logging in via TTY: [ 646.474008] systemd-logind(2208): Failed to start user service, ignoring: Unknown Unit: user@1000.service --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#893819: marked as done (systemd-shim: logind does not create a session, because systemd-shim does not create /init.scope like systemd does)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #893819, regarding systemd-shim: logind does not create a session, because systemd-shim does not create /init.scope like systemd does 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.) -- 893819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: important Preface: Some software begins to depends on an existing logind-session. These sessions are created + tracked via libpam-systemd, which makes an dbus call to systemd-logind. systemd-shim it here to support logind, which replaces consolekit (AFAIUI) on systems where systemd is not the init process (i.e. pid 1). Problem: In auth.log: login[6880]: pam_systemd(login:session): Failed to create session: No such device or address The message belongs to -ENXIO, which is emitted here: https://github.com/systemd/systemd/blob/master/src/basic/cgroup-util.c#L1458 Result: $ loginctl SESSIONUID USER SEAT TTY 0 sessions listed. Expected result: $ loginctl [... some sessions ...] Root cause: $ systemd-cgls Control group /: -.slice ├─ 1 init [2] ├─1630 /lib/systemd/systemd-udevd --daemon ├─3661 /sbin/rpcbind -w [...] $ cat /proc/1/cgroup# or some other pid 4:name=systemd:/ [...] But since systemd 226 (AFAICT), all pids are moved (by systemd as init) into the /init.scope cgroup. In the systemd-shim case, systemd-logind still expects pid 1 and the pid of the login process to be in a such named cgroup - but fails, because everything is in the root slice (-.slice) and "nothing comes after the /". Evidence: $ mkdir /sys/fs/cgroup/systemd/init.scope $ echo 1 > /sys/fs/cgroup/systemd/init.scope/tasks # ... move login process (kdm/mingetty/...) there, too ... # e.g. by respawning mingetty on a particular tty, e.g. tty4 $ systemd-cgls # or: cat /proc/$PID/cgroup [... those two processes are indeed now in the new cgroup ...] Now login on that tty4, so that the login process is (resp. will be spawned in) the /init.scope cgroup. $ loginctl [...] 1 sessions listed. Required action: systemd-shim has to adjust the cgroups (using cgmanager?) accordingly for systemd-logind (and thus pam-logind) to succeed. Thank you. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (x86_64) Kernel: Linux 4.16.0-rc6 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-shim depends on: ii cgmanager 0.41-2 ii libc6 2.27-2 ii libglib2.0-0 2.53.4-3 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: ii pm-utils 1.4.1-9 -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#883555: marked as done (systemd-shim should be Multi-Arch: foreign)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #883555, regarding systemd-shim should be Multi-Arch: foreign 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.) -- 883555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883555 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt Version: 1.6~alpha5 User: helm...@debian.org Usertags: rebootstrap Control: affects -1 + src:kde-gtk-config I noticed that apt-get build-dep --arch-only -a mips kde-gtk-config fails in an amd64 chroot. The final message is that libgtk-3-dev:mips was not installable. Now why do I think this is a bug? 1. dose-builddebcheck thinks that kde-gtk-config is satisfiable. 2. If I install libgtk-3-dev:mips before issuing that command, it succeeds (and replaces systemd-shim with systemd-sysv). 3. If I install systemd-sysv before that command, it succeeds. It seems a bit like apt is first resolving the tree around libgtk-3-dev using systemd-shim and then fails to back down to systemd-sysv for the full tree. I note that libpam-systemd has a dependency (with this order) on "systemd-shim | systemd-sysv". If the issue is not immediately reproducible in an amd64 sid chroot, try using http://snapshot.debian.org/archive/debian/20171205T034902Z/. I'll append the full resolver output from sbuild (which is not apt-get build-dep, but close) to the end of this mail. Helmut Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-kde-gtk-config-dummy:mips : Depends: libgtk-3-dev:mips but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use du: cannot access '/<>': No such file or directory E: read_command failed to execute du E: Cannot determine space needed for /<> (du failed) Reading package lists... Building dependency tree... Reading state information... MarkInstall sbuild-build-depends-kde-gtk-config-dummy:mips < none -> 0.invalid.0 @un puN Ib > FU=1 Installing libc6-dev as Depends of sbuild-build-depends-kde-gtk-config-dummy MarkInstall libc6-dev:mips < none -> 2.25-3 @un uN Ib > FU=0 Installing libc6 as Depends of libc6-dev MarkInstall libc6:mips < none -> 2.25-3 @un uN Ib > FU=0 Installing libgcc1 as Depends of libc6 MarkInstall libgcc1:mips < none -> 1:7.2.0-16 @un uN Ib > FU=0 Installing gcc-7-base as Depends of libgcc1 MarkInstall gcc-7-base:mips < none -> 7.2.0-16 @un uN > FU=0 Installing linux-libc-dev as Depends of libc6-dev MarkInstall linux-libc-dev:mips < none -> 4.14.2-1 @un uN > FU=0 Installing libstdc++-7-dev as Depends of sbuild-build-depends-kde-gtk-config-dummy MarkInstall libstdc++-7-dev:mips < none -> 7.2.0-16 @un uN Ib > FU=0 Installing libgcc-7-dev as Depends of libstdc++-7-dev MarkInstall libgcc-7-dev:mips < none -> 7.2.0-16 @un uN Ib > FU=0 Installing libgomp1 as Depends of libgcc-7-dev MarkInstall libgomp1:mips < none -> 7.2.0-16 @un uN > FU=0 Installing libatomic1 as Depends of libgcc-7-dev MarkInstall libatomic1:mips < none -> 7.2.0-16 @un uN > FU=0 Installing libstdc++6 as Depends of libstdc++-7-dev MarkInstall libstdc++6:mips < none -> 7.2.0-16 @un uN > FU=0 Installing cmake as Depends of sbuild-build-depends-kde-gtk-config-dummy MarkInstall cmake:amd64 < none -> 3.9.5-1 @un uN Ib > FU=0 Installing cmake-data as Depends of cmake MarkInstall cmake-data:amd64 < none -> 3.9.5-1 @un uN > FU=0 Installing procps as Depends of cmake MarkInstall procps:amd64 < none -> 2:3.3.12-3 @un uN Ib > FU=0 Installing libncurses5 as Depends of procps MarkInstall libncurses5:amd64 < none -> 6.0+20171125-1 @un uN > FU=0 Installing libprocps6 as Depends of procps MarkInstall libprocps6:amd64 < none -> 2:3.3.12-3 @un uN > FU=0 Installing lsb-base as Depends of procps MarkInstall lsb-base:amd64 < none -> 9.20170808 @un uN > FU=0 Installing libarchive13 as Depends of cma
Bug#875574: marked as done (systemd-shim: sdccard change events not detected under sysvinit)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #875574, regarding systemd-shim: sdccard change events not detected under sysvinit 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.) -- 875574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: normal Dear Maintainer, I have noticed yet another thing that works in systemd but not in sysvinit, so I guess it is systemd-shim issue. When using sysvinit, when I introduce an sdcard in the reader sdcard change event is not detected and no device is created by udev. It is recognised if sdcard is already present during boot or if partprobe is run after inserting sdcard. Trying to access the full device (e.g., trying to mount /dev/sde instead of /dev/sde1) fails as expected, but seems to also trigger detection for later usage. Since this works under systemd I guess there is a missing feature in systemd-shim. I am aware that systemd-shim is orphaned, so I am filing this bug report to at least have this issue documented. Regards, -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8), LANGUAGE=es_ES.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages systemd-shim depends on: ii cgmanager 0.41-2 ii libc6 2.24-17 ii libglib2.0-0 2.54.0-1 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: ii pm-utils 1.4.1-17 -- no debconf information -- Agustin --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#901404: marked as done (systemd-shim: Please dpkg-divert the dbus services you want dbus-activatable)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #901404, regarding systemd-shim: Please dpkg-divert the dbus services you want dbus-activatable 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.) -- 901404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: shim-patches-removal Hello Debian systemd-shim Maintainers, The Debian systemd package is currently carrying a debian-specific patch to enable usage of various systemd daemons via systemd-shim on Debian systems. In particular, it patches several systemd services to make them activatable by DBus. [1] Unfortunately none of the systemd maintainers actively tests the non-systemd code paths in those daemons anymore, so we don't feel comfortable enabling those services for sysvinit in the systemd package itself. systemd-shim already has code to dpkg-divert a dbus service provided by systemd, so we think systemd-shim should take over the divert of the rest of the units which it wants to support to run under sysvinit. We intend to drop the patch before buster is released in the not too distant future. When we do that, we will bump the severity of this bug report to serious. [1] https://salsa.debian.org/systemd-team/systemd/blob/debian/238-1/debian/patches/debian/Make-logind-hostnamed-localed-timedated-D-Bus-activa.patch Saludos, Felipe Sateler -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-shim depends on: pn cgmanager ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: pn pm-utils --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#895418: marked as done (systemd-shim: incompatibility with a new version of systemd)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #895292, regarding systemd-shim: incompatibility with a new version of systemd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 895292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: important Affects: gdm3 Hi, I admit I didn't spend much time investigating this issue (I need a working Sid box), but from past experience, I guess it comes from a new systemd-shim incompatibility introduced by some change in systemd-logind (or GDM, but IMHO it's less unlikely than systemd). The symptoms are identical to #801749 (but since people there mention journalctl, I guess they were not using SysV init, so it can't be a duplicate of this bug): GDM doesn't start (the screen keeps displaying the console, with the cursor blinking frenetically), and syslog shows lots and lots of "gdm3: Child process XYZ was already dead." and "gdm3: Unable to kill session worker process". lightdm (under SysV init) does start normally. Switching the init system to systemd gets rid of the problem, and allows GDM to start normally (this is why I'm filing this report against systemd-shim). Please note that I didn't try to downgrade systemd or GDM to find the exact culprit (or the version introducing the change), I made an educated guess and switched the init system directly, which worked. I have a lot of stuff to do on my Sid box ATM and I can't afford the time. Please also note that I don't reboot this box very often, so the incompatibility may have been introduced by a systemd update a long time ago, not necessarily the latest one. Regards, -- Raphaël Halimi --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#903295: marked as done (libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #903295, regarding libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed 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.) -- 903295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: grave Justification: renders package unusable Dear Maintainer, I am running sysvinit-core based desktop Debian system (sid). When recently trying to dist-upgrade, libpam-systend package requires systemd-shim version >=10-4~ but there is no such version in repositories. The only alternative is replacing sysvinit-core with systemd-sysv i.e. running systemd as init system. This renders package systemd-shim unusable. root@hpsiddie:/home/manul# apt-get dist-upgrade -d sysvinit-core+ libpam-systemd+ Reading package lists... Done Building dependency tree Reading state information... Done sysvinit-core is already the newest version (2.88dsf-59.10). Calculating upgrade... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpam-systemd : Depends: systemd-shim (>= 10-4~) but it is not going to be installed or systemd-sysv but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages systemd-shim depends on: ii cgmanager 0.41-2 ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: ii pm-utils 1.4.1-18 -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#907486: marked as done (libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #903295, regarding libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed 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.) -- 903295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-systemd Version: 238-5 Severity: grave Justification: renders package unusable Dear Maintainer, (This bug has been reported also against systemd-shim: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 ) libpam-systemd requires systemd-shim version >=10-4~. No such version exists. This would make systemd-shim unusable. root@hpsiddie:/home/manul# apt-get dist-upgrade -d sysvinit-core+ libpam-systemd+ Reading package lists... Done Building dependency tree Reading state information... Done sysvinit-core is already the newest version (2.88dsf-59.10). Calculating upgrade... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpam-systemd : Depends: systemd-shim (>= 10-4~) but it is not going to be installed or systemd-sysv but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (600, 'testing-debug'), (600, 'testing'), (400, 'unstable-debug'), (400, 'unstable'), (200, 'experimental-debug'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=es_US.UTF-8, LC_CTYPE=es_US.UTF-8 (charmap=UTF-8), LANGUAGE=es_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages libpam-systemd depends on: ii dbus1.12.10-1 ii libc6 2.27-5 ii libpam-runtime 1.1.8-3.8 ii libpam0g1.1.8-3.8 ii systemd 238-5 ii systemd-shim10-3 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#914285: marked as done (systemd-shim: prevents calling GetDynamicUsers() and other recent APIs on systemd Manager)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #914285, regarding systemd-shim: prevents calling GetDynamicUsers() and other recent APIs on systemd Manager 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.) -- 914285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dbus Version: 1.12.10-1 Severity: minor dbus generates over 100 lines a day like this in auth.log: Nov 21 13:20:39 tucano dbus-daemon[3507]: [system] Rejected send message, 4 matched rules; type="method_call", sender=":1.383314" (uid=1000 pid=2330 comm="/usr/bin/dbus-daemon --syslog --fork --print-pid 5") interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/lib/systemd/systemd --system --deserialize 538 ") This happens while I work at the console, but not when I work remotely. Using the atop logs, I can tell that process 2330 was a dbus-daemon starting and ending at 13:20:39. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (101, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=C:en_GB:en:en_US:it:fr:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dbus depends on: ii adduser 3.118 ii libapparmor1 2.13.1-3+b1 ii libaudit1 1:2.8.4-2 ii libc6 2.27-8 ii libcap-ng00.7.9-1 ii libdbus-1-3 1.12.10-1 ii libexpat1 2.2.6-1 ii libselinux1 2.8-1+b1 ii libsystemd0 239-12 ii lsb-base 9.20170808 dbus recommends no packages. Versions of packages dbus suggests: ii dbus-user-session [default-dbus-session-bus] 1.12.10-1 ii dbus-x11 [dbus-session-bus] 1.12.10-1 Versions of packages dbus is related to: ii dbus-x11 1.12.10-1 ii systemd 239-12 ii systemd-sysv 239-12 -- no debconf information --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#901405: marked as done (systemd-shim: Please add a sysvinit service to create directories on /run at boot)
Your message dated Sat, 01 Dec 2018 03:05:54 + with message-id and subject line Bug#915038: Removed package(s) from unstable has caused the Debian Bug report #901405, regarding systemd-shim: Please add a sysvinit service to create directories on /run at boot 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.) -- 901405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: systemd-shim Version: 10-3 Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: shim-patches-removal Hello Debian systemd-shim Maintainers, The Debian systemd package is currently carrying two debian-specific patches to enable usage of systemd-shim on Debian systems. In particular, we patch some code to continue even if /run/systemd/machines/ and /run/systemd/machines/ don't exist[1][2]. These two patches could be avoided if systemd-shim would create the relevant directories during early boot (sometime in rcS). Therefore we would like for systemd-shim to provide these directories so we can drop these patches. If you ship such a SysV init script, please make sure to mask that, so it is not accidentally run when systemd is the active PID 1 (assuming the SysV init script is called /etc/init.d/systemd-shim, the symlink would be /lib/systemd/system/systemd-shim.service → /dev/null). We intend to drop the patches before buster is released in the not too distant future. When we do that, we will bump the severity of this bug report to serious. [1] https://salsa.debian.org/systemd-team/systemd/blob/debian/238-1/debian/patches/debian/Start-logind-on-demand-via-libpam-systemd.patch [2] https://salsa.debian.org/systemd-team/systemd/blob/debian/238-1/debian/patches/debian/Make-sd_login_monitor_new-work-for-logind-without-sy.patch Saludos, Felipe Sateler -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-shim depends on: pn cgmanager ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 systemd-shim recommends no packages. Versions of packages systemd-shim suggests: pn pm-utils --- End Message --- --- Begin Message --- Version: 10-3+rm Dear submitter, as the package systemd-shim has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/915038 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
libsoundio is marked for autoremoval from testing
libsoundio 1.0.2-2 is marked for autoremoval from testing on 2018-12-15 It is affected by these RC bugs: 835590: libsoundio1: Missing hard dependency on libjack-jackd2-0
