[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#902437: marked as done (xwayland: Firefox crashes Wayland on some web pages)



Your message dated Thu, 16 Aug 2018 10:11:40 +0200
with message-id <7e1d740f-9213-aa44-bbd9-8d0f83f2d25f@debian.org>
and subject line Re: Bug#902437: xwayland: Firefox crashes Wayland on some web pages
has caused the Debian Bug report #902437,
regarding xwayland: Firefox crashes Wayland on some web pages
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 owner@bugs.debian.org
immediately.)


-- 
902437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902437
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: xwayland
Version: 2:1.20.0-2
Severity: important

Dear Maintainer,

My apologies for ruining your day with what looks like a tricky driver
bug. I hate debugging such things, myself.

I'm marking this "important", because the issue makes me not dare to
browse the web: I've had to reboot my system several times a day
lately. If you think it should be a lower severity, please downgrade.

Also, I made a wild guess at which package to report this issue
against, and I am so utterly, comically ignorant of everything in a
modern Debian desktop system that I may have guessed wrongly; please
reassign if so.

I run Debian sid on two different laptops: a Lenovo Thinkpad X220, and
a Lenovo Yoga 900. Both use an Intel graphics card or chip. For the
past week or two, the X220 has been crashing from time to time. I
thought it might be bad memory in the laptop, so I switched to the
Yoga. Then the Yoga started crashing.

After much headbanging and wailing, I've manged to find way to
reproduce the crash. I use Firefox as my web browser, and certain web
pages trigger the crash reproducibly. One such web page is here:

http://johannesbrodwall.com/2018/06/24/forget-about-clean-code-lets-embrace-compassionate-code/

What happens is that Firefox does not render that page, only updates
the page title in the window title, and then becomes unresponsive.
Menus don't react in anyway. i can't close the tab or window with
Ctrl-W, or by clicking on the window close button. After a few more
seconds, the whole desktop stops working, meaning that pressing the
capslock key no longer toggles the LED. The mouse cursor may or may
not work. If it does work, moving it to the top left corner of the
GNOME desktop makes the mouse not work anymore. Also, the desktop does
not do the "whoosh" feature of GNOME where it shows all windows on the
current virtual desktop, and the "dock" on the left side of the
screen.

The machine seems to work otherwise: I can log into it via ssh, and
run commands on the command line. I can restart gdm3 from the ssh
session, but if I log back in, it doesn't work: I get a dark grey
screen, no windows, and nothing else for about half a minute, and then
it's back to the gdm3 login screen. Logging in as a different user
seems to work.

There's nothing new in dmesg output, when the crash happens. I've run
the in-kernel memtest on the Yoga, and it resports no problems. (I've
not bothered to run it on the X220 yet. I can, if it'd be helpful to
you.)

I reconfigured gdm3 on the Yoga to start Xorg instead of Wayland, and
now the web page above works fine in Firefox. No crash.. The webpage
renders fine under Wayland using Chromium.

I am OK with this workaround, but I assume the bug should be fixed if
Wayland is to be the default in Debian. The problem is reproducible
for me. If others can reproduce it, it should be doable on any X220,
which is, or used to be, a common laptop. I will be keeping mine
in storage for a while, so that if there's a need, I can try new
package versions to see if they fix the problem.

Happy hunting.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages xwayland depends on:
ii  libaudit1           1:2.8.3-1
ii  libbsd0             0.9.1-1
ii  libc6               2.27-3
ii  libdrm2             2.4.92-1
ii  libegl1             1.0.0+git20180308-3
ii  libepoxy0           1.4.3-1
ii  libgbm1             18.1.2-1
ii  libgcrypt20         1.8.3-1
ii  libgl1              1.0.0+git20180308-3
ii  libpixman-1-0       0.34.0-2
ii  libselinux1         2.8-1
ii  libsystemd0         239-1
ii  libwayland-client0  1.15.0-2
ii  libxau6             1:1.0.8-1+b2
ii  libxdmcp6           1:1.1.2-3
ii  libxfont2           1:2.0.3-1
ii  libxshmfence1       1.3-1
ii  xserver-common      2:1.20.0-2

xwayland recommends no packages.

xwayland suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On 08/15/2018 12:10 PM, Lars Wirzenius wrote:
> On Tue, 2018-06-26 at 20:10 +0100, Steve McIntyre wrote:
>> Confirmed here on a fresh install of sid on another X220...
> 
> This seems to work on my Yoga laptop now.
> 
Thanks for testing.  I'll assume this was indeed a dupe of #901883 and
close this out now.

Cheers,
Julien

--- End Message ---

Reply to: