Bug 99133

Summary:	sftp in konqueror fails
Product:	[Retired] Red Hat Linux	Reporter:	Phil Cyc <z2rrlgzuxys3x.pyqmmmplz>
Component:	kdebase	Assignee:	Than Ngo <than>
Status:	CLOSED ERRATA	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	mgarski
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-10-25 08:37:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Phil Cyc 2003-07-14 20:52:46 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701

Description of problem:
When trying to connect with konqueror via sftp on any ssh server - openssh as
well as ssh - an error message is shown after about a minute that says

> An error occured while loading sftp://user.tld
> Could not connect to host localhost

and a message window pops up saying

> Error encountered while talking to ssh.

Connecting via command line works w/o problems.

I'm using ssh 3.2.3 and kdebase-3.1-13.


Version-Release number of selected component (if applicable):
kdebase-3.1-13
ssh-3.2.3-1

How reproducible:
Always

Steps to Reproduce:
1. run konqueror
2. try connecting to a server via sftp://user.tld
3. wait about a minute.
    

Actual Results:  
- Konqueror shows:
> An error occured while loading sftp://user.tld
> Could not connect to host localhost

- A message pops up:
> Error encountered while talking to ssh.


Expected Results:  Konqueror should display the contents of $user's home
directory on $some.host.tld.


Additional info:

I replaced OpenSSH with ssh 3.2.3 (www.ssh.com). Nothing else changed.

Comment 1 Marcin Garski 2005-10-24 18:45:30 UTC

Can't reproduce it on KDE 3.4.2 on FC 4.

Comment 2 Than Ngo 2005-10-25 08:37:08 UTC

it seems this bug is fixed in KDE 3.4.2 on FC 3/4