From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] can't build gnome 3.2 (3.0 was ok)
Date: Tue, 11 Oct 2011 15:30:48 -0700 [thread overview]
Message-ID: <CADPrc81GyusP9vTpOqc5soiwVR4EsWfQVacq9MUA27TTsSUhyQ@mail.gmail.com> (raw)
In-Reply-To: <yu91uujqirg.fsf@nyu.edu>
On Tue, Oct 11, 2011 at 3:13 PM, Allan Gottlieb <gottlieb@nyu.edu> wrote:
> For me, gnome 3.2 has been quite a regression over 3.0.
Weird; for me it works so much better than 3.0.
> Summary:
>
> gdm-3.2.0-r1 crashes and when I revert to the 3.0 gdm, I get to the
> login screen but then gnome-shell crashes. I tried to downgrade to
> gnome-shell-3.0.2-r1, but that needs libgnome-menu, which is not in
> portage/layman.
>
> The crash of gdm is described in bug #385525.
>
> The crash of gnome-shell is described in the following .xsession-errors
> file (tracker-miner-fs.log and tracker-store.log are empty).
>
> any help would be appreciated.
> allan
Are you running the updated git of gnome-overlay? I had troubles with
gnome-settings-daemon until a couple of days.
Can you try to start GNOME with a clean config (no ~/.config, no
~/.local, no ~/.gconf, no ~/.gnome*). Just backup your current config
and remove it from $HOME, or try to start GNOME with a dummy new user.
Also, in my case, having gnome-shell extensions installed caused me
problems when upgrading.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2011-10-11 22:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 22:13 [gentoo-user] can't build gnome 3.2 (3.0 was ok) Allan Gottlieb
2011-10-11 22:30 ` Canek Peláez Valdés [this message]
2011-10-11 23:42 ` David Abbott
2011-10-12 1:19 ` Allan Gottlieb
2011-10-12 1:18 ` Allan Gottlieb
2011-10-12 1:37 ` Canek Peláez Valdés
2011-10-12 14:26 ` David Abbott
2011-10-12 16:52 ` Allan Gottlieb
2011-10-12 15:31 ` Allan Gottlieb
2011-10-12 16:49 ` Canek Peláez Valdés
2011-10-12 20:58 ` Allan Gottlieb
2011-10-12 21:19 ` Canek Peláez Valdés
2011-10-12 21:53 ` Allan Gottlieb
2011-10-12 22:08 ` Canek Peláez Valdés
2011-10-12 22:16 ` Michael Schreckenbauer
2011-10-12 22:25 ` Canek Peláez Valdés
2011-10-12 22:27 ` Allan Gottlieb
2011-10-12 22:52 ` Allan Gottlieb
2011-10-13 0:04 ` Canek Peláez Valdés
2011-10-13 0:02 ` Canek Peláez Valdés
2011-10-13 1:20 ` Allan Gottlieb
2011-10-13 1:36 ` Allan Gottlieb
2011-10-13 4:10 ` Canek Peláez Valdés
2011-10-13 13:39 ` Allan Gottlieb
2011-10-13 8:58 ` Michael Schreckenbauer
2011-10-13 13:29 ` Allan Gottlieb
2011-10-13 13:36 ` Michael Mol
2011-10-13 13:47 ` Allan Gottlieb
2011-10-13 13:53 ` Michael Mol
2011-10-13 15:05 ` Michael Schreckenbauer
2011-10-14 1:03 ` Allan Gottlieb
2011-10-12 21:40 ` Michael Schreckenbauer
2011-10-12 22:02 ` Allan Gottlieb
2011-10-12 22:10 ` Michael Schreckenbauer
2011-10-12 22:46 ` Allan Gottlieb
2011-10-13 0:03 ` Canek Peláez Valdés
2011-10-13 13:34 ` Allan Gottlieb
2011-10-13 18:45 ` Canek Peláez Valdés
2011-10-14 1:20 ` Allan Gottlieb
2011-10-14 1:58 ` Canek Peláez Valdés
2011-10-14 2:44 ` Allan Gottlieb
-- strict thread matches above, loose matches on Subject: below --
2011-10-13 12:21 Denis I. Polukarov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADPrc81GyusP9vTpOqc5soiwVR4EsWfQVacq9MUA27TTsSUhyQ@mail.gmail.com \
--to=caneko@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox