Failed to set wall message, ignoring: Message recipient disconnected from message bus without replying

[David Oxland]

Tried to shutdonw in 3 min
got this message.
 repeatable happened yesterday as well
15.04

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 12 22:54:23 2015
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2015-01-29 (226 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 10117
ProcCmdline: /lib/systemd/systemd-logind
ProcEnviron:
 LANG=en_CA.UTF-8
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
SegvAnalysis:
 Segfault happened at: 0x7f1002cbc6fa <strlen+42>: movdqu (%rax),%xmm12
 PC (0x7f1002cbc6fa) ok
 source "(%rax)" (0x55907c000000) not located in a known VMA region (needed readable region)!
 destination "%xmm12" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: systemd
StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 __GI___strdup (s=0x55907c000000 <error: Cannot access memory at address 0x55907c000000>) at strdup.c:41
 ?? ()
 ?? ()
 ?? ()
Title: systemd-logind crashed with SIGSEGV in strlen()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: I7KT31AUS
dmi.board.vendor: LENOVO
dmi.board.version: 31900058 STD
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.modalias: dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr:
dmi.product.name: 10117
dmi.product.version: Lenovo H535
dmi.sys.vendor: LENOVO

[Apport retracing service (apport)]

StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:106
 __GI___strdup (s=0x55907c000000 <error: Cannot access memory at address 0x55907c000000>) at strdup.c:41
 free_and_strdup (p=0x55907c5f0168, s=0x55907c000000 <error: Cannot access memory at address 0x55907c000000>) at ../src/basic/util.c:6023
 method_set_wall_message.lto_priv.423 (message=0x55907c5fbcf0, userdata=0x55907c5f0010, error=0x7ffc36803fc0) at ../src/login/logind-dbus.c:2321
 method_callbacks_run (found_object=0x7ffc36804120, require_fallback=false, c=0x55907c5f65b0, m=0x55907c5fbcf0, bus=0x55907c5f2b80) at ../src/libsystemd/sd-bus/bus-objects.c:410

[Martin Pitt (pitti)]

This was fixed in https://launchpad.net/ubuntu/+source/systemd/225-1ubuntu4

* Fix shutdown with specifying a time.

[David Oxland (doxland)]

Anything that I need to do here?
Use alternate shutdown method, so that it won't keep reporting bugs? Alternate method being (on screen.)
Ignore?
Thanks

[Martin Pitt (pitti)]

Hello David,

David Oxland [2015-09-14 20:29 -0000]:
> Anything that I need to do here?
> Use alternate shutdown method, so that it won't keep reporting bugs? Alternate method being (on screen.)

After installing the current 15.04 version (225-1ubuntu4) and
rebooting once this should be gone; can you still reproduce it with
that?

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

[David Oxland (doxland)]

I don't use lubuntu at all
Just plain Ubuntu desktop 15.04

[Mark Thomas (markthomas)]

David,

That's not lubuntu, it's 1 (one) ubuntu 4.

[Martin Pitt (pitti)]

Apparently this still happens a lot, reopening.

[Martin Pitt (pitti)]

Trivially reproducible in a VM. So https://github.com/systemd/systemd/commit/3d1c455f9a8 fixed the timed shutdown (this does work now), but still leaves the crash. This works fine with 226, so we just need to find the commit to backport.

[Martin Pitt (pitti)]

Fixed with https://github.com/systemd/systemd/commit/91b3e7f, pulled that into the wily branch.

[David Oxland (doxland)]

Had a system problem
 Installed 14.04
It's not happened since.

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 225-1ubuntu5

---------------
systemd (225-1ubuntu5) wily; urgency=medium

  * Add microphone mute keymap for Dell Precision. (LP: #1494135)
  * Fix logind crash when setting wall messages (on timed shutdown).
    (LP: #1495178)
  * udev.postinst: Actually call upgrade_fixes(), so that the "disable
    persistent names on upgrades" quirk actually runs.
  * Revert networkd calling if-{up,post-down}.d/ scripts. About half of the
    existing hooks are not relevant or even actively detrimental when running
    with networkd. For the relevant ones, a lot of them should be fixed in the
    projects themselves (using IP_FREEBIND etc.). (Closes: #798625)
  * Add systemd-networkd-resolvconf-update.{path,service} units to send DNS
    server updates from networkd to resolvconf, if installed and enabled.

 -- Martin Pitt <email address hidden> Wed, 30 Sep 2015 15:37:09 +0200

[David Oxland (doxland)]

Mentioned on 2015-09-25 that I had to install 14.04. on and no problem since.
 It is or something similar is happening again.
 sudo shutdown 3 min brings me to black screen with power off indicated.
 but I come back a few minutes later and power on light is illuminated.
 -pushing it brings a 10 seconds of hard drive activity and then a power lamp is off for good.

[Brian Murray (brian-murray)]

The Error Tracker still has plenty of instances of a crash that was marked as a duplicate of this with versions of the package that should have been fixed.

https://errors.ubuntu.com/problem/a98c4726841f0104ae643afa816a2e765e36aee5

[Martin Pitt (pitti)]

This was perfectly reproducible until 225-1ubuntu4, and got fixed in 225-1ubuntu5. If you can still reproduce this crash (after a fresh boot), please tell me how. My gut feeling is that the version number of the recent duplicates is wrong as you probably upgraded to the latest version (which doesn't restart logind), then restarted the computer, so apport thought you already have the new package version?

[David Oxland (doxland)]

Shutdown via term.
Current, as described before with 14.04 LTS updated every day. and a few reboots from stopped machine.
Mentioned on 2015-09-25 that I had to install 14.04. on and no problem since.
 It is or something similar is happening again.
 sudo shutdown 3 min. brings me to black screen with power on indicated. .
 -pushing it brings a 10 seconds of hard drive activity and then a power lamp is off for good.

--Shutdown via Gui is as expected.

[Martin Pitt (pitti)]

@David: Note that this *only* affects Ubuntu 15.10. Ubuntu 14.04 doesn't even use systemd yet. You reported the bug against 15.10, so I figure that's what you had installed at that time.

[Martin Pitt (pitti)]

Curiously this gets fixed by https://github.com/systemd/systemd/commit/2cf088b . I now tried all combinations of setting wall messages or not, timed or immediate shutdown, and they now all work without crashes.

[Launchpad Janitor (janitor)]

This bug was fixed in the package systemd - 225-1ubuntu9

---------------
systemd (225-1ubuntu9) wily; urgency=medium

  * debian/tests/logind: Ignore non-zero exit code of shutdown -c in the new
    "scheduled shutdown" check. This sometimes happens, fails the test, and
    isn't terribly important. Ignore the exit code for now.

 -- Martin Pitt <email address hidden> Thu, 15 Oct 2015 13:34:18 +0200