Hi,

we've got a problem reported from a user using labplot on macos. The start=
 of
labplot fails, the application is hanging and the sample of the running
process points to the following call stack:

Heaviest stack for the main thread of the target process:
  11  start + 1903 (dyld + 25631) [0x7ff8021a641f]
  11  ??? (labplot2 + 89750) [0x10e717e96]
  11  ??? (labplot2 + 501311) [0x10e77c63f]
  11  ??? (labplot2 + 494708) [0x10e77ac74]
  11  ??? (labplot2 + 505861) [0x10e77d805]
  11  KStandardAction::_k_createInternal(KStandardAction::StandardAction,
QObject*) + 2997 (libKF5ConfigWidgets.5.dylib + 182085) [0x1113df745]
  11  KStandardShortcut::shortcutWatcher() + 63 (libKF5ConfigGui.5.dylib +
76383) [0x10ff97a5f]
  11  ??? (libKF5ConfigGui.5.dylib + 75750) [0x10ff977e6]
  11  KConfigWatcher::create(QExplicitlySharedDataPointer<KSharedConfig>
const&) + 272 (libKF5ConfigCore.5.dylib + 249968) [0x1114b1070]
  11  ??? (libKF5ConfigCore.5.dylib + 252061) [0x1114b189d]
  11  QDBusConnection::sessionBus() + 44 (QtDBus + 21452) [0x1116e73cc]
  11  ??? (QtDBus + 8736) [0x1116e4220]
  11  ??? (QtDBus + 8902) [0x1116e42c6]
  11  ??? (QtCore + 2211491) [0x112b5cea3]
  11  QSemaphore::acquire(int) + 110 (QtCore + 171262) [0x11296acfe]
  11  QWaitCondition::wait(QMutex*, QDeadlineTimer) + 83 (QtCore + 186499)
[0x11296e883]
  11  ??? (QtCore + 186603) [0x11296e8eb]
  11  __psynch_cvwait + 10 (libsystem_kernel.dylib + 16638) [0x7ff8024c40f=
e]
 *11  psynch_cvcontinue + 0 (com.apple.kec.pthread + 20884)
[0xffffff8003782194]


This problem is not reproducible on my MacBook nor was it ever reported
earlier by any other macos users.

Does somebody has an idea for what can go wrong during the DBus initializa=
tion
in KConfigWatcher::create()?


Regards,
Alexander