On Sunday 28 Jul 2013 17:16:55 Canek Peláez Valdés wrote: > On Sun, Jul 28, 2013 at 8:23 AM, Michael Hampicke <m...@hadt.biz> wrote: > > Am 28.07.2013 10:07, schrieb Stefan G. Weichinger: > >> Am 28.07.2013 10:04, schrieb Canek Peláez Valdés: > >>> The only "special" thing I'm doing is to mask >sys-apps/systemd-204, > >>> since 205 introduced the new cgroups management code (with systemd as > >>> the only writer of the cgroups hierarchy), and it seems to cause some > >>> minor problems with logind. Other than that, it works withouth a > >>> glitch: gnome-base/gnome-3.8.0, sys-apps/systemd-204, no consolekit at > >>> all. > >> > >> Same here, yes. I run systemd-206 but I didn't notice an problem(s) yet. > >> Maybe there are some and I don't get it ;-) > > > > I had one problem, but I am not sure, if it's related to systemd > 204, > > the removal of consolekit, or gnome at all. > > > > But when logging into my gnome session, /usr/libexec/gvfsd-fuse can not > > be started, because the permissions of /dev/fuse are rw------ root:root > > > > Other distros like ubuntu have a fuse group for that, which does not > > exist on gentoo. So I assume the default permissions for /dev/fuse on > > gentoo machines should be rw-rw-rw- root:root? > > My problem was that *sometimes* (not always) I was unable to unlock my > session after suspending my laptop or desktop. Reverting back to > systemd-204 solved it, so I'm assuming that's the problem, although I > didn't really investigated the issue.
On my vanilla stable Gentoo with openrc, /dev/fuse permissions are: $ ls -la /dev/fuse crw-rw-rw- 1 root root 10, 229 Jul 29 08:22 /dev/fuse -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
