You are not logged in.
Hey there,
yesterday, I updated, among other things, the kernel and gnome-shell. Gnome-shell is now on version 3.10.2-1
Since then, every time I try to startx with gnome-session enabled in .xinitrc, I just get this screen:
http://i.imgur.com/c4IxcBv.jpg
I would have taken a screenshot, but you know... I can't.
Any help is greatly appreciated. Thanks!
P.S. I did some googling but couldn't really find anything useful. A while ago someone posted here with the same problem, but there were no replies to the thread.
I'm using i3 right now, but I'll probably reboot, try to start gnome, and then run dmesg to see if that turns up anything. I'll post the results.
EDIT: Alright, I switched from Slim to GDM as my login manager and now it works fine. It seems to have been a Slim-related problem. I really don't know why, but yeah. If anyone had the same problem: try using GDM instead of whatever it is you're using now.
I might try to fix whatever was wrong with Slim, if I find the time, and post it here. Cheers!
Last edited by Lonje (2013-11-22 10:17:40)
Offline
I had that same problem last night after upgrading to gnome-shell-3.10.2
downgrading to 3.10.1 solves the issue
I'm not using any login manager, but simply start gnome-session with startx, so I don't think this is related to slim.
I'm gonna do some diagnostics when I have time and figure out what's going on
Offline
I had that same problem last night after upgrading to gnome-shell-3.10.2
downgrading to 3.10.1 solves the issueI'm not using any login manager, but simply start gnome-session with startx, so I don't think this is related to slim.
Me neither. If gnome-shell 3.10.2 is the culprit, I hope there'll be a fix soon. In the mean time, I won't log out this current gnome shell.
Offline
apparently theres gnome-shell-3.10.2.1 now but that didn't seem to solve the issue.
I checked journalctl and apparently it gets flooded with this message when I try to start gnome shell >=3.10.2
(gnome-shell:6161): St-CRITICAL **: st_border_image_get_filename: assertion 'ST_IS_BORDER_IMAGE (image)' failedgoogle didn't return any results for that error..
@Lonje could you possibly remove the [SOLVED] from topic title since the problem seems to persist?
Offline
apparently theres gnome-shell-3.10.2.1 now but that didn't seem to solve the issue.
I second that.
Offline
can confirm. using alternative login managers or startx is broken. gdm works.
Tho it didnt crash here. it just froze.
Last edited by Rasi (2013-11-16 11:09:43)
He hoped and prayed that there wasn't an afterlife. Then he realized there was a contradiction involved here and merely hoped that there wasn't an afterlife.
Douglas Adams
Offline
Just a quick reminder that this is not yet solved.
Offline
Removed the Solved tag. Sorry I didn't do it sooner.
Offline
This is the first time I've posted to this thread but I've been following it from the beginning.
I'm using lightdm and everything was working fine until I upgraded gnome-shell-3.10.1-1 to gnome-shell-3.10.2-1. After logging back in I got the infamous "Something has gone wrong" screen. Downgrading gnome-shell back to 3.10.1-1 immediately fixed the problem. Soon after I upgraded to gnome-shell-3.10.2.1-1 on Nov 15 and the problem came back, again fixed by downgrading. Today Dec 4 another upgrade, this time to gnome-shell-3.10.2.1-2, and still the same thing. Three released versions of gnome-shell-3.10.2 and this problem persists? Are the developers even aware of this?
Offline
Three released versions of gnome-shell-3.10.2 and this problem persists? Are the developers even aware of this?
I don't know much about how these things work. The fact that the problem is still there after 3 released versions of gnome-shell makes me think it's gnome-shell-extension-related. Maybe we, who have this problem, are using some particular gnome-shell extensions. I'm using this one (the latest code from github).
Offline
I'm pretty sure it's not related to any extensions since gnome disables every extension when it fails to start, and still fails if you try after that.
I have nothing but user styles extension enabled anyway.
Offline
okay, did some digging. this seems kinda silly but simply installing gdm solves the issue for me
gnome-shell 3.10.2* apparently failed because it couldn't find the org.gnome.login-screen schema, which is provided by gdm.
If this works for others I'll put a bug report out to add gdm as dependency for gnome-shell
Last edited by ooo (2013-12-05 05:52:12)
Offline
okay, did some digging. this seems kinda silly but simply installing gdm solves the issue for me
I can confirm that even though I don't use gdm to login but use startx from the command line.
Offline
The problem has finally been fixed.
I opened a bug report for gnome-shell, and after supplying copies of my system journal after a failed gnome-shell 3.10.2* login, developer Jan Steffens found the problem was in libgdm. He then released an updated copy of libgdm, version 3.10.0.1-2.
extra/libgdm 3.10.0.1-2 [installed]
GDM support library
extra/gnome-shell 3.10.2.1-2 (gnome) [installed]
The next generation GNOME Shell
ooo was partly right in pointing out that the problem seemed related to gdm, however the full gdm itself is not actually required for gnome-shell to work and should not be.
Those that do not use gdm and do not even want it installed on their systems can instead simply install or update libgdm. The full version of gdm-3.10.0.1-2 will of course also work.
Good work Jan, and many thanks.
Last edited by polaris6262 (2013-12-06 02:03:11)
Offline