Bug 1631055 - blueman uses env python, not system python
Summary: blueman uses env python, not system python
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: blueman
Version: 28
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Artur Frenszek-Iwicki
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-19 20:04 UTC by Kale Kundert
Modified: 2019-01-05 03:02 UTC (History)
3 users (show)

Fixed In Version: blueman-2.1-0.14.alpha3.fc29 blueman-2.1-0.11.alpha3.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-05 02:30:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Kale Kundert 2018-09-19 20:04:13 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.11.1 Chrome/65.0.3325.230 Safari/537.36
Build Identifier: 

After `dnf install blueman`, blueman is installed into the system python: `/usr/bin/python3`.  However, the shebang lines in the installed executables read  `#!/usr/bin/env python3`.  If the first python installation on `$PATH` is not `/usr/bin/python3` (e.g. if you've installed your own python), blueman will fail to launch with the following error:

Traceback (most recent call last):
  File "/usr/bin/blueman-manager", line 19, in <module>
    from blueman.main.Manager import Blueman
ModuleNotFoundError: No module named 'blueman'

The solution is to change the shebang lines to `#!/usr/bin/python3`, so that blueman works regardless of the user's $PATH.

Reproducible: Always

Comment 1 Fedora Update System 2018-12-27 20:08:31 UTC
blueman-2.1-0.14.alpha3.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-88674ec2d2

Comment 2 Fedora Update System 2018-12-27 20:08:56 UTC
blueman-2.1-0.11.alpha3.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-442e242808

Comment 3 Fedora Update System 2018-12-28 06:25:14 UTC
blueman-2.1-0.11.alpha3.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-442e242808

Comment 4 Fedora Update System 2018-12-28 08:31:04 UTC
blueman-2.1-0.14.alpha3.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-88674ec2d2

Comment 5 Fedora Update System 2019-01-05 02:30:59 UTC
blueman-2.1-0.14.alpha3.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2019-01-05 03:02:00 UTC
blueman-2.1-0.11.alpha3.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.