I have a Lenovo Z-series laptop with an A10 Kaveri chipset that I am trying to get to work with LEAP. I have done a clean install of LEAP, coming from Ubuntu 14.04. After the install starting from first boot I get the Oh No!! error screen, IceWM works as does KDE when I did a clean install but when I attempt to use Gnome I get this error screen. I am not sure what is going on, I thought it might be a driver issue due to me having some issues with the open source AMD driver and Unity so after some research I activated lightdm and installed the proprietary driver but still no change.
So I am wondering a few things:
Am I missing some steps switching over to lightdm and fglrx?
Is there something I need to do to make the AMD open source driver work with gdm or Gnome?
Is there something else I am missing that is an easy fix for this issue?
I do not want to use KDE at all, I really don’t like it. I am open to Enlightment DE but really do prefer Gnome. So any troubleshooting help would be greatly appreciated.
On Tue, 10 Nov 2015 17:26:01 +0000, ragnarokxg wrote:
> I have a Lenovo Z-series laptop with an A10 Kaveri chipset that I am
> trying to get to work with LEAP. I have done a clean install of LEAP,
> coming from Ubuntu 14.04. After the install starting from first boot I
> get the Oh No!! error screen, IceWM works as does KDE when I did a clean
> install but when I attempt to use Gnome I get this error screen. I am
> not sure what is going on, I thought it might be a driver issue due to
> me having some issues with the open source AMD driver and Unity so after
> some research I activated lightdm and installed the proprietary driver
> but still no change.
>
> So I am wondering a few things:
>
>
>
> - Am I missing some steps switching over to lightdm and fglrx?
> - Is there something I need to do to make the AMD open source driver
> work with gdm or Gnome?
> - Is there something else I am missing that is an easy fix for this
> issue?
>
>
> I do not want to use KDE at all, I really don’t like it. I am open to
> Enlightment DE but really do prefer Gnome. So any troubleshooting help
> would be greatly appreciated.
First thing to do in troubleshooting stuff like this is to disable all
plugins (that should happen by default after it errors, but it may not).
Usually the Oh No error screen is a result of a poorly written extension
or just something that errors out. It’s the one thing about GNOME I
wish there was more info about - how to troubleshoot/fix these problems -
the lack of info in the error is a real problem for me.
I have found the same situation happening to me on multiple computers, after the initial installation. What seems to get me out of the problem is pressing Ctrl + Alt + F1 to get to TTY, then login as root and perform a system update with
That is one of the issues I am having here, because I am unable to actually do anything in the DE. All it allows me to do is log out. Everything pretty much works in IceWM and KDE which really confused me. And knowing that gdm doesn’t play nice with the proprietary drivers that kind of took away one fix I did know so I am at a loss.
Looking at the Xorg log files also doesn’t have anything that just jumps up at me as an error which is what also confounds me.
On Tue, 10 Nov 2015 19:46:02 +0000, ragnarokxg wrote:
> That is one of the issues I am having here, because I am unable to
> actually do anything in the DE. All it allows me to do is log out.
> Everything pretty much works in IceWM and KDE which really confused me.
> And knowing that gdm doesn’t play nice with the proprietary drivers that
> kind of took away one fix I did know so I am at a loss.
Maybe try creating a new user and see if it runs from a clean home
directory. If this was an upgrade, it’s possible there’s something in
the earlier release’s config that’s causing a problem.
