Interesting, so this is just me then. Thanks for reporting your findings.
I am getting this on a full fresh installation, and it is reproducible.
I start with anarsoul's archlinux image for the Pinebook 1080 (not ayufan's as mentioned above):
https://github.com/anarsoul/linux-bu...s/tag/20190112
Out of all of the Pinebook images I have tried, this one gives the best kernel with all features working (specifically adjustable screen brightness), and I have tried all that I can find, including building my own, which has not gone well yet (another thread for another day).
I boot this up and run a full update, just to get any fresh kernel, modules, or firmware.
Then I strip out everything except /boot, /usr/lib/modules, and /usr/lib/firmware. I then move /usr/lib/firmware to /lib/firmware and /usr/lib/modules to /lib/modules. Then I extract the latest rootfs for Slarm64 into the root directory.
When I boot off of that SD card, I get a working slacwkare prompt, as expected. Then I hook it up to a USB-Ethernet dongle, set my mirror, type:
Code:
slackpkg update && slackpkg install a ap d e f k kde l n t tcl x xap xfce y
and then I walk away and do something else for a while. Eventually I have to restart the process, when slackpkg gets updated. After that, the process continues smoothly. In the process, blueman, python3, and pycairo all definitely get installed, I double-checked after you suggested it.
Eventually, I can log into Xfce with a new non-root user and everything works fine. In the past, I have had to adjust the permissions on a few directories for things to work right, such as Firefox, but those things were relatively simple to figure out.
Even on a fresh install though, as just described, I get this output, in contrast to yours:
Code:
bash-5.0$ blueman-manager
blueman-manager version 2.1.1 starting
Stale PID, overwriting
(blueman-manager:4206): Gtk-CRITICAL **: 09:15:15.386: gtk_image_menu_item_set_use_stock: assertion 'GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed
(blueman-manager:4206): Gtk-CRITICAL **: 09:15:15.386: gtk_image_menu_item_set_always_show_image: assertion 'GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed
/usr/lib64/python3.8/site-packages/gi/overrides/__init__.py:319: Warning: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed
return super_init_func(self, **new_kwargs)
(blueman-manager:4206): Gtk-CRITICAL **: 09:15:15.388: gtk_menu_item_set_label: assertion 'GTK_IS_MENU_ITEM (menu_item)' failed
(blueman-manager:4206): Gtk-CRITICAL **: 09:15:15.388: gtk_image_menu_item_set_image: assertion 'GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed
(blueman-manager:4206): Gtk-CRITICAL **: 09:15:15.388: gtk_menu_item_set_use_underline: assertion 'GTK_IS_MENU_ITEM (menu_item)' failed
/usr/lib64/python3.8/site-packages/gi/overrides/__init__.py:319: Warning: g_object_notify_queue_thaw: assertion 'g_atomic_int_get(&object->ref_count) > 0' failed
return super_init_func(self, **new_kwargs)
/usr/lib64/python3.8/site-packages/gi/overrides/__init__.py:319: Warning: g_object_is_floating: assertion 'G_IS_OBJECT (object)' failed
return super_init_func(self, **new_kwargs)
**
ERROR:../gi/pygobject-object.c:722:pygobject_register_wrapper: assertion failed: (gself->obj->ref_count >= 1)
Bail out! ERROR:../gi/pygobject-object.c:722:pygobject_register_wrapper: assertion failed: (gself->obj->ref_count >= 1)
Aborted
bash-5.0$
So, if this is only happening on my machine, and only lately (this used to work fine a few months ago, I can clearly recall, this started in late November approximately), then I am starting to wonder about the hardware and/or kernel+modules+firmware.
The above process will produce these results every time for me. Next I will try a few different starting images, just to see if I can get a different result launching blueman-manager, even if the screen brightness does not work, etc.
Otherwise, this installation works pretty well, I cannot report anything else that seems to be broken, just blueman-manager and blueman-applet.
When I have more time, I will try out different starting images and kernels, etc. I guess this is my own little project. Thanks for helping me isolate the issue a bit further.