From: Allan Gottlieb <gottlieb@nyu.edu>
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 18:02:16 -0400 [thread overview]
Message-ID: <yu9aa95eumv.fsf@nyu.edu> (raw)
In-Reply-To: <4648346.0B5O5UOGn3@pc> (Michael Schreckenbauer's message of "Wed, 12 Oct 2011 23:40:48 +0200")
On Wed, Oct 12 2011, Michael Schreckenbauer wrote:
>
> gnome-shell segfaults.
> I remember some problems with gnome-shell and GL from the dri-devel-ML.
> What video-card are you using? Drivers/version?
> Is there any other WM you can start, execute
> gnome-shell --replace
> in a console and dump the output here?
> Could you try running gnome in "fallback-mode"?
> Afaik you can enable this with
> gsettings set org.gnome.desktop.session session-name gnome-fallback
Actually the gnome-shell segfault is the 2nd problem. gdm crashes with
Oh no, a problem has occurred unless its gnome-shell use flag is
disabled, which could possibly be the cause of gnome-shell failing.
Canek has suggested we attack the gdm problem (see other msgs in this
thread) and that is the current plan. Unfortunately we are still not
there.
In bug 385525, those who needed -gnome-shell for gdm could then not get
gnome-shell to run (i.e., just like me).
It does seem that many are successfully running gdm so I must have
something wrong in my setup. What use flags did you build gdm with.
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 the help,
allan
next prev parent reply other threads:[~2011-10-12 22:02 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
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 [this message]
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=yu9aa95eumv.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--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