Did you actually boot with systemd as PID1? Note that this isn't
supported in Ubuntu 14.10 (only upstart). On current vivid, running
"journalctl" under upstart just exits cleanly with 1. Can you reproduce
this crash easily, i. e. does it still happen on your system if you run
journalctl? (the stack trace isn't very helpful, I'm afraid).
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Information type changed from Private to Public
--
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/1389355
Title:
systemd-journald crashed with signal 7
Status in systemd package in Ubuntu:
Incomplete
Bug description:
I am not sure how I triggered this.
What I can say is that journalctl does not find any journals to show.
nazgul@rivendell:~$ journalctl
No journal files were found.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: systemd 208-8ubuntu8 [modified:
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Tue Nov 4 01:21:58 2014
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2013-01-08 (665 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcCmdline: /lib/systemd/systemd-journald
Signal: 7
SourcePackage: systemd
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: systemd-journald crashed with signal 7
UpgradeStatus: Upgraded to utopic on 2014-10-23 (12 days ago)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1389355/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
