[Bug 229534] New: Kontact hangs with error libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"

[Tristan Miller]

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

           Summary: Kontact hangs with error libakonadi
                    Akonadi::SessionPrivate::socketError: Socket error
                    occurred: "QLocalSocket::connectToServer: Invalid
                    name"
           Product: kontact
           Version: 4.4.1
          Platform: openSUSE RPMs
        OS/Version: unspecified
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: psychonaut at nothingisreal.com


Version:            (using KDE 4.4.1)
Installed from:    openSUSE RPMs

This bug appears to be new in KDE 4.4.1.  I don't recall it happening in KDE
4.4.0.

Reproducibility: Always

Steps to reproduce:
1. On the local machine, launch Kontact.  Then quit Kontact.
2. On a remote machine, use NoMachine NX client to launch Kontact on the local
machine.  (See the attached screenshot for how to do this.)  Then quit Kontact.
3. On the local machine, launch Kontact.  The Kontact window appears, but it is
completely unresponsive.  Meanwhile the following message gets output to the
console about every second:
   kontact(22370)/libakonadi Akonadi::SessionPrivate::socketError: Socket error
occurred: "QLocalSocket::connectToServer: Invalid name"