Bug 347518

Summary:	Dolphin hangs when Klipper is disabled
Product:	[Applications] dolphin	Reporter:	Andrey A. <qweritos>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	cfeck, elvis.angelaccio, justin.zobel, qweritos
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Bug Depends on:	331857
Bug Blocks:
Attachments:	~/.kde4/share/config/klipperrc

Description Andrey A. 2015-05-10 15:12:34 UTC

This bug acts the same way like https://bugs.kde.org/show_bug.cgi?id=331857 but only when I got ~/.kde4/share/config/klipperrc with this content:

[$Version]
update_info=klipper-kconfigxt.upd:KlipperNoSpacesInKeyNames
[General]
AutoStart=false
Number of Actions=0
Version=0.9.7

and I got similar error in my .xsession-errors:

dolphin(1234)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "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." 


After I run manualy run klipper from apps menu - then dolphin starts normaly.

Reproducible: Always

Steps to Reproduce:
1. Place ~/.kde4/share/config/klipperrc with content:
[$Version]
update_info=klipper-kconfigxt.upd:KlipperNoSpacesInKeyNames
[General]
AutoStart=false
Number of Actions=0
Version=0.9.7

2. Restart Xorg or re-login in kde
3. After KDE is fully initialized try to start dolphin.

Actual Results:  
Frozen dolphin window, another kde application could be started while that dolphin process exists.


Linux-4.0.0-pf1
KDE-4.14.7

Comment 1 Andrey A. 2015-05-10 16:02:01 UTC

Created attachment 92525 [details]
~/.kde4/share/config/klipperrc

Comment 2 Christoph Feck 2015-05-16 17:49:11 UTC

Is there any reason you assigned this away from Klipper? If yes, can you please provide insight what you found out?

Comment 3 Martin Flöser 2015-05-17 18:03:35 UTC

Well it cannot be a klipper bug if something else doesn't work if klipper is not running. Klipper is just a clipboard history tool, but doesn't provide a clipboard - that's a standard X11 feature.

I do not know or have any idea where the bug is and that's why I moved to the generic kde component.

Comment 4 Justin Zobel 2020-10-25 01:02:30 UTC

Andrey can you please confirm if this is still an issue on current KDE releases?

Comment 5 Bug Janitor Service 2020-11-09 04:33:39 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2020-11-24 04:34:04 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!