We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: nautilus (Ubuntu)
did you get the issue again?
--
nautilus crashed with SIGSEGV after bluetooth oops
https://bugs.launchpad.net/bugs/306700
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
Sure: will give it a go.
2009/3/11 Sebastien Bacher seb...@ubuntu.com
could you try again if you can trigger the crash easily and describe
how?
--
nautilus crashed with SIGSEGV after bluetooth oops
https://bugs.launchpad.net/bugs/306700
You received this bug notification because you are a
could you try again if you can trigger the crash easily and describe
how?
--
nautilus crashed with SIGSEGV after bluetooth oops
https://bugs.launchpad.net/bugs/306700
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Also, please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will greatly aid us in tracking down your problem and resolving
this bug.
**
Hi: apologies for the somwhat flip comment in the bug report: I may have
been frustrated by not being able to find the right component.
From memory, I had a bluetooth 'phone connected and was browsing the
pictures folder.
I believe the URL was something like obex://{GUID}
The problem seems to be
