After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 750087 - gnome-commander brakes at SSH server connections
gnome-commander brakes at SSH server connections
Status: RESOLVED OBSOLETE
Product: gnome-commander
Classification: Other
Component: networking
unspecified
Other Linux
: Normal major
: 1.4
Assigned To: GNOME Commander maintainer(s)
GNOME Commander maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-05-29 07:15 UTC by tomislav.parcina
Modified: 2015-06-01 07:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tomislav.parcina 2015-05-29 07:15:34 UTC
gnome-commander brakes every time I try to connect to SSH server. I use to connect to that server successfully, but now it brakes every time.

My details:
- Fedora release 20 (Heisenbug)
- xfce 4.10
- gnome-commander 1.5.0

Best regards.
Comment 1 Uwe Scholz 2015-05-29 12:01:42 UTC
Thanks for taking the time to report this bug. Are you sure to use GCMD v1.5.0? This is not the current stable version. We even need a little bit more information. Up to now it might be a duplicate of bug #637700.

You'll need to add a stack trace to this bug report; please see http://live.gnome.org/GettingTraces for more information about how to do so.
Thanks in advance!
Comment 2 tomislav.parcina 2015-05-29 13:02:54 UTC
When I open about, there I see "gnome-commander 1.5.0". But "yum info gnome-commander" shows "Version : 1.4.5". Which info is correct?

I have installed debuginfo but it doesn't detect the crash. If I run "gdb gnome-commander" and then "run" I get:
Starting program:  
No executable file specified.
Use the "file" or "exec-file" command.

If I execute "file gnome-commander" I get:
"/usr/bin/gnome-commander": not in executable format: File format not recognized

I need more help how to capture trace.

Best regards.
Comment 3 Uwe Scholz 2015-05-31 13:15:30 UTC
It seems as if Fedora accidentally used the "master" branch of our git repository for creating the current 1.4.5 package instead of the "gcmd-1-4" branch. It could be that this is related to your problem, but I don't really know. 

It might be that this will be fixed in the next version coming out in some days: Version 1.4.7 has been introduced into Fedora recently (see https://admin.fedoraproject.org/updates/gnome-commander). 

For getting the GCMD stack trace: Please check for which architecture gnome-commander was compiled for. Just do 

file /usr/bin/gnome-commander

If the output is something like:

"... ELF 64-bit LSB executable, x86-64 ..."

you should also install a 64bit version of gdb. So you have to check "file /usr/bin/gdb", too.

If the condition from above does not hold, you have to reinstall gdb for the correct architecture.
Comment 4 Mamoru TASAKA 2015-06-01 00:35:53 UTC
Please try gnome-commander-1.4.7-1.fc20, which will appear
on testing in a few days. You can directly download the rpm
from:

http://koji.fedoraproject.org/koji/buildinfo?buildID=640170
Comment 5 tomislav.parcina 2015-06-01 07:44:42 UTC
(In reply to Mamoru TASAKA from comment #4)
> Please try gnome-commander-1.4.7-1.fc20, which will appear
> on testing in a few days. You can directly download the rpm
> from:

In my repo, 1.4.7 is still not available. But 1.4.6 has become available, and this bug is not present there. :)

Guys, thank you for your help.

Best regards.