LinuxQuestions.org - [SOLVED] Slarm64 / Xfce / Blueman / PyGObject

- Slackware - ARM (https://www.linuxquestions.org/questions/slackware-arm-108/)

- - Slarm64 / Xfce / Blueman / PyGObject - GUI seems broken? (https://www.linuxquestions.org/questions/slackware-arm-108/slarm64-xfce-blueman-pygobject-gui-seems-broken-4175667406/)

Slarm64 / Xfce / Blueman / PyGObject - GUI seems broken?

Is anyone else running into this? I have not been able to launch Blueman in quite some time, using Slarm64 + Xfce on a Pinebook (using ayufan's kernel from his Arch image, in which Blueman works fine). I checked this in a fresh installation to rule out custom configurations, and it still happens straight out of the box.

Blueman used to work as expected, but has been failing for untold weeks (months?), and the error message changes a bit depending on the circumstances. Usually, I get this:

Code:

(blueman-manager:6337): Gtk-CRITICAL **: 17:45:19.954: gtk_image_menu_item_set_use_stock: assertion 'GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed



(blueman-manager:6337): Gtk-CRITICAL **: 17:45:19.955: 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:6337): Gtk-CRITICAL **: 17:45:19.960: gtk_menu_item_set_label: assertion 'GTK_IS_MENU_ITEM (menu_item)' failed



(blueman-manager:6337): Gtk-CRITICAL **: 17:45:19.960: gtk_image_menu_item_set_image: assertion 'GTK_IS_IMAGE_MENU_ITEM (image_menu_item)' failed



(blueman-manager:6337): Gtk-CRITICAL **: 17:45:19.960: 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

I find that blueman-assistant still works. The actual bluetooth driver still seems to work fine. All of this prompted me to learn how to use bluetoothctl from the cli, and I have started to like that better anyway. So, I have not lost bluetooth functionality, there just seems to be a GUI issue with Blueman that I have been battling for a while now. Any insights? None of this is urgent, I just get curious about such things.

Thanks.

interesting to know how blueman-manager behaves in slackware64 and slackwarearm

Quote:

Originally Posted by sndwvs (Post 6076763)

interesting to know how blueman-manager behaves in slackware64 and slackwarearm

Ah, good point. I know for sure that blueman-manager works as expected in standard Slackware64-current as well as Slackware64 14.2. No problems there at all, I just tested both.

I do not have a slackwarearm machine at the moment, although I might in a few months. If I get time, I might create a qemu image for slackwarearm to test in.

Hi,

blueman-applet is working here. Make sure all dependencies are installed, ie, blueman, python3 and pycairo.

Edit- added cmd line output

Code:

$ blueman-manager 



(blueman-manager:2314): dbind-WARNING **: 13:44:04.989: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

blueman-manager version 2.1.1 starting

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.

Quote:

Originally Posted by shelldweller (Post 6079579)

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):

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$

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.

Searching for g_atomic_int_get, it seems to be dependent on architecture. Is the original image for multilib / armhf perhaps (as opposed to arm64)?

Appreciate your detailed installation report.

if a precompiled application is used, then rather it uses /lib/ld-linux-aarch64.so.1
just make symlink ln -s /lib64/ld-linux-aarch64.so.1 /lib/ld-linux-aarch64.so.1
or patchelf --set-interpreter /lib64/ld-linux-aarch64.so.1 <PROGRAM>

Quote:

Originally Posted by sndwvs (Post 6079616)

Hrm...thanks for the suggestion. I made the symbolic link from /lib64 to /lib as suggested, but it did not change the issue or the output in any noticeable way.

I also tried the patchelf suggestion, and I get this error:

Code:

bash-5.0# patchelf --set-interpreter /lib64/ld-linux-aarch64.so.1 /usr/bin/blueman-manager

patchelf: not an ELF executable

Searching around finds similar problems, although nothing conclusive....

https://gitlab.gnome.org/GNOME/pygobject/issues/377

I think I am just going to move on from this one unless anyone has an obvious fix, I have bigger fish to fry now that the semester is in full swing (I teach).

Thanks for the input, I really appreciate it.

I almost missed this one....

Quote:

Originally Posted by aaditya (Post 6079610)

Searching for g_atomic_int_get, it seems to be dependent on architecture. Is the original image for multilib / armhf perhaps (as opposed to arm64)?

The original image is specifically for the Pinebook 1080, so arm64 specifically. The same applicaiton launches without error in the original image, which is part of my confusion.

Updates fixed the problem

Both blueman and gtk+3 were recently updated/rebuilt within the past week or so. Now this bug is gone; blueman-manager now launches without complaint. Marking thread as solved, thanks for the inputs.