Re: Refresh the xserver-xorg-video-openchrome package

[Dylan]

Hi Andreas,

2017-01-11 20:04 GMT+01:00 Andreas Boll :
> I noticed that this commit [1] missed an entry in the
> debian/patches/series file.
> Thus the patch "Reproducible_build.patch" won't be applied during the build.
> Could you add that missing entry?
> Otherwise the updated package looks good to me.

Thanks for pointing this mistake. :-)
It's corrected now.

Best regards,
Dylan

xserver-xorg-video-openchrome: Changes to 'debian-unstable'

[Dylan Aïssi]

 debian/changelog|1 +
 debian/patches/Reproducible_build.patch |6 +++---
 debian/patches/series   |1 +
 3 files changed, 5 insertions(+), 3 deletions(-)

New commits:
commit bba375afef712603b2191cc8275f78edf07bd4ec
Author: Dylan Aïssi 
Date:   Wed Jan 11 23:36:10 2017 +0100

Really apply the patch Reproducible_build.patch

diff --git a/debian/changelog b/debian/changelog
index 0b9678f..f7e0e00 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,7 @@ xserver-xorg-video-openchrome (1:0.5.0-2) UNRELEASED; 
urgency=medium
   * Fix FTBFS on Hurd:
  - Exclude libdrm-dev from Build-Depend for Hurd-any instead only i386.
  - Add a condition (!hurd) into dh_install target for libchromeXvMC*.
+  * Really apply the patch Reproducible_build.patch.
 
  -- Dylan Aïssi   Wed, 14 Dec 2016 22:47:09 +0100
 
diff --git a/debian/patches/Reproducible_build.patch 
b/debian/patches/Reproducible_build.patch
index a816710..5ab9dca 100644
--- a/debian/patches/Reproducible_build.patch
+++ b/debian/patches/Reproducible_build.patch
@@ -3,9 +3,9 @@ Description: Make the build reproducible.
 Origin: https://bugs.debian.org/831405
 Applied-Upstream: 0.5.173, 
https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=25ba0a4
 
 a/src/Makefile.am  2016-07-15 17:56:15.066700891 +0200
 b/src/Makefile.am  2016-07-15 18:22:08.362042386 +0200
-@@ -113,6 +113,9 @@
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -112,6 +112,9 @@
  if [ -d .svn ]; then \
echo '#define BUILDCOMMENT "(development build, at revision '\
"`svnversion -nc .. | sed -e s/^[^:]*://`"')"' > 
$@.tmp; \
diff --git a/debian/patches/series b/debian/patches/series
index b234234..e312057 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 Fix_spelling_error.patch
+Reproducible_build.patch

Bug#742448: xserver-xorg-core: using PRIME causes xorg to crash

[Alexander Kudrevatykh]

Hi, I can't check it because now I didn't have hardware with prime support
--
Alexander Kudrevatykh

11 января 2017 г. 22:42:25 GMT+03:00, Andreas Boll  
пишет:
>Control: tag -1 moreinfo
>
>On Mon, Mar 24, 2014 at 12:01:15AM +0400, Alexander Kudrevatykh wrote:
>> Package: xserver-xorg-core
>> Version: 2:1.15.0-2
>> Severity: normal
>> 
>> output of xrandr --listproviders
>> 
>> Providers: number : 2
>> Provider 0: id: 0x68 cap: 0xb, Source Output, Sink Output, Sink
>Offload crtcs:
>> 3 outputs: 4 associated providers: 0 name:Intel
>> Provider 1: id: 0x41 cap: 0xf, Source Output, Sink Output, Source
>Offload, Sink
>> Offload crtcs: 2 outputs: 0 associated providers: 0 name:radeon
>> 
>> after
>> xrandr --setprovideroffloadsink 0x41 0x68
>> DRI_PRIME=1 glxinfo
>> causes xorg to crash log of crash attached
>> 
>> 
>
>Hi,
>
>is this still an issue with a newer xserver-xorg-core version (e.g.
>the version from jessie or preferably from stretch/sid)?
>
>Thanks,
>Andreas


signature.asc
Description: PGP signature

Processed: reassign 848960 to xserver-xorg-core

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 848960 xserver-xorg-core 2:1.19.0-2
Bug #848960 [xserver-xorg] xserver-xorg segfaults after starting afterstep
Bug reassigned from package 'xserver-xorg' to 'xserver-xorg-core'.
No longer marked as found in versions xorg/1:7.7+18.
Ignoring request to alter fixed versions of bug #848960 to the same values 
previously set
Bug #848960 [xserver-xorg-core] xserver-xorg segfaults after starting afterstep
Marked as found in versions xorg-server/2:1.19.0-2.
> tags 848960 moreinfo
Bug #848960 [xserver-xorg-core] xserver-xorg segfaults after starting afterstep
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
848960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 850472, tagging 850083

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 850472 + moreinfo
Bug #850472 [libgl1-mesa-dev] missing libGL.so broken link
Added tag(s) moreinfo.
> tags 850083 + moreinfo
Bug #850083 [libgl1-mesa-glx] libgl1-mesa-glx: Driver radeonsi_dri not in 
expected directory /usr/lib32/dri/tls/
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
850083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850083
850472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#742448: xserver-xorg-core: using PRIME causes xorg to crash

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #742448 [xserver-xorg-core] xserver-xorg-core: using PRIME causes xorg to 
crash
Ignoring request to alter tags of bug #742448 to the same tags previously set

-- 
742448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#742448: xserver-xorg-core: using PRIME causes xorg to crash

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #742448 [xserver-xorg-core] xserver-xorg-core: using PRIME causes xorg to 
crash
Added tag(s) moreinfo.

-- 
742448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#742448: xserver-xorg-core: using PRIME causes xorg to crash

[Andreas Boll]

Control: tag -1 moreinfo

On Mon, Mar 24, 2014 at 12:01:15AM +0400, Alexander Kudrevatykh wrote:
> Package: xserver-xorg-core
> Version: 2:1.15.0-2
> Severity: normal
> 
> output of xrandr --listproviders
> 
> Providers: number : 2
> Provider 0: id: 0x68 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs:
> 3 outputs: 4 associated providers: 0 name:Intel
> Provider 1: id: 0x41 cap: 0xf, Source Output, Sink Output, Source Offload, 
> Sink
> Offload crtcs: 2 outputs: 0 associated providers: 0 name:radeon
> 
> after
> xrandr --setprovideroffloadsink 0x41 0x68
> DRI_PRIME=1 glxinfo
> causes xorg to crash log of crash attached
> 
> 

Hi,

is this still an issue with a newer xserver-xorg-core version (e.g.
the version from jessie or preferably from stretch/sid)?

Thanks,
Andreas


signature.asc
Description: Digital signature

Re: Refresh the xserver-xorg-video-openchrome package

[Andreas Boll]

Hi Dylan,

I noticed that this commit [1] missed an entry in the
debian/patches/series file.
Thus the patch "Reproducible_build.patch" won't be applied during the build.
Could you add that missing entry?
Otherwise the updated package looks good to me.

Thanks,
Andreas

[1] 
https://anonscm.debian.org/cgit/pkg-xorg/driver/xserver-xorg-video-openchrome.git/commit/?id=e9f91e4b742035b3b9989f195497d0c27b38c291

2017-01-10 11:49 GMT+01:00 Dylan :
> Hi,
> Could someone upload the package to unstable?
> I have updated the package to fix the FTBFS on Hurd.
>
> Thanks.
>
> Best regards,
> Dylan
>

Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty

[Agustin Martin]

