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.11.0-0.rc4.git3.1.fc27.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: Manager.py:40:_init:GLib.GError: g-dbus-error-quark: Errore nel chiamare StartServiceByName per 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 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-dbus-error-quark: Errore nel chiamare StartServiceByName per 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 0x7f3f74cec798 (blueman+bluez+Manager+Manager at 0x562b227e8ae0)> __class__: <class 'blueman.bluez.Manager.Manager'>
Created attachment 1269173 [details] File: backtrace
Created attachment 1269174 [details] File: cgroup
Created attachment 1269175 [details] File: environ
Created attachment 1269176 [details] File: mountinfo
Created attachment 1269177 [details] File: namespaces
Created attachment 1269178 [details] File: open_fds
I hit this crash right after the boot of "Fedora-Xfce-Live-x86_64-26-20170420.n.0.iso". This seems a violation of the "2.5.4 SELinux and crash notifications" Final criterion "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop." Xfce is not release blocking, so I'm proposing this as Freeze Exception
For the record: there is a similar report for armvl7, which may be release blocking (https://bugzilla.redhat.com/show_bug.cgi?id=1412282)...
Wolfgang
Wolfgang, please remove blueman from the MATE ISO since blueberry is already a working replacement and present
Will do after beta freeze.
thanks, apologies for the double post^^
Hi Mike, i am still wondering that blueman will installed, because i did this change a while ago , in fedora-comps and fedora-kickstart. https://pagure.io/fedora-kickstarts/c/7dd6ea8fedc840d43d2fd71c7f4e62d6bcb623f1?branch=master https://pagure.io/fedora-comps/c/0e95efcb0a8d484c3e242370ba08f49312d83deb?branch=master Well, sadly we have no alpha release for Mate, but you can download actual spins here. https://kojipkgs.fedoraproject.org/compose/branched/ https://kojipkgs.fedoraproject.org/compose/branched/latest-Fedora-26/compose/Spins/x86_64/iso/ And i did a f26 installation from spin with latest from sunday and there was only blueberry installed.
Ah okay, my F26 nightly ISO is just over a month old, dated 20170408 which was available around the time of alphas going public. I've just done a distro-sync before actually running MATE from run level 3 after install. my F27 MATE ISO from yesterday has blueberry only If it's already been changed for F26 before beta freeze that is great. I'll get a new nightly today and sorry for wasting your time Wolfgang
*** This bug has been marked as a duplicate of bug 1412282 ***