Bug 5622

Summary:	draksnapshot causes dbus notification after kde startup
Product:	Mageia	Reporter:	Juergen Harms <juergen.harms>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	balcaen.john, brejoc, doktor5000, filip.komar, filorin, imeo, javier_diaz, mageia, marja11, piscestong, thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:	MGA3TOO, MGA4TOO
Source RPM:	draksnapshot	CVE:
Status comment:

Description Juergen Harms 2012-04-26 15:57:10 CEST

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)

Manuel Hiebel 2012-04-27 00:00:31 CEST

CC: (none) => balcaen.john, lmenut

Comment 1 John Balcaen 2012-04-27 00:49:48 CEST

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.

Comment 2 Juergen Harms 2012-04-27 09:15:33 CEST

>> 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?

Comment 3 Marja Van Waes 2012-05-26 13:10:26 CEST

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

Comment 4 Juergen Harms 2012-05-26 17:47:43 CEST

Thanks for picking this up: yes the bug is still very present in Mageia 2

Sander Lepik 2012-05-26 18:55:06 CEST

Keywords: NEEDINFO => (none)
CC: (none) => sander.lepik

Marja Van Waes 2012-06-03 08:46:17 CEST

CC: (none) => marja11
Whiteboard: (none) => MGA2TOO

Comment 5 Diep Pham Van 2012-06-17 15:23:49 CEST

I've got this message after install draksnapshot ( and it didn't work), after remove it, this message is disappear.

CC: (none) => imeo

Comment 6 John Balcaen 2012-06-17 17:04:42 CEST

(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 ?

Comment 7 Juergen Harms 2012-06-17 17:49:12 CEST

> 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!

Comment 8 Marja Van Waes 2012-06-17 21:50:01 CEST

@ thierry

Which plans are there for draksnapshot?

CC: (none) => thierry.vignaud
Summary: dbus notification after kde startup => draksnapshot causes dbus notification after kde startup
Source RPM: (none) => draksnapshot

Jochen Breuer 2013-01-30 13:43:44 CET

CC: (none) => brejoc

Comment 9 Filip Komar 2013-06-27 17:09:12 CEST

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

Javier Díaz 2013-09-21 23:09:37 CEST

CC: (none) => javier_diaz

Comment 10 Florian Hubold 2014-02-03 23:05:46 CET

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) => doktor5000
Assignee: bugsquad => thierry.vignaud
Whiteboard: MGA2TOO => MGA3TOO, MGA4TOO

Luc Menut 2014-02-21 00:32:25 CET

CC: lmenut => (none)

Guillaume 2014-03-11 18:46:33 CET

CC: (none) => guillaume.ber17

Comment 11 Jin-tong Hu 2014-06-29 10:52:20 CEST

The issue still persists in the latest Cauldron.

CC: (none) => piscestong

Comment 12 Juergen Harms 2019-02-19 18:50:28 CET

obsolete

Resolution: (none) => OLD
Status: NEW => RESOLVED