<br><br><div class="gmail_quote">2012/10/30 Canek Peláez Valdés <span dir="ltr"><<a href="mailto:caneko@gmail.com" target="_blank">caneko@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="HOEnZb"><div class="h5">On Tue, Oct 30, 2012 at 3:45 PM, João Matos <<a href="mailto:jaoneto@gmail.com">jaoneto@gmail.com</a>> wrote:<br> ><br> ><br> > 2012/10/29 Canek Peláez Valdés <<a href="mailto:caneko@gmail.com">caneko@gmail.com</a>><br> >><br> >> On Mon, Oct 29, 2012 at 4:42 PM, João Matos <<a href="mailto:jaoneto@gmail.com">jaoneto@gmail.com</a>> wrote:<br> >> > I found the solution a few hours ago here<br> >> ><br> >> > <a href="http://en.gentoo-wiki.com/wiki/Systemd#PAM_support:_su.2C_sudo.2C_screen." target="_blank">http://en.gentoo-wiki.com/wiki/Systemd#PAM_support:_su.2C_sudo.2C_screen.</a>..<br> >> > . Now everything is fine :)<br> >> ><br> >> > About the packages you mentioned, you've ran 'equery uses pambase polkit<br> >> > udisks upower', and none of them has the userflag systemd.<br> >><br> >> # equery uses pambase polkit udisks upower<br> >> [ : I - package is installed with flag ]<br> >> * Found these USE flags for sys-auth/pambase-20120417-r1:<br> >> [snip]<br> >> + + systemd : Use pam_systemd module to register user sessions<br> >> in the systemd control group hierarchy.<br> >><br> >> * Found these USE flags for sys-auth/polkit-0.107-r1:<br> >> [snip]<br> >> + + systemd : Use sys-apps/systemd instead of<br> >> sys-auth/consolekit for session tracking<br> >><br> >> * Found these USE flags for sys-fs/udisks-2.0.0:<br> >> [snip]<br> >> + + systemd : Support sys-apps/systemd's logind<br> >><br> >> * Found these USE flags for sys-power/upower-0.9.18:<br> >> [snip]<br> >> + + systemd : Use sys-apps/systemd for hibernate and suspend<br> >><br> >> Depends on the versions ;)<br> ><br> ><br> > yep. I've used ~amd64 for about 5 years, but last year I decided to use<br> > amd64. Maybe systemd suport is better in more recent packages.<br> <br> </div></div>Indeed it is. I don't run ~amd64, BTW; I just keyword some things (the<br> kernel, systemd+udev, and GNOME, basically).<br> <div class="im"><br> > Well, I've just find out a new little problem: PulseAudio. I've found<br> > nothing about systemd+pulseaudio on google, what means that it is too easy<br> > to some one carry about writing about it, or nobody tried it yet. Does<br> > anyone knows how to start it? Maybe writing a pulseaudio.service or<br> > something like that.<br> <br> </div>Both projects have the same author: Lennart Poettering. There is<br> usually nothing to be done so they work together; in GNOME, PulseAudio<br> is started automatically by the session manager, I suppose it should<br> be something similar in KDE-land. Actually, since PA is a user (not a<br> system) service, the init system you use doesn't matter.<br></blockquote><div><br>The past week I've changed my whole system (get rid of genkernel, installed systemd...). It's been difficult to find out how to solve some problem that appear, because I have to guess what originated it. But I think I have a progress with that one: revdep-rebuild found a problem with pulseaudio (and some others), I still get an error while I compile it, but I'm working on it.<br> <br>I was thinking It should be a service, since it was on my rc default level. But it seems it is not encouraged anymore. Thank you anyway.<br></div></div><br>-- <br>João de Matos<br>Linux User #461527<br>