Bug 131631

Summary:	[usability] "Cannot talk to klauncher" message is useless
Product:	[Unmaintained] kio	Reporter:	Isaac Wilcox <iwilcox>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nate, osterfeld
Priority:	NOR	Keywords:	triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Isaac Wilcox 2006-08-01 04:56:26 UTC

Version:           1.4.1 (2:1.4.1-0ubuntu1) (using KDE KDE 3.5.3)
Installed from:    Ubuntu Packages

If klauncher isn't running (like, you didn't run kdeinit or something like that, can't tell exactly), amarok will pop up a dialog on startup saying "Cannot talk to klauncher".  It's a totally useless error message - it doesn't tell you what to do about it, nor whether you need to do anything, nor what Amarok will be unable to do as a result.  I'm calling this a bug because IMO it's a usability issue.

Comment 1 Alexandre Oliveira 2006-08-01 07:26:18 UTC

I agree. This message isn't on Amarok's source though, it comes from kde. Let's find out where it comes from and reassign.

Comment 2 Alexandre Oliveira 2006-08-01 18:11:35 UTC

Comes from kdelibs/kio/kio/slave.cpp

Comment 3 Frank Osterfeld 2006-09-03 23:31:01 UTC

Any ideas what a user can actually do when getting this message? I think restarting KDE is probably the most promising action...

Comment 4 David Faure 2006-09-04 13:14:39 UTC

Yes, restarting kde, or just restarting kdeinit (typing kdeinit in a terminal)
or fixing the installation (if he's mixing kde3 and the current kde4, for instance, although this might have improved already)

Comment 5 Nate Graham 2018-04-23 18:48:30 UTC

Is this still relevant or applicable with KDE Frameworks 5.45?

Comment 6 Andrew Crouthamel 2018-09-28 03:28:04 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 set the bug status 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 7 Andrew Crouthamel 2018-10-29 02:04:57 UTC

Dear Bug Submitter,

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!