[Touch-packages] [Bug 1433426] Re: systemd crashed with SIGSEGV in _IO_acquire_lock_fct()

2015-03-25 Thread dino99
Closing that report now, as it has been only seen 1 time. ** Changed in: systemd (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/14

[Touch-packages] [Bug 1433426] Re: systemd crashed with SIGSEGV in _IO_acquire_lock_fct()

2015-03-20 Thread dino99
Feedback That issue has not been seen since that report. So it may have been fixed by some package(s) upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1433426 Title:

[Touch-packages] [Bug 1433426] Re: systemd crashed with SIGSEGV in _IO_acquire_lock_fct()

2015-03-18 Thread Didier Roche
** Changed in: systemd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1433426 Title: systemd crashed with SIGSEGV in _IO_acquire_loc

[Touch-packages] [Bug 1433426] Re: systemd crashed with SIGSEGV in _IO_acquire_lock_fct()

2015-03-17 Thread dino99
Also found that segfault into journalctl, but does not know if it the same issue or an other one. systemd-udevd[369]: '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0' [494] terminated by signal 11 (Segmentation fault) systemd-udevd[371]: '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 1' [497