severity 742322 important
forwarded 742322 https://bugs.freedesktop.org/show_bug.cgi?id=76899
thanks
Am 31.03.2014 08:24, schrieb Didier 'OdyX' Raboud:
Le jeudi, 27 mars 2014, 02.32:58 Michael Biebl a écrit :
OdyX, I took the liberty to CC you.
So this issue is indeed triggered by CUPS and the
Le jeudi, 27 mars 2014, 02.32:58 Michael Biebl a écrit :
OdyX, I took the liberty to CC you.
So this issue is indeed triggered by CUPS and the way it sets up the
socket configuration.
Yay, thanks. I suspected that this was causing the problem but couldn't
reproduce it, now we do have a trail.
Hi,
On 27.03.2014 02:29, Michael Biebl wrote:
Thanks a lot for the back trace!
I'm glad I could help.
This helped me to reproduce the sequence of events which need to happen
to trigger the abort. So this is good news (well sort of).
This is great news, at least for me, as I now can reboot
Hi,
I build systemd with debugging symbols and extracted a backtrace from
the core dump:
#0 0x7f1a0b51a75b in raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
#1 0x0040ca85 in crash (sig=6) at ../src/core/main.c:142
#2 signal handler called
#3
Am 26.03.2014 17:39, schrieb Andreas Cadhalpun:
Hi,
I build systemd with debugging symbols and extracted a backtrace from
the core dump:
Thanks a lot for the back trace!
This helped me to reproduce the sequence of events which need to happen
to trigger the abort. So this is good news (well
Am 27.03.2014 02:29, schrieb Michael Biebl:
Am 26.03.2014 17:39, schrieb Andreas Cadhalpun:
The sequence of events is
a/ make sure cups.socket is running and correctly setup
b/ make sure cups.service is not running
c/ make /etc/systemd/system/cups.socket.d/cupsd-listen.conf a dangling
Am 27.03.2014 02:29, schrieb Michael Biebl:
Am 26.03.2014 17:39, schrieb Andreas Cadhalpun:
The sequence of events is
a/ make sure cups.socket is running and correctly setup
b/ make sure cups.service is not running
c/ make /etc/systemd/system/cups.socket.d/cupsd-listen.conf a dangling
7 matches
Mail list logo
