Bug#639922: libgl1-mesa-dri-experimental: When using nouveau gl driver it renders black window in 3d

[Mathieu Malaterre]

On Thu, Apr 21, 2016 at 7:42 AM, Vladimir Berezenko  wrote:
> В письме от 13 апреля 2016 08:14:48 пользователь Mathieu Malaterre написал:
>> On Wed, Apr 13, 2016 at 6:16 AM, Vladimir Berezenko 
> wrote:
>> > В письме от 12 апреля 2016 08:57:23 пользователь Mathieu Malaterre
> написал:
>> >> Is the bug still accurate with newer version ?
>> >
>> > Seems not. When using recompiled kernel with 4k pages 3d seems working
>> > except weird colors in KDE5 plasma and constant segfaulting plasmashell
>> > when mouse cursor comes over popup notification,
>>
>> Hum. I am not confident what I should report upstream at:
>> https://bugs.freedesktop.org/show_bug.cgi?id=###
>>
>> Do you have some kind of backtrace ? Is this within mesa ? within nouveau ?
>>
>> I'd like to report that issue upstream.
>
> I've got a gdb output:
> (gdb) bt
> #0  0x0f5901b0 in QQuickItemPrivate::itemToParentTransform(QTransform&) const
> () from /usr/lib/powerpc-linux-gnu/libQt5Quick.so.5
> #1  0x0f59046c in QQuickItemPrivate::itemToWindowTransform() const () from
> /usr/lib/powerpc-linux-gnu/libQt5Quick.so.5
> #2  0x0f590460 in QQuickItemPrivate::itemToWindowTransform() const () from
> /usr/lib/powerpc-linux-gnu/libQt5Quick.so.5
> #3  0x0f5952cc in QQuickItem::mapToScene(QPointF const&) const () from
> /usr/lib/powerpc-linux-gnu/libQt5Quick.so.5
> #4  0x0ff6bde4 in ?? () from /usr/lib/powerpc-linux-gnu/libKF5PlasmaQuick.so.5
> #5  0x0ff71d14 in PlasmaQuick::Dialog::event(QEvent*) () from 
> /usr/lib/powerpc-
> linux-gnu/libKF5PlasmaQuick.so.5
> #6  0x0e34da88 in QApplicationPrivate::notify_helper
> (this=this@entry=0x100c2100, receiver=receiver@entry=0x10de04f8,
> e=e@entry=0xff7ffdc8) at kernel/qapplication.cpp:3716
> #7  0x0e354204 in QApplication::notify (this=0xde38, receiver=0x10de04f8,
> e=0xff7ffdc8) at kernel/qapplication.cpp:3499
> #8  0x0d8b5c74 in QCoreApplication::notifyInternal (this=0xde38,
> receiver=0x10de04f8, event=0xff7ffdc8) at kernel/qcoreapplication.cpp:965
> #9  0x0ff71e24 in PlasmaQuick::Dialog::event(QEvent*) () from 
> /usr/lib/powerpc-
> linux-gnu/libKF5PlasmaQuick.so.5
> #10 0x0e34da88 in QApplicationPrivate::notify_helper
> (this=this@entry=0x100c2100, receiver=receiver@entry=0x10de04f8,
> e=e@entry=0xff800588) at kernel/qapplication.cpp:3716
> #11 0x0e354204 in QApplication::notify (this=0xde38, receiver=0x10de04f8,
> e=0xff800588) at kernel/qapplication.cpp:3499
> #12 0x0d8b5c74 in QCoreApplication::notifyInternal (this=0xde38,
> receiver=0x10de04f8, event=0xff800588) at kernel/qcoreapplication.cpp:965
> #13 0x0ff71e24 in PlasmaQuick::Dialog::event(QEvent*) () from 
> /usr/lib/powerpc-
> linux-gnu/libKF5PlasmaQuick.so.5
> #14 0x0e34da88 in QApplicationPrivate::notify_helper
> (this=this@entry=0x100c2100, receiver=receiver@entry=0x10de04f8,
> e=e@entry=0xff800d48) at kernel/qapplication.cpp:3716
> #15 0x0e354204 in QApplication::notify (this=0xde38, receiver=0x10de04f8,
> e=0xff800d48) at kernel/qapplication.cpp:3499
> #16 0x0d8b5c74 in QCoreApplication::notifyInternal (this=0xde38,
> receiver=0x10de04f8, event=0xff800d48) at kernel/qcoreapplication.cpp:965
> #17 0x0ff71e24 in PlasmaQuick::Dialog::event(QEvent*) () from 
> /usr/lib/powerpc-
> linux-gnu/libKF5PlasmaQuick.so.5
> #18 0x0e34da88 in QApplicationPrivate::notify_helper
> (this=this@entry=0x100c2100, receiver=receiver@entry=0x10de04f8,
> e=e@entry=0xff801508) at kernel/qapplication.cpp:3716
> #19 0x0e354204 in QApplication::notify (this=0xde38, receiver=0x10de04f8,
> e=0xff801508) at kernel/qapplication.cpp:3499
> #20 0x0d8b5c74 in QCoreApplication::notifyInternal (this=0xde38,
> receiver=0x10de04f8, event=0xff801508) at kernel/qcoreapplication.cpp:965
> #21 0x0ff71e24 in PlasmaQuick::Dialog::event(QEvent*) () from 
> /usr/lib/powerpc-
> linux-gnu/libKF5PlasmaQuick.so.5
> #22 0x0e34da88 in QApplicationPrivate::notify_helper
> (this=this@entry=0x100c2100, receiver=receiver@entry=0x10de04f8,
> e=e@entry=0xff801cc8) at kernel/qapplication.cpp:3716
> #23 0x0e354204 in QApplication::notify (this=0xde38, receiver=0x10de04f8,
> e=0xff801cc8) at kernel/qapplication.cpp:3499
> #24 0x0d8b5c74 in QCoreApplication::notifyInternal (this=0xde38,
> receiver=0x10de04f8, event=0xff801cc8) at kernel/qcoreapplication.cpp:965
> #25 0x0ff71e24 in PlasmaQuick::Dialog::event(QEvent*) () from 
> /usr/lib/powerpc-
> linux-gnu/libKF5PlasmaQuick.so.5
> #26 0x0e34da88 in QApplicationPrivate::notify_helper
> (this=this@entry=0x100c2100, receiver=receiver@entry=0x10de04f8,
> e=e@entry=0xff802488) at kernel/qapplication.cpp:3716
> #27 0x0e354204 in QApplication::notify (this=0xde38, receiver=0x10de04f8,
> e=0xff802488) at kernel/qapplication.cpp:3499
> #28 0x0d8b5c74 in QCoreApplication::notifyInternal (this=0xde38,
> receiver=0x10de04f8, event=0xff802488) at kernel/qcoreapplication.cpp:965
> #29 0x0ff71e24 in PlasmaQuick::Dialog::event(QEvent*) () from 
> /usr/lib/powerpc-
> 

Processed: severity of 821954 is wishlist ...

[Debian Bug Tracking System]

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

> severity 821954 wishlist
Bug #821954 [libdrm] libdrm: diff for NMU version 2.4.67-1.1
Severity set to 'wishlist' from 'normal'
> retitle 821954 libdrm: Patch to _just_ compile on hurd (no functionality 
> implied) , close it
Bug #821954 [libdrm] libdrm: diff for NMU version 2.4.67-1.1
Changed Bug title to 'libdrm: Patch to _just_ compile on hurd (no functionality 
implied) , close it' from 'libdrm: diff for NMU version 2.4.67-1.1'.
> thanks
Stopping processing here.

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

Bug#821954: libdrm: diff for NMU version 2.4.67-1.1

[Tobias Frost]

On Wed, 20 Apr 2016 22:09:58 +0200 Julien Cristau 
wrote:
> On Wed, Apr 20, 2016 at 21:31:51 +0200, Tobias Frost wrote:
> 
> > Package: libdrm
> > Version: 2.4.67-1
> > Severity: normal
> > Tags: patch pending
> > 

> Also, when did hurd grow DRM support?  It doesn't make sense to build
> libdrm without that...

Then it probably makes sense to declare the Architectures: in d/control
appropriately, doesn't it? 

NMU canceled.

wayland_1.10.0-2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 20 Apr 2016 21:38:58 +0200
Source: wayland
Binary: libwayland-client0 libwayland-server0 libwayland-cursor0 libwayland-dev 
libwayland-doc
Architecture: source
Version: 1.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Emilio Pozuelo Monfort 
Description:
 libwayland-client0 - wayland compositor infrastructure - client library
 libwayland-cursor0 - wayland compositor infrastructure - cursor library
 libwayland-dev - wayland compositor infrastructure - development files
 libwayland-doc - wayland compositor infrastructure - documentation files
 libwayland-server0 - wayland compositor infrastructure - server library
Closes: 821170
Changes:
 wayland (1.10.0-2) unstable; urgency=medium
 .
   * Don't build the documentation on binary-arch only builds. Move the
 build-dependencies needed for the documentation to build-depends-indep.
 Closes: #821170.
   * Move the manpages to libwayland-doc.
   * Switch to dbgsym packages.
Checksums-Sha1:
 7df232fce29b6d09cdb43cd5346717c092805961 2324 wayland_1.10.0-2.dsc
 44fce70fdec5d2a1095b32e5cb8d2b778734823b 7963 wayland_1.10.0-2.diff.gz
Checksums-Sha256:
 286235130a577dda45254d7ea5a3cde4a9fa193fb444669bcca6b2e069b88473 2324 
wayland_1.10.0-2.dsc
 a17c105e27250fbe440585eb8584d8fd2da2a1080602877d9f9fa747f060d312 7963 
wayland_1.10.0-2.diff.gz
Files:
 4fb7b14300da64a801cf0606ad76d361 2324 x11 optional wayland_1.10.0-2.dsc
 610fc5d7d43548b31ee7026dc1f70b0c 7963 x11 optional wayland_1.10.0-2.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXF91kAAoJEJ1GxIjkNoMCz5UQAMekwJ9rTOVyFfvlke7/sssR
xqnPZL84iBeXqw0TmlIFkN7cOyepOVOE8Vf9DgeOc+5iMUVY8DKQh4j/IQYYL65m
5fe/MMmy2ziSyEO8ew63SXWBrD8uATgfXu40vQjWwrb4LKBuCQtsxqxo+1S2umi1
20ocnKHZ/CM/rBVWxL2GNpSFU2RbrjaSjZY7mRXTS39lC4YN6ORc4OGqDVO1/iXP
gfQ2OQq8yOgo0pI2BQ/GObJ5PZ84uMjnKeCJjFAEi06QVh8SyWl6YardXfR2VqBV
CkkosB6TflrxITGqbid6NtaRwiZuIu2CU98OGg04Z9WuSXTz/VUvChttNXKvuUcT
iGAtrTMNAaNBGgc2M8CyE724bTyvfUBPfuGOgYvAWTTjCGZTKG31qLXapdAPyBcC
4R6VyeASq5i5y43+nrJ7++iScUSE3aFvymKeNjbOnQjuTR9gmgsh9b1ot11RSw1j
4CnTPkWt4Ie2bCY7I5kooVi7OKKukbfr9QpfK+JTfxki3DXF6Ag4YCFUde9tGOyM
CJ4Ti+gPkEXSW46TbFilgBcrH2ivAx2yGZnUWfqmIGfhwQ+RCT7H31MKOHN/s9/v
oIFKq08UQpasdmKRPjcWa5LM2QlNSAZ1gaJgwrIzQxIbakFJ5fIfIwqKFfj8Fo0w
D3MtWElWgpq1R2bDjRZO
=s8EX
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#821170: marked as done (wayland: Please try to move doxygen to Build-Depends-Indep)

[Debian Bug Tracking System]

Your message dated Wed, 20 Apr 2016 22:32:02 +
with message-id 
and subject line Bug#821170: fixed in wayland 1.10.0-2
has caused the Debian Bug report #821170,
regarding wayland: Please try to move doxygen to Build-Depends-Indep
to be marked as done.

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

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


-- 
821170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wayland
Severity: wishlist

I saw that there is a circular B-Dloop involving wayland and doxygen on 
powerpcspe:

wayland -> doxygen -> qtbase5-dev -> libgbm-dev -> libgbm-dev -> libwayland-dev

Thanks for considering!

--
tobi

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: wayland
Source-Version: 1.10.0-2

We believe that the bug you reported is fixed in the latest version of
wayland, 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 821...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated wayland 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: Wed, 20 Apr 2016 21:38:58 +0200
Source: wayland
Binary: libwayland-client0 libwayland-server0 libwayland-cursor0 libwayland-dev 
libwayland-doc
Architecture: source
Version: 1.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Emilio Pozuelo Monfort 
Description:
 libwayland-client0 - wayland compositor infrastructure - client library
 libwayland-cursor0 - wayland compositor infrastructure - cursor library
 libwayland-dev - wayland compositor infrastructure - development files
 libwayland-doc - wayland compositor infrastructure - documentation files
 libwayland-server0 - wayland compositor infrastructure - server library
Closes: 821170
Changes:
 wayland (1.10.0-2) unstable; urgency=medium
 .
   * Don't build the documentation on binary-arch only builds. Move the
 build-dependencies needed for the documentation to build-depends-indep.
 Closes: #821170.
   * Move the manpages to libwayland-doc.
   * Switch to dbgsym packages.
Checksums-Sha1:
 7df232fce29b6d09cdb43cd5346717c092805961 2324 wayland_1.10.0-2.dsc
 44fce70fdec5d2a1095b32e5cb8d2b778734823b 7963 wayland_1.10.0-2.diff.gz
Checksums-Sha256:
 286235130a577dda45254d7ea5a3cde4a9fa193fb444669bcca6b2e069b88473 2324 
wayland_1.10.0-2.dsc
 a17c105e27250fbe440585eb8584d8fd2da2a1080602877d9f9fa747f060d312 7963 
wayland_1.10.0-2.diff.gz
Files:
 4fb7b14300da64a801cf0606ad76d361 2324 x11 optional wayland_1.10.0-2.dsc
 610fc5d7d43548b31ee7026dc1f70b0c 7963 x11 optional wayland_1.10.0-2.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXF91kAAoJEJ1GxIjkNoMCz5UQAMekwJ9rTOVyFfvlke7/sssR
xqnPZL84iBeXqw0TmlIFkN7cOyepOVOE8Vf9DgeOc+5iMUVY8DKQh4j/IQYYL65m
5fe/MMmy2ziSyEO8ew63SXWBrD8uATgfXu40vQjWwrb4LKBuCQtsxqxo+1S2umi1
20ocnKHZ/CM/rBVWxL2GNpSFU2RbrjaSjZY7mRXTS39lC4YN6ORc4OGqDVO1/iXP
gfQ2OQq8yOgo0pI2BQ/GObJ5PZ84uMjnKeCJjFAEi06QVh8SyWl6YardXfR2VqBV
CkkosB6TflrxITGqbid6NtaRwiZuIu2CU98OGg04Z9WuSXTz/VUvChttNXKvuUcT
iGAtrTMNAaNBGgc2M8CyE724bTyvfUBPfuGOgYvAWTTjCGZTKG31qLXapdAPyBcC
4R6VyeASq5i5y43+nrJ7++iScUSE3aFvymKeNjbOnQjuTR9gmgsh9b1ot11RSw1j
4CnTPkWt4Ie2bCY7I5kooVi7OKKukbfr9QpfK+JTfxki3DXF6Ag4YCFUde9tGOyM
CJ4Ti+gPkEXSW46TbFilgBcrH2ivAx2yGZnUWfqmIGfhwQ+RCT7H31MKOHN/s9/v
oIFKq08UQpasdmKRPjcWa5LM2QlNSAZ1gaJgwrIzQxIbakFJ5fIfIwqKFfj8Fo0w
D3MtWElWgpq1R2bDjRZO
=s8EX
-END PGP SIGNATURE End Message ---

Bug#791567: marked as done (libwayland-server0: Multiseat configurazione stopped working after libwayland upgrade from 1.7.0-2 to 1.8.1-1)

[Debian Bug Tracking System]

Your message dated Wed, 20 Apr 2016 22:15:01 +0200
with message-id <5717e345.2080...@debian.org>
and subject line Re: Bug#791567: libwayland-server0: Multiseat configurazione 
stopped working after libwayland upgrade from 1.7.0-2 to 1.8.1-1
has caused the Debian Bug report #791567,
regarding libwayland-server0: Multiseat configurazione stopped working after 
libwayland upgrade from 1.7.0-2 to 1.8.1-1
to be marked as done.

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

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


-- 
791567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwayland-server0
Version: 1.8.1-1
Severity: normal

Dear Maintainer,

I have a machine with 2 nvidia graphic cards, configured as multiseat, with 2
seats.
Debian is version testing (stretch). I use nouveau driver for nvidia cards.
The output of "loginctl seat-status seat1" is normal.

during an upgrade, libwayland updated from 1.7.0-2 to 1.8.1-1 and systemd/udev
from version 215-17 to
220-7. After that multiseat stopped working.
X server for seat1 is not started.
Using keyboard on seat1 affects seat0. The mouse does not have this behaviour.

I tried:
- loginctl flush-devices and the loginctl attach to redo multiseat
configuration
- move of keyboard and mouse on another usb ports
- change of desktop manager (from gdm3 to lightdm)
- upgrade of systemd to 221-1
- search on internet for known bugs or anomalies

I already opened a bug for systemd package and I wrote to systemd list. They
said that systemd just do a list of attached devices on seats. If output of
"loginctl seat-status" is ok it should not be a problem of systemd but
"something between X and gdm". Gdm upgraded from 3.14.1-7 to 3.14.1-8 therefore
should not be the cause.

"something between X and gdm" could be libwayland?

Regards



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwayland-server0 depends on:
ii  libc62.19-18
ii  libffi6  3.1-2+b2

libwayland-server0 recommends no packages.

libwayland-server0 suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
On 06/07/15 12:07, Alberto wrote:
> Package: libwayland-server0
> Version: 1.8.1-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I have a machine with 2 nvidia graphic cards, configured as multiseat, with 2
> seats.
> Debian is version testing (stretch). I use nouveau driver for nvidia cards.
> The output of "loginctl seat-status seat1" is normal.
> 
> during an upgrade, libwayland updated from 1.7.0-2 to 1.8.1-1 and systemd/udev
> from version 215-17 to
> 220-7. After that multiseat stopped working.
> X server for seat1 is not started.
> Using keyboard on seat1 affects seat0. The mouse does not have this behaviour.
> 
> I tried:
> - loginctl flush-devices and the loginctl attach to redo multiseat
> configuration
> - move of keyboard and mouse on another usb ports
> - change of desktop manager (from gdm3 to lightdm)
> - upgrade of systemd to 221-1
> - search on internet for known bugs or anomalies
> 
> I already opened a bug for systemd package and I wrote to systemd list. They
> said that systemd just do a list of attached devices on seats. If output of
> "loginctl seat-status" is ok it should not be a problem of systemd but
> "something between X and gdm". Gdm upgraded from 3.14.1-7 to 3.14.1-8 
> therefore
> should not be the cause.
> 
> "something between X and gdm" could be libwayland?

Definitely not. wayland doesn't do anything on an X session.

I'm closing this. Feel free to reopen if you're still suffering from this, and
we'll look for a package to reassign this to.

Cheers,
Emilio--- End Message ---

Bug#821954: libdrm: diff for NMU version 2.4.67-1.1

[Julien Cristau]

On Wed, Apr 20, 2016 at 21:31:51 +0200, Tobias Frost wrote:

