Installing gnome-3.32[extras] pulls in gnome-base/gnome-extra-apps, which pulls in net-misc/vino. The vino ebuild requires sys-apps/dbus[user-session] if the systemd USE flag is set. This conflicts with other packages that require sys-apps/dbus[-user-session]. Reproducible: Always Bug 639434 and Bug 576028 may be relevant or related to this.
What packages require dbus[-user-session] ? Only thing is that bluez user-session choice has to match with dbus user-session choice.
Bug 528674 might be more relevant, as the issue is likely with systemd + selinux. I'll add the relevant chat logs from the #gentoo channel, in hopes of providing context and clarification. 05:48:30 +leio | there is no conflict 05:48:49 +leio | you need to have bluez USE=user-session match dbus USE=user-session 05:48:50 +leio | that's it. 05:49:16 +leio | vino requires user-session for it to actually be useful automatically (gnome-settings-daemon requires user-session to launch the remote desktop service of vino when you enable it) 05:49:40 grawity | is that because it always tries to launch vino via systemd? 05:49:52 +leio | In the near future I will remove vino user-session requirement, but add it to a gnome core package if USE=systemd 05:50:07 +leio | yes, it always uses vino via user activation. 05:50:26 +leio | if you want to use it without systemd, you get to run the daemon from libexec manually 05:51:05 +leio | on an openrc system, it doesn't really matter I believe - just dbus[user-session] isn't enough - it needs systemd user session too. 05:51:30 +leio | hence the plan to move that user-session dep to what actually launches vino and gnome-remote-desktop via user systemd services 05:51:44 ilmostro | leio: I wonder how that will work with systemd + selinux. Otherwise, there will never be support for such systems :( 05:52:04 +leio | probably works just fine; fedora does selinux, I believe? 05:52:48 ilmostro | leio: Indeed; on gentoo, I am running systemd + selinux. At the moment, bluez doesn't even list user-session as a USE flag when listed with equery u bluez. 05:53:28 ilmostro | leio: I'm trying to collect all relevant info, as this has come up a number of times in the past 05:53:54 +leio | With GNOME 3.34 dbus[user-session] will be a hard requirement on systemd systems 05:54:18 +leio | on openrc systems, it'll remain as-is, that just vino, gnome-remote-desktop and such can't auto-launch, as today 05:56:06 ilmostro | leio: so upstream decision is hard-coding that for the benefit of systemd-related feature, right? Openrc is not able to use autolaunch (feature) anyway? 05:57:35 +leio | No, the upstream decision with 3.34 is that gnome-session launches all the services via systems in the user scope, not itself 05:57:42 +leio | via systemd* 05:58:51 ilmostro | Yikes; that might either be a blocker for gentoo + gnome + selinux, unless systemd + selinux support is stabilized 05:59:10 +leio | openrc remains working the old way, for now 05:59:47 +leio | someone needs to step up and take care of these gnome and systemd selinux gentoo rules 05:59:54 ilmostro | leio: sorry about the incessant questions; just for clarification, "for now" means <gnome-3.34 as it stands 06:00:23 +leio | no, it means 3.34 will remain as-is in terms of gnome services launching without systemd. 06:00:29 +leio | They have not yet removed the old code, but there are plans. 06:02:37 +leio | once I shift around the user-session deps, I will also package.use what's needed in gnome/systemd profiles
As far as I can tell, the net-wireless/bluez ebuild requires sys-apps/dbus[-user-session] if/when the systemd USE flag is enabled. So, maybe this bug should be focusing on that instead, since other packages (including vino ) depend on the user-session USE flag.
(In reply to Amel Hodzic from comment #3) > As far as I can tell, the net-wireless/bluez ebuild requires > sys-apps/dbus[-user-session] if/when the systemd USE flag is enabled. So, > maybe this bug should be focusing on that instead, since other packages > (including vino ) depend on the user-session USE flag. No... just enable user-session for both dbus and bluez.
The only issue I have seen is that, on a system without user-session globally enabled, portage will unmask dbus[user-session] to fit vino requirement... but later it will fail to update world because of the conflict with bluez[-user-session]. That can be avoided if we enable by default user-session in our gnome/systemd profile
I can't seem to get this to work. setting 'USE="user-session"' still fails to resolve dependencies for sys-apps/dbus and net-wireless/bluez on my system with systemd. The same is true when using it on the commandline. sys-apps/dbus:0 (sys-apps/dbus-1.12.16:0/0::gentoo, ebuild scheduled for merge) conflicts with >=sys-apps/dbus-1.6:0/0=[-user-session] required by (net-wireless/bluez-5.52:0/3::gentoo, installed) ^^^^^^^^^^^^^ >=sys-apps/dbus-1.6:=[-user-session] required by (net-wireless/bluez-5.52:0/3::gentoo, installed)
The issue raised in the previous comment seems to be isolated to my system with systemd + selinux. The following command allowed sys-apps/dbus[user-session] and net-wireless/bluez[user-session] to build as expected. # echo 'net-wireless/bluez -user-session' >> /etc/portage/profile/package.use.mask
fwiw, I reworked the deps a week or couple weeks ago to do the user-session stuff on gnome-settings-daemon instead, and I added the USE=user-session stuff to gnome systemd profiles
