Bug 474631

Summary: ModemManager-Qt hits asserts if ModemManager has errors starting up and exporting objects to bus
Product: [Frameworks and Libraries] frameworks-modemmanager-qt Reporter: Janet Blackquill <uhhadd>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: REPORTED ---    
Severity: crash CC: kde, lamarque, lukas.tinkl
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Janet Blackquill 2023-09-17 19:14:30 UTC 
mmqt hits an assert in modemdevice.cpp around here:
```
    bool success = QDBusConnection::systemBus().connect(QLatin1String(MMQT_DBUS_SERVICE),
                                         QLatin1String(MMQT_DBUS_PATH),
                                         QLatin1String(DBUS_INTERFACE_MANAGER),
                                         QStringLiteral("InterfacesAdded"),
                                         this,
                                         SLOT(onInterfacesAdded(QDBusObjectPath, ModemManager::MMVariantMapMap)));
    Q_ASSERT(success);
```

OBSERVED RESULT
mmqt assumes that modemmanager is always functional

EXPECTED RESULT
mmqt gracefully handles modemmanager failing to initialise due to e.g. hardware issues

ADDITIONAL INFORMATION
this causes downstream issues in kded and plasmashell, which causes much of the plasma session to become unfunctional due to code calling into mmqt
Comment 1 David Edmundson 2023-09-17 21:43:35 UTC 
>mmqt gracefully handles modemmanager failing to initialise due to e.g. hardware issues

That wouldn't cause this assert. We're blindly connecting a match rule to a slot. Nothing remote matters at all.
Comment 2 David Edmundson 2023-09-17 21:45:06 UTC Comment hidden (spam)