[Unstable][Mate 1.22][Brisk Menu] Brisk Menu is busted

Hello.

I noticed Archlinux moved to Mate 1.22.

https://lists.archlinux.org/pipermail/arch-commits/2019-March/591469.html

Brisk menu need some tweaking to be both build and working under Mate 1.22.

See this bug report: https://gitlab.manjaro.org/packages/community/mate/brisk-menu/issues/1

Without this patch, a lot of things will be broken :frowning:

2 Likes

Since arch late to release mate 1.22 yesterday i push all mate 1.22 to release 0.1 so brisk is already patched… Funny to see today arch release it :grinning:

And it crashes on start…

Even if it is in french, it is clear there is a problem...

Got an error log:

Error log.
mars 30 09:21:16 fredo-manja-mate brisk-menu[3606]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 09:21:16 fredo-manja-mate brisk-menu[3606]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 09:21:16 fredo-manja-mate brisk-menu[3606]: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkToggleButton)
mars 30 09:21:16 fredo-manja-mate brisk-menu[3606]: Negative content height -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkToggleButton)
mars 30 09:21:16 fredo-manja-mate dbus-daemon[2924]: [session uid=1000 pid=2924] Activating service name='org.mate.ScreenSaver' requested by ':1.68' (uid=1000 pid=3606 comm="/usr/libexec/brisk-menu ")
mars 30 09:21:19 fredo-manja-mate brisk-menu[3606]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 09:21:19 fredo-manja-mate brisk-menu[3606]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 09:21:19 fredo-manja-mate brisk-menu[3606]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 09:21:19 fredo-manja-mate brisk-menu[3606]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 09:21:19 fredo-manja-mate brisk-menu[3606]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 09:21:19 fredo-manja-mate brisk-menu[3606]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 09:21:19 fredo-manja-mate brisk-menu[3606]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 09:21:19 fredo-manja-mate brisk-menu[3606]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 09:21:19 fredo-manja-mate brisk-menu[3606]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 09:21:19 fredo-manja-mate audit[3606]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=6 pid=3606 comm="brisk-menu" exe="/usr/libexec/brisk-menu" sig=11 res=1
mars 30 09:21:19 fredo-manja-mate kernel: brisk-menu[3606]: segfault at 3 ip 00007f1ec75711fd sp 00007fff0b6c29a8 error 4 in libgobject-2.0.so.0.6000.0[7f1ec756b000+34000]
mars 30 09:21:19 fredo-manja-mate kernel: audit: type=1701 audit(1553934079.129:97): auid=1000 uid=1000 gid=1000 ses=6 pid=3606 comm="brisk-menu" exe="/usr/libexec/brisk-menu" sig=11 res=1
mars 30 09:21:20 fredo-manja-mate systemd-coredump[3864]: Process 3606 (brisk-menu) of user 1000 dumped core.
                                                          #3  0x000055fe0a057b6f n/a (brisk-menu)
                                                          #7  0x000055fe0a052858 n/a (brisk-menu)
                                                          #11 0x000055fe0a05dcc9 n/a (brisk-menu)
                                                          #12 0x000055fe0a05e067 n/a (brisk-menu)
                                                          #19 0x000055fe0a05016b n/a (brisk-menu)
                                                          #21 0x000055fe0a0501be n/a (brisk-menu)

Kinda related bug report: https://github.com/solus-project/brisk-menu/issues/115

Good cacth…

Looks like Mate-desktop 1.22 with brisk menu enabled will stay on unstable for some time… Weird bug to say the least :frowning:

Simply remove brisk-menu. I’ll push the batch later to testing when I’m finished with adding kde-unstable to our repos for BlueSystems.

Well, I’ll try to do my best to get a fix for brisk. At least, I got a debug log I’ll add to bug report.

debug log
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: g_set_application_name() called multiple times
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: g_set_application_name() called multiple times
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkToggleButton)
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkToggleButton)
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: Negative content height -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkToggleButton)
mars 30 11:49:41 fredo-arch-mate brisk-menu[4616]: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkToggleButton)
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:11 fredo-arch-mate brisk-menu[4616]: gtk_icon_theme_lookup_by_gicon_for_scale: assertion 'G_IS_ICON (icon)' failed
mars 30 11:50:49 fredo-arch-mate brisk-menu[5034]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:50:49 fredo-arch-mate brisk-menu[5034]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:50:49 fredo-arch-mate brisk-menu[5034]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:50:49 fredo-arch-mate brisk-menu[5034]: gdk_window_get_origin: assertion 'GDK_IS_WINDOW (window)' failed
mars 30 11:50:49 fredo-arch-mate brisk-menu[5034]: g_set_application_name() called multiple times
mars 30 11:50:49 fredo-arch-mate brisk-menu[5034]: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkToggleButton)
mars 30 11:50:49 fredo-arch-mate brisk-menu[5034]: Negative content width -11 (allocation 1, extents 6x6) while allocating gadget (node button, owner GtkToggleButton)
mars 30 11:50:49 fredo-arch-mate brisk-menu[5034]: Negative content height -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkToggleButton)
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate kernel: brisk-menu[5034]: segfault at 3 ip 00007f83e8b2d1fd sp 00007ffc89b31b88 error 4 in libgobject-2.0.so.0.6000.0[7f83e8b27000+34000]
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate brisk-menu[5034]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 30 11:50:54 fredo-arch-mate systemd-coredump[5085]: Process 5034 (brisk-menu) of user 1000 dumped core.
                                                         #3  0x0000558b5a02784f brisk_classic_category_button_constructed (brisk-menu)
                                                         #7  0x0000558b5a022778 brisk_classic_window_add_section (brisk-menu)
                                                         #11 0x0000558b5a02d9c9 brisk_apps_backend_init_menus (brisk-menu)
                                                         #12 0x0000558b5a02dd67 brisk_apps_backend_reload (brisk-menu)
                                                         #19 0x0000558b5a020147 main (brisk-menu)
                                                         #21 0x0000558b5a02019e _start (brisk-menu)
-- Subject: Le processus 5034 (brisk-menu) a généré un fichier « core »
-- Le processus 5034 (brisk-menu) a planté et généré un fichier « core ».

I only hope Mate 1.22 won’t be pushed to stable until brisk is working for good… It will give a bad experience to Mate users if so. But it is your choice after all.

Our focus is not on Mate. I removed Brisk from our repos for now. When we have time we might readd it.

1 Like

Ok. I understand, but it will break a lot of people installation. I hope debug log I added will help fixing these crashes.

If you want another “user-friendly menu” you’ll have to upgrade mate-menu to its version 19.04 to replace brisk menu.

I think we can’t reasonably continue to install Manjaro for Noobs. It’s a very good distro but more and more unstable by choice.

Nice day…

This bug is out of our control… If Solus dev don t take a look into it we have to look forward… I don t know if mate team also join into the party… I think after the go out of Ikey all apps bring from Solus need more attention… No idea if really Solus OS can still be considered a Rolling distro… I look into mate and Budgie when have time but my focus is for gnome…

Yes sure, but can you wait a patch if we make a little pressure to patch the brisk ?

F Bezies tries too: https://github.com/solus-project/brisk-menu/issues/115

I think both teams are aware of this bug. It is annoying for all users, to the point that Ubuntu Mate say they’ll stay with Mate 1.20 for their 19.04 release: https://ubuntu-mate.org/blog/ubuntu-mate-disco-beta/

You may be wondering why we’re not shipping MATE Desktop 1.22? The answer, stability. MATE Desktop 1.22 introduces some underlying API changes in core components and while all first party MATE Desktop applications are compatible with the changes and completely stable, some third party applications are not. Some third party applications are big crashers now and we’ve not been able to fix them in time.

So, we are playing it safe and sticking with MATE Desktop 1.20 and working with upstreams so we can land MATE Desktop 1.22 early in the Ubuntu MATE 19.10 development cycle.

Looks like brisk menu stinks like rotten meat :frowning:

Wascar our dev in TnV searching for patching the brisk and report it to the team

Good luck. He’ll need it!

Sure if a patch solve the problem we can reconsider :wink:

1 Like

just let us try and wait please

If we got a working patch - I know both @Elrondo46 and Wascar - I’ll test it with pleasure. And report it!

You’ve been saying this for the past two years, and yet you’re still here. :kissing_heart: