Bug 1479336

Summary: [abrt] blueman: _init(): Manager.py:40:_init:GLib.GError: g-io-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. (36)
Product: [Fedora] Fedora Reporter: Peter Gervase <pgervase>
Component: bluemanAssignee: Pete Walter <walter.pete>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: fedora, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ac6281f24efdb3dab3eb863b51113e9e251d20da
Whiteboard: abrt_hash:345f53c6ff7886792881242bd2005a293ec562e6;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 17:57:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: cpuinfo
none
File: environ
none
File: mountinfo
none
File: namespaces
none
File: open_fds none

Description Peter Gervase 2017-08-08 11:43:41 UTC
Description of problem:
I turned on my computer this morning and then had to manually run `startx`. When I got logged in, I got this abrt notice.

Version-Release number of selected component:
blueman-2.1-0.5.alpha1.fc26

Additional info:
reporter:       libreport-2.9.1
cmdline:        python3 /usr/bin/blueman-applet
crash_function: _init
exception_type: GLib.GError
executable:     /usr/bin/blueman-applet
kernel:         4.13.0-0.rc3.git4.1.fc27.x86_64
runlevel:       N 5
type:           Python3
uid:            1001

Truncated backtrace:
Manager.py:40:_init:GLib.GError: g-io-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. (36)

Traceback (most recent call last):
  File "/usr/bin/blueman-applet", line 27, in <module>
    BluemanApplet()
  File "/usr/lib/python3.6/site-packages/blueman/main/Applet.py", line 33, in __init__
    self.Manager = Bluez.Manager()
  File "/usr/lib/python3.6/site-packages/blueman/bluez/Manager.py", line 30, in __new__
    cls._instance._init(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/blueman/bluez/Manager.py", line 40, in _init
    self.__bus_name, '/', None, None, None)
GLib.GError: g-io-error-quark: Error calling StartServiceByName for org.bluez: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found. (36)

Local variables in innermost frame:
self: <Manager.Manager object at 0x7f81057f2798 (blueman+bluez+Manager+Manager at 0x12ec044260)>
__class__: <class 'blueman.bluez.Manager.Manager'>

Comment 1 Peter Gervase 2017-08-08 11:43:46 UTC
Created attachment 1310574 [details]
File: backtrace

Comment 2 Peter Gervase 2017-08-08 11:43:47 UTC
Created attachment 1310575 [details]
File: cgroup

Comment 3 Peter Gervase 2017-08-08 11:43:48 UTC
Created attachment 1310576 [details]
File: cpuinfo

Comment 4 Peter Gervase 2017-08-08 11:43:50 UTC
Created attachment 1310577 [details]
File: environ

Comment 5 Peter Gervase 2017-08-08 11:43:51 UTC
Created attachment 1310578 [details]
File: mountinfo

Comment 6 Peter Gervase 2017-08-08 11:43:52 UTC
Created attachment 1310579 [details]
File: namespaces

Comment 7 Peter Gervase 2017-08-08 11:43:54 UTC
Created attachment 1310580 [details]
File: open_fds

Comment 8 Jan Kurik 2017-08-15 06:15:05 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 9 Peter Gervase 2017-09-29 12:49:08 UTC
This is still an issue with blueman-2.1-0.7.alpha1.fc27.x86_64

Comment 10 Ben Cotton 2018-11-27 18:25:25 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Ben Cotton 2018-11-30 17:57:44 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.