| Summary: | Konqueror: Syncing a folder via SSH with bad proxy gives SIGSEGV | ||
|---|---|---|---|
| Product: | TDE | Reporter: | eseesehache |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | NEEDINFO --- | ||
| Severity: | normal | CC: | bugwatch, darrella |
| Priority: | P5 | ||
| Version: | 3.5.13.x [Trinity] | ||
| Hardware: | amd64 | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Attachments: | Crash trace | ||
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. Is this report still valid? |
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.