blueman-manager crashed with blueman.bluez.errors.DBusNotReadyError in callback(): Resource Not Ready
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
blueman (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
Адаптер Bluetooth в режиме запрета сопряжения,не возможно разблокировать.
ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: blueman 2.1.4-1
ProcVersionSign
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: KDE
Date: Thu Mar 11 15:29:59 2021
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2021-03-11 (0 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210211)
InterpreterPath: /usr/bin/python3.9
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=ru_RU.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1
PythonArgs: ['/usr/
PythonDetails: N/A
SourcePackage: blueman
Title: blueman-manager crashed with blueman.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
tags: | removed: need-duplicate-check |
Changed in blueman (Ubuntu): | |
importance: | Undecided → Medium |
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 privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.