QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

[Volodymyr Kolesnykov]

Happens every time I start Kate from the console.

$ kate
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

Other than that the application seems to work fine.

$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04

$ apt-cache policy kate
kate:
  Installed: 4:4.8.1-0ubuntu1
  Candidate: 4:4.8.1-0ubuntu1
  Version table:
 *** 4:4.8.1-0ubuntu1 0
        500 http://ua.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: kate 4:4.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 19 11:48:13 2012
ExecutablePath: /usr/bin/kate
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 LANG=ru_RU.UTF-8
 LANGUAGE=ru_RU:ru
SourcePackage: kate
UpgradeStatus: Upgraded to precise on 2012-03-18 (0 days ago)

[Laurent Bonnaud (laurent-bonnaud)]

User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20100101 Firefox/11.0
Build Identifier:

Each time I start a konsole, I see the following error messages:

$ konsole
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

Other KDE applications display the same error (for instance akregator).

Reproducible: Always

Steps to Reproduce:
1. Start konsole from a terminal
2. Look at what it displays in the terminal
3.
Actual Results:
error messages

Expected Results:
no error messages

This happend in KDE 4.8.1 in Ubuntu precise and in the KDE 4.8.1backport for oneiric. KDE 4.7.x did not have this problem.

[adaptee (adaptee)]

This is a common problem for all KDE applications using class KUniqueApplication with Qt 4.8. Other examples are klipper,ktorrent, kmix, etc.

See https://git.reviewboard.kde.org/r/103699/

[Laurent Bonnaud (laurent-bonnaud)]

Thanks for the pointer!

I am looking forward to seeing this patch integrated into a future KDE release...

[adaptee (adaptee)]

*** Bug 297229 has been marked as a duplicate of this bug. ***

[Laurent Bonnaud (laurent-bonnaud)]

This bug is still there in KDE 4.8.2.

Could somebody mark this bug as CONFIRMED since there is a duplicate ?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bob Vincent (pillarsdotnet)]

Also happens when starting kopete from the console.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[choury (zhouwei400-w)]

Also happens when starting kgpg from the console.

[Gannet (ken20001)]

Also happens when starting Muon from the console.

[Gannet (ken20001)]

Guys, please, vote here for this bug: https://bugs.kde.org/show_bug.cgi?id=297020

[J-z3gxr (j-z3gxr)]

I get the message and the application never starts. It does not happen some time after restart, but only afer some time of using computer. But it happens everyday. I use debian wheezy.

[Assembler-coder (assembler-coder)]

Got the same problem. Now I can't start Dolphin. Very very bad problem.

[J-z3gxr (j-z3gxr)]

is there a workaroud before the patch get integrated? It renders kde unusable for me.

[adaptee (adaptee)]

