On 22/02/2015 20:40, Eric Valette wrote:
On 22/02/2015 20:34, Michael Biebl wrote:
Am 22.02.2015 um 20:30 schrieb Eric Valette:
seems close. And yes I have no login. Once I had the graphic start but
no kdm... Could try to extract journald from 218 and see if the bug
vanishes.
Martin identifie
On 22/02/2015 20:34, Michael Biebl wrote:
Am 22.02.2015 um 20:30 schrieb Eric Valette:
seems close. And yes I have no login. Once I had the graphic start but
no kdm... Could try to extract journald from 218 and see if the bug
vanishes.
Martin identified [1] commit 13790add4bf64 as the problema
Am 22.02.2015 um 20:30 schrieb Eric Valette:
> seems close. And yes I have no login. Once I had the graphic start but
> no kdm... Could try to extract journald from 218 and see if the bug
> vanishes.
Martin identified [1] commit 13790add4bf64 as the problematic one.
You could try rebuilding v219
On 22/02/2015 20:21, Michael Biebl wrote:
Am 22.02.2015 um 11:59 schrieb Eric Valette:
Package: dbus
Version: 1.9.10-3
Severity: important
Since update to this experimental version and systemd 219,
I experience frequend lockup at boot, after systemd display
(from memory) "Starting dbus daemon".
Am 22.02.2015 um 11:59 schrieb Eric Valette:
> Package: dbus
> Version: 1.9.10-3
> Severity: important
>
> Since update to this experimental version and systemd 219,
> I experience frequend lockup at boot, after systemd display
> (from memory) "Starting dbus daemon". I have experienced
> this on t
5 matches
Mail list logo
