Thanks, I can confirm that rolling back to xserver-xorg-core 2:1.19.6-1
fixes the problem for me for now.

On Sun, Aug 5, 2018 at 3:55 PM Sven Joachim <svenj...@gmx.de> wrote:

> Control: reassign -1 xserver-xorg-core
> Control: forcemerge 900550 -1
>
> On 2018-08-05 15:43 -0400, Eric Cooper wrote:
>
> > Package: xserver-xorg-video-nouveau
> > Version: 1:1.0.15-3
> > Severity: important
> >
> > I did an "apt-get upgrade" today that installed new
> > xserver-xorg-{core,nouveau} packages. Now X does not start on my system.
> > The same segmentation fault occurs every time I run "startx".
> > [...]
> > [   301.726] (EE)
> > [   301.726] (EE) Backtrace:
> > [   301.726] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d)
> [0x56123945b8dd]
> > [   301.726] (EE) 1: /usr/lib/xorg/Xorg (0x5612392a8000+0x1b7599)
> [0x56123945f599]
> > [   301.726] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7f1b1ca80000+0x128e0) [0x7f1b1ca928e0]
> > [   301.726] (EE) 3: /usr/lib/xorg/Xorg (miRenderColorToPixel+0xe)
> [0x5612393cfbde]
> > [   301.726] (EE) 4: /usr/lib/xorg/modules/libexa.so
> (0x7f1b19a8d000+0xf13b) [0x7f1b19a9c13b]
> > [   301.726] (EE) 5: /usr/lib/xorg/Xorg (0x5612392a8000+0x13a8b6)
> [0x5612393e28b6]
> > [   301.726] (EE) 6: /usr/lib/xorg/Xorg (0x5612392a8000+0x12ec1c)
> [0x5612393d6c1c]
> > [   301.726] (EE) 7: /usr/lib/xorg/Xorg (0x5612392a8000+0x5b008)
> [0x561239303008]
> > [   301.726] (EE) 8: /usr/lib/xorg/Xorg (0x5612392a8000+0x5f008)
> [0x561239307008]
> > [   301.726] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6
> (__libc_start_main+0xe7) [0x7f1b1c8e5b17]
> > [   301.727] (EE) 10: /usr/lib/xorg/Xorg (_start+0x2a) [0x5612392f0d0a]
> > [   301.727] (EE)
> > [   301.727] (EE) Segmentation fault at address 0x8
> > [   301.727] (EE)
> > Fatal server error:
> > [   301.727] (EE) Caught signal 11 (Segmentation fault). Server aborting
>
> This is bug #900550 in xserver-xorg-core, a fix is pending in git[1].
>
> Cheers,
>        Sven
>
>
> 1.
> https://salsa.debian.org/xorg-team/xserver/xorg-server/commit/aa7aaeb5223830a3670dc658152e28f125c17de8
>

Reply via email to