** Description changed:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
+ https://errors.ubuntu.com/problem/f32979eb9251bc31b3b1460dc3a27b4fc2d48007
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core
** Tags removed: artful eoan groovy yakkety zesty
--
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() from AbortServer() from
FatalError("no screens
OK, clarified somewhat now. This bug is back to being about just "no
screens found".
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found")
I think this is the wrong bug for all of those duplicates. There's no
evidence of either of those messages here. I'll see if I can split this
into other bugs...
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n") f
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found") from dix_main()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from
WakeupHandler()
--
You
It seems like I get this crash only when I am typing in VS Code. I
found this post in Stack Overflow which suggest disabling GPU
acceleration in VS Code. I've made this configuration change to VS Code
and so far no more crashes.
https://stackoverflow.com/questions/29966747/how-can-i-disable-gpu-
I tried the steps that Daniel suggested -- apt full-update and
verification of xorg-server version. No change. I am still getting
random crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543192
Please update your 20.04 systems:
sudo apt update
sudo apt full-upgrade
Reboot.
and make sure you have
xorg-server 2:1.20.8-2ubuntu2.1
Although that is for bug 1879893, it might help some people here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Tags added: groovy
--
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() from AbortServer() from
FatalError("no screens found") from dix_main()
To
** Description changed:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
+ https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core
** Tags added: focal
--
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() from AbortServer() from
FatalError("no screens found") from dix_main()
To
** Changed in: xorg-server (Ubuntu)
Assignee: zulhisman (zoelagare) => (unassigned)
--
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() from Abor
me_problem
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) => zulhisman (zoelagare)
--
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
** Tags added: eoan
--
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() from AbortServer() from
FatalError("no screens found") from dix_main()
To m
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main() ["no screens found"]
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found") from dix_main()
--
You received this bug notification because y
Apparently, I am able to reproduce this quite easily with Xubuntu 18.04
as seen in bug #1815429 . The workaround which works for me is to add
the ppa:xubuntu-dev/experimental and upgrade xfwm4 to version 4.13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
At least some of my issue was triggered by a yet unfixed NIS/systemd
bug. systemd-logind would hang (and watchdog kicks in) if it tried to
contact the NIS service because of a new IP firewall they implemented.
I don't think this was entirely all of my problems but it certainly
confused the issue.
Just to close the loop on this, it seems that my problem was a corrupted
dist-upgrade and reinstalling a fresh Xubuntu 18.04 fixed it.
--
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:
Xo
That file (/etc/gdm3/custom.conf) doesn't exist on my system. I haven't
been getting the popup for an error occurring today though. (The
details in that dialog said it was a duplicate of this issue, which is
how I found this)
I still have an issue where if I lock the screen it goes black with a
Shawn can you check /etc/gdm3/custom.conf and make sure wayland isn't
disabled?
--
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() from AbortServer()
I just updated to Xubuntu 18.04 (from 17.10) and I have started getting
this when I log in.
--
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() from A
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238?comments=all
I ran into the no screens bug. Logging in resulted in a black screen for
many minutes after which the login screen reappeared and I am able to
login fine. A systemd watchdog kicks in during the many minutes to
restart systemd
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() ["no screens found"]
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main() ["no screens found"]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
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 notific
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.
https://bugs.launchpad.net/bugs
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. Agre
** 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:
https://
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.
htt
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 'wake
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 Ubun
** 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:
https://
** 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
DistroRel
It happens to me every time I unlock my session
--
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()
To manage notifications about this bug go to:
htt
Crash occurred while running benchmark inside Dirt Rally (xubuntu 17.04
Beta 1).
Description:Ubuntu Zesty Zapus (development branch)
Release:17.04
xserver-xorg-core:
Installed: 2:1.18.4-1ubuntu9
Candidate: 2:1.18.4-1ubuntu9
Version table:
*** 2:1.18.4-1ubuntu9 500
500 h
** Tags added: zesty
--
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()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
miked@free-yak:~$ lsb_release -rd
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
miked@free-yak:~$ apt-cache policy xserver-xorg-core
xserver-xorg-core:
Installed: 2:1.18.4-1ubuntu6
Candidate: 2:1.18.4-1ubuntu6
Version table:
*** 2:1.18.4-1ubuntu6 500
** Tags added: yakkety
--
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()
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
** Tags added: bugpattern-needed
--
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()
To manage notifications about this bug go to:
https://bugs.launc
Just got the bug 2016-3-29 fresh install today from xenial-desktop-amd64.iso
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development branch)"
Linux Lenovo2 4.4.0-16-generic #32-Ubuntu SMP Thu Mar 24 22:38:01 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
model
Still an issue when trying to log into the unity8 desktop session.
** Information type changed from Private to Public
--
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
40 matches
Mail list logo