On Tue, Oct 04, 2016 at 11:43:07AM +0200, Agustin Martin wrote:
> On Wed, Sep 07, 2016 at 12:08:15PM +0200, Agustin Martin wrote:
> > On Wed, Jan 27, 2016 at 03:51:22PM +0100, Agustin Martin wrote:
> > > On Wed, Jan 27, 2016 at 08:29:21AM +0100, Julien Cristau wrote:
> > > > On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote:
> > > > 
> > > > > Package: xserver-xorg-core
> > > > > Version: 2:1.17.3-2
> > > > > Severity: normal
> > > > > 
> > > > > Dear Maintainers,
> > > > > 
> > > > > I am having a strange problem apparently starting with 2:1.17.2-3.
> > > > > 
> > > > > I often have a display-manager controlled X session for one user and 
> > > > > open
> > > > > another X session in a free tty for a different user with startx.
> > > > > 
> > > > > This has been working for a long time. However, after a recent testing
> > > > > upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail
> > > > > (failure happened before in a sid box, but there were more upgrades to
> > > > > look when trying to locate which change might be responsible).
> > > > > 
> > > > > When I have a display-mamager controlled X session and, without 
> > > > > leaving the
> > > > > session, switch to a free tty, login as another user and start an X 
> > > > > session
> > > > > with startx original X session gets killed and I am sent to DM 
> > > > > greeter.
> > > > > 
> > > > Please provide the log from both X processes.
> > > 
> > > Hi, thanks for quick reply.
> > > 
> > > Please find them attached.
> > 
> > Hi,
> > 
> > Just to add some additional info. This problem is happening not only with
> > the xserver-xorg-video-nouveau driver, but also if I remove it leaving the 
> > fbdev
> > or vesa drivers.

Hi, some funny info about this problem,

I am using a sysvinit box and it is currently suffering from

https://bugs.debian.org/844785 [systemd-shim not fully compatible with systemd 
232]

and similar bugs against lightdm

#770885 lightdm: Restart, Suspend, Hibernate, Shut Down all greyed out and 
nonfunctional
#804165 lightdm: Options reboot,suspend,hibernate are all greyed out

The funny thing is that as soon as this systemd-shim bug reappeared my
original problem reported in this bug #812791 report become no longer present
when using "sysvinit"+"buggy systemd-shim".

I have booted with systemd to see what happens and my original problem
reappeared, cannot switch.

So, this may be related to interaction with policykit or friends, but apart
from that guess I am clueless.

Regards,

-- 
Agustin

Bug#786504: marked as done (xorg-server: Assertion `temp_priv->type != GLAMOR_TEXTURE_LARGE' failed.)

[Debian Bug Tracking System]

Your message dated Wed, 11 Jan 2017 19:43:48 +0100
with message-id <2017084347.GA27337@localhost.localdomain>
and subject line Re: Bug#786504: xorg-server: Assertion `temp_priv->type != 
GLAMOR_TEXTURE_LARGE' failed.
has caused the Debian Bug report #786504,
regarding xorg-server: Assertion `temp_priv->type != GLAMOR_TEXTURE_LARGE' 
failed.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
786504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xorg-server
Version: 2:1.16.4-1
Severity: normal

Dear Maintainer,


using iceweasel, going to http://lcamtuf.coredump.cx/afl/demo/ then pressing
the first "click here" link which points to:
http://lcamtuf.coredump.cx/afl/demo/jpeg/full/
these are some example inputs from the afl fuzzer.
instead of displaying, the screen went black and i was logged out. the gdm
login screen was shown.

~/.xsession-errors contains nothing particular.

however, /var/log messages contains these interesting lines:

(snip. lots of these similar jpeg error messages)
May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 5
extraneous bytes before marker 0xa1
May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 8
extraneous bytes before marker 0xc4
May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 1
extraneous bytes before marker 0xe0
May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 4
extraneous bytes before marker 0xc4
May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 8
extraneous bytes before marker 0xc4
May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 16
extraneous bytes before marker 0xc4
May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Invalid SOS parameters for
sequential JPEG
May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 16
extraneous bytes before marker 0xc4
May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: bad
Huffman code
May 22 12:35:14 tonfisk gdm-Xorg-:1[27988]: Xorg:
.../../glamor/glamor_largepixmap.c:787: glamor_merge_clipped_regions: Assertion
`temp_priv->type != GLAMOR_TEXTURE_LARGE' failed.
May 22 12:35:14 tonfisk kernel: [60039.502124] switching from power state:
May 22 12:35:14 tonfisk kernel: [60039.502126]  ui class: performance
May 22 12:35:14 tonfisk kernel: [60039.502127]  internal class: none
(snip. gdm-Xorg restarts)


I do not know if this may be related:
https://bugs.freedesktop.org/show_bug.cgi?id=87866



-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Fri, May 22, 2015 at 01:13:50PM +0200, Paul Dreik wrote:
> Source: xorg-server
> Version: 2:1.16.4-1
> Severity: normal
> 
> Dear Maintainer,
> 
> 
> using iceweasel, going to http://lcamtuf.coredump.cx/afl/demo/ then pressing
> the first "click here" link which points to:
> http://lcamtuf.coredump.cx/afl/demo/jpeg/full/
> these are some example inputs from the afl fuzzer.
> instead of displaying, the screen went black and i was logged out. the gdm
> login screen was shown.
> 
> ~/.xsession-errors contains nothing particular.
> 
> however, /var/log messages contains these interesting lines:
> 
> (snip. lots of these similar jpeg error messages)
> May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 5
> extraneous bytes before marker 0xa1
> May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 8
> extraneous bytes before marker 0xc4
> May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 1
> extraneous bytes before marker 0xe0
> May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 4
> extraneous bytes before marker 0xc4
> May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 8
> extraneous bytes before marker 0xc4
> May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 16
> extraneous bytes before marker 0xc4
> May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Invalid SOS parameters for
> sequential JPEG
> May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: 16
> extraneous bytes before marker 0xc4
> May 22 12:35:14 tonfisk iceweasel.desktop[28508]: Corrupt JPEG data: bad
> Huffman code
> May 22 12:35:14 tonfisk gdm-Xorg-:1[27988]: Xorg:
> 

Bug#818325: marked as done (xserver-xorg-core: Missing the mouse pointer after locking the screen)

[Debian Bug Tracking System]

Your message dated Wed, 11 Jan 2017 19:29:05 +0100
with message-id <2017082905.GA27113@localhost.localdomain>
and subject line Re: Bug#818325: xserver-xorg-core: Missing the mouse pointer 
after locking the screen
has caused the Debian Bug report #818325,
regarding xserver-xorg-core: Missing the mouse pointer after locking the screen
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
818325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-core
Version: 2:1.18.2-1
Severity: important

Dear Maintainer,

After upgrading the two following packages:


[UPGRADE] xserver-common:amd64 2:1.18.1-1 -> 2:1.18.2-1
[UPGRADE] xserver-xorg-core:amd64 2:1.18.1-1 -> 2:1.18.2-1


The mouse pointer simply disappears when I want to log into the system after
locking the screen. After restarting the Xserver, everything backs to normal,
but when I lock the screen again, I won't see the pointer after login. I'm
using lightdm as DM.

I can get the mouse pointer back also when I switch to TTY using ctl-alt-f1 and
then to xsession via ctrl-alt-f7.



-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor
Integrated Graphics Controller [8086:0046] (rev 02)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 24
-rw-r--r-- 1 root root 1351 Jan 20 17:52 10-keyboard.conf
-rw-r--r-- 1 root root  820 Jan 24 16:09 10-mouse.conf
-rw-r--r-- 1 root root 2024 Mar  4 16:10 20-monitor-intel-dual.conf
-rw-r--r-- 1 root root  697 Jan 20 18:03 50-synaptics.conf
-rw-r--r-- 1 root root  852 Jan 20 17:51 90-serverlayout.conf

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.4.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1
20160224 (Debian 5.3.1-10) ) #1 SMP Debian 4.4.4-2 (2016-03-09)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 15362 Feb 14 12:37 /var/log/Xorg.3.log
-rw-r--r-- 1 root root 30608 Mar 15 23:48 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 31519 Mar 15 23:49 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 30290 Mar 15 23:49 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 41041.245]
X.Org X Server 1.18.2
Release Date: 2016-03-11
[ 41041.245] X Protocol Version 11, Revision 0
[ 41041.245] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
[ 41041.245] Current Operating System: Linux morfikownia 4.4.0-1-amd64 #1 SMP
Debian 4.4.4-2 (2016-03-09) x86_64
[ 41041.245] Kernel command line: BOOT_IMAGE=../vmlinuz-4.4.0-1-amd64
root=/dev/mapper/debian_laptop-root acpi_osi="!Windows 2012" acpi=force
acpi_enforce_resources=lax cgroup_enable=memory  net.ifnames=1 apparmor=1
security=apparmor udev.children-max=64 plymouth.enable=1 quiet splash ro
initrd=../initrd.img-4.4.0-1-amd64
[ 41041.245] Build Date: 12 March 2016  07:32:38AM
[ 41041.245] xorg-server 2:1.18.2-1 (http://www.debian.org/support)
[ 41041.245] Current version of pixman: 0.33.6
[ 41041.245]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 41041.245] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 41041.245] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 15 23:49:18
2016
[ 41041.245] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 41041.245] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 41041.245] (**) Option "defaultserverlayout" "Main"
[ 41041.245] (**) ServerLayout "Main"
[ 41041.245] (**) |-->Screen "Screen0" (0)
[ 41041.245] (**) |   |-->Monitor "LVDS1"
[ 41041.246] (**) |   |-->Device "Device0"
[ 41041.246] (**) |-->Screen "Screen1" (1)
[ 41041.246] (**) |   |-->Monitor "VGA1"
[ 41041.246] (**) |   |-->Device "Device0"
[ 41041.246] (**) Option "DontVTSwitch" "off"
[ 41041.246] (**) Option "DontZap" "on"
[ 41041.246] (**) Option "DontZoom" "on"
[ 41041.246] (**) Option "BlankTime" "10"
[ 41041.246] (**) Option "StandbyTime" "10"
[ 41041.246] (**) 

Bug#818325: xserver-xorg-core: Missing the mouse pointer after locking the screen

[Andreas Boll]

According to the upstream bug report [1] this issue has been resolved.
Thus I'm closing this bug report too.
Feel free to reopen this report if you still have this issue.

Thanks,
Andreas

[1] https://bugs.freedesktop.org/show_bug.cgi?id=94677

On Wed, Mar 16, 2016 at 12:07:59AM +0100, Mikhail Morfikov wrote:
> Package: xserver-xorg-core
> Version: 2:1.18.2-1
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrading the two following packages:
> 
> 
> [UPGRADE] xserver-common:amd64 2:1.18.1-1 -> 2:1.18.2-1
> [UPGRADE] xserver-xorg-core:amd64 2:1.18.1-1 -> 2:1.18.2-1
> 
> 
> The mouse pointer simply disappears when I want to log into the system after
> locking the screen. After restarting the Xserver, everything backs to normal,
> but when I lock the screen again, I won't see the pointer after login. I'm
> using lightdm as DM.
> 
> I can get the mouse pointer back also when I switch to TTY using ctl-alt-f1 
> and
> then to xsession via ctrl-alt-f7.
> 


signature.asc
Description: Digital signature

Bug#820322: X crashes using modesetting driver

[Andreas Boll]

On Mon, May 30, 2016 at 03:26:10PM +0200, Reinhard Karcher wrote:
> reassign src:linux
> fixed-upstream 4.7-rc1
> thanks
> 
> Using a selfcompiled kernel 4.7-rc1, the crash disappeared.
> 
> Reinhard

Is this still an issue with a Debian linux kernel >= 4.7

Thanks,
Andreas


signature.asc
Description: Digital signature

Processed: forcibly merging 824987 832551

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 824987 832551
Bug #824987 [xserver-xorg-core] xbacklight doesn't work with modesetting driver 
on Intel
Bug #832551 [xserver-xorg-core] xserver-xorg-core: Various X tools stop working 
with new xserver-xorg-core
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=96572'.
Severity set to 'normal' from 'important'
Marked as found in versions xorg-server/2:1.18.3-1.
Bug #824987 [xserver-xorg-core] xbacklight doesn't work with modesetting driver 
on Intel
Marked as found in versions xorg-server/2:1.18.4-1 and xorg-server/2:1.18.4-2.
Merged 824987 832551
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
824987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824987
832551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#605621: marked as done (keyboard no longer working in X)

[Debian Bug Tracking System]

Your message dated Wed, 11 Jan 2017 18:19:31 +0100
with message-id <2017071930.GA26333@localhost.localdomain>
and subject line Re: Bug#605621: keyboard no longer working in X
has caused the Debian Bug report #605621,
regarding keyboard no longer working in X
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
605621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: upgrade-reports
Severity: normal

After upgrading from lenny to squeeze my keyboard stopped working in X (but
worked with the console). It turned out that my /etc/X11/xorg.conf contained
an invalid keyboard variant ("nodeadkeys" from a "de" keyboard I had a few
years ago). X in lenny simply ignored the invalid variant (I guess, or was
us/nodeadkeys valid in lenny?).

This setting was put into /etc/default/keyboard during the upgrade, but
X in squeeze silently fails with a wrong keyboard variant. See also bug
571636 for a similar problem.

The real problem IMHO is that X silently fails for invalid keyboard
layouts or variants (invalid in the sense that there is no keymap for that
layout/variant, not that it does not match the real layout). Why can't X
print an error message to the log file, and fall back to some default?

Even if some keys result in different characters a wrong layout/variant
is much better that a completely dead keyboard.

Ironically, the "nodeadkeys" variant had exactly the opposite effect, it
rendered *all* keys dead ;-)

Joachim

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (950, 'testing'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


--- End Message ---
--- Begin Message ---
On Thu, Feb 17, 2011 at 02:17:02PM +0100, Julien Cristau wrote:
> reassign 605621 xorg-server
> tag 605621 upstream patch
> kthxbye
> 
> On Wed, Dec  1, 2010 at 22:23:48 +0100, Joachim Reichel wrote:
> 
> > The real problem IMHO is that X silently fails for invalid keyboard
> > layouts or variants (invalid in the sense that there is no keymap for that
> > layout/variant, not that it does not match the real layout). Why can't X
> > print an error message to the log file, and fall back to some default?
> > 
> > Even if some keys result in different characters a wrong layout/variant
> > is much better that a completely dead keyboard.
> > 
> > Ironically, the "nodeadkeys" variant had exactly the opposite effect, it
> > rendered *all* keys dead ;-)
> > 
> This should be fixed by http://patchwork.freedesktop.org/patch/4039/
> 
> Cheers,
> Julien
> 

This patch has been merged long ago.
Closing this bug.

d3499556d8d83396fa2585bd00371a81e086be36
Author: Peter Hutterer 
Date:   Thu Feb 10 15:12:14 2011 +1000

xkb: if the keymap failed to compile, load the default keymap instead.

We really need symbols, compat, keynames, vmods and types for a sensible 
keymap.

Try this in your xorg.conf.d snippets for all keyboards:
Option "XkbLayout" "us"
Option "XkbVariant" "nodeadkeys"

us(nodeadkeys) doesn't exist so xkbcomp provides everything but the symbols
map. We say we want everything but don't _need_ anything, the server happily
gives us a keymap with every key mapped to NoSymbol. This in turn isn't what
we want after all.

So instead, require symbols, compat, keynames, vmods and types from the
keymap and if that fails, load the default keymap instead. If that fails
too, all bets are off.

Signed-off-by: Peter Hutterer 
Reviewed-by: Dan Nicholson 

Thanks,
Andreas


signature.asc
Description: Digital signature
--- End Message ---

mesa: Changes to 'ubuntu'

[Timo Aaltonen]

 debian/changelog |7 +++
 debian/rules |2 +-
 2 files changed, 8 insertions(+), 1 deletion(-)

New commits:
commit 14030036fcec06a8f237c2e12b079c28492759a3
Author: Timo Aaltonen 
Date:   Wed Jan 11 19:01:06 2017 +0200

rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already. (LP: 
#1605796)

diff --git a/debian/changelog b/debian/changelog
index 812a26d..5691a92 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mesa (13.0.3-1ubuntu2) UNRELEASED; urgency=medium
+
+  * rules: Drop forcing -O2 to fix ppc64el ftbfs, gcc got fixed already.
+(LP: #1605796)
+
+ -- Timo Aaltonen   Wed, 11 Jan 2017 19:01:00 +0200
+
 mesa (13.0.3-1ubuntu1) zesty; urgency=medium
 
   * Merge from Debian.
diff --git a/debian/rules b/debian/rules
index da94876..a5eba40 100755
--- a/debian/rules
+++ b/debian/rules
@@ -12,7 +12,7 @@ DEB_HOST_ARCH_CPU  ?= $(shell dpkg-architecture 
-qDEB_HOST_ARCH_CPU)
 
 ifeq (,$(filter $(DEB_HOST_ARCH), armhf))
 buildflags = \
-   $(shell DEB_CFLAGS_MAINT_APPEND="-Wall -O2" 
DEB_CXXFLAGS_MAINT_APPEND="-Wall -O2" dpkg-buildflags --export=configure)
+   $(shell DEB_CFLAGS_MAINT_APPEND=-Wall DEB_CXXFLAGS_MAINT_APPEND=-Wall 
dpkg-buildflags --export=configure)
 else
 # Workaround for a variant of LP: #725126
 buildflags = \

Processed: Re: Bug#742433: xserver-xorg-core: Segmentation fault using bad pointer from __glXGetAnswerBuffer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #742433 [xserver-xorg-core] xserver-xorg-core: Segmentation fault using bad 
pointer from __glXGetAnswerBuffer
Ignoring request to alter tags of bug #742433 to the same tags previously set

-- 
742433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#742433: xserver-xorg-core: Segmentation fault using bad pointer from __glXGetAnswerBuffer

[Andreas Boll]

Control: tag -1 moreinfo

On Mon, Mar 24, 2014 at 04:31:16AM +1100, Steven McDonald wrote:
> Package: xserver-xorg-core
> Version: 2:1.15.0-2
> Severity: normal
> Tags: upstream patch
> 
> Hi there!
> 
> While trying to play the game FTL, installed using Debian's steam:i386
> package, I experienced consistently reproducible X segfaults at game
> startup time.
> 
> Doing a bit of digging with gdb, I got the following backtrace from the
> active thread at the time of the segfault:
> 
> -- 8< --
> #0  _mesa_GenTextures (n=256, textures=) at 
> ../../../../src/mesa/main/texobj.c:1031
> #1  0x7f825ccce606 in __glXDisp_GenTextures (cl=0x7f826383bce0, 
> pc=) at ../../glx/indirect_dispatch.c:2596
> #2  0x7f825cce21a0 in __glXDispatch (client=) at 
> ../../glx/glxext.c:606
> #3  0x7f826260584e in Dispatch () at ../../dix/dispatch.c:433
> #4  0x7f826260964a in dix_main (argc=8, argv=0x7fff41a21a28, 
> envp=) at ../../dix/main.c:294
> #5  0x7f825fe4ab45 in __libc_start_main (main=0x7f82625f4c00 , 
> argc=8, argv=0x7fff41a21a28, init=, fini=, 
> rtld_fini=, stack_end=0x7fff41a21a18) at libc-start.c:287
>   #6  0x7f82625f4c2e in _start ()
> -- >8 --
> 
> After a little more digging, I found that the fault is in xorg-server
> and not mesa, due to __glXDisp_GenTextures passing a garbage pointer as
> the second argument to _mesa_GenTextures. This pointer comes from
> __glXGetAnswerBuffer within xorg-server.
> 
> I found that line 94 of glx/indirect_util.c in particular is
> responsible for turning the pointer into a garbage value:
> 
> temp_buf = (temp_buf + mask) & ~mask;
> 
> I don't have a very deep understanding of how this line is evaluated,
> but as best I can determine, (temp_buf + mask) is an "intptr_t" (which
> should be a 64-bit value on my 64-bit system), and mask is a
> "const unsigned" (which is a 32-bit integer). NOTing mask and ANDing
> the result with a 64-bit pointer seems to produce a pointer limited to
> the range of a 32-bit integer, which causes a segfault when access is
> attempted.
> 
> I did notice that the same behaviour does not manifest with mask as a
> *signed* 32-bit value, but I can't explain that with my level of C
> knowledge.
> 
> In any case, I am attaching a patch which fixes the problem by changing
> the declaration of mask from "const unsigned" to "const uintptr_t".
> I've tested and confirmed that I can run the game with this patch
> applied.
> 
> Please let me know if you need any further information. :)
> 
>  - Steven
> 

Hi,

is this still an issue with a newer xserver-xorg-core version (e.g.
the version from jessie or stretch/sid)?

Thanks,
Andreas

> Make sure we're using a pointer-sized integer when doing pointer
> arithmetic.
> --- a/glx/indirect_util.c
> +++ b/glx/indirect_util.c
> @@ -73,7 +73,7 @@
>   void *local_buffer, size_t local_size, unsigned 
> alignment)
>  {
>  void *buffer = local_buffer;
> -const unsigned mask = alignment - 1;
> +const uintptr_t mask = alignment - 1;
>  
>  if (local_size < required_size) {
>  const size_t worst_case_size = required_size + alignment;



signature.asc
Description: Digital signature

Processed: Re: Bug#742433: xserver-xorg-core: Segmentation fault using bad pointer from __glXGetAnswerBuffer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #742433 [xserver-xorg-core] xserver-xorg-core: Segmentation fault using bad 
pointer from __glXGetAnswerBuffer
Added tag(s) moreinfo.

-- 
742433: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#725747: xserver-xorg-core: Using PRIME providers when discreet card is set to be primary leads to xserver crash

[Andreas Boll]

Control: tag -1 moreinfo

On Tue, Oct 08, 2013 at 02:16:10AM +0300, Pauli wrote:
> Package: xserver-xorg-core
> Version: 2:1.14.3-3
> Severity: normal
> Tags: upstream patch
> 
> Dear Maintainer,
> 
> With hydrid graphics laptop I had started X with discreet radein set as
> primary card using vgaswitcheroo. During that run I ended up trying to
> enable PRIME offloading to radeon:
> 
> xrandr --setprovideroutputsource radeon Intel
> 
> That led to following crash:
> #0  0x7ff44fd431e5 in __GI_raise (sig=sig@entry=6) at 
> ../nptl/sysdeps/unix/sysv/linux/raise.c:56
> #1  0x7ff44fd46398 in __GI_abort () at abort.c:90
> #2  0x7ff44fd3c272 in __assert_fail_base (fmt=0x7ff44fe799c0 "%s%s%s:%u: 
> %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7ff452186ce7 
> "slave->isGPU", 
> file=file@entry=0x7ff452186cb2 "../../dix/dispatch.c", 
> line=line@entry=3937, function=function@entry=0x7ff452186d80 
> <__PRETTY_FUNCTION__.17904> "DetachUnboundGPU")
> at assert.c:92
> #3  0x7ff44fd3c322 in __GI___assert_fail 
> (assertion=assertion@entry=0x7ff452186ce7 "slave->isGPU", 
> file=file@entry=0x7ff452186cb2 "../../dix/dispatch.c", 
> line=line@entry=3937, function=function@entry=0x7ff452186d80 
> <__PRETTY_FUNCTION__.17904> "DetachUnboundGPU") at assert.c:101
> #4  0x7ff45202b2f0 in DetachUnboundGPU (slave=slave@entry=0x7ff45429c0d0) 
> at ../../dix/dispatch.c:3937
> #5  0x7ff4520a77fd in xf86RandR14ProviderSetOffloadSink 
> (pScreen=0x7ff45429c0d0, provider=0x7ff4526ece20, 
> sink_provider=0x7ff45428f970)
> at ../../../../hw/xfree86/modes/xf86RandR12.c:1821
> #6  0x7ff4520ec911 in ProcRRSetProviderOffloadSink (client= out>) at ../../randr/rrprovider.c:338
> #7  0x7ff45202ad6e in Dispatch () at ../../dix/dispatch.c:432
> #8  0x7ff45201a2ca in main (argc=10, argv=0x7fff78e24868, envp= out>) at ../../dix/main.c:298
> 
> Problem is missing check that provider is actually configured as offscreen
> card in protocol request validation.
> 
> Attached patch adds the missing check to the protocol layer to avoid
> server from asserting.
> 

Hi,

is this still an issue with a newer xserver-xorg-core version (e.g.
the version from jessie or stretch/sid)?

Thanks,
Andreas

> diff --git a/randr/rrprovider.c b/randr/rrprovider.c
> index b321e62..53a610a 100644
> --- a/randr/rrprovider.c
> +++ b/randr/rrprovider.c
> @@ -291,6 +291,8 @@ ProcRRSetProviderOutputSource(ClientPtr client)
>  
>  if (!(provider->capabilities & RR_Capability_SinkOutput))
>  return BadValue;
> +if (!provider->pScreen->isGPU)
> +return BadValue;
>  
>  if (stuff->source_provider) {
>  VERIFY_RR_PROVIDER(stuff->source_provider, source_provider, 
> DixReadAccess);
> @@ -322,6 +324,8 @@ ProcRRSetProviderOffloadSink(ClientPtr client)
>  VERIFY_RR_PROVIDER(stuff->provider, provider, DixReadAccess);
>  if (!(provider->capabilities & RR_Capability_SourceOffload))
>  return BadValue;
> +if (!provider->pScreen->isGPU)
> +return BadValue;
>  
>  if (stuff->sink_provider) {
>  VERIFY_RR_PROVIDER(stuff->sink_provider, sink_provider, 
> DixReadAccess);



signature.asc
Description: Digital signature

Processed: Re: Bug#725747: xserver-xorg-core: Using PRIME providers when discreet card is set to be primary leads to xserver crash

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #725747 [xserver-xorg-core] xserver-xorg-core: Using PRIME providers when 
discreet card is set to be primary leads to xserver crash
Ignoring request to alter tags of bug #725747 to the same tags previously set

-- 
725747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#725747: xserver-xorg-core: Using PRIME providers when discreet card is set to be primary leads to xserver crash

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #725747 [xserver-xorg-core] xserver-xorg-core: Using PRIME providers when 
discreet card is set to be primary leads to xserver crash
Added tag(s) moreinfo.

-- 
725747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#829386: xorg: Xorg crashes

[Shérab]

Hi,

Samuel Thibault (2017/01/08 13:05 +0100):
> Control: tags -1 + patch fixed-upstream
> 
> Hello,
> 
> I have attached the upstream fix for this issue, to be applied to the
> xserver-xorg-input-libinput package. Could Jean-Philippe, Sebastien and
> Sebastian test it so that we can apply it to Debian before Stretch?

It works for me, thanks a lot for the hard work!

Shérab.

Bug#773709: marked as done (xserver-xorg: X crashes when displaying a very large jpeg file with certain viewers)

[Debian Bug Tracking System]

Your message dated Wed, 11 Jan 2017 17:49:13 +0100
with message-id <2017064913.GA25483@localhost.localdomain>
and subject line Re: Bug#773709: [PATCH] glamor: Call glamor_pixmap_destroy_fbo 
from glamor_set_pixmap_private
has caused the Debian Bug report #773709,
regarding xserver-xorg: X crashes when displaying a very large jpeg file with 
certain viewers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
773709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg
Version: 1:7.7+7
Severity: normal

Dear Maintainer,

When I try to diplay this 19 857 × 3 038, 24.85 Mio jpeg picture
http://upload.wikimedia.org/wikipedia/commons/3/31/78_-_Qu%C3%A9bec_-
_Juin_2009.jpg
in iceweasel, not only iceweasel crashes, but the whole desktop too, leaving
me on the login screen. The crash happens immediately, I don't think
iceweasel has the time to download the whole picture. When I download the
picture and display it with eog, the same thing happens.
ristretto, feh and imagemagick can display it just fine.

The graphic card is a Radeon R9 280X, and I use the free radeon driver on a
debian testing install. When I use the non-free fglrx driver, the crash
doesn't occur.

Regards,



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Oct  3 10:52 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2401376 Dec  9 23:24 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798]

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.3 (Debian 4.8.3-16) ) #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 43548 Dec 22 13:25 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[  2310.576] 
X.Org X Server 1.16.2.901 (1.16.3 RC 1)
Release Date: 2014-12-09
[  2310.577] X Protocol Version 11, Revision 0
[  2310.577] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian
[  2310.577] Current Operating System: Linux desktop 3.16.0-4-amd64 #1 SMP 
Debian 3.16.7-ckt2-1 (2014-12-08) x86_64
[  2310.577] Kernel command line: BOOT_IMAGE=/vmlinuz root=/dev/sda1
[  2310.577] Build Date: 09 December 2014  10:15:28PM
[  2310.577] xorg-server 2:1.16.2.901-1 (http://www.debian.org/support) 
[  2310.577] Current version of pixman: 0.32.6
[  2310.577]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  2310.577] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  2310.577] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 22 13:25:43 
2014
[  2310.577] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  2310.577] (==) No Layout section.  Using the first Screen section.
[  2310.577] (==) No screen section available. Using defaults.
[  2310.577] (**) |-->Screen "Default Screen Section" (0)
[  2310.577] (**) |   |-->Monitor ""
[  2310.577] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  2310.577] (==) Automatically adding devices
[  2310.577] (==) Automatically enabling devices
[  2310.577] (==) Automatically adding GPU devices
[  2310.577] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  2310.577]Entry deleted from font path.
[  2310.577] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[  2310.577] (==) ModulePath set to "/usr/lib/xorg/modules"
[  2310.577] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[  2310.577] (II) Loader magic: 0x7f524c345d80
[  2310.577] (II) Module ABI versions:
[  

Bug#833291: marked as done (Xorg: crash (SIGABRT))

[Debian Bug Tracking System]

Your message dated Wed, 11 Jan 2017 17:39:32 +0100
with message-id <2017063932.GA24277@localhost.localdomain>
and subject line Re: Bug#833291: Xorg: crash (SIGABRT)
has caused the Debian Bug report #833291,
regarding Xorg: crash (SIGABRT)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
833291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-core
Version: 2:1.18.4-1
Severity: normal
File: /usr/lib/xorg/Xorg

I had the following crash just after losing network.
I am running GNOME and GDM from Debian testing.
If this bug isn't helpful, please close it.

$ gdb -batch -n -ex 'set height 0' -ex bt -ex 'thread apply all bt full' --core 
/var/crash/1000/23421-1000-1000-6-1470145643-chianamo--usr-lib-xorg-Xorg.core 
/usr/lib/xorg/Xorg
[New LWP 23421]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xorg/Xorg vt7 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -backgr'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7fae2b1d01c8 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
54  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
#0  0x7fae2b1d01c8 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x7fae2b1d164a in __GI_abort () at abort.c:89
#2  0x55819e1ca04e in OsAbort () at ../../os/utils.c:1408
#3  0x55819e0a7ebc in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at 
../../../../hw/xfree86/common/xf86Init.c:1066
#4  0x55819e0a7f6a in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at 
../../../../hw/xfree86/common/xf86Init.c:1110
#5  0x55819e1cfcb2 in AbortServer () at ../../os/log.c:874
#6  0x55819e1d0aed in FatalError (f=f@entry=0x55819e1ffcf0 "Caught signal 
%d (%s). Server aborting\n") at ../../os/log.c:1015
#7  0x55819e1c78ee in OsSigHandler (signo=11, sip=, 
unused=) at ../../os/osinit.c:150
#8  0x7fae2b1d0250 in  () at 
/lib/x86_64-linux-gnu/libc.so.6
#9  0x7fae2329bbfd in _fbGetWindowPixmap (pWindow=0x0) at 
../../fb/fbscreen.c:84
#10 0x55819e145e37 in present_restore_screen_pixmap (screen=0x55819ff51cb0) 
at ../../present/present.c:442
#11 0x55819e145f05 in present_set_abort_flip 
(screen=screen@entry=0x55819ff51cb0) at ../../present/present.c:458
#12 0x55819e146672 in present_flip_destroy 
(screen=screen@entry=0x55819ff51cb0) at ../../present/present.c:1030
#13 0x55819e145223 in present_close_screen (screen=0x55819ff51cb0) at 
../../present/present_screen.c:61
#14 0x55819e0f5768 in CursorCloseScreen (pScreen=0x55819ff51cb0) at 
../../xfixes/cursor.c:187
#15 0x55819e1435c4 in AnimCurCloseScreen (pScreen=) at 
../../render/animcur.c:106
#16 0x55819e068dd7 in dix_main (argc=12, argv=0x7ffd8b765738, 
envp=) at ../../dix/main.c:354
#17 0x7fae2b1bd730 in __libc_start_main (main=0x55819e052f60 , 
argc=12, argv=0x7ffd8b765738, init=, fini=, 
rtld_fini=, stack_end=0x7ffd8b765728) at ../csu/libc-start.c:291
#18 0x55819e052f99 in _start ()

Thread 1 (Thread 0x7fae2d431a40 (LWP 23421)):
#0  0x7fae2b1d01c8 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 23421
selftid = 23421
#1  0x7fae2b1d164a in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x6d20656874202c79, 
sa_sigaction = 0x6d20656874202c79}, sa_mask = {__val = {7070762909662671717, 
171515904, 0, 0, 0, 0, 0, 0, 0, 0, 140386024359120, 94015194543968, 
140726943239872, 0, 140386060409408, 94015221395744}}, sa_flags = 0, 
sa_restorer = 0x1}
sigs = {__val = {32, 0 }}
#2  0x55819e1ca04e in OsAbort () at ../../os/utils.c:1408
#3  0x55819e0a7ebc in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at 
../../../../hw/xfree86/common/xf86Init.c:1066
i = 
#4  0x55819e0a7f6a in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at 
../../../../hw/xfree86/common/xf86Init.c:1110
i = 
#5  0x55819e1cfcb2 in AbortServer () at ../../os/log.c:874
#6  0x55819e1d0aed in FatalError (f=f@entry=0x55819e1ffcf0 "Caught signal 
%d (%s). Server aborting\n") at ../../os/log.c:1015
Python Exception  Attempt to dereference a generic pointer.: 
#7  0x55819e1c78ee in OsSigHandler (signo=11, sip=, 
unused=) at ../../os/osinit.c:150
unused = 
sip = 
signo = 11
#8  0x7fae2b1d0250 in  () at 
/lib/x86_64-linux-gnu/libc.so.6
#9  0x7fae2329bbfd 

Bug#832560: xserver-xorg-core: performance is very bad since using built-in modesetting 4th gen GMA on ivy bridge

[Andreas Boll]

On Sun, Aug 07, 2016 at 01:50:40PM +0200, Martin Dosch wrote:
> Am 02.08.2016 um 20:53 schrieb Julien Cristau:
> > Please show the output of dpkg -l '*mesa*', you seem to have some bits
> > from experimental, but possibly not all that's needed.  And please
> > attach your X log (after removing xorg.conf again), which should be in
> > ~/.local/share/xorg.
> 
> 
> Ok, it seems like libgbm1 was not yet installed from experimental which
> i did now.
> 
> Now it looks like this:
> 
> > dpkg -l '*mesa*'
> > Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
> > | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
> >  Halb installiert/Trigger erWartet/Trigger anhängig
> > |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: 
> > GROSS=schlecht)
> > ||/ NameVersion  Architektur  Beschreibung
> > +++-===---===
> > ii  libegl1-mesa:amd64  12.0.1-3 amd64free 
> > implementation of the EGL API -- runtime
> > un  libegl1-mesa-drivers(keine 
> > Beschreibung vorhanden)
> > ii  libgl1-mesa-dri:amd64   12.0.1-3 amd64free 
> > implementation of the OpenGL API -- DRI module
> > ii  libgl1-mesa-dri:i38612.0.1-3 i386 free 
> > implementation of the OpenGL API -- DRI module
> > un  libgl1-mesa-dri-experim (keine 
> > Beschreibung vorhanden)
> > ii  libgl1-mesa-glx:amd64   12.0.1-3 amd64free 
> > implementation of the OpenGL API -- GLX runtim
> > ii  libgl1-mesa-glx:i38612.0.1-3 i386 free 
> > implementation of the OpenGL API -- GLX runtim
> > ii  libglapi-mesa:amd64 12.0.1-3 amd64free 
> > implementation of the GL API -- shared library
> > ii  libglapi-mesa:i386  12.0.1-3 i386 free 
> > implementation of the GL API -- shared library
> > ii  libgles1-mesa:amd64 12.0.1-3 amd64free 
> > implementation of the OpenGL|ES 1.x API -- run
> > ii  libgles2-mesa:amd64 12.0.1-3 amd64free 
> > implementation of the OpenGL|ES 2.x API -- run
> > ii  libglu1-mesa:amd64  9.0.0-2.1amd64Mesa OpenGL 
> > utility library (GLU)
> > ii  libwayland-egl1-mesa:am 12.0.1-3 amd64
> > implementation of the Wayland EGL platform -- runti
> > ii  mesa-utils  8.3.0-1  amd64Miscellaneous 
> > Mesa GL utilities
> > ii  mesa-utils-extra8.3.0-1  amd64Miscellaneous 
> > Mesa utilies (opengles, egl)
> > ii  mesa-va-drivers:amd64   12.0.1-3 amd64Mesa VA-API 
> > video acceleration drivers
> > ii  mesa-vdpau-drivers:amd6 12.0.1-3 amd64Mesa VDPAU 
> > video acceleration drivers
> > ii  mesa-vulkan-drivers 12.0.1-3 amd64Mesa Vulkan 
> > graphics drivers
> > un  mesag3  (keine 
> > Beschreibung vorhanden)
> > un  xlibmesa3   (keine 
> > Beschreibung vorhanden)
> 
> Right now I can't afford restarting X but I'll do later and have a look
> if it will work now.
> 
> Best regards,
> Martin
> 

Hi,

did you have a chance to restart your X session?
Is this still an issue?

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#834737: marked as done (xserver-xorg-core: Xorg crashes with SIGABRT in _fbGetWindowPixmap)

[Debian Bug Tracking System]

Your message dated Wed, 11 Jan 2017 17:22:58 +0100
with message-id <2017062258.GA22856@localhost.localdomain>
and subject line Re: Bug#834737: xserver-xorg-core: Xorg crashes with SIGABRT 
in _fbGetWindowPixmap
has caused the Debian Bug report #834737,
regarding xserver-xorg-core: Xorg crashes with SIGABRT in _fbGetWindowPixmap
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
834737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-core
Version: 2:1.18.4-1
Severity: important
Tags: upstream

Not sure how the crash occurred. I log all crashes in the system, and I noticed
this crash.

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth
/run/user/1000/gdm/Xauthority -backgr'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7f53bdeee1c8 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x7f53bdeee1c8 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1  0x7f53bdeef64a in __GI_abort () at abort.c:89
#2  0x55577c5af04e in OsAbort () at ../../os/utils.c:1408
#3  0x55577c48cebc in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at
../../../../hw/xfree86/common/xf86Init.c:1066
#4  0x55577c48cf6a in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at
../../../../hw/xfree86/common/xf86Init.c:1110
#5  0x55577c5b4cb2 in AbortServer () at ../../os/log.c:874
#6  0x55577c5b5aed in FatalError (f=f@entry=0x55577c5e4cf0 "Caught signal
%d (%s). Server aborting\n") at ../../os/log.c:1015
#7  0x55577c5ac8ee in OsSigHandler (signo=11, sip=,
unused=) at ../../os/osinit.c:150
#8  0x7f53bdeee250 in  () at /lib/x86_64-linux-
gnu/libc.so.6
#9  0x7f53b6bdcbfd in _fbGetWindowPixmap (pWindow=0x0) at
../../fb/fbscreen.c:84
#10 0x55577c52ae37 in present_restore_screen_pixmap (screen=0x55577d4c7fc0)
at ../../present/present.c:442
#11 0x55577c52af05 in present_set_abort_flip
(screen=screen@entry=0x55577d4c7fc0) at ../../present/present.c:458
#12 0x55577c52b672 in present_flip_destroy
(screen=screen@entry=0x55577d4c7fc0) at ../../present/present.c:1030
#13 0x55577c52a223 in present_close_screen (screen=0x55577d4c7fc0) at
../../present/present_screen.c:61
#14 0x55577c4da768 in CursorCloseScreen (pScreen=0x55577d4c7fc0) at
../../xfixes/cursor.c:187
#15 0x55577c5285c4 in AnimCurCloseScreen (pScreen=) at
../../render/animcur.c:106
#16 0x55577c44ddd7 in dix_main (argc=12, argv=0x7ffc7f7c1d18,
envp=) at ../../dix/main.c:354
#17 0x7f53bdedb730 in __libc_start_main (main=0x55577c437f60 ,
argc=12, argv=0x7ffc7f7c1d18, init=, fini=,
rtld_fini=, stack_end=0x7ffc7f7c1d08) at ../csu/libc-start.c:291
#18 0x55577c437f99 in _start ()
(gdb) q



-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.0 
20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

No Xorg X server log files found.

udev information:
-
P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input8
E: EV=3
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PRODUCT=19/0/1/0
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: USEC_INITIALIZED=14713078

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input8/event8
N: input/event8
E: BACKSPACE=guess
E: DEVNAME=/dev/input/event8
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input8/event8
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: LIBINPUT_DEVICE_GROUP=19/0/1/0:LNXPWRBN/button
E: MAJOR=13
E: MINOR=72
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=15605593
E: XKBLAYOUT=us

Processed: bug 850940 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=99333

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 850940 https://bugs.freedesktop.org/show_bug.cgi?id=99333
Bug #850940 [xserver-xorg-core] [xserver-xorg-core] plasmashell freezes with 
xorg-server 1.19.0
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=99333'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
850940: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#846779: xserver-xorg-core: chrome freezes with xorg-server 1.19.0

[Andreas Boll]

Hi,

could you try this patch [1]?

Thanks,
Andreas

[1] https://patchwork.freedesktop.org/patch/132089/

On Mon, Dec 12, 2016 at 03:28:33PM +0900, Michel Dänzer wrote:
> On 12/12/16 05:39 AM, Frédéric Brière wrote:
> > On Sat, Dec 10, 2016 at 10:07:51PM -0500, Frédéric Brière wrote:
> >> Otherwise, I guess I'll have to muster up the courage to try to bisect
> >> this.  (gulp!)
> > 
> > It wasn't exactly a nice leisurely stroll through the park, but I did
> > manage to bisect and pinpoint f993091 as the guilty commit.
> 
> Thanks for that!
> 
> 
> > At this point, I guess there's not much left to do, apart from filing a
> > bug upstream?  (Oh, great, Bugzilla.  )
> 
> Yeah, that's the logical next step.
> 
> 
> -- 
> Earthling Michel Dänzer   |   http://www.amd.com
> Libre software enthusiast | Mesa and X developer


signature.asc
Description: Digital signature

Re: I am missing the x fontserver in jessie

[Julien Cristau]

On 01/11/2017 02:54 PM, Roesner, Thomas wrote:
> Dear all,
> 
> i am missing the  xfs package in Jessie. Has this package been removed
> or is there an alternative package?
> 
> I need an fontserver on debian 8 for a remote system (exceed).
> 
Hi Thomas,

see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733958 for the
rationale to remove the font server.

Cheers,
Julien

I am missing the x fontserver in jessie

[Roesner, Thomas]

Dear all,
i am missing the  xfs package in Jessie. Has this package been removed or is 
there an alternative package?
I need an fontserver on debian 8 for a remote system (exceed).

Can anybody help?

Kind Regards
Thomas Roesner

Siemens AG
Building Technologies Division
Solution and Service Portfolio
BT SSP SOL R CI DMS
Otto-Hahn-Ring 6
81739 München, Deutschland
Tel.: +49 89 636-632336
Fax: +49 89 636-40334
mailto:roesner.tho...@siemens.com
www.siemens.com/ingenuityforlife
[www.siemens.com/ingenuityforlife]
Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme; 
Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Lisa Davis, Klaus Helmrich, 
Janina Kugel, Siegfried Russwurm, Ralf P. Thomas; Sitz der Gesellschaft: Berlin 
und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, 
München, HRB 6684; WEEE-Reg.-Nr. DE 23691322

Bug#850940: [xserver-xorg-core] plasmashell freezes with xorg-server 1.19.0

[MAG4 Piemonte]

Package: xserver-xorg-core
Version: 2:1.19.0-3
Severity: normal

--- Please enter the report below this line. ---
Hi, after upgrading to version 1.19.0-(2,3) plasmashell freezes frequently 
with the same symptoms described here
https://bugs.kde.org/show_bug.cgi?id=373131
and also here
https://lists.debian.org/debian-kde/2016/12/msg2.html
Downgrading to version 1.18.4-2 makes the problem disappear.
May be the error is solved by
https://bugs.freedesktop.org/show_bug.cgi?id=99333
Regards!

--- System information. ---
Architecture: 
Kernel:   Linux 4.8.0-2-686-pae

Debian Release: stretch/sid
  500 testing httpredir.debian.org 
  500 stable  download.webmin.com 

--- Package information. ---
Depends  (Version) | Installed
==-+-
xserver-common (>= 2:1.19.0-3) | 2:1.19.0-3
keyboard-configuration | 1.155
udev  (>= 149) | 232-8
libegl1-mesa   | 13.0.2-3
 OR libegl1| 
libaudit1 (>= 1:2.2.1) | 1:2.6.7-1
libc6(>= 2.17) | 2.24-8
libdbus-1-3(>= 1.9.14) | 1.10.14-1
libdrm2 (>= 2.3.1) | 2.4.74-1
libepoxy0 (>= 1.0) | 1.3.1-1
libgbm1(>= 10.2~0) | 13.0.2-3
libgcrypt20 (>= 1.7.0) | 1.7.5-2
libgl1-mesa-glx| 13.0.2-3
 OR libgl1 | 
libpciaccess0(>= 0.12.902) | 0.13.4-1
libpixman-1-0  (>= 0.30.0) | 0.34.0-1
libselinux1(>= 2.0.82) | 2.6-3
libsystemd0| 232-8
libudev1  (>= 183) | 232-8
libxau6| 1:1.0.8-1
libxdmcp6  | 1:1.1.2-1.1
libxfont2 (>= 1:2.0.1) | 1:2.0.1-3
libxshmfence1  | 1.2-1


Recommends  (Version) | Installed
=-+-==
libgl1-mesa-dri (>= 7.10.2-4) | 13.0.2-3
libpam-systemd| 232-8


Suggests (Version) | Installed
==-+-===
xfonts-100dpi  | 1:1.0.4+nmu1
 OR xfonts-75dpi   | 1:1.0.4+nmu1
xfonts-scalable| 1:1.0.3-1.1


--- Output from package bug script ---
X server symlink status:

lrwxrwxrwx 1 root root 13 ago 16  2011 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 dic 16 19:39 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/
ATI] RS780 [Radeon HD 3200] [1002:9610]

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 4.8.0-2-686-pae (debian-ker...@lists.debian.org) (gcc version 
5.4.1 20161202 (Debian 5.4.1-4) ) #1 SMP Debian 4.8.15-2 (2017-01-04)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 37082 gen  5 10:13 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 32774 gen  5 10:15 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 56465 gen 11 12:15 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[36.227] (--) Log file renamed from "/var/log/Xorg.pid-1009.log" to "/var/
log/Xorg.0.log"
[36.248] 
X.Org X Server 1.19.0
Release Date: 2016-11-15
[36.249] X Protocol Version 11, Revision 0
[36.249] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian
[36.249] Current Operating System: Linux hipnos 4.8.0-2-686-pae #1 SMP 
Debian 4.8.15-2 (2017-01-04) i686
[36.249] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-2-686-pae 
root=UUID=3f97e352-0d19-4a21-8aac-5c3c9677ee26 ro quiet splash
[36.249] Build Date: 16 December 2016  07:33:27PM
[36.249] xorg-server 2:1.19.0-3 (https://www.debian.org/support) 
[36.249] Current version of pixman: 0.34.0
[36.249]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[36.249] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[36.249] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 11 10:50:30 
2017
[36.321] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[36.656] (==) No Layout section.  Using the first Screen section.
[36.656] (==) No 

mesa: Changes to 'ubuntu'

[Timo Aaltonen]

 VERSION
|2 
 debian/changelog   
|   47 +
 debian/compat  
|2 
 debian/control 
|8 
 debian/patches/0001-intel-blorp_blit-Create-structure-for-src-dst-coordi.patch 
|  137 +++
 debian/patches/0002-intel-blorp_blit-Split-blorp-blits-if-they-are-too-l.patch 
|  151 +++
 debian/patches/0003-intel-blorp_blit-Adjust-blorp-surface-parameters-for.patch 
|  160 
 debian/patches/0004-intel-blorp-Always-use-UINT-formats-on-SKL.patch   
|  140 +++
 debian/patches/0005-intel-blorp_blit-Move-RGB-R-conversion-to-follow-bli.patch 
|  173 
 debian/patches/0006-intel-blorp_blit-Enable-splitting-large-blorp-blits.patch  
|   87 ++
 debian/patches/0007-intel-blorp_blit-Add-split_blorp_blit_debug-switch.patch   
|   57 +
 debian/patches/0008-i965-Increase-max-texture-to-16k-for-gen7.patch
|   45 +
 debian/patches/r600-sb-Fix-loop-optimization-related-hangs-on-eg.diff  
|  387 ++
 debian/patches/series  
|   13 
 debian/patches/vl-zscan-fix-Fix-trivial-sign-compare-warnings.diff 
|   28 
 debian/rules   
|   17 
 debian/source/format   
|1 
 docs/relnotes/13.0.2.html  
|3 
 docs/relnotes/13.0.3.html  
|  176 
 src/amd/common/ac_nir_to_llvm.c
|2 
 src/amd/vulkan/radv_device.c   
|3 
 src/amd/vulkan/radv_meta_bufimage.c
|   27 
 src/compiler/Makefile.glsl.am  
|5 
 src/compiler/glsl/builtin_functions.cpp
|   12 
 src/compiler/glsl/link_uniforms.cpp
|2 
 src/compiler/glsl/linker.cpp   
|1 
 src/compiler/nir/nir_opt_undef.c   
|4 
 src/compiler/spirv/vtn_glsl450.c   
|   23 
 src/egl/main/eglapi.c  
|4 
 src/gallium/auxiliary/cso_cache/cso_cache.c
|4 
 src/gallium/auxiliary/tgsi/tgsi_info.c 
|1 
 src/gallium/drivers/radeon/r600_pipe_common.c  
|6 
 src/gallium/drivers/radeonsi/si_compute.c  
|1 
 src/gallium/drivers/radeonsi/si_descriptors.c  
|   19 
 src/gallium/drivers/radeonsi/si_pipe.c 
|5 
 src/gallium/drivers/radeonsi/si_shader.c   
|  183 +++-
 src/gallium/drivers/radeonsi/si_shader.h   
|2 
 src/gallium/drivers/radeonsi/si_state.c
|   25 
 src/gallium/drivers/radeonsi/si_state_draw.c   
|   24 
 src/gallium/drivers/radeonsi/si_state_shaders.c
|7 
 src/gallium/drivers/vc4/vc4_program.c  
|   27 
 src/intel/genxml/gen9.xml  
|2 
 src/intel/vulkan/anv_allocator.c   
|   27 
 src/intel/vulkan/anv_descriptor_set.c  
|1 
 src/intel/vulkan/anv_device.c  
|   52 -
 src/intel/vulkan/anv_gem.c 
|6 
 src/intel/vulkan/anv_image.c   
|   16 
 src/intel/vulkan/anv_private.h 
|   13 
 src/intel/vulkan/genX_cmd_buffer.c 
|   36 
 src/mesa/drivers/dri/i965/Makefile.am  
|7 
 src/mesa/drivers/dri/i965/brw_fs.cpp   
|   10 
 src/mesa/drivers/dri/i965/brw_fs.h 
|6 
 src/mesa/drivers/dri/i965/brw_fs_copy_propagation.cpp  
|   19 
 src/mesa/drivers/dri/i965/brw_vec4_gs_visitor.cpp  
|8 
 src/mesa/drivers/dri/i965/intel_mipmap_tree.c  
|2 
 src/mesa/drivers/dri/i965/test_fs_copy_propagation.cpp