*** This bug is a duplicate of bug 68347 ***
Marking this bug as a duplicate of bug 68347 - it has a debug backtrace.
** This bug has been marked a duplicate of bug 68347
crashes on start-up sometimes
** Changed in: bluez-gnome (Ubuntu)
Status: Needs Info => Rejected
--
Problem repor
I could imagine that it crashed on shutting the machine down and apport
popped up with the crash report the next time you logged in. Maybe it
was an upgrade issue. *shrug* :/
--
Problem report for bluez-passkey-gnome
https://launchpad.net/bugs/66323
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
I personally have never seen a crash with bt-applet. The D-Bus proxy
object has the weird behavior that I described, but that's it. I have to
make some small adjustments for the icon display policy and then I will
release a new version. Postponing this to edgy-updates should be fine.
--
Problem r
On the question what I was doing when I got the error message: I just
booted my system, and I got the error either while the desktop manager
was loading, of right after it finished loading (not entirely sure).
Either way, it was before I started doing stuff myself - the bug
manifested itself during
I take this of the list off release critical bugs. I was not able to
reproduce this and the patch clearly needs more testing than we can do
in 9 days. This is a candidates for edgy-updates.
** Changed in: bluez-gnome (Ubuntu)
Target: ubuntu-6.10 => None
--
Problem report for bluez-passkey
Syncing the full source of bt-applet is a better idea. There exists
another problem with the current use of the D-Bus proxy objects and
attaching signal handlers. It is enough to attach the adapter signals
once per lifetime of bt-applet. It doesn't matter if the adapter get
removed or reattached. I
I extracted what I think are the necessary bits from
http://librarian.launchpad.net/4822238/implement_icon_policy_settings.patch
- can you try with this patch? If you're not comfortable with building
your own package, I'm happy to attach a i386 or amd64 package.
** Attachment added: "proposed patc
Is this in any way reproducible? Do you remember what you did, when it
crashed?
** Changed in: bluez-gnome (Ubuntu)
Status: Unconfirmed => Needs Info
--
Problem report for bluez-passkey-gnome
https://launchpad.net/bugs/66323
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Thanks for the Bug report. This seems to be the dbus problem that Marcel
referred to. It should be fixed in CVS, now we need to find the right
patch for it.
** Changed in: bluez-gnome (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Bluetooth
Target: None => ubuntu
