blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8e in position 4: invalid start byte

Bug #1860851 reported by Paul Ortyl
144
This bug affects 29 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Confirmed
Medium
Joshua Peisach

Bug Description

crashed without direct interaction

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: blueman 2.1.1-1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 21:28:44 2020
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/blueman-applet
InstallationDate: Installed on 2016-02-25 (1429 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
InterpreterPath: /usr/bin/python3.7
ProcCmdline: /usr/bin/python3 /usr/bin/blueman-applet
Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1
PythonArgs: ['/usr/bin/blueman-applet']
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
SourcePackage: blueman
Title: blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8e in position 4: invalid start byte
Traceback: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8e in position 4: invalid start byte
UpgradeStatus: Upgraded to focal on 2020-01-22 (2 days ago)
UserGroups:

Revision history for this message
Paul Ortyl (ortylp) wrote :
tags: removed: need-duplicate-check
Changed in blueman (Ubuntu):
importance: Undecided → Medium
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in blueman (Ubuntu):
status: New → Confirmed
Revision history for this message
Dan Halbert (dhalbert) wrote :

Error appeared during latest set of package updates.

Revision history for this message
Derk Willem te Bokkel (dtebokkel) wrote :

after update .. not rebooted

Revision history for this message
Joshua Peisach (itzswirlz) wrote :

I keep having this issue. I'll try to make a debdiff and see what I can do.

Changed in blueman (Ubuntu):
assignee: nobody → Joshua Peisach (itzswirlz)
Revision history for this message
Joshua Peisach (itzswirlz) wrote :

Actually, it seems like this is fine now, maybe in version 2.1.2. I don't see any issues now...

A lot has been updated since Ubuntu Cinnamon (which is what I'm testing on) Beta ISO has been released and a rebuild will begin on Wednesday at 7 PM EDT. Then I can see where we are. So lets hold it for now.

Revision history for this message
Owen (osavill-z) wrote :

Just happened to me. Running 20.04 with blueman 2.1.2-1

Revision history for this message
H I Murphy (him610) wrote :

I had left the system up and running with Chrome browser open for a couple of hours. When I came back the notice of failure was one the screen.
blueman/focal,now 2.1.2-1 amd64 [installed,automatic]

Revision history for this message
Ricardo (ricardoviapiana) wrote :

Same here with 2.1.2-1 amd64 at UbuntuStudio 20.04 beta. Updated with proposed packages few minutes ago, but not rebooted because it is a live usb.

Revision history for this message
Joshua Peisach (itzswirlz) wrote :

I still can't find it, but I think it's safe to say that it's time to contact the maintainer about the issue-continuously, this is clearly a problem.

Revision history for this message
Joshua Peisach (itzswirlz) wrote :

I contacted the maintainer, awaiting response. I built an Ubuntu Cinnamon-Remix ISO just now with the fixed update-manager patch and the bug crash report doesn't appear. Make sure you upgrade your blueman, and then see if it persists through different products.

Revision history for this message
Derk Willem te Bokkel (dtebokkel) wrote :

this crash happened to me on a fresh install of focal while doing the first software update.

Blueman-applet was running in the panel and apparently is running again after the crash ..

Norbert (nrbrtx)
tags: removed: wayland-session
Revision history for this message
Joshua Peisach (itzswirlz) wrote :

I just tested and played with my Ubuntu Cinnamon Remix for Apr 16 (Final Freeze), and I see no issues with blueman at all. I suggest a close

Revision history for this message
Renato Athaydes (renatoathaydes) wrote :

This just happened to me. I just upgraded a couple of days ago to Ubuntu 20.04

Revision history for this message
Jamie Simpson (booyaamps) wrote :

Confirmed here as well. Just did a fresh re-install of ubuntu studio 20.04, this is happening out of the box. This is with Sengled bluetooh speaker/LED lights. I should note, audio connects and works with no issues. This happens when trying to bind to the bulb's serial port (to contol dimming). Worked fine on 19.10.

Revision history for this message
Bill (franksmcb) (franksmcb) wrote :

Running Ubuntu MATE 20.10 I had the blueman-applet crash. First time having the crash in 20.10

Revision history for this message
Joshua Peisach (itzswirlz) wrote :

Safe to say its time to backport a patch from upstream if it exists

Revision history for this message
Joshua Peisach (itzswirlz) wrote :

wait-this issue still occurs and yet we still use python2 here?

Checking https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942916, in version 2.1.3-2 they switch to cython3.

Three releases occured since 20.04 release. And in JournalErrors, too, systemd has had issues, which was also patched in latest versions of blueman.

Updates are relatively sparce sadly-but it's worth SRUing all the patches we did to 20.04 to quickly fix this thanks to Eoan support ending.

Revision history for this message
Fernando Racca (fracca) wrote :

Reproduced on Ubuntu 20.04 when using my Sony WH-1000XM3 headsets

Revision history for this message
Claudio Patrone (cpatrone-t) wrote :

Reproduced on Ubuntu 20.04. The error message appears starting or stopping the bluetooth service ("sudo systemctl start bluetooth.service" or ""sudo systemctl stop bluetooth.service"").

Revision history for this message
Joel Franco (joel-franco) wrote :

same here. Thanks

Revision history for this message
Bill (franksmcb) (franksmcb) wrote :

This is occurring 21.04 after upgrades on 10 Nov. 2020

Revision history for this message
Marty (allmarty) wrote :

For me it occurs on 20.10 with updates from a few days ago while pairing my Thinkpad Bluetooth Laser Mouse. Other devices are working fine.

Revision history for this message
Robert Hardy (rhardy) wrote :

This error was annoying. Something triggered it and the logs were not clear on what.
I'm was file corruption somewhere. I had some old files in /home/myusername/.cache/blueman*
I removed those and logged out and in. No more crash but it may not last.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Just happened to me in jammy when changing some sound configuration via "Pulseaudio volume control" while listening to music via bluetooth headphones. After the crash, the bluetooth connection had broken and audio came out of the internal speaker instead.

tags: added: jammy
Revision history for this message
Michael De La Rue (mikedlr) wrote (last edit ):

I just had the same happen to me in 23.04 / Lunar Lobster. Also sent in a crash report I hope. No idea when or if anything iin particular was happening; just got the crash report pop up after having to force a reboot.

tags: added: lunar
Revision history for this message
Quigi (brechbuehler) wrote :

Just happened in 22.04, when using bluetooth for EasyTether.

Running Ubuntu 22.04.2 LTS.
Traceback:
   UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfe in position 1: invalid start byte

Architecture, according to bug report (presumably Apport 2.20.11-0ubuntu82.5): amd64.
But the processor is intel vPRO i7, and "uname -m" reports x86_64.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.