crashes on startup of Ubuntu MATE

[cybermaxpower]

hi,
At login the desktop start's and this message is shown (this is only some times happens)

I don't know why this message is happening? my work around is to click "don't delete" and to reset the MATE panel.

[HaroldV]

I have the same problem, you solvented it ?

[cybermaxpower]

No not yet, got so fedup with it i stopped using it.

[patricktokeeffe]

Did you verify mate-applet-brisk-menu is installed? I upgraded 16.04→18.04 LTS and discovered it wasn't:

lar@dmz:~$ apt-cache search brisk
mate-applet-brisk-menu - Solus Project's Brisk Menu MATE Panel Applet
lar@dmz:~$ apt-cache policy mate-applet-brisk-menu
mate-applet-brisk-menu:
  Installed: (none)
  Candidate: 0.5.0-7ubuntu1
  Version table:
     0.5.0-7ubuntu1 500
        500 http://ports.ubuntu.com bionic/universe armhf Packages

I was encountering this error each time I reset the top panel, but installing the package eliminated it.

[mark-orion]

I am having similar problems. The crashes usually happen after I added custom entries via menulibre. Brisk should be far more tolerant to wrong entries in config files and simply ignore these entries instead of crashing.

[arisboch]

Got the same problem, I normally just delete and re-add the menu.

[dmusican]

I similarly have this same problem. Happens regularly on login.

[dmusican]

I went with post from @mark-orion and repaired or deleted all bad items that menulibre flagged as broken. I tried two relogins and a reboot after that, and no problem with Brisk. Hopefully that took are of it. Thanks. Echoing above comments: it seems as though Brisk has a bug where it is crashing on encountering these bad items.

[Sepero]

I was having this issue on Ubuntu 18.04 and Ubuntu 20.04. The solution for me was:

1. Open Mate Tweak.
2. Go to "Panel" on the left menu.
3. Change panel from "Familiar" to anything else.
4. Change panel back to "Familiar"

Source: https://ubuntu-mate.community/t/brisk-menu-repeated-problems-and-has-completely-disappeared-now/17355/4

[denizgezmis]

It is most likely due to a library conflict. Right after that crash message, if you open up a terminal program and run the command:
dmesg
you would see messages like :
.. brisk-menu[31551]: segfault at 1 ip 00007f1581c6f412 sp 00007ffec5c50d30 error 4 in libgio-2.0

If so, it is clearly a library conflict. i.e., the library installed on your system and brisk-menu requires are not compatible. Unfortunately, nothing much you could do other than expect the bug fixed in the new release.