Yes, it's fixed. Thanks a lot.
Lorenz
Yes, that certainly seems possible as I mentioned in my initial
report. However, I can exclude the possibility of it being a duplicate
of #813687 after the upgrade to mutter 3.18.3.
Still reproducible but the log messages changed:
> Mar 01 11:53:03 i10pc82 kernel: snd_hda_codec_hdmi hdaudioC0D0: HDMI: ELD buf
> size is 0, force 128
> Mar 01 11:53:03 i10pc82 kernel: snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid
> ELD data byte 0
> Mar 01 11:53:03 i10pc82 /usr/lib/gdm3/gdm-x-
-display-server" (wayland). Maybe these can be
of help?
Cheers
Lorenz
On Tue, Feb 23, 2016 at 2:35 PM, Lorenz Hübschle-Schneider
wrote:
> Package: xwayland
> Version: 2:1.18.1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> sinc
Package: xwayland
Version: 2:1.18.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
since today my machine is no longer lockable, as Xwayland segfaults upon waking
up whenever I lock the screen for more than a few seconds. The precise
criterion for the crash happening
Package: xorg
Version: 1:7.6+6
Severity: important
On a clean install of Debian testing (completely up-to-date as of 10 minutes
ago) on a Thinkpad T420 4180W1H, upon starting an X server, it seems to disable
mouse and keyboard.
The laptop comes with a dual-graphics-card-setup using NVidia's Opti
6 matches
Mail list logo
