I tried your work-around, but it did not work for me.
tau ~] sudo dpkg -i bluez_4.84-0ubuntu1_i386.deb
dpkg: warning: downgrading bluez from 4.96-0ubuntu4 to 4.84-0ubuntu1.
And it re-started bluetooth. So far so good.
The GUI remains completedly buggared as described before.
Something is different though. When I request to browse files
on one of my phones, an icon appears on the desktop. It offers me
to cancel the operation, and after a few seconds, dies:
Failed to mount OBEX volume: DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
What a mess.
How can this still be broken after all this time, when
it was working flawlessly last year?
Oliver,
I tried your work-around, but it did not work for me.
tau ~] sudo dpkg -i bluez_4. 84-0ubuntu1_ i386.deb
dpkg: warning: downgrading bluez from 4.96-0ubuntu4 to 4.84-0ubuntu1.
And it re-started bluetooth. So far so good.
The GUI remains completedly buggared as described before.
Something is different though. When I request to browse files
on one of my phones, an icon appears on the desktop. It offers me
to cancel the operation, and after a few seconds, dies:
Failed to mount OBEX volume: DBus error org.freedesktop .DBus.Error. NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
What a mess.
How can this still be broken after all this time, when
it was working flawlessly last year?