gnome-commander crashed with signal 5 in _XError() after connecting to FTP server using gnome-keyring authentication

Bug #333318 reported by Aurius Bendikas Chang
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Baltix
New
Undecided
Unassigned
gnome-commander (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: gnome-commander

Create FTP connection and check that will be using Gnome Keyring for authentication.
Select new connection and click connect.
Will crash in 2 sec.
100% reproducable.

Works fine if using normal authentication

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-commander
Package: gnome-commander 1.2.7-1
ProcCmdline: gnome-commander
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-commander
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libbonoboui-2.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XEventsQueued () from /usr/lib/libX11.so.6
Title: gnome-commander crashed with signal 5 in _XError()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare video

https://bugzilla.gnome.org/show_bug.cgi?id=659281

And this is an answer from gnome-commander developer:

"The crash is caused by opening auth dlg by a thread not running the main
loop...

The problem will be fixed in the nearest release - 1.4.

 As a workaround, please add manually corresponding password/key pair to
'default' keyring using Seahorse."

Revision history for this message
Aurius Bendikas Chang (aurius-bendikas) wrote :
Changed in gnome-commander:
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gdk_x_error (display=0x89cfc30, error=0xbfabd9a8)
bonobo_x_error_handler (display=0x89cfc30, error=0x8e6d100)
_XError (dpy=0x89cfc30, rep=0x8cd22a8)
process_responses (dpy=0x89cfc30, wait_for_first_event=0,
_XEventsQueued (dpy=0x89cfc30, mode=2)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-commander:
importance: Undecided → Medium
visibility: private → public
Revision history for this message
Alessio Treglia (quadrispro) wrote :

Is this reproducible with the latest release available on Maverick?

Changed in gnome-commander (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Aurius Bendikas Chang (aurius-bendikas) wrote :

Can not verify that it is reproducible on Maverick, but it is reproducible on 10.04 LTS.

Revision history for this message
Mantas Kriaučiūnas (mantas) wrote :

It seems crash after connecting to FTP server using gnome-keyring authentication still appears with latest gnome-commander from Ubuntu Maverick and Natty - I've backported gnome-commander 1.2.8.8 from Natty to Ubuntu 10.04 LTS and can confirm the crash.

gnome-commander 1.2.8.8 packages for Ubuntu 10.04 LTS are available in official Baltix GNU/Linux repository:
https://launchpad.net/~baltix-members/+archive

Maybe this bug is fixed in latest gnome-commander 1.2.8.9 (released 2010-12-03), look at changelog:
http://ftp.acc.umu.se/pub/GNOME/sources/gnome-commander/1.2/gnome-commander-1.2.8.9.changes

Changed in gnome-commander (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Mantas Kriaučiūnas (mantas) wrote :
Download full text (7.3 KiB)

It's strange, bug terminal output after crash when connecting to FTP server using gnome-keyring authentication is different every time:

ubuntu@ubuntu:~$ gnome-commander --sync
gnome-commander: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnome-commander: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Segmentation fault (core dumped)
ubuntu@ubuntu:~$

Another try:

ubuntu@ubuntu:~$ gnome-commander --sync
gnome-commander: ../../src/xcb_io.c:249: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
Aborted (core dumped)
ubuntu@ubuntu:~$

One more time:

ubuntu@ubuntu:~$ gnome-commander --sync

** (gnome-commander:25959): WARNING **: Failed to open file '/home/ubuntu/.gnome-commander/gnome-commander.xml': No such file or directory
*** glibc detected *** gnome-commander: double free or corruption (fasttop): 0x092a8798 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6(+0x6b591)[0x51ab591]
/lib/tls/i686/cmov/libc.so.6(+0x6cde8)[0x51acde8]
/lib/tls/i686/cmov/libc.so.6(cfree+0x6d)[0x51afecd]
/usr/lib/libX11.so.6(+0x4197f)[0x671997f]
/usr/lib/libX11.so.6(_XEventsQueued+0x56)[0x671a356]
/usr/lib/libX11.so.6(XPending+0x68)[0x6702a68]
/usr/lib/libgdk-x11-2.0.so.0(+0x53909)[0xd9d909]
/lib/libglib-2.0.so.0(g_main_context_check+0x2c9)[0x5b7799]
/lib/libglib-2.0.so.0(+0x3f0ce)[0x5b80ce]
/lib/libglib-2.0.so.0(g_main_loop_run+0x187)[0x5b8817]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb9)[0x10b93c9]
gnome-commander[0x80ceeca]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0x5156bd6]
gnome-commander[0x805d9a1]
======= Memory map: ========
00110000-00129000 r-xp 00000000 00:10 3782 /usr/lib/libatk-1.0.so.0.3009.1
00129000-0012a000 ---p 00019000 00:10 3782 /usr/lib/libatk-1.0.so.0.3009.1
0012a000-0012b000 r--p 00019000 00:10 3782 /usr/lib/libatk-1.0.so.0.3009.1
0012b000-0012c000 rw-p 0001a000 00:10 3782 /usr/lib/libatk-1.0.so.0.3009.1
0012c000-001c6000 r-xp 00000000 00:10 2364 /usr/lib/libgio-2.0.so.0.2400.1
001c6000-001c7000 ---p 0009a000 00:10 2364 /usr/lib/libgio-2.0.so.0.2400.1
001c7000-001c8000 r--p 0009a000 00:10 2364 /usr/lib/libgio-2.0.so.0.2400.1
001c8000-001c9000 rw-p 0009b000 00:10 2364 /usr/lib/libgio-2.0.so.0.2400.1
001c9000-001ca000 rw-p 00000000 00:00 0
001ca000-001e2000 r-xp 00000000 00:10 3762 /usr/lib/libgdk_pixbuf-2.0.so.0.2000.1
001e2000-001e3000 r--p 00017000 00:10 3762 /usr/lib/libgdk_pixbuf-2.0.so.0.2000.1
001e3000-001e4000 rw-p 00018000 00:10 3762 /usr/lib/libgdk_pixbuf-2.0.so.0.2000.1
001e4000-001ee000 r-xp 00000000 00:10 3774 /usr/lib/libpangocairo-1.0.so.0.2800.0
001ee000-001ef000 r--p 00009000 00:10 3774 /usr/lib/libpangocairo-1.0.so.0.2800.0
001ef000-001f0000 rw-p 0000a000 00:10 3774 /usr/lib/libpangocairo-1.0.so.0.2800.0
001f0000-001f3000 r-xp 00000000 00:10 862 /usr/lib/libgmodule-2.0.so.0.2400.1
001f3000-001f4000 r--p 00002000 00:10 862 /usr/lib/libgmodule-2.0.so.0.2400.1
001f4000-001f5000 rw-p 00003000 00:10 862 /usr/lib/libgmodule-2.0.so.0.2400.1
001f5000-001f9000 r-xp 00000000 00:10 852 /usr/lib/libgth...

Read more...

Revision history for this message
Alessio Treglia (quadrispro) wrote :

Is this reproducible with the latest release available in Natty?

Revision history for this message
Alessio Treglia (quadrispro) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Changed in gnome-commander (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alessandro (maetech) wrote :

I have this bug on Ubuntu 10.04 with gnome-commander 1.2.8.5
Trying to open SSH connection to a server, while the dialog window says "connecting...", after about 10 seconds the program crashes. In the terminal says: "gnome-commander: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0." . Reproducible.

Revision history for this message
Shadar (zxlmm) wrote :

Ubuntu 10.04 - same thing as Alessandro showed above.

And sometimes this instead:

The program 'gnome-commander' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 26452 error_code 158 request_code 148 minor_code 8)
  (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.)
The program 'gnome-commander' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
  (Details: serial 26456 error_code 158 request_code 148 minor_code 7)
  (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.)
Segmentation fault

Revision history for this message
Shadar (zxlmm) wrote :

I've just built new version of gnome-commander 1.2.8.12 from source - and bug is still there.

Revision history for this message
Shadar (zxlmm) wrote :

I filed this bug in gnome bugzilla:
https://bugzilla.gnome.org/show_bug.cgi?id=659281

And this is an answer from gnome-commander developer:

"The crash is caused by opening auth dlg by a thread not running the main
loop...

The problem will be fixed in the nearest release - 1.4.

 As a workaround, please add manually corresponding password/key pair to
'default' keyring using Seahorse."

description: updated
Revision history for this message
Uwe (turboscholz) wrote :

I think this bug is obsolete now, because v.1.4 was released a while ago. If you still experience a crash in v1.4 when connecting to a FTP server, please have a look at
https://bugzilla.gnome.org/show_bug.cgi?id=751117

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.