GNOME Bugzilla – Bug 637700
GCMD crash on connection to server using SSH
Last modified: 2015-05-29 11:59:31 UTC
System: Ubuntu: 11.04 GCMD version: 1.4 git 2010-12-18 Reproduce: 1. Create a connection using a password for SSH and fill in all information. 2. Edit the connection after the save and remove the "password" so that gcmd is going to ask for a password. 3. Restart gnome-commander. At some point you could get a crash simular to the below: Gdk-ERROR **: The program 'gnome-commander' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 23679 error_code 16 request_code 7 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... (process:14001): Gdk-ERROR (recursed) **: The program 'gnome-commander' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 23680 error_code 1 request_code 0 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) aborting... Multiple segmentation faults occurred; can't display error dialog Tried running this using --sync but without any result. This bug is related to the problem where password is being set wrong in bug: https://bugzilla.gnome.org/show_bug.cgi?id=626390
maybe... Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I will try to get a gdb trace tonight.
Created attachment 177055 [details] Crash report stacktrace Crash report stacktrace
Confirmed in GCMD before v1.4.6: Removing a password from the GCMD GUI could lead to a crash in the connection to a remote server. Since v1.4.6 it is not anymore possible to type your connection password directly in the GCMD GUI. Please refer to bug #653573 for more information about that. If GCMD still crashes after resetting ~/gnome-commander/gnome-commander.xml, please feel free to reopen this bug.