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

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

[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?

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

[Thanasis]

Thanks for the heads-up.

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

[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)?

[Todd Goodman]

* walt <w41ter@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] Re: [~amd64] Anyone survive the big gnome update from this morning (July 25)?[painfully FIXED]

[walt]

On 07/25/2013 06:10 PM, walt wrote:
> 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.

Two things changed today to help fix the problems:  more gnome
package updates were committed overnight, and I changed my
make.profile from plain "desktop" to "desktop/gentoo".

I spent all day today fixing and working around problems, though.
Mostly conflicting package slots, conflicting useflags, and two
gnome packages that won't compile.  I'm pooped, but gnome-shell
is actually working now!

Tomorrow: I start installing gnome-shell extensions :/

BTW, gnome-base/gnome-fallback doesn't work for me any longer, but
there are recent gnome-shell extensions that do similar things.

BTW #2, I had to start with a clean home directory with no gnome
stuff left over from before the update, otherwise the loveable and
very cuddly "Oh No!  Something has gone very wrong and you're now
screwed" icon pops up.  I'll try to narrow down the guilty config
files tomorrow