[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2018-02-15 Thread M Grmn
Might not be helpful. I edited my radeon.conf (which had "Detail") so I removed that. Plus I had to chown {user}:{user} .Xauthority to be able to login (otherwise it would just kick me back to login screen) It helpt me logging in, but ofcourse not as it should. -- You received this bug

[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2018-02-15 Thread Joao Paulo Carvalho
It happens to me to. Usually, when I click (with mouse) at some panel element (calendar, configuration icon etc.). I've a Dell Notebook with NVidia on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2018-02-14 Thread Mdm Wm
Hardware: NVidia GeForce GTX 850M/PCIe/SSE2 Intel® Core™ i7-5500U CPU @ 2.40GHz × 4 Steps to reproduce on Bionic (18.04 dev) 1. Install normal (Gnome desktop on wayland) 2. Install xubuntu-desktop 3. At some point the installation will ask for changing display manager to lightdm.

[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2018-02-09 Thread Apport retracing service
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543192 Title: Xorg crashed with SIGABRT in OsAbort() ["no screens found"] To manage notifications about this bug go to:

[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2017-10-31 Thread Robert Baumgartner
I'm getting this in 16.04 very frequently as well. If you want my system info as well, or if I can help debug in some other way let me know and I will be happy to help get this fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2017-10-25 Thread kerryland
Happened to me in 17.10. Like @fcole90 seemed to happen after unlocking my session after unsuspending my machine in the morning. The unlocking itself seemed to be stuck displaying some message about letting me continue in a few moments, but it never did. I used ctrl-alt-f6 then crtl-alt-f7 to

[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2017-07-15 Thread Francis Poulin
I am having the same problem in my new Dell XPS 15, every time I boot up (16.04). Is there any one who might have some advice on how we can fix this? Any help would be greatly appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2017-06-25 Thread Apport retracing service
** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543192 Title: Xorg crashed with SIGABRT in OsAbort() ["no screens found"] To manage notifications about this bug go to:

[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

2017-05-29 Thread Daniel van Vugt
** Summary changed: - Xorg crashed with SIGABRT in OsAbort() + Xorg crashed with SIGABRT in OsAbort() ["no screens found"] ** Description changed: + https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530 + + --- + No idea what happened. ProblemType: Crash