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 identified [1] commit 13790add4bf64 as the problematic one.
You could try rebuilding v219 with that commit reverted.
Maybe you can confirm that this is indeed the same issue.
OK will try to do that but probably not today. If I find it also at work
tomorrow, maybe tomorrow. So far I have it on all machines I tried but
not always...
I decided to give it a try anyway. I had to reboot my laptop 4 times
before been able to log in.
After doing apt-get source systemd I tried to apply the patch but
unfortunately it does not apply on 219 but on upstream git:
patch -p1 -R --dry-run -i ../revertJournald.patch
checking file src/journal/journald-server.c
Unreversed patch detected! Ignore -R? [n]
Apply anyway? [n] y
Hunk #1 FAILED at 1182.
Hunk #2 succeeded at 1455 (offset -11 lines).
Hunk #3 succeeded at 1552 (offset -10 lines).
1 out of 3 hunks FAILED
checking file src/journal/journald-stream.c
checking file src/journal/journald-stream.h
checking file units/systemd-journald.service.in
Hunk #1 succeeded at 23 with fuzz 1.
Will see if the succeeding hunks are sufficient...
-- eric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
