Bug 271977

Summary:	Incorrectly formatted smb path causes dolphin to crash
Product:	[Unmaintained] kio	Reporter:	Patrick Grimm <patrick.grimm>
Component:	smb	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	adawit, andresbajotierra, faure, kdelibs-bugs-null
Priority:	NOR
Version First Reported In:	4.6
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	KDE crash handler output dolphin --nofork console output

Description Patrick Grimm 2011-04-29 14:14:34 UTC

Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

Dolphin will crash if the user enters a malformed smb address as a places shortcut and attempts to navigate to the smb share by clicking the places shortcut.

Reproducible: Always

Steps to Reproduce:
1. Create a places entry in dolphin to an smb share with a url that has no trailing / such as smb://192.168.1.100
2. Click the places shortcut and enter your access credentials.

Actual Results:  
Dolphin crashes with a seg fault (11)

Expected Results:  
Dolphin should gracefully fail or automatically add the trailing / to the malformed address.

Dolphin will also crash in the same manner if the malformed smb address is entered directly in the location bar.

I can not actually find documentation on the format of the address so when I say malformed this is strictly based on my observations. The address referenced above should be valid from a user perspective.

Comment 1 Dario Andres 2011-05-01 14:58:39 UTC

[Comment from a bug report cleaner]
I guess this could be related to bug 266903 / bug 197851 (which also talks about "malformed" paths). A backtrace could be useful to identify if they are indeed related.
Regards

Comment 2 Patrick Grimm 2011-05-01 15:23:03 UTC

Created attachment 59496 [details]
KDE crash handler output

I installed the kde debug symbols and created a crash report for this.

Comment 3 Dario Andres 2011-05-01 15:24:22 UTC

[Comment from a bug report cleaner]
Yes, the backtrace is indeed related too. Thanks

Comment 4 David Faure 2011-05-02 23:44:22 UTC

When I type smb://192.168.0.2 in dolphin's location bar, I don't get such a crash; there must be something more.

Please look at .xsession-errors or start dolphin --nofork in a terminal, there should be additional messages. From the backtrace I see that "dir" is null, so at least this should show up:
"Internal error: itemsInUse did not contain ...."

Comment 5 Patrick Grimm 2011-05-03 04:33:40 UTC

Created attachment 59564 [details]
dolphin --nofork console output

Results of dolphin --nofork are attached. Note that the smb share is being accessed over a cisco vpn session using KVpnc.

Comment 6 Dawit Alemayehu 2013-09-02 16:13:52 UTC


*** This bug has been marked as a duplicate of bug 316339 ***