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