From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: about to give up on systemd and gnome
Date: Fri, 23 May 2014 19:40:02 -0400 [thread overview]
Message-ID: <28031.1400888402@ccs.covici.com> (raw)
In-Reply-To: <537FCBCA.6060902@gmail.com>
walt <w41ter@gmail.com> wrote:
> On 05/23/2014 12:50 PM, covici@ccs.covici.com wrote:
> > Hi. Well, I thought I was making progress with systemd, but my gnome
> > session kept saying "oh no something has gone wrong" and would not
> > work. Also, after such a thing has happened, all my consoles would keep
> > using the last line to put every line and so I had to keep rebooting.
> > And when I would reboot systemd would not behave the same way, sometimes
> > it would hang at certain places, and sometimes it would go all the way
> > through, but things would not start properly -- maybe a concurrency
> > problem, but its hard to say what was going on. What a mess, but I
> > guess I have a setup which systemd does not like, too much parallellism
> > and no way to get things to start in the order I want them -- or at
> > least none I could figure out!
> >
> > I am open to suggestions here, and I have a log segment I can put
> > somewhere to illustrage the "oh no" problem, but I am getting tired of
> > the mess and if I can find something which works with orca I will do
> > that instead.
>
> I've spent many frustrating days fighting the "oh no" syndrome and I
> found two very annoying workarounds before I gave up on gnome3.
>
> First, the file ~/.gnomerc-errors may give you some good hints. Many
> of my "oh no" moments were caused by broken xorg 3D rendering support,
> i.e. broken video drivers, etc, etc.
>
> Second, many other "oh no" moments were caused by $SOME_MYSTERIOUS
> item in ~/.config or ~/.local suddenly rendered erroneous by a gnome3
> update.
>
> I found some of those problem items by renaming those two directories
> and starting with a completely blank gnome3 slate.
>
> If gnome-shell starts okay with the new tabla rasa then you can copy
> the old .local and .config subdirectories one by one into the new gnome
> environment until you can reproduce the original breakage. Repeat as
> needed.
Thanks for the hint --I have no ~/.gnomerc-errors -- I have a
.Xsession-errors, but it never told me anything useful.
I may try your other suggestion next time I have the courage to boot
into systemd.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
next prev parent reply other threads:[~2014-05-23 23:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 19:50 [gentoo-user] about to give up on systemd and gnome covici
2014-05-23 21:49 ` Walter Dnes
2014-05-23 22:29 ` [gentoo-user] " walt
2014-05-23 23:40 ` covici [this message]
2014-05-23 22:36 ` [gentoo-user] " Tom Wijsman
2014-05-23 23:42 ` covici
2014-05-24 5:52 ` covici
2014-05-24 5:58 ` Edward M
2014-05-24 6:15 ` covici
2014-05-24 6:19 ` covici
2014-05-23 23:20 ` EdwardM
2014-05-24 8:10 ` Tom Wijsman
2014-05-24 9:40 ` covici
2014-05-24 10:23 ` Tom Wijsman
2014-05-24 11:02 ` covici
2014-05-24 19:29 ` covici
2014-05-25 0:06 ` [gentoo-user] " walt
2014-05-25 8:13 ` [gentoo-user] " Tom Wijsman
2014-05-25 9:26 ` covici
2014-05-28 0:07 ` Tom Wijsman
2014-05-28 2:24 ` covici
2014-05-25 9:38 ` covici
2014-05-25 10:33 ` Tom Wijsman
2014-05-25 11:45 ` covici
2014-05-25 12:02 ` covici
2014-05-25 12:14 ` Tom Wijsman
2014-05-25 12:34 ` covici
2014-05-25 8:32 ` Marc Stürmer
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=28031.1400888402@ccs.covici.com \
--to=covici@ccs.covici.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