Bug 1618476

Summary: [abrt] blueman: __init__(): Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Błąd podczas wywoływania metody StartServiceByName dla org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out ...
Product: [Fedora] Fedora Reporter: Maciej Kycler <maciej.kycler>
Component: bluemanAssignee: Pete Walter <walter.pete>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: fedora, nushio, walter.pete
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/abd85fff08adc314685584b5df3f01329a142e9f
Whiteboard: abrt_hash:67c7a65099f55e6420993420302a84abc1c03b4b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 19:05:57 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 Maciej Kycler 2018-08-16 18:07:45 UTC
Description of problem:
This error appears every time during first log in after system boot. No idea what is causing this.
This PC is a dekstop PC with Bluetooth USB dongle attached when needed. Normally this dongle is disconnected.

Version-Release number of selected component:
1:blueman-2.1-0.9.alpha2.fc28

Additional info:
reporter:       libreport-2.9.5
cmdline:        python3 /usr/bin/blueman-applet
crash_function: __init__
exception_type: GLib.GError
executable:     /usr/bin/blueman-applet
interpreter:    python3-3.6.5-1.fc28.x86_64
kernel:         4.16.8-300.fc28.x86_64
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Błąd podczas wywoływania metody StartServiceByName dla org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20)

Traceback (most recent call last):
  File "/usr/bin/blueman-applet", line 42, in <module>
    BluemanApplet()
  File "/usr/lib/python3.6/site-packages/blueman/main/Applet.py", line 23, in __init__
    self.Manager = Bluez.Manager()
  File "/usr/lib/python3.6/site-packages/blueman/bluez/Manager.py", line 16, in __call__
    cls._instance = super().__call__(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/blueman/bluez/Manager.py", line 38, in __init__
    self.__bus_name, '/', None, None, None)
GLib.GError: g-dbus-error-quark: Błąd podczas wywoływania metody StartServiceByName dla org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20)

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

Potential duplicate: bug 1554023

Comment 1 Maciej Kycler 2018-08-16 18:07:51 UTC
Created attachment 1476480 [details]
File: backtrace

Comment 2 Maciej Kycler 2018-08-16 18:07:53 UTC
Created attachment 1476481 [details]
File: cgroup

Comment 3 Maciej Kycler 2018-08-16 18:07:54 UTC
Created attachment 1476482 [details]
File: cpuinfo

Comment 4 Maciej Kycler 2018-08-16 18:07:56 UTC
Created attachment 1476483 [details]
File: environ

Comment 5 Maciej Kycler 2018-08-16 18:07:57 UTC
Created attachment 1476484 [details]
File: mountinfo

Comment 6 Maciej Kycler 2018-08-16 18:07:59 UTC
Created attachment 1476485 [details]
File: namespaces

Comment 7 Maciej Kycler 2018-08-16 18:08:00 UTC
Created attachment 1476486 [details]
File: open_fds

Comment 8 Ben Cotton 2019-05-02 21:05:17 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 9 Artur Frenszek-Iwicki 2019-05-08 10:28:24 UTC
Fedora 28 will be EOL soon. Please upgrade to Fedora 29 or Fedora 30.

On the new Fedoras, there's a new version of blueman, 2.1.beta1, currently in testing.
https://bodhi.fedoraproject.org/updates/?packages=blueman
Please check out the testing version, or wait until it reaches stable, and check if the error still occurs.

Comment 10 Ben Cotton 2019-05-28 19:05:57 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.