This solution seems to be a workaround, but it doesn't solve the actual problem. Basically, the logic of this granite component consist in adapting resource resolver to session, getting access control manager from session, and then check if the user has privileges for certain paths. Also, I debugged the jsp (/libs/granite/ui/components/foundation/renderconditions/privilege/privilege.jsp/jcr:content) and it constantly has necessary privileges, but the UI is wrong at dropdown menu.
Then you can adapt /libs/wcm/core/content/editor/jcr:content/content/items/content/header/items/headerbar/it ems/pageinfopopover/items/list/items/requestpublish like libs/wcm/core/content/editor/jcr:content/content/items/content/header/items/headerbar/it ems/pageinfopopover/items/list/items/publish
you can overlay and changed the property of requestpublish node if you don't want to use.
If you worried about only a title, you overlay and change the title(granite:title) of node to "Publish Page" /libs/wcm/core/content/editor/jcr:content/content/items/content/header/items/headerbar/items/pageinfopopover/items/list/items/requestpublish