Description of problem: I am getting a notification popup several tens of seconds after each kde startup. The notification says Error: Service disabled Error while initializing DBus Disabling the service I did not observe any important negative consequences - no problem if this bug is only fixed after system release. But it should be fixed, it looks "ugly" and frightening. Version-Release number of selected component (if applicable): How reproducible: 100%, each time after the start of a kde session - but the delay from startup to the notification varies. I did not find any indications in the various logs - except, maybe, in .xsession-errors. The following line is not apparently related, but always comes at the same time as the notification: QGraphicsLinearLayout::removeAt: invalid index 1 Steps to Reproduce: 1. Launch a kde session and start to use it 2. 3. I asked for confirmation if the same thing happens for other users - got one confirmation, which means that the problem probably depends on the kde components that are (not) configured. Doug Laidlaw <laidlaws@hotkey.net.au> also found a quote which indicates a probable reason / solution: --Quote--- Found an old post with the solution!! big_smile https://bbs.archlinux.org/viewtopic.php?id=73944 basically dbus runs a system bus and a user bus. rc.conf starts the system bus but I needed to add "launch-dbus" to the exec line of .xinitrc Now gnome-do and docky both work! --End quote--- Doug also confirms that the kde sound comes late (for me too - again, with the delay varying)
CC: (none) => balcaen.john, lmenut
knotify is just the messenger here. if dbus was not working the kde session won't start at all. Here you need check which service is not correctly launched by systemd probably (because the syntax seems to be systemd related ). /var/log/(messages|syslog) is probably the first step to check.
>> I did not find any indications in the various logs Means: nothing related found in dmesg, /var/log/syslog and messages. What other places should I check?
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Thanks for picking this up: yes the bug is still very present in Mageia 2
Keywords: NEEDINFO => (none)CC: (none) => sander.lepik
CC: (none) => marja11Whiteboard: (none) => MGA2TOO
I've got this message after install draksnapshot ( and it didn't work), after remove it, this message is disappear.
CC: (none) => imeo
(In reply to comment #5) > I've got this message after install draksnapshot ( and it didn't work), after > remove it, this message is disappear. Thanks for the pointer Diep Pham Van. (In reply to comment #4) > Thanks for picking this up: yes the bug is still very present in Mageia 2 Juergen Harms > do you also have drasnapshot installed ?
> do you also have drasnapshot installed. Yes, for historical reasons draksnapshot figures in my list of packages to be installed after sysinstall (script). I just gave it a big kick into some area and the problem has gone away! never had the idea to associate draksnapshot with kde login. Great thanks, this has really been an annoying problem!
@ thierry Which plans are there for draksnapshot?
CC: (none) => thierry.vignaudSummary: dbus notification after kde startup => draksnapshot causes dbus notification after kde startupSource RPM: (none) => draksnapshot
CC: (none) => brejoc
I had this scary dialog too after fresh install of Mageia-3-i586-DVD. Removal of draksnapshot seems to help and rsnapshot still works ;).
CC: (none) => filip.komar
CC: (none) => javier_diaz
From various forums reports issue seems to still persist, including M4. https://forums.mageia.org/en/viewtopic.php?f=7&t=6824 https://forums.mageia.org/de/viewtopic.php?f=18&t=1301 https://forums.mageia.org/de/viewtopic.php?f=7&t=1283 What do we do about this? It's only a scary message on login, but nevertheless should be fixed or draksnapshot should be dropped. @Thierry: ping? cf. #c8
CC: (none) => doktor5000Assignee: bugsquad => thierry.vignaudWhiteboard: MGA2TOO => MGA3TOO, MGA4TOO
CC: lmenut => (none)
CC: (none) => guillaume.ber17
The issue still persists in the latest Cauldron.
CC: (none) => piscestong
obsolete
Resolution: (none) => OLDStatus: NEW => RESOLVED