Bug 1532474 - [abrt] blueman: __init__(): Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Fehler beim Aufruf von StartServiceByName für org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out ...
Summary: [abrt] blueman: __init__(): Manager.py:38:__init__:GLib.GError: g-dbus-error-...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: blueman
Version: 27
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:20e092e5c0c7792b3a9d4eb6929...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-09 03:22 UTC by Marco Nolden
Modified: 2018-11-30 21:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 21:06:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.15 KB, text/plain)
2018-01-09 03:22 UTC, Marco Nolden
no flags Details
File: cgroup (289 bytes, text/plain)
2018-01-09 03:22 UTC, Marco Nolden
no flags Details
File: cpuinfo (1.36 KB, text/plain)
2018-01-09 03:22 UTC, Marco Nolden
no flags Details
File: environ (1.60 KB, text/plain)
2018-01-09 03:22 UTC, Marco Nolden
no flags Details
File: mountinfo (4.13 KB, text/plain)
2018-01-09 03:23 UTC, Marco Nolden
no flags Details
File: namespaces (129 bytes, text/plain)
2018-01-09 03:23 UTC, Marco Nolden
no flags Details
File: open_fds (866 bytes, text/plain)
2018-01-09 03:23 UTC, Marco Nolden
no flags Details

Description Marco Nolden 2018-01-09 03:22:47 UTC
Version-Release number of selected component:
blueman-2.1-0.8.alpha2.fc27

Additional info:
reporter:       libreport-2.9.3
cmdline:        python3 /usr/bin/blueman-applet
crash_function: __init__
exception_type: GLib.GError
executable:     /usr/bin/blueman-applet
kernel:         4.14.11-300.fc27.x86_64
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Fehler beim Aufruf von StartServiceByName für 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: Fehler beim Aufruf von StartServiceByName für 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 0x7ff1c0038798 (blueman+bluez+Manager+Manager at 0x55ce5bca97a0)>
__class__: <class 'blueman.bluez.Manager.Manager'>

Comment 1 Marco Nolden 2018-01-09 03:22:54 UTC
Created attachment 1378858 [details]
File: backtrace

Comment 2 Marco Nolden 2018-01-09 03:22:55 UTC
Created attachment 1378859 [details]
File: cgroup

Comment 3 Marco Nolden 2018-01-09 03:22:57 UTC
Created attachment 1378860 [details]
File: cpuinfo

Comment 4 Marco Nolden 2018-01-09 03:22:58 UTC
Created attachment 1378861 [details]
File: environ

Comment 5 Marco Nolden 2018-01-09 03:23:00 UTC
Created attachment 1378862 [details]
File: mountinfo

Comment 6 Marco Nolden 2018-01-09 03:23:01 UTC
Created attachment 1378863 [details]
File: namespaces

Comment 7 Marco Nolden 2018-01-09 03:23:02 UTC
Created attachment 1378864 [details]
File: open_fds

Comment 8 Raphael Groner 2018-01-10 13:55:04 UTC
Similar problem has been detected:

nearly after every login to plasma

reporter:       libreport-2.9.3
cmdline:        python3 /usr/bin/blueman-applet
crash_function: __init__
exception_type: GLib.GError
executable:     /usr/bin/blueman-applet
kernel:         4.14.11-300.fc27.x86_64
package:        blueman-2.1-0.8.alpha2.fc27
reason:         Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Fehler beim Aufruf von StartServiceByName für org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20)
runlevel:       N 5
type:           Python3
uid:            1000

Comment 9 Raphael Groner 2018-01-10 13:58:31 UTC
Reporter, what did you do, esp. with the DBus service to break?

Comment 10 Marco Nolden 2018-01-12 10:02:26 UTC
Similar problem has been detected:

Just happens after login to GNOME

reporter:       libreport-2.9.3
cmdline:        python3 /usr/bin/blueman-applet
crash_function: __init__
exception_type: GLib.GError
executable:     /usr/bin/blueman-applet
kernel:         4.14.11-300.fc27.x86_64
package:        blueman-2.1-0.8.alpha2.fc27
reason:         Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Fehler beim Aufruf von StartServiceByName für org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20)
runlevel:       N 5
type:           Python3
uid:            1000

Comment 11 Marco Nolden 2018-01-12 10:04:18 UTC
(In reply to Raphael Groner from comment #9)
> Reporter, what did you do, esp. with the DBus service to break?

Didn't do anything special, it just happens after login to GNOME shell

Comment 12 Marco Nolden 2018-01-13 09:58:15 UTC
Similar problem has been detected:

Login to gnome-shell

reporter:       libreport-2.9.3
cmdline:        python3 /usr/bin/blueman-applet
crash_function: __init__
exception_type: GLib.GError
executable:     /usr/bin/blueman-applet
kernel:         4.14.11-300.fc27.x86_64
package:        blueman-2.1-0.8.alpha2.fc27
reason:         Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Fehler beim Aufruf von StartServiceByName für org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20)
runlevel:       N 5
type:           Python3
uid:            1000

Comment 13 Andre Vehreschild 2018-04-18 07:13:49 UTC
Similar problem has been detected:

Systemstart with no bt-device.

reporter:       libreport-2.9.3
cmdline:        python3 /usr/bin/blueman-applet
crash_function: __init__
exception_type: GLib.GError
executable:     /usr/bin/blueman-applet
kernel:         4.15.16-300.fc27.x86_64
package:        1:blueman-2.1-0.8.alpha2.fc27
reason:         Manager.py:38:__init__:GLib.GError: g-dbus-error-quark: Fehler beim Aufruf von StartServiceByName für org.bluez: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) (20)
runlevel:       N 5
type:           Python3
uid:            1000

Comment 14 Ben Cotton 2018-11-27 16:07:21 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 15 Ben Cotton 2018-11-30 21:06:27 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.


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