Reading the eselect news about upower, it sounds like I, a systemd user, should and is recommended that I install both upower and upower-pm-utils, with the latter being optional? Anyway, upower-pm-utils is blocking upower. Now I can't update my system or take care of the preserved-rebuild. And I don't use gnome so I could care less about Gnome 3.12. Reproducible: Always Steps to Reproduce: 1. 2.emerge --sync emerge -uDpv world 3. Actual Results: upower is blocked by upower-pm-utils. Expected Results: A happy hands free update, which is becoming rarer and rarer in Gentoo land each passing month.
(In reply to Nolan Eakins from comment #0) > Reading the eselect news about upower, it sounds like I, a systemd user, > should and is recommended that I install both upower and upower-pm-utils, > with the latter being optional? No. If you use systemd + gnome-3, you want upower. If you use systemd + kde or systemd + xfce, you want upower-pm-utils until kde and xfce are updated to support upower properly. If you don't use systemd, you don't have any options, you need upower-pm-utils. Probably we need to document this better, for example in the wiki.
Masking >=upower-0.99 while unmasking upower-0.9.8-ish has emerge humming along. This is frustrating. It seems strange that I had to downgrade upower as 0.99 was working just fine with systemd and xfce. Ideally I should never need to manually [un]mask packages just to update. I expect a better set of ebuilds in Portage. I'll check later to see if downgrading upower causes any bugs.
Don't trust my memory to remember version numbers. Presently running upower-0.9.23, so mistaken about the downgrade. So refining my comment, why did Portage insist on upgrading to upower-0.99 causing a block instead of skipping 0.99?
(In reply to Alexandre Rostovtsev from comment #1) > (In reply to Nolan Eakins from comment #0) > > Reading the eselect news about upower, it sounds like I, a systemd user, > > should and is recommended that I install both upower and upower-pm-utils, > > with the latter being optional? > > No. > > If you use systemd + gnome-3, you want upower. > > If you use systemd + kde or systemd + xfce, you want upower-pm-utils until > kde and xfce are updated to support upower properly. They do. It's just that UPower doesn't provide Hibernate and Suspend anymore, so saying "until kde and xfce are updated to support upower properly", they already do! What you meant to say was "until kde and xfce are updated to use something else for non-systemd users for hibernate and suspend" > > If you don't use systemd, you don't have any options, you need > upower-pm-utils. Not really true, not everyone requires hibernate and suspend or they might use pm-{suspend,hibernate} by command line or by some scripted fashion in their $desktop. > Probably we need to document this better, for example in the wiki. I don't know what's so hard... old upower, upower-pm-utils has hibernate/suspend, new upower doesn't Anyways, I don't see a bug mentioned in the bug, so closing as duplicate of the prev. useless bug regarding this -> *** This bug has been marked as a duplicate of bug 512252 ***
(In reply to Nolan Eakins from comment #3) > Don't trust my memory to remember version numbers. Presently running > upower-0.9.23, so mistaken about the downgrade. So refining my comment, why > did Portage insist on upgrading to upower-0.99 causing a block instead of > skipping 0.99? Portage has packages that are not compatible with 0.99, and Portage has packages that *force* 0.99 as minimum dependency, Portage has packages that explicitely only work with upower-pm-utils So, if you are seeing unsolvable dependencies, then you might want to uninstall some incompatible packages, uninstall outdated overlays, update outdate overlays, re-emerge installed upower consumers, ... Hint: grep sys-power/upower /var/db/pkg/*/*/*.ebuild Complete world update output with --tree --verbose should have been attached here if you suspected a real bug, otherwise gentoo-user mailing list or forums.gentoo.org are better sources to act as helpdesk. Thanks!
Created attachment 380044 [details] emerge -uDpv --tree world This should be obvious.
Created attachment 380046 [details] emerge --info
I'd have posted to the forums but my account got froze for 30 minutes because I couldn't remember my password, but this is a bug in Portage. Updating my status, by masking upower-0.99 and using upower-0.9.23-r3 alongside upower-pm-utils with everything else up to date, systemd no longer suspends when I press my power button even when HandlePowerKey=suspend. XFCE has also lost the battery status icon. Bravo! As far as resolving the upower-0.99 and upower-pm-utils block, is the latter supposed to work with the former? I thought upower-pm-utils was just a compatibility layer so old packages can work with upower-0.99.
With systemd, it's systemd, not upower* that does hibernate and suspend, and when you say... (In reply to Nolan Eakins from comment #8) > systemd no longer > suspends when I press my power button even when HandlePowerKey=suspend. ...it would imply you have bigger problems with your systemd, possibly even logind/polkit related authorization problems > XFCE has also lost the battery status icon. Bravo! xfce4-power-manager no longer has system tray icon, it got a new battery panel plug-in you have to explicitely insert to the panel. that's not a bug, it's a feature. > As far as resolving the upower-0.99 and upower-pm-utils block, is the latter > supposed to work with the former? I thought upower-pm-utils was just a > compatibility layer so old packages can work with upower-0.99. it's one or another, sys-power/upower doesn't have anything to do with hibernate/suspend anymore, only sys-power/upower-pm-utils provides hibernate/suspend, but since you are a systemd user, it's sys-apps/systemd that provides hibernate/suspend and in your portage output, I see outdated packages like: net-im/telepathy-mission-control-5.14.1 that doesn't work correctly for systemd at all, at least version 5.16.1 is required for proper systemd deps so these packages conflicts are coming from outdated packages, it's common you have to solve some blockers by individually upgrading some packages, like # emerge '>=net-im/telepathy-mission-control-5.16.1' for starters. the output will be different after upgrading telepathy-mission-control OR alternatively disabling it's USE="upower" just use the http://forums.gentoo.org/ for thesetype of help, if you are having problems reading the portage output, because that telepathy-mission-control was obvious after you used --tree, as you can see what package is trying to pull in upower-pm-utils from the output.
*** This bug has been marked as a duplicate of bug 512252 ***
>> systemd no longer >> suspends when I press my power button even when HandlePowerKey=suspend. > >...it would imply you have bigger problems with your systemd, possibly even >logind/polkit related authorization problems `systemd suspend` works, even from my user account. Systemd did see the button press. I'll be testing upower-0.99 tonight or tomorrow. Hopefully that does it. > and in your portage output, I see outdated packages like: > >net-im/telepathy-mission-control-5.14.1 I did bump that, though that bump really needs to happen in the portage tree. 5.14.1 is the latest to be keyworded "x86 amd64". > just use the http://forums.gentoo.org/ for thesetype of help, if you are having > problems reading the portage output, because that telepathy-mission-control was > obvious after you used --tree, as you can see what package is trying to pull in > upower-pm-utils from the output. I've known about "--tree" for years. My problems were: the news item wasn't clear on if I needed upower and/or upower-pm-utils; and telepathy-mission-control and the other ebuilds that pulled in upower-pm-utils need better $DEPENDS that don't pull in upower-pm-utils with USE=systemd while keeping upower-0.99 out. See https://bugs.gentoo.org/show_bug.cgi?id=512252#c32
