https://bugs.kde.org/show_bug.cgi?id=474631

            Bug ID: 474631
           Summary: ModemManager-Qt hits asserts if ModemManager has
                    errors starting up and exporting objects to bus
    Classification: Frameworks and Libraries
           Product: frameworks-modemmanager-qt
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: plasma-b...@kde.org
          Reporter: uhh...@gmail.com
                CC: lamar...@kde.org, lukas.ti...@merlin.cz
  Target Milestone: ---

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

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to