{"action":"closed","issue":{"url":"https://api.github.com/repos/blueman-project/blueman/issues/417","labels_url":"https://api.github.com/repos/blueman-project/blueman/issues/417/labels{/name}","comments_url":"https://api.github.com/repos/blueman-project/blueman/issues/417/comments","events_url":"https://api.github.com/repos/blueman-project/blueman/issues/417/events","html_url":"https://github.com/blueman-project/blueman/issues/417","id":122962962,"number":417,"title":"blueman-applet startup failure","user":{"login":"spinosae","id":9039605,"avatar_url":"https://avatars.githubusercontent.com/u/9039605?v=3","gravatar_id":"","url":"https://api.github.com/users/spinosae","html_url":"https://github.com/spinosae","followers_url":"https://api.github.com/users/spinosae/followers","following_url":"https://api.github.com/users/spinosae/following{/other_user}","gists_url":"https://api.github.com/users/spinosae/gists{/gist_id}","starred_url":"https://api.github.com/users/spinosae/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/spinosae/subscriptions","organizations_url":"https://api.github.com/users/spinosae/orgs","repos_url":"https://api.github.com/users/spinosae/repos","events_url":"https://api.github.com/users/spinosae/events{/privacy}","received_events_url":"https://api.github.com/users/spinosae/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/blueman-project/blueman/labels/needinfo","name":"needinfo","color":"009800"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-12-18T14:58:30Z","updated_at":"2015-12-21T11:51:04Z","closed_at":"2015-12-21T11:51:04Z","body":"I have been having problem with blueman since a while ago (possibly since 27th Nov). My system:\r\n```bash\r\n$uname -a\r\nLinux fedora 4.2.7-300.fc23.x86_64 #1 SMP Wed Dec 9 22:28:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux\r\n$ dnf list installed | grep blue\r\nNetworkManager-bluetooth.x86_64       1:1.0.6-8.fc23            @updates        \r\nblueman.x86_64                        2.1-0.3.git7a2e20e.fc23   @fedora         \r\nbluez.x86_64                          5.36-1.fc23               @System         \r\nbluez-cups.x86_64                     5.36-1.fc23               @System         \r\nbluez-hid2hci.x86_64                  5.36-1.fc23               @System         \r\nbluez-libs.x86_64                     5.36-1.fc23               @System         \r\nbluez-libs-devel.x86_64               5.36-1.fc23               @System         \r\ngnome-bluetooth.x86_64                1:3.18.1-1.fc23           @updates        \r\ngnome-bluetooth-libs.x86_64           1:3.18.1-1.fc23           @updates        \r\ngnome-bluetooth-libs-devel.x86_64     1:3.18.1-1.fc23           @updates        \r\npulseaudio-module-bluetooth.x86_64    7.1-1.fc23                @updates  \r\n```\r\nSymptom: After system boot, bluetooth-applet appeared to be loaded (listed in processes) but no icon showed up in the system tray. If I start bluetooth-manager right away, it would took much longer to load the GUI and the manager wouldn't function properly. However if I kill bluetooth-applet (pkill) first, then applet and manager can start and work properly (icon will show up in tray). Here is the boot log:\r\n```bash\r\n$ journalctl --boot=-7 | grep blueman\r\nDec 18 19:31:47 fedora dbus[983]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)\r\nDec 18 19:31:47 fedora org.blueman.Mechanism[983]: Unable to init server: Could not connect: Connection refused\r\nDec 18 19:31:47 fedora org.blueman.Mechanism[983]: Unable to init server: Could not connect: Connection refused\r\nDec 18 19:31:47 fedora blueman-mechanism[3775]: Starting blueman-mechanism\r\nDec 18 19:31:47 fedora dbus[983]: [system] Successfully activated service 'org.blueman.Mechanism'\r\nDec 18 19:31:47 fedora org.blueman.Mechanism[983]: (blueman-mechanism:3775): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed\r\nDec 18 19:31:47 fedora blueman-mechanism[3775]: loading RfKill\r\nDec 18 19:31:47 fedora blueman-mechanism[3775]: loading Ppp\r\nDec 18 19:31:47 fedora blueman-mechanism[3775]: loading Network\r\nDec 18 19:31:47 fedora blueman-mechanism[3775]: loading Rfcomm\r\nDec 18 19:31:47 fedora blueman.desktop[3340]: (blueman-applet:3340): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed\r\nDec 18 19:31:50 fedora blueman.desktop[4876]: blueman-applet version 2.0 starting\r\nDec 18 19:31:50 fedora blueman.desktop[4876]: There is an instance already running\r\nDec 18 19:32:17 fedora blueman-mechanism[3775]: Exiting\r\n```\r\nThe suspicious line is ``Dec 18 19:31:50 fedora blueman.desktop[4876]: There is an instance already running``. It seemed that an instance of blueman-applet was runing before /etc/xdg/autostart/blueman.desktop was loaded. This line wasn't in the log before Nov 27. I can't figure out what changed at that point of time. Now my workaround was to kill blueman-applet first and start again in the .desktop file. However I wonder whether something broke in blueman. Could you look into it? Tell me if you need more log."}}