Today after I made a system update and then a reboot, gdm froze at it's very start - I see only a black screen after the standard systemd loading that is. I can switch to a tty console and operate from there though. I've spend a couple of hours trying to identify the issue alone though I was unsuccessful.
I've noticed that today's updates were related to gnome - that's why I think it's gdm. Any clues on how to find what's the problem and/or how to solve it?
If it's helpful I'm using a Lenovo Y560, the version with core i3 and a switchable graphics (turned off), with the latest catalyst driver.
Last edited by SnowyMan95 (2013-05-14 21:42:12)
Well, had the same issue here. I think Mutter is the cause, but I downgraded most parts of Gnome 3.8.2.
pacman -U /var/cache/pacman/pkg/mutter*
If that doesn't solve the issue, downgrade gnome-shell and gnome-session as well.
Last edited by Shinto (2013-05-14 17:51:23)
Same problem here. The error is :
(gnome-shell:634): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed (gnome-shell:634): Clutter-CRITICAL **: Unable to initialize Clutter: The OpenGL version could not be determined
Downgrade gnome-shell "solves" the problem, but totem 3.8.2 has the same problem :
(totem:1592): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed (totem:1592): Clutter-CRITICAL **: Unable to initialize Clutter: The OpenGL version could not be determined (totem:1592): Totem-WARNING **: gtk-clutter failed to initialise, expect problems from here on. (totem:1592): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed (totem:1592): Clutter-CRITICAL **: Unable to initialize Clutter: The OpenGL version could not be determined Erreur de segmentation (core dumped)
Downgrade totem "solves" it, too.
I use the catalyst driver.
Last edited by mirandir (2013-05-14 18:10:34)
I have exactly same problem in my desktop computer as midardir explains. It seems to be something related to Clutter. Any hints?
Okay, basically I downgraded the packages and everything works fine now, hopefully the new ones will be patched soon so I can update. I don't know why didn't I think of that myself, dumb me ^^ Thank you very much then ツ
Thanks to all of you. Downgrading gnome-shell and totem "solves" the problem in the meantime.
P.S. I use catalyst too.
Last edited by Dysk (2013-05-14 23:16:09)
If life is going to exist in a Universe of this size, then the one thing it cannot afford to have is a sense of proportion.
Same problem here using catalyst. Anyone reported the bug?
As I looked at the bugtracer - it's still not reported. You're free to do so if you want, since I don't really know what to write there nor do I have the account.
Bug reported at: https://bugs.archlinux.org/task/35310
Please comment on the report and provide more information please
I don't really know what I'm doing.
Same problem here, but this method not works for me.
I've downgraded gnome-shell and totem, but gnome still not works.
Maybe because i have to use Xorg1.12 for my Catalyst driver (Legacy driver) and this method works all for Xorg1.13.
I tried to switch in open driver (Radeon) and last release of Xorg1.14 and all works fine but the known issue of FAN for open driver is tedious!
Now i' m using xfce4 and slim as display manager.
Last edited by Angelsoul (2013-05-16 09:37:13)
--------------------- Laptop -----------------------
ArchLinux 64bit on DELL XPS 15
Well that is SO off-topic... but,
at the moment, I'm totally annoyed of Arch.
I'm using it on my two machines, one Intel/Nvidia and one with AMD/AMD and both systems are getting more and more unstable.
I understand that I'm not using Debian stable. And I don't want to. But for a couple of months I wish Arch would be a little more reliable. I WANT a rolling release distro, but I dont want to struggle every 2 or so updates with downgrading and withholding packages, spending 1 hour+ fixing things, reading forums and filing/commenting on bugs.
Is this just me, maybe because my installations are from like 2 years ago and i should start from scratch (which seems totally odd for me for linux)? Or has my point of view changed and I'm just getting old and pragmatic?
I don't like Ubuntu with its backports, ppa's and unity and mir and and and and... but I'm close to switch back to that .
Old and pragmatic? Might be true xd
For me it's the first real issue that appeared for about... hmm I don't remember, it was last year though. If you are speaking of those small changes like when /lib was being replaced with a symlink, it's just the matter of checking forum and doing a few things to make it work, not much of a bother. I think it's a good thing that the developers relay on users with doing some things that programs couldn't. It allows Arch to stay a very simple distro, the only minus (or plus, depends) is that people need some knowledge and time to actually use it. But I think it's worth the effort.
Last edited by SnowyMan95 (2013-05-17 06:42:33)
Hi! Same problem here, did a fresh install and surprisingly couldn't use gnome with catalyst. Found this thread, would like to solve this Problem cause I'm sitting infront of a really slow acting machine in combination with open source driver, but I don't have needed packeges for the downgrade. Can somone create a link to x64 ones?
Has anone gotten anything resolved for this issue? I am experiencing something similar where I get the "Oops! Something has gone wrong!" message, resulting in gdm crashing, when trying to load gdm with gnome-shell-3.8.2-2. This has forced me to remain on gnome-shell-3.8.1-1 for three weeks. Additionally, I have the AMD Catalyst proprietary drivers installed: gnomecatalyst-13.4-3, along with xorg 1.13.
Last edited by brom (2013-05-24 04:50:57)
I think I read somewhere that their are problems with the proprietary ati driver and gnome, try the open driver?
Proprietary AMD drivers make everything difficult; I have not had any success with the AMD open source driver in the past so I have been avoiding it. For the meantime, I guess I will simply remain on gnome-shell-3.8.1-1. On my other machine, I am using Intel HD graphics, where I am able to run the latest gnome-shell and xorg without a problem. Good to see it is a known bug though.
Problem can be solved by adding this custom repository to your pacman.conf file. This will allow you to upgrade to gnome-shell-3.8.2-3 without gdm breaking; gnome-shell-calendar-server is also working now as well.
[gnome-catalyst] Server = http://catalyst.wirephire.com/repo/gnome-catalyst/$arch