public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 17:02:37 -0700	[thread overview]
Message-ID: <CADPrc82gGnByV1ezFBTtgshQDJP-zUmG+OeTT2_QX+kUAO6eCw@mail.gmail.com> (raw)
In-Reply-To: <yu962jtetgo.fsf@nyu.edu>

On Wed, Oct 12, 2011 at 3:27 PM, Allan Gottlieb <gottlieb@nyu.edu> wrote:
> On Wed, Oct 12 2011, Canek Peláez Valdés wrote:
>
>> 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.
>
> The output is below
>
>> 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?
>
> OK I will add it to my use flags.  That machine has profile
> linux/x86/10.0.  My real machine has profile
> linux/amd64/10.0/desktop/gnome.  Clearly the x86 vs amd64 is right, but
> I could(?) change my profile to desktop/gnome.  But that sounds like a
> big change that could open a can of worms.  My main machine (running
> gnome 2 not 3) has the gnome-keyring use flag for gdm)
>
>> 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.
>
> I should have said that the video is working.  The "blue drapery"
> appears for a second before we get the black screen with the "oh no"
> msg.

Yeah, but Michael suggested that gnome-shell is crashing with your
particular combination of card/drivers. It is possible, for the quick
search I did for this problem.

What it is true is that gnome-shell is dying when gdm calls it:

Oct 12 17:47:48 oldlap gnome-session[15888]: DEBUG(+): GsmXSMPClient:
IceProcessMessagesIOError on '0x80aa870 [gnome-shell
106560af3f298b1c4413184560649172300000158880000]'

If it is related to the video card/driver that you use, try reemerging
cogl and clutter; it doesn't matter that a world upgrade don't want to
reemerge it, sometimes the ebuilds change without changing versions.
My versions and useflags of cogl and clutter are:

# emerge -1pv clutter cogl

These are the packages that would be merged, in order:

Calculating dependencies                ... done!
[ebuild   R   ~] media-libs/cogl-1.8.0  USE="doc examples
introspection pango -debug -test" 0 kB [1]
[ebuild   R   ~] media-libs/clutter-1.8.0  USE="doc introspection
-debug" 0 kB [1]

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México



  parent reply	other threads:[~2011-10-13  0:04 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
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 [this message]
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=CADPrc82gGnByV1ezFBTtgshQDJP-zUmG+OeTT2_QX+kUAO6eCw@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