Ubuntu SDK fails to work when a dbus session is not present.

[Brandon Schaefer]

When attempting to run the Ubuntu SDK when there is no dbus session daemon running causes the SDK to fail. The first assumption seems to be in the clipboard.

With no dbus-session:
http://paste.ubuntu.com/11794311/

With a dbus-session:
http://paste.ubuntu.com/11794350/

Which then yields:
http://i.imgur.com/wU8NLdm.png

The QML:
http://paste.ubuntu.com/11794368/

[Gerry Boland (gerboland)]

QtUbuntu only tries to connect to dbus when app requests contents of the clipboard for the first time, and not at startup.

Testing a simple QML file with qtubuntu, it works fine without a dbus service running.

If application does this at startup, qtubuntu may be a source of a crash, quoting the relevant code:

void UbuntuClipboard::setupDBus()
{
    QDBusConnection dbusConnection = QDBusConnection::sessionBus();

    bool ok = dbusConnection.connect(
            "com.canonical.QtMir",
            "/com/canonical/QtMir/Clipboard",
            "com.canonical.QtMir.Clipboard",
            "ContentsChanged",
            this, SLOT(updateMimeData(QByteArray)));
    if (!ok) {
        qCritical("UbuntuClipboard - Failed to connect to ContentsChanged signal form the D-Bus system clipboard.");
    }

    mDBusClipboard = new QDBusInterface("com.canonical.QtMir",
            "/com/canonical/QtMir/Clipboard",
            "com.canonical.QtMir.Clipboard",
            dbusConnection);

    mDBusSetupDone = true;
}

Will consider that as an enhancement.