Skip to content

When a second call comes in while a call is already ongoing, vibration starts and cannot be stopped. Reproducible.

This is on a Librem 5 with Byzantium and the latest updates.

Steps I use to reproduce this:

  • I call person A
  • While the call to person A is ongoing, person B tries to call me
  • The call from person B is terminated but causes vibration to start, very much disturbing my conversation with person A
  • A "missed call" notification pops up, but no option to stop the vibration
  • After hanging up the call with person A, the vibration is still ongoing
  • Vibration continues until reboot

Here is what journalctl says when the call from person B happens:

sep 18 15:15:16 pureos phosh[1516]: The XKEYBOARD keymap compiler (xkbcomp) reports:
sep 18 15:15:16 pureos phosh[1516]: > Warning:          Unsupported maximum keycode 569, clipping.
sep 18 15:15:16 pureos phosh[1516]: >                   X11 cannot support keycodes above 255.
sep 18 15:15:16 pureos phosh[1516]: Errors from xkbcomp are not fatal to the X server
sep 18 15:15:16 pureos ModemManager[627]: <info>  [modem0/call1] call state changed: unknown -> ringing-in (incoming-new)
sep 18 15:15:16 pureos ModemManager[627]: <info>  [modem0/call1] call state changed: ringing-in -> waiting (unknown)
sep 18 15:15:16 pureos ModemManager[627]: <info>  [modem0/call1] user request to hangup call
sep 18 15:15:16 pureos ModemManager[627]: <info>  [modem0/call1] call state changed: waiting -> terminated (terminated)

Later, just when I reboot, there is also this message that could be related:

sep 18 15:16:16 pureos feedbackd[914]: Failed to erase vibra effect with id 1: Invalid argument

So it seems like there is a rogue "vibra effect" that got started when the call from person B came in, and that vibra effect hangs around without anyone being responsible for it.

I can reproduce this, it happens in the same way every time. However, when I tried the same thing on another Librem 5 unit, this did not happen. Not sure why it would happen on one and not the other. But anyway, since it is reproducible for one of them I can try different things like turn on debug logging or similar, if someone can advice how to do that and what to look for. For example, is there a way to get log output when a new vibration effect is started, perhaps including something about who started it and why?

Can the "Unsupported maximum keycode" message have anythiing to do with this, or is that unrelated? I guess itc ould be a coincidence that it happened at nearly the same time.