> Package: libdrm
> Version: 2.4.67-1
> Severity: normal
> Tags: patch pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for libdrm (versioned as 2.4.67-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
> 
> This NMU ports libdrm to hurd. This will help us to compile e.g
> gst-plugins-bad1.0 which will help us to remove obsolete binary
> packages and eventually libpng 1.2...
> 
> The patch has been written in a way to only change code on hurd,
> all other archs are unaffected.
> 
Also, when did hurd grow DRM support?  It doesn't make sense to build
libdrm without that...

Cheers,
Julien

wayland: Changes to 'debian-unstable'

[Emilio Pozuelo Monfort]

 debian/changelog  |   10 ++
 debian/control|   63 --
 debian/libwayland-dev.install |3 --
 debian/libwayland-doc.install |3 ++
 debian/rules  |   12 ++--
 5 files changed, 28 insertions(+), 63 deletions(-)

New commits:
commit b68680e20fdbb27eb42845e4abe71066daf396e8
Author: Emilio Pozuelo Monfort 
Date:   Wed Apr 20 21:39:13 2016 +0200

Release to unstable

diff --git a/debian/changelog b/debian/changelog
index 6e94e14..bcbb87c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-wayland (1.10.0-2) UNRELEASED; urgency=medium
+wayland (1.10.0-2) unstable; urgency=medium
 
   * Don't build the documentation on binary-arch only builds. Move the
 build-dependencies needed for the documentation to build-depends-indep.
@@ -6,7 +6,7 @@ wayland (1.10.0-2) UNRELEASED; urgency=medium
   * Move the manpages to libwayland-doc.
   * Switch to dbgsym packages.
 
- -- Emilio Pozuelo Monfort   Wed, 20 Apr 2016 19:58:36 +0200
+ -- Emilio Pozuelo Monfort   Wed, 20 Apr 2016 21:38:58 +0200
 
 wayland (1.10.0-1) unstable; urgency=medium
 

commit 226ffd3974de14cc2dd5b13caba48107ebb8c8de
Author: Emilio Pozuelo Monfort 
Date:   Wed Apr 20 21:27:49 2016 +0200

Switch to dbgsym packages

diff --git a/debian/changelog b/debian/changelog
index cf99c33..6e94e14 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,7 @@ wayland (1.10.0-2) UNRELEASED; urgency=medium
 build-dependencies needed for the documentation to build-depends-indep.
 Closes: #821170.
   * Move the manpages to libwayland-doc.
+  * Switch to dbgsym packages.
 
  -- Emilio Pozuelo Monfort   Wed, 20 Apr 2016 19:58:36 +0200
 
diff --git a/debian/control b/debian/control
index 08fbc66..c610c86 100644
--- a/debian/control
+++ b/debian/control
@@ -44,24 +44,6 @@ Description: wayland compositor infrastructure - client 
library
  This package ships the library that implements the client side of
  the Wayland protocol.
 
-Package: libwayland-client0-dbg
-Section: debug
-Priority: extra
-Architecture: any
-Depends:
- libwayland-client0 (= ${binary:Version}),
- ${shlibs:Depends},
- ${misc:Depends},
-Description: wayland compositor infrastructure - client library (debug)
- Wayland is a protocol for a compositor to talk to its clients as well
- as a C library implementation of that protocol. The compositor can be
- a standalone display server running on Linux kernel modesetting and
- evdev input devices, an X application, or a wayland client
- itself. The clients can be traditional applications, X servers
- (rootless or fullscreen) or other display servers.
- .
- This package provides debugging symbols for the libwayland-client0 package.
-
 Package: libwayland-server0
 Section: libs
 Architecture: any
@@ -84,24 +66,6 @@ Description: wayland compositor infrastructure - server 
library
  This package ships the library that implements the server side of
  the Wayland protocol.
 
-Package: libwayland-server0-dbg
-Section: debug
-Priority: extra
-Architecture: any
-Depends:
- libwayland-server0 (= ${binary:Version}),
- ${shlibs:Depends},
- ${misc:Depends},
-Description: wayland compositor infrastructure - server library (debug)
- Wayland is a protocol for a compositor to talk to its clients as well
- as a C library implementation of that protocol. The compositor can be
- a standalone display server running on Linux kernel modesetting and
- evdev input devices, an X application, or a wayland client
- itself. The clients can be traditional applications, X servers
- (rootless or fullscreen) or other display servers.
- .
- This package provides debugging symbols for the libwayland-server0 package.
-
 Package: libwayland-cursor0
 Section: libs
 Architecture: any
@@ -122,24 +86,6 @@ Description: wayland compositor infrastructure - cursor 
library
  .
  This package ships a helper library to manage cursors.
 
-Package: libwayland-cursor0-dbg
-Section: debug
-Priority: extra
-Architecture: any
-Depends:
- libwayland-cursor0 (= ${binary:Version}),
- ${shlibs:Depends},
- ${misc:Depends},
-Description: wayland compositor infrastructure - cursor library (debug)
- Wayland is a protocol for a compositor to talk to its clients as well
- as a C library implementation of that protocol. The compositor can be
- a standalone display server running on Linux kernel modesetting and
- evdev input devices, an X application, or a wayland client
- itself. The clients can be traditional applications, X servers
- (rootless or fullscreen) or other display servers.
- .
- This package provides debugging symbols for the libwayland-cursor0 package.
-
 Package: libwayland-dev
 Section: libdevel
 Architecture: any
diff --git a/debian/rules b/debian/rules
index bb0539c..8ad1821 100755
--- a/debian/rules
+++ b/debian/rules
@@ -23,9 +23,9 @@ override_dh_makeshlibs:
 
 # Debug package:
 

Processing of wayland_1.10.0-2_source.changes

[Debian FTP Masters]

wayland_1.10.0-2_source.changes uploaded successfully to localhost
along with the files:
  wayland_1.10.0-2.dsc
  wayland_1.10.0-2.diff.gz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

wayland: Changes to 'refs/tags/wayland-1.10.0-2'

[Emilio Pozuelo Monfort]

Tag 'wayland-1.10.0-2' created by Emilio Pozuelo Monfort  at 
2016-04-20 19:39 +

Tagging upload of wayland 1.10.0-2 to unstable.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAABCAAGBQJXF9rvAAoJEJ1GxIjkNoMCiCEQAMf1rseurI2i/p04rbIG3g7L
nScUCdcNgvIcP5PUadXzty4zwY2eZdEKqbbc7p7Q5rwSujCDw/u+2NYjVVSxTiVL
lXF6B9t+lDXXvaElkRqNyVGMgtQ6xJd4kcKRNzBhVb6xkIyqPyxWUHY+9Hgjz9O9
ADkCJeCedLP804sceyvSFrjgaYvKGw73v9ULxLZEXJbMs8SnBf5gMB4xTNKqPVsW
d9lqWilbkhHVw3ZIz6CTly8GnVpxCae51sLBnwTxZU5Aa7AlDaeMgL7y/eRgnT3P
L8Ltr1zawouifYRc/lw1Ji8+dBbkAdcVfoPEqbIpQQo3vW5QbYO+cqutIwhuQjWY
09b9/qome+H8CO3Sy2sJW6dYz1ih+8BVICxKgwnFbY1GDYzL/GodLSh/1VAZM1g7
I7fxAySQQHXjwGRZ7EconCQWQ3C1YkiZAOgWCrS1VBSiVlr77D1TmDtC7KnOhQk+
YEynU0VThLLU2fZwhPwy8Ks31iF/s1n7uUgcmsHTLNGMk0nh4QVut9NMUST5yfrx
M4qcWcv7BfThzuWoct4hwDlO93+wyqUnIqPron0GfUksi2Kz9rzwbIUCejdKwu1C
3Di90JJwPKLvKNwtaHKy7bq4m0hJumpHiLCfm9MOqVSF69O3VLJ9aQjDN1d4xpk5
dbE2/NoiXn34mzhQ4aAf
=OziP
-END PGP SIGNATURE-

Changes since wayland-1.10.0-1:
Emilio Pozuelo Monfort (4):
  Don't build the documentation on binary-arch only builds
  Move the manpages to libwayland-doc
  Switch to dbgsym packages
  Release to unstable

---
 debian/changelog  |   10 ++
 debian/control|   63 --
 debian/libwayland-dev.install |3 --
 debian/libwayland-doc.install |3 ++
 debian/rules  |   12 ++--
 5 files changed, 28 insertions(+), 63 deletions(-)
---

Bug#821954: libdrm: diff for NMU version 2.4.67-1.1

[Julien Cristau]

On Wed, Apr 20, 2016 at 21:31:51 +0200, Tobias Frost wrote:

> Package: libdrm
> Version: 2.4.67-1
> Severity: normal
> Tags: patch pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for libdrm (versioned as 2.4.67-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
> 
> This NMU ports libdrm to hurd. This will help us to compile e.g
> gst-plugins-bad1.0 which will help us to remove obsolete binary
> packages and eventually libpng 1.2...
> 
> The patch has been written in a way to only change code on hurd,
> all other archs are unaffected.
> 
Was this sent/reviewed upstream?  If not, then please cancel the NMU.

Cheers,
Julien

Processing of libdrm_2.4.67-1.1_source.changes

[Debian FTP Masters]

libdrm_2.4.67-1.1_source.changes uploaded successfully to localhost
along with the files:
  libdrm_2.4.67-1.1.dsc
  libdrm_2.4.67-1.1.diff.gz

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

Bug#821954: libdrm: diff for NMU version 2.4.67-1.1

[Tobias Frost]

Package: libdrm
Version: 2.4.67-1
Severity: normal
Tags: patch pending

Dear maintainer,

I've prepared an NMU for libdrm (versioned as 2.4.67-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

This NMU ports libdrm to hurd. This will help us to compile e.g
gst-plugins-bad1.0 which will help us to remove obsolete binary
packages and eventually libpng 1.2...

The patch has been written in a way to only change code on hurd,
all other archs are unaffected.

--
tobi

Regards.
diff -u libdrm-2.4.67/debian/changelog libdrm-2.4.67/debian/changelog
--- libdrm-2.4.67/debian/changelog
+++ libdrm-2.4.67/debian/changelog
@@ -1,3 +1,10 @@
+libdrm (2.4.67-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch for hurd. (Closes: #xx) 
+
+ -- Tobias Frost   Wed, 20 Apr 2016 21:19:56 +0200
+
 libdrm (2.4.67-1) unstable; urgency=medium
 
   * New upstream release.
diff -u libdrm-2.4.67/debian/patches/series libdrm-2.4.67/debian/patches/series
--- libdrm-2.4.67/debian/patches/series
+++ libdrm-2.4.67/debian/patches/series
@@ -1,0 +2 @@
+02_hurd.patch
only in patch2:
unchanged:
--- libdrm-2.4.67.orig/debian/patches/02_hurd.patch
+++ libdrm-2.4.67/debian/patches/02_hurd.patch
@@ -0,0 +1,147 @@
+--- a/include/drm/drm.h
 b/include/drm/drm.h
+@@ -42,10 +42,19 @@
+ #include 
+ typedef unsigned int drm_handle_t;
+ 
++#elif defined(__gnu_hurd__)
++#include 
++#include 
++
+ #else /* One of the BSDs */
+ 
+ #include 
+ #include 
++
++#endif
++
++#if !defined(__linux__)
++
+ typedef int8_t   __s8;
+ typedef uint8_t  __u8;
+ typedef int16_t  __s16;
+--- a/xf86drm.h
 b/xf86drm.h
+@@ -58,7 +58,11 @@
+ 
+ #else /* One of the *BSDs */
+ 
++#if defined(__gnu_hurd__)
++#include 
++#else
+ #include 
++#endif
+ #define DRM_IOCTL_NR(n) ((n) & 0xff)
+ #define DRM_IOC_VOIDIOC_VOID
+ #define DRM_IOC_READIOC_OUT
+--- a/xf86drm.c
 b/xf86drm.c
+@@ -103,6 +103,16 @@
+ 
+ #define memclear(s) memset(, 0, sizeof(s))
+ 
++/* for systems like hurd which does not have PATH_MAX.
++ Usage is only for string manipulation, so it is save to define it.
++ 1kB will be plenty space...*/
++#ifndef PATH_MAX
++#define MY_PATH_MAX (1024)
++#else
++#define MY_PATH_MAX PATH_MAX
++#endif
++
++
+ static drmServerInfoPtr drm_server_info;
+ 
+ void drmSetServerInfo(drmServerInfoPtr info)
+@@ -2835,14 +2845,15 @@
+ static int drmParseSubsystemType(int maj, int min)
+ {
+ #ifdef __linux__
+-char path[PATH_MAX + 1];
+-char link[PATH_MAX + 1] = "";
++
++char path[MY_PATH_MAX + 1];
++char link[MY_PATH_MAX + 1] = "";
+ char *name;
+ 
+-snprintf(path, PATH_MAX, "/sys/dev/char/%d:%d/device/subsystem",
++snprintf(path, MY_PATH_MAX, "/sys/dev/char/%d:%d/device/subsystem",
+  maj, min);
+ 
+-if (readlink(path, link, PATH_MAX) < 0)
++if (readlink(path, link, MY_PATH_MAX) < 0)
+ return -errno;
+ 
+ name = strrchr(link, '/');
+@@ -2857,18 +2868,19 @@
+ #warning "Missing implementation of drmParseSubsystemType"
+ return -EINVAL;
+ #endif
++
+ }
+ 
+ static int drmParsePciBusInfo(int maj, int min, drmPciBusInfoPtr info)
+ {
+ #ifdef __linux__
+-char path[PATH_MAX + 1];
++char path[MY_PATH_MAX + 1];
+ char data[128 + 1];
+ char *str;
+ int domain, bus, dev, func;
+ int fd, ret;
+ 
+-snprintf(path, PATH_MAX, "/sys/dev/char/%d:%d/device/uevent", maj, min);
++snprintf(path, MY_PATH_MAX, "/sys/dev/char/%d:%d/device/uevent", maj, 
min);
+ fd = open(path, O_RDONLY);
+ if (fd < 0)
+ return -errno;
+@@ -2949,11 +2961,11 @@
+  drmPciDeviceInfoPtr device)
+ {
+ #ifdef __linux__
+-char path[PATH_MAX + 1];
++char path[MY_PATH_MAX + 1];
+ unsigned char config[64];
+ int fd, ret;
+ 
+-snprintf(path, PATH_MAX, "/sys/class/drm/%s/device/config", d_name);
++snprintf(path, MY_PATH_MAX, "/sys/class/drm/%s/device/config", d_name);
+ fd = open(path, O_RDONLY);
+ if (fd < 0)
+ return -errno;
+@@ -3082,7 +3094,7 @@
+ DIR *sysdir;
+ struct dirent *dent;
+ struct stat sbuf;
+-char node[PATH_MAX + 1];
++char node[MY_PATH_MAX + 1];
+ int node_type, subsystem_type;
+ int maj, min;
+ int ret, i, node_count;
+@@ -3118,7 +3130,7 @@
+ if (node_type < 0)
+ continue;
+ 
+-snprintf(node, PATH_MAX, "%s/%s", DRM_DIR_NAME, dent->d_name);
++snprintf(node, MY_PATH_MAX, "%s/%s", DRM_DIR_NAME, dent->d_name);
+ if (stat(node, ))
+ continue;
+ 
+@@ -3198,7 +3210,7 @@
+ DIR *sysdir;
+ struct dirent *dent;
+ struct stat sbuf;
+-char node[PATH_MAX + 1];
++char node[MY_PATH_MAX + 1];
+ int node_type, subsystem_type;
+ int maj, min;
+ int ret, i, node_count, device_count;
+@@ -3220,7 +3232,7 @@
+ if (node_type < 0)
+ continue;
+ 
+-snprintf(node, PATH_MAX, "%s/%s", DRM_DIR_NAME, 

xorg: Changes to 'debian-unstable'

[Emilio Pozuelo Monfort]

 debian/changelog |6 ++
 debian/control   |1 +
 2 files changed, 7 insertions(+)

New commits:
commit e72c0bce0b8464fd7052ece5bc7adf77e63781ca
Author: Emilio Pozuelo Monfort 
Date:   Wed Apr 20 19:33:37 2016 +0200

Make x-x-input-all depend on x-x-input-libinput

diff --git a/debian/changelog b/debian/changelog
index f7cb255..fb2c22d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+xorg (1:7.7+15) UNRELEASED; urgency=medium
+
+  * Make x-x-input-all depend on x-x-input-libinput. Closes: #821760.
+
+ -- Emilio Pozuelo Monfort   Wed, 20 Apr 2016 19:32:45 +0200
+
 xorg (1:7.7+14) unstable; urgency=medium
 
   [ Timo Aaltonen ]
diff --git a/debian/control b/debian/control
index ebf144f..388e49f 100644
--- a/debian/control
+++ b/debian/control
@@ -74,6 +74,7 @@ Architecture: any
 Depends:
  xserver-xorg-input-evdev [linux-any],
  xserver-xorg-input-kbd [!linux-any],
+ xserver-xorg-input-libinput [linux-any],
  xserver-xorg-input-mouse [!linux-any],
  xserver-xorg-input-synaptics [!s390x],
  xserver-xorg-input-vmmouse [amd64 i386 x32],

Bug#821760: Please pull in xserver-xorg-input-libinput

[Emilio Pozuelo Monfort]

Control: tags -1 pending

On 20/04/16 11:35, Julien Cristau wrote:
> On Tue, Apr 19, 2016 at 04:26:30 +0200, Michael Biebl wrote:
> 
>> Package: xserver-xorg-input-all
>> Version: 1:7.7+14
>> Severity: normal
>>
>> Hi,
>>
>> GNOME 3.20 has dropped support for non-libinput mouse configurations [1]
>> So any configuration changes you make in gnome-control-center won't have
>> any effect unless xserver-xorg-input-libinput is installed, e.g. my
>> tap-to-click touchpad settings had no effect otherwise [2]
>>
>> We quickly discussed this issue on #debian-gnome IRC where I suggested
>> that we let one of the GNOME packages pull in
>> xserver-xorg-input-libinput.
>>
>> pochu mentioned that doing this via xserver-xorg-input-all might be
>> nicer. What's the state of xserver-xorg-input-libinput, Timo? Do you
>> consider it ready for the masses and do we want to have it installed
>> (and enabled) by default?
>>
> I don't know the answer to that question, but if the answer is no, then
> it shouldn't be pulled in by gnome either...

It should be. I've been using it for a while and it's working fairly well. Also
Timo said that it doesn't override wacom.

I've added it in git, will wait a few days before uploading.

Cheers,
Emilio

Processed: Re: Bug#821760: Please pull in xserver-xorg-input-libinput

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #821760 [xserver-xorg-input-all] Please pull in xserver-xorg-input-libinput
Added tag(s) pending.

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

Bug#821389: xinput: please support distinct device IDs

[Julien Cristau]

On Mon, Apr 18, 2016 at 13:40:31 +0200, Harald Dunkel wrote:

> Package: xinput
> Version: 1.6.1-1
> 
> Seems that xinput doesn't really know how to identify
> the devices, either. Sample session:
> 
> % xinput list-props "Logitech USB Receiver"
> Warning: There are multiple devices matching 'Logitech USB Receiver'.
> To ensure the correct one is selected, please use the device ID, or prefix the
> device name with 'pointer:' or 'keyboard:' as appropriate.
> 
> unable to find device Logitech USB Receiver
> 
I don't think there's an xinput bug here.  xinput just doesn't have any
more information about the devices...

Cheers,
Julien

Bug#815162: xserver-xorg-legacy: completely broken (locks up input / xf86OpenConsole: Cannot open virtual console)

[Julien Cristau]

On Sun, Apr 17, 2016 at 06:24:31 +0200, Jan Braun wrote:

> Control: unmerge -1
> Control: severity -1 important
> Control: tag -1 - moreinfo
> Control: retitle -1 xserver-xorg-legacy: locks up input when used with 
> neither libpam-systemd nor manual configuration
> 
> Jan Braun schrob:
> > If you want to downgrade (and merge with #814313), I won't object, but
> > I'll not do that myself because dataloss failure mode and apt-listbugs
> > visibility.
> 
> Sorry, but you merged with #814394 (wishlist moreinfo), not #814313
> (important). If you actually think this bug is a wishlist and/or needs
> more info, please explain.
> 
This is not a bug.  If you ignore the Recommends on libpam-systemd, you
need manual configuration to make things not broken.

Cheers,
Julien

Bug#821760: Please pull in xserver-xorg-input-libinput

[Julien Cristau]

On Tue, Apr 19, 2016 at 04:26:30 +0200, Michael Biebl wrote:

> Package: xserver-xorg-input-all
> Version: 1:7.7+14
> Severity: normal
> 
> Hi,
> 
> GNOME 3.20 has dropped support for non-libinput mouse configurations [1]
> So any configuration changes you make in gnome-control-center won't have
> any effect unless xserver-xorg-input-libinput is installed, e.g. my
> tap-to-click touchpad settings had no effect otherwise [2]
> 
> We quickly discussed this issue on #debian-gnome IRC where I suggested
> that we let one of the GNOME packages pull in
> xserver-xorg-input-libinput.
> 
> pochu mentioned that doing this via xserver-xorg-input-all might be
> nicer. What's the state of xserver-xorg-input-libinput, Timo? Do you
> consider it ready for the masses and do we want to have it installed
> (and enabled) by default?
> 
I don't know the answer to that question, but if the answer is no, then
it shouldn't be pulled in by gnome either...

Cheers,
Julien

Bug#821763: xserver-xorg-video-radeon: LibreOffice Preferences UI font corruption on AMD A6-1450 APU/Radeon HD 8250

[Michel Dänzer]

On 19.04.2016 16:18, J Mo wrote:
> 
> The other system I put my drive into had a Nvidia GTX 970 and definitely
> nouveau as it's newly installed Debian as of last week and I made no
> special configuration changes.

So, can you check whether the Xorg modesetting driver is used with that,
and whether it enables glamor acceleration? And if either is not true,
can you try forcing it in xorg.conf and see if you can reproduce the
problem then?


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer