Re: gvfsd-dav SIGABRT when using WebDAV [& how-to-get-a-core?]
- From: Tomas Bzatek <tbzatek redhat com>
- To: awilliam whitemice org
- Cc: gvfs-list gnome org
- Subject: Re: gvfsd-dav SIGABRT when using WebDAV [& how-to-get-a-core?]
- Date: Tue, 08 Jan 2013 13:55:18 +0100
On Fri, 2013-01-04 at 09:46 -0500, Adam Tauno Williams wrote:
> Backtrace
> =========
> Program received signal SIGABRT, Aborted.
> 0x00007f61351aad25 in raise () from /lib64/libc.so.6
> (gdb) bt
Thanks for the backtrace, could you also try "t a a bt" to get backtrace
of all active threads? Most likely there won't be more anyway.
Installing debugging symbols would help to reveal more details too
(usually -debuginfo or -dbg packages).
> write(2, "**\nGLib:ERROR:gmain.c:2781:g_main_context_acquire: assertion
> failed: (context->owner_count == 0)\n", 97) = 97
This is important, yet it doesn't tell us much either. What is the glib
and libsoup versions installed? Is the gvfs package compiled against
these particular versions?
> DOH! Ok, got that. Right click -> New file from template ... CRASH!
Tried to reproduce on two different systems, no luck. A gvfs daemon log
would be useful for this. Try killing all gvfs processes and start
`GVFS_DEBUG=1 GVFS_HTTP_DEBUG=all /usr/libexec/gvfsd -r` in the
terminal, grabbing the output. That would tell us which operations were
in progress.
--
Tomas Bzatek
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]