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
Control: reopen -1
Control: tags -1 - unreproducible moreinfo
Control: severity -1 critical
Justification: breaks many packages, even shutdown/reboot
Dear systemd maintainers,
I'm also hitting this bug. I upgraded systemd to 204-8 yesterday and now
upgrading cups-daemon to 1.7.1-10 failed,
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
Package: systemd
Version: 204-8
Severity: grave
Justification: breaks other packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I just upgraded from 204-7 to 204-8 and during the process all services which
needs to get restared fails to restart:
NOTE: I did *not* yet reboot; will check if
PS: Can't reboot by normal means:
LANG=C reboot
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.
current systemd status:
ps x | grep systemd
1 ?Ss 0:06 /lib/systemd/systemd --system --deserialize
17
558 pts/0S+ 0:00 grep systemd
Update:
After rebooting using Magic SysReq, system boots and apt-get install -f
completes
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 22.03.2014 12:35, schrieb coldtobi:
Failed to get D-Bus connection: Failed to connect to socket
/run/systemd/private: Connection refused
This is an indication that systemd crashed. If you can reproduce the
sequence of events to trigger this crash, please let us know and we'll
reopen the bug
Am 22.03.2014 13:45, schrieb Michael Biebl:
Am 22.03.2014 12:35, schrieb coldtobi:
Failed to get D-Bus connection: Failed to connect to socket
/run/systemd/private: Connection refused
This is an indication that systemd crashed. If you can reproduce the
sequence of events to trigger this
Package: systemd
Followup-For: Bug #742322
Control: -1 tags moreinfo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Is this the way systemd people generally respond to problem reports? Just
closing bugs and hide (possible) problems? I'm very disappointed. You know, in
Debian we do not hide
Can't reproduce by downgrading and re-upgrading. Stopping here putting effort
into systemd
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi coldtobi,
coldtobi t...@coldtobi.de writes:
Is this the way systemd people generally respond to problem reports? Just
closing bugs and hide (possible) problems? I'm very disappointed. You know, in
Debian we do not hide problems.
Typically I wouldn’t even respond to this, but your last
16 matches
Mail list logo
