[Bug 787327]

2011-06-16 Thread Apport retracing service
() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/787327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 787327] Stacktrace.txt

2011-06-16 Thread Apport retracing service
: bluetooth-properties crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/787327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu

[Bug 787327] ThreadStacktrace.txt

2011-06-16 Thread Apport retracing service
is subscribed to the bug report. https://bugs.launchpad.net/bugs/787327 Title: bluetooth-properties crashed with SIGABRT in __kernel_vsyscall() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/787327/+subscriptions -- ubuntu-bugs mailing list

[Bug 787327] Crash report cannot be processed

2011-06-16 Thread Apport retracing service
://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/787327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 787327] [NEW] bluetooth-properties crashed with SIGABRT in __kernel_vsyscall()

2011-06-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by Jamie Strandboge (jdstrand): Binary package hint: gnome-bluetooth qwqewr ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: gnome-bluetooth 2.91.2.is.2.32.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux

[Bug 787327] Re: bluetooth-properties crashed with SIGABRT in __kernel_vsyscall()

2011-06-03 Thread Jamie Strandboge
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross