Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Sun, 2013-07-28 at 11:16 -0500, 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. This turned out to be an upstream issue. See: https://bugs.freedesktop.org/show_bug.cgi?id=67267 and the corresponding Gentoo bug: https://bugs.gentoo.org/show_bug.cgi?id=477954 Upstream has already fixed it on git, so we'll either have to wait until systemd-207 or see if the systemd maintainers cherry pick the patch as 206-r1 on portage. --Mark
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
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.
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Mon, Jul 29, 2013 at 3:28 AM, Mark Pariente markparie...@gmail.com wrote: On Sun, 2013-07-28 at 11:16 -0500, 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. This turned out to be an upstream issue. See: https://bugs.freedesktop.org/show_bug.cgi?id=67267 Yeah, I suspected so; that was my theory in the mail I sent yesterday: http://article.gmane.org/gmane.linux.gentoo.user/267762 So it is indeed the new slices code. I'm staying on 204 until 207 comes out. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Sat, Jul 27, 2013 at 5:56 PM, walt w41...@gmail.com wrote: On 07/27/2013 03:08 PM, Canek Peláez Valdés wrote: And actually, the long term plan is for systemd --user to basically replace gnome-session-manager, Is Lennart part of the gnome project now? ;) so just installing systemd is not going to work at all in the future, even if it *may* seems to work now (which I'm pretty sure it doesn't). Maybe I'll be able to confirm or deny tomorrow morning :) The update will take all night (on my slower machine) but I fear that the build will quit with an error as soon as my head hits the pillow. I'll let you know in the morning. As an aside, I got this great idea for automating the update: Instead of removing all gnome packages before updating gnome (much too much boring work for lazy me) I updated the glib package first because All Things Gnome depend on glib. Then I started revdep-rebuild, which of course will automatically re- install every gnome package on the machine (and update to the latest versions of everything in the process :). Of course portage refused to do the glib update because of a zillion or more package conflicts, so I worked around that by running: #ebuild /usr/portage/dev-libs/glib/glib-2.36.3-r1 merge Let's see how many hours of pain my laziness will cost me this time :) I finally updated; I had no problems whatsoever. I also stopped using my overlay (and will soon discontinue it); with the introduction of virtual/service-manager, it's not longer necessary to have a systemd-only (without OpenRC) machine. 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. Then again, this is how I've been running my machines since last year. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
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 ;-) Stefan
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
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? signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
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. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
[gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On 07/28/2013 01:04 AM, Canek Peláez Valdés wrote: I finally updated; I had no problems whatsoever. The only way I could solve all of the conflicts on my openrc machine was to enable the systemd useflag globally (to prevent consolekit and udev being pulled in). It's updating to gnome-3.8 now and I'm sure it will take all night. With systemd being used by several critical gnome packages I'm thinking that systemd will indeed need to be running for all those packages to work correctly. But I'll find out tomorrow :)
[gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On 07/27/2013 03:08 PM, Canek Peláez Valdés wrote: And actually, the long term plan is for systemd --user to basically replace gnome-session-manager, Is Lennart part of the gnome project now? ;) so just installing systemd is not going to work at all in the future, even if it *may* seems to work now (which I'm pretty sure it doesn't). Maybe I'll be able to confirm or deny tomorrow morning :) The update will take all night (on my slower machine) but I fear that the build will quit with an error as soon as my head hits the pillow. I'll let you know in the morning. As an aside, I got this great idea for automating the update: Instead of removing all gnome packages before updating gnome (much too much boring work for lazy me) I updated the glib package first because All Things Gnome depend on glib. Then I started revdep-rebuild, which of course will automatically re- install every gnome package on the machine (and update to the latest versions of everything in the process :). Of course portage refused to do the glib update because of a zillion or more package conflicts, so I worked around that by running: #ebuild /usr/portage/dev-libs/glib/glib-2.36.3-r1 merge Let's see how many hours of pain my laziness will cost me this time :)
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Sat, Jul 27, 2013 at 03:56:41PM -0700, walt wrote On 07/27/2013 03:08 PM, Canek Peláez Valdés wrote: And actually, the long term plan is for systemd --user to basically replace gnome-session-manager, Is Lennart part of the gnome project now? ;) Lennart is a Redhat employee, and Gnome+systemd are Redhat's pride and joy. It's not linux anymore, it's REDHAT-GNOME-OS. -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
Re: [gentoo-user] Re: [~amd64] Some possibly (?) helpful hints re the big gnome-3.8 update
On Jul 27, 2013 5:57 PM, walt w41...@gmail.com wrote: On 07/27/2013 03:08 PM, Canek Peláez Valdés wrote: And actually, the long term plan is for systemd --user to basically replace gnome-session-manager, Is Lennart part of the gnome project now? ;) He has been on Planet GNOME for many years now. When people talks about GNOME OS, it implicitly includes the Linux kernel, sytemd/udev (including journald, hostnamed, logind, etc.), dbus, Avahi, PulseAudio, and all the GNOME stack from glib up to GNOME Shell. Vertical tight integration from kernel to end user apps. Regards.
