You are not logged in.
Pages: 1
Topic closed
Today after I run pacman -Suy, GDM/Gnome won't start anymore after reboot. The error message I get after GDM starts is:
Oh no! Something has gone wrong.
A problem has occurred and the system can't recover. Please contact a system administrator
Does anyone have any idea what happened and how can I recover the system?
Here is the complete log for the update:
http://bpaste.net/show/209520/
Here is the journalctl -u gdm log:
Here is tail -2000 /var/log/messages.log:
And here is the /var/log/Xorg.0.log:
http://bpaste.net/show/209549/
I can't imagine any other log file that might help figure out what happened, let me know if there's anything else.
Any help is appreciated. Thanks.
Edit: I stopped gdm, created a ~/.xinitrc and could successfully start Gnome with startx. The problem remains with GDM.
Edit: The last update solved my problem: http://sprunge.us/RKWA
Last edited by falmp (2014-04-22 20:38:20)
Offline
what version of upower do you have installed? I believe upower should've been updated to the latest version along with GDM and its dependancies, but it wouldn't hurt to check. I know GDM won't start without the correct version.
Offline
I have this:
[2014-04-16 23:20] [PACMAN] upgraded upower (0.9.23-2 -> 0.99.0-2)
Offline
I have the same issue...
Offline
Checking the journalctl -u gdm, the only odd message I see is:
Failed to give slave programs access to the display. Trying to proceed.
Anyone?
Offline
Well, the latest update solved my problem:
Offline
I have the same problem and the system is already updated with 'pacman -Syu'. In another forum it`s written that I could try using startx to start the gnome-session instead of gdm.
Then I used 'systemctl disable gdm' to temporarily switch off gdm
Afterwards I uncommented #exec gnome-session in ./xinitrc and started gnome with startx. Gnome starts correct then. Now I use slim as graphical login manager, waiting for gdm to appear in one of the next system updates.
Offline
I'm not sure my issue is really the same one, but am hoping for some guidance here if possible. Trying to start GDM gives me the same error message/screen. After tdm fails I can switch to a console,
sudo systemctl stop gdm.service
then
sudo systemctl start lightdm.service
and lightdm starts fine. However, trying to log in to gnome-session gives me the very same error as I had with GDM. I can log into XFCE just fine. Attempting to start gnome-ession via startx also gives me the error screen. Does anyone know how I can diagnose the problem? Thanks,
Matt
Offline
hmm, several attempts at pacman -Syu allowed me to update the rest of my system; gnome now starts and hopefully gdm wil las well. Almost there!
Offline
Still not solved for me. I have to start gnome with startx - otherwise I will see the "ohh no ... message"
Offline
Today I installed xf86-video-vesa instead of xf86-video-ati. Now gnome can also be started via gdm as it should be.
So it´s at least running now without the error message "oh no.." and without console "startx..."
Doublecheck: Switching back to the ati-driver runs back into the problem.
Offline
Sorry for my delay (again). I'm downgraded mesa driver and work pretty good. Just the applications that requires specific "opencl" driver don't work with GPU rendering (Blender, for example).
Edit:
OOps! My mistake. This not is my topic.
Last edited by 1retfel (2021-05-16 03:04:09)
Offline
Closing.
Offline
Pages: 1
Topic closed