| 1 |
On 05/13/2013 04:06 AM, covici@××××××××××.com wrote: |
| 2 |
> When I start gdm, I get a message on the screen which says oh no, |
| 3 |
> something has gone wrong. |
| 4 |
|
| 5 |
If I had a bitcoin for every time I've seen that message I could buy |
| 6 |
all of us a beer. Maybe two :) |
| 7 |
|
| 8 |
> The log file is at |
| 9 |
> http://pastebin.com/qwNE7ee6 -- I would appreciate any help. |
| 10 |
|
| 11 |
There are no obvious problems in your Xorg log, so the real error |
| 12 |
is not logged there. I don't use gdm so I'm not sure where those |
| 13 |
errors are logged. Anyone? |
| 14 |
|
| 15 |
The main reason I don't like using one of the *dm display managers |
| 16 |
is exactly to avoid this sort of PITA where you can't even see the |
| 17 |
real error messages. That's why I use startx instead. |
| 18 |
|
| 19 |
Anyway, the trick *I* would try is to add the gentoo=nox kernel |
| 20 |
option to the grub boot prompt (assuming you use grub) to prevent |
| 21 |
gentoo from even trying to start an X session, thus avoiding gdm |
| 22 |
and allowing you to use startx so you can read the gnome error |
| 23 |
messages on the console while X starts up. |
| 24 |
|
| 25 |
If you can ssh into that machine you could also try removing xdm |
| 26 |
from your /etc/runlevels/default directory, assuming it's there. |
| 27 |
I'm not at all sure how the *dms are usually started during boot, |
| 28 |
so someone else could give you a better answer. |
Archives