gvfsd-trash crashed (maybe sshfs related)

Bug #317540 reported by Bogdan Butnaru
6
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gvfs

Not sure what causes this. I've seen it happen spontaneously in the background (e.g., while surfing the net, or even when I'm not near the computer).

I _think_ this happens only after bug #317237, but since there are delays involved with that one too I'm not quite 100% certain.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
NonfreeKernelModules: nvidia
Package: gvfs 1.1.3-0ubuntu2
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.2 /org/gtk/gvfs/exec_spaw/0
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? () from /lib/libc.so.6
 free () from /lib/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: gvfsd-trash crashed with SIGSEGV in free()
Uname: Linux 2.6.28-4-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse-rt sambashare

Tags: apport-crash
Revision history for this message
Bogdan Butnaru (bogdanb) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_int_free () from /lib/libc.so.6
free () from /lib/libc.so.6
trash_dir_set_files (dir=0x1864900, items=0x0)
trash_dir_free (dir=0x1864900) at trashdir.c:314
trash_watcher_remount (watcher=0x1851d50)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gvfs:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem. Could you also attach your .xsession-errors to the bug when you get the issue?

Changed in gvfs:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue in the current jaunty version?

Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

I'm not sure how to check; this always happens more or less randomly, so I don't know how to trigger it.

I still get bug #317237 regularly, I'm not sure about this one. (I suspect Apport doesn't catch everything: I've had several types of crashes that I've only seen reported once or occasionally by Apport despite the crash itself happening repeatedly.)

Revision history for this message
Sebastien Bacher (seb128) wrote :

did youg et the issue again since?

Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

I haven't had Apport report it crashing, no; but like I said, I've seen at times crashes that Apport didn't mention, so I can't be sure. (Since this particular application doesn't do anything immediately obvious, I can't tell if it crashes unless I'm looking for it; actually, what does it do?)

Revision history for this message
Sebastien Bacher (seb128) wrote :

there has been no recent duplicated and the jaunty code changed a lot let's close for now and reopen if somebody run into it again later

Changed in gvfs (Ubuntu):
status: Incomplete → 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.