I went through all the comments and could not find any solution.
Considering that many people have started using ubuntu, requesting you
all to be more precise while posting solutions. everyone is not master
of ubuntu/linux.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: xserver-xorg-video-modesetting (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Title:
Xorg crashed with SIGABRT in
Where's the fun in succesful boots?
Anyhow just append 'and started plymouth-splash' to the start on line in
/etc/init/lightdm.conf, after the 'and started dbus' line.
This should fix the race between plymouth show-splash and lightdm
starting.
--
You received this bug notification because you
Like this?
start on ((filesystem
and runlevel [!06]
and started dbus
and started plymouth-splash
and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
or stopped udev-fallback-graphics))
or runlevel PREVLEVEL=S)
I'm still
If so, this is the Xorg
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1157614/+attachment/3597822/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, it looks like Xorg loading is sane there, so it would appear you
are hitting a different bug. Perhaps backlight related? Can you file a
separate bug against xserver-xorg-video-intel for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Can you boot with plymouth debugging information? Add 'plymouth:debug'
to command line, then attach /var/log/plymouth-debug.log here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-modesetting (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also a new xorg.0.log from 2:1.13.3-0ubuntu3 would be nice if
intiialization still goes wrong. The last log I have is from 2b1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Title:
Xorg
This bug was fixed in the package xserver-xorg-video-nouveau -
1:1.0.6-0ubuntu4
---
xserver-xorg-video-nouveau (1:1.0.6-0ubuntu4) raring; urgency=low
* Clean up (forced) device close (LP: #1157614)
- 102-fixup-close.diff
-- Maarten Lankhorst maarten.lankho...@ubuntu.com Mon,
With the latest updates I have booted by computer 10 times and seen no
crashes.
A few times, however, I see a black screen with just my mouse
Here is xorg and plymouth debug from successful boot
** Attachment added: Xorg.0.log
Plymouth debug
** Attachment added: plymouth-debug.log
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1157614/+attachment/3597278/+files/plymouth-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Most of the time these files came out as 0Bytes. but many retries later
and I have plymouth-debug and Xorg from a boot that goes to black screen
with mouse.
I hope it's helpful
** Attachment added: Xorg.0.log
plymouth-debug
** Attachment added: plymouth-debug.log
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1157614/+attachment/3597350/+files/plymouth-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: xserver-xorg-video-intel (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Title:
Xorg crashed with SIGABRT in WakeupHandler()
To manage notifications about this
** Tags added: crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Title:
Xorg crashed with SIGABRT in WakeupHandler()
To manage notifications about this bug go to:
This bug was fixed in the package xserver-xorg-video-ati -
1:7.1.0-0ubuntu2
---
xserver-xorg-video-ati (1:7.1.0-0ubuntu2) raring; urgency=low
* Fix not removing socket and block handler on close (LP: #1157614)
- fixup-close.patch
* Handle drmModeGetConnector failure better.
This bug was fixed in the package xorg-server - 2:1.13.3-0ubuntu3
---
xorg-server (2:1.13.3-0ubuntu3) raring; urgency=low
* Refresh autoconfig-fixup-tell-changed-so-randr-clients-can-t.patch
- Unbind offload sink and render slave simultaneously.
This prevents a
Still crashes :/
Do you want me to report it as a bug, or can you get all the info you
need from the .crash file?
** Attachment added: _usr_bin_Xorg.0.crash
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1157614/+attachment/3588905/+files/_usr_bin_Xorg.0.crash
--
You received
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1157614/+attachment/3588906/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Oh it is because I'm using nouveau?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Title:
Xorg crashed with SIGABRT in WakeupHandler()
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1050494 ***
https://bugs.launchpad.net/bugs/1050494
This is the Xorg log from that boot
I noticed that sometimes the ubuntu logo would pop up for a moment, then
go to a black screen. And sometimes it would go into low graphics mode.
This is a crash report
*** This bug is a duplicate of bug 1050494 ***
https://bugs.launchpad.net/bugs/1050494
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1050494, so is being marked as such.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Title:
oooh ohhh oohh can you do 'sudo udevadm trigger --action=add
--subsystem-match=drm' ? I bet it breaks! :D
At least this is what I get, anyway..
==2422== Invalid write of size 8
==2422==at 0x161118: AttachOutputGPU (list.h:132)
==2422==by 0x1D9E85: xf86AutoConfigOutputDevice
Does the bug go away if you edit /etc/init/udevtrigger.conf ?
Change
exec udevadm trigger --action=add
to
exec udevadm trigger --action=add --subsystem-nomatch=drm
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
** Changed in: xorg-server
** Also affects: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided
Status: New
--
You
I ran sudo udevadm trigger --action=add --subsystem-match=drm and it
went black and logged me out. On returning I had a crash report, let me
know if you want me to report it (It had the same title as this report)
I edited udevtrigger.conf and it did not fix the bug.
For the first time I have
Maybe not, it's 0bytes in size
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Title:
Xorg crashed with SIGABRT in WakeupHandler()
To manage notifications about this bug go to:
It should probably check if the device is already added, instead of
blindly re-adding. :-)
I understand the drmmode part now.
It goes wrong in 3 places at the moment:
* bugs in xorg-server
- Fix 1: drm_device_keep_trying.patch (pushed to debian git, proposed on
mailing list)
- Fix 2:
** Also affects: xserver-xorg-video-modesetting (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157614
Title:
Xorg crashed with SIGABRT in
Here is the lightdm crash. I notice is says I have the 'sleep 5' applied
to lightdm.conf, so I guess this means it crashed when I was booting in
successfully as thats the work around I use to login.
Is it to do with the edit I made to udevtrigger?
I can't report it as I have an obsolete package
here is also the crash report from when the ubuntu logo pops up for a
split second and then it just goes black: bug 1157819
(with your that edit to udevtrigger applied)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
34 matches
Mail list logo
