/srv/irclogs.ubuntu.com/2014/04/21/#ubuntu-us-or.txt

bkeroWow, upgrade process really sucks.20:44
bkero1) ppa-purge all ppas else face the 'broken packages' silent failure of update-manager or do-release-upgrade, 2) reinstall ubuntu-desktop metapackage, 3) reboot, 4) do-release-upgrade/update-manager, 5) reboot, 6) install ppas, 7) reboot20:45
adam_gPPAs <321:01
blkperlslangasek: :( https://bugs.launchpad.net/indicator-session/+bug/47439222:55
lubotu1Ubuntu bug 474392 in indicator-session (Ubuntu) "indicator-session menus are not policykit aware" [Low,Confirmed]22:55
blkperlhow how am I suppose to stop users from clicking suspend <.<22:55
nibalizermove the pm-suspend binary to somewhere else lol22:57
nibalizerreplace it with a shell script that says 'NO'22:57
nibalizeror better yet figlet no22:57
blkperlit doesn't call pm-suspend it calls the xorg-libs directly22:58
nibalizeroh wtf22:58
nibalizerblkperl: it looks like someone has a suggestion on how to patch it to work23:00
nibalizeri bet you could get that working in a day or 223:01
nibalizerprobably would be pretty fun23:01
blkperlnope, don't want to maintain that23:01
nibalizeror incredibly frustrating23:01
nibalizeri mean the patch would likely be accepted into ubuntu23:01
slangasekblkperl: umm, that bug is ancient, how is that your bug?23:05
blkperlslangasek: read Trusty comment23:06
blkperlthey re-broke it23:06
slangasekalso, how does indicator-session being policykit aware or not have to do with anything?  the indicator-session itself has no privileges to trigger a suspend; the bug is elsewhere23:06
blkperlI'm not saying the bug is correclty named23:06
blkperlbut yes its broken in Trusty :)23:06
slangasekno, that bug is about the options being *displayed* when they shouldn't be23:06
slangasekbut a non-policykit-aware indicator doesn't mean that users have privs to trigger a suspend23:07
blkperlbut they do23:07
slangasek*because of an unrelated bug*23:07
blkperlbug number?23:08
blkperlor should I file one23:08
slangasekyou should file one23:08
blkperlok thanks!23:08
slangasekbecause the problem you're describing (users can suspend when they shouldn't) is not the same as that bug (users who can't suspend are shown a menu option)23:08
blkperlshould I file it agasint indicator-session?23:09
slangasekit's not an indicator bug, better to file it on whatever indicator-session is calling that's not respecting policykit23:09
slangaseksystemd might be the best choice initially (for logind)23:10
blkperlso file against logind or systemd?23:10
slangaseksystemd23:10
slangaseklogind isn't a package23:10
blkperlk23:10
blkperlhttps://bugs.launchpad.net/indicator-session/+bug/116502723:11
lubotu1Ubuntu bug 1165027 in Session Menu "Indicator-session Hibernate/Suspend capabilities are inconsistent with unity dialogue" [Medium,Triaged]23:11
blkperlwhat about that ^ slangasek23:11
slangasekarguably a duplicate of the first bug23:12
slangasekyour bug is that logind is honoring a suspend/hibernate request that you believe it should not23:12
* blkperl tries to remember how to verify policykit rules23:14
blkperlhttps://bugs.launchpad.net/ubuntu/+source/systemd/+bug/131084523:21
lubotu1Ubuntu bug 1310845 in systemd (Ubuntu) "systemd-logind is not honoring polickykit rules for suspend/reboot/shutdown" [Undecided,New]23:21
blkperlnot really sure what else to put in the bug report23:21
blkperlthanks for the help slangasek :)23:22
nibalizerya slangasek thanks :)23:22
slangasekn/p23:23

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!