[SOLVED] After recent wayland / bluez upgrade in debian sid, blueman? has error
Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
After recent wayland / bluez upgrade in debian sid, blueman? has error
Hi All,
Apparently this is a well known bug, so I'm surprised not to find any posts on it at LQ.
There were recent (july) upgrades to some wayland packages and to bluez. I recently reinstalled sid.
Now, after login, when the desktop opens I get this error message:
"org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process org.blueman.Mechanism received signal 5
You might not be able to connect to the Bluetooth network via this machine"
Apparently this has been traced to one of two problems. Either recent changes to wayland (1.4.0-1 => 1.5.0-1) and / or to new release of bluez (4.x => 5.x).
The result is that, after stopping and restarting it with blueman, bluetooth can find my phone, and pair with it. Then, when I try to connect to Network Access Point, it connects, but fails to get any IP address.
It seems I have to downgrade packages, but this is not proving so easy. For example, as far as I can see, apt-get cannot find the old libwayland-client0 version 1.4.0-1 in any of the sid or wheezy repos. Downgraded bluez successfully, but was unsure which version to go back to, and this has made no difference so far.
Hi descendantcommand,
I can get the .deb files easily, and have downloaded libwayland-client0_1.4.0-1.deb and copied into /var/cache/apt/archive, but
apt-get update is not admitting use of snapshot archives, on the basis that the archive is eg 120 days out of date. And it does not see the package that I put in the local apt-get archives.
Were you thinking of using dpkg??? Man page says on downgrades there is no dependency checking. But many many packages depend on (eg) libwayland-client0.
Got it first time, and now posting this with my acer c720chromebook, running debian sid, tethered with bluetooth to the phone's internet connection. To get apt-get to ignore the expired nature of the snapshot archive, I used this command:
Could not find that functionality anywhere in apt preferences documentation.
And then to check that only minimal bad things could happen upon the downgrade, first simulate:
which should read: ...debian.org/archive/debian/20140131T221256Z/ sid main except the above URL did not show right here.
And bluetooth now good. There are several wayland related packages, but that seems to be the only one that needed to be downgraded.
Thanks for your help.
I shall now try to reboot! Assuming that's good, I'll still wait a few more days before marking this thread solved: To see what else (if anything) has been broken.
Andrew.
Last edited by aal; 08-17-2014 at 06:06 AM.
Reason: URL did not show right.
On boot, bluetooth not working, but after turn off and turn on with blueman, it works, however I have had to refresh IP address too many times.
Battery monitor freezes. Only works once when start xfce4-powermanager. So need restart every time I look at battery.
Panel freezes occasionally.
AND of real importance, the battery life is not what it used to be before taking the machine to Acer service centre, here in New Delhi. There was a step change in battery capacity as shown by xfce4-powermanager, by ~ -5% of capacity. But the lifetime on battery is only about half of what it was, or less. Either the service centre swapped batteries, or something is radically different in the way the software is now driving this machine.
I don't want to be too paranoid about the service centre. I only concluded the problem is real today and just started looking at it. Both cpus are running "performance" 1.4 GHz. I would rather they were set to "on demand". Or fixed at 800.
Is that configurable from xfce? I recall they were set that way before, but cannot find the tool anymore.
Alternatively, what's the console command, and I'll go the man page.
After testing on an AIRCON train, from delhi to jaipur, it is now clear what's been going on with my battery life.
I had formed ideas about battery life in North India - Dharmshala and Ladakh - 20-25C. After the repair, I had rebuilt the machine in a delhi hotel room at ~40C. Now, with the aircon, the battery full capacity as shown by power-manager, has recovered. Have had the machine on for 6 hours, and showing 29% battery. If I go to Helsinki, the battery capacity will probably exceed specification.
Apologies to Acer. It turns out they not only changed the LCD screen as requested, but also changed the housing (whose flakinng paint had damaged the LCD).
I can live with the battery monitor that freezes. It's almost better this way. To do the reset, I have put a launcher button immediately below the panel battery monitor. One gets to see the last reading, then hit reset and look at the present reading.
Bluetooth is entirely useable. If the panel freezes, it is easy to reset with a desktop launcher.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.