Package: systemd Version: 215-7 Severity: important Dear Maintainer,
after upgrading the systemd package, some things stop working (at least after a suspend-resume cycle): * Clicking the WiFi checkbox in NetworkManager to enable WiFi has no effect (I am using the KDE frontend). I tried "rfkill unblock" with both IDs related to my WiFi card, to no avail. I even re-loaded the kernel module, again no success. * Selecting "Reboot" in the K-Menu just logs me out. I have to select "reboot" again in lightdm to get a reboot. After the reboot, WiFi behaving as usual again. This happened with both recent systemd upgrades (215-6 and 215-7). I did not yet do further testing to reproduce the issue, in case this is already well-known. However, if necessary, I can do that. Just let me know which information is most useful for you. Note: This may well be RC (after all, it breaks other software). I leave that decision up to you. Kind regards, Ralf -- Package-specific info: -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.0+ (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 Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.2-3 ii libc6 2.19-13 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libgcrypt20 1.6.2-4+b1 ii libkmod2 18-3 ii liblzma5 5.1.1alpha+20120614-2+b2 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-7 ii mount 2.25.2-3 ii sysv-rc 2.88dsf-58 ii udev 215-7 ii util-linux 2.25.2-3 Versions of packages systemd recommends: ii dbus 1.8.12-1 ii libpam-systemd 215-7 Versions of packages systemd suggests: ii systemd-ui 3-2 -- Configuration Files: /etc/systemd/journald.conf changed: [Journal] SystemMaxUse=200M -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
