Bug 384863 - Global menu not exported for different user
Summary: Global menu not exported for different user
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasmashell
Classification: Plasma
Component: Global Menu widget (other bugs)
Version First Reported In: 5.10.5
Platform: Debian unstable Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-19 19:04 UTC by Antonio Russo
Modified: 2017-09-20 08:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonio Russo 2017-09-19 19:04:44 UTC
If a user "mainuser" starts a KDE session, and then starts some application "someapplication" running as another user "otheruser", as it stands, someapplication will not have its global menu available in mainuser's KDE session (though it otherwise integrates fine into that X session: clipboard, etc).

It would be nice if the global menu worked for programs running as another user.
Comment 1 Kai Uwe Broulik 2017-09-19 19:50:02 UTC
I don't think DBus allows this.
Comment 2 Antonio Russo 2017-09-20 03:04:09 UTC
Yeah, I saw that a user dbus cannot be accessed by another (unprivileged) user. I was hoping there might already some work on this.

Maybe something like https://www.freedesktop.org/wiki/Software/DBusRemote/ but maybe something like "(user) dbus over (system) dbus" would be relatively easy to implement?
Comment 3 David Edmundson 2017-09-20 08:32:49 UTC
You can chmod your session DBus socket, and then export the env vars...
Or find a way to proxy it (like your link)

but generally speaking this isn't something we want to do on the plasma level. That's up to you when you start the other app.