By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 480 - Konqueror: Syncing a folder via SSH with bad proxy gives SIGSEGV
Summary: Konqueror: Syncing a folder via SSH with bad proxy gives SIGSEGV
Status: NEEDINFO
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: amd64 Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-06-26 16:42 CDT by eseesehache
Modified: 2018-05-27 11:10 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Crash trace (2.25 KB, application/octet-stream)
2011-06-26 16:42 CDT, eseesehache 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description eseesehache 2011-06-26 16:42:50 CDT 
Created attachment 69 [details]
Crash trace

When I try to synchonize a folder via Rsync+SSH (button at top right), with a server coniguration of:

user@host:port:/tmp

gave a SIGSEGV. I was using SSH trough a proxy that was misconfigured, so it was intentionally bad configured, but it should display a connection error and not cause konqueror crash. 

With wireshark I saw it tried to connect to the server at port 22, sent three SYN's and gave up.

I'm using Debian Squeeze with the deb's provided in the front page.

Thanks for your effort and giving life to this great desktop!
Miguel.
Comment 1 eseesehache 2011-06-26 17:55:54 CDT 
It's not trivial to reproduce.
Sometimes crash, but other times works as expected (throws an error but doens't die).

One time it crashed rendered Trinity practically unusable (when clicking desktop and another icons dind't launch any of them complaining about DCOP error or something like this).

The configuration of SSH has been done adding ProxyCommand into ~/.ssh/config, so it uses "connect.c" (google it) as wrapper to tunnel it into a SOCKS proxy.

Sorry for my english.
Comment 2 Darrell 2013-05-22 20:32:48 CDT 
Is this report still valid?