** Changed in: gvfs
Importance: Unknown = Critical
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
S B - This bug is fixed. If you are still experiencing crashes in gvfs,
you should submit a new crash report and let the retracer handle it
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a
Thank you. I'm pretty sure it is a crash, or something relating to it is
not functioning properly, causing me to lose my sound. When I run the
command sudo alsa reload, I get this error message:
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/zee/.gvfs
Output information
That's not a crash and is unrelated to this problem. Your problem is
related to bug #225361
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the
Ok, thank you for your concern. I see it as a fix to this issue by the time
I was not too bothered going to know that strange reason. Thank you very
much and good life for you. (my english is too bad, sorry!)
2008/11/11 Chris Coulson [EMAIL PROTECTED]
That's not a crash and is unrelated to this
Yeah, you're right. That bug more corresponds to my problem. Thanks!
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
Sorry if I have not lived up to the circumstances, but my English is almost
nothing, I helped with the translator of Google to be able to understand and
answer your mails. You command a very cordial greeting from Buenos Aires,
Argentina, and I remain at your disposal for what we humbly can help
I still don't understand how to fix this in Intrepid. I have the most
recent stable version of gvfs, so what is still the problem?
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member
Many thanks, seems this fix really cures the bug.
My 'apport' has become unempoyed since then ;-)
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
My English is very bad. Sorry. I am very grateful for the efforts they have
taken in this matter, which fortunately was resolved. Many, thank you very
much. See you soon friends.
2008/11/6 ingo [EMAIL PROTECTED]
Many thanks, seems this fix really cures the bug.
My 'apport' has become unempoyed
Copied hardy-proposed to hardy-updates.
** Changed in: gvfs (Ubuntu Hardy)
Status: Fix Committed = Fix Released
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Congratulations to Sebastian for the fix!
Hardy-amd64
I upgraded these packages from hardy-proposed::
gvfs-fuse
gvfs
gvfs-backends
and tried all the things which prior lead to the crash, like switching user,
(u)mounting nfs-exports, several reboots, ...
The crash is gone, was unable to get
ingo [2008-10-30 11:47 -]:
Is there any need to pin those versions, or will they soon move to the
standard repository?
Yes, they'll move to -updates in a few days, when we don't hear about
regressions.
** Tags added: verification-done
** Tags removed: verification-needed
--
** Attachment added: the debdiff for the stable update
http://launchpadlibrarian.net/18979278/gvfs.debdiff
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop
Accepted into hardy-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:
From the instructions on https://wiki.ubuntu.com/Testing/EnableProposed , I
think you can maybe replace this last line
sudo aptitude -t hardy-proposed
With this command, so as to just install these updates, without the confusing
text-based interface:
sudo aptitude install -t hardy-proposed
please fix, tanks
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing list
Has the Intrepid version had enough testing? It's been over a month now.
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
Sorry could you explain what you mean. and what do you think I have to do
with intrepids amount of testing.
2008/9/12 Richard Ayotte [EMAIL PROTECTED]
Has the Intrepid version had enough testing? It's been over a month now.
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
@matthewrebus: I was refering to Sebastien Bacher response to ingo on
July 24th
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/235698/comments/36.
He mentioned that once that patch was tested in Intrepid that it would
be uploaded as a Hardy update candidate but I haven't seen it yet so I
How do I implement this patch?
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing list
Thanks for the answer! And sorry for the noise :$
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs
Or am I wrong and such bugs don't get fixed usually in finished
distributions? An answer would be nice, I experience this bug every
single boot. /: Thanks!
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification
I think you will find your answer in comment 36.
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/235698/comments/36
That doesn't mean you will necessarily like the answer.
My patch should apply to the version shipped in Hardy, so you could roll
your own in the meantime.
--
Any ideas when it will be fixed in hardy?
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing list
This bug was fixed in the package gvfs - 0.99.4-0ubuntu1
---
gvfs (0.99.4-0ubuntu1) intrepid; urgency=low
* New upstream version:
- Require glib = 2.17.6
- Support und update serialization of GEmblem and GEmblemedIcon
- Add x-content/* support to daemon mounts
- Use
** Changed in: gvfs
Status: New = Fix Released
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs
could you try to open a bug on bugzilla.gnome.org and attach your patch
there rather than add comments rather? the current ubuntu team is
overworked and not writting this code so you are just commenting at the
wrong place to get feedback on your changes, the bugtriagers can send
your patches
alright, you did and that's
http://bugzilla.gnome.org/show_bug.cgi?id=543552, there is several bugs
described on this launchpad bug and that doesn't make things easier to
read, note that dbus should be stable so those crashes are likely
triggered on session closing only and not something users
** Changed in: gvfs
Status: Unknown = New
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing
I got this again just now on Intrepid (gvfs/intrepid uptodate
0.99.3-0ubuntu1). Not fixed, setting status to triaged. If my latest
.crash is useful, let me know and I'll submit it.
** Changed in: gvfs (Ubuntu)
Status: Fix Released = Triaged
--
gvfs-fuse-daemon crashed with SIGSEGV in
What do you know. I was right!
If anyone has the time. (which I don't, sorry). the please try
to recreate this by the procedure I described in the comments above
(https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/235698/comments/27).
You might need to try this a few times to get it to
This bug was fixed in the package gvfs - 0.99.3-0ubuntu1
---
gvfs (0.99.3-0ubuntu1) intrepid; urgency=low
* New upstream version:
- Fix frequent crasher in volume monitor
gvfs (0.99.2-0ubuntu1) intrepid; urgency=low
* New upstream version:
- Move hal and gphoto volume
good to know, but please consider:
1. this bug was reported for Hardy
2. Hardy LTS will survive Intrepid by far with regard to updates.
So, when does the fix come for Hardy?
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received
the fix will be uploaded as an hardy update candidate after getting some
testing in intrepid
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
I very much doubt that the initial issue has been fixed.
It seems that upstream bug 536614 might have been fixed, but that
doesn't deal with shutdown. And if you take 3 seconds to look at the
backtraces in the initial reports in this bug, you will see that
vfs_destroy predominates.
There
** Changed in: gvfs (Ubuntu Hardy)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Confirmed
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug
This bug has been filed upstream as I cannot seem to find a repeat of it
there.
http://bugzilla.gnome.org/show_bug.cgi?id=543552
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of
http://bugzilla.gnome.org/show_bug.cgi?id=543552 contains the same patch as bug
http://bugzilla.gnome.org/show_bug.cgi?id=536614
Doesn't the rule is that a bug is a duplicate when it has the same cause? This
is the case here.
Anyway, there are other bugs at Launchpad that are linked to in gnome
My patch addresses a completely different issue to the bug that was
already linked.
The bug I was fixing has nothing to do with
http://bugzilla.gnome.org/show_bug.cgi?id=536614. In particular, the
problem itemized in this bug is very different to that bug.
My patch can _only_ fix bugs when the
the issue might be similar to
http://bugzilla.gnome.org/show_bug.cgi?id=536614, could you attach you
patch upstream and ask for comments there?
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you
Just some comments in case they are useful.
The program crashes at the line which calls fs-op.destroy in
fuse_fs_destroy.
The ?? in frame 2 is this function. This function must be set by
something that calls the library.
I cannot find any source code for whatever this function is. But it
Well duh. The source code is in gvfs.
And the function is vfs_destroy as shown above.
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Sorry about all the spam. But it appears that subthread_main_loop has
uninitialised data in it when the g_main_loop_quit() function is called.
From my core file:
(gdb) print *subthread_main_loop
$10 = {context = 0x62696c0062696c2f, is_running = 1600349031, ref_count =
1869819507}
That's a lot
I want to unsuscribe myself from the updates. How do I do this? Whenever
I try to do so, I get to a Forbidden page.
--- On Mon, 14/7/08, Austin Lund [EMAIL PROTECTED] wrote:
From: Austin Lund [EMAIL PROTECTED]
Subject: [Bug 235698] Re: gvfs-fuse-daemon crashed with SIGSEGV
I am able to recreate this one now. The following is the recipe:
1. Start with a working DBus session.
2. Run the gvfs-fuse-daemon
3. Kill the DBus session without disconnecting the gvfs-fuse-daemon session.
You should find that it crashes under these conditions and gives exactly
the backtraces
It is not possible to create this in the single thread mode. So here is
a snippit from valgrind from the thread that dies:
==13915== Invalid read of size 4
==13915==at 0x5929D06: g_main_loop_quit (gmain.c:2875)
==13915==by 0x403B39: vfs_destroy (gvfsfusedaemon.c:2147)
==13915==by
This patch fixes this for me.
I don't know if it is the best way of fixing it. Perhaps someone could
suggest something better.
** Attachment added: Patch to fix.
http://launchpadlibrarian.net/16028112/patch1.txt
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
I have this problem, too, since updating last night hardy-proposed.
After gdm login, apport told me about the crash.
Some days ago, I played with intrepid and go that same error. Because of
many problems, I reinstalled hardy in 64 bit. I did not have this bug
anymore. I think that something has
Please fix
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I've had the crash also in Intrepid 8.10
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I also got the crash on 8.10 and can upload the .crash to another bug if
it would help (although I didn't have debug symbols installed at the
time of the crash).
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug
I got the same error message. I've still got the .crash file if another
apport report is needed.
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
This is occurring to me on Hardy Proposed during user login from the GDM
screen. Ive attached the apport crash log.
** Attachment added: Apport crash details
http://launchpadlibrarian.net/15472661/_usr_lib_gvfs_gvfs-fuse-daemon.1000.crash
--
gvfs-fuse-daemon crashed with SIGSEGV in
nullack, please do not attach .crash files to the report, use apport to
send it rather, thanks.
** Attachment removed: Apport crash details
http://launchpadlibrarian.net/15472661/_usr_lib_gvfs_gvfs-fuse-
daemon.1000.crash
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
I'm not sure if those logs are complete, but I think they look like the
program finished.
** Attachment added: gvfs-fuse-daemon-valgrind.log
http://launchpadlibrarian.net/15431855/gvfs-fuse-daemon-valgrind.log
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
** Changed in: gvfs (Ubuntu)
Status: Incomplete = Confirmed
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
i submitted Bug #240840 which is with the dbgsyms installed.
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
Sebastien, no offense meant, but the backtraces of hardy and intrepid
look very similar, what makes you think it'd be a different issue?
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a
could be the same issue but almost nobody is getting the issue in hardy
where it seems to crash at each session change on intrepid
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member
Sebastien - I'm not sure it is possible to say that almost nobody is
suffering this bug in Hardy. Bare in mind that Apport is disabled by
default, so the only people who will ever notice the crash are the
people who have manually re-enabled Apport (like myself). The bug seems
to have no other
I'm already waiting for it to crash but I'm not sure what triggers it (I
was one of the duplicates).
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
could you try to obtain a valgrind log following the instructions at
[WWW] https://wiki.ubuntu.com/Valgrind and attach the file to the bug
report?
** Changed in: gvfs (Ubuntu)
Status: Confirmed = Incomplete
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
happened again today just after login, seems it is somting essential!
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
the intrepid issue is an another bug than the hardy one and seems to be
due to some other component update there
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/235698
You received this bug notification because you are a member of Ubuntu
Desktop
This crash occurs in my current intrepid system with
#0 0x7f225fb86a5a in pthread_mutex_lock () from /lib/libpthread.so.0
#1 0x7f226083f07e in IA__g_main_loop_quit (loop=0x658f00) at
/build/buildd/glib2.0-2.17.0/glib/gmain.c:2946
#2 0x00403bea in vfs_destroy (param=value
had the very same crash this morning just after booting and log-in.
To obtain a backtrace we need the -dbgsym or -dbg packages for 'gfs-fuse'.
They are not available in the Hardy repositories :-(
--
gvfs-fuse-daemon crashed with SIGSEGV in pthread_mutex_lock()
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.
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/14781906/CoreDump.gz
**
68 matches
Mail list logo
