** Changed in: gvfs
Importance: Unknown = Critical
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Copied to hardy-updates.
** Changed in: gvfs (Ubuntu Hardy)
Status: Fix Committed = Fix Released
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for
** Tags added: verification-done
** Tags removed: verification-needed
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing
It works for me. I saved numerous times without a single crash today.
Thanks!
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs
** Attachment added: debdiff for the stable update
http://launchpadlibrarian.net/16302766/gvfs.debdiff
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for
** Description changed:
Version: 0.2.4-0ubuntu1
I had great hopes for today's update in hardy-proposed given this
changelog entry Fix fuse locking and file handle life-cycle issues
that were causing frequent crashes. Alas even after a reboot, the
gvfs-fuse-daemon is still very
Accepted into -proposed, please test and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: gvfs (Ubuntu Hardy)
Status: Confirmed = Fix Committed
** Tags added:
I don't mean to rush anyone, but about how long does it take before
these fixes appear in Hardy proposed?
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for
** Changed in: gvfs (Ubuntu Hardy)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Confirmed
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a
Upstream has since also added
http://bugzilla.gnome.org/attachment.cgi?id=114799action=view
as 'belt and braces' for another locking issue gvfs-fuse-lock-on-
open.patch
Can both of these be sent for hardy-proposed, please?
--
regular segfaults with .gvfs access
Ah, the real bug has been found and fixed upstream. I can confirm it [1]
resolves the problem.
[1] http://bugzilla.gnome.org/attachment.cgi?id=114694action=view
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a
This bug was fixed in the package gvfs - 0.99.1-0ubuntu3
---
gvfs (0.99.1-0ubuntu3) intrepid; urgency=low
* debian/patches/90_from_svn_fix_fuse_crasher.patch:
- change from svn to fix fuse crasher (lp: #235326)
-- Sebastien Bacher [EMAIL PROTECTED] Fri, 18 Jul 2008 18:15:32
** Changed in: gvfs
Status: In Progress = Fix Released
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing list
** Changed in: gvfs
Status: New = In Progress
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing list
Since the glib2.0 release 2.6.14 on 3rd July in hardy-proposed, I am no
longer seeing this issue. Can anyone else confirm?
Current version is 2.16.4-0ubuntu2 with gvfs-fuse at 0.2.5-0ubuntu1 (the
real bug seems to be in glib2.0, not the fuse daemon)
--
regular segfaults with .gvfs access
I've been experiencing the same problem for since the release of Ubuntu
8.04 and the fix mentioned at the top also didn't help me. I just want
to mention how I always experience the problem just in case it offers
some clues:
1. Make a Samba share on another server. Mine are unpublished i.e. you
thank you for your work on that, could you install libglib2.0-0-dbgsym
and get a new valgrind log?
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I've sent the issue upstream now on
http://bugzilla.gnome.org/show_bug.cgi?id=536614
** Changed in: gvfs (Ubuntu)
Status: Incomplete = Triaged
** Also affects: gvfs via
http://bugzilla.gnome.org/show_bug.cgi?id=536614
Importance: Unknown
Status: Unknown
--
regular segfaults
** Changed in: gvfs
Status: Unknown = New
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing list
libglib2.0-0-dbgsym now installed... valgrind log attached.
I have also sent this to the upstream bug you listed.
** Attachment added: valgrind.log
http://launchpadlibrarian.net/15015115/valgrind.log
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: gvfs (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) =
First I undid the shell script described above so that the non-debug
hardy-proposed binary was present at /usr/lib/gvfs/gvfs-fuse-daemon,
then installed the .ddeb:
-rwxr-xr-x 1 root root 46032 2008-05-27 15:29
/usr/lib/debug/usr/lib/gvfs/gvfs-fuse-daemon
And finally logged out + in, and followed
As per https://wiki.ubuntu.com/Valgrind ...
** Attachment added: valgrind-gvfs-fuse-daemon.log
http://launchpadlibrarian.net/14773116/valgrind-gvfs-fuse-daemon.log
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you
OK, I've re-read the backtrace and realised I need to flesh it out with
symbols from 'gvfs' , libfuse2, et al... so here's another try attached
- hopefully this will be more use.
** Attachment added: gdb-gvfs-fuse-daemon.txt
http://launchpadlibrarian.net/14777444/gdb-gvfs-fuse-daemon.txt
--
** Attachment added: gvfs.log
http://launchpadlibrarian.net/14754180/gvfs.log
--
regular segfaults with .gvfs access
https://bugs.launchpad.net/bugs/235326
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
--
SUCCESS!
Simply by adding '-s' to the gvfs-fuse-daemon arguments (disable multi-
threaded operation) I am able to hammer away with complete reliability!
I do not notice any loss in performance. In the interim, I have renamed
/usr/lib/gvfs/gvfs-fuse-daemon to /usr/lib/gvfs/gvfs-fuse-daemon.real
26 matches
Mail list logo
