[Bug 201585] Re: gvfsd-smb crashed with SIGSEGV
** Changed in: gvfs Status: New => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/201585 Title: gvfsd-smb crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/201585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201585] Re: gvfsd-smb crashed with SIGSEGV
** Changed in: gvfs Importance: Unknown = Critical -- gvfsd-smb crashed with SIGSEGV https://bugs.launchpad.net/bugs/201585 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 https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201585] Re: gvfsd-smb crashed with SIGSEGV
As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information. ** Changed in: gvfs (Ubuntu) Importance: Medium = Low Status: Incomplete = Invalid -- gvfsd-smb crashed with SIGSEGV https://bugs.launchpad.net/bugs/201585 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201585] Re: gvfsd-smb crashed with SIGSEGV
** Changed in: gvfs Status: Unknown = New -- gvfsd-smb crashed with SIGSEGV https://bugs.launchpad.net/bugs/201585 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201585] Re: gvfsd-smb crashed with SIGSEGV
upstream comment on the bug It seems we're getting a GVfsJob with a NULL run method. I don't see how that is possible though. If someone can reproduce this in gdb please try p (char *)g_type_name_from_instance (job) in frame 1 in thread 1. (i.e. the g_vfs_job_run call) can you trigger the bug easily? could you give it a try? I can guide you to do that if required ** Changed in: gvfs (Ubuntu) Status: Triaged = Incomplete -- gvfsd-smb crashed with SIGSEGV https://bugs.launchpad.net/bugs/201585 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201585] Re: gvfsd-smb crashed with SIGSEGV
Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=522190 ** Visibility changed to: Public ** Changed in: gvfs (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: New = Triaged ** Also affects: gvfs via http://bugzilla.gnome.org/show_bug.cgi?id=522190 Importance: Unknown Status: Unknown -- gvfsd-smb crashed with SIGSEGV https://bugs.launchpad.net/bugs/201585 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
