Mageia forum

I'm running Mageia 2 x86_64 with KDE. Shortly after the desktop appears I get a message saying that the dbus service cannot be started, then it disappears. It looks like a plasma notification in the lower right corner. I see nothing in the logs Anyone have any ideas?

oboedad55 wrote:I'm running Mageia 2 x86_64 with KDE. Shortly after the desktop appears I get a message saying that the dbus service cannot be started, then it disappears. It looks like a plasma notification in the lower right corner. I see nothing in the logs Anyone have any ideas?

Is it this issue? https://bugs.mageia.org/show_bug.cgi?id=5622

marja wrote:

oboedad55 wrote:I'm running Mageia 2 x86_64 with KDE. Shortly after the desktop appears I get a message saying that the dbus service cannot be started, then it disappears. It looks like a plasma notification in the lower right corner. I see nothing in the logs Anyone have any ideas?

Is it this issue? https://bugs.mageia.org/show_bug.cgi?id=5622

Yes, that's the one. Thanks for pointing it out.

oboedad55 wrote:

marja wrote:
Is it this issue? https://bugs.mageia.org/show_bug.cgi?id=5622

Yes, that's the one. Thanks for pointing it out.

yw

If the error message irritates you, then add a comment in the bug report that you have the problem, too.

That'll improve the chance it'll get fixed

well here knotify is just the messenger as i wrote on the bug report.
So it's quite difficult to « suppress » this warning if we don't know which app cause the issue :/

mikala wrote:well here knotify is just the messenger as i wrote on the bug report.
So it's quite difficult to « suppress » this warning if we don't know which app cause the issue :/

Is it crazy to think that users with the bug could compare what they have running with people who don't have the bug to find whether one service makes the difference?

it is not.
However so far i just notice a " me too" on it :/

mikala wrote:it is not.
However so far i just notice a " me too" on it :/

So what should be compared? The output of

Code: Select all

systemctl -a

?

I don't know :/
Currently we should check applications using dbus (which could lead to a lot of distribution).
The way mageia was installed, which packages were installed after, etc could probably to help & reproduce it so we can narrow the culprit.
systemctl is going to lead only to global service when the culprit could be a "user application" (but should of course be useful :p )

mikala wrote:I don't know :/
Currently we should check applications using dbus (which could lead to a lot of distribution).
The way mageia was installed, which packages were installed after, etc could probably to help & reproduce it so we can narrow the culprit.
systemctl is going to lead only to global service when the culprit could be a "user application" (but should of course be useful :p )

That sounds like an awful lot of work for something that seems to be nothing but just an unneeded error message. However, if the message is needed, then someone will find out something doesn't work
Maybe it is best to sit back and wait and see whether that happens.
I know there is no sitting back for you, way to many other bugs