http://bugzilla.opensuse.org/show_bug.cgi?id=918158 Bug ID: 918158 Summary: error 4 segfault in systemd and systemd-udev Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: ivan.topolsky@isb-sib.ch QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 Build Identifier: systemd-udevd[772]: segfault at 18 ip 00007fa5e0700a55 sp 00007fffc57d9f70 error 4 in libc-2.19.so[7fa5e0688000+19e000] followed a little bit later by: kernel:[73256.715384] systemd[1]: segfault at 7ce00000 ip 0000000000460384 sp 00007fff16f78d70 error 4 in systemd[400000+114000] broadcast on all terminals. Reproducible: Sometimes Steps to Reproduce: (0. not sure about this step: the first crash in systemd-udev might happen after resume from "Suspend-to-RAM") 1. "zypper update" 2. zypper updates a service (cups in my last occurence) 3. zypper restarts a service Actual Results: segfault broadcast on all terminal. systemd dies. systemctl is unresponsive. SysRq magic key is the only way to (more or less) cleanly restart the system Expected Results: systemd should NOT die. (Or at least, there should be a clean way to reload it) started following a recent upgrade of the system from the official opensuse update repository. might be related to glib2 problems that plague my KDE desktop. Similar to this: https://bugzilla.redhat.com/show_bug.cgi?id=1071128 https://bbs.archlinux.org/viewtopic.php?id=177801 Related to this (similar results, different component of systemd) : https://bugzilla.opensuse.org/show_bug.cgi?id=905369 -- You are receiving this mail because: You are on the CC list for the bug.