Chrome log spam about org.freedesktop.ModemManager1.Modem.Messaging.List D-Bus errors |
||||
Issue descriptionDevice imaged from R65-10309.0.0. The following is continuously written to my log: [7129:7129:0119/112652.065751:ERROR:object_proxy.cc(626)] Failed to call method: org.freedesktop.ModemManager1.Modem.Messaging.List: object_path= /org/freedesktop/ModemManager1/Modem/71: org.freedesktop.ModemManager1.Error.Core.WrongState: Cannot list SMS messages: device not yet enabled
,
Jan 19 2018
,
Jan 19 2018
Thanks for finding an owner Dan.
,
Feb 5 2018
Which device are you using? Is your device equipped with a SIM card slot, and a SIM card which can receive SMS messages?
,
Feb 5 2018
Per #1, it's a Pixel. I'd guess it's one of the ones with built-in LTE...
,
Feb 6 2018
It seems NetworkSmsHandler is doing something wrong, but I guess not many people in UI team are testing the code on a device which comes with builtin LTE. I guess Steven has some insight about NetworkSmsHandler, also maybe I can reproduce this if I happen to find a device with LTE in our team's cabinet.
,
Feb 6 2018
Here's the issue: NetworkSmsHandler monitors the Devices property of shill.Manager interface, and upon each update of the property, it iterates through all cellular devices from the device list and creates a new NetworkSmsDeviceHandler for each cellular device. The construction of a ModemManager1NetworkSmsDeviceHandler object will trigger a call to the org.freedesktop.ModemManager1.Modem.Messaging.List method. That's not good as NetworkSmsHandler should avoid creating a ModemManager1NetworkSmsDeviceHandler for the same SMS D-Bus object exposed by ModemManager.
,
Feb 6 2018
a minor correction to #7: "... same SMS D-Bus object ..." should be "... same Modem D-Bus object ..."
,
Feb 6 2018
When the code was written we did not anticipate more than one Cellular device. We should fix that incorrect assumption.
,
Feb 6 2018
Re #9: I think the issue is reproducible with one cellular device as well. The Devices property of the shill.Manager interface can be updated every time a (unrelated) device is added or removed (e.g. unplug and replug an Ethernet adapter) from the device list. The current code would create a new NetworkSmsDeviceHandler for each cellular device encountered during the update, even through the same object may have been created previously. Another issue is that the list of NetworkSmsDeviceHandler never removes old objects.
,
Sep 28
Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.
,
Oct 5
|
||||
►
Sign in to add a comment |
||||
Comment 1 by sky@chromium.org
, Jan 19 2018