@nuiin I doubt that this problem is related to the operating system. I'm using the windows version and noticed this issue today after updating.
When you click on the edit button, an error appears in the console, as you mentioned
startpage.js:2 Uncaught (in promise) TypeError: Error in invocation of contextMenusPrivate.showMenu(integer x, integer y, array items, function callback): Error at parameter 'items': Error at index 3: Invalid type: expected contextMenusPrivate.ContextMenuItem, found undefined.
at e.show (startpage.js:2:375912)
at d (startpage.js:2:517799)
e.show @ startpage.js:2
d @ startpage.js:2
await in d (async)
Pe @ startpage.js:2
Ue @ startpage.js:2
(anonymous) @ startpage.js:2
zr @ startpage.js:2
Rr @ startpage.js:2
(anonymous) @ startpage.js:2
lc @ startpage.js:2
Ne @ startpage.js:2
Zr @ startpage.js:2
Qt @ startpage.js:2
Yt @ startpage.js:2
The error message indicates that there is a problem with the contextMenusPrivate.showMenu function call. In the 'e.show()' function, it is calling 'chrome.contextMenusPrivate.showMenu()' with parameters 'r', 'a', 'o.items', and 'o.handler'. The error message indicates that the 'items' parameter (which is 'o.items' in this case) is expected to be of type 'contextMenusPrivate.ContextMenuItem', but it's receiving 'undefined' instead.
The 'o.items' in the 'show' function could be malformed or have missing properties that cause the 'chrome.contextMenusPrivate.showMenu' function to throw an error. This also could be caused by the 'n(e)' function not returning the expected object with the 'items' property, or the 'items' property not being set correctly in the first place. Or there might be an issue with the 'await' keyword being used in the 'd' function, causing a timing issue or a problem with resolving promises.
Actually, I thought this was a recent problem, but now I see that it is already more than a month old.