This seems like a bug to me, as the program tries to access unallocated memory. If it does that naturally it will crash. You should probably file this as a bug report on the Bitbucket repository.
Yeah, I was also thinking along the lines of a possible bug.
Yet the thing is: it used to work until a few days ago.
I don´t know whether it could have something to do with ModemManager itself.
Because as part of routine updates ModemManager got a new version and was updated to version 1.10.0-1 on 2019-05-17. That´s pretty much the exact point in time when modem-manger-gui stopped working…
BTW: My modem-manager-gui version is 0.0.19.1-1. I think it´s the latest one.
I think I know hat you meant by “broken packages”.
I set the filter to it and it doesn´t show anything.
And modem-manager-gui itself doesn´t show any signs like a red box.
So I´d have to say: No, it´s not a broken package.
Just install the previously working version. Then, when an even newer version is released, you may install that one. Since you’re apparently using the newest version, you can file a bug report on Bitbucket.
Tnx for the suggestion.
BUT: I´m not sure what to re-install.
As far as modem-manager-gui is concerned (v. 0.0.19.1-1): this one doesn´t seem to have changed recently. This version did work.
What has changed is ModemManager (2019-05-17). So it would seem I´d have to look for the previous version of that one, right?
modem-manager-gui is just the graphical user interface for modem-manager. Described as an analogy, modem-manager is your computer and modem-manager-gui is your display connected to the computer. So when you upgrade your computer, no need to upgrade your display. Same goes with this program. Just revert to an older version of modem-manager.
Thanks for the explanation.
In the meantime I contacted the developer of ModemManager via e-mail.
Perhaps I´ll get a response. It would be interesting to see what he has to say…
Anyway reverting to an older version of ModemManager seems the way to go.
I´ll have to investigate where to obtain one.
this link shows how to install (sudo apt install package=version_number) an older version (with the caveat that there may be dependency issues) and the link below lists a version of modemmanager (1.6.8-2ubuntu1) that should still be in the bionic repo: https://packages.ubuntu.com/bionic/modemmanager
Thank a lot for the explanation and the links. This saved me a lot of time invetigating.
By the way:
After an incredibly short time (only 4 minutes later) I received an answer to my e-mail from
Till Kamppeter, the maintainer of ModemManager.
After describing the problem my final question and his answer was:
My question is: Is it possible that the new version of ModemManager could be responsible for this? Might there be any incompatibilities?
This is possible. We need to investigate this.
Please post a bug report on modem-manager for that. Thanks/
Till