Attachment 125096 Details for Bug 96951 – the assert

the assert

nohup.out.txt (text/plain), 1.51 KB, created by Tod Jackson on 2016-07-16 00:09:19 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Tod Jackson

Created: 2016-07-16 00:09:19 UTC

Size: 1.51 KB

patch

obsolete

>
>
>This is a pre-release version of the X server from The X.Org Foundation.
>It is not supported in any way.
>Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
>Select the "xorg" product for bugs you find in this release.
>Before reporting bugs in pre-release versions please check the
>latest version in the X.Org Foundation git repository.
>See http://wiki.x.org/wiki/GitPage for git access instructions.
>
>X.Org X Server 1.18.99.1
>Release Date: 2015-11-09
>X Protocol Version 11, Revision 0
>Build Operating System: Linux 4.6.4 x86_64 Gentoo
>Current Operating System: Linux Fortune 4.6.4 #1 SMP PREEMPT Fri Jul 15 15:01:41 MST 2016 x86_64
>Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.6.4 root=/dev/sda1 ro init=/usr/lib/systemd/systemd loglevel=3
>Build Date: 15 July 2016  02:32:50PM
> 
>Current version of pixman: 0.34.0
>	Before reporting problems, check http://wiki.x.org
>	to make sure that you have the latest version.
>Markers: (--) probed, (**) from config file, (==) default setting,
>	(++) from command line, (!!) notice, (II) informational,
>	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>(==) Log file: "/var/log/Xorg.2.log", Time: Fri Jul 15 16:46:11 2016
>(==) Using config directory: "/etc/X11/xorg.conf.d"
>(==) Using system config directory "/usr/share/X11/xorg.conf.d"
>xinit: connection to X server lost
>
>waiting for X server to shut down X: /var/tmp/portage/x11-base/xorg-server-9999/work/xorg-server-9999/present/present_screen.c:95: present_clear_window_flip: Assertion `flip_pending->abort_flip' failed.
>

Actions: View

Attachments on bug 96951: 125094 | 125095 | 125096 | 125357 | 125359 | 125390 | 125402 | 125416 | 125423 | 125477

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.