Re: [gentoo-user] [~amd64] Anyone survive the big gnome update from this morning (July 25)?

2013-07-26 Thread Thanasis
Thanks for the heads-up.



Re: [gentoo-user] [~amd64] Anyone survive the big gnome update from this morning (July 25)?

2013-07-26 Thread Stefan G. Weichinger
Am 26.07.2013 03:10, schrieb walt:
 I'm very happy that I did the gnome update on a virtual gentoo
 machine instead of my real machine :)  The virtual gentoo is
 unusable at the moment because gnome is very sick indeed.
 
 I avoided the big update on my real machine when I saw that
 gnome-shell (I think it was) demanded the installation of
 systemd on my openrc-only system.
 
 Now, I've been running systemd on the virtual gentoo machine
 for months with no problems, so I wasn't worried about the
 big update on that machine.
 
 AFAICT the systemd update has nothing to do with gnome's sickness,
 systemd-206 seems to be working just fine on the virtual machine.
 
 The gnome desktop, however, is completely black except for one
 functioning gnome main-menu applet, which lets me open an xterm
 for potential debugging efforts.
 
 Running nautilus from the xterm prompt produces this error:
 
 GLib-GIO_ERROR: Settings schema 'org.gnome.desktop.background'
 does not contain a key named 'draw-background'
 Trace/breakpoint trap
 
 Has anyone else tried the same update yet?

I didn't notice anything today ... which might be related to the fact
that I unmasked gnome-3.8 months(?) ago.

So gnome-shell-3.8.3-r2 got keywords changed ... right?

I am sure you already did the usual revdep-rebuild-stuff etc?

Stefan




Re: [gentoo-user] [~amd64] Anyone survive the big gnome update from this morning (July 25)?

2013-07-26 Thread Todd Goodman
* walt w41...@gmail.com [130725 21:12]:
 I'm very happy that I did the gnome update on a virtual gentoo
 machine instead of my real machine :)  The virtual gentoo is
 unusable at the moment because gnome is very sick indeed.
 
 I avoided the big update on my real machine when I saw that
 gnome-shell (I think it was) demanded the installation of
 systemd on my openrc-only system.
 
 Now, I've been running systemd on the virtual gentoo machine
 for months with no problems, so I wasn't worried about the
 big update on that machine.
 
 AFAICT the systemd update has nothing to do with gnome's sickness,
 systemd-206 seems to be working just fine on the virtual machine.
 
 The gnome desktop, however, is completely black except for one
 functioning gnome main-menu applet, which lets me open an xterm
 for potential debugging efforts.
 
 Running nautilus from the xterm prompt produces this error:
 
 GLib-GIO_ERROR: Settings schema 'org.gnome.desktop.background'
 does not contain a key named 'draw-background'
 Trace/breakpoint trap
 
 Has anyone else tried the same update yet?

I blocked the whole update by adding entries to package.mask (don't know
if there was an easier way) because I don't want systemd on my ~amd work
machines.

Todd



[gentoo-user] [~amd64] Anyone survive the big gnome update from this morning (July 25)?

2013-07-25 Thread walt
I'm very happy that I did the gnome update on a virtual gentoo
machine instead of my real machine :)  The virtual gentoo is
unusable at the moment because gnome is very sick indeed.

I avoided the big update on my real machine when I saw that
gnome-shell (I think it was) demanded the installation of
systemd on my openrc-only system.

Now, I've been running systemd on the virtual gentoo machine
for months with no problems, so I wasn't worried about the
big update on that machine.

AFAICT the systemd update has nothing to do with gnome's sickness,
systemd-206 seems to be working just fine on the virtual machine.

The gnome desktop, however, is completely black except for one
functioning gnome main-menu applet, which lets me open an xterm
for potential debugging efforts.

Running nautilus from the xterm prompt produces this error:

GLib-GIO_ERROR: Settings schema 'org.gnome.desktop.background'
does not contain a key named 'draw-background'
Trace/breakpoint trap

Has anyone else tried the same update yet?