Summary: | systemd --user process segfaults randomly | ||
---|---|---|---|
Product: | systemd | Reporter: | Abdó Roig-Maranges <abdo.roig> |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | CC: | abdo.roig |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Abdó Roig-Maranges
2014-03-06 21:36:26 UTC
I took an other look at the journal, and it seems it may have to do with a sudo root session. I hadn't noticed the close timestamps before, and figured the crash was random. Here is the relevant piece of journal: Mar 06 20:41:40 grothendieck sudo[957]: abdo : TTY=pts/3 ; PWD=/home/abdo ; USER=root ; COMMAND=/usr/bin/pacman -U /home/abdo/opt/paur/build/linkchecker-dev/linkchecker-dev-20140305.11-1-any.pkg.tar.xz Mar 06 20:41:40 grothendieck sudo[957]: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 06 20:41:40 grothendieck sudo[957]: pam_unix(sudo:session): session closed for user root Mar 06 20:41:40 grothendieck sudo[984]: abdo : TTY=pts/3 ; PWD=/home/abdo ; USER=root ; COMMAND=/usr/bin/pacman -U /home/abdo/opt/paur/build/emacs-yasnippet-dev/emacs-yasnippet-dev-20140306.2-1-x86_64.pkg.tar.xz Mar 06 20:41:40 grothendieck sudo[984]: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 06 20:41:40 grothendieck kernel: systemd[594]: segfault at b8 ip 000000000048101e sp 00007fffa11deb60 error 4 in systemd[400000+106000] Mar 06 20:41:40 grothendieck systemd-coredump[991]: Process 594 (systemd) dumped core. The backtrace looks corrupted. Any chance you can trigger this with an unstripped systemd binary and then get us a correctl backtrace? I'm running an unstripped systemd since yesterday, waiting for it to blow up again. It may take some time, since I don't know how to trigger it. I forgot about this. It got fixed after some upgrade. I'll mark it as resolved then! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.