Bug#926540: unblock: xorg-server/2:1.20.4-1

[Andreas Boll]

Hi Cyril and Niels,

On Tue, Jun 4, 2019 at 8:02 PM Niels Thykier  wrote:
>
> Cyril Brulebois:
> > Apologies for the delay, been busy…
> >
> > Runtime tests look good, no objections.
> >
> >
> > Cheers,
> >
>
> Unblocked, thanks.
> ~Niels
>

Thanks for reviewing and unblocking!
Andreas

Bug#928807: unblock: mesa/18.3.6-2

[Andreas Boll]

Hi Paul and Sam,

On Wed, Jun 5, 2019 at 9:47 PM Paul Gevers  wrote:
>
> Unblocked, thanks.
>
> Paul
>

Thanks for reviewing and unblocking!
Andreas

Bug#928807: unblock: mesa/18.3.6-2

[Andreas Boll]

Hi Paul,

On Thu, May 30, 2019 at 09:58:14PM +0200, Paul Gevers wrote:
> Control: tags -1 moreinfo
> 
> Hi Andreas,
> 
> On Sat, 11 May 2019 16:43:45 +0200 Andreas Boll  wrote:
> > This unblock request contains a stable upstream release with lots of
> > bug fixes for mesa's graphics drivers including fixes for driver
> > crashes and visual corruption. It fixes two RC bugs (#922346,
> > #926857).
> 
> How would a targeted fix look like? New upstream releases don't meet the
> freeze policy and the diff is way to big to properly review.
> 
> Paul
> 

Mesa upstream is very conservative in which patches it includes into
its stable releases. Those cherry-picked patches are all targeted
fixes. No new features and also no huge fixes are allowed. See also
[1]. They also do lots of regression testing on those stable releases.

I'd be in favor of taking all fixes from the upstream stable release
and not only just those which explicitly fix reported Debian RC bugs.

I'd recommend to review the git branch patch by patch instead of the
whole diff at once. Those patches have good commit messages which help
to review the patches.

E.g.
git clone https://salsa.debian.org/xorg-team/lib/mesa.git
cd mesa
gitk mesa-18.3.4-2..mesa-18.3.6-2

Does this help?

Thanks,
Andreas

[1] https://mesa3d.org/submittingpatches.html#criteria

Bug#926540: unblock: xorg-server/2:1.20.4-1

[Andreas Boll]

Hi kibi,

On Sat, Apr 06, 2019 at 10:25:31PM +0200, Cyril Brulebois wrote:
> Hi,
> 
> Andreas Boll  (2019-04-06):
> > CCing kibi for unblock-udeb review
> 
> This is coming a little late for RC1 that should be published very soon.
> I've added this to my local todo list but feel free to prod me once RC1
> is published.
> 

Ping :)

Thanks,
Andreas

Bug#928812: unblock: xserver-xorg-video-ati/1:19.0.1-1

[Andreas Boll]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package xserver-xorg-video-ati

It forwards the git snapshot upload 1:18.1.99+git20190207-1 to the final
release including additional fixes and another small stable release
with further fixes.

>From the Debian changelog:
xserver-xorg-video-ati (1:19.0.1-1) unstable; urgency=medium

  [ Timo Aaltonen ]
  * New bugfix release.
