gvfsd-ftp crashed with SIGABRT in raise()

Bug #765155 reported by Mihai Stefan
68
This bug affects 15 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gvfs

I tried connecting to a FTP bookmark in Nautilus, an gvfs crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gvfs-backends 1.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Mon Apr 18 23:38:54 2011
ExecutablePath: /usr/lib/gvfs/gvfsd-ftp
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/gvfs/gvfsd-ftp --spawner :1.10 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libgnome-keyring.so.0
Title: gvfsd-ftp crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to natty on 2011-04-14 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare www-data

Revision history for this message
Mihai Stefan (mihaistefan88) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gvfs (Ubuntu):
status: New → Confirmed
Revision history for this message
Jhosman Lizarazo (jhosman) wrote :

I use nautilus as media center and connect to FTP servers, when establishing a connection all perecta behaves, but we know that an FTP server is a timeout, after overcoming the inactivity timeout, I try and retrieve the contents Nautilus crashed, the FTP server I have it in my favorites. When I open nautilus, favorite disappears, I try to create a new connection, nautilus crashed again, then restarts already there favorite icon and I can make the connection again.

Revision history for this message
Jhosman Lizarazo (jhosman) wrote :

I use Ubuntu Raring 13.04

Revision history for this message
Dmitry Misharov (quarckster) wrote :

Confirm this bug for Raring

Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

Also found using 12.04 LTS

Revision history for this message
dino99 (9d9) wrote :

This version has expired

Changed in gvfs (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

Not invalid: 12.04 is LTS.

Changed in gvfs (Ubuntu):
status: Invalid → New
Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

Extra debug information from recent crash should have been added to the bug report automatically. However, I don't see it.

Revision history for this message
dino99 (9d9) wrote :

@jan
if you are concerned by that issue on a recent release, then open a new report with the required debug info.
That one is useless and set back to invalid

Changed in gvfs (Ubuntu):
status: New → Invalid
Revision history for this message
jan (jan-ubuntu-h-i-s) wrote :

Well 12.04 LTS is a recent release, supported till mid 2017.
https://wiki.ubuntu.com/LTS

The error report apparently could not be attached to a bug set to invalid.
I'm not sure where launchpad has not stored my data.

jan (jan-ubuntu-h-i-s)
Changed in gvfs (Ubuntu):
status: Invalid → New
Revision history for this message
dino99 (9d9) wrote :

@jan

how do you think devs can find a solution from a dead release ? Precise does not use the same libs as Natty. So closing that report again.
Open your own report with the Precise crash file (use ubuntu-bug on the crash file)

Changed in gvfs (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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