Bug#917026: xorg: All the system freezes when ejects an USB stick with Thunar

2018-12-21 Thread Bernhard Übelacker 
Hello Alain,
just saw your report and though it sounds similar to another one [1].
Do you have linux-image in version 4.9.130-2 installed?
Were older kernels working like expected?
If possible you might want also check if reverting back
to 4.9.110-3+deb9u6 gives you a not hanging system on eject.

Kind regards,
Bernhard

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914696

Bug#917046: mesa: ease cross build dependency installability

2018-12-21 Thread Héctor Orón Martínez 
Source: mesa
Version: 18.3.0-1
Severity: wishlist
Tags: patch

Dear Maintainer,

  Please consider easing cross dependency installability.
  Find propose patch:
  https://salsa.debian.org/xorg-team/lib/mesa/merge_requests/6

Regards

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.17.0-3-amd64 (SMP w/16 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_AD:ca (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#917034: xterm crashes on certain Unicode characters when font was selected with -fa

2018-12-21 Thread Alexander Meyer 
* Sven Joachim  [2018-12-21 20:38]:

> On 2018-12-21 20:16 +0100, Alexander Meyer wrote:
> 
>> Package: xterm
>> Version: 340-1
>> Severity: important
>> [...]
>> I've found a bug report from Arch Linux that looks similar:
>> https://bugs.archlinux.org/task/61115
> 
> Strange that you looked in the Arch bugtracker, but apparently not in
> the Debian BTS…

That came up via a web search as I had originally thought the bug had to
do with mutt.

>> But the last comment there claims the bug disappeared in 340 which is not the
>> case for me.
> 
> I could also still reproduce it, that's why I did not close #916349 in
> the xterm 340-1 upload.

I couldn't tell whether that bug was the same as mine, as none of the
error messages mentioned there came up for me, also that bug doesn't
talk about segfaulting.

If you think this is the same bug, then feel free to merge, of course.

Thanks
Alex

Processed: Re: Bug#917034: xterm crashes on certain Unicode characters when font was selected with -fa

2018-12-21 Thread Debian Bug Tracking System 
Processing control commands:

> merge 916349 -1
Bug #916349 [xterm] xterm: X error (BadLength) when trying to display some 
glyphs
Bug #916349 [xterm] xterm: X error (BadLength) when trying to display some 
glyphs
Marked as found in versions xterm/340-1.
Bug #917034 [xterm] xterm crashes on certain Unicode characters when font was 
selected with -fa
Marked as found in versions xterm/338-1.
Merged 916349 917034

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

Bug#917034: xterm crashes on certain Unicode characters when font was selected with -fa

2018-12-21 Thread Sven Joachim 
Control: merge 916349 -1

On 2018-12-21 20:16 +0100, Alexander Meyer wrote:

> Package: xterm
> Version: 340-1
> Severity: important
> [...]
> I've found a bug report from Arch Linux that looks similar:
> https://bugs.archlinux.org/task/61115

Strange that you looked in the Arch bugtracker, but apparently not in
the Debian BTS…

> But the last comment there claims the bug disappeared in 340 which is not the
> case for me.

I could also still reproduce it, that's why I did not close #916349 in
the xterm 340-1 upload.

Cheers,
   Sven

Bug#917034: xterm crashes on certain Unicode characters when font was selected with -fa

2018-12-21 Thread Alexander Meyer 
Package: xterm
Version: 340-1
Severity: important

Dear Maintainer,

after updating from 337-1 to 338-1 in testing, xterm crashes with a segfault
when certain Unicode characters appear in the buffer. This only happens when I
have selected a font using the -fa option. It doesn't seem to matter which font
it is. (I've randomly tried a few from my fc-list.)

I've installed 340-1 from unstable, but the bug persists.

As I came across this issue while reading mails in mutt, I've tried to identify
the exact characters causing it. It turned out that these commands cause the
crash:

$ /usr/bin/printf "\U0001F384"# U+1F384 CHRISTMAS TREE
$ /usr/bin/printf "\U0001F385"# U+1F385 FATHER CHRISTMAS
$ /usr/bin/printf "\U0001F3E1"# U+1F3E1 HOUSE WITH GARDEN
$ /usr/bin/printf "\U0001F644"# U+1F644 FACE WITH ROLLING EYES

Whereas these commands work fine:

$ /usr/bin/printf "\U0001F601"# U+1F601 GRINNING FACE WITH SMILING EYES
$ /usr/bin/printf "\U0001F604"# U+1F604 SMILING FACE WITH OPEN MOUTH 
AND SMILING EYES

To reproduce this bug, run one of the aforementioned commands after starting
xterm with e.g.

$ xterm -fa 'Noto Mono'

When leaving out -fa, xterm doesn't crash.

Please find below a backtrace.

As the bug was introduced after updating xterm (libfontconfig1 remained
untouched during that update), I'm filing this under xterm for the time being.

xterm 337-1 doesn't crash. Interestingly, though, in 337-1 all six
above-mentioned characters are not displayed at all when running with e.g.
-fa 'Noto Mono'. I just see a two-glyph-wide blank space. Whereas in 338-1 and
340-1, the two non-crashing characters U+1F601 and U+1F604 are actually
displayed.

I've found a bug report from Arch Linux that looks similar:
https://bugs.archlinux.org/task/61115
But the last comment there claims the bug disappeared in 340 which is not the
case for me.

I don't know a great deal about X font handling, so in case you need more info,
please try to explain in detail what you need to know. Thanks in advance. Also,
I don't care that much if those special glyphs are actually displayed correctly
in my xterm or not, it's just that xterm shouldn't crash.


Backtrace:

Reading symbols from /usr/bin/xterm...Reading symbols from 
/usr/lib/debug/.build-id/e1/82f855c9d3aa8701e44c1fc1d41e81eb0b0bd6.debug...done.
done.
(gdb) run -fa 'Noto Mono'
Starting program: /usr/bin/xterm -fa 'Noto Mono'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x77d662d1 in FcConfigEvaluate (p=0x556fdfd0, 
p_pat=0x559ea680, kind=kind@entry=FcMatchFont, e=0x0) at fccfg.c:977
(gdb) bt full
#0  0x77d662d1 in FcConfigEvaluate (p=0x556fdfd0, 
p_pat=0x559ea680, kind=kind@entry=FcMatchFont, e=0x0) at fccfg.c:977
v = {type = FcTypeVoid, u = {s = 0x556fd670 "\300\326oUUU", 
i = 1433392752, b = 1433392752, d = 4.6355706243752135e-310, 
m = 0x556fd670, c = 0x556fd670, f = 0x556fd670, 
l = 0x556fd670, r = 0x556fd670}}
vl = {type = 1433007920, u = {s = 0x0, i = 0, b = 0, d = 0, m = 0x0, 
c = 0x0, f = 0x0, l = 0x0, r = 0x0}}
vr = {type = 1436460672, u = {s = 0x0, i = 0, b = 0, d = 0, m = 0x0, 
c = 0x0, f = 0x0, l = 0x0, r = 0x0}}
vle = 
vre = 
m = 
str = 
op = 
buf1 = {u = {d = 0, i = 0, l = 0, 
c = "\000\000\000\000\000\000\000\000 
\326oUUU\000\000H\367iUUU\000\000\000\000\000\000\000\000\000\000\200\246\236UUU",
 '\000' , 
"\256m\326\367\377\177\000\000\000\000\000\000\000\000\000\000\320\325oUUU\000\000`\367iUUU\000\000\000\000\000\000\000\000\000\000\200\246\236UUU",
 '\000' , 
"\256m\326\367\377\177\000\000\000\000\000\000\000\000\000\000\200\325oUUU\000\000x\367iUUU\000\000\000\000\000\000\000\000\000\000\200\246\236UUU",
 '\000' , 
"\256m\326\367\377\177\000\000\000\000\000\000\000\000\000\000"...}}
buf2 = {u = {d = 0, i = 0, l = 0, 
c = 
"\000\000\000\000\000\000\000\000\340\324oUUU\000\000\250\367iUUU\000\000\000\000\000\000\000\000\000\000\025",
 '\000' , "\a\000\000\000\000\000\000\000 
\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000\020\300aUUU\000\000\017\000\000\000\000\000\000\000@\000\000\000\000\000\000\000\260\377\377\377\377\377\377\377\000\000\000\000\000\000\000\000\002\000\000\000\060",
 '\000' , "[\000\000\000w", '\000' , 
"n\000\000\000|\000\000\000\t\000\000\000\000\000\000\000\017\000\000\000\000\000\000\000\025",
 '\000' , "\260\377\377\377\377\377\377\377"...}}
#1  0x77d66418 in FcConfigEvaluate (p=p@entry=0x556fdfd0, 
p_pat=p_pat@entry=0x559ea680, kind=kind@entry=FcMatchFont, 
e=e@entry=0x55683b38) at fccfg.c:1003
m = {xx = 1.4821969375237396e-323, xy = 6.9533490418283141e-310, 
  yx =

Bug#916349: Happens with other xterm clients as well

2018-12-21 Thread Sven Joachim 
On 2018-12-21 17:49 +0100, Philipp Marek wrote:

> I'm using
>
> !XTerm*faceName: DejaVu Sans Mono
>
> and my xterm -> mosh -> screen -> irssi crashes reproducibly when resizing 
> the window in the irssi tab. At least it did so 10 times in a row before
> starting to reply here ;)
>
> Yeah, and now it happens again - resizing the window _sometimes_ works
> in a plain shell window, in the IRSSI window it reproducibly crashes.
>
>
> Another font file is being opened, though:
>
> 13967 17:30:55.114945 openat(AT_FDCWD, 
> "/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf", O_RDONLY) = 5

That's the font which triggers the problem.  Uninstalling the
fonts-noto-color-emoji works around it.

> No missing glyphs that I know of ... how would I see them?

At least not with xfd(1) because it shows the same allergic reaction as
xterm:

,
| $ xfd -fa 'Noto Color Emoji'
| X Error of failed request:  BadLength (poly request too large or internal 
Xlib length error)
|   Major opcode of failed request:  139 (RENDER)
|   Minor opcode of failed request:  20 (RenderAddGlyphs)
|   Serial number of failed request:  226
|   Current serial number in output stream:  484
`

See also #892611 in Emacs.

Cheers,
   Sven

Bug#916349: Happens with other xterm clients as well

2018-12-21 Thread Philipp Marek 
I'm using

!XTerm*faceName: DejaVu Sans Mono

and my xterm -> mosh -> screen -> irssi crashes reproducibly when resizing 
the window in the irssi tab. At least it did so 10 times in a row before
starting to reply here ;)

Yeah, and now it happens again - resizing the window _sometimes_ works
in a plain shell window, in the IRSSI window it reproducibly crashes.


Another font file is being opened, though:

13967 17:30:55.114945 openat(AT_FDCWD, 
"/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf", O_RDONLY) = 5


No missing glyphs that I know of ... how would I see them?

Still I don't see why it should crash because of that.

Bug#917026: xorg: All the system freezes when ejects an USB stick with Thunar

2018-12-21 Thread alain 
Source: xorg
Severity: important

Dear Maintainer,

I mount a fat USB sticker with Thunar (and udisks).
All work fine.
When I eject with the arrow button in Thunar, all xorg freezes. The
mouse does not work and only a poweroff with the power button works.

Alt-Fx does not work.

No errors log in syslog.

-- System Information:
Debian Release: 9.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

wayland-protocols_1.17-1_source.changes ACCEPTED into unstable

2018-12-21 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 21 Dec 2018 16:04:03 +0100
Source: wayland-protocols
Binary: wayland-protocols
Architecture: source
Version: 1.17-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Héctor Orón Martínez 
Description:
 wayland-protocols - wayland compositor protocols
Changes:
 wayland-protocols (1.17-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/copyright: update
Checksums-Sha1:
 4056b67168438d66c62a0c86932a1ed0cccaf3e1 2342 wayland-protocols_1.17-1.dsc
 7d2569c838c776545e3eb1b1049b9c37178aae24 107680 
wayland-protocols_1.17.orig.tar.xz
 7066c91a88ac5c3794d98d75389386dce04561b9 847 
wayland-protocols_1.17.orig.tar.xz.asc
 e5e6d9630592d04dc85505b2422993c31967d9ce 8676 
wayland-protocols_1.17-1.debian.tar.xz
 ca8964c43c541e0f850cb980351c7d0d78d469cd 6298 
wayland-protocols_1.17-1_source.buildinfo
Checksums-Sha256:
 0b012a2078bc71b3cd54d649c74cc093435955fed172f5c1950d3f1bfdaffbc0 2342 
wayland-protocols_1.17-1.dsc
 df1319cf9705643aea9fd16f9056f4e5b2471bd10c0cc3713d4a4cdc23d6812f 107680 
wayland-protocols_1.17.orig.tar.xz
 47cd5922de9eecc9788a357c4e5ef4ce077f3bf3ffd2725d72d394de0f3a8e2a 847 
wayland-protocols_1.17.orig.tar.xz.asc
 7c3673e276079553999abda9f157ee28d9c467eb6e0f760969fcb31f94d41412 8676 
wayland-protocols_1.17-1.debian.tar.xz
 b5cbfbe48fcca95410a1d277889c98440fdf74b3120b594dda6cb38dcf28ac1a 6298 
wayland-protocols_1.17-1_source.buildinfo
Files:
 05723975080606afcf01c2d82f6450c8 2342 x11 optional wayland-protocols_1.17-1.dsc
 55ddd5fdb02b73b9de9559aaec267315 107680 x11 optional 
wayland-protocols_1.17.orig.tar.xz
 497353375a6febbbda1561122e725fdd 847 x11 optional 
wayland-protocols_1.17.orig.tar.xz.asc
 39522b3625c21dcc838a6dd7809b1d8b 8676 x11 optional 
wayland-protocols_1.17-1.debian.tar.xz
 202af8795f7bcda9e6a1e453d3a3f326 6298 x11 optional 
wayland-protocols_1.17-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAlwdARwACgkQryKDqnbi
rHvwbRAAmAsnEQas718jJt3FAlhtbiFIQgBiG9rTp6wmTOoaA/mAldOz4KmwjgQB
o2u2og/UIFBs85M6Ho6BKfhkX68+XYlqambnPeJ9e0BVjOSIpM0tk1gLS4Zf0wSp
+fkn1B875gZ/t7gkzPbLWakWXZhDPGQGK6VhEzogCi1wMnMVjCwX/EiYHxSO+umK
FuwM3lOWy+kCt0+oxwkDSPMbTOAjPfSki9Uzg2X8Sm0YTZlLnaMf5SIQZztdyLzD
M30VME9sN1zSdOGriIlOPdyqK86vEySec5tUFsb0nHDvdmQ5gbIp2q90TnsLHLQW
9Jm0MkD7riDNl+5ogeXo+lTa4bxuXzGl2kBeb1zLc+XcU2xURsN9pVVCOWuZr+kN
DSc5jELX+TxwoBQtArIRiUOLRlCXokQTp4YdR2UJuXqAIR+Qd/OQKlklPdnc5yK0
WQ7H55WEX2A8A+SFPlZOS5WuvawSTJQOib0bakA2nVHasGyQmOsUftx9YYwXKcH9
xrM0qzgbK7l1E1+S/HUPc3cE2p5P9tHXjd78cZDoA6q2rRGV57LVmIIcZbsAp1AA
EX8acRZN8LjuCKTJme/KgCfBUN55dC3/7nl+DnORAfe7c4AA8CpcMysNKD1y4d75
OWxKFDkadx/0OU46xqCoxZkbw2zJnBsFgEkwWF+Xk4aDi3rURAc=
=3fV5
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processed: closing 910409

2018-12-21 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> close 910409
Bug #910409 [wayland-protocols] wayland-protocols: Can't use second monitor via 
HDMI
Marked Bug as done
> thanks
Stopping processing here.

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

Processing of wayland-protocols_1.17-1_source.changes

2018-12-21 Thread Debian FTP Masters 
wayland-protocols_1.17-1_source.changes uploaded successfully to localhost
along with the files:
  wayland-protocols_1.17-1.dsc
  wayland-protocols_1.17.orig.tar.xz
  wayland-protocols_1.17.orig.tar.xz.asc
  wayland-protocols_1.17-1.debian.tar.xz
  wayland-protocols_1.17-1_source.buildinfo

Greetings,

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

Bug#910409: wayland-protocols: Can't use second monitor via HDMI

2018-12-21 Thread Pavlo Solntsev 
Thank you for paying attention to this issue. Shortly: this problem was
resolved. I am using testing and it looks like something was broken between
updates. After the next update, the problem was solved automatically.
Everything works fine now. We can close this bug. Thanks.

-Pavlo Solntsev
-

*Please avoid sending me Word or PowerPoint attachments.See
http://www.gnu.org/philosophy/no-word-attachments.html
*


On Fri, Dec 21, 2018 at 8:42 AM Hector Oron  wrote:

> Hello,
>
> On Fri, Oct 05, 2018 at 10:48:33PM -0500, Pavlo Solntsev wrote:
> > Package: wayland-protocols
> > Version: 1.16-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > I am not sure what package name I should use for this report. Today
> (Oct. 5,
> > 22:40T+6) I updated my system debian testing and my external monitor stop
> > working. In my xrandr output I see only one monitor
> > Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
> > XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y
> axis)
> > 290mm x 170mm
> >1920x1080 59.96*+
>
> `wayland-protocols` is not the package you are looking for.
> Do you see any relevant messages from kernel? i.e. `/var/log/messages`
>
> > Combination Fn+F8 (switch video mode) doesn't produce anything. I am not
> sure
> > what information I should ptovide. Please guide and I will send you
> info. You
> > can contact me directly if it helps: p.sun.fun at gmail dot com.
> >
> > The following packages were upgraded:
> > 2018-10-05 22:02:49 install libcamel-1.2-62:amd64  3.30.1-1
> > 2018-10-05 22:02:49 status half-installed libcamel-1.2-62:amd64 3.30.1-1
>
> Why do you have half-installed packages? Can you fully upgrade your system?
>
> > 2018-10-05 22:02:49 status half-installed
> evolution-plugin-bogofilter:amd64
> > 3.28.5-1
> > 2018-10-05 22:02:49 status half-installed
> evolution-plugin-bogofilter:amd64
> > 3.28.5-1
> > 2018-10-05 22:02:49 status half-installed
> evolution-plugin-pstimport:amd64
> > 3.28.5-1
> > 2018-10-05 22:02:49 status half-installed
> evolution-plugin-pstimport:amd64
> > 3.28.5-1
> > 2018-10-05 22:02:49 status half-installed evolution-plugins:amd64
> 3.28.5-1
> > 2018-10-05 22:02:49 status half-installed evolution-plugins:amd64
> 3.28.5-1
> > 2018-10-05 22:02:50 status half-installed evolution:amd64 3.28.5-1
> > 2018-10-05 22:02:50 status half-installed evolution:amd64 3.28.5-1
> > 2018-10-05 22:02:50 status half-installed libevolution:amd64 3.28.5-1
> > 2018-10-05 22:02:50 status half-installed libevolution:amd64 3.28.5-1
> > 2018-10-05 22:02:50 status half-installed evolution-data-server:amd64
> 3.28.5-3
> > 2018-10-05 22:02:51 status half-installed evolution-data-server:amd64
> 3.28.5-3
> > 2018-10-05 22:02:51 status installed libedata-cal-1.2-28:amd64 3.28.5-3
> > 2018-10-05 22:02:51 status half-installed libedata-cal-1.2-28:amd64
> 3.28.5-3
> > 2018-10-05 22:02:51 status not-installed libedata-cal-1.2-28:amd64 
> > 2018-10-05 22:02:51 status half-installed libecal1.2-dev:amd64 3.28.5-3
> > 2018-10-05 22:02:51 status half-installed libecal1.2-dev:amd64 3.28.5-3
> > 2018-10-05 22:02:52 status half-installed libecal-1.2-19:amd64 3.28.5-3
> > 2018-10-05 22:02:52 status half-installed libecal-1.2-19:amd64 3.28.5-3
> > 2018-10-05 22:02:52 status half-installed libebook-1.2-19:amd64 3.28.5-3
> > 2018-10-05 22:02:52 status half-installed libebook-1.2-19:amd64 3.28.5-3
> > 2018-10-05 22:02:52 status half-installed libedata-book1.2-dev:amd64
> 3.28.5-3
> > 2018-10-05 22:02:52 status half-installed libedata-book1.2-dev:amd64
> 3.28.5-3
> > 2018-10-05 22:02:52 status half-installed libedata-book-1.2-25:amd64
> 3.28.5-3
> > 2018-10-05 22:02:52 status half-installed libedata-book-1.2-25:amd64
> 3.28.5-3
> > 2018-10-05 22:02:53 status half-installed libebackend1.2-dev:amd64
> 3.28.5-3
> > 2018-10-05 22:02:53 status half-installed libebackend1.2-dev:amd64
> 3.28.5-3
> > 2018-10-05 22:02:53 status half-installed libebackend-1.2-10:amd64
> 3.28.5-3
> > 2018-10-05 22:02:53 status half-installed libebackend-1.2-10:amd64
> 3.28.5-3
> > 2018-10-05 22:02:53 status half-installed libedataserverui1.2-dev:amd64
> > 3.28.5-3
> > 2018-10-05 22:02:53 status half-installed libedataserverui1.2-dev:amd64
> > 3.28.5-3
> > 2018-10-05 22:02:53 status half-installed libebook-contacts1.2-dev:amd64
> > 3.28.5-3
> > 2018-10-05 22:02:53 status half-installed libebook-contacts1.2-dev:amd64
> > 3.28.5-3
> > 2018-10-05 22:02:53 status half-installed libedataserver1.2-dev:amd64
> 3.28.5-3
> > 2018-10-05 22:02:54 status half-installed libedataserver1.2-dev:amd64
> 3.28.5-3
> > 2018-10-05 22:02:54 status half-installed libcamel1.2-dev:amd64 3.28.5-3
> > 2018-10-05 22:02:54 status half-installed libcamel1.2-dev:amd64 3.28.5-3
> > 2018-10-05 22:02:54 status half-installed libsecret-common:all 0.18.6-2
> > 2018-10-05 22:02:54

[Git][xorg-team/wayland/wayland-protocols] Pushed new tag wayland-protocols-1.17-1

2018-12-21 Thread Héctor Orón Martínez 
Héctor Orón Martínez pushed new tag wayland-protocols-1.17-1 at X Strike Force 
/ wayland / wayland-protocols

-- 
View it on GitLab: 
https://salsa.debian.org/xorg-team/wayland/wayland-protocols/tree/wayland-protocols-1.17-1
You're receiving this email because of your account on salsa.debian.org.

Bug#910409: wayland-protocols: Can't use second monitor via HDMI

2018-12-21 Thread Hector Oron 
Hello,

On Fri, Oct 05, 2018 at 10:48:33PM -0500, Pavlo Solntsev wrote:
> Package: wayland-protocols
> Version: 1.16-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I am not sure what package name I should use for this report. Today (Oct. 5,
> 22:40T+6) I updated my system debian testing and my external monitor stop
> working. In my xrandr output I see only one monitor
> Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
> XWAYLAND0 connected 1920x1080+0+0 (normal left inverted right x axis y axis)
> 290mm x 170mm
>1920x1080 59.96*+

`wayland-protocols` is not the package you are looking for.
Do you see any relevant messages from kernel? i.e. `/var/log/messages`

> Combination Fn+F8 (switch video mode) doesn't produce anything. I am not sure
> what information I should ptovide. Please guide and I will send you info. You
> can contact me directly if it helps: p.sun.fun at gmail dot com.
> 
> The following packages were upgraded:
> 2018-10-05 22:02:49 install libcamel-1.2-62:amd64  3.30.1-1
> 2018-10-05 22:02:49 status half-installed libcamel-1.2-62:amd64 3.30.1-1

Why do you have half-installed packages? Can you fully upgrade your system?

> 2018-10-05 22:02:49 status half-installed evolution-plugin-bogofilter:amd64
> 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugin-bogofilter:amd64
> 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugin-pstimport:amd64
> 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugin-pstimport:amd64
> 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugins:amd64 3.28.5-1
> 2018-10-05 22:02:49 status half-installed evolution-plugins:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed evolution:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed evolution:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed libevolution:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed libevolution:amd64 3.28.5-1
> 2018-10-05 22:02:50 status half-installed evolution-data-server:amd64 3.28.5-3
> 2018-10-05 22:02:51 status half-installed evolution-data-server:amd64 3.28.5-3
> 2018-10-05 22:02:51 status installed libedata-cal-1.2-28:amd64 3.28.5-3
> 2018-10-05 22:02:51 status half-installed libedata-cal-1.2-28:amd64 3.28.5-3
> 2018-10-05 22:02:51 status not-installed libedata-cal-1.2-28:amd64 
> 2018-10-05 22:02:51 status half-installed libecal1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:51 status half-installed libecal1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libecal-1.2-19:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libecal-1.2-19:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libebook-1.2-19:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libebook-1.2-19:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libedata-book1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libedata-book1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libedata-book-1.2-25:amd64 3.28.5-3
> 2018-10-05 22:02:52 status half-installed libedata-book-1.2-25:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebackend1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebackend1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebackend-1.2-10:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebackend-1.2-10:amd64 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libedataserverui1.2-dev:amd64
> 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libedataserverui1.2-dev:amd64
> 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebook-contacts1.2-dev:amd64
> 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libebook-contacts1.2-dev:amd64
> 3.28.5-3
> 2018-10-05 22:02:53 status half-installed libedataserver1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:54 status half-installed libedataserver1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:54 status half-installed libcamel1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:54 status half-installed libcamel1.2-dev:amd64 3.28.5-3
> 2018-10-05 22:02:54 status half-installed libsecret-common:all 0.18.6-2
> 2018-10-05 22:02:54 status half-installed libsecret-common:all 0.18.6-2
> 2018-10-05 22:02:54 status half-installed libsecret-1-dev:amd64 0.18.6-2
> 2018-10-05 22:02:54 status half-installed libsecret-1-dev:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed libsecret-1-0:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed libsecret-1-0:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed gir1.2-secret-1:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed gir1.2-secret-1:amd64 0.18.6-2
> 2018-10-05 22:02:55 status half-installed gir1.2-ebookcontacts-1.2:amd64
> 3.28.5-3
> 2018-10-05 22:02:55 status half-installed gir1.2-ebookcontacts-1.2:amd64
> 3.28.5-3
> 2018-10-05 22:02:55 status half-installed gir1.2-edataserverui-1.2:amd64
> 3.28.5-3
> 2018-10-05 22:02:55 status half-installed

mesa_18.2.7-2_source.changes ACCEPTED into unstable

2018-12-21 Thread Debian FTP Masters 



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 21 Dec 2018 09:22:16 +0100
Source: mesa
Binary: libxatracker2 libxatracker-dev libd3dadapter9-mesa 
libd3dadapter9-mesa-dev libgbm1 libgbm-dev libegl-mesa0 libegl1-mesa 
libegl1-mesa-dev libwayland-egl1-mesa libgles2-mesa libgles2-mesa-dev 
libglapi-mesa libglx-mesa0 libgl1-mesa-glx libgl1-mesa-dri libgl1-mesa-dev 
mesa-common-dev libosmesa6 libosmesa6-dev mesa-va-drivers mesa-vdpau-drivers 
mesa-vulkan-drivers mesa-opencl-icd
Architecture: source
Version: 18.2.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Emilio Pozuelo Monfort 
Description:
 libd3dadapter9-mesa - state-tracker for Direct3D9
 libd3dadapter9-mesa-dev - state-tracker for Direct3D9 -- development files
 libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library
 libegl1-mesa - transitional dummy package
 libegl1-mesa-dev - free implementation of the EGL API -- development files
 libgbm-dev - generic buffer management API -- development files
 libgbm1- generic buffer management API -- runtime
 libgl1-mesa-dev - free implementation of the OpenGL API -- GLX development 
files
 libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules
 libgl1-mesa-glx - transitional dummy package
 libglapi-mesa - free implementation of the GL API -- shared library
 libgles2-mesa - transitional dummy package
 libgles2-mesa-dev - free implementation of the OpenGL|ES 2.x API -- 
development files
 libglx-mesa0 - free implementation of the OpenGL API -- GLX vendor library
 libosmesa6 - Mesa Off-screen rendering extension
 libosmesa6-dev - Mesa Off-screen rendering extension -- development files
 libwayland-egl1-mesa - transitional dummy package
 libxatracker-dev - X acceleration library -- development files
 libxatracker2 - X acceleration library -- runtime
 mesa-common-dev - Developer documentation for Mesa
 mesa-opencl-icd - free implementation of the OpenCL API -- ICD runtime
 mesa-va-drivers - Mesa VA-API video acceleration drivers
 mesa-vdpau-drivers - Mesa VDPAU video acceleration drivers
 mesa-vulkan-drivers - Mesa Vulkan graphics drivers
Changes:
 mesa (18.2.7-2) unstable; urgency=medium
 .
   * Temporarily disable libsensors support to bootstrap with libsensors5.
Checksums-Sha1:
 3402f4540cd96c8649592fb0a15edc30ef8285ae 5055 mesa_18.2.7-2.dsc
 916a26ff5b31bf49fa70ac433b6cf0287e0d6249 19627919 mesa_18.2.7.orig.tar.gz
 6e711439a6f36e2f6d9688923ee0ebe382417780 101215 mesa_18.2.7-2.diff.gz
 86315dab4c9401f725fc3c55e4352f9b2aa865f4 9201 mesa_18.2.7-2_source.buildinfo
Checksums-Sha256:
 494313d8b6416e0a7401ff17cf0cb503a8fc8b5c6722656b148ba94e777c2090 5055 
mesa_18.2.7-2.dsc
 092351cfbcd430ec595fbd3a3d8d253fd62c29074e1740d7198b00289ab400f8 19627919 
mesa_18.2.7.orig.tar.gz
 95f6ae51522ffdcd708afd23bd7c2241f5a4743d35fa26310bf220103e863c56 101215 
mesa_18.2.7-2.diff.gz
 82b4279d6d9ae5319fee7dfb862e2cd9438da104ca1ddeb715eb73163a99bc70 9201 
mesa_18.2.7-2_source.buildinfo
Files:
 86edcc05b94a58bd39a1423996a4105c 5055 graphics optional mesa_18.2.7-2.dsc
 6da03050077d073bfee765ae330bc2d5 19627919 graphics optional 
mesa_18.2.7.orig.tar.gz
 8c3778c30157a65c6cf7806215e04c53 101215 graphics optional mesa_18.2.7-2.diff.gz
 63ba340ef3987d9947367cd239704d19 9201 graphics optional 
mesa_18.2.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEcJymx+vmJZxd92Q+nUbEiOQ2gwIFAlwcotgACgkQnUbEiOQ2
gwKIpQ/9H9GdbUi2uwzC7PXxh6p70/dmElcQAmGEYWtGtf/eJmXit5P6QFeZ1inb
QmYVqNHQMXcA87yyWNLQv6n8iDo+lJ+teiczYeq11JzMMIDChanWxQRgnz5kkdbg
Nt7poNtGD8vbRNelpeL/RpUbuYfsVUIxMO3+ZZEmsGOTGQfud/nRanhdy0Ae5bGW
4ze2yksHR6nIY6TvtppqLhEEB1qlbhtBW4E7cgBKQbF2y77UA4VlvA91ODArlQtM
alIp/zX0ffvUv2QmOQuN4U27fm/03Grdntzox9rSN7Hn6IeYIuC4KXgoVQi6jgds
eUzD1jMf+hCHLL+ISYi6OdH5A1jXQwpC3Qj6IXVd1gf1X75ixJgd5bobaJm1IY4r
tgw7eoyqUqf6p/t1b8KactRg8i8k7221HNtsWOWBJkEMmpcdR9lxOGPvWxfmvnLg
8kXSzSPbQ7zaZujeQ2Y0A86HIm5YC2mnox1Q3hnbTtfLLCarVA4Mm8DCiZkKZT2z
F82Ubz+AnyHGUk2n65iexKxcblxjq/GaDQllHJTebVu/agUP2TljFc6I1eX7wRfU
bzVD7JYzUKmO6QtMhCZwIKbIi5kDumfBsaemPn1iDDAkVQeBj3ivGuhikqJhIZ87
xJZ5JXvQ88NLmkhwEnOC87jHo1KDn0Db86dUL3TnVVe7HY9Atx0=
=eNqA
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of mesa_18.2.7-2_source.changes

2018-12-21 Thread Debian FTP Masters 
mesa_18.2.7-2_source.changes uploaded successfully to localhost
along with the files:
  mesa_18.2.7-2.dsc
  mesa_18.2.7.orig.tar.gz
  mesa_18.2.7-2.diff.gz
  mesa_18.2.7-2_source.buildinfo

Greetings,

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

[Git][xorg-team/lib/mesa][debian-unstable] 2 commits: Temporarily disable libsensors support

2018-12-21 Thread Emilio Pozuelo Monfort 
Emilio Pozuelo Monfort pushed to branch debian-unstable at X Strike Force / lib 
/ mesa


Commits:
dce28f0e by Emilio Pozuelo Monfort at 2018-12-21T07:57:50Z
Temporarily disable libsensors support

- - - - -
24a0385b by Emilio Pozuelo Monfort at 2018-12-21T08:22:24Z
Release to sid

- - - - -


3 changed files:

- debian/changelog
- debian/control
- debian/rules


Changes:

=
debian/changelog
=
@@ -1,3 +1,9 @@
+mesa (18.2.7-2) unstable; urgency=medium
+
+  * Temporarily disable libsensors support to bootstrap with libsensors5.
+
+ -- Emilio Pozuelo Monfort   Fri, 21 Dec 2018 09:22:16 +0100
+
 mesa (18.2.7-1) unstable; urgency=medium
 
   * New upstream release.


=
debian/control
=
@@ -15,7 +15,7 @@ Build-Depends:
  libx11-dev,
  libxxf86vm-dev,
  libexpat1-dev,
- libsensors4-dev [!hurd-any],
+# libsensors4-dev [!hurd-any],
  libxfixes-dev,
  libxdamage-dev,
  libxext-dev,


=
debian/rules
=
@@ -120,7 +120,7 @@ else
confflags_GALLIUM += --enable-vdpau
confflags_GALLIUM += --enable-va
confflags_GALLIUM += --enable-gallium-extra-hud
-   confflags_GALLIUM += --enable-lmsensors
+#  confflags_GALLIUM += --enable-lmsensors
with_libva = ,libva
 endif
 



View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/compare/11599bb5107bd7677aae93f38e6b72d903481765...24a0385ba23bd2ceb00c6c2d80a913026afb07f2

-- 
View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/compare/11599bb5107bd7677aae93f38e6b72d903481765...24a0385ba23bd2ceb00c6c2d80a913026afb07f2
You're receiving this email because of your account on salsa.debian.org.

[Git][xorg-team/lib/mesa] Pushed new tag mesa-18.2.7-2

2018-12-21 Thread Emilio Pozuelo Monfort 
Emilio Pozuelo Monfort pushed new tag mesa-18.2.7-2 at X Strike Force / lib / 
mesa

-- 
View it on GitLab: 
https://salsa.debian.org/xorg-team/lib/mesa/tree/mesa-18.2.7-2
You're receiving this email because of your account on salsa.debian.org.