xorg-server: Changes to 'ubuntu'
debian/changelog | 7 + debian/patches/os-make-sure-the-clientswritable-fd-set-is-initialized.diff | 63 ++ debian/patches/series | 1 3 files changed, 71 insertions(+) New commits: commit 90d42c38b455afbe55579612f7e59a151bcb465e Author: Timo Aaltonen Date: Tue Sep 8 10:30:46 2015 +0300 release to wily diff --git a/debian/changelog b/debian/changelog index 229ceff..2448815 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,9 +1,9 @@ -xorg-server (2:1.17.2-1ubuntu6) UNRELEASED; urgency=medium +xorg-server (2:1.17.2-1ubuntu6) wily; urgency=medium * os-make-sure-the-clientswritable-fd-set-is-initialized.diff: Fix crashers caused by newer xproto bumping XFD_SETSIZE. (LP: #1484380) - -- Timo Aaltonen Tue, 08 Sep 2015 10:16:29 +0300 + -- Timo Aaltonen Tue, 08 Sep 2015 10:30:31 +0300 xorg-server (2:1.17.2-1ubuntu5) wily; urgency=medium commit aef44943b6730c8f3800dbef6ff55b36657b5d5e Author: Timo Aaltonen Date: Tue Sep 8 10:30:22 2015 +0300 os-make-sure-the-clientswritable-fd-set-is-initialized.diff: Fix crashers caused by newer xproto bumping XFD_SETSIZE. (LP: #1484380) diff --git a/debian/changelog b/debian/changelog index fe8c4d1..229ceff 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +xorg-server (2:1.17.2-1ubuntu6) UNRELEASED; urgency=medium + + * os-make-sure-the-clientswritable-fd-set-is-initialized.diff: Fix +crashers caused by newer xproto bumping XFD_SETSIZE. (LP: #1484380) + + -- Timo Aaltonen Tue, 08 Sep 2015 10:16:29 +0300 + xorg-server (2:1.17.2-1ubuntu5) wily; urgency=medium * disable-rotation-transform-gpuscreens.patch: Revert back to disabling diff --git a/debian/patches/os-make-sure-the-clientswritable-fd-set-is-initialized.diff b/debian/patches/os-make-sure-the-clientswritable-fd-set-is-initialized.diff new file mode 100644 index 000..b3a7d2e --- /dev/null +++ b/debian/patches/os-make-sure-the-clientswritable-fd-set-is-initialized.diff @@ -0,0 +1,63 @@ +From 7cc7ffd25d5e50b54cb942d07d4cb160f20ff9c5 Mon Sep 17 00:00:00 2001 +From: Martin Peres +Date: Fri, 17 Jul 2015 17:21:26 +0300 +Subject: [PATCH] os: make sure the clientsWritable fd_set is initialized + before use + +In WaitForSomething(), the fd_set clientsWritable may be used unitialized when +the boolean AnyClientsWriteBlocked is set in the WakeupHandler(). This leads to +a crash in FlushAllOutput() after x11proto's commit +2c94cdb453bc641246cc8b9a876da9799bee1ce7. + +The problem did not manifest before because both the XFD_SIZE and the maximum +number of clients were set to 256. As the connectionTranslation table was +initalized for the 256 clients to 0, the test on the index not being 0 was +aborting before dereferencing the client #0. + +As of commit 2c94cdb453bc641246cc8b9a876da9799bee1ce7 in x11proto, the XFD_SIZE +got bumped to 512. This lead the OutputPending fd_set to have any fd above 256 +to be uninitialized which in turns lead to reading an index after the end of +the ConnectionTranslation table. This index would then be used to find the +client corresponding to the fd marked as pending writes and would also result +to an out-of-bound access which would usually be the fatal one. + +Fix this by zeroing the clientsWritable fd_set at the beginning of +WaitForSomething(). In this case, the bottom part of the loop, which would +indirectly call FlushAllOutput, will not do any work but the next call to +select will result in the execution of the right codepath. This is exactly what +we want because we need to know the writable clients before handling them. In +the end, it also makes sure that the fds above MaxClient are initialized, +preventing the crash in FlushAllOutput(). + +Thanks to everyone involved in tracking this one down! + +Reported-by: Karol Herbst +Reported-by: Tobias Klausmann +Signed-off-by: Martin Peres +Tested-by: Martin Peres +Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=91316 +Cc: Ilia Mirkin +Cc: Martin Peres +Cc: Olivier Fourdan +Cc: Alan Coopersmith +--- + os/WaitFor.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/os/WaitFor.c b/os/WaitFor.c +index 431f1a6..993c14e 100644 +--- a/os/WaitFor.c b/os/WaitFor.c +@@ -158,6 +158,7 @@ WaitForSomething(int *pClientsReady) + Bool someReady = FALSE; + + FD_ZERO(&clientsReadable); ++FD_ZERO(&clientsWritable); + + if (nready) + SmartScheduleStopTimer(); +-- +2.4.5 + diff --git a/debian/patches/series b/debian/patches/series index bbac1ac..e1f102b 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -51,3 +51,4 @@ xmir-rootless.patch xmir-desktop-file-hint-flag.patch drm_device_keep_trying.patch xi2-resize-touch.patch +os-make-sure-the-clientswritable-fd-set-is-initialized.diff
Re: [Pkg-opencl-devel] New libclc snapshot
On 2015-09-03 14:57, Timo Aaltonen wrote: > On 02.09.2015 20:35, Andreas Boll wrote: >> Hi all, >> >> for mesa-opencl-icd we need a newer libclc snapshot which is >> compatible with LLVM-3.7, since we are upgrading mesa from LLVM-3.5 to >> 3.7. >> I'm volunteering to prepare such a new snapshot. >> So here is my question: >> Do you have for libclc a git repository for collaboration? >> If not could you create one under the umbrella of pkg-opencl? > I've put an updated package to > > git://git.debian.org/git/users/tjaalton/libclc.git > > feel free to use it as a base for the official update, and/or for the > migration to git. I imported the package history into git and rebased Timo's and Andreas' changes on top of this, the repository is now available at git+ssh://git.debian.org/git/pkg-opencl/libclc.git git://anonscm.debian.org/pkg-opencl/libclc.git https://anonscm.debian.org/cgit/pkg-opencl/libclc.git and writable by the members of the pkg-opencl alioth project. Andreas
Bug#798317: xserver-xorg-video-radeon: Strange interaction of radeon config, screenshot and x11vnc
Dear Michel, > I don't know what the problem is, but FWIW you shouldn't enable Option > "RenderAccel", because RENDER acceleration uses the 3D engine, which > isn't validated on RN100 GPUs. That might explain at least the issue > with Option "EXAPixmaps" enabled. Thanks. I'll try later to disable RenderAccel and test enabling EXAPixmaps again. I must confess that I copied the configuration file from somewhere and, without much understanding, commented and uncommented lines until I the black screen problem was solved, but at the next boot it came back. Regards, Luis -- o W. Luis Mochán, | tel:(52)(777)329-1734 /<(*) Instituto de Ciencias Físicas, UNAM | fax:(52)(777)317-5388 `>/ /\ Apdo. Postal 48-3, 62251 | (*)/\/ \ Cuernavaca, Morelos, México | moc...@fis.unam.mx /\_/\__/ Consider using GnuPrivacyGuard https://www.gnupg.org/ My key: 791EB9EB, C949 3F81 6D9B 1191 9A16 C2DF 5F0A C52B 791E B9EB, yours?
pixman: Changes to 'debian-unstable'
.gitignore| 46
ChangeLog | 1955 +++
configure.ac |5
debian/changelog | 17
debian/control|9
debian/patches/ppc64el.diff | 14
debian/patches/series |1
debian/rules |5
pixman/Makefile.am|2
pixman/pixman-arm-asm.h | 37
pixman/pixman-arm-common.h| 11
pixman/pixman-arm-neon-asm-bilinear.S | 12
pixman/pixman-arm-neon-asm.S | 12
pixman/pixman-arm-neon-asm.h | 20
pixman/pixman-arm-neon.c | 24
pixman/pixman-arm-simd-asm-scaled.S | 11
pixman/pixman-arm-simd-asm.S | 525 ++
pixman/pixman-arm-simd-asm.h | 116 +
pixman/pixman-arm-simd.c | 44
pixman/pixman-combine-float.c | 338 ++--
pixman/pixman-combine32.c | 1686 +---
pixman/pixman-fast-path.c |2
pixman/pixman-general.c | 27
pixman/pixman-gradient-walker.c |2
pixman/pixman-inlines.h |3
pixman/pixman-mips-dspr2-asm.S|2
pixman/pixman-mips-dspr2-asm.h|4
pixman/pixman-mips-dspr2.c| 10
pixman/pixman-mips-dspr2.h|8
pixman/pixman-mmx.c | 109 +
pixman/pixman-private.h |6
pixman/pixman-sse2.c | 24
pixman/pixman-vmx.c | 1315 +++-
pixman/pixman.c | 18
test/Makefile.sources | 60
test/affine-bench.c | 436 +
test/blitters-test.c | 20
test/check-formats.c | 176 --
test/composite.c | 11
test/lowlevel-blt-bench.c | 507 +-
test/pixel-test.c | 2780 +-
test/radial-invalid.c | 54
test/solid-test.c | 353
test/thread-test.c| 29
test/tolerance-test.c | 360
test/utils.c | 653 ++-
test/utils.h | 13
47 files changed, 9417 insertions(+), 2455 deletions(-)
New commits:
commit 42fab57651e2ebdde5d260ae76809a2500086839
Author: Andreas Boll
Date: Fri Sep 4 13:40:42 2015 +0200
Bump standards version to 3.9.6.
diff --git a/debian/changelog b/debian/changelog
index 245fb5c..e73a52d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,6 +6,7 @@ pixman (0.33.2-1) UNRELEASED; urgency=medium
* Update Vcs-* fields.
* Add upstream url.
* Drop XC- prefix from Package-Type field.
+ * Bump standards version to 3.9.6.
[ intrigeri ]
* Simplify hardening build flags handling (closes: #760100).
diff --git a/debian/control b/debian/control
index c78d8b6..6188e41 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Build-Depends:
dh-autoreconf,
pkg-config,
quilt,
-Standards-Version: 3.9.2
+Standards-Version: 3.9.6
Vcs-Git: https://anonscm.debian.org/git/pkg-xorg/lib/pixman.git
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-xorg/lib/pixman.git
Homepage: http://pixman.org/
commit 56432ef5e5a38ddd77e23d10e1e8f724afcbedd8
Author: Andreas Boll
Date: Fri Sep 4 13:38:49 2015 +0200
Drop XC- prefix from Package-Type field.
diff --git a/debian/changelog b/debian/changelog
index e6627d6..245fb5c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,6 +5,7 @@ pixman (0.33.2-1) UNRELEASED; urgency=medium
* Enable vmx on ppc64el (closes: #786345).
* Update Vcs-* fields.
* Add upstream url.
+ * Drop XC- prefix from Package-Type field.
[ intrigeri ]
* Simplify hardening build flags handling (closes: #760100).
diff --git a/debian/control b/debian/control
index 03277a6..c78d8b6 100644
--- a/debian/control
+++ b/debian/control
@@ -28,7 +28,7 @@ Description: pixel-manipulation library for X and cairo
Package: libpixman-1-0-udeb
Section: debian-installer
-XC-Package-Type: udeb
+Package-Type: udeb
Architecture: any
Depends:
${shlibs:Depends},
commit c0f98e1cf4fa897eb67a3ef737b24deacda5ae7e
Author: Andreas Boll
Date: Fri Sep 4 11:47:45 2015 +0200
Add upstream url.
diff --git a/debian/changelog b/debian/changelog
index 05d7550..e6627d6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,7 @@ pixman (0.33.2-1) UNRELEASED; urgency=medium
* New upstream release candidate.
* Enable vmx on ppc64el (closes: #786345).
* Update Vcs-* fields.
+ * Add upstream url.
[ intrigeri ]
* Simplify hardening build flags handling (closes: #760100).
diff --git a/debian/control b/debian/control
index a56b239..03277a6 100644
--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Build-Depends:
Standards-Version: 3.9.2
Vcs-Git: http
pixman: Changes to 'upstream-unstable'
Rebased ref, commits from common ancestor:
commit ee790044b08e3b668e6aa5d9229f46ed7295ebf0
Author: Oded Gabbay
Date: Sat Aug 1 22:34:53 2015 +0300
Pre-release version bump to 0.33.2
Signed-off-by: Oded Gabbay
diff --git a/configure.ac b/configure.ac
index 0339494..554b6d2 100644
--- a/configure.ac
+++ b/configure.ac
@@ -54,7 +54,7 @@ AC_PREREQ([2.57])
m4_define([pixman_major], 0)
m4_define([pixman_minor], 33)
-m4_define([pixman_micro], 1)
+m4_define([pixman_micro], 2)
m4_define([pixman_version],[pixman_major.pixman_minor.pixman_micro])
commit 8d9be3619a906855a3e3a1e052317833cb24cabe
Author: Oded Gabbay
Date: Wed Jul 1 14:34:07 2015 +0300
vmx: implement fast path iterator vmx_fetch_a8
no changes were observed when running cairo trimmed benchmarks.
Running "lowlevel-blt-bench src_8_" on POWER8, 8 cores,
3.4GHz, RHEL 7.1 ppc64le gave the following results:
reference memcpy speed = 25197.2MB/s (6299.3MP/s for 32bpp fills)
Before After Change
L1 965.34 3936 +307.73%
L2 942.99 3436.29+264.40%
M 902.24 2757.77+205.66%
HT 448.46 784.99 +75.04%
VT 430.05 819.78 +90.62%
R 412.9 717.04 +73.66%
RT 168.93 220.63 +30.60%
Kops/s 10251303 +27.12%
It was benchmarked against commid id e2d211a from pixman/master
Siarhei Siamashka reported that on playstation3, it shows the following
results:
== before ==
src_8_ = L1: 194.37 L2: 198.46 M:155.90 (148.35%)
HT: 59.18 VT: 36.71 R: 38.93 RT: 12.79 ( 106Kops/s)
== after ==
src_8_ = L1: 373.96 L2: 391.10 M:245.81 (233.88%)
HT: 80.81 VT: 44.33 R: 48.10 RT: 14.79 ( 122Kops/s)
Signed-off-by: Oded Gabbay
Acked-by: Siarhei Siamashka
diff --git a/pixman/pixman-vmx.c b/pixman/pixman-vmx.c
index 773ad76..a9bd024 100644
--- a/pixman/pixman-vmx.c
+++ b/pixman/pixman-vmx.c
@@ -3139,6 +3139,49 @@ vmx_fetch_x8r8g8b8 (pixman_iter_t *iter, const uint32_t
*mask)
return iter->buffer;
}
+static uint32_t *
+vmx_fetch_a8 (pixman_iter_t *iter, const uint32_t *mask)
+{
+int w = iter->width;
+uint32_t *dst = iter->buffer;
+uint8_t *src = iter->bits;
+vector unsigned int vmx0, vmx1, vmx2, vmx3, vmx4, vmx5, vmx6;
+
+iter->bits += iter->stride;
+
+while (w && (((uintptr_t)dst) & 15))
+{
+*dst++ = *(src++) << 24;
+w--;
+}
+
+while (w >= 16)
+{
+ vmx0 = load_128_unaligned((uint32_t *) src);
+
+ unpack_128_2x128((vector unsigned int) AVV(0), vmx0, &vmx1, &vmx2);
+ unpack_128_2x128_16((vector unsigned int) AVV(0), vmx1, &vmx3, &vmx4);
+ unpack_128_2x128_16((vector unsigned int) AVV(0), vmx2, &vmx5, &vmx6);
+
+ save_128_aligned(dst, vmx6);
+ save_128_aligned((dst + 4), vmx5);
+ save_128_aligned((dst + 8), vmx4);
+ save_128_aligned((dst + 12), vmx3);
+
+ dst += 16;
+ src += 16;
+ w -= 16;
+}
+
+while (w)
+{
+ *dst++ = *(src++) << 24;
+ w--;
+}
+
+return iter->buffer;
+}
+
#define IMAGE_FLAGS\
(FAST_PATH_STANDARD_FLAGS | FAST_PATH_ID_TRANSFORM | \
FAST_PATH_BITS_IMAGE | FAST_PATH_SAMPLES_COVER_CLIP_NEAREST)
@@ -3148,6 +3191,9 @@ static const pixman_iter_info_t vmx_iters[] =
{ PIXMAN_x8r8g8b8, IMAGE_FLAGS, ITER_NARROW,
_pixman_iter_init_bits_stride, vmx_fetch_x8r8g8b8, NULL
},
+{ PIXMAN_a8, IMAGE_FLAGS, ITER_NARROW,
+ _pixman_iter_init_bits_stride, vmx_fetch_a8, NULL
+},
{ PIXMAN_null },
};
commit 47f74ca94637d79ee66c37a81eea0200e453fcc1
Author: Oded Gabbay
Date: Mon Jun 29 15:31:02 2015 +0300
vmx: implement fast path iterator vmx_fetch_x8r8g8b8
It was benchmarked against commid id 2be523b from pixman/master
POWER8, 8 cores, 3.4GHz, RHEL 7.1 ppc64le.
cairo trimmed benchmarks :
Speedups
t-firefox-asteroids 533.92 -> 489.94 : 1.09x
Signed-off-by: Oded Gabbay
Acked-by: Siarhei Siamashka
diff --git a/pixman/pixman-vmx.c b/pixman/pixman-vmx.c
index 0950850..773ad76 100644
--- a/pixman/pixman-vmx.c
+++ b/pixman/pixman-vmx.c
@@ -3105,6 +3105,52 @@ static const pixman_fast_path_t vmx_fast_paths[] =
{ PIXMAN_OP_NONE },
};
+static uint32_t *
+vmx_fetch_x8r8g8b8 (pixman_iter_t *iter, const uint32_t *mask)
+{
+int w = iter->width;
+vector unsigned int ff00 = mask_ff00;
+uint32_t *dst = iter->buffer;
+uint32_t *src = (uint32_t *)iter->bi
Processed: tagging 797661, user debian...@lists.debian.org, usertagging 797661, found 769146 in 1:5.7p3-1 ...
Processing commands for cont...@bugs.debian.org:
> tags 797661 + pending
Bug #797661 [xserver-xorg-core] Fails to upgrade, file conflict with x11-common
Added tag(s) pending.
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 797661 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 769146 1:5.7p3-1
Bug #769146 [openntpd] openntpd: fails to upgrade from 'sid' - trying to
overwrite /etc/apparmor.d/usr.sbin.ntpd
Marked as found in versions openntpd/1:5.7p3-1.
> found 769146 1:5.7p4-1
Bug #769146 [openntpd] openntpd: fails to upgrade from 'sid' - trying to
overwrite /etc/apparmor.d/usr.sbin.ntpd
Marked as found in versions openntpd/1:5.7p4-1.
> affects 798353 - libsndio-dev
Bug #798353 [libsndio-dev] libsndio-dev and libroar-dev: error when trying to
install together
Removed indication that 798353 affects libsndio-dev
> found 798344 1.2.6p7-1
Bug #798344 [check-mk-multisite] Expects /etc/check_mk/conf.d directory
Marked as found in versions check-mk/1.2.6p7-1.
> severity 798344 serious
Bug #798344 [check-mk-multisite] Expects /etc/check_mk/conf.d directory
Severity set to 'serious' from 'important'
> usertags 798344 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 782098 2.2.0-2
Bug #782098 {Done: Mathieu Malaterre }
[openexr,libopenexr-dev] openexr, libopenexr-dev: directory vs. symlink
conflict: /usr/share/doc/{openexr, libopenexr-dev} -> /usr/share/doc/libopenexr6
Marked as found in versions openexr/2.2.0-2; no longer marked as fixed in
versions openexr/2.2.0-2 and reopened.
> usertags 796864 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 796864 + libmodglue1-dev
Bug #796864 [libmodglue1v5] libmodglue1v5 and libmodglue1: error when trying to
install together
Added indication that 796864 affects libmodglue1-dev
> usertags 797825 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 797825 + relion-bin+gui relion-bin+mpi relion-bin+mpi+gui
Bug #797825 [librelion-1.3-1] file conflicts between
librelion{+mpi}{+gui}-1.3-1{v5} packages
Added indication that 797825 affects relion-bin+gui, relion-bin+mpi, and
relion-bin+mpi+gui
> found 798374 usrmerge/2
Bug #798374 [piuparts] usrmerge: cannot be tested with piuparts
Marked as found in versions usrmerge/2.
> found 769766 0.13
Bug #769766 [debci] debci: unowned files after purge (policy 6.8, 10.8):
/var/lib/debci/*
Marked as found in versions debci/0.13.
> found 793679 0.12.0-1
Bug #793679 [sddm] sddm: unowned files after purge (policy 6.8, 10.8):
/var/log/sddm.log
Marked as found in versions sddm/0.12.0-1.
> found 775385 1.14.2-2
Bug #775385 [lightdm] lightdm: unowned symlink after purge (policy 6.8, 10.8):
/etc/systemd/system/display-manager.service
Marked as found in versions lightdm/1.14.2-2.
> found 789917 gfortran-triplet/5.2.1-14+really5.2.1-13cross1
Bug #789917
[gfortran-aarch64-linux-gnu,gfortran-arm-linux-gnueabi,gfortran-arm-linux-gnueabihf,gfortran-mips-linux-gnu,gfortran-mipsel-linux-gnu,gfortran-powerpc-linux-gnu]
gfortran-: leaves alternatives after purge: /usr/bin/-f{77,
95}
The source gfortran-triplet and version 5.2.1-14+really5.2.1-13cross1 do not
appear to match any binary packages
Marked as found in versions gfortran-triplet/5.2.1-14+really5.2.1-13cross1.
> found 682739 matlab-support/0.0.21
Bug #682739 [piuparts-master] pre_test_* custom script should signal
"untestable, don't try" via exit code
Marked as found in versions matlab-support/0.0.21.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
682739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682739
769146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769146
769766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769766
775385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775385
782098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782098
789917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789917
793679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793679
796864: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796864
797661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797661
797825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797825
798344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798344
798353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798353
798374: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#798317: xserver-xorg-video-radeon: Strange interaction of radeon config, screenshot and x11vnc
I turned off RenderAccel, turned on EXAPixmaps and rebooted. Everything seems to work fine now; I got into X and screenshot captures correctly the screen images and x11vnc displays the screen correctly. Thanks, Luis On Tue, Sep 08, 2015 at 08:47:55AM -0500, Luis Mochan wrote: > Dear Michel, > > I don't know what the problem is, but FWIW you shouldn't enable Option > > "RenderAccel", because RENDER acceleration uses the 3D engine, which > > isn't validated on RN100 GPUs. That might explain at least the issue > > with Option "EXAPixmaps" enabled. > Thanks. I'll try later to disable RenderAccel and test enabling > EXAPixmaps again. I must confess that I copied the configuration > file from somewhere and, without much understanding, commented and > uncommented lines until I the black screen problem was solved, but at > the next boot it came back. > Regards, > Luis > > -- > > o > W. Luis Mochán, | tel:(52)(777)329-1734 /<(*) > Instituto de Ciencias Físicas, UNAM | fax:(52)(777)317-5388 `>/ /\ > Apdo. Postal 48-3, 62251 | (*)/\/ \ > Cuernavaca, Morelos, México | moc...@fis.unam.mx /\_/\__/ > Consider using GnuPrivacyGuard https://www.gnupg.org/ > My key: 791EB9EB, C949 3F81 6D9B 1191 9A16 C2DF 5F0A C52B 791E B9EB, yours? > > > -- o W. Luis Mochán, | tel:(52)(777)329-1734 /<(*) Instituto de Ciencias Físicas, UNAM | fax:(52)(777)317-5388 `>/ /\ Apdo. Postal 48-3, 62251 | (*)/\/ \ Cuernavaca, Morelos, México | moc...@fis.unam.mx /\_/\__/ GPG: 791EB9EB, C949 3F81 6D9B 1191 9A16 C2DF 5F0A C52B 791E B9EB
Re: Processed: tagging 797661, user debian...@lists.debian.org, usertagging 797661, found 769146 in 1:5.7p3-1 ...
Hi Andreas, On Tue, Sep 8, 2015 at 15:06:20 +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > tags 797661 + pending > Bug #797661 [xserver-xorg-core] Fails to upgrade, file conflict with > x11-common > Added tag(s) pending. > > user debian...@lists.debian.org > Setting user to debian...@lists.debian.org (was a...@debian.org). > > usertags 797661 piuparts > There were no usertags set. > Usertags are now: piuparts. > > found 769146 1:5.7p3-1 [snip lots of unrelated other bugs] This is really annoying, could you please not alter unrelated bugs in the same control message? Thanks, Julien signature.asc Description: Digital signature
Bug#798408: [arm] libgles2-mesa-dev and libglew-dev disagree over GLsizeiptr
Package: libgles2-mesa-dev, libglew-dev Version: 10.5.7-1, 1.10.0-3 Severity: important The 2 buildd attempts of tulip 4.7.0 on armel and armhf both failed, starting with the following type conflicts, and openscad hits a similar problem. https://bugs.debian.org/793137 https://bugs.debian.org/797816 libglew-dev and libgles2-mesa-dev were the same in both builds (I'm puzzled that arnold does not use an uptodate mesa versions, BTW) In file included from /usr/include/arm-linux-gnueabi/qt5/QtGui/qopengl.h:97:0, from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/qgl.h:39, from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/qglframebufferobject.h:37, from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/QGLFramebufferObject:1, from /«PKGBUILDDIR»/library/tulip-gui/src/GlOffscreenRenderer.cpp:26: /usr/include/GLES3/gl3.h:69:25: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr' typedef khronos_ssize_t GLsizeiptr; ^ In file included from /«PKGBUILDDIR»/library/tulip-gui/src/GlOffscreenRenderer.cpp:24:0: /usr/include/GL/glew.h:1663:19: note: previous declaration as 'typedef ptrdiff_t GLsizeiptr' typedef ptrdiff_t GLsizeiptr; ^ In file included from /usr/include/arm-linux-gnueabi/qt5/QtGui/qopengl.h:97:0, from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/qgl.h:39, from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/qglframebufferobject.h:37, from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/QGLFramebufferObject:1, from /«PKGBUILDDIR»/library/tulip-gui/src/GlOffscreenRenderer.cpp:26: /usr/include/GLES3/gl3.h:70:26: error: conflicting declaration 'typedef khronos_intptr_t GLintptr' typedef khronos_intptr_t GLintptr; ^ In file included from /«PKGBUILDDIR»/library/tulip-gui/src/GlOffscreenRenderer.cpp:24:0: /usr/include/GL/glew.h:1662:19: note: previous declaration as 'typedef ptrdiff_t GLintptr' typedef ptrdiff_t GLintptr; ^
Processed: affects 798408, affects 798408
Processing commands for cont...@bugs.debian.org: > affects 798408 793137 Bug #798408 [libgles2-mesa-dev, libglew-dev] [arm] libgles2-mesa-dev and libglew-dev disagree over GLsizeiptr Added indication that 798408 affects 793137 > affects 798408 797816 Bug #798408 [libgles2-mesa-dev, libglew-dev] [arm] libgles2-mesa-dev and libglew-dev disagree over GLsizeiptr Added indication that 798408 affects 797816 > thanks Stopping processing here. Please contact me if you need assistance. -- 798408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#798408: [arm] libgles2-mesa-dev and libglew-dev disagree over GLsizeiptr
On Tue, Sep 8, 2015 at 23:11:53 +0200, Yann Dirson wrote: > Package: libgles2-mesa-dev, libglew-dev > Version: 10.5.7-1, 1.10.0-3 > Severity: important > > The 2 buildd attempts of tulip 4.7.0 on armel and armhf both failed, > starting with the following type conflicts, and openscad hits a > similar problem. > > https://bugs.debian.org/793137 > https://bugs.debian.org/797816 > > libglew-dev and libgles2-mesa-dev were the same in both builds (I'm > puzzled that arnold does not use an uptodate mesa versions, BTW) > I'm not sure that's our bug. You probably shouldn't be mixing GLES and desktop GL that way... Cheers, Julien signature.asc Description: Digital signature
Bug#798408: [arm] libgles2-mesa-dev and libglew-dev disagree over GLsizeiptr
On Tue, Sep 08, 2015 at 11:44:21PM +0200, Julien Cristau wrote: > On Tue, Sep 8, 2015 at 23:11:53 +0200, Yann Dirson wrote: > > > Package: libgles2-mesa-dev, libglew-dev > > Version: 10.5.7-1, 1.10.0-3 > > Severity: important > > > > The 2 buildd attempts of tulip 4.7.0 on armel and armhf both failed, > > starting with the following type conflicts, and openscad hits a > > similar problem. > > > > https://bugs.debian.org/793137 > > https://bugs.debian.org/797816 > > > > libglew-dev and libgles2-mesa-dev were the same in both builds (I'm > > puzzled that arnold does not use an uptodate mesa versions, BTW) > > > I'm not sure that's our bug. You probably shouldn't be mixing GLES and > desktop GL that way... Hm, how that you mention it: GlOffscreenRenderer only tries to mix QtOpenGL and GLew, it is *qt5/QtGui/qopengl.h* including GLES. With all those #ifdef's, it's hard to tell at first sight if qt5opengl on other archs is doing the same, but https://packages.debian.org/sid/libqt5gui5 shows that arm* are the only archs where q5 links to GLES, while it's linking to libgl1 on all other archs. No info about this in changelog.Debian, and no README.Debian either for libqt5gui5. Is that in fact a bug in qtbase-opensource-src ?
Bug#698989: libgl1-mesa-dri: glxinfo segmentation fault in nouveau_vieux_dri.so
Package: libgl1-mesa-dri Version: 10.6.3-1 Followup-For: Bug #698989 Dear Maintainer, I have the same or very similar problem with the 10.6.3-1 version of libgl1 -mesa-dri. I always get a segmentation fault when running glxgears or glxinfo. Running glxinfo leaves the following in syslog: Sep 8 17:13:02 kitchencomp kernel: [ 4094.174665] glxinfo [19742]: segfault at f0 ip b69900c5 sp bfb5ddec error 4 in nouveau_vieux_dri.so[b680+652000] Sep 8 17:13:25 kitchencomp kernel: [ 4116.827296] glxinfo[19859]: segfault at f0 ip b69250c5 sp bfbaa41c error 4 in nouveau_vieux_dri.so[b6795000+652000] I recently reinstalled xserver-xorg-core:i386 (1.17.2-1.1), xserver-xorg-video- nouveau:i386 (1.0.11-1+b1), libdrm-nouveau2:i386 (2.4.64-1), libgl1-mesa- dri:i386 (10.6.3-1), and libgl1-mesa-glx:i386 (10.6.3-1) to see whether that would fix the problem, but it didn't. I had direct rendering working with the nouveau driver when the nvidia proprietary driver for this card first became incompatible with xorg. I don't know which upgrade resulted in the loss of direct rendering. I'm submitting this report with data compiled while running the 3.16.0-4-686-pae kernel, but I have the same problem when running the 4.1.0-1-686-pae kernel as well as an earlier non-pae kernel. --John Harrington -- Package-specific info: glxinfo: X server symlink status: lrwxrwxrwx 1 root root 13 Aug 27 2012 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2539480 Aug 11 06:09 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV18 [GeForce4 MX 4000] [10de:0185] (rev c1) Xorg X server configuration file status: -rw-r--r-- 1 root root 5017 Aug 13 14:27 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: --- Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 Screen 1 "Screen1" RightOf "Screen0" Screen 2 "Screen2" RightOf "Screen1" InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" FontPath "built-ins" EndSection Section "Module" Load"glx" # Load"dri" Load "extmod" Load "dbe" Load "dri2" Load "record" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Monitor" Identifier "Monitor1" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Monitor" Identifier "Monitor2" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz", ### : "%" ### [arg]: arg optional #Option "SWcursor" # [] #Option "HWcursor" # [] #Option "NoAccel" # [] #Option "ShadowFB" # [] #Option "VideoKey" # #Option "WrappedFB" # [] #Option "GLXVBlank" # [] #Option "ZaphodHeads" # #Option "PageFlip" # [] #Option "SwapLimit" # #Option "AsyncUTSDFS" # [] Identifier "Device0" Driver "nouveau" BusID "PCI:1:0:0" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz", ### : "%" ### [arg]: arg optional #Option "ShadowFB" # [] #Option "Rotate"# #Option "fbdev" # #Option "debug" # [] Identifier "Device1"
Bug#798317: xserver-xorg-video-radeon: Strange interaction of radeon config, screenshot and x11vnc
On 09.09.2015 01:35, Luis Mochan wrote: > I turned off RenderAccel, turned on EXAPixmaps and > rebooted. Everything seems to work fine now; I got into X and > screenshot captures correctly the screen images and x11vnc displays > the screen correctly. Is there still a problem without Option "EXAPixmaps"? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
Bug#798317: xserver-xorg-video-radeon: Strange interaction of radeon config, screenshot and x11vnc
I haven´t rebooted without that option, but it seems it runs faster without it (I turned it off and restarted X). Regards On September 8, 2015 9:34:20 PM CDT, "Michel Dänzer" wrote: >On 09.09.2015 01:35, Luis Mochan wrote: >> I turned off RenderAccel, turned on EXAPixmaps and >> rebooted. Everything seems to work fine now; I got into X and >> screenshot captures correctly the screen images and x11vnc displays >> the screen correctly. > >Is there still a problem without Option "EXAPixmaps"? -- W. Luis Mochán desde su inservible teléfono
Bug#798317: xserver-xorg-video-radeon: Strange interaction of radeon config, screenshot and x11vnc
On 09.09.2015 11:46, Luis Mochan wrote: > I haven´t rebooted without that option, but it seems it runs faster without > it (I turned it off and restarted X). The EXAPixmaps option was specifically introduced to be disabled on GPUs like yours for this reason. :) -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
