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: Wed, 12 Oct 2011 15:08:18 -0700 [thread overview]
Message-ID: <CADPrc83Fw5Yjxwm=hNq0spV_PZP8S9qoL8gtJbq+2ET0kHk8gA@mail.gmail.com> (raw)
In-Reply-To: <yu9ehyhev13.fsf@nyu.edu>
On Wed, Oct 12, 2011 at 2:53 PM, Allan Gottlieb <gottlieb@nyu.edu> wrote:
> On Wed, Oct 12 2011, Canek Peláez Valdés wrote:
>
>> On Wed, Oct 12, 2011 at 1:58 PM, Allan Gottlieb <gottlieb@nyu.edu> wrote:
>>>
>>> I notice that I have the default "accessibility" use flag on.
>>> I am tempted to turn it off to reduce the number of packages
>>> involved. Any downside?
>>
>> Not that I know of. Can you please backup /var/lib/gdm, and clean the
>> directory completely? Don't erase the directory, just its contents
>> (including *ALL* the hidden files); gdm needs this directory to start,
>> and it's gid gdm and uid gdm.
>
> I cleaned it. Then built gdm with the gnome-shell flag. This slightly
> repopulated the directory (see ls -lAR below).
>
>> After you have cleaned it, recompile gdm with the gnome-shell and try
>> again. I still don't see why gnome-shell is not starting, but gdm may
>> have problems with its user config (which is stored in /var/lib/gdm),
>> and *maybe* gnome-shell cannot start correctly if gdm is not built
>> with the gnome-shell use flag.
>>
>> Regards.
>
> gdm again failed (oh no, something has gone wrong) upon restart.
> To be certain, I did a reboot, gdm failed again, and then *really*
> cleaned the directory (including the files put there by the emerge)
> It again failed.
The files would reappear everytime you run gdm; they are its
configuration files.
> I tried an emerge --newuse --update --with-bdeps=y world,
> this complained because qt-gui didn't have the accessibility flag.
>
> So I put back accessibility and redid the update world.
> As expected only gdm was rebuilt.
> I restarted gdm (via xdm as usual) and the same failure occurred.
>
> I can't get gdm to run with the gnome-shell use flag.
>
> What use flags do you have for gdm? Here is mine
> Installed versions: 3.2.0-r1[1](05:47:00 PM 10/12/2011)(accessibility consolekit elibc_glibc gnome-shell introspection ipv6 tcpd xklavier -debug -fprint -gnome-keyring -selinux -smartcard -test -xinerama)
>
> thanks for all your efforts,
It's really weird; can I see /var/log/messages (or whatever logger
file you have)? With Enable=true in the [debug] key on
/etc/gdm/custom.conf, we should be able to see why gdm is dying.
My flags are:
Installed versions: 3.2.0-r1[1](05:20:40 PM 10/11/2011)(consolekit
elibc_glibc gnome-keyring gnome-shell introspection ipv6 tcpd xklavier
-accessibility -debug -fprint -selinux -smartcard -test -xinerama)
Mmmh. I didn't even know you could remove gnome-keyring from gdm. If
you are using GNOME, I don't see no reason to disable it. Maybe try
it?
Anyhow, the logs from gdm failing should tell us something. I don't
think is the video, like Michael suggested; supposedly gnome-shell
would detect that.
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-12 22:09 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
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 [this message]
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='CADPrc83Fw5Yjxwm=hNq0spV_PZP8S9qoL8gtJbq+2ET0kHk8gA@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