- Use radeon_finish in drmmode_crtc_scanout_update. Fixes a crash if
  using exa acceleration (Closes: #924540).
- Revert "glamor: Avoid glamor_create_pixmap for pixmaps backing
  windows". Fixes visual corruption issues (LP: #1822075).

 -- Andreas Boll   Sat, 06 Apr 2019 21:38:04 +0200

xserver-xorg-video-ati (1:19.0.0-1) unstable; urgency=medium

  * New upstream release.

 -- Timo Aaltonen   Tue, 12 Mar 2019 18:40:57 +0200

xserver-xorg-video-ati (1:18.1.99+git20190207-1) unstable; urgency=medium

I've attached a git-diff with the following command:
  git diff 
xserver-xorg-video-ati-1_18.1.99+git20190207-1..xserver-xorg-video-ati-1_19.0.1-1

Further I've attached the output of git-shortlog to list all commit
titles.

unblock xserver-xorg-video-ati/1:19.0.1-1

Thanks,
Andreas
diff --git a/configure.ac b/configure.ac
index 84f25cfd..49e82fc8 100644
--- a/configure.ac
+++ b/configure.ac
@@ -23,7 +23,7 @@
 # Initialize Autoconf
 AC_PREREQ([2.60])
 AC_INIT([xf86-video-ati],
-[18.1.99],
+[19.0.1],
 [https://bugs.freedesktop.org/enter_bug.cgi?product=xorg=Driver/Radeon],
 [xf86-video-ati])
 
diff --git a/debian/changelog b/debian/changelog
index 6d2f0e6f..0c3bda3a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+xserver-xorg-video-ati (1:19.0.1-1) unstable; urgency=medium
+
+  [ Timo Aaltonen ]
+  * New bugfix release.
+- Use radeon_finish in drmmode_crtc_scanout_update. Fixes a crash if
+  using exa acceleration (Closes: #924540).
+- Revert "glamor: Avoid glamor_create_pixmap for pixmaps backing
+  windows". Fixes visual corruption issues (LP: #1822075).
+
+ -- Andreas Boll   Sat, 06 Apr 2019 21:38:04 +0200
+
+xserver-xorg-video-ati (1:19.0.0-1) unstable; urgency=medium
+
+  * New upstream release.
+
+ -- Timo Aaltonen   Tue, 12 Mar 2019 18:40:57 +0200
+
 xserver-xorg-video-ati (1:18.1.99+git20190207-1) unstable; urgency=medium
 
   * New upstream snapshot.
diff --git a/src/drmmode_display.c b/src/drmmode_display.c
index 71f3539f..0e9e2474 100644
--- a/src/drmmode_display.c
+++ b/src/drmmode_display.c
@@ -785,7 +785,7 @@ drmmode_crtc_scanout_update(xf86CrtcPtr crtc, DisplayModePtr mode,
 	 screen->GetWindowPixmap(screen->root),
 	 extents)) {
 			RegionEmpty(DamageRegion(drmmode_crtc->scanout_damage));
-			radeon_glamor_finish(scrn);
+			radeon_finish(scrn, drmmode_crtc->scanout[scanout_id].bo);
 
 			if (!drmmode_crtc->flip_pending) {
 radeon_drm_abort_entry(drmmode_crtc->
@@ -1576,6 +1576,51 @@ drmmode_output_mode_valid(xf86OutputPtr output, DisplayModePtr pModes)
 	return MODE_OK;
 }
 
+static void
+drmmode_output_attach_tile(xf86OutputPtr output)
+{
+#if XORG_VERSION_CURRENT >= XORG_VERSION_NUMERIC(1, 17, 99, 901, 0)
+	drmmode_output_private_ptr drmmode_output = output->driver_private;
+	drmModeConnectorPtr koutput = drmmode_output->mode_output;
+	RADEONEntPtr pRADEONEnt = RADEONEntPriv(output->scrn);
+	struct xf86CrtcTileInfo tile_info, *set = NULL;
+	int i;
+
+	if (!koutput) {
+		xf86OutputSetTile(output, NULL);
+		return;
+	}
+
+	/* look for a TILE property */
+	for (i = 0; i < koutput->count_props; i++) {
+		drmModePropertyPtr props;
+		props = drmModeGetProperty(pRADEONEnt->fd, koutput->props[i]);
+		if (!props)
+			continue;
+
+		if (!(props->flags & DRM_MODE_PROP_BLOB)) {
+			drmModeFreeProperty(props);
+			continue;
+		}
+
+		if (!strcmp(props->name, "TILE")) {
+			drmModeFreePropertyBlob(drmmode_output->tile_blob);
+			drmmode_output->tile_blob =
+drmModeGetPropertyBlob(pRADEONEnt->fd,
+		   koutput->prop_values[i]);
+		}
+		drmModeFreeProperty(props);
+	}
+	if (drmmode_output->tile_blob) {
+		if (xf86OutputParseKMSTile(drmmode_output->tile_blob->data,
+	   drmmode_output->tile_blob->length,
+	   _info) == TRUE)
+			set = _info;
+	}
+	xf86OutputSetTile(output, set);
+#endif
+}
+
 static int
 koutput_get_prop_idx(int fd, drmModeConnectorPtr koutput,
 int type, const char *name)
@@ -1648,6 +1693,8 @@ drmmode_output_get_modes(xf86OutputPtr output)
 	}
 	xf86OutputSetEDID(output, mon);
 
+	drmmode_output_attach_tile(output);
+
 	/* modes should already be available */
 	for (i = 0; i < koutput->count_modes; i++) {
 		Mode = xnfalloc(sizeof(DisplayModeRec));
@@ -1665,8 +1712,11 @@ drmmode_output_destroy(xf86OutputPtr output)
 	drmmode_output_private_ptr drmmode_output = output->driver_private;
 	i

Bug#928807: unblock: mesa/18.3.6-2

[Andreas Boll]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package mesa

This unblock request contains a stable upstream release with lots of
bug fixes for mesa's graphics drivers including fixes for driver
crashes and visual corruption. It fixes two RC bugs (#922346,
#926857).

Debian changelog diff:
mesa (18.3.6-2) unstable; urgency=medium

  * Cherry-pick c77acc3ceba (meson: remove meson-created megadrivers
symlinks) from upstream master branch. Removes a broken symlink
(Closes: #926857).

 -- Andreas Boll   Sat, 11 May 2019 15:43:07 +0200

mesa (18.3.6-1) unstable; urgency=medium

  [ Timo Aaltonen ]
  * libgl1-mesa-dri: Remove /etc/drirc which isn't installed anymore.
(Closes: #920241)

  [ Andreas Boll ]
  * New upstream release.
- wayland/egl: Ensure EGL surface is resized on DRI
  update_buffers(). Fixes a crash with xwayland (Closes: #922346).
  * Rebase patches/fix-hurd-ftbfs.diff.

 -- Andreas Boll   Sat, 06 Apr 2019 20:58:43 +0200


I've attached a git-diff with the following command:
  git diff mesa-18.3.4-2..mesa-18.3.6-2

Further I've attached the output of git-shortlog to list all commit
titles.

unblock mesa/18.3.6-2

Thanks,
Andreas
diff --git a/VERSION b/VERSION
index 0548779ef21..d63efa719a7 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-18.3.4
+18.3.6
diff --git a/bin/.cherry-ignore b/bin/.cherry-ignore
index d69c2cacb4f..1041997a21e 100644
--- a/bin/.cherry-ignore
+++ b/bin/.cherry-ignore
@@ -36,3 +36,19 @@ cbd1ad6165f0aea7fb7c6fd1b36ad5317dd65cb7 st/mesa: require RGBA2, RGB4, and RGBA4
 
 # stable The commit addresses functionality not present in branch
 1b8983c25be19073c02fe9630e949be55f8280fa radv: fix using LOAD_CONTEXT_REG with old GFX ME firmwares on GFX8
+
+# stable Explicit 19.0 only nominations, require work which did not land in branch
+8ab95b849e66f3221d80a67eef2ec6e3730901a8 anv: Refactor descriptor pushing a bit
+5c30fffeec1732c21d600c036f95f8cdb1bb5487 anv: Take references to push descriptor set layouts
+
+# shaCommit references invalid sha - a offender did not land in branch.
+85ee157283c667372baf7c03259cba08853f0067 gitlab-ci: autotools needs to be told which llvm version to use
+
+# revert The commit was reverted shortly after it was applied on master
+47fc359822494935852de1e70e4d840b2fe6a25c anv: release memory allocated by glsl types during spirv_to_nir
+
+# stable Explicitly 19.0 nomination, seemingly a performance patch
+5ef2b8f1f2ebcdb4ffe5c98b3f4f48e584cb4b22 nir: Add a pass for lowering IO back to vector when possible
+
+# fixes Temporary block perf. fix depending on previous opt. pass
+6d5d89d25a0a4299dbfcbfeca71b6c7e65ef3d45 intel/nir: Vectorize all IO
diff --git a/bin/install_megadrivers.py b/bin/install_megadrivers.py
index d29b1911218..b5ac78887bf 100644
--- a/bin/install_megadrivers.py
+++ b/bin/install_megadrivers.py
@@ -35,7 +35,11 @@ def main():
 args = parser.parse_args()
 
 if os.path.isabs(args.libdir):
-to = os.path.join(os.environ.get('DESTDIR', '/'), args.libdir[1:])
+destdir = os.environ.get('DESTDIR')
+if destdir:
+to = os.path.join(destdir, args.libdir[1:])
+else:
+to = args.libdir
 else:
 to = os.path.join(os.environ['MESON_INSTALL_DESTDIR_PREFIX'], args.libdir)
 
@@ -45,7 +49,6 @@ def main():
 if os.path.lexists(to):
 os.unlink(to)
 os.makedirs(to)
-shutil.copy(args.megadriver, master)
 
 for driver in args.drivers:
 abs_driver = os.path.join(to, driver)
@@ -67,7 +70,14 @@ def main():
 name, ext = os.path.splitext(name)
 finally:
 os.chdir(ret)
+
+# Remove meson-created master .so and symlinks
 os.unlink(master)
+name, ext = os.path.splitext(master)
+while ext != '.so':
+if os.path.lexists(name):
+os.unlink(name)
+name, ext = os.path.splitext(name)
 
 
 if __name__ == '__main__':
diff --git a/debian/changelog b/debian/changelog
index 4d94b368e1f..70ce002e9c5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,25 @@
+mesa (18.3.6-2) unstable; urgency=medium
+
+  * Cherry-pick c77acc3ceba (meson: remove meson-created megadrivers
+symlinks) from upstream master branch. Removes a broken symlink
+(Closes: #926857).
+
+ -- Andreas Boll   Sat, 11 May 2019 15:43:07 +0200
+
+mesa (18.3.6-1) unstable; urgency=medium
+
+  [ Timo Aaltonen ]
+  * libgl1-mesa-dri: Remove /etc/drirc which isn't installed anymore.
+(Closes: #920241)
+
+  [ Andreas Boll ]
+  * New upstream release.
+- wayland/egl: Ensure EGL surface is resized on DRI
+  update_buffers(). Fixes a crash with xwayland (Closes: #922346).
+  * Rebase patches/fix-hurd-ftbfs.diff.
+
+ -- Andreas Boll   Sat, 06 Apr 2019 20:58:43 +0200
+
 mesa (18.3.4-2) unstable; urgency=medium
 
   * Cherry-pick f6556ec7d12 (dri: meson: do not prefix user provided dri-
diff --git a/debian/gbp.conf

Bug#920665: xwayland: Crash with external display, notifications, and screen idle [upstream patch attached]

[Andreas Boll]

Hi,

On Thu, Apr 04, 2019 at 04:30:31PM +0300, csaavedra...@gmail.com wrote:
> I see that this landed in unstable (in the next upstream release) but
> testing is still affected, as it's frozen. I installed testing in a new
> machine and I have hit this crasher again. I think this should be
> considered serious enough to be fixed in testing/upcoming stable.

Yeah, as testing is currently frozen an unblock request is required to
unblock xorg-server/2:1.20.4-1 and thus allow it to migrate to
testing. I've filed such a request at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926540

Thanks,
Andreas

Bug#926540: unblock: xorg-server/2:1.20.4-1

[Andreas Boll]

CCing kibi for unblock-udeb review

On Sat, Apr 06, 2019 at 07:13:34PM +0200, Andreas Boll wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package xorg-server:
> 
> This stable release fixes a bunch of important issues including
> xserver crashes. There are multiple fixes related to xwayland, present
> and modesetting.
> 
> Debian changelog entry:
> xorg-server (2:1.20.4-1) unstable; urgency=medium
> 
>   [ Timo Aaltonen ]
>   * New upstream release.
> - present/wnmd: Fix use after free on CRTC removal
>   (Closes: #920665).
> - xwayland: Replace xwl_window::present_window with
>   ::present_flipped (Closes: #921734).
> 
>   [ Andreas Boll ]
>   * Refresh 07_use-modesetting-driver-by-default-on-GeForce.diff.
> 
>  -- Andreas Boll   Tue, 05 Mar 2019 21:11:12 +0100
> 
> 
> Further I've attached a git-diff with the following command to exclude
> uninteresting CI stuff and tests to make the diff more readable:
> 
> git diff xorg-server-2_1.20.3-1..xorg-server-2_1.20.4-1 -- . ':(exclude)test' 
> ':(exclude).gitlab-ci*' ':(exclude).travis.yml' > ../xorg-server_1.20.4-1.diff
> 
> I've also attached the output of git-shortlog to list all commit
> titles.
> 
> unblock xorg-server/2:1.20.4-1
> 
> Thanks,
> Andreas

Bug#926540: unblock: xorg-server/2:1.20.4-1

[Andreas Boll]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package xorg-server:

This stable release fixes a bunch of important issues including
xserver crashes. There are multiple fixes related to xwayland, present
and modesetting.

Debian changelog entry:
xorg-server (2:1.20.4-1) unstable; urgency=medium

  [ Timo Aaltonen ]
  * New upstream release.
- present/wnmd: Fix use after free on CRTC removal
  (Closes: #920665).
- xwayland: Replace xwl_window::present_window with
  ::present_flipped (Closes: #921734).

  [ Andreas Boll ]
  * Refresh 07_use-modesetting-driver-by-default-on-GeForce.diff.

 -- Andreas Boll   Tue, 05 Mar 2019 21:11:12 +0100


Further I've attached a git-diff with the following command to exclude
uninteresting CI stuff and tests to make the diff more readable:

git diff xorg-server-2_1.20.3-1..xorg-server-2_1.20.4-1 -- . ':(exclude)test' 
':(exclude).gitlab-ci*' ':(exclude).travis.yml' > ../xorg-server_1.20.4-1.diff

I've also attached the output of git-shortlog to list all commit
titles.

unblock xorg-server/2:1.20.4-1

Thanks,
Andreas
diff --git a/Makefile.am b/Makefile.am
index 32d4d21e76..19511f765d 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -72,7 +72,7 @@ pkgconfigdir = $(libdir)/pkgconfig
 pkgconfig_DATA = xorg-server.pc
 endif
 
-EXTRA_DIST = xorg-server.pc.in xorg-server.m4 autogen.sh
+EXTRA_DIST = xorg-server.pc.in xorg-server.m4 autogen.sh README.md
 
 DISTCHECK_CONFIGURE_FLAGS=\
 	--with-xkb-path=$(XKB_BASE_DIRECTORY) \
diff --git a/README b/README.md
similarity index 65%
rename from README
rename to README.md
index 529526d189..bc39f41cd4 100644
--- a/README
+++ b/README.md
@@ -1,4 +1,5 @@
-	X Server
+X Server
+
 
 The X server accepts requests from client applications to create windows,
 which are (normally rectangular) "virtual screens" that the client program
@@ -16,29 +17,19 @@ https://en.wikipedia.org/wiki/X_server
 All questions regarding this software should be directed at the
 Xorg mailing list:
 
-https://lists.freedesktop.org/mailman/listinfo/xorg
-
-Please submit bug reports to the Xorg bugzilla:
-
-https://bugs.freedesktop.org/enter_bug.cgi?product=xorg
+  https://lists.freedesktop.org/mailman/listinfo/xorg
 
 The master development code repository can be found at:
 
-git://anongit.freedesktop.org/git/xorg/xserver
-
-https://cgit.freedesktop.org/xorg/xserver
+  https://gitlab.freedesktop.org/xorg/xserver
 
 For patch submission instructions, see:
 
-	https://www.x.org/wiki/Development/Documentation/SubmittingPatches
-
-For more information on the git code manager, see:
-
-https://wiki.x.org/wiki/GitPage
+  https://www.x.org/wiki/Development/Documentation/SubmittingPatches
 
 As with other projects hosted on freedesktop.org, X.Org follows its
 Code of Conduct, based on the Contributor Covenant. Please conduct
 yourself in a respectful and civilized manner when using the above
 mailing lists, bug trackers, etc:
 
-	https://www.freedesktop.org/wiki/CodeOfConduct
+  https://www.freedesktop.org/wiki/CodeOfConduct
diff --git a/Xi/xibarriers.c b/Xi/xibarriers.c
index d0be701352..1926762add 100644
--- a/Xi/xibarriers.c
+++ b/Xi/xibarriers.c
@@ -611,7 +611,9 @@ CreatePointerBarrierClient(ClientPtr client,
 }
 pbd->deviceid = dev->id;
 
+input_lock();
 xorg_list_add(>entry, >per_device);
+input_unlock();
 }
 
 ret->id = stuff->barrier;
@@ -626,7 +628,9 @@ CreatePointerBarrierClient(ClientPtr client,
 ret->barrier.directions &= ~(BarrierPositiveX | BarrierNegativeX);
 if (barrier_is_vertical(>barrier))
 ret->barrier.directions &= ~(BarrierPositiveY | BarrierNegativeY);
+input_lock();
 xorg_list_add(>entry, >barriers);
+input_unlock();
 
 *client_out = ret;
 return Success;
@@ -689,7 +693,9 @@ BarrierFreeBarrier(void *data, XID id)
 mieqEnqueue(dev, (InternalEvent *) );
 }
 
+input_lock();
 xorg_list_del(>entry);
+input_unlock();
 
 FreePointerBarrierClient(c);
 return Success;
@@ -709,7 +715,9 @@ static void add_master_func(void *res, XID id, void *devid)
 pbd = AllocBarrierDevice();
 pbd->deviceid = *deviceid;
 
+input_lock();
 xorg_list_add(>entry, >per_device);
+input_unlock();
 }
 
 static void remove_master_func(void *res, XID id, void *devid)
@@ -752,7 +760,9 @@ static void remove_master_func(void *res, XID id, void *devid)
 mieqEnqueue(dev, (InternalEvent *) );
 }
 
+input_lock();
 xorg_list_del(>entry);
+input_unlock();
 free(pbd);
 }
 
diff --git a/configure.ac b/configure.ac
index 80f0ce7853..30544218a6 100644
--- a/configure.ac
+++ b/configure.ac
@@ -26,9 +26,9 @@ dnl
 dnl Process this file with autoconf to create configure.
 
 AC_PREREQ(2.60)
-AC_INIT([xorg-server], 1.20.3, [https://bugs.fr

Bug#926085: unblock: qreator/16.06.1-3.1

[Andreas Boll]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package qreator

This version fixes the rc bug #900573. It fixes a program crash due to
incorrect PIL imports. See also the attached debdiff.

unblock qreator/16.06.1-3.1

Thanks,
Andreas
diff -Nru qreator-16.06.1/debian/changelog qreator-16.06.1/debian/changelog
--- qreator-16.06.1/debian/changelog2018-04-14 14:48:31.0 +0200
+++ qreator-16.06.1/debian/changelog2019-03-30 20:35:12.0 +0100
@@ -1,3 +1,11 @@
+qreator (16.06.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Fix-python-pil-imports.patch, fixes a program crash due to
+incorrect PIL imports (Closes: #900573).
+
+ -- Andreas Boll   Sat, 30 Mar 2019 20:35:12 +0100
+
 qreator (16.06.1-3) unstable; urgency=medium
 
   * [207e2e1] Port qreator to libnm (Closes: #857227)
diff -Nru qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch 
qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch
--- qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch 1970-01-01 
01:00:00.0 +0100
+++ qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch 2019-03-27 
21:45:38.0 +0100
@@ -0,0 +1,22 @@
+Author: Andreas Boll 
+Date:   Wed Mar 27 21:09:41 2019 +0100
+
+Fix python-pil imports
+
+Fixes bug #900573
+
+diff --git a/qreator/QRCode.py b/qreator/QRCode.py
+index d3a0130..930a538 100644
+--- a/qreator/QRCode.py
 b/qreator/QRCode.py
+@@ -20,8 +20,8 @@ try:
+ except ImportError:
+ print "You need to install the python-qrencode package"
+ sys.exit(1)
+-import Image
+-import ImageOps
++from PIL import Image
++from PIL import ImageOps
+ import cairo
+ import array
+
diff -Nru qreator-16.06.1/debian/patches/series 
qreator-16.06.1/debian/patches/series
--- qreator-16.06.1/debian/patches/series   2018-04-14 14:48:31.0 
+0200
+++ qreator-16.06.1/debian/patches/series   2019-03-27 21:45:54.0 
+0100
@@ -3,3 +3,4 @@
 Port-to-geoclue-2.0.patch
 Port-to-libnm.patch
 Fix-IndexError-when-a-wifi-network-has-100-strength.patch
+Fix-python-pil-imports.patch

Bug#900573: qreator: Proposed patch to fix the crash

[Andreas Boll]

On Thu, Mar 28, 2019 at 10:22:31PM +0800, Chow Loong Jin wrote:
> On Wed, Mar 27, 2019 at 10:31:35PM +0100, Andreas Boll wrote:
> > Control: severity -1 serious
> > Control: tags -1 + patch
> > 
> > Dear maintainer,
> > 
> > I've prepared a patch to fix this issue.
> > Also currently the package qreator isn't useful at all with this issue
> > because it crashes on startup. Thus bumping severity to serious
> > because this package shouldn't end up in Debian Buster without a fix
> > for this issue.
> > 
> > Please let me know if I should upload this fix as NMU or if you like
> > to upload it yourself.
> 
> Please go ahead and upload this fix. Thanks.
> 
> -- 
> Kind regards,
> Loong Jin

Cool, I've uploaded it to sid now.
Attached is the nmudiff.

Thanks,
Andreas
diff -Nru qreator-16.06.1/debian/changelog qreator-16.06.1/debian/changelog
--- qreator-16.06.1/debian/changelog	2018-04-14 14:48:31.0 +0200
+++ qreator-16.06.1/debian/changelog	2019-03-30 20:35:12.0 +0100
@@ -1,3 +1,11 @@
+qreator (16.06.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Fix-python-pil-imports.patch, fixes a program crash due to
+incorrect PIL imports (Closes: #900573).
+
+ -- Andreas Boll   Sat, 30 Mar 2019 20:35:12 +0100
+
 qreator (16.06.1-3) unstable; urgency=medium
 
   * [207e2e1] Port qreator to libnm (Closes: #857227)
diff -Nru qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch
--- qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch	1970-01-01 01:00:00.0 +0100
+++ qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch	2019-03-27 21:45:38.0 +0100
@@ -0,0 +1,22 @@
+Author: Andreas Boll 
+Date:   Wed Mar 27 21:09:41 2019 +0100
+
+Fix python-pil imports
+
+Fixes bug #900573
+
+diff --git a/qreator/QRCode.py b/qreator/QRCode.py
+index d3a0130..930a538 100644
+--- a/qreator/QRCode.py
 b/qreator/QRCode.py
+@@ -20,8 +20,8 @@ try:
+ except ImportError:
+ print "You need to install the python-qrencode package"
+ sys.exit(1)
+-import Image
+-import ImageOps
++from PIL import Image
++from PIL import ImageOps
+ import cairo
+ import array
+
diff -Nru qreator-16.06.1/debian/patches/series qreator-16.06.1/debian/patches/series
--- qreator-16.06.1/debian/patches/series	2018-04-14 14:48:31.0 +0200
+++ qreator-16.06.1/debian/patches/series	2019-03-27 21:45:54.0 +0100
@@ -3,3 +3,4 @@
 Port-to-geoclue-2.0.patch
 Port-to-libnm.patch
 Fix-IndexError-when-a-wifi-network-has-100-strength.patch
+Fix-python-pil-imports.patch


signature.asc
Description: PGP signature

Bug#900573: qreator: Proposed patch to fix the crash

[Andreas Boll]

Control: severity -1 serious
Control: tags -1 + patch

Dear maintainer,

I've prepared a patch to fix this issue.
Also currently the package qreator isn't useful at all with this issue
because it crashes on startup. Thus bumping severity to serious
because this package shouldn't end up in Debian Buster without a fix
for this issue.

Please let me know if I should upload this fix as NMU or if you like
to upload it yourself.

Thanks,
Andreas
diff -Nru qreator-16.06.1/debian/changelog qreator-16.06.1/debian/changelog
--- qreator-16.06.1/debian/changelog	2018-04-14 14:48:31.0 +0200
+++ qreator-16.06.1/debian/changelog	2019-03-27 21:27:47.0 +0100
@@ -1,3 +1,11 @@
+qreator (16.06.1-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add Fix-python-pil-imports.patch, fixes a program crash due to
+incorrect PIL imports (Closes: #900573).
+
+ -- Andreas Boll   Wed, 27 Mar 2019 21:27:47 +0100
+
 qreator (16.06.1-3) unstable; urgency=medium
 
   * [207e2e1] Port qreator to libnm (Closes: #857227)
diff -Nru qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch
--- qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch	1970-01-01 01:00:00.0 +0100
+++ qreator-16.06.1/debian/patches/Fix-python-pil-imports.patch	2019-03-27 21:27:47.0 +0100
@@ -0,0 +1,22 @@
+Author: Andreas Boll 
+Date:   Wed Mar 27 21:09:41 2019 +0100
+
+Fix python-pil imports
+
+Fixes bug #900573
+
+diff --git a/qreator/QRCode.py b/qreator/QRCode.py
+index d3a0130..930a538 100644
+--- a/qreator/QRCode.py
 b/qreator/QRCode.py
+@@ -20,8 +20,8 @@ try:
+ except ImportError:
+ print "You need to install the python-qrencode package"
+ sys.exit(1)
+-import Image
+-import ImageOps
++from PIL import Image
++from PIL import ImageOps
+ import cairo
+ import array
+
diff -Nru qreator-16.06.1/debian/patches/series qreator-16.06.1/debian/patches/series
--- qreator-16.06.1/debian/patches/series	2018-04-14 14:48:31.0 +0200
+++ qreator-16.06.1/debian/patches/series	2019-03-27 21:27:47.0 +0100
@@ -3,3 +3,4 @@
 Port-to-geoclue-2.0.patch
 Port-to-libnm.patch
 Fix-IndexError-when-a-wifi-network-has-100-strength.patch
+Fix-python-pil-imports.patch

Bug#913359: xkbcomp.pc requires libxkbfile-dev as dependency

[Andreas Boll]

tags 913359 +patch
forwarded 913359 
https://gitlab.freedesktop.org/xorg/app/xkbcomp/merge_requests/3
thanks

Hi,

On Tue, Feb 12, 2019 at 01:53:04AM +0600, Judit Foglszinger wrote:
> tags 913359 -patch
> thanks
> 
> > x11-xkb-utils should very much not depend on any -dev package.
> Ok.  Then the patch tag doesn't apply anymore.

I've proposed an alternative patch to fix this issue upstream.
See https://gitlab.freedesktop.org/xorg/app/xkbcomp/merge_requests/3

Thanks,
Andreas

Bug#914316: Fixed in gcc-8 8.2.0-10

[Andreas Boll]

On Sun, Nov 25, 2018 at 1:29 AM Michael Biebl  wrote:
>
> On Sat, 24 Nov 2018 09:33:11 +0100 Sven Joachim  wrote:
> > Source: gcc-8
> > Version: 8.2.0-10
> >
> > The miscompilation of mesa has been fixed in the latest gcc-8 upload,
> > please see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87859 for
> > details.
>
> I recompiled mesa with 8.2.0-10 and I can confirm the fix.
>
> Andreas, thank you for the quick mesa update! Feel free to drop my
> workaround again in one of your next uploads.

Thanks Michael, we have removed your workaround in mesa 18.3.0~rc4-1.

Andreas

Bug#914267: mesa: [regression] with Mesa 18.2.5-2 the charackter model in Tomb Raider is no longer rendered.

[Andreas Boll]

Control: tag -1 pending

On Thu, Nov 22, 2018 at 05:15:17PM +0100, Michael Biebl wrote:
> Control: severity -1 serious
> 
> Hi mesa maintainers,
> 
> after further contemplating about this, I think this bug is ugly enough
> and hard to diagnose for our users, that the package should not enter
> testing in this state.
> I'm thus raising the severity to RC which will prevent testing migration
> and also make the bug more visible to users.
> 
> Regards,
> Michael

Thank you all for reporting and tracking down this issue!
I'll upload Michael's workaround asap.

Thanks,
Andreas

Bug#912462: stretch-pu: package xorg-server/2:1.19.2-1+deb9u5

[Andreas Boll]

Hi Adam, Cyril,

On Thu, Nov 01, 2018 at 06:12:17PM +0100, Cyril Brulebois wrote:
> Hi Adam, Andreas,
> 
> Adam D. Barratt  (2018-10-31):
> > I'd be OK with that, but as xorg-server produces a udeb, it'll need a
> > d-i ack first. CCing KiBi and tagging appropriately.

Great!

> 
> The xserver udeb is configured with --disable-glx, so I suppose this
> glx/glxscreen.c modification isn't impacting any code paths in the udeb?
> (from my reading configure.ac & glx/Makefile.am, plus common sense, but
> I could be wrong)

Yeah, I came to the same conclusion.
I've gone ahead and uploaded it to p-u-new.


Thanks,
Andreas

Bug#912462: stretch-pu: package xorg-server/2:1.19.2-1+deb9u5

[Andreas Boll]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Control: block 908601 by -1

Hi,

I'd like to backport an upstream xorg-server patch to stable to fix
issue #908601. It fixes a kwin regression caused by Mesa >= 18.0. This
issue has already been fixed in xorg-server in unstable and testing.
However with backporting Mesa to stretch-backports this issue has also
been triggered with xorg-server in stretch. Since we don't backport
xorg-server to stretch-backports and the required patch for stretch is
very small I'd like to fix this issue via stretch-pu.

Attached is the debdiff between xorg-server 2:1.19.2-1+deb9u4 and
2:1.19.2-1+deb9u5.

Thanks,
Andreas
diff -u xorg-server-1.19.2/debian/changelog xorg-server-1.19.2/debian/changelog
--- xorg-server-1.19.2/debian/changelog
+++ xorg-server-1.19.2/debian/changelog
@@ -1,3 +1,12 @@
+xorg-server (2:1.19.2-1+deb9u5) stretch; urgency=medium
+
+  * Cherry-pick c2954b16c (glx: do not pick sRGB config for 32-bit RGBA
+visual) from upstream. Fixes various blending issues with kwin and
+Mesa >= 18.0 (i.e. Mesa from stretch-backports) (Closes: #908601).
+Thanks to Nicholas D Steeves and Robert Trebula for testing!
+
+ -- Andreas Boll   Wed, 31 Oct 2018 17:58:03 +0100
+
 xorg-server (2:1.19.2-1+deb9u4) stretch-security; urgency=medium
 
   * Disable -logfile and -modulepath when running with elevated privileges.
diff -u xorg-server-1.19.2/debian/patches/series 
xorg-server-1.19.2/debian/patches/series
--- xorg-server-1.19.2/debian/patches/series
+++ xorg-server-1.19.2/debian/patches/series
@@ -12,0 +13 @@
+12_glx-do-not-pick-sRGB-config-for-32-bit-RGBA-visual.patch
only in patch2:
unchanged:
--- 
xorg-server-1.19.2.orig/debian/patches/12_glx-do-not-pick-sRGB-config-for-32-bit-RGBA-visual.patch
+++ 
xorg-server-1.19.2/debian/patches/12_glx-do-not-pick-sRGB-config-for-32-bit-RGBA-visual.patch
@@ -0,0 +1,31 @@
+commit c2954b16c8730c7ed8441fd8dba25900f3aed265
+Author: Tapani Pälli 
+Date:   Tue Nov 28 09:23:29 2017 +0200
+
+glx: do not pick sRGB config for 32-bit RGBA visual
+
+This fixes blending issues seen with kwin and gnome-shell when
+32bit visual has sRGB capability set.
+
+Reviewed-by: Adam Jackson 
+Signed-off-by: Tapani Pälli 
+Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103699
+Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103646
+Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103655
+
+diff --git a/glx/glxscreens.c b/glx/glxscreens.c
+index 73444152a..596d972e0 100644
+--- a/glx/glxscreens.c
 b/glx/glxscreens.c
+@@ -271,6 +271,11 @@ pickFBConfig(__GLXscreen * pGlxScreen, VisualPtr visual)
+ /* If it's the 32-bit RGBA visual, demand a 32-bit fbconfig. */
+ if (visual->nplanes == 32 && config->rgbBits != 32)
+ continue;
++/* If it's the 32-bit RGBA visual, do not pick sRGB capable config.
++ * This can cause issues with compositors that are not sRGB aware.
++ */
++if (visual->nplanes == 32 && config->sRGBCapable == GL_TRUE)
++continue;
+ /* Can't use the same FBconfig for multiple X visuals.  I think. */
+ if (config->visualID != 0)
+ continue;

Bug#908812: libgl1-mesa-dev: dependency on transitional packages

[Andreas Boll]

Control: tag -1 pending

On Thu, Oct 11, 2018 at 01:32:06PM +0200, Jörg-Volker Peetz wrote:
> Version: 18.1.9-1
> 
> Dear Maintainer(s),
> 
> in version 18.1.9-1 this package still depends on the packages 
> x11proto-dri2-dev and
> x11proto-gl-dev which are marked as transitional.
> 
> Regards,
> Jörg.

This issue has been fixed in mesa 18.2.0-2 / experimental but
unfortunately it is still in NEW.

https://ftp-master.debian.org/new/mesa_18.2.0-2.html

Thanks,
Andreas

Bug#906177: RM: libxatracker2 libxatracker-dev [armel arm64 armhf mips mips64el mipsel ppc64el s390x] -- NBS; needs manual cruft removal

[Andreas Boll]

On Wed, Aug 15, 2018 at 12:08:25PM +0300, Adrian Bunk wrote:
> Package: ftp.debian.org
> Severity: normal
> 
> Manual cruft removal is required for libxatracker2 libxatracker-dev,
> likely due to the build dependency from xserver-xorg-video-vmware.

Friendly ping.
This issue currently blocks mesa from migrating to testing.

Thanks,
Andreas

Bug#904995: xserver-common: black screen with mouse on screen rotate.

[Andreas Boll]

On Thu, Aug 16, 2018 at 10:49:33AM +0200, Michel Dänzer wrote:
> On 2018-08-16 10:27 AM, Simon Polack wrote:
> > The issue seems to be not limited to ATI/AMD graphics, as i face it on
> > intel aswell.
> 
> That's probably a separate bug in the modesetting driver, which might
> indeed be fixed in upstream xserver 1.20.1.

The issue in the modesetting driver has been fixed in xorg-server
2:1.20.1-1 and the issue in xserver-xorg-video-ati will be fixed asap.

Thanks,
Andreas

Bug#848864: libtool: diff for NMU version 2.4.6-2.1

[Andreas Boll]

Control: tags 848864 + pending

Dear maintainer,

I've prepared an NMU for libtool (versioned as 2.4.6-2.1) and uploaded
it to DELAYED/10. This NMU restores most of the original performance
of libtool 2.4.2. Please feel free to tell me if I should delay it
longer.

Thanks,
Andreas
diff -Nru libtool-2.4.6/debian/changelog libtool-2.4.6/debian/changelog
--- libtool-2.4.6/debian/changelog	2016-08-20 14:34:31.0 +0200
+++ libtool-2.4.6/debian/changelog	2018-04-17 19:50:37.0 +0200
@@ -1,3 +1,14 @@
+libtool (2.4.6-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Mitigate exessive sed forking (Closes: #848864):
+- Add 0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch
+- Add 0011-libtool-optimizing-options-parser-hooks.patch
+- Add 0012-funclib-refactor-quoting-methods-a-bit.patch
+- Refresh 0020-libtool-fix-GCC-clang-linking-with-fsanitize.patch
+
+ -- Andreas Boll <ab...@debian.org>  Tue, 17 Apr 2018 19:50:37 +0200
+
 libtool (2.4.6-2) unstable; urgency=medium
 
   * Don't show the debain version in --version, just in --help
diff -Nru libtool-2.4.6/debian/patches/0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch libtool-2.4.6/debian/patches/0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch
--- libtool-2.4.6/debian/patches/0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch	1970-01-01 01:00:00.0 +0100
+++ libtool-2.4.6/debian/patches/0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch	2018-01-19 11:28:13.0 +0100
@@ -0,0 +1,235 @@
+From 32f0df9835ac15ac17e04be57c368172c3ad1d19 Mon Sep 17 00:00:00 2001
+From: Pavel Raiskup <prais...@redhat.com>
+Date: Sun, 4 Oct 2015 21:55:03 +0200
+Subject: [PATCH] libtool: mitigate the $sed_quote_subst slowdown
+
+When it is reasonably possible, use shell implementation for
+quoting.
+
+References:
+http://lists.gnu.org/archive/html/libtool/2015-03/msg5.html
+http://lists.gnu.org/archive/html/libtool/2015-02/msg0.html
+https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20006
+
+* gl/build-aux/funclib.sh (func_quote): New function that can be
+used as substitution for '$SED $sed_quote_subst' call.
+* build-aux/ltmain.in (func_emit_wrapper): Use func_quote instead
+of '$SED $sed_quote_subst'.
+(func_mode_link): Likewise.
+* NEWS: Document.
+* bootstrap: Sync with funclib.sh.
+---
+ NEWS|  3 +++
+ bootstrap   | 61 +++--
+ build-aux/ltmain.in | 10 
+ gl/build-aux/funclib.sh | 61 +++--
+ 4 files changed, 117 insertions(+), 18 deletions(-)
+
+diff --git a/bootstrap b/bootstrap
+index c179f51d..fe9e9cac 100755
+--- a/bootstrap
 b/bootstrap
+@@ -230,7 +230,7 @@ vc_ignore=
+ 
+ # Source required external libraries:
+ # Set a version string for this script.
+-scriptversion=2015-01-20.17; # UTC
++scriptversion=2015-10-04.22; # UTC
+ 
+ # General shell script boiler plate, and helper functions.
+ # Written by Gary V. Vaughan, 2004
+@@ -1257,6 +1257,57 @@ func_relative_path ()
+ }
+ 
+ 
++# func_quote ARG
++# --
++# Aesthetically quote one ARG, store the result into $func_quote_result.  Note
++# that we keep attention to performance here (so far O(N) complexity as long as
++# func_append is O(1)).
++func_quote ()
++{
++$debug_cmd
++
++func_quote_result=$1
++
++case $func_quote_result in
++  *[\\\`\"\$]*)
++case $func_quote_result in
++  *'*'*|*'['*)
++func_quote_result=`$ECHO "$func_quote_result" | $SED "$sed_quote_subst"`
++return 0
++;;
++esac
++
++func_quote_old_IFS=$IFS
++for _G_char in '\' '`' '"' '$'
++do
++  # STATE($1) PREV($2) SEPARATOR($3)
++  set start "" ""
++  func_quote_result=dummy"$_G_char$func_quote_result$_G_char"dummy
++  IFS=$_G_char
++  for _G_part in $func_quote_result
++  do
++case $1 in
++quote)
++  func_append func_quote_result "$3$2"
++  set quote "$_G_part" "\\$_G_char"
++  ;;
++start)
++  set first "" ""
++  func_quote_result=
++  ;;
++first)
++  set quote "$_G_part" ""
++  ;;
++esac
++  done
++  IFS=$func_quote_old_IFS
++done
++;;
++  *) ;;
++esac
++}
++
++
+ # func_quote_for_eval ARG...
+ # --
+ # Aesthetically quote ARGs to be evaled later.
+@@ -1273,12 +1324,8 @@ func_quote_for_eval ()
+ func_quote_for_eval_unquoted_result=
+ func_quote_for_eval_result=
+ while test 0 -lt $#; do
+-  case $1 in
+-*[\\\`\"\$]*)
+-	  _G_unquoted_arg=`printf '%s\n' "$1" |$SED "$sed_

Bug#890866: mesa: regression vs mesa 17.3.3-1: crash on i915 triggered by running emacs

[Andreas Boll]

Control: severity -1 serious
Control: tags -1 upstream
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=105169

On Mon, Feb 19, 2018 at 08:06:49PM -0500, Theodore Y. Ts'o wrote:
> Source: mesa
> Version: 17.3.4-1
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrading to Mesa 17.3.4-1, starting emacs (in X11) would reliably
> cause the X server to crash.   Reverting to mesa 17.3.3-1 with the
> following packages:
> 
> libegl1-mesa_17.3.3-1_amd64.deb
> libegl-mesa0_17.3.3-1_amd64.deb
> libgbm1_17.3.3-1_amd64.deb
> libgl1-mesa-dri_17.3.3-1_amd64.deb
> libgl1-mesa-glx_17.3.3-1_amd64.deb
> libglapi-mesa_17.3.3-1_amd64.deb
> libglx-mesa0_17.3.3-1_amd64.deb
> libwayland-egl1-mesa_17.3.3-1_amd64.deb
> mesa-va-drivers_17.3.3-1_amd64.deb
> mesa-vdpau-drivers_17.3.3-1_amd64.deb
> 
> Causes the problem to go away.  This was running on a 2018 Dell XPS 13
> (model number 9370) with a 4k display.  Found in dmesg was the
> following:
> 
> Feb 19 14:07:00 cwcc kernel: [ 1740.829003] [drm] GPU HANG: ecode 
> 9:0:0x85df3cff, in Xorg [1098], reason: Hang on rcs0, action: reset
> Feb 19 14:07:00 cwcc kernel: [ 1740.829111] [drm] GPU hangs can indicate a 
> bug anywhere in the entire gfx stack, including userspace.
> Feb 19 14:07:00 cwcc kernel: [ 1740.829112] [drm] Please file a _new_ bug 
> report on bugs.freedesktop.org against DRI -> DRM/Intel
> Feb 19 14:07:00 cwcc kernel: [ 1740.829113] [drm] drm/i915 developers can 
> then reassign to the right component if it's not a kernel issue.
> Feb 19 14:07:00 cwcc kernel: [ 1740.829114] [drm] The gpu crash dump is 
> required to analyze gpu hangs, so please always attach it.
> Feb 19 14:07:00 cwcc kernel: [ 1740.829115] [drm] GPU crash dump saved to 
> /sys/class/drm/card0/error
> Feb 19 14:07:00 cwcc kernel: [ 1740.829123] i915 :00:02.0: Resetting rcs0 
> after gpu hang
> Feb 19 14:07:08 cwcc kernel: [ 1748.819899] i915 :00:02.0: Resetting rcs0 
> after gpu hang
> 

Hi,

Thanks for reporting to upstream!
Could you test Mesa 18.0.0~rc4-1 from experimental? According to [1]
some GPU hangs are supposed to be fixed.

Thanks,
Andreas

[1] https://bugs.freedesktop.org/show_bug.cgi?id=104578#c17


signature.asc
Description: PGP signature

Bug#890485: xserver-xorg-core 1.19.6 crash

[Andreas Boll]

On Fri, Feb 16, 2018 at 01:11:20PM +0100, Marek Vasut wrote:
> On 02/16/2018 11:47 AM, Andreas Boll wrote:
> > On Thu, Feb 15, 2018 at 09:54:43AM +0100, Marek Vasut wrote:
> >> Package: xserver-xorg-core
> >> Version: 2:1.19.6-1
> >>
> >> After update from 2:1.19.5-1 crashes with
> >>
> >> (EE) Backtrace:
> >> (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x555939ea4e3d]
> >> (EE) 1: /usr/lib/xorg/Xorg (0x555939ced000+0x1bbbd9) [0x555939ea8bd9]
> >> (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f3fc30fa000+0x12180)
> >> [0x7f3fc310c180]
> >> (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x110) [0x7f3fc2d786a0]
> >> (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x1c7) [0x7f3fc2d79cf7]
> >> (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3fc2d44000+0x76f87)
> >> [0x7f3fc2dbaf87]
> >> (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3fc2d44000+0x7d27a)
> >> [0x7f3fc2dc127a]
> >> (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3fc2d44000+0x7efdc)
> >> [0x7f3fc2dc2fdc]
> >> (EE) 8: /usr/lib/xorg/Xorg (PanoramiXCreateConnectionBlock+0x22d)
> >> [0x555939deaeed]
> >> (EE) 9: /usr/lib/xorg/Xorg (0x555939ced000+0x56d79) [0x555939d43d79]
> >> (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xea)
> >> [0x7f3fc2d64f2a]
> >> (EE) 11: /usr/lib/xorg/Xorg (_start+0x2a) [0x555939d2da3a]
> >> (EE)
> >> (EE)
> >> error:
> >> (EE) Caught signal 6 (Aborted). Server aborting
> >>
> >> Note that this did not crash in 1.19.5-1 and compiling this tag from
> >> debian xorg git makes the X11 work again, so something changed between
> >> those two revisions -- 1.19.5-1 and 1.19.6-1 .

The biggest change between those revisions is the new upstream
xorg-server release 1.19.6. [1]

> >>
> > Please report this upstream at
> > https://bugs.freedesktop.org/enter_bug.cgi?product=xorg=Server%2FExt%2FXinerama
> > and let us know the bug number for tracking.
> 
> But this is a bug in the debian-patched X11 packages ?

It's most likely a bug introduced with the new upstream release.
There's only one newly added Debian-only patch
(07-glx-do-not-pick-srgb-config-for-32bit-rgba-visual.diff). All the
other changes documented in debian/changelog are packaging related
changes. You could try to disable this patch by commenting the patch
in the debian/patches/series file and rebuilding xorg-server. Though I
don't think your issue is caused by this patch.

Thanks,
Andreas

[1] https://lists.x.org/archives/xorg-announce/2017-December/002830.html

> 
> -- 
> Best regards,
> Marek Vasut


signature.asc
Description: PGP signature

Bug#890485: xserver-xorg-core 1.19.6 crash

[Andreas Boll]

On Thu, Feb 15, 2018 at 09:54:43AM +0100, Marek Vasut wrote:
> Package: xserver-xorg-core
> Version: 2:1.19.6-1
> 
> After update from 2:1.19.5-1 crashes with
> 
> (EE) Backtrace:
> (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x555939ea4e3d]
> (EE) 1: /usr/lib/xorg/Xorg (0x555939ced000+0x1bbbd9) [0x555939ea8bd9]
> (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f3fc30fa000+0x12180)
> [0x7f3fc310c180]
> (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x110) [0x7f3fc2d786a0]
> (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x1c7) [0x7f3fc2d79cf7]
> (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3fc2d44000+0x76f87)
> [0x7f3fc2dbaf87]
> (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3fc2d44000+0x7d27a)
> [0x7f3fc2dc127a]
> (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3fc2d44000+0x7efdc)
> [0x7f3fc2dc2fdc]
> (EE) 8: /usr/lib/xorg/Xorg (PanoramiXCreateConnectionBlock+0x22d)
> [0x555939deaeed]
> (EE) 9: /usr/lib/xorg/Xorg (0x555939ced000+0x56d79) [0x555939d43d79]
> (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xea)
> [0x7f3fc2d64f2a]
> (EE) 11: /usr/lib/xorg/Xorg (_start+0x2a) [0x555939d2da3a]
> (EE)
> (EE)
> error:
> (EE) Caught signal 6 (Aborted). Server aborting
> 
> Note that this did not crash in 1.19.5-1 and compiling this tag from
> debian xorg git makes the X11 work again, so something changed between
> those two revisions -- 1.19.5-1 and 1.19.6-1 .
> 
> I use Xinerama though, which did trigger bugs in the past, xorg.conf below:
> Section "ServerLayout"
> Identifier  "Layout0"
> Option  "Xinerama"  "on"
> Option  "Clone" "off"
> Screen  0   "Screen0"
> Screen  1   "Screen1"   RightOf "Screen0"
> Screen  2   "Screen2"   LeftOf  "Screen3"
> Screen  3   "Screen3"   LeftOf  "Screen0"
> EndSection
> 
> Section "Device"
> Identifier  "Device0"
> Driver  "nouveau"
> BusID   "PCI:5:0:0"
> Option  "ZaphodHeads"   "DP-1"
> Screen  0
> EndSection
> 
> Section "Device"
> Identifier  "Device1"
> Driver  "nouveau"
> BusID   "PCI:5:0:0"
> Option  "ZaphodHeads"   "DP-2"
> Screen  1
> EndSection
> 
> Section "Device"
> Identifier  "Device2"
> Driver  "nouveau"
> BusID   "PCI:6:0:0"
> Option  "ZaphodHeads"   "DP-3"
> Screen  0
> EndSection
> 
> Section "Device"
> Identifier  "Device3"
> Driver  "nouveau"
> BusID   "PCI:6:0:0"
> Option  "ZaphodHeads"   "DP-4"
> Screen  1
> EndSection
> 
> Section "Screen"
> Identifier  "Screen0"
> Device  "Device0"
> Monitor "Monitor0"
> DefaultDepth24
> Option  "Rotate""left"
> SubSection  "Display"
> Modes   "2560x1440"
> Depth   24
> EndSubSection
> EndSection
> 
> Section "Screen"
> Identifier  "Screen1"
> Device  "Device1"
> Monitor "Monitor1"
> DefaultDepth24
> Option  "Rotate""left"
> SubSection  "Display"
> Modes   "2560x1440"
> Depth   24
> EndSubSection
> EndSection
> 
> Section "Screen"
> Identifier  "Screen2"
> Device  "Device2"
> Monitor "Monitor2"
> DefaultDepth24
> Option  "Rotate""left"
> SubSection  "Display"
> Modes   "2560x1440"
> Depth   24
> EndSubSection
> EndSection
> 
> Section "Screen"
> Identifier  "Screen3"
> Device  "Device3"
> Monitor "Monitor3"
> DefaultDepth24
> Option  "Rotate""left"
> SubSection  "Display"
> Modes   "2560x1440"
> Depth   24
> EndSubSection
> EndSection
> 
> Section "Monitor"
> Identifier  "Monitor0"
> Option  "Rotate""left"
> EndSection
> 
> Section "Monitor"
> Identifier  "Monitor1"
> Option  "Rotate""left"
> EndSection
> 
> Section "Monitor"
> Identifier  "Monitor2"
> Option  "Rotate""left"
> EndSection
> 
> Section "Monitor"
> Identifier  "Monitor3"
> Option  "Rotate""left"
> EndSection
> 
> -- 
> Best regards,
> Marek Vasut

Please report this upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg=Server%2FExt%2FXinerama
and let us know the bug number for tracking.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#889979: Composite extension broken

[Andreas Boll]

On Fri, Feb 09, 2018 at 06:07:00PM +0200, Theodore Lytras wrote:
> Package: xserver-xephyr
> Version: 1:1.19.6-1
> Severity: important
> 
> I use Xephyr to play Sid Meier's Alpha Centauri (yes, people still play 
> that), 
> and this requires disabling its Composite extension (or the game hangs). 
> Unfortunately, on my amd64 machine with Xephyr version 1.19.6 this throws an 
> error (used to work with version 1.19.5):
> 
> $ Xephyr :1 -screen 800x600 -extension Composite
> 
> Xephyr: ../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key-
> >initialized' failed.
> (EE) 
> (EE) Backtrace:
> (EE) 0: Xephyr (xorg_backtrace+0x4d) [0x5608257337bd]
> (EE) 1: Xephyr (0x56082556d000+0x1ca559) [0x560825737559]
> (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0b03af6000+0x12180) 
> [0x7f0b03b08180]
> (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0x110) [0x7f0b037746a0]
> (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x1c7) [0x7f0b03775cf7]
> (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7f0b0374+0x2cfca) 
> [0x7f0b0376cfca]
> (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f0b0374+0x2d042) 
> [0x7f0b0376d042]
> (EE) 7: Xephyr (0x56082556d000+0x3c252) [0x5608255a9252]
> (EE) 8: Xephyr (0x56082556d000+0x1c1c1f) [0x56082572ec1f]
> (EE) 9: Xephyr (0x56082556d000+0x12c667) [0x560825699667]
> (EE) 10: Xephyr (0x56082556d000+0x12bcc5) [0x560825698cc5]
> (EE) 11: Xephyr (0x56082556d000+0x12b115) [0x560825698115]
> (EE) 12: Xephyr (InitExtensions+0x3d) [0x56082562ce2d]
> (EE) 13: Xephyr (0x56082556d000+0x7c93f) [0x5608255e993f]
> (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xea) 
> [0x7f0b03760f2a]
> (EE) 15: Xephyr (_start+0x2a) [0x5608255a92fa]
> (EE) 
> (EE) 
> Fatal server error:
> (EE) Caught signal 6 (Aborted). Server aborting
> (EE) 
> 
> Withour "-extension Composite" Xephyr starts, but unfortunately I can't play 
> the game. Given that this is the only reason I use Xephyr (and I suspect that 
> applies to many people as well), I think this bug qualifies as "important"...

Please report this upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg=Server%2FDDX%2FXephyr
and let us know the bug number for tracking.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#890337: Disabling Trackpoint Scrolling via xorg.conf freezes screen/input

[Andreas Boll]

On Tue, Feb 13, 2018 at 10:11:13AM -0500, Joachim Breitner wrote:
> Package: xserver-xorg-core
> Version: 2:1.19.6-1
> Severity: normal
> 
> I have upgraded xserver-xorg-core and xserver-xorg-legacy from
> 2:1.19.5-1 to 2:1.19.6-1. When I rebooted, the system (a T460s Thinkpad)
> would start, but as soon as the X server is started, the screen would
> turn black and no input would be accepted -- not even switching to the
> text terminal.
> 
> The problem disappeared once I removed the file
> /etc/X11/xorg.conf.d/30-scoll.conf with this content:
> 
> Section "InputClass"
> Identifier "TPPS/2 IBM TrackPoint"
> Driver "libinput"
> Option "ScrollMethod" "none"
> EndSection
> 
> 
> I have added the corresponding xorg log to the list of log files below,
> note how it stops abruptly at
> 
> [   187.857] (II) event9  - (II) Integrated Camera: Integrated C: (II) is 
> tagged by udev as: Keyboard
> [   187.857] (II) event9  - (II) Integrated Camera: Integrated C: (II) device 
> is a keyboard
> [   187.858] (II) config/udev: Adding input device (unnamed) (/dev/ttyS0)
> [   187.858] (**) (unnamed): Applying InputClass "TPPS/2 IBM TrackPoint"
> [   187.858] (II) Using input driver 'libinput' for '(unnamed)'
> [   187.858] (**) (unnamed): always reports core events
> [   187.858] (**) Option "Device" "/dev/ttyS0"
> [   187.858] (**) Option "_source" "server/udev"
> 
> Cheers,
> Joachim

Please report this upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg=Server%2FInput%2FCore
and let us know the bug number for tracking.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#889035: src:llvm-toolchain-5.0: New symbols appeared in the symbols file

[Andreas Boll]

Package: src:llvm-toolchain-5.0
Version: 1:5.0.1-2
Severity: normal

Dear Maintainer,

There are new symbols exported by libclang1-5.0. Please update the symbols
file.

New symbols: (see also build log [1])

--- new_symbol_file (libclang1-5.0_1:5.0.1-2_i386)
+++ dpkg-gensymbolsuaN6L9   2017-12-22 22:00:39.778307536 +
@@ -62,12 +62,14 @@
  clang_Cursor_isAnonymous@LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isBitField@LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isDynamicCall@LLVM_5.0 1:5.0~svn298832-1~
+ clang_Cursor_isExternalSymbol@LLVM_5.0 1:5.0.1-2
  clang_Cursor_isFunctionInlined@LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isMacroBuiltin@LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isMacroFunctionLike@LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isNull@LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isObjCOptional@LLVM_5.0 1:5.0~svn298832-1~
  clang_Cursor_isVariadic@LLVM_5.0 1:5.0~svn298832-1~
+ clang_EnumDecl_isScoped@LLVM_5.0 1:5.0.1-2
  clang_EvalResult_dispose@LLVM_5.0 1:5.0~svn298832-1~
  clang_EvalResult_getAsDouble@LLVM_5.0 1:5.0~svn298832-1~
  clang_EvalResult_getAsInt@LLVM_5.0 1:5.0~svn298832-1~
@@ -187,6 +189,7 @@
  clang_findReferencesInFileWithBlock@LLVM_5.0 1:5.0~svn298832-1~
  clang_formatDiagnostic@LLVM_5.0 1:5.0~svn298832-1~
  clang_free@LLVM_5.0 1:5.0~svn298832-1~
+ clang_getAddressSpace@LLVM_5.0 1:5.0.1-2
  clang_getAllSkippedRanges@LLVM_5.0 1:5.0~svn302377-1~
  clang_getArgType@LLVM_5.0 1:5.0~svn298832-1~
  clang_getArrayElementType@LLVM_5.0 1:5.0~svn298832-1~
@@ -213,6 +216,7 @@
  clang_getCursorCompletionString@LLVM_5.0 1:5.0~svn298832-1~
  clang_getCursorDefinition@LLVM_5.0 1:5.0~svn298832-1~
  clang_getCursorDisplayName@LLVM_5.0 1:5.0~svn298832-1~
+ clang_getCursorExceptionSpecificationType@LLVM_5.0 1:5.0.1-2
  clang_getCursorExtent@LLVM_5.0 1:5.0~svn298832-1~
  clang_getCursorKind@LLVM_5.0 1:5.0~svn298832-1~
  clang_getCursorKindSpelling@LLVM_5.0 1:5.0~svn298832-1~
@@ -249,6 +253,7 @@
  clang_getEnumConstantDeclUnsignedValue@LLVM_5.0 1:5.0~svn298832-1~
  clang_getEnumConstantDeclValue@LLVM_5.0 1:5.0~svn298832-1~
  clang_getEnumDeclIntegerType@LLVM_5.0 1:5.0~svn298832-1~
+ clang_getExceptionSpecificationType@LLVM_5.0 1:5.0.1-2
  clang_getExpansionLocation@LLVM_5.0 1:5.0~svn298832-1~
  clang_getFieldDeclBitWidth@LLVM_5.0 1:5.0~svn298832-1~
  clang_getFile@LLVM_5.0 1:5.0~svn298832-1~
@@ -299,6 +304,7 @@
  clang_getTypeKindSpelling@LLVM_5.0 1:5.0~svn298832-1~
  clang_getTypeSpelling@LLVM_5.0 1:5.0~svn298832-1~
  clang_getTypedefDeclUnderlyingType@LLVM_5.0 1:5.0~svn298832-1~
+ clang_getTypedefName@LLVM_5.0 1:5.0.1-2
  clang_hashCursor@LLVM_5.0 1:5.0~svn298832-1~
  clang_indexLoc_getCXSourceLocation@LLVM_5.0 1:5.0~svn298832-1~
  clang_indexLoc_getFileLocation@LLVM_5.0 1:5.0~svn298832-1~
@@ -344,6 +350,7 @@
  clang_reparseTranslationUnit@LLVM_5.0 1:5.0~svn298832-1~
  clang_saveTranslationUnit@LLVM_5.0 1:5.0~svn298832-1~
  clang_sortCodeCompletionResults@LLVM_5.0 1:5.0~svn298832-1~
+ clang_suspendTranslationUnit@LLVM_5.0 1:5.0.1-2
  clang_toggleCrashRecovery@LLVM_5.0 1:5.0~svn298832-1~
  clang_tokenize@LLVM_5.0 1:5.0~svn298832-1~
  clang_visitChildren@LLVM_5.0 1:5.0~svn298832-1~


For easier detection of such issues I'd recommend bumping the dpkg-gensymbols
checker level to 4. This will cause the build to fail if there are any symbol
changes (added or removed).

e.g.
- dh_makeshlibs -plibclang1-5.0 -V"libclang1-5.0 (>= 1:5.0~svn298832-1~)"
+ dh_makeshlibs -plibclang1-5.0 -V"libclang1-5.0 (>= 1:5.0~svn298832-1~)" -- -c4


Thanks,
Andreas

[1] 
https://buildd.debian.org/status/fetch.php?pkg=llvm-toolchain-5.0=i386=1%3A5.0.1-2=1513980534=0

Bug#848864: libtool: diff for NMU version 2.4.6-2.1

[Andreas Boll]

Control: tags 848864 + patch

Dear maintainer,

I've prepared an NMU for libtool (versioned as 2.4.6-2.1) to fix this
issue. This NMU restores most of the original performance of libtool
2.4.2.

Please review.

Thanks,
Andreas
diff -Nru libtool-2.4.6/debian/changelog libtool-2.4.6/debian/changelog
--- libtool-2.4.6/debian/changelog	2016-08-20 14:34:31.0 +0200
+++ libtool-2.4.6/debian/changelog	2018-01-19 11:37:19.0 +0100
@@ -1,3 +1,14 @@
+libtool (2.4.6-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Mitigate exessive sed forking (Closes: #848864):
+- Add 0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch
+- Add 0011-libtool-optimizing-options-parser-hooks.patch
+- Add 0012-funclib-refactor-quoting-methods-a-bit.patch
+- Refresh 0020-libtool-fix-GCC-clang-linking-with-fsanitize.patch
+
+ -- Andreas Boll <andreas.boll@gmail.com>  Fri, 19 Jan 2018 11:37:19 +0100
+
 libtool (2.4.6-2) unstable; urgency=medium
 
   * Don't show the debain version in --version, just in --help
diff -Nru libtool-2.4.6/debian/patches/0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch libtool-2.4.6/debian/patches/0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch
--- libtool-2.4.6/debian/patches/0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch	1970-01-01 01:00:00.0 +0100
+++ libtool-2.4.6/debian/patches/0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch	2018-01-19 11:28:13.0 +0100
@@ -0,0 +1,235 @@
+From 32f0df9835ac15ac17e04be57c368172c3ad1d19 Mon Sep 17 00:00:00 2001
+From: Pavel Raiskup <prais...@redhat.com>
+Date: Sun, 4 Oct 2015 21:55:03 +0200
+Subject: [PATCH] libtool: mitigate the $sed_quote_subst slowdown
+
+When it is reasonably possible, use shell implementation for
+quoting.
+
+References:
+http://lists.gnu.org/archive/html/libtool/2015-03/msg5.html
+http://lists.gnu.org/archive/html/libtool/2015-02/msg0.html
+https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20006
+
+* gl/build-aux/funclib.sh (func_quote): New function that can be
+used as substitution for '$SED $sed_quote_subst' call.
+* build-aux/ltmain.in (func_emit_wrapper): Use func_quote instead
+of '$SED $sed_quote_subst'.
+(func_mode_link): Likewise.
+* NEWS: Document.
+* bootstrap: Sync with funclib.sh.
+---
+ NEWS|  3 +++
+ bootstrap   | 61 +++--
+ build-aux/ltmain.in | 10 
+ gl/build-aux/funclib.sh | 61 +++--
+ 4 files changed, 117 insertions(+), 18 deletions(-)
+
+diff --git a/bootstrap b/bootstrap
+index c179f51d..fe9e9cac 100755
+--- a/bootstrap
 b/bootstrap
+@@ -230,7 +230,7 @@ vc_ignore=
+ 
+ # Source required external libraries:
+ # Set a version string for this script.
+-scriptversion=2015-01-20.17; # UTC
++scriptversion=2015-10-04.22; # UTC
+ 
+ # General shell script boiler plate, and helper functions.
+ # Written by Gary V. Vaughan, 2004
+@@ -1257,6 +1257,57 @@ func_relative_path ()
+ }
+ 
+ 
++# func_quote ARG
++# --
++# Aesthetically quote one ARG, store the result into $func_quote_result.  Note
++# that we keep attention to performance here (so far O(N) complexity as long as
++# func_append is O(1)).
++func_quote ()
++{
++$debug_cmd
++
++func_quote_result=$1
++
++case $func_quote_result in
++  *[\\\`\"\$]*)
++case $func_quote_result in
++  *'*'*|*'['*)
++func_quote_result=`$ECHO "$func_quote_result" | $SED "$sed_quote_subst"`
++return 0
++;;
++esac
++
++func_quote_old_IFS=$IFS
++for _G_char in '\' '`' '"' '$'
++do
++  # STATE($1) PREV($2) SEPARATOR($3)
++  set start "" ""
++  func_quote_result=dummy"$_G_char$func_quote_result$_G_char"dummy
++  IFS=$_G_char
++  for _G_part in $func_quote_result
++  do
++case $1 in
++quote)
++  func_append func_quote_result "$3$2"
++  set quote "$_G_part" "\\$_G_char"
++  ;;
++start)
++  set first "" ""
++  func_quote_result=
++  ;;
++first)
++  set quote "$_G_part" ""
++  ;;
++esac
++  done
++  IFS=$func_quote_old_IFS
++done
++;;
++  *) ;;
++esac
++}
++
++
+ # func_quote_for_eval ARG...
+ # --
+ # Aesthetically quote ARGs to be evaled later.
+@@ -1273,12 +1324,8 @@ func_quote_for_eval ()
+ func_quote_for_eval_unquoted_result=
+ func_quote_for_eval_result=
+ while test 0 -lt $#; do
+-  case $1 in
+-*[\\\`\"\$]*)
+-	  _G_unquoted_arg=`printf '%s\n' "$1" |$SED "$sed_quote_subst"` ;;
+-*)
+-  _G_unquoted_a

Bug#848864: libtool: Get rid of excessive sed forks -- significant performance regression

[Andreas Boll]

On Tue, Dec 20, 2016 at 11:22:46AM +0100, Andreas Boll wrote:
> Package: libtool
> Version: 2.4.6-2
> Severity: important
> Tags: upstream fixed-upstream
> Forwarded: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20006
> 
> Dear Maintainer,
> 
> libtool 2.4.6-0.1 has introduced a performance regression which results
> in significant slowdown in compile time. Version 2.4.6-2 is still
> affected.
> 
> Especially buildds of slower arches like mips* and arm* suffer a lot
> from this performance regression. Here are a few examples how mesa is
> affected by this bug:
> 
> [2016-02-07] Accepted libtool 2.4.6-0.1 (source amd64 all) into unstable
> 
> mipsel: https://buildd.debian.org/status/logs.php?pkg=mesa=mipsel
> 11.1.1-2 (sid)  Maybe-Successful2016-01-15 19:04:32 mipsel-aql-02 
>   50m
> 11.1.2-1 (sid)  Maybe-Successful2016-02-11 14:30:46 mipsel-aql-02 
>   1h 22m
> 
> armhf: https://buildd.debian.org/status/logs.php?pkg=mesa=armhf
> 11.1.1-2 (sid)  Maybe-Successful2016-01-15 19:15:32 hoiby   34m
> 11.1.2-1 (sid)  Maybe-Successful2016-02-11 12:39:21 hoiby   52m
> 
> i386: https://buildd.debian.org/status/logs.php?pkg=mesa=i386
> 11.1.1-2 (sid)  Maybe-Successful2016-01-15 18:20:15 x86-grnet-01  
>   7m
> 11.1.2-1 (sid)  Maybe-Successful2016-02-11 11:54:33 x86-grnet-01  
>   10m
> 
> x32: https://buildd.debian.org/status/logs.php?pkg=mesa=x32
> 11.1.1-2 (sid)  Maybe-Successful2016-01-15 18:36:30 physik  17m
> 11.1.2-1 (sid)  Maybe-Successful2016-02-11 12:36:45 physik  28m
> 
> or systemd on x32: 
> https://buildd.debian.org/status/logs.php?pkg=systemd=x32
> 228-6 (sid) Maybe-Successful2016-02-04 12:42:54 physik  42m
> 229-1 (sid) Maybe-Successful2016-02-11 23:35:48 physik  1h 3m
> 
> 
> This bug has been reported to upstream and has been fixed already [1].
> There's also a blog post about this issue [2].
> Unfortunately upstream hasn't released a new upstream release with those
> fixes yet.
> 
> Please cherry-pick the following three patches from upstream master
> branch to mitigate the excessive sed forking:
> 
> http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=32f0df9835ac15ac17e04be57c368172c3ad1d19
> http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=16dbc070d32e6d4601cb5878dfdf69f2e29c84e1
> http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=9187e9a231e0a06cc29c336857e95f07f855b2c9
> 
> With those patches applied, libtool 2.4.6 still isn't as fast as 2.4.2
> was, but it's much better than the unpatched version.
> 
> 
> Thanks,
> Andreas
> 
> [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20006
> [2] 
> https://harald.hoyer.xyz/2015/03/05/libtool-getting-rid-of-18-sed-forks/

Hi,

Friendly one year ping:

I was hoping that there would be a new upstream release with those
regression fixes included in the meantime. Unfortunately there still
hasn't been any new release since 2015. Also the upstream git
repository looks pretty silent [1].  So it doesn't look like that
there'll be a new release anytime soon.

Any chance to cherry-pick those patches and upload them to
experimental or unstable?

Thanks,
Andreas

[1] https://git.savannah.gnu.org/cgit/libtool.git/log/


signature.asc
Description: PGP signature

Bug#851130: [debhelper-devel] Bug#851130: Bug#851130: debhelper: dh runs dh_quilt_patch after dh_autoreconf in compat 10

[Andreas Boll]

On Fri, Jul 14, 2017 at 08:37:15PM +0200, gregor herrmann wrote:
> On Thu, 16 Mar 2017 20:40:59 +0100, Sven Joachim wrote:
> 
> > > On Thu, Jan 12, 2017 at 06:11:00PM +, Niels Thykier wrote:
> > >> Control: reassign -1 quilt
> > >> Control: retitle -1 quilt: Update dh-sequence module
> > >> 
> > >> Hi Martin and Ryan,
> > >> 
> > >> Please update your debhelper sequence (quilt.pm) to use:
> > >> 
> > >> """
> > >> insert_before("dh_update_autotools_config", "dh_quilt_patch");
> > >> """
> >  
> > >> This requires a dependency on debhelper (>= 9.20160114)
> > 
> > I don't see why this is necessary, because insert_before just seems to
> > be a no-op if the first argument is not present in the sequence, 
> 
> I think, and Niels just confirmed on IRC, that he meant to _replace_
>  insert_before("dh_auto_configure", "dh_quilt_patch");
> with
>  insert_before("dh_update_autotools_config", "dh_quilt_patch");
> instead of adding the latter, and then the dependency would be
> required on the first debhelper version which has
> dh_update_autotools_config.
> 
> > but I
> > must admit that I haven't tested with Jessie's debhelper version.
> 
> Just tried: jessie chroot, /usr/share/perl5/Debian/Debhelper/Sequence/quilt.pm
> with your patch:
> 
> # dh $@ --with quilt --no-act build  
>dh_testdir
>dh_quilt_patch
>dh_auto_configure
>dh_auto_build
>dh_auto_test
> 
> The same in stretch:
> 
> # dh $@ --with quilt --no-act build
> dh: Compatibility levels before 9 are deprecated (level 7 in use)
>dh_testdir
>dh_quilt_patch
>dh_update_autotools_config
>dh_auto_configure
>dh_auto_build
>dh_auto_test
>create-stamp debian/debhelper-build-stamp
> 
> So it looks like the patch works indeed with "old" and "new
> debhelper. In that case we don't need the dependency.
> 
> (I'd probably add a comment to the code why there are now 2
> insert_before; a pointer to this bug e.g. :))
> 
> 
> Cheers,
> gregor

Hi,

any chance to apply that patch and upload it to unstable?
This issue still blocks us from migrating to compat >= 10.

Thanks,
Andreas

Bug#884599: libinput10: jittery synaptics touchpad in wayland session

[Andreas Boll]

On Sun, Dec 17, 2017 at 01:09:16PM +, James Cowgill wrote:
> Package: libinput10
> Version: 1.9.4-1
> Severity: normal
> 
> Hi,
> 
> Since upgrading to libinput 1.9.4-1, I have noticed my synaptics
> touchpad on my laptop has become very jittery. Placing my finger on the
> touchpad without moving it causes the mouse to move around very
> slightly. This is a massive PITA when trying to click precisely somewhere.
> 
> Downgrading to 1.9.3-1 fixes this.
> 
> The laptop is an old Dell XPS 15 L502X, but I'm not sure how to get any
> extra information about my touchpad (if that would be useful).
> 
> Thanks,
> James

Could be related to the new patch fix-lp1696929.patch we ship since
1.9.4-1. Can you rebuild and test libinput 1.9.4-1 without that patch?

Thanks,
Andreas

Bug#882592: Trackpad behaves erratic

[Andreas Boll]

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=104303

On Sun, Dec 17, 2017 at 01:09:48PM +0100, Jörg-Volker Peetz wrote:
> Andreas Boll wrote on 12/14/17 14:29:
> > Severity: normal
> > 
> > On Sat, Nov 25, 2017 at 11:15:06AM +0100, J�rg-Volker Peetz wrote:
> >> Package: libinput10
> >> Version: 1.9.2-1
> >>
> >> Dear Maintainer(s),
> >>
> >> this is to confirm the regression this version introduces and to describe 
> >> some
> >> problems.
> >> After update from version 1.8.3-1 (also update of libc6 from version 
> >> 2.24-15)
> >> the mouse clicks from my Logitech K830 keyboard with built in touchpad
> >> (appearing like a PS/2 mouse) sometimes make problems.
> >> Double tapping to maximize a window in openbox doesn't work at all any 
> >> more.
> >> Double tapping to select a word in text doesn't work, it needs three taps 
> >> now.
> >> Sometimes, after using the emulated middle mouse button the left mouse 
> >> button
> >> behaves like the middle button. To recover, I normally have to press the 
> >> right
> >> mouse button.
> >>
> >> Regards,
> >> jvp.
> >>
> > 
> > Please report this upstream at
> > https://bugs.freedesktop.org/enter_bug.cgi?product=wayland=libinput
> > and let us know the bug number for tracking.
> > 
> > Thanks,
> > Andreas
> > 
> Hello Andreas,
> 
> at Freedesktop.org Bugzilla this now is Bug 104303:
> https://bugs.freedesktop.org/show_bug.cgi?id=104303
> 
> Regards,
> jvp.

Thanks for reporting this issue to upstream.
Andreas

Bug#884356: mesa FTBFS on ia64

[Andreas Boll]

On Thu, Dec 14, 2017 at 08:29:25AM -0500, Jason Duerstock wrote:
> Source: mesa
> Severity: normal
> 
> Dear Maintainer,
> 
> On ia64, mesa appears to FTBFS due to a missing link to libpthread by libgbm:
> 
> /bin/bash ../../libtool  --tag=CC   --mode=link gcc -I../../../include 
> -I../../../src -I../../../src/loader -I../../../src/gbm/main
>  -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
> -D_GNU_SOURCE -DUSE_GCC_ATOMIC_BUILTINS -DNDEBUG -DTEXTURE_FL
> OAT_ENABLED -DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF 
> -DHAVE_MKOSTEMP -DHAVE_STRTOD_L -DHAVE_DL_ITERATE_PHDR -DHAVE_POSIX_MEMALIGN 
> -DHAVE_GALLIUM_EXTRA_HUD=1 -DHAVE_LIBSENSORS=1 -DUSE_LIBGLVND=1 -DHAVE_LIBDRM 
> -DGLX_USE_DRM -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS 
> -DHAVE_X11_PLATFORM -DHAVE_SURFACELESS_PLATFORM -DHAVE_WAYLAND_PLATFORM 
> -DWL_HIDE_DEPRECATED -DHAVE_DRM_PLATFORM -DHAVE_DRI3 -DENABLE_SHADER_CACHE 
> -DHAVE_MINCORE -DHAVE_ST_VDPAU -fvisibility=hidden  
> -DDEFAULT_DRIVER_DIR='"/usr/lib/ia64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri"'
>  -I/usr/include/libdrm  -g -O2 -fdebug-prefix-map=/mnt/a/sid/mesa-17.3.0=. 
> -Wformat -Werror=format-security -Wall -Wall 
> -Werror=implicit-function-declaration -Werror=missing-prototypes 
> -Wmissing-prototypes -fno-math-errno -fno-trapping-math -std=c99  
> -no-undefined -version-info 1:0 -Wl,--gc-sections -Wl,--no-undefined  -o 
> libgbm.la -rpath /usr/lib/ia64-linux-gnu main/backend.lo main/gbm.lo 
> backends/dri/gbm_dri.lo!
>   ../../sr
>  c/loader/libloader.la ../../src/util/libmesautil.la 
> ../../src/util/libxmlconfig.la -ldl 
> ../../src/egl/wayland/wayland-drm/libwayland-drm.la -lwayland-server -ldrm
> libtool: link: gcc -shared  -fPIC -DPIC  main/.libs/backend.o 
> main/.libs/gbm.o backends/dri/.libs/gbm_dri.o  -Wl,--whole-archive 
> ../../src/loader/.libs/libloader.a ../../src/util/.libs/libmesautil.a 
> ../../src/util/.libs/libxmlconfig.a 
> ../../src/egl/wayland/wayland-drm/.libs/libwayland-drm.a 
> -Wl,--no-whole-archive  -lz -lexpat -lm -ldl -lwayland-server -ldrm  -g -O2 
> -Wl,--gc-sections -Wl,--no-undefined   -Wl,-soname -Wl,libgbm.so.1 -o 
> .libs/libgbm.so.1.0.0
> /usr/bin/ld: Warning: gc-sections option ignored

Maybe it's related to this warning.

> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
> `u_thread_setname':
> ./build/src/util/../../../src/util/u_thread.h:66: undefined reference to 
> `pthread_setname_np'
> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
> `thrd_join':
> ./build/src/util/../../../include/c11/threads_posix.h:336: undefined 
> reference to `pthread_join'
> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
> `u_thread_create':
> ./build/src/util/../../../src/util/u_thread.h:48: undefined reference to 
> `pthread_sigmask'
> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
> `thrd_create':
> ./build/src/util/../../../include/c11/threads_posix.h:296: undefined 
> reference to `pthread_create'
> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
> `u_thread_create':
> ./build/src/util/../../../src/util/u_thread.h:50: undefined reference to 
> `pthread_sigmask'
> ./build/src/util/../../../src/util/u_thread.h:50: undefined reference to 
> `pthread_sigmask'
> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
> `call_once':
> ./build/src/util/../../../include/c11/threads_posix.h:96: undefined reference 
> to `pthread_once'
> ./build/src/util/../../../include/c11/threads_posix.h:96: undefined reference 
> to `pthread_once'
> ../../src/util/.libs/libmesautil.a(libmesautil_la-u_queue.o): In function 
> `u_thread_get_time_nano':
> ./build/src/util/../../../src/util/u_thread.h:84: undefined reference to 
> `pthread_getcpuclockid'
> 
> I have attached the last 50 lines of the build log, but the full log is 
> available if you need it.

Yes, the full log would be nice, especially the part from configure
would be interesting.

Thanks,
Andreas

Bug#884466: mesa: firefox, thunderbird, chromium don't start with mesa 17.3.0-1

[Andreas Boll]

Control: severity -1 serious
Control: tag -1 upstream

On Fri, Dec 15, 2017 at 05:04:26PM +0100, Rodolphe Pelloux-Prayer wrote:
> Package: libglx-mesa0
> Version: 17.3.0-1
> Severity: important
> File: mesa
> 
> Dear Maintainer,
> 
> after upgrading to 17.3.0-1, firefox, thunderbird and chromium don't start or 
> more accuratly seems to not display ([AMD/ATI] Oland GL [FirePro W2100])
> 
> Starting firefox in gdb:
> Start it from the beginning? (y or n) y
> Starting program: /usr/lib/firefox/firefox 
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x7fffe4844700 (LWP 9406)]
> [Thread 0x7fffe4844700 (LWP 9406) exited]
> Error: GDK_BACKEND does not match available displays
> [Inferior 1 (process 9345) exited with code 01]
> 
> Downgrade to 17.2.5 fix the issue.

Please report this upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa=Drivers%2FGallium%2Fradeonsi
and let us know the bug number for tracking.


Thanks,
Andreas

Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

[Andreas Boll]

Control: tag -1 moreinfo

On Fri, Oct 13, 2017 at 10:24:19AM +0200, Andreas Boll wrote:
> Control: severity -1 important
> 
> On Mon, Oct 02, 2017 at 09:00:59PM +0200, Dominik Kupschke wrote:
> > Hi,
> > 
> > I was able to start some steam games without steam-runtime.
> > Also non Steam Games work properly.
> > 
> > Regards
> > Dominik
> 
> Hi,
> 
> so it looks like an issue with the steam-runtime. Please report this
> issue to Valve on github and let us know the bug number/url for
> tracking.
> 
> I'm lowering the severity to important to let Mesa migrate to testing
> since it blocks lots of packages.
> 
> Thanks,
> Andreas

Is this still an issue with mesa 17.3.0? Did you report this issue to
Valve on github?

Thanks,
Andreas

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

[Andreas Boll]

Control: tags -1 moreinfo

On Wed, Oct 18, 2017 at 11:31:49PM +0200, Salvo Tomaselli wrote:
> cube desktop and wobbly windows of kwin work.
> 
> See this https://bugs.archlinux.org/task/55578
> 
> I tried with latest kernel compiled by myself and with default kernel.
> Same result.
> 
> 2017-10-18 22:29 GMT+02:00 Andreas Boll <andreas.boll@gmail.com>:
> > On Wed, Oct 18, 2017 at 04:25:58PM +0200, Salvo Tomaselli wrote:
> >> I just tried running the game again, on a fully upgraded unstable
> >> system. The issue is most certainly still present, but now it's in
> >> testing too…
> >>
> >> > Hi Salvo,
> >> >
> >> > could you try to use llvm from testing?
> >> > Does this issue affect other opengl apps (e.g. other (non-)steam games, 
> >> > amd64
> >> > games, ...) too?
> >
> > Hi,
> >
> > Now that you can reproduce the issue again
> > does it affect other opengl apps too?
> >
> > Please report this issue upstream. Please follow the instructions at
> > https://01.org/linuxgraphics/documentation/how-report-bugs and let us
> > know the bug number for tracking.
> >
> > Thanks,
> > Andreas

Is this still an issue with mesa 17.3.0?
Did you report this issue upstream?

Thanks,
Andreas

Bug#879041: libglvnd0: Nvidia-Installer 384.90: "An incomplete installation of libglvnd was found."

[Andreas Boll]

Control: reassign -1 src:nvidia-graphics-drivers

On Fri, Dec 01, 2017 at 08:27:05AM -0500, Chris Manougian wrote:
> 384.98-2 dropped into sid this morning. It installed.
> 
> This last weekend, I purged nvidia, and reinstalled.  What was available in
> sid was 375.82, and it stalled.  Then 378 came into sid, and it was
> installable.  Then this morning, I was able to install 384.98-2.
> 
> Still having a mesa-related error:
> 
> root@asus:/home/chris# glxinfo | grep OpenGL
> libGL error: No matching fbConfigs or visuals found
> libGL error: failed to load driver: swrast
> X Error of failed request:  GLXBadContext
>   Major opcode of failed request:  154 (GLX)
>   Minor opcode of failed request:  6 (X_GLXIsDirect)
>   Serial number of failed request:  48
>   Current serial number in output stream:  47
> root@asus:/home/chris#  glxinfo  | grep rendering
> libGL error: No matching fbConfigs or visuals found
> libGL error: failed to load driver: swrast
> X Error of failed request:  GLXBadContext
>   Major opcode of failed request:  154 (GLX)
>   Minor opcode of failed request:  6 (X_GLXIsDirect)
>   Serial number of failed request:  48
>   Current serial number in output stream:  47
> root@asus:/home/chris#
> 
> But that's another issue that I'm hoping a mesa update will fix. The
> installation issue is resolved for me.

This doesn't look like a mesa issue. Re-assigning to nvidia-graphics-drivers.

Thanks,
Andreas

Bug#879583: libgl1-mesa-glx: Couldn't open libGL.so.1, undefined symbol _giapi_tls_Current

[Andreas Boll]

Control: tags -1 moreinfo

On Mon, Oct 23, 2017 at 05:45:56AM +, Paul Lou wrote:
> Package: libgl1-mesa-glx
> Version: 17.2.2-1
> Severity: important
> 
> Dear Maintainer,
> 
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> Performed aptitude upgrade today, upgraded libgl1-mesa-glx from
> 13.0.6-1+b2, and rebooted.
> 
>* What was the outcome of this action?
> Now xinit fails to start due to error
> xf86EnableIOPorts: failed to set IOPL for I/O (operation not permitted)
> Couldn't open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined
> symbol: _giapi_tls_Current
> xinit: giving up
> 
> Another computer with very similar setup, except with nVidia graphics card,
> failed to upgrade today from 13.0.6-1 to 17.2.2-1 (due to dependency issues
> with libegl1-glvnd-nvidia [375.82-5], libgl1-glvnd-nvidia-glx [375.82-5],
> libglx0-glvnd-nvidia[375.82-5]) does not have the reported issues.
> 
> On the affected computer, `ldd -r /usr/lib/x86_64-linux-gnu/libGL.so.1`
> returns the same undefined symbol error.
> 
>* What outcome did you expect instead?
> Successfully launch startx.
> 

Is this still an issue? I think this was fixed in a newer version of
nvidia-graphics-drivers.

Thanks,
Andreas

Bug#833867: libgl1-mesa-dri: crash (SIGSEGV) in mesa on exit of totem

[Andreas Boll]

On Tue, Aug 09, 2016 at 05:49:01PM +0800, Paul Wise wrote:
> Package: libgl1-mesa-dri
> Version: 11.2.2-1
> Severity: normal
> 
> I got a crash (SIGSEGV) in mesa when totem (GNOME video player) was
> exiting. The Debian GNOME team advised me to file this against mesa.
> If the backtrace below isn't useful, please close this bug.

Upstream closed the forwarded bug as unreproducible.

Closing this bug too.

Thanks,
Andreas

Bug#855465: upstream bug report

[Andreas Boll]

Control: tag -1 moreinfo

On Sun, Feb 19, 2017 at 12:04:45AM +0530, Jyotirmoy Bhattacharya wrote:
> This could possibly be the following upstream bug
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=99447
> 
> which was fixed by commit e86fdd58

Is this still an issue with a newer version of libinput?

Thanks,
Andreas

Bug#876198: libinput10: Can't initiate a touchpad motion near a corner

[Andreas Boll]

Control: tag -1 upstream

On Tue, Sep 19, 2017 at 03:51:50PM +0100, Tony Houghton wrote:
> Package: libinput10
> Version: 1.8.2-1
> Severity: normal
> 
> When using GNOME on Wayland I can't move the pointer with the touchpad
> if I initially start touching it near a corner. Even if I drag my finger
> across the middle from the corner, the pointer doesn't move, and no
> events are shown in libinput-debug-events. If I do the opposite, ie
> start the motion near the middle of the touchpad, it continues to track
> my finger correctly if I move it into the corners.
> 
> I only noticed this recently, so it's probably something in the most
> recent version to enter Debian. GNOME on Xorg is not affected; AIUI
> GNOME on Wayland uses libinput, and something else on Xorg, so I guessed
> this is the culprit package.
> 
> The machine is a Lenovo Thinkpad Carbon X1 4th Generation. From
> libinput-list-devices:
> 
> Device:   SynPS/2 Synaptics TouchPad
> Kernel:   /dev/input/event1
> Group:8
> Seat: seat0, default
> Size: 100x57mm
> Capabilities: pointer
> Tap-to-click: disabled
> Tap-and-drag: enabled
> Tap drag lock:disabled
> Left-handed:  disabled
> Nat.scrolling:disabled
> Middle emulation: disabled
> Calibration:  n/a
> Scroll methods:   *two-finger edge
> Click methods:*button-areas clickfinger
> Disable-w-typing: enabled
> Accel profiles:   none
> Rotation: n/a
> 

Please report this upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=wayland=libinput
and let us know the bug number for tracking.

Thanks,
Andreas

Bug#861631: libinput10: Imposible to increase TrackPoint speed

[Andreas Boll]

Control: tag -1 moreinfo

On Mon, May 08, 2017 at 01:45:47PM +0900, Charles Plessy wrote:
> Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=100965
> 
> Le Wed, May 03, 2017 at 11:00:36AM +0200, Julien Cristau a écrit :
> > 
> > please file this upstream at
> > https://bugs.freedesktop.org/enter_bug.cgi?component=Input%2Flibinput=xorg
> > including your full X log and details about the hardware.  Let us know
> > the bug number for tracking.
> 
> Hi Julien,
> 
> submitted, thank you.
> 
> -- 
> Charles

Looks like the upstream bug report has been closed.
Is this still an issue?

Thanks,
Andreas

Bug#882592: Trackpad behaves erratic

[Andreas Boll]

Severity: normal

On Sat, Nov 25, 2017 at 11:15:06AM +0100, Jörg-Volker Peetz wrote:
> Package: libinput10
> Version: 1.9.2-1
> 
> Dear Maintainer(s),
> 
> this is to confirm the regression this version introduces and to describe some
> problems.
> After update from version 1.8.3-1 (also update of libc6 from version 2.24-15)
> the mouse clicks from my Logitech K830 keyboard with built in touchpad
> (appearing like a PS/2 mouse) sometimes make problems.
> Double tapping to maximize a window in openbox doesn't work at all any more.
> Double tapping to select a word in text doesn't work, it needs three taps now.
> Sometimes, after using the emulated middle mouse button the left mouse button
> behaves like the middle button. To recover, I normally have to press the right
> mouse button.
> 
> Regards,
> jvp.
> 

Please report this upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=wayland=libinput
and let us know the bug number for tracking.

Thanks,
Andreas

Bug#884333: mesa: Since 17.3.0~rc5-1 GNOME 3.26.x login broken

[Andreas Boll]

On Wed, Dec 13, 2017 at 06:58:58PM -0800, Marc Jeffrey Driftmeyer wrote:
> Source: mesa
> Version: 17.3.0
> Severity: normal
> 
> Dear Maintainer,
> 
> I upgraded from 17.2.5 after a failed test of the Experimental 17.3.0 branch 
> release candidates hoping to see if this issue had been addressed, and it 
> hasn't.
> 
> I had to downgrade to 17.2.5 to file this bug with GNOME 3.26.2 in Sid and 
> the Mesa 17.3 branch giving the infamous Oops something went wrong logout 
> continous retry phenomenom no one enjoys. Perhaps someone could think of 
> logout turns into console login after 1 failed try?
Is there any useful information about this issue in your dmesg or any
other log file?

> 
> At any rate, I just thought you might want to test this more thoroughly. I'll 
> wait until a few more stable releases from Mesa are out before trying again.
Works fine here with r600g. Also confirmed working on intel gfx. Could
be a driver specific issue. Which driver do you use?

Please follow-up with the output from mesa's bug script
'reportbug libgl1-mesa-dri'.

Thanks,
Andreas

> 
> Marc J. Driftmeyer
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.14.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

Bug#847570: linux-image-4.9.0-rc8-amd64-unsigned: AMDGPU not build with support for GCN1.0 and GCN1.1 VGAs

[Andreas Boll]

On Thu, Jan 05, 2017 at 03:19:23AM +, Ben Hutchings wrote:
> On Fri, 2016-12-09 at 16:06 +0100, Ferdinand Pöll wrote:
> > Package: linux-image-4.9.0-rc8-amd64-unsigned
> > Version: 4.9~rc8-1~exp1
> > Severity: wishlist
> > Tags: patch
> > 
> > Dear Maintainer,
> > 
> > I have an AMD Radeon R9 270X and I'd like to use the new amdgpu driver with 
> > it.
> > Since 4.9, linux includes experimental support for GCN 1.0 VGAs, but it's 
> > not
> > enabled in the debian builds as well as the support for GCN 1.1 cards (which
> > isn't new in the kernel anymore). In the kernel build config, you just need 
> > to
> > set CONFIG_DRM_AMDGPU_SI=Y (for GCN1.0-based cards) and 
> > CONFIG_DRM_AMDGPU_CIK=Y
> > (for GCN1.1-based cards). To use amdgpu if it is built into the kernel with 
> > the
> > old gpus users just need to blacklist radeon and upon the next reboot linux
> > will load amdgpu and users can install amdgpu-pro if they want to or just 
> > stick
> > with the newest free graphics driver.
> 
> I don't think this will work the way you expect.  kmod will load both
> modules unless one of them is blacklisted, and it's not documented
> which one will be tried first.  So we could end up loading amdgpu on
> systems that should still be using radeon by default.
> 
> We could perhaps patch amdgpu so that it isn't auto-loaded for the GCN
> 1.0 GPUs.  But I'm not yet convinced this is worth doing.
> 
> Ben.
> 

Hi Ben,

upstream has landed a solution for this issue in 4.13 which doesn't
require blacklisting radeon anymore [1].

Please consider setting CONFIG_DRM_AMDGPU_SI=Y and
CONFIG_DRM_AMDGPU_CIK=Y to allow the optional usage of amdgpu on
GCN1.0 and GCN1.1 based cards [2]. The default driver will be still
radeon but users who want to use amdgpu can choose amdgpu by providing
the following kernel parameters for GCN1.0 cards:

  radeon.si_support=0 amdgpu.si_support=1

and for GCN1.1 cards:

  radeon.cik_support=0 amdgpu.cik_support=1


Thanks,
Andreas

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?id=2b059658d6796a096ef06be9da994d6c44401d5b
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/amdgpu/Kconfig?h=v4.13


signature.asc
Description: PGP signature

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

[Andreas Boll]

On Wed, Oct 18, 2017 at 04:25:58PM +0200, Salvo Tomaselli wrote:
> I just tried running the game again, on a fully upgraded unstable
> system. The issue is most certainly still present, but now it's in
> testing too…
> 
> > Hi Salvo,
> >
> > could you try to use llvm from testing?
> > Does this issue affect other opengl apps (e.g. other (non-)steam games, 
> > amd64
> > games, ...) too?

Hi,

Now that you can reproduce the issue again
does it affect other opengl apps too?

Please report this issue upstream. Please follow the instructions at
https://01.org/linuxgraphics/documentation/how-report-bugs and let us
know the bug number for tracking.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#868843: xorg-server: please make the BUILD_{DATE,TIME} reproducible

[Andreas Boll]

Control: tags -1 fixed-upstream

On Fri, Jul 21, 2017 at 08:41:01AM +0100, Chris Lamb wrote:
> forwarded 868843 
> https://lists.x.org/pipermail/xorg-devel/2017-July/054127.html
> thanks
> 
> Updating URL.
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb, Debian Project Leader
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>`-

Fixed by 
https://cgit.freedesktop.org/xorg/xserver/commit/?id=937ed782ae5e4e0da739f0630d1681b3754f0281

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

[Andreas Boll]

Control: severity -1 important

(Adding original bug reporter)

On Tue, Oct 03, 2017 at 06:32:25AM +0200, Antoine Le Gonidec wrote:
> On Thu, 28 Sep 2017 23:15:27 +0200 Salvo Tomaselli 
> wrote:
> > I had downgraded my mesa. I wanted to try again but I can't upgrade it
> > because of some llvm breakage at the moment.
> > (…)
> > I seguenti pacchetti hanno dipendenze non soddisfatte:
> > libllvm5.0 : Rompe: libllvm5.0:i386 (!= 1:5.0-2) but 1:5.0-1 is to be 
> > installed
> > libllvm5.0:i386 : Rompe: libllvm5.0 (!= 1:5.0-1) but 1:5.0-2 is installed
> 
> You can still install these packages without waiting for the resolution
> of bug #876752 by forcing the highest common version for these two
> architectures:
> apt install libllvm5.0{,:i386}=1:5.0~+rc2-1
> 
> You need to have the testing repositories in your APT sources or this
> won’t work.
> 

Hi Salvo,

could you try to use llvm from testing?
Does this issue affect other opengl apps (e.g. other (non-)steam games, amd64
games, ...) too?

In the meantime I'm lowering the severity to important to let Mesa
migrate to testing since it blocks lots of packages.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

[Andreas Boll]

Control: severity -1 important

On Mon, Oct 02, 2017 at 09:00:59PM +0200, Dominik Kupschke wrote:
> Hi,
> 
> I was able to start some steam games without steam-runtime.
> Also non Steam Games work properly.
> 
> Regards
> Dominik

Hi,

so it looks like an issue with the steam-runtime. Please report this
issue to Valve on github and let us know the bug number/url for
tracking.

I'm lowering the severity to important to let Mesa migrate to testing
since it blocks lots of packages.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#874715: mesa Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

[Andreas Boll]

On Fri, Sep 29, 2017 at 07:21:42AM +0200, Dominik Kupschke wrote:
> Yes I am fine with changing the severity to important.
> 
> This issue affects all of my steam games (> 100), so the migration of the 
> packet to testing could be bad for a lot of people.
> 
> Regards
> Dominik

So does this issue affect only i386 games or steam games. Could you
try some non-steam i386 games/benchmarks and some amd64
games/benchmarks?

There's currently an issue with llvm not building on i386. Maybe
that's somehow related. Could you attach the list of installed llvm
packages?
dpkg -l | grep llvm

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#874656: libegl1-mesa: Makes team fortress 2 crash the entire machine

[Andreas Boll]

On Sat, Sep 09, 2017 at 11:16:54PM +0300, Timo Aaltonen wrote:
> On 09.09.2017 02:31, Salvo Tomaselli wrote:
> > Well I had to downgrade to testing since it was making my machine crash.
> 
> Doesn't crash my KBL now that I tested it. Try an older kernel maybe.

Can you reproduce this issue with an older kernel (from snapshot.debian.org) or 
a newer kernel (from experimental)?

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#874715: mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

[Andreas Boll]

(Adding original bug reporter)

Is this still an issue with mesa 17.2.1?
Could the following be related to your issue?

On Fri, Sep 15, 2017 at 08:01:54AM +0200, Gert Wollny wrote:
> Since you are using radeonsi you may have a conflict between the system
>  libstdc++ and the one shipped with the steam runtime (Although this
> usually meant Steam doesn't start at all). 
> 
> cf: https://github.com/ValveSoftware/steam-for-linux/issues/3273


Could you please attach the output from LIBGL_DEBUG=verbose glxinfo
and if possible replace mesa-utils:amd64 with mesa-utils:i386 and run
glxinfo again and attach its output too.

Thanks,
Andreas


signature.asc
Description: PGP signature

Bug#860749: mesa-va-drivers: Critical error in library 'mesa' with i965 video driver

[Andreas Boll]

On Tue, May 09, 2017 at 03:00:34PM +0200, Andreas Boll wrote:
> The following looks like an issue with the kernel graphics driver:

Looks like a known upstream kernel issue:
https://bugs.freedesktop.org/show_bug.cgi?id=93782

Please try the workaround described in comment 40 [1] first, by adding

video=SVIDEO-1:d

to the kernel command line.

Thanks,
Andreas

[1] https://bugs.freedesktop.org/show_bug.cgi?id=93782#c40

> 
> > [   21.472066] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] 
> > *ERROR* [CRTC:26:pipe A] flip_done timed out
> > [   21.576017] [ cut here ]
> > [   21.576062] WARNING: CPU: 0 PID: 100 at 
> > /build/linux-9r9Ph5/linux-4.9.18/drivers/gpu/drm/drm_irq.c:1254 
> > drm_wait_one_vblank+0x197/0x1a0 [drm]
> > [   21.576200] vblank wait timed out on crtc 0
> > [   21.576201] Modules linked in: uvcvideo videobuf2_vmalloc arc4 
> > videobuf2_memops iwl3945 videobuf2_v4l2 iwlegacy videobuf2_core 
> > snd_hda_codec_si3054 mac80211 videodev media cfg80211 iTCO_wdt 
> > iTCO_vendor_support joydev evdev r592 memstick snd_hda_codec_realtek 
> > snd_hda_codec_generic rfkill snd_hda_intel pcspkr snd_hda_codec coretemp 
> > serio_raw snd_hda_core snd_hwdep lpc_ich mfd_core snd_pcm snd_timer sg i915 
> > shpchp drm_kms_helper ene_ir rc_core drm i2c_algo_bit battery ac snd 
> > soundcore video wmi button acpi_cpufreq tpm_tis tpm_tis_core tpm parport_pc 
> > ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic 
> > fscrypto ecb glue_helper lrw gf128mul ablk_helper cryptd aes_x86_64 mbcache 
> > sr_mod cdrom sd_mod ata_generic psmouse i2c_i801 i2c_smbus ata_piix libata 
> > scsi_mod tg3 firewire_ohci sdhci_pci
> > [   21.576257]  sdhci mmc_core firewire_core crc_itu_t ptp pps_core libphy 
> > ehci_pci uhci_hcd ehci_hcd usbcore usb_common
> > [   21.576269] CPU: 0 PID: 100 Comm: kworker/u4:3 Not tainted 4.9.0-2-amd64 
> > #1 Debian 4.9.18-1
> > [   21.576270] Hardware name: - N/A 
> >/IFT01 , BIOS 1.18 06/18/2008
> > [   21.576276] Workqueue: events_unbound async_run_entry_fn
> > [   21.576278]   b4928714 a5e440917a60 
> > 
> > [   21.576281]  b4676e9e 9898383c a5e440917ab8 
> > 
> > [   21.576283]  0101 98983a6edc08 9898383f8800 
> > b4676f1f
> > [   21.576286] Call Trace:
> > [   21.576293]  [] ? dump_stack+0x5c/0x78
> > [   21.576296]  [] ? __warn+0xbe/0xe0
> > [   21.576298]  [] ? warn_slowpath_fmt+0x5f/0x80
> > [   21.576301]  [] ? finish_wait+0x3c/0x70
> > [   21.576315]  [] ? drm_wait_one_vblank+0x197/0x1a0 [drm]
> > [   21.576317]  [] ? prepare_to_wait_event+0xf0/0xf0
> > [   21.576389]  [] ? 
> > intel_get_load_detect_pipe+0x624/0x640 [i915]
> > [   21.576425]  [] ? intel_tv_detect+0x155/0x550 [i915]
> > [   21.576440]  [] ? 
> > drm_property_replace_global_blob+0xd8/0x120 [drm]
> > [   21.576458]  [] ? 
> > drm_helper_probe_single_connector_modes+0x3f6/0x4e0 [drm_kms_helper]
> > [   21.576465]  [] ? 
> > drm_fb_helper_initial_config+0xac/0x440 [drm_kms_helper]
> > [   21.576500]  [] ? intel_fbdev_initial_config+0x14/0x30 
> > [i915]
> > [   21.576502]  [] ? async_run_entry_fn+0x34/0x140
> > [   21.576504]  [] ? process_one_work+0x184/0x410
> > [   21.576506]  [] ? worker_thread+0x4d/0x480
> > [   21.576508]  [] ? process_one_work+0x410/0x410
> > [   21.576510]  [] ? kthread+0xce/0xf0
> > [   21.576512]  [] ? __switch_to+0x2c1/0x6c0
> > [   21.576514]  [] ? kthread_park+0x60/0x60
> > [   21.576517]  [] ? ret_from_fork+0x25/0x30
> > [   21.576519] ---[ end trace 872a41b26fe6df4f ]---



signature.asc
Description: Digital signature

Bug#860749: mesa-va-drivers: Critical error in library 'mesa' with i965 video driver

[Andreas Boll]

Hi,

On Wed, Apr 19, 2017 at 03:00:46PM -0300, Carlos Donizete Froes wrote:
> Package: mesa-va-drivers
> Version: 13.0.6-1
> Severity: critical
> Tags: lfs
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
>* What led up to the situation?
>- After installing Debian Stretch RC-3 in notebook, it does not open the
> graphical environment (gnome, kde, xfce, mate).
> 
>* What exactly did you do (or not do) that was effective (or ineffective)?
>- I accessed the GRUB recovery mode, where was able to open the graphical
> environment, but it was extremely slow.
>- But when you start in normal mode, the system freezes on the dark screen.
> 
>* What was the outcome of this action?
>- I did a search and found on the site official:
> https://www.mesa3d.org/relnotes/17.0.4.html
>- For 'nouveau' and 'i965' is very important when have several fixes that
> have the problem addressed.

Please try mesa 17.0.4 from experimental.

> 
>* What outcome did you expect instead?
>- I hope it corrects this error, in the company where the work has 3
> notebooks with this configuration. It works great without Debian Jessie, but
> testing Debian Stretch RC-3, this giving video driver problems.
> 
> Thanks!
> 
> 
> 
> VGA-compatible devices on PCI bus:
> --
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
> GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c)
> 
> Xorg X server log files on system:
> --
> -rw-r--r-- 1 coringao coringao 24218 Apr 19 13:22 
> /home/coringao/.local/share/xorg/Xorg.0.log
> 
> Contents of most recent Xorg X server log file 
> (/home/coringao/.local/share/xorg/Xorg.0.log):
> -

snip

The following loads the generic modesetting driver with glamor
acceleration. Maybe glamor has issues on your hardware + driver
combination (glamor + OpenGL driver + kernel driver).

> [73.538] (II) LoadModule: "modesetting"
> [73.538] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
> [73.553] (II) Module modesetting: vendor="X.Org Foundation"
> [73.553]  compiled for 1.19.2, module version = 1.19.2
> [73.553]  Module class: X.Org Video Driver
> [73.553]  ABI class: X.Org Video Driver, version 23.0

snip

> [73.594] (II) modeset(0): Creating default Display subsection in Screen 
> section
>   "Default Screen Section" for depth/fbbpp 24/32
> [73.594] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
> [73.594] (==) modeset(0): RGB weight 888
> [73.594] (==) modeset(0): Default visual is TrueColor
> [73.594] (II) Loading sub module "glamoregl"
> [73.594] (II) LoadModule: "glamoregl"
> [73.594] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
> [73.610] (II) Module glamoregl: vendor="X.Org Foundation"
> [73.610]  compiled for 1.19.2, module version = 1.0.0
> [73.610]  ABI class: X.Org ANSI C Emulation, version 0.4
> [73.610] (II) glamor: OpenGL accelerated X.org driver based.
> [73.636] (II) glamor: EGL version 1.4 (DRI2):
> [73.642] (II) modeset(0): glamor initialized
snip

Could you try to use xserver-xorg-video-intel driver by copying the
template xorg.conf to /etc/X11:

cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf /etc/X11


The following looks like an issue with the kernel graphics driver:

> [   21.472066] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] 
> *ERROR* [CRTC:26:pipe A] flip_done timed out
> [   21.576017] [ cut here ]
> [   21.576062] WARNING: CPU: 0 PID: 100 at 
> /build/linux-9r9Ph5/linux-4.9.18/drivers/gpu/drm/drm_irq.c:1254 
> drm_wait_one_vblank+0x197/0x1a0 [drm]
> [   21.576200] vblank wait timed out on crtc 0
> [   21.576201] Modules linked in: uvcvideo videobuf2_vmalloc arc4 
> videobuf2_memops iwl3945 videobuf2_v4l2 iwlegacy videobuf2_core 
> snd_hda_codec_si3054 mac80211 videodev media cfg80211 iTCO_wdt 
> iTCO_vendor_support joydev evdev r592 memstick snd_hda_codec_realtek 
> snd_hda_codec_generic rfkill snd_hda_intel pcspkr snd_hda_codec coretemp 
> serio_raw snd_hda_core snd_hwdep lpc_ich mfd_core snd_pcm snd_timer sg i915 
> shpchp drm_kms_helper ene_ir rc_core drm i2c_algo_bit battery ac snd 
> soundcore video wmi button acpi_cpufreq tpm_tis tpm_tis_core tpm parport_pc 
> ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic 
> fscrypto ecb glue_helper lrw gf128mul ablk_helper cryptd aes_x86_64 mbcache 
> sr_mod cdrom sd_mod ata_generic psmouse i2c_i801 i2c_smbus ata_piix libata 
> scsi_mod tg3 firewire_ohci sdhci_pci
> [   21.576257]  sdhci mmc_core firewire_core crc_itu_t ptp pps_core libphy 
> ehci_pci uhci_hcd ehci_hcd usbcore usb_common
> [   21.576269] CPU: 0 PID: 100 Comm: kworker/u4:3 Not tainted 4.9.0-2-amd64 
> #1 Debian 4.9.18-1
> [   21.576270] Hardware name: - N/A 

Bug#857591: libclc-amdgcn: apply upstream Mesa patch

[Andreas Boll]

Control: fixed -1 0.2.0+git20170213-1

On Sun, Mar 12, 2017 at 05:12:55PM -0700, Ian Bruce wrote:
> Package: libclc-amdgcn
> Version: 0.2.0+git20160907-3
> Severity: important
> Tags: upstream patch
> 
> Running the "clinfo" utility (with AMD GPU), from the package of the
> same name, produces the following openCL compile error:
> 
> unsupported call to function get_local_size
> 
> This is a known problem, and is being widely complained of, as it makes
> openCL unusable on AMD GPUs:
> 
> http://www.google.com/search?q=%22unsupported+call+to+function+get_local_size%22
> 
> Fortunately, a patch is now available from Mesa upstream:
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=99856#c24
> 
> However, it is suggested that "distros will probably have to apply that
> patch individually":
> 
> https://bugs.freedesktop.org/attachment.cgi?id=130136
> 
> Please do so; until this is done, libclc-amdgcn is effectively unusable.

Hi,

libclc 0.2.0+git20170213-1 from experimental shouldn't be affected by
this issue because it uses LLVM 4.0. See also [1]

[1] https://bugs.freedesktop.org/show_bug.cgi?id=99856#c14

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#857623: mesa-opencl-icd: openCL is broken in LLVM < v5

[Andreas Boll]

Control: reassign -1 src:llvm-toolchain-3.9 1:3.9.1-5
Control: block 848258 by -1
Control: forwarded -1 https://bugs.llvm.org/show_bug.cgi?id=30217

On Mon, Mar 13, 2017 at 05:32:40AM -0700, Ian Bruce wrote:
> Package: mesa-opencl-icd
> Version: 13.0.5-1
> Severity: important
> Tags: upstream patch
> 
> LLVM versions before v5 contain a known language bug, involving the use
> of pointers as boolean values, which makes them essentially unusable for
> openCL:
> 
> https://bugs.llvm.org/show_bug.cgi?id=30217
> 
> https://reviews.llvm.org/D29038
> 
> https://reviews.llvm.org/rL294313
> 
> For an example of the problems this causes, see here:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848258
> 
> https://developer.blender.org/T50522
> 
> a trivial test case illustrating the bug:
> 
> 
> $ cat ptr-expr2.c
> int ptr_expr(int *p)
> {
> if (!p)
> return(0);
> else
> return(1);
> }
> 
> $ clang-3.9 -x cl -emit-llvm -S ptr-expr2.c
> ptr-expr2.c:3:9: error: invalid argument type 'int *' to unary expression
> if (!p)
> ^~
> 1 error generated.
> 
> $ clang-4.0 -x cl -emit-llvm -S ptr-expr2.c
> ptr-expr2.c:3:9: error: invalid argument type 'int *' to unary expression
> if (!p)
> ^~
> 1 error generated.
> 
> $ clang-5.0 -x cl -emit-llvm -S ptr-expr2.c
> $ # compilation succeeds
> 
> 
> possible solutions:
> 
> - make openCL require LLVM-v5
> 
> - backport the bugfix from LLVM-v5 to earlier versions;
>   it is apparently a single line change (see LLVM link above)

Dear LLVM maintainers,

please cherry-pick r294313 for llvm-3.9 and llvm-4.0.

Thanks,
Andreas


> Until one or other of these solutions is applied, openCL in Mesa is
> effectively unusable.
> 
> 
> 
> -- System Information:
> Debian Release: 9.0
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), 
> (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages mesa-opencl-icd depends on:
> ii  libc62.24-9
> ii  libclc-amdgcn0.2.0+git20160907-3
> ii  libclc-r600  0.2.0+git20160907-3
> ii  libdrm-amdgpu1   2.4.74-1
> ii  libdrm-nouveau2  2.4.74-1
> ii  libdrm-radeon1   2.4.74-1
> ii  libdrm2  2.4.74-1
> ii  libelf1  0.168-0.2
> ii  libexpat12.2.0-2
> ii  libgcc1  1:6.3.0-6
> ii  libgcrypt20  1.7.6-1
> ii  libllvm3.9   1:3.9.1-4
> ii  libsensors4  1:3.4.0-3+b1
> ii  libstdc++6   6.3.0-6
> ii  ocl-icd-libopencl1 [libopencl1]  2.2.11-1
> 
> mesa-opencl-icd recommends no packages.
> 
> mesa-opencl-icd suggests no packages.
> 
> Versions of packages xserver-xorg depends on:
> ii  x11-xkb-utils  7.7+3+b1
> ii  xkb-data   2.19-1
> ii  xserver-xorg-core  2:1.19.2-1
> ii  xserver-xorg-input-evdev [xorg-driver-input]   1:2.10.5-1
> ii  xserver-xorg-video-radeon [xorg-driver-video]  1:7.8.0-1+b1
> 
> Versions of packages xserver-xorg recommends:
> ii  libgl1-mesa-dri  13.0.5-1
> 
> Versions of packages xserver-xorg-core depends on:
> ii  keyboard-configuration1.160
> ii  libaudit1 1:2.6.7-1
> ii  libbsd0   0.8.3-1
> ii  libc6 2.24-9
> ii  libdbus-1-3   1.10.16-1
> ii  libdrm2   2.4.74-1
> ii  libegl1-mesa  13.0.5-1
> ii  libepoxy0 1.3.1-2
> ii  libgbm1   13.0.5-1
> ii  libgcrypt20   1.7.6-1
> ii  libgl1-mesa-glx [libgl1]  13.0.5-1
> ii  libpciaccess0 0.13.4-1
> ii  libpixman-1-0 0.34.0-1
> ii  libselinux1   2.6-3
> ii  libsystemd0   232-19
> ii  libudev1  232-19
> ii  libxau6   1:1.0.8-1
> ii  libxdmcp6 1:1.1.2-3
> ii  libxfont2 1:2.0.1-3
> ii  libxshmfence1 1.2-1
> ii  udev  232-19
> ii  xserver-common2:1.19.2-1
> 
> Versions of packages xserver-xorg-core recommends:
> ii  libgl1-mesa-dri  13.0.5-1
> ii  libpam-systemd   232-19
> 
> Versions of packages xserver-xorg-core suggests:
> ii  xfonts-100dpi1:1.0.4+nmu1
> ii  xfonts-75dpi 1:1.0.4+nmu1
> ii  xfonts-scalable  1:1.0.3-1.1
> 
> -- no debconf information


signature.asc
Description: Digital signature

Bug#853153: closed by Timo Aaltonen <tjaal...@debian.org> (Bug#853153: fixed in xserver-xorg-video-siliconmotion 1:1.7.9-2)

[Andreas Boll]

On Thu, Mar 09, 2017 at 12:39:14PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the xserver-xorg-video-siliconmotion package:
> 
> #853153: xserver-xorg-video-siliconmotion: segfault on starting
> 
> It has been closed by Timo Aaltonen .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Timo Aaltonen 
>  by
> replying to this email.
> 
> 
> -- 
> 853153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853153
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Thu, 09 Mar 2017 12:37:09 +
> From: Timo Aaltonen 
> To: 853153-cl...@bugs.debian.org
> Subject: Bug#853153: fixed in xserver-xorg-video-siliconmotion 1:1.7.9-2
> 
> Source: xserver-xorg-video-siliconmotion
> Source-Version: 1:1.7.9-2
> 
> We believe that the bug you reported is fixed in the latest version of
> xserver-xorg-video-siliconmotion, which is due to be installed in the Debian 
> FTP archive.
> 
> A summary of the changes between this version and the previous one is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 853...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Timo Aaltonen  (supplier of updated 
> xserver-xorg-video-siliconmotion package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Format: 1.8
> Date: Thu, 09 Mar 2017 14:03:59 +0200
> Source: xserver-xorg-video-siliconmotion
> Binary: xserver-xorg-video-siliconmotion
> Architecture: source
> Version: 1:1.7.9-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian X Strike Force 
> Changed-By: Timo Aaltonen 
> Description:
>  xserver-xorg-video-siliconmotion - X.Org X server -- SiliconMotion display 
> driver
> Closes: 853153
> Changes:
>  xserver-xorg-video-siliconmotion (1:1.7.9-2) unstable; urgency=medium
>  .
>* fix-screeninit.diff: Fix driver crashing xserver 1.19. Thanks Steven
>  Chamberlain! (Closes: #853153)
>* fix-arm64-ftbfs.diff: Fix arm64 build, possibly also hppa, m68k,
>  sh4.
> Checksums-Sha1:
>  8d50331b0b2f53e419e0888a5bff72cd270544dc 2243 
> xserver-xorg-video-siliconmotion_1.7.9-2.dsc
>  87c000f3e09bd068339da6df1904bfb1e8280e18 15543 
> xserver-xorg-video-siliconmotion_1.7.9-2.diff.gz
> Checksums-Sha256:
>  098ca2904bf11443672b48ea002dda9e9c275af8c75169d776afa38d93d1b8b1 2243 
> xserver-xorg-video-siliconmotion_1.7.9-2.dsc
>  3e02f26a5017a5543c9ece0adbdde957498484ec17ab42f69f9f7e8ae9983e58 15543 
> xserver-xorg-video-siliconmotion_1.7.9-2.diff.gz
> Files:
>  e52494fbf64d45f2912a919357c215af 2243 x11 optional 
> xserver-xorg-video-siliconmotion_1.7.9-2.dsc
>  b21b0d8f6ea741e1942bf5b582a27eab 15543 x11 optional 
> xserver-xorg-video-siliconmotion_1.7.9-2.diff.gz
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iQIcBAEBCAAGBQJYwUULAAoJEMtwMWWoiYTcC0UP/R1Wb1enpTNyu2TB1ci255SA
> GyIEzU9FuhlEvnnX1SDNYdP4Q6WEMTDq+i/LSZhEFkikVPl29qjjChvCFAupsk8b
> VwzsRPZCiu6GtBwuQCw9BBvYumkXkIzxpzn4pwx9Bz4BMvfswKZgjjDkFR+wsr7X
> wxTsaex9B6aJcdUo4irUFBTUmF7+PuHIAxexigkfVAJ7D/47oM03yDS5ZrFGyE7i
> sLiojnCG9AC7EEQXc0kYoC7fBzvbyF6Zylc1mfBMYajXywj7KOXRS8IL/1/gyDpU
> 3Csyy3g7uCXgxjCRVBSqW04unaaNAmK5tG0wok/CIYSnPwAKwSV6V3hZWfJiYrAX
> 8XNxfFGiK0yshV4quN1ygMDbg3iniNcrQnolkIqMH+7EjT6xHSQcCWoLwB45+jsH
> 9knDGNbVurVQm5USxN/wHP50SwUyqktPoXG4L71yl1AsvvoGN+qbXNPVyQcvufzp
> 8ZtHHUcO3t5BbmV3wQ2klgbj2ZF+SDHQosF6NMV1DXLqaEzbXO793NncSpXe1gnz
> f2jIn71UkUYrBlgWvWZOvLUknRWaxktXf3Zt8cVpHZw99xgs1kd/9oFRsqDG+6Db
> ImcyvodkOvKbPiEdARIn3zBlPKMAacVQ//cz+Dpz8J/Q9Q3grx3zaWi2rQhow06K
> USKk/fsl5CqGsWHtJ5g9
> =kOiK
> -END PGP SIGNATURE-

> Date: Mon, 30 Jan 2017 20:02:51 +0900
> From: Jonny 
> To: sub...@bugs.debian.org
> Subject: It can't start by a segmentation fault
> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; i686-pc-linux-gnu)
> 
> Package: xserver-xorg-video-siliconmotion
> Version: 1:1.7.9-1
> Severity: critical
> 
> Hi,
> 
> it was not able to start at all after I was rebuilt in xorg-server after 1.19.
> It can start in xserver-xorg-core 2:1.18.4-2 and 
> xserver-xorg-video-siliconmiton 1:1.7.8-2.

Hi,

could you please verify that xserver-xorg-video-siliconmotion 1:1.7.9-2
fixes your issue?

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#810913: mesa: Enable OpenCL on ppc64el

[Andreas Boll]

On Mon, Jul 25, 2016 at 03:28:06PM -0500, Timothy Pearson wrote:
> > As I understand your first mail in this report, this requires a fix
> > somewhere first?  (I wouldn't want to apply a "temporary" patch in
> > Debian.)
> 
> Unfortunately it doesn't look like upstream is going to patch their code. 
> There is a protracted "blame game" going on between mesa and gcc:
> https://bugs.freedesktop.org/show_bug.cgi?id=93687
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58241
> 
> Master Khronos bug report (unfortunately largely ignored):
> https://www.khronos.org/bugzilla/show_bug.cgi?id=1449
> 
> I suspect this won't be dealt with unless downstream distributions patch
> the codebase themselves.
> 
> Thanks!

Hi Timothy,

there seems to be some progress on this issue.
A new patch has been proposed on the upstream mailing list.

Could you please try the following patch?
https://patchwork.freedesktop.org/patch/141591/

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#826581: Issues on broadwell

[Andreas Boll]

Control: reassign -1 src:linux

On Sun, Feb 19, 2017 at 12:47:38AM +0100, Yuri D'Elia wrote:
> Starting with 4.8 kernels, booting with i915.enable_rc6=0 fixes this
> issue for me, including several other random crashes that were occurring
> without apparent reason.
> 
> I guess it would be proper to move this report against one of the
> current kernel images, since the problem still persists on current sid
> kernels.

Yeah, reassigning to src:linux.

Please be prepared to provide more information / logs to the kernel
maintainers.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#775855: closed by Emilio Pozuelo Monfort <po...@debian.org> (Bug#775855: fixed in weston 1.12.0-2)

[Andreas Boll]

This change has been reverted for stretch. Reopening.

 weston (1.12.0-3) unstable; urgency=medium
 .
   * Remove useless dependency on libegl1-mesa-drivers.
   * Disable the freerdp backend for stretch. freerdp2 doesn't build
 everywhere and is not in testing, and the backend fails to build
 against our snapshot of freerdp 1.
   * Drop obsolete --enable-libinput-backend configure switch.


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#850658: closed by Emilio Pozuelo Monfort <po...@debian.org> (Bug#850658: fixed in weston 1.12.0-2)

[Andreas Boll]

This change has been reverted for stretch. Reopening.

 weston (1.12.0-3) unstable; urgency=medium
 .
   * Remove useless dependency on libegl1-mesa-drivers.
   * Disable the freerdp backend for stretch. freerdp2 doesn't build
 everywhere and is not in testing, and the backend fails to build
 against our snapshot of freerdp 1.
   * Drop obsolete --enable-libinput-backend configure switch.


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#855120: opentk: Please disable OpenGL ES 1 support

[Andreas Boll]

Source: opentk
Version: 1.1.4c+dfsg-2
Severity: normal

Dear Maintainer,

we are in the process of removing OpenGL ES 1 support for buster. We
have gone ahead and uploaded Mesa version 17.0.0~rc3-1 (with disabled
GLES1 support) to experimental. Thus the packages libgles1-mesa-dev and
libgles1-mesa won't be available for buster.

Please disable OpenGL ES 1 support in opentk and consider uploading a
version with disabled GLES1 support to experimental for easier testing
during the freeze of stretch.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#855122: mesa-demos: Please disable OpenGL ES 1 support

[Andreas Boll]

Source: mesa-demos
Version: 8.3.0-3
Severity: normal

Dear Maintainer,

we are in the process of removing OpenGL ES 1 support for buster. We
have gone ahead and uploaded Mesa version 17.0.0~rc3-1 (with disabled
GLES1 support) to experimental. Thus the packages libgles1-mesa-dev and
libgles1-mesa won't be available for buster.

Please disable OpenGL ES 1 support in mesa-demos and consider uploading a
version with disabled GLES1 support to experimental for easier testing
during the freeze of stretch.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#855119: apitrace: Please disable OpenGL ES 1 support

[Andreas Boll]

Source: apitrace
Version: 7.1+git20160531.2d78bef0+repack-1.1
Severity: normal

Dear Maintainer,

we are in the process of removing OpenGL ES 1 support for buster. We
have gone ahead and uploaded Mesa version 17.0.0~rc3-1 (with disabled
GLES1 support) to experimental. Thus the packages libgles1-mesa-dev and
libgles1-mesa won't be available for buster.

Please disable OpenGL ES 1 support in apitrace and consider uploading a
version with disabled GLES1 support to experimental for easier testing
during the freeze of stretch.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#855117: vlc: Please disable OpenGL ES 1 support

[Andreas Boll]

Source: vlc
Version: 2.2.4-13
Severity: normal

Dear Maintainer,

we are in the process of removing OpenGL ES 1 support for buster. We
have gone ahead and uploaded Mesa version 17.0.0~rc3-1 (with disabled
GLES1 support) to experimental. Thus the packages libgles1-mesa-dev and
libgles1-mesa won't be available for buster.

Please disable OpenGL ES 1 support in vlc and consider uploading a
version with disabled GLES1 support to experimental for easier testing
during the freeze of stretch.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#852614: mesa: Please enable the etnaviv gallium driver on arm

[Andreas Boll]

Control: clone -1 -2
Control: reassign -2 src:libdrm 2.4.74-1
Control: retitle -2 libdrm: Please enable etnaviv on arm
Control: block -1 by -2

On Wed, Jan 25, 2017 at 04:59:17PM +0100, Andreas Henriksson wrote:
> Source: mesa
> Version: 17.0.0~rc1-1
> Severity: wishlist
> 
> Dear Maintainer,
> 
> There's a new (arm) gallium driver in mesa 17 called etnaviv for
> Vivante GC* GPUs, notably used on the Wandboard
> (which is an officially supported board by debian:
> https://www.debian.org/releases/stable/armhf/ch02s01.html.en#armhf-armmp-supported-platforms
> )
> 
> Please consider enabling and shipping it!

Sure, but we need to enable etnaviv support in libdrm first.

On which arm architectures should we enable etnaviv? armel/armhf/arm64
I guess only on armhf since the kernel has enabled DRM_ETNAVIV only on
armhf.

Do we need to enable the imx gallium driver too?

> 
> Regards,
> Andreas Henriksson
> 
> PS. A mesa 17 backport to stretch (with etnaviv enabled) would be nice.

Once stretch is released and Mesa >= 17 is in buster we can do a
backport.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#852616: llvm-toolchain-3.9: Please revert "AMDGPU: Fix an interaction between WQM and polygon stippling"

[Andreas Boll]

Source: llvm-toolchain-3.9
Version: 1:3.9.1-3
Severity: important
Tags: upstream
Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=99078

Dear Maintainer,

please revert the following commit:

AMDGPU: Fix an interaction between WQM and polygon stippling
https://github.com/llvm-mirror/llvm/commit/c280d74837d8239fc6cf567576b766ca3f4844c5

This commit causes wrong colors in icons when using radeonsi + LLVM
3.9.1.

This regression was introduced with LLVM 3.9.1.

See also:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.9/+bug/1656620
https://llvm.org/bugs/show_bug.cgi?id=31722

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#851768: dch: please allow dch -r --team

[Andreas Boll]

Package: devscripts
Version: 2.17.0
Severity: wishlist

Dear Maintainer,

it would be nice if dch could allow combining -r with --team. It
should do the same as dch -r but it should additionally add a "Team
upload." changelog comment as first entry.

Here's an example of how it should work:

-foobar (1.0.1-1) UNRELEASED; urgency=medium
+foobar (1.0.1-1) unstable; urgency=medium

+ * Team upload.
  * New upstream release.
  * Foo bar.

- -- John Doe  Wed, 16 Jan 2017 14:14:14 +0100
+ -- John Doe  Wed, 18 Jan 2017 16:16:16 +0100


Currently one has to manually add the "Team upload." comment before doing
dch -r.

Doing a dch --team just before the dch -r command won't work, as it adds a
hole new changelog section with an incremented release number.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#851130: debhelper: dh runs dh_quilt_patch after dh_autoreconf in compat 10

[Andreas Boll]

Package: debhelper
Version: 10.2.3
Severity: important

Dear Maintainer,

in compat level 10 dh runs dh_quilt_patch after dh_autoreconf for source
format 1.0 packages. Thus it won't apply the patches early enough and
causes issues like [1]. Switching back to compat 9 fixes this issue.

Please run dh_quilt_patch before dh_autoreconf in compat 10 too.

Thanks,
Andreas

[1] 
https://anonscm.debian.org/cgit/pkg-xorg/lib/mesa.git/commit/?h=ubuntu=5fb138afff6aa05898e81b9102e2c6b74e956072


signature.asc
Description: Digital signature

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

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

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

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

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#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

Bug#847073: xserver-xorg-video-intel still crashes, but just if attached to the dockingstation.

[Andreas Boll]

Nice to hear!

Andreas

2017-01-09 10:12 GMT+01:00 Andreas Gocht <andreas.go...@gmail.com>:
> Hey there,
>
> it seems to work with the new driver.
>
> Thank you.
>
> Best,
>
> Andreas
>
> 2016-12-22 16:21 GMT+01:00 Andreas Boll <andreas.boll@gmail.com>:
>>
>> On Thu, Dec 22, 2016 at 02:59:51PM +0100, Andreas Gocht wrote:
>> > Dear all,
>> >
>> > I tried the new package. Unfortunately, the Intel driver still crashes,
>> > but
>> > just if I am attached to my docking station. Otherwise it works just
>> > fine.
>> >
>> > Attached you'll find the Xorg log, and the backtrace. I am using a
>> > Lenovo
>> > T540p with an ThinkPad Ultra Dock. I have a Intel(R) Core(TM) i7-4710MQ
>> > CPU
>> > installed.
>> >
>> > Best,
>> >
>> > Andreas
>>
>> Hi,
>>
>> according to your attached Xorg log you are still using the old package:
>>
>> [  5374.174] (II) intel(0): SNA compiled: xserver-xorg-video-intel
>> 2:2.99.917+git20161105-1+b1
>>
>> Please make sure that you have installed 2:2.99.917+git20161206-1 and
>> restarted your xserver.
>>
>> Thanks,
>> Andreas
>
>

Bug#847073: xserver-xorg-video-intel still crashes, but just if attached to the dockingstation.

[Andreas Boll]

On Thu, Dec 22, 2016 at 02:59:51PM +0100, Andreas Gocht wrote:
> Dear all,
> 
> I tried the new package. Unfortunately, the Intel driver still crashes, but
> just if I am attached to my docking station. Otherwise it works just fine.
> 
> Attached you'll find the Xorg log, and the backtrace. I am using a Lenovo
> T540p with an ThinkPad Ultra Dock. I have a Intel(R) Core(TM) i7-4710MQ CPU
> installed.
> 
> Best,
> 
> Andreas

Hi,

according to your attached Xorg log you are still using the old package:

[  5374.174] (II) intel(0): SNA compiled: xserver-xorg-video-intel 
2:2.99.917+git20161105-1+b1

Please make sure that you have installed 2:2.99.917+git20161206-1 and
restarted your xserver.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#848792: beignet: Beignet causes blender crash

[Andreas Boll]

Forwarded post from rnpalmer:

> That message does come from beignet-opencl-icd
> (http://sources.debian.net/src/beignet/1.2.1-1/src/intel/intel_driver.c#L140),
> and means that context creation failed, but doesn't specify why.
> 
> To find out, please obtain a debug backtrace as follows:
> 
> $ sudoedit /etc/apt/sources.list
> [add the debug archive (deb
> http://debug.mirrors.debian.org/debian-debug/ testing-debug main) if
> not already present: https://wiki.debian.org/HowToGetABacktrace]
> $ sudo apt-get update
> $ sudo apt-get install gdb beignet-opencl-icd-dbgsym
> libdrm-intel-dbgsym
> $ gdb blender
> (gdb) set pagination 0
> (gdb) break intel/intel_bufmgr_gem.c:3175
> [this will probably ask whether to make it pending on future library
> load - answer yes]
> (gdb) run
> [trigger the crash - this will freeze, not close, the blender window]
> (gdb) bt full
> 
> What hardware are you using (lspci -nn | grep -e "\[03..\]:" )?
> 
> Does the beignet test suite
> (/usr/lib/x86_64-linux-gnu/beignet/utest_run from the beignet-dev
> package) also crash/fail?
> 
> Does the crash go away if you disable OpenCL in Blender's settings
> (https://www.blender.org/manual/preferences/system.html#compute-device)?
> 
> There are upstream bug reports that Blender's OpenCL doesn't work in
> beignet, but they appear to be different problems.


I guess this could be related to LLVM bug #848368. Blender crashes
because it uses different LLVM versions in the same process:
mesa-opencl-icd uses LLVM 3.9 and beignet-opencl-icd probably uses
LLVM 3.8.

It has been reported that Blender also crashes if pocl (using LLVM
3.8) and mesa-opencl-icd are installed at the same time
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846162#5).

See also bug #846410, kdevelop crashes if using two different LLVM
versions in the same process.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#848864: libtool: Get rid of excessive sed forks -- significant performance regression

[Andreas Boll]

Package: libtool
Version: 2.4.6-2
Severity: important
Tags: upstream fixed-upstream
Forwarded: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20006

Dear Maintainer,

libtool 2.4.6-0.1 has introduced a performance regression which results
in significant slowdown in compile time. Version 2.4.6-2 is still
affected.

Especially buildds of slower arches like mips* and arm* suffer a lot
from this performance regression. Here are a few examples how mesa is
affected by this bug:

[2016-02-07] Accepted libtool 2.4.6-0.1 (source amd64 all) into unstable

mipsel: https://buildd.debian.org/status/logs.php?pkg=mesa=mipsel
11.1.1-2 (sid)  Maybe-Successful2016-01-15 19:04:32 mipsel-aql-02   
50m
11.1.2-1 (sid)  Maybe-Successful2016-02-11 14:30:46 mipsel-aql-02   
1h 22m

armhf: https://buildd.debian.org/status/logs.php?pkg=mesa=armhf
11.1.1-2 (sid)  Maybe-Successful2016-01-15 19:15:32 hoiby   34m
11.1.2-1 (sid)  Maybe-Successful2016-02-11 12:39:21 hoiby   52m

i386: https://buildd.debian.org/status/logs.php?pkg=mesa=i386
11.1.1-2 (sid)  Maybe-Successful2016-01-15 18:20:15 x86-grnet-01
7m
11.1.2-1 (sid)  Maybe-Successful2016-02-11 11:54:33 x86-grnet-01
10m

x32: https://buildd.debian.org/status/logs.php?pkg=mesa=x32
11.1.1-2 (sid)  Maybe-Successful2016-01-15 18:36:30 physik  17m
11.1.2-1 (sid)  Maybe-Successful2016-02-11 12:36:45 physik  28m

or systemd on x32: 
https://buildd.debian.org/status/logs.php?pkg=systemd=x32
228-6 (sid) Maybe-Successful2016-02-04 12:42:54 physik  42m
229-1 (sid) Maybe-Successful2016-02-11 23:35:48 physik  1h 3m


This bug has been reported to upstream and has been fixed already [1].
There's also a blog post about this issue [2].
Unfortunately upstream hasn't released a new upstream release with those
fixes yet.

Please cherry-pick the following three patches from upstream master
branch to mitigate the excessive sed forking:

http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=32f0df9835ac15ac17e04be57c368172c3ad1d19
http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=16dbc070d32e6d4601cb5878dfdf69f2e29c84e1
http://git.savannah.gnu.org/cgit/libtool.git/commit/?id=9187e9a231e0a06cc29c336857e95f07f855b2c9

With those patches applied, libtool 2.4.6 still isn't as fast as 2.4.2
was, but it's much better than the unpatched version.


Thanks,
Andreas

[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20006
[2] https://harald.hoyer.xyz/2015/03/05/libtool-getting-rid-of-18-sed-forks/


signature.asc
Description: Digital signature

Bug#846698: xserver-xorg-video-sisusb: FTBFS: ../../src/sisusb_driver.c:1670:6: error: too many arguments to function 'pScreen->BlockHandler'

[Andreas Boll]

Control: tags -1 patch fixed-upstream pending

Hi,

thanks much for your work. I've noticed that upstream has already
merged a patch for compatibility with xserver 1.19 [1]. I've gone
ahead and cherry-picked that patch from upstream (the diff is
identical, but it has proper authorship).  Furthermore I've cleaned up
the package a little bit and included your second patch to fix
#745173.

We'll upload the fixed package soon.

Thanks,
Andreas

[1] 
https://cgit.freedesktop.org/xorg/driver/xf86-video-sisusb/commit/?id=6d44eb7a6075b9cc359b44282a7095a8b46c8a38

On Thu, Dec 15, 2016 at 04:41:29PM +0100, Mateusz Łukasik wrote:
> Tags: control + patch
> 
> Hi,
> 
> My NMU debdiff to fix that. Patch is take over from PLD Linux.
> 
> 
> -- 
>  .''`.  Mateusz Łukasik
> : :' :  http://mati75.eu
> `. `'   Debian Member - mat...@linuxmint.pl
>   `-GPG: D93B 0C12 C8D0 4D7A AFBC  FA27 CCD9 1D61 11A0 6851
> 
> 

> diff -u xserver-xorg-video-sisusb-0.9.6/debian/changelog 
> xserver-xorg-video-sisusb-0.9.6/debian/changelog
> --- xserver-xorg-video-sisusb-0.9.6/debian/changelog
> +++ xserver-xorg-video-sisusb-0.9.6/debian/changelog
> @@ -1,3 +1,11 @@
> +xserver-xorg-video-sisusb (1:0.9.6-2.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Fix FTBFS with xserver 1.19. (Closes: #846698)
> +  * Use arch:linux-any. (Closes: #745173)
> +
> + -- Mateusz Łukasik   Mon, 12 Dec 2016 09:58:58 +0100
> +
>  xserver-xorg-video-sisusb (1:0.9.6-2) unstable; urgency=low
>  
>* Release to unstable.
> diff -u xserver-xorg-video-sisusb-0.9.6/debian/control 
> xserver-xorg-video-sisusb-0.9.6/debian/control
> --- xserver-xorg-video-sisusb-0.9.6/debian/control
> +++ xserver-xorg-video-sisusb-0.9.6/debian/control
> @@ -22,7 +22,7 @@
>  Vcs-Browser: 
> http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-sisusb.git
>  
>  Package: xserver-xorg-video-sisusb
> -Architecture: any
> +Architecture: linux-any
>  Depends:
>   ${shlibs:Depends},
>   ${misc:Depends},
> diff -u xserver-xorg-video-sisusb-0.9.6/debian/patches/series 
> xserver-xorg-video-sisusb-0.9.6/debian/patches/series
> --- xserver-xorg-video-sisusb-0.9.6/debian/patches/series
> +++ xserver-xorg-video-sisusb-0.9.6/debian/patches/series
> @@ -1,0 +2 @@
> +xserver-1.19.patch
> only in patch2:
> unchanged:
> --- xserver-xorg-video-sisusb-0.9.6.orig/debian/patches/xserver-1.19.patch
> +++ xserver-xorg-video-sisusb-0.9.6/debian/patches/xserver-1.19.patch
> @@ -0,0 +1,16 @@
> +--- xf86-video-chips-1.2.6/src/compat-api.h~ 2015-09-26 18:28:01.0 
> +0200
>  xf86-video-chips-1.2.6/src/compat-api.h  2016-11-28 09:12:37.337570460 
> +0100
> +@@ -75,8 +75,13 @@
> + 
> + #define SCREEN_INIT_ARGS_DECL ScreenPtr pScreen, int argc, char **argv
> + 
> ++#if ABI_VIDEODRV_VERSION >= SET_ABI_VERSION(23, 0)
> ++#define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout
> ++#define BLOCKHANDLER_ARGS arg, pTimeout
> ++#else
> + #define BLOCKHANDLER_ARGS_DECL ScreenPtr arg, pointer pTimeout, pointer 
> pReadmask
> + #define BLOCKHANDLER_ARGS arg, pTimeout, pReadmask
> ++#endif
> + 
> + #define CLOSE_SCREEN_ARGS_DECL ScreenPtr pScreen
> + #define CLOSE_SCREEN_ARGS pScreen



signature.asc
Description: Digital signature

Bug#758094: libgl1-mesa-glx:x32: SIGSEGV in OpenGL applications on x32

[Andreas Boll]

Control: tags -1 moreinfo

On Thu, Aug 14, 2014 at 08:19:54AM -0400, Daniel Schepler wrote:
> On Thu, Aug 14, 2014 at 4:46 AM, Thorsten Glaser  wrote:
> > Package: libgl1-mesa-glx
> > Version: 10.2.5-1
> > Severity: normal
> >
> > Hi!
> >
> > After crossgrading from i386 to x32, OpenGL applications crash.
> >
> > glxgears from mesa-utils:i386 (8.2.0-1) works, but
> > glxgears from mesa-utils:x32 (8.2.0-1) fails:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0xf76db60b in glLightfv () from /usr/lib/x86_64-linux-gnux32/libGL.so.1
> > (gdb) bt
> > #0  0xf76db60b in glLightfv () from /usr/lib/x86_64-linux-gnux32/libGL.so.1
> > #1  0x0040146f in ?? ()
> > #2  0xf6aceeea in __libc_start_main (main=, argc=1, 
> > argv=,
> > init=, fini=, rtld_fini=, 
> > stack_end=0xd448)
> > at libc-start.c:287
> > #3  0x00401cfc in ?? ()
> >
> > I've first noticed that in "xlock -nolock -mode cage",
> > which, with debugging information, has:
> >
> > Program terminated with signal SIGSEGV, Segmentation fault.
> > #0  0xf6af524b in glGetBooleanv () from 
> > /usr/lib/x86_64-linux-gnux32/libGL.so.1
> > (gdb) bt
> > #0  0xf6af524b in glGetBooleanv () from 
> > /usr/lib/x86_64-linux-gnux32/libGL.so.1
> > #1  0x0040fcfe in init_GL (mi=mi@entry=0x228bde0) at visgl.c:287
> > #2  0x004dc6d4 in init_cage (mi=) at cage.c:400
> > #3  0x0040e462 in call_init_hook (ls=0x823340 , 
> > mi=) at mode.c:1290
> > #4  0x0040887c in justDisplay (display=0x226e870) at xlock.c:2821
> > #5  0x0040764f in main (argc=36104304, argv=0x0) at xlock.c:3998
> >
> > Bugs occur in (first glxgears, then xlock):
> >
> > (gdb) disas
> > Dump of assembler code for function glLightfv:
> >0xf76db600 <+0>: movrax,QWORD PTR [rip+0x21b9f1]# 
> > 0xf78f6ff8
> >0xf76db607 <+7>: movr11,QWORD PTR fs:[rax]
> > => 0xf76db60b <+11>:jmpQWORD PTR [r11+0x500]
> >
> > (gdb) disas
> > Dump of assembler code for function glGetBooleanv:
> >0xf6af5240 <+0>: movrax,QWORD PTR [rip+0x21adb1]# 
> > 0xf6d0fff8
> >0xf6af5247 <+7>: movr11,QWORD PTR fs:[rax]
> > => 0xf6af524b <+11>:jmpQWORD PTR [r11+0x810]
> >
> > So this appears to be an indirect function call both times.
> 
> Always before, when I needed to hand-patch the mesa sources to get a
> custom build, I would disable the x86_64 assembly altogether.  It
> would appear that some more porting of the assembly to x32 is needed
> before it's safe to use.  In this case, my guess would be that the
> assembly is indexing into an array of function pointers, which on x32
> would need to be adjusted to jmpl *(4*index, %reg) or maybe addr32 jmp
> *(4*index, %{reg}d) instead of jmpq *(8*index, %reg).
> -- 
> Daniel Schepler

Could you retest with mesa 13.0.2-3 from sid?
I've disabled assembly usage on x32.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#808784: Refresh the xserver-xorg-video-openchrome package

[Andreas Boll]

Hi Dylan,

Welcome to the X Strike Force team!

Please join pkg-xorg group on Alioth [1].
No need to push the package on mentors.
Just prepare it in git and some DD of the team will upload the package for you.
Feel free to join us on IRC [oftc] #debian-x

Thanks,
Andreas

[1] https://alioth.debian.org/projects/pkg-xorg/

2016-12-07 22:55 GMT+01:00 Dylan <bob.dyb...@gmail.com>:
> Hi Andreas,
>
> 2016-12-05 14:31 GMT+01:00 Andreas Boll <andreas.boll@gmail.com>:
>> I have some comments for further improvements:
>>
>> Please use `wrap-and-sort -a -s` to be more consistent with the
>> previous style and other xsf packages.
>>
>> With the debhelper compat change you can also remove the build-dep on
>> dh-autoreconf since debhelper >= 10 depends on dh-autoreconf itself.
>> Furthermore you can remove autoreconf from the dh line in debian/rules
>> since debhelper compat level 10 enables it by default. See also [1].
>>
>> Other than that your changes look good to me.
>>
>
> Thanks for your review. I pushed your suggestions and some other changes.
>
> What do you prefer for the next steps (push on Alioth and the sponsorship)?
> Should I join the team to push myself these changes on the repository?
> Should I push the package on mentors.debian.net?
>
> Thanks
>
> Best regards,
> Dylan

Bug#846162: closed by Andreas Boll <andreas.boll....@gmail.com> (Re: Bug#846162: mesa-opencl-icd: Corrupt POLARIS10 ref in clinfo via mesa-opencl-icd 13.0.1-2)

[Andreas Boll]

Sure, once clang-3.9.1 lands in unstable I can rebuild Mesa.

Thanks,
Andreas

On Tue, Dec 06, 2016 at 12:48:59PM -0800, Marc Jeffrey Driftmeyer wrote:
> Having installed this do we not need Mesa to be rebuilt against it to verify 
> it? I checked CLINFO and it still doesn’t recognize the GPGPU. 
> 
> Am I to assume a new rebuild of Mesa 13.0.2 is in the works?
> 
> - Marc 
> 
> 
> > On Dec 6, 2016, at 7:33 AM, Debian Bug Tracking System 
> > <ow...@bugs.debian.org> wrote:
> > 
> > This is an automatic notification regarding your Bug report
> > which was filed against the clang-3.9 package:
> > 
> > #846162: clang-3.9: Corrupt POLARIS10 ref in clinfo via mesa-opencl-icd 
> > 13.0.1-2
> > 
> > It has been closed by Andreas Boll <andreas.boll@gmail.com>.
> > 
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Andreas Boll 
> > <andreas.boll@gmail.com> by
> > replying to this email.
> > 
> > 
> > -- 
> > 846162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846162
> > Debian Bug Tracking System
> > Contact ow...@bugs.debian.org with problems
> > 
> > From: Andreas Boll <andreas.boll@gmail.com>
> > Subject: Re: Bug#846162: mesa-opencl-icd: Corrupt POLARIS10 ref in clinfo 
> > via mesa-opencl-icd 13.0.1-2
> > Date: December 6, 2016 at 7:29:18 AM PST
> > To: Marc Jeffrey Driftmeyer <m...@reanimality.com>, 
> > 846162-d...@bugs.debian.org
> > Cc: pkg-llvm-t...@lists.alioth.debian.org
> > 
> > 
> > Version: 1:3.9.1~+rc2-1~exp1
> > 
> > Upstream has backported clang support for polaris GPUs and it's
> > already included in version 1:3.9.1~+rc2-1~exp1 [1].
> > Closing this bug accordingly.
> > 
> > Thanks,
> > Andreas
> > 
> > [1] 
> > https://sources.debian.net/src/llvm-toolchain-3.9/1:3.9.1~%2Brc2-1~exp1/clang/lib/Basic/Targets.cpp/#L2099
> > 
> > On Tue, Nov 29, 2016 at 03:38:54PM -0800, Marc Jeffrey Driftmeyer wrote:
> >> As an AMD stockholder it truly baffles me; and as a NeXT/Apple engineering 
> >> alum I am surprised that Raja didn’t chew ass and make sure their new 
> >> GPGPUs were supported in the actual software stack their entire software 
> >> future depends upon.
> >> 
> >>  .Case("polaris10", GK_VOLCANIC_ISLANDS)
> >>  .Case("polaris11", GK_VOLCANIC_ISLANDS)
> >> 
> >> Two lousy lines of code. I’m glad you tracked it down and I was a pain in 
> >> the ass for pointing it out.
> >> 
> >> Looking forward to actually being able to use the card I bought to its 
> >> fullest. 
> >> 
> >> Sincerely,
> >> 
> >> Marc Jeffrey Driftmeyer
> >> 
> >>> On Nov 29, 2016, at 9:06 AM, Andreas Boll <andreas.boll@gmail.com> 
> >>> wrote:
> >>> 
> >>> r280120


signature.asc
Description: Digital signature

Bug#847229: xserver-xorg-video-intel: Xserver crashes when Option "AccelMethod" "sna" is enables in xorg.conf

[Andreas Boll]

Control: forcemerge 847073 -1

This is a duplicate of bug #847073.

Thanks,
Andreas

On Tue, Dec 06, 2016 at 05:48:00PM +0100, Andreas Gocht wrote:
> Package: xserver-xorg-video-intel
> Version: 2:2.99.917+git20161105-1
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> In order to load the intel graphic driver as default I had to add an
> /etc/X11/xorg.conf.d/09-intel.conf . With the default graphic driver settings
> the XServer crashed.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> I changed the Option "AccelMethod" to "uxa". When I change back to "sna" it
> crashes again.
> 
>* What was the outcome of this action?
> 
> Changing to "uxa" solved the problem. However, as far as I know sna is 
> supposed
> to replace uxa. Moreover, sna is default.
> 
>* What outcome did you expect instead?
> 
> I would expect the XServer to work with default settings ;-)
> 
> I did a bit of bug tracking. First of all there is the XOrg log, which I
> attached. Moreover, I was able to create a backtrace with help of the
> following article:
> 
> https://www.x.org/wiki/Development/Documentation/ServerDebugging/
> 
> The backtrace is attached as well. Finally, there are a few info’s about my
> system:
> I am using a Lenovo T540p, which has an additional Nvidia graphic card. I use 
> a
> docking station with two monitors attached. The screen of the Lenovo is
> deactivated.
> 
> Finally the package version is 2:2.99.917+git20161105-1
> 
> I hope this information might help.
> 
> Best,
> 
> Andreas
> 
> 

snip

> 
> Thread 1 "Xorg" received signal SIGSEGV, Segmentation fault.
> 0x75d3a889 in __readdir (dirp=dirp@entry=0x0) at 
> ../sysdeps/posix/readdir.c:44
> 44../sysdeps/posix/readdir.c: Datei oder Verzeichnis nicht gefunden.
> #0  0x75d3a889 in __readdir (dirp=dirp@entry=0x0) at 
> ../sysdeps/posix/readdir.c:44
> dp = 
> saved_errno = 2
> #1  0x71a76618 in has_connector_backlight (output=0x559e90d0, 
> output=0x559e90d0) at ../../../src/sna/sna_display.c:1036
> sna_output = 
> dir = 0x0
> str = 0x0
> path = "/sys/class/drm/card0-DP-3\000A-2/modes\000\000\000m\000ht", 
> '\000' , "\003\000\000\000\060", '\000' , 
> "[\000\000\000n", '\000' , 
> "w\000\000\000|\000\000\000\070\331\377\377\377\177\000\000\000\373\001\366\377\177\000\000
>  
> \000\000\000\000\000\000\000\000\020\350\367\377\177\000\000\b\000\000\000\000\000\000\000
>  
> \333\377\377\377\177\000\000\240\333\377\377\377\177\000\000\224\035\320\365\377\177\000\000\005\000\000\000\000\000\000\000\340\332\377\377\377\177\000\000\340\331\377\377\377\177\000\000"...
> de = 
> #2  sna_output_backlight_init (output=0x559e90d0) at 
> ../../../src/sna/sna_display.c:1083
> sna_output = 0x559e8fa0
> from = X_CONFIG
> pci = 
> best_iface = 
> #3  sna_output_add (sna=sna@entry=0x77e81000, id=, 
> serial=serial@entry=0) at ../../../src/sna/sna_display.c:5144
> scrn = 0x559e2130
> config = 0x559e3830
> compat_conn = {conn = {encoders_ptr = 140737488344608, modes_ptr = 
> 140737488344768, props_ptr = 93824997036144, prop_values_ptr = 
> 93824997036176, count_modes = 0, count_props = 6, count_encoders = 3, 
> encoder_id = 0, 
> connector_id = 61, connector_type = 10, connector_type_id = 3, 
> connection = 2, mm_width = 0, mm_height = 0, subpixel = 0, pad = 0}, pad = 
> {4294956576, 32767, 4294956736, 32767, 1436455024, 21845, 1436455056, 21845, 
> 0, 6, 3, 0, 
> 61, 10, 3, 2, 0, 0, 0, 0}}
> enc = {encoder_id = 0, encoder_type = 0, crtc_id = 0, possible_crtcs 
> = 0, possible_clones = 0}
> dummy = {clock = 4294957104, hdisplay = 32767, hsync_start = 0, 
> hsync_end = 55344, htotal = 65535, hskew = 32767, vdisplay = 0, vsync_start = 
> 55344, vsync_end = 65535, vtotal = 32767, vscan = 0, vrefresh = 24, flags = 
> 48, 
>   type = 4294958416, name = 
> "\377\177\000\000\220\334\377\377\377\177\000\000/\334\377\377\377\177", 
> '\000' }
> sna_output = 0x559e8fa0
> outputs = 
> output = 0x559e90d0
> possible_encoders = 
> attached_encoders = 
> possible_crtcs = 
> output_name = 
> name = 
> "DP2-1\000\000\000\070\200\311\365\377\177\000\000p\331\377\377\377\177\000\000@0\336\367\377\177\000"
> path = 
> len = 5
> i = 
> #4  0x71a77d47 in sna_mode_pre_init (scrn=scrn@entry=0x559e2130, 
> sna=sna@entry=0x77e81000) at ../../../src/sna/sna_display.c:7467
> xf86_config = 0x559e3830
> res = 0x559e3750
> num_fake = 1
> i = 6
> #5  0x71a80603 in sna_pre_init (scrn=0x559e2130, probe= out>) at ../../../src/sna/sna_driver.c:658
> sna = 
> buf = "x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, 
> 

Bug#846882: wrong scale for backlight with Xfce

[Andreas Boll]

Control: tags -1 upstream

On Tue, Dec 06, 2016 at 05:05:41PM +0100, Rpnpif wrote:
> Le  6 décembre 2016, Andreas Boll a écrit :
> > xserver-xorg-video-intel has some special backlight handling [2] so
> > it's plausible that an updated package could cause regressions related
> > to backlight.
> 
> > > [13.881] 
> > > X.Org X Server 1.16.4
> > > Release Date: 2014-12-20
> > > [13.881] X Protocol Version 11, Revision 0
> > > [13.881] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
> > > [13.881] Current Operating System: Linux Asus-901 
> > > 4.7.0-0.bpo.1-686-pae #1 SMP Debian 4.7.8-1~bpo8+1 (2016-10-19) i686
> > > [13.881] Kernel command line: 
> > > BOOT_IMAGE=/boot/vmlinuz-4.7.0-0.bpo.1-686-pae 
> > > root=UUID=2ed3bc82-5cc0-4529-a13c-2e6f80b5b588 ro resume=/dev/sdb1 quiet  
> > 
> > snip
> > 
> > > [14.063] (II) intel(0): Using Kernel Mode Setting driver: i915, 
> > > version 1.6.0 20160425
> > > [14.063] (II) intel(0): SNA compiled: xserver-xorg-video-intel 
> > > 2:2.99.917+git20161105-1~bpo8+1 (Vincent Cheng <vch...@debian.org>)  
> > 
> > Reassigning to xserver-xorg-video-intel for now.
> > 
> > Thanks,
> > Andreas
> > 
> > [1] http://snapshot.debian.org/package/xserver-xorg-video-intel/
> > [2] 
> > https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/?qt=grep=backlight
> 
> You are right!
> The 2:2.99.917+git20160706-1~bpo8+1 release works fine but not
> 2:2.99.917+git20161105-1~bpo8+1.
> 
> So it is really a regression on the last release.
> Perhaps a wrong choice of the best iface or about, or other thing.
> 
> My system have two backlight interfaces:
> /sys/class/backlight/eeepc and /sys/class/backlight/intel_backlight
> 
> The first is safer but the second permits atomic variations of the
> backlight.
> 
> Thank you.
> 
> -- 
> Alain Rpnpif

Please follow
https://01.org/linuxgraphics/documentation/how-report-bugs
to file a bug with intel.  Let us know the bug number for tracking.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#846882: libdrm2: wrong scale for backlight with Xfce

[Andreas Boll]

Control: reassign -1 xserver-xorg-video-intel 2:2.99.917+git20161105-1~bpo8+1
Control: retitle -1 xserver-xorg-video-intel: wrong scale for backlight with 
Xfce

On Mon, Dec 05, 2016 at 06:37:28PM +0100, Rpnpif wrote:
> Hi,
> 
> Le  5 décembre 2016, Andreas Boll a écrit :
> 
> > Which older versions? Do you mean xserver-xorg-video-intel?
> > I guess it's related to the last upload of xserver-xorg-video-intel to
> > jessie-backports.
> 
> I spoke about the previous version in Jessie-backports. I do not
> remember the reference.

Can you try the previous xserver-xorg-video-intel backport version
2:2.99.917+git20160706-1~bpo8+1 from snapshot.d.o [1]?
> 
> I am not sure that xserver-xorg-video-intel is the culprit because
> lightdm works fine.

xserver-xorg-video-intel has some special backlight handling [2] so
it's plausible that an updated package could cause regressions related
to backlight.

> 
> Joined the logs.
> 
> Regards.
> 
> -- 
> Alain Rpnpif

> [13.881] 
> X.Org X Server 1.16.4
> Release Date: 2014-12-20
> [13.881] X Protocol Version 11, Revision 0
> [13.881] Build Operating System: Linux 3.2.0-4-amd64 i686 Debian
> [13.881] Current Operating System: Linux Asus-901 4.7.0-0.bpo.1-686-pae 
> #1 SMP Debian 4.7.8-1~bpo8+1 (2016-10-19) i686
> [13.881] Kernel command line: 
> BOOT_IMAGE=/boot/vmlinuz-4.7.0-0.bpo.1-686-pae 
> root=UUID=2ed3bc82-5cc0-4529-a13c-2e6f80b5b588 ro resume=/dev/sdb1 quiet

snip

> [14.063] (II) intel(0): Using Kernel Mode Setting driver: i915, version 
> 1.6.0 20160425
> [14.063] (II) intel(0): SNA compiled: xserver-xorg-video-intel 
> 2:2.99.917+git20161105-1~bpo8+1 (Vincent Cheng <vch...@debian.org>)

Reassigning to xserver-xorg-video-intel for now.

Thanks,
Andreas

[1] http://snapshot.debian.org/package/xserver-xorg-video-intel/
[2] 
https://cgit.freedesktop.org/xorg/driver/xf86-video-intel/log/?qt=grep=backlight


signature.asc
Description: Digital signature

Bug#808784: Refresh the xserver-xorg-video-openchrome package

[Andreas Boll]

Hi Dylan,

thanks much for working on xxv-openchrome!

I have some comments for further improvements:

Please use `wrap-and-sort -a -s` to be more consistent with the
previous style and other xsf packages.

With the debhelper compat change you can also remove the build-dep on
dh-autoreconf since debhelper >= 10 depends on dh-autoreconf itself.
Furthermore you can remove autoreconf from the dh line in debian/rules
since debhelper compat level 10 enables it by default. See also [1].

Other than that your changes look good to me.

Thanks,
Andreas

[1] 
https://anonscm.debian.org/cgit/pkg-xorg/lib/libdrm.git/commit/?id=d963fbc94795e4903f9ada320540380a3e774b7b

2016-12-04 0:31 GMT+01:00 Dylan :
> Hi the Debian X Strike Force team,
> The package of xserver-xorg-video-openchrome is quite outdated, with
> the reborn of openchrome project and the approaching of the Debian
> Freeze, it could be great to refresh the package.
>
> Since the package is RFA, I propose myself to update this package,
> maybe not to adopt in a first time. Let's see how I deal with it.
> Moreover, I don't have access to a supported hardware so a
> (co-?)maintainer with the hardware should be better.
>
> I am only DM, so I will need sponsor for this package. I have already
> started to update the package [1].
>
> Best regards,
> Dylan
>
> [1] https://bitbucket.org/Dybian/openchrome/
>

Bug#846882: libdrm2: wrong scale for backlight with Xfce

[Andreas Boll]

On Sat, Dec 03, 2016 at 10:57:58PM +0100, Alain wrote:
> Package: libdrm2
> Version: 2.4.73-1~bpo8+1
> Severity: normal
> 
> The scale of change of the intensity of the backlight is wrong.
> Changing this is done with the hot keys to increase or decrease.
> 
> The minimum get a black screen.
> cat /sys/class/backlight/eeepc/brigthness
> 0
> cat /sys/class/backlight/intel_backlight/brigthness
> 0
> 
> 1st press on the hot key : get also a black screen.
> cat /sys/class/backlight/eeepc/brigthness
> 1
> cat /sys/class/backlight/intel_backlight/brigthness
> 79787
> 
> 2nd press : get a medium intensity.
> cat /sys/class/backlight/eeepc/brigthness
> 2
> cat /sys/class/backlight/intel_backlight/brigthness
> 159374
> 
> 3rd to 12th press get a normal change of the backlight.
> To : 796875
> But the intensity of the 12th is less than the 11th.
> 
> Expected :
> The minimum should not light off the screen.
> /sys/class/backlight/intel_backlight/brigthness
> 159374
> >From /sys/class/backlight/eeepc/brigthness=1 to 10 or 12, the backlight 
> should change linearly without light off.
> 
> This buggy behaviour was seen only with Xfce, not with lightdm or the Linux 
> console.
> 
> The older libdrm and xserver-xorg work fine.

Which older versions? Do you mean xserver-xorg-video-intel?
I guess it's related to the last upload of xserver-xorg-video-intel to
jessie-backports.

Please attach the Xorg log and the output from dmesg.

Thanks,
Andreas

> 
> -- System Information:
> Debian Release: 8.6
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 4.7.0-0.bpo.1-686-pae (SMP w/2 CPU cores)
> Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages libdrm2 depends on:
> ii  libc6  2.19-18+deb8u6
> ii  multiarch-support  2.19-18+deb8u6
> 
> libdrm2 recommends no packages.
> 
> libdrm2 suggests no packages.
> 
> -- no debconf information


signature.asc
Description: Digital signature

Bug#847012: vlc: hardware accelaration must be disable to avoid scrambled video

[Andreas Boll]

On Sun, Dec 04, 2016 at 11:15:31PM +0100, Sebastian Ramacher wrote:
> Control: reassign -1 mesa-vdpau-drivers 13.0.2-1
> 
> On 2016-12-05 00:01:53, Karagkiaouris Diamantis wrote:
> > Package: src:vlc
> > Version: 2.2.4-9
> > Severity: important
> > 
> > Dear Maintainer,
> > 
> > Every time i try to open a dvd movie iso, it plays the video distorted.
> > The video iamge is scrabled and if i disable the video accelaration
> > everything seems to be working.
> > 
> > This is the output of vlc -vvv with hardware accelaration enabled:
> > 

snip

> > 
> > [7fa4580676d8] avcodec decoder: Using G3DVL VDPAU Driver Shared Library 
> > version 1.0 for hardware decoding.
> 
> This looks a lot like #846297 to me. Are you using a AMD card too?
> 
> In any case, reassinging to mesa is this issues looks like a driver bug.
> 
> Cheers
> 

Please provide the output from dmesg and vdpauinfo. Furthermore please
attach the Xorg log.

Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#846297: mesa-vdpau-drivers: breaks vdpau for mpeg2video with mpv and vlc

[Andreas Boll]

Control: forward -1 https://bugs.freedesktop.org/show_bug.cgi?id=98914

Thanks for the number.

Andreas

On Wed, Nov 30, 2016 at 04:20:17PM +0100, Jörg-Volker Peetz wrote:
> Hi,
> 
> have reported this upstream: 
> https://bugs.freedesktop.org/show_bug.cgi?id=98914
> Tracking number is 98914.
> Feel free to contact me, if further information is required.
> 
> Regards,
> jvp.
> 
> Andreas Boll wrote on 11/30/16 13:28:
> > Control: tags -1 + upstream
> > 
> > Hi,
> > 
> > please report this upstream to
> > https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa=Drivers%2FGallium%2Fr600
> > and let us know the bug number for tracking.
> > 
> > Thanks,
> > Andreas
> > 
> 


signature.asc
Description: Digital signature

Bug#846297: mesa-vdpau-drivers: breaks vdpau for mpeg2video with mpv and vlc

[Andreas Boll]

Control: tags -1 + upstream

Hi,

please report this upstream to
https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa=Drivers%2FGallium%2Fr600
and let us know the bug number for tracking.

Thanks,
Andreas

On Wed, Nov 30, 2016 at 12:19:34PM +0100, Jörg-Volker Peetz wrote:
> Hi,
> 
> please see the attached files.
> 
> Thanks for caring,
> jvp.
> 
> 
> Andreas Boll wrote on 11/30/16 11:56:
> > Hi,
> > 
> > please provide the output from dmesg and vdpauinfo. Furthermore the
> > Xorg log would be useful too.
> > 
> > Thanks,
> > Andreas
> > 


signature.asc
Description: Digital signature

Bug#846297: mesa-vdpau-drivers: breaks vdpau for mpeg2video with mpv and vlc

[Andreas Boll]

Hi,

please provide the output from dmesg and vdpauinfo. Furthermore the
Xorg log would be useful too.

Thanks,
Andreas

On Tue, Nov 29, 2016 at 10:47:18PM +0100, Jörg-Volker Peetz wrote:
> Package: mesa-vdpau-drivers
> Version: 13.0.2-1
> Severity: normal
> 
> Dear Maintainer,
> 
> on my AMD CPU/AMD GPU hybrid HP Pavilion notebook under X with radeon video
> driver the vdpau hardware video output for the mpeg2video codec broke 
> beginning
> with Mesa 13.0. Such videos are totally scrambled on the screen now.
> Codec h264 is still working.
> 
> What additional information is needed to help fix it?
> 
> Regards,
> jvp.
> 


signature.asc
Description: Digital signature

Bug#845331: xxv-omap still FTBFS against xserver 1.19

[Andreas Boll]

Control: tags -1 + fixed-upstream patch

Upstream has released a new version of xf86-video-omap with support for
xserver 1.19. See also [1].

Thanks,
Andreas

[1] 
https://cgit.freedesktop.org/xorg/driver/xf86-video-omap/log/?id=xf86-video-omap-0.4.5

On Thu, Nov 24, 2016 at 07:47:37PM +0100, Andreas Boll wrote:
> Control: reopen 845331
> 
> Unfortunately it wasn't enough to fix the build against xserver 1.19.
> Apparently xxv-omap needs to be ported to the new NotifyFd API.
> 
> Build log: 
> https://buildd.debian.org/status/fetch.php?pkg=xf86-video-omap=armhf=0.4.4-2=1479924520
> 
> Thanks,
> Andreas


signature.asc
Description: Digital signature

Bug#845639: Compatibility with xserver 1.19 / xorg-video-abi-23

[Andreas Boll]

Source: nvidia-graphics-drivers-legacy-304xx
Version: 304.132-1
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your xorg driver package compatible with xserver 1.19 (i.e.
supporting xorg-video-abi-23).


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845637: FTBFS with xserver 1.19

[Andreas Boll]

Source: xf86-video-glamo
Version: 0.0.0+20110719.gitcb9ed170-2
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your xorg driver package compatible with xserver 1.19 (i.e.
supporting xorg-video-abi-23).

Build log: 
https://buildd.debian.org/status/fetch.php?pkg=xf86-video-glamo=amd64=0.0.0%2B20110719.gitcb9ed170-2%2Bb3=1480025806


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845638: Compatibility with xserver 1.19 / xorg-video-abi-23

[Andreas Boll]

Source: nvidia-graphics-drivers
Version: 367.57-2
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your xorg driver package compatible with xserver 1.19 (i.e.
supporting xorg-video-abi-23).


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845640: Compatibility with xserver 1.19 / xorg-video-abi-23

[Andreas Boll]

Source: nvidia-graphics-drivers-legacy-340xx
Version: 340.98-1
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your xorg driver package compatible with xserver 1.19 (i.e.
supporting xorg-video-abi-23).


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845635: FTBFS with xserver 1.19

[Andreas Boll]

Source: virtualbox
Version: 5.1.10-dfsg-1
Severity: serious
Control: block 843265 by -1

Dear Maintainer,

your package is part of the ongoing xserver 1.19 transition #843265.
Please make your package compatible with xserver 1.19 (i.e. supporting
xorg-video-abi-23 and/or xorg-input-abi-24).

Build log: 
https://buildd.debian.org/status/fetch.php?pkg=virtualbox=amd64=5.1.10-dfsg-1%2Bb1=1480027319


Thanks,
Andreas


signature.asc
Description: Digital signature

Bug#845331: Reopen Bug#845331, xxv-omap still FTBFS against xserver 1.19 (Bug#845331: fixed in xf86-video-omap 0.4.4-2)

[Andreas Boll]

Control: reopen 845331

Unfortunately it wasn't enough to fix the build against xserver 1.19.
Apparently xxv-omap needs to be ported to the new NotifyFd API.

Build log: 
https://buildd.debian.org/status/fetch.php?pkg=xf86-video-omap=armhf=0.4.4-2=1479924520

Thanks,
Andreas

On Wed, Nov 23, 2016 at 05:24:09PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the xserver-xorg-video-omap package:
> 
> #845331: xserver-xorg-video-omap: Compatibility with xserver 1.19
> 
> It has been closed by Sebastian Reichel <s...@debian.org>.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Sebastian Reichel 
> <s...@debian.org> by
> replying to this email.
> 
> 
> -- 
> 845331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845331
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Wed, 23 Nov 2016 17:20:34 +
> From: Sebastian Reichel <s...@debian.org>
> To: 845331-cl...@bugs.debian.org
> Subject: Bug#845331: fixed in xf86-video-omap 0.4.4-2
> 
> Source: xf86-video-omap
> Source-Version: 0.4.4-2
> 
> We believe that the bug you reported is fixed in the latest version of
> xf86-video-omap, which is due to be installed in the Debian FTP archive.
> 
> A summary of the changes between this version and the previous one is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 845...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Sebastian Reichel <s...@debian.org> (supplier of updated xf86-video-omap 
> package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Wed, 23 Nov 2016 17:09:26 +0100
> Source: xf86-video-omap
> Binary: xserver-xorg-video-omap
> Architecture: source
> Version: 0.4.4-2
> Distribution: unstable
> Urgency: low
> Maintainer: Sebastian Reichel <s...@debian.org>
> Changed-By: Sebastian Reichel <s...@debian.org>
> Description:
>  xserver-xorg-video-omap - X.Org X server -- OMAP display driver
> Closes: 820321 845331
> Changes:
>  xf86-video-omap (0.4.4-2) unstable; urgency=low
>  .
>* Remove staging note from package description (Closes: #820321)
>* Update Debian Standards Version to 3.9.8
>* Add upstream patches for ABI 23 support (Closes: #845331)
>* Switch to compat level 10
>* Enable bindnow hardening
> Checksums-Sha1:
>  87db47be2adb8a456a9943a363e6f337e1fcf376 2117 xf86-video-omap_0.4.4-2.dsc
>  6ec7eb5627df1f0275f765033d276a478c3e7e27 3792 
> xf86-video-omap_0.4.4-2.debian.tar.xz
> Checksums-Sha256:
>  e631ffec3a132839a135baece7995fa038f132e3dff730e097eed6efd1aa7536 2117 
> xf86-video-omap_0.4.4-2.dsc
>  3f310b53d830370d7c5510553278009498e4a552cf73f242b762146cf2afad49 3792 
> xf86-video-omap_0.4.4-2.debian.tar.xz
> Files:
>  4a1c24281550667c823195711e1722fa 2117 x11 optional 
> xf86-video-omap_0.4.4-2.dsc
>  76aa9006c82c39cdcd4bd796a9d71de6 3792 x11 optional 
> xf86-video-omap_0.4.4-2.debian.tar.xz
> 
> -BEGIN PGP SIGNATURE-
> 
> iQJDBAEBCgAtFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAlg1yiEPHHNyZUBkZWJp
> YW4ub3JnAAoJENju1/PIO/qa/McP+wbAZspOjjXAgyaNCsbwx+WivGb5i/KnP1ug
> ArOCVHWMjQd8RwwyMR0S9e8ISCx4wdzPwyrFg63jel0NEKUm6hJMrNEDn8wJYtQQ
> cINNwQQWYc/GKcOLwpVnFDiu2UkE/aYPHjlWAr2Q8AJ1XCyK097SUnOT/1zKf/wr
> EfOgMKauEC/woj2JZ+1FJBsWw2Wfq2qTnx7YCTk/Fz7BjyU/r3wffAWzl7cCQG7F
> ikf26vbJRaUb2kGVZ9sOrjwOTdKaUIgSYmKl4Ec9oKFbPczvjwM9yxH4kZ/EALPN
> F1KXW72ClRlfMAK78AdDNRw+HU5IblxoSy3EHlc2MrxQ0HpMj2Hd0ORSPr84PCze
> RGuIKHeJV7oGymnyNBxh3CkU4ziJjPiVwwy6cbR5Y8uYbATJMqbE6BUsIK+ZU73t
> 2ViGMZ24XIoY9QT9r4uD8bno6BaBk8exZCSQRHqrt86tgDPIlsy/UuZBkfIqZJPV
> EFc38hU4B2HkIjRPQbmXncNmwS01/GuGvBZpQKNsgnQWXpDM1SvOuYQ3uZH0SB7Q
> XXV9f/+uEiJxnK5zP3aPAG1WozJOX8OzcI6LuemcFdYKxBs1il2kzkcdBMh+/jwq
> +Ovc07LkbVmapkWICwUrTxEmXFD2T7TMtAg11t0Bwwb2pvyeKny7c7iKkukgJzxx
> F3WFZKiu
> =3erl
> -END PGP SIGNATURE-

> Date: Tue, 22 Nov 2016 15:59:15 +0100
> From: Andreas Boll <andreas.boll@gmail.com>
> To: Debian Bug Tracking System <sub...@bugs.debian.org>
> Subject: xserver-xorg-video-omap: Compatibility with xserver 1.19
> User-Agent: Mutt/1.5.23 (2014-03-12)
> 
> Package: xserver-xorg-vide