Bug 330278

Summary:	kdialog warnings
Product:	[Unmaintained] kio	Reporter:	nikos.giotis
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	cpigat242, nate
Priority:	NOR	Keywords:	triaged
Version:	4.10.5
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	patch that fixes the issue A more efficient patch

Description nikos.giotis 2014-01-22 09:20:11 UTC

I get warnings errors and some lag when using the kdialog, either directly (eg. `kdialog --getopenfilename .`) or indirectly when used by other programs.
The messages I get were about KSambaSharePrivate:: .. (can't remember the actual output right now)
This is fixed by applying http://bugsfiles.kde.org/attachment.cgi?id=84643 so this issue is related to this https://bugs.kde.org/show_bug.cgi?id=320199 
The other messages I got were from KUrlCompletion::postProcessMatch. (can't remember the actual output either). The problem this time is shown when the postProcessMatch tries to stat a relative filename. It tries to stat filenames that have "//" somewhere inside the path. I will attach a patch that when combined with the one above fixes the warnings here.

Reproducible: Always

Steps to Reproduce:
1. kdialog --getopenfilename .

Comment 1 nikos.giotis 2014-01-22 09:20:59 UTC

Created attachment 84790 [details]
patch that fixes the issue

Comment 2 nikos.giotis 2014-01-24 08:50:37 UTC

Created attachment 84829 [details]
A more efficient patch

Comment 3 David Faure 2014-02-15 17:35:06 UTC

step 1 is not enough to reproduce the bug. Please give me more details on how to reproduce it?

Comment 4 nikos.giotis 2014-02-16 01:28:04 UTC

This seems to be triggered by (also?) not having an smb.conf file. Now I am using KDE 4.11.5. This is the output I get after moving /etc/samba/smb.conf
:~$ kdialog.proper --getopenfilename .
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
kdialog(4512) KSambaSharePrivate::testparmParamValue: We got some errors while running testparm "Load smb config files from /etc/samba/smb.conf
Error loading services.
" 
kdialog(4512) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find smb.conf!

Now (4.11.5), when the file is in place I don't get the KSambaSharePrivate::test warning, but the UPower:: ... ones are still here. That seems to be another bug. This time, I have also checked that kdebugdialog has 'Disabled all debug output' option enabled. Souldn't these kind of (debug?) output messages been printed at lease only when debug output is enabled? Also, why does kdialog need UPower?

Comment 5 David Faure 2014-02-16 11:15:02 UTC

We're mixing issues. The patch in this report is about KUrlCompletion, not about samba shares stuff....

Comment 6 David Faure 2014-09-11 15:32:43 UTC

For the UPower warnings I created https://bugs.kde.org/show_bug.cgi?id=339014 after talking to Lukas.

Comment 7 Nate Graham 2018-04-24 21:19:17 UTC

Is there anything left to do here?

Comment 8 Andrew Crouthamel 2018-09-28 03:40: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 9 Andrew Crouthamel 2018-10-29 02:23:33 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!