Re: Gnome "unrunnable" after upgrade to Wheezy (Was: "Gnome 3 fail scenario")

2014-01-27 Thread Patrick Bartek
On Mon, 27 Jan 2014, Bob Bernstein wrote: > [snip] > > I have MATE running, evidently very nicely, on a home wheezy > machine, so _real soon now_ I will put it on my new wheezy on the > vpn. I looked at cinnamon but, unlike MATE, they have not yet seen > fit to create a repo of debs that I cou

Re: Gnome "unrunnable" after upgrade to Wheezy (Was: "Gnome 3 fail scenario")

2014-01-27 Thread Bob Bernstein
On Sun, 26 Jan 2014, Patrick Bartek wrote: Or does your VPS use the system's hardware you're logging in from to display the VPS desktop? Yes. Do you own the hardware your VPS runs on... No. or does a "service" and you just purchase space. Yes. Since I think they do a bang-up job, here'

Re: Gnome "unrunnable" after upgrade to Wheezy (Was: "Gnome 3 fail scenario")

2014-01-26 Thread Patrick Bartek
On Sun, 26 Jan 2014, Bob Bernstein wrote: > On Sun, 26 Jan 2014, Patrick Bartek wrote: > > > Your system probably older, and lacks the hardware requirements to > > run GNOME 3 -- mine does, too -- and hence it drops to fallback > > mode. The problem is usually the graphics card. > > My machine,

Re: Gnome "unrunnable" after upgrade to Wheezy (Was: "Gnome 3 fail scenario")

2014-01-26 Thread Bob Bernstein
On Sun, 26 Jan 2014, Patrick Bartek wrote: Your system probably older, and lacks the hardware requirements to run GNOME 3 -- mine does, too -- and hence it drops to fallback mode. The problem is usually the graphics card. My machine, a "virtual private server," has NO video card. I even ran

Re: Gnome "unrunnable" after upgrade to Wheezy (Was: "Gnome 3 fail scenario")

2014-01-26 Thread Patrick Bartek
On Sun, 26 Jan 2014, Bob Bernstein wrote: > I just upgraded squeeze to wheezy on a remote vps host, a "Linode." > Gnome will only launch as far as running the session provided by the > gnome-session-fallback' package. > > Prior to installing _that_ package gnome's failure was sufficiently > ha

Gnome "unrunnable" after upgrade to Wheezy (Was: "Gnome 3 fail scenario")

2014-01-26 Thread Bob Bernstein
I just upgraded squeeze to wheezy on a remote vps host, a "Linode." Gnome will only launch as far as running the session provided by the gnome-session-fallback' package. Prior to installing _that_ package gnome's failure was sufficiently hard to prevent the vpn server on the host from launchin

Re: Check config files on upgrade (was ... Re: Gnome 3 fail scenario)

2014-01-26 Thread Chris Bannister
On Sun, Jan 26, 2014 at 11:59:28AM +, Brad Rogers wrote: > On Mon, 27 Jan 2014 00:39:47 +1300 > Chris Bannister wrote: > > Hello Chris, > > >keep my own version of the config file, which led to my crisis. > >Now if I had known to compare the new '/etc/vim/vimrc' with my one ... > > IDK what

Re: Check config files on upgrade (was ... Re: Gnome 3 fail scenario)

2014-01-26 Thread Brad Rogers
On Mon, 27 Jan 2014 00:39:47 +1300 Chris Bannister wrote: Hello Chris, >keep my own version of the config file, which led to my crisis. >Now if I had known to compare the new '/etc/vim/vimrc' with my one ... IDK what it was like then, but nowadays you're asked if you wish to view the difference

Check config files on upgrade (was ... Re: Gnome 3 fail scenario)

2014-01-26 Thread Chris Bannister
On Sat, Jan 25, 2014 at 07:53:28PM -0500, Bob Bernstein wrote: > Why oh why do I ever choose the package maintainer's config for a > package I have already config'd? It's one of those questions that > plagues perennial philosophy. But I digress... It can bite you both ways! e.g. if a major new ver

Re: Gnome 3 fail scenario

2014-01-26 Thread Joe
On Sat, 25 Jan 2014 19:53:28 -0500 (EST) Bob Bernstein wrote: > > Why oh why do I ever choose the package maintainer's config for a > package I have already config'd? It's one of those questions that > plagues perennial philosophy. Because sometimes if you don't, things break badly. Upgradi

Gnome 3 fail scenario

2014-01-25 Thread Bob Bernstein
When we last left Bob he was preparing to upgrade a host from squeeze to wheezy, using apt-get. That has been on the whole a roaring success, with only a sprinkling of issues -- the usual headache with dovecot, due *entirely* to pilot error. Why oh why do I ever choose the package maintainer