Bug#728026: systemd: timeout opening/writing control channel /run/initctl + Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused

2013-11-02 Thread Michael Stapelberg
control: reassign -1 src:linux linux/3.11 control: found -1 linux/3.12 control: retitle -1 userspace apps using epoll_wait have their memory corrupted control: noowner -1 Hi, Axel and I looked into this yesterday and realized that systemd segfaults (as visible in the “journalctl” output after

Processed: Re: Bug#728026: systemd: timeout opening/writing control channel /run/initctl + Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused

2013-11-02 Thread Debian Bug Tracking System
Processing control commands: reassign -1 src:linux linux/3.11 Bug #728026 [systemd] systemd: timeout opening/writing control channel /run/initctl + Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused Bug reassigned from package 'systemd' to

Bug#728026: systemd: timeout opening/writing control channel /run/initctl + Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: Connection refused

2013-10-27 Thread Axel Beckert
Package: systemd Version: 204-3 Severity: grave Justification: no more able to shutdown system except by turning off power Dear Systemd Maintainers, first sorry for the late bug report. The following happened the first time on 13th of September 2013 (i.e. shortly after the 204-3 upload while