(In reply to comment #6)
> Got the same problem. Now I can't start Dolphin. Very very bad problem.

Dolphin stops using KUniqueApplication since KDE SC 4.7. So :

  * If you are using KDE SC 4.7+, your dolphin problem can't be caused by this KUniqueAplication specific issue.
  * If you are using something older than KDE SC 4.8 together with Qt 4.8, that is not a good idea by itself.

(In reply to comment #7)
> is there a workaroud before the patch get integrated? It renders kde
> unusable for me.

AFAIK, this warning hasn't caused any real bug(at least I haven't heard about any in bugs.kde.org) . If you really think your problem is caused by this warning, open a new bug report, write down specific and detailed information of your problem, and link back to this bug report.

[Assembler-coder (assembler-coder)]

I don't know exactly if it related to the bug or not, but I stopped nepomuk and right after that... three instances of Dolphin started, which I was trying to run before.

qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit

[Soo-Hyun Choi (s.choi)]

I still got the same warning with Ubuntu 12.04 32-bit for KDE 4.8.3. It seems that Konsole behaves extremely sluggish due to this warning message. Not satisfied.

[Soo-Hyun Choi (s.choi)]

Due to this warning, Konsole seems to behave very sluggish. I am under Ubuntu 12.04 32-bit, KDE 4.8.3.

[Jan-Pieter Jacobs (jpjacobs)]

Same for me. Happens with about any Kde application launched.

I can confirm the nepomuk daemon taking 100% CPU, and making other applications unresponsive.
After disabling file indexing things got a bit better, but I still have stability problems, even with desktop effects disabled.

For instance: applications fail to launch (or only launch after a long, long time), the activity bar gets blanked and irresponsive applications crash, etc etc. If I try again, the problem is not reproducible. So it's pretty random. I'm not sure that everything is related, but this DBUS message is there every time...

I'm using Ubuntu 12.04 64 bit, KDE 4.8.4

[maxim (off220)]

same for me. Kubuntu 12.04 x86-64. Latest updates.

[aldobelus (aldobelus)]

Hola, a mí también me ha aparecido este error cuando intentaba echar a andar el kfilebox. He de decir que no estoy seguro de haber hecho bien la instalación de la aplicación, aunque seguí los pasos lo mejor que pude. El sistema operativo es Chakra Archímedes; creo que es la última versión estable, si no me equivoco. Perdón, soy recién llegado a Chakra...
De otro lado, mi Dolphin va perfectamente, como un avión, como siempre. Pero yo también inutilicé Nepomuk y Strigi ayer, creo (se me mezclan los días con tanto ordenador!), no sé si tendrá que ver. Sólo me ha ocurrido con kfilebox, lo demás va bien (cruzo los dedos)

[Christoph-maxiom (christoph-maxiom)]

*** Bug 303744 has been marked as a duplicate of this bug. ***

[Peter M. Clausen (pclausen)]

I cant open any application right now - getting fustrated.

Fully updated Kubuntu 12.04 64-bit. It worked quite well yesterday.... :-(

[Peter M. Clausen (pclausen)]

Maybe it helps others:
in fustration I changed to tty1 Ctrl +Alt F1
then:
<code>
$ sudo stop kdm
$ rm -rf ~/.kde ~/.kderc /var/tmp/kdecache-<MY USERNAME>
$ sudo start kdm
</code>

I lost all my customizaitons (~2 days of work), but at least now KDE is working again. The error:
<code>
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
</code>
remains though...

[Laurent Bonnaud (laurent-bonnaud)]

I upgraded my Kubuntu system to KDE 4.9 from precise kde backports and this bug is still there.

[Peter M. Clausen (pclausen)]

I gave up on Kubuntu 12.04 and installed Linux Mint 13 (XFCE) instead. I still want to use kde-apps (kate, kdevelop, konquoror, ...) and they run OK, but also in this setting I get he above message from following apps:
kate
systemsettings
konqouror
kdebugdialog

Interestingly these KDE-apps does NOT display this message at start up (?)
kdevelop
k4dirstat

-------------------------------------------------------------
Output from Konqouror
-------------------------------------------------------------
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KDE Daemon (kded) already running.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(2511) kdemain: Reusing existing ksycoca
...

[Sergey Ivanov (icegood1980)]

still present. Applications: kate, wicd-kde

[Sergey Ivanov (icegood1980)]

I mean under kubuntu 12.04

[adaptee (adaptee)]

*** Bug 305266 has been marked as a duplicate of this bug. ***

[šumski (schumski-deactivatedaccount-deactivatedaccount)]

Patch for Qt, omits qdbusconnection warnings in release/no-debug mode.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "qt-everywhere-opensource-src-4.8.1-qdbusconnection_no_debug.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[S-kdebugs-h (s-kdebugs-h)]

Same issue on KDE 4.8.4 (Debian/Wheezy 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux).

It starts the moment KDM goes up and slowly fills log up to ~50MB after about 50 hrs:
Xsession: X session started for {my-username} at Sun Sep 2 21:23:39 EDT 2012
localuser:{my-username} being added to access control list
startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

Looks like nepomuk just adds to it, but the message shows with or without it.

[Gabor Vas (cognac-gamma)]

It affects my plasma-desktop, see duplicate. Very frustrating.

[Christoph-maxiom (christoph-maxiom)]

*** Bug 307731 has been marked as a duplicate of this bug. ***

[Dr Gregory House (greghouse)]

Same issue on KDE 4.9.3 with Gentoo Linux x86_64 when amarok is started
(Linux superb 3.4.9-gentoo #3 SMP PREEMPT Sat Nov 10 02:10:29 ALMT 2012 x86_64 Pentium(R) Dual-Core CPU E6500 @ 2.93GHz GenuineIntel GNU/Linux)

[drhouse123:~]$ amarok
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
 QUrl( "http://ws.audioscrobbler.com/2.0/?api_key=&lang=ru&method=user.getNeighbours&user=" )
 QUrl( "http://ws.audioscrobbler.com/2.0/?api_key=&lang=ru&method=user.getFriends&user=" )
 QUrl( "http://ws.audioscrobbler.com/2.0/?api_key=&lang=ru&method=user.getTopTags&user=" )
 QUrl( "http://ws.audioscrobbler.com/2.0/?api_key=&lang=ru&method=user.getTopArtists&user=" )

[adaptee (adaptee)]

*** Bug 311943 has been marked as a duplicate of this bug. ***

[Jdales (jdales)]

So what is the solution?

On Dec 19, 2012, at 12:04 PM, Jekyll Wu <email address hidden> wrote:

> https://bugs.kde.org/show_bug.cgi?id=297020
>
> Jekyll Wu <email address hidden> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |<email address hidden>
>
> --- Comment #22 from Jekyll Wu <email address hidden> ---
> *** Bug 311943 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

[Jdales (jdales)]

Its not the error message hat concerns me. Its the inconsistency of the keyboard opening and closing. I need that to be on point.
On Dec 19, 2012, at 12:04 PM, Jekyll Wu <email address hidden> wrote:

> https://bugs.kde.org/show_bug.cgi?id=297020
>
> Jekyll Wu <email address hidden> changed:
>
> What |Removed
> ----------------------------------------------------------------------------
> CC| |<email address hidden>
>
> --- Comment #22 from Jekyll Wu <email address hidden> ---
> *** Bug 311943 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

[tormen (quickhelp)]

For me this often breaks my keyboard shortcuts - none of my
When I try to access "systemsettings" from the console, I'll see this error message.
When I try to access the "shortcuts and gestures" module, it takes 2-3 /minutes/ to show.
Applying changes within the module often result in a segfault!

If there is anything I can do to help collect more data / do tests, /please/ let me know!

[tormen (quickhelp)]

For me this often breaks my keyboard shortcuts (setup in the "shortcuts and gestures" module)!
When they are not working, then:
* When I try to access "systemsettings" from the console, I'll see this error message.
* When I try to access the "shortcuts and gestures" module, it takes 2-3 /minutes/ to show.
* Applying changes within the module often result in a segfault!

If there is anything I can do to help collect more data / do tests, /please/ let me know!

[tormen (quickhelp)]

Sorry for the double post earlier :/

~ % systemsettings #12353 me@seven pts/6
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

>>>> And when the "shortcuts and gestures" module finally got loaded:
systemsettings(6012)/khotkeys: Unable to start server org.kde.khotkeys (kded module) [ "org.freedesktop.DBus.Error.NoReply" ]: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

>>>> And when I changed an existing shortcut (by assigning a different keyboard shortcut) and systemsettings crashed:
systemsettings(6012)/khotkeys: Unable to start server org.kde.khotkeys (kded module) [ "org.freedesktop.DBus.Error.NoReply" ]: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
KCrash: Application 'systemsettings' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/me/.kde4/socket-seven/kdeinit4__0

Are these additional error messages I am seeing and I am having with using the "Shortcuts and Gestures" module in systemsettings related and consequences from the first error message "session D-Bus connection created before QCoreApplication." ?
Or should they be reported in a different bug ?

The above is reproducable (once I get the initial error message "QDBusConnection: session D-Bus connection created before QCoreApplication.")!
For me often with a restart of the computer the problems are gone.
... I am not sure yet, but I also think the problems either appear right after login or not at all (until I reboot).

[Raul-kde-bugzilla (raul-kde-bugzilla)]

I have this error messages with kde 4.9.5 but it is related to kwalletd.

I need to kill kwalletd before it starts to work again.

[David Faure (faure)]

Everyone: this warning from QDBusConnection is HARMLESS, and is not the reason for any bug you might be seeing in the application showing this warning. Do not associate things that are completely unrelated.

I started to look into changing KUniqueApplication so that the warning doesn't get printed, but it turns out to be very difficult due to the forking, see kde-core-devel for more information.

[JaSauders (jasauders)]

I just ran into this same exact error when I tried to pass a -e parameter to Konsole. I was trying to bind a shortcut so I could hit a key combination and Konsole would open to an SSH session on my server.

konsole -e 'ssh jason@192.168.1.20'

Running that command results in two lines of the above error, along with what appears to be a Konsole session opening and closing immediately with no SSH session present. If I run the exact same command in other terminals, it works fine... example:

terminator -e 'ssh jason@192.168.1.20'
gnome-terminal -e 'ssh jason@192.168.1.20'

Thought I'd comment. Thanks!

[osirisgothra (osirisgothra)]

Just wanted to post that this bug seems to still exist under Ubuntu 12.04 LTS and 12.10
with KDE 9.10.0 installed and all upgrades to current backports, is this really a bug or maybe
there just needs to be a way to turn off these warnings?

[osirisgothra (osirisgothra)]

-- Footnote to that, maybe place it in the kdebugdialog??

[Luis Alvarado (luisalvarado)]

Started happening since the updates I did on 13.04 Today April 24.

cyrex@cyrex:~$ ktorrent
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

And the problem is, because of this, I can not start downloading any torrent.

[Bryan McKinley (bryan-mckinley)]

Happens every time I start a remote ssh konsole, as in:

$ ssh -X network konsole
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
unnamed app(15824): KUniqueApplication: Cannot find the D-Bus session server: "Failed to connect to socket /tmp/dbus-kKT1rz9E0S: Connection refused"

unnamed app(15815): KUniqueApplication: Pipe closed unexpectedly.

[Larry Williams (ltwilliams58)]

The issue remains in 13.04 raring.

I can't tell if this is related to konsole ignoring and overwriting konsolerc. Would be nice to see this resolved or, at least, conformation that the konsole issue is not related.

[N1ck 7h0m4d4k15 (nicktux)]

The issue remains in Kubuntu 13.10 (Saucy Salamander). Package : KMix is not opening either from menu or Konsole.

[pazuzuthewise (pazuzuthewise)]

It happens to me also in Saucy x86. Ktorrent would not start, and when invoked from console, it gives the respective error message. Disabling nepomuk (in System settings > Desktop search), seems to fix the problem. With Nepomuk disabled, Ktorrent starts normally.

[Bergstein (bergstein)]

Unuseful log crap is not harmless.

(In reply to comment #29)
> Everyone: this warning from QDBusConnection is HARMLESS, and is not the
> reason for any bug you might be seeing in the application showing this
> warning. Do not associate things that are completely unrelated.
>
> I started to look into changing KUniqueApplication so that the warning
> doesn't get printed, but it turns out to be very difficult due to the
> forking, see kde-core-devel for more information.

[8-kde (8-kde)]

(In reply to comment #28)
> I have this error messages with kde 4.9.5 but it is related to kwalletd.
>
> I need to kill kwalletd before it starts to work again.

Please update your installation, as that kwalletd version had some lock problems I already solved.

[gaara (yoggic)]

Same bug in Kubuntu 14.04, with KDE 4.13.0
m2n@m2n:~$ konsole
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
guillaume@guillaume-m2n:~$ Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
Same with Kate.
Hope It will be fix soon!

[Harald Sitter (apachelogger)]

Actually, let's close the bug because it should not be tracked on launchpad. Please refer to the linked upstream bug report for progress on this.

For what it is worth though, this is not an error but a warning that really does not cause any problems.

[jimav (james-avera)]

Well, it's not quite true that it "does not cause any problems".
It completely pollutes your terminal so you can't see output from previous commands without scrolling back.

And if "application may misbehave" is true, then it's a bug, not just a nuisance.

[Eero-taipale (eero-taipale)]

(In reply to comment #30)
> Unuseful log crap is not harmless.

IMO this is not only unuseful, this is harmful since it continuosly leads people spending time with this issue.

[Daniel Stelmach (daniel-stelmach)]

Same bug in Kubuntu 14.04 KDE 4.13.0

[Alexander Pánek (a-panek)]

This bug renders Konsole unusable. It also seems to cause a lot of other disturbances in KDE which I cannot reproduce right now.

However, Konsole *never* starts, invoking it from another terminal application renders the above error and then quits.

This is definitely a bug and harmful.

[gaara (yoggic)]

Same issue here:
$ kate
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
$ amarok
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

[robert leleu (robert-jean-leleu)]

same issue// but my installation is the result of installing a new Mint16 on sda, and then mounting the existing sdb1 on the new home

leleu@leleu-portable ~/Qt $ synaptiks
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

[Paul Abrahams (abrahams)]

I encounter this in KDE 4.14.2, Kubuntu 14.10, whenever I use kstart.

[Paul Abrahams (abrahams)]

When I try to use kstart I get this message, and the application opens on the wrong desktop even though I've used the "--desktop" parameter. Since I can't use kstart without getting this message, I don't know if the kstart problem is related or not.

[Laurent Bonnaud (laurent-bonnaud)]

For the record, this bug still exists in Konsole 3.0.1 / KF 5.9.0

[osirisgothra (osirisgothra)]

This bug is never going to be fixed because it is more or less just stating an obvious fact. It seems that there somehow no real easy way to avoid this message, other than going in and redirecting all your kde apps that use QCoreApplication to 2>/dev/null. I've experienced this message from ~4.8 to present (for me, 5.9.0 now in kf). While looking at all the other bugs out there, it seems futile to even ask at this point. Unless you can get about 10,000 people to post about it (different people with different IPs!! are the only counted!)

[Uqbar (uqbar)]

While running programs with "&> /dev/null" will "fix" a lot of bug
reports, I think this is not the right approach.
We call it the ostrich approach.
Either there is a bug within Qt itself (by complaining against
something cannot be fiex), or lot of Qt/KDE programmers are dumb (by
making all the same strupid error).

I would suggest to forget about this report until it will vanish.
A lot of bugs here have got their "won't fix" this way.

[Laurent Bonnaud (laurent-bonnaud)]

This bug is still there in Kubuntu 15.10 and Konsole Version 15.08.0
Using:
KDE Frameworks 5.14.0
Qt 5.4.2 (built against 5.4.2)
The xcb windowing system

[Alain-calmet (alain-calmet)]

I have the same BUG in 1 install of Kubuntu 14.04 LTS.
I had never seen it before on 10 different install of Fedora, Mageia 4 (KDE 4.12) or Mageia 5 (KDE 4.14).
              --------------------------
For me DEBIAN / UBUNTU / MINT is for GNOME / UNITY / MATE only.
And KDE is definitly for the planet RED HAT ∕ FEDORA ∕ MAGEIA...

[Laurent Bonnaud (laurent-bonnaud)]

This bug still exists in neon packages:

Konsole Version 15.08.0
Using:
KDE Frameworks 5.20.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

[David Faure (faure)]

This is because konsole needs to be ported from KUniqueApplication (a kdelibs4support class) to KDBusService. Please file a konsole-specific bug about that.

[Uqbar (uqbar)]

@David Faure, do you mean the bug is in konsole even if it's kate to complain?
Or maybe you mistyped konsole for kate?

[Laurent Bonnaud (laurent-bonnaud)]

> This is because konsole needs to be ported from KUniqueApplication (a kdelibs4support class) to KDBusService.

Thank you for the hint!

> Please file a konsole-specific bug about that.

Done, see bug #361182.

[GreyGeek (greygeek77)]

I am running Kubuntu 16.04 with the latest patches and Plasma 5.6. A few days ago I installed KGpg and created a key. It ran perfectly. Then an update came down the pipe. Now, I cannot start KGpg from my user menu or from a user Konsole. The attempt aborts with the message
"QDBusConnection: session D-Bus connection created before QCoreApplication. ... "

Systemctl shows I have two dbus services running:
dbus.service loaded active running D-Bus System Message Bus
dbus.socket loaded active running D-Bus System Message Bus Socket

However, if in a Konsole I enter "kdesudo kgpg" it will start up and run as root.

Obviously this message is NOT a "harmless" and more than a mere nuisance if it prevents programs from being run. A LOT of these "nuisances" have popped up on Kubuntu and other distros using both Plasma 4 and 5 for over FOUR YEARS, and its not doing KDE's reputation any service.

KDE Neon is being built with QtQuick and QML and the bug has appeared on it as well, as evidenced by previous posts. That suggests that the bug is in QDBusConnection itself.

[David Faure (faure)]

This has been fixed by deprecating KUniqueApplication in KF 5.0 and porting the apps to KDBusService instead.

[KitchM (tech-frontrowcomputer)]

The originally reported issue is still occurring when trying to start kgpg in Xubuntu 14.04.4.