those logs have no error, why did you change the bug to triaged?

getting a log of the error is not trivial, I've renamed gvfsd-trash to
gvfsd-trash-binary and wrote and small gvfsd-trash wrapper which calls
the real binary under valgrind, the log have some jump errors sometime
but those lack the first two symbols as the stacktrace on this bug do,
which is weird because libgioremote-volume-monitor.so which seems to be
the concerned code has debug symbols

-- 
gvfsd-trash crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/252174
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to