On 05/23/2014 12:50 PM, cov...@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.
