Debian Bug report logs - #833342
chromium: crashes upon the first keypress in wayland

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Rostislav Pehlivanov <atomnuker@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: chromium: crashes upon the first keypress in wayland

Date: Wed, 03 Aug 2016 10:23:44 +0100

Package: chromium
Version: 52.0.2743.82-4
Severity: important

Dear Maintainer,

Since the switch to GTK3 in unstable Chromium has started to crash
upon the first keypress in Wayland with the following log:

[25511:25511:0803/101959:ERROR:browser_main_loop.cc(283)] GLib-GObject: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display'
[25511:25511:0803/101959:ERROR:browser_main_loop.cc(283)] GLib-GObject: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display'
[25511:25511:0803/101959:ERROR:browser_main_loop.cc(283)] GLib-GObject: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display'
[25511:25511:0803/101959:ERROR:browser_main_loop.cc(283)] GLib-GObject: invalid cast from 'GdkWaylandDisplay' to 'GdkX11Display'

It appears that since GTK3 supports Wayland it's automatically picked as
the backend and since Chromium either hasn't fully stabilized its support for it
or there's a bug the crash happens. Previously with gtk2 Xwayland was always used.
The browser is perfectly usable and stable as long as no actual keys have been pressed, e.g.
navigating with a mouse.

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

Kernel: Linux 4.7.0-custom (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  libasound2           1.1.1-2
ii  libatk1.0-0          2.20.0-1
ii  libavcodec57         7:3.1.1-3
ii  libavformat57        7:3.1.1-3
ii  libavutil55          7:3.1.1-3
ii  libc6                2.23.90+20160725.b898b64-1
ii  libcairo2            1.14.6-1+b1
ii  libcups2             2.1.4-4
ii  libdbus-1-3          1.11.2-1
ii  libexpat1            2.2.0-1
ii  libfontconfig1       2.11.0-6.4
ii  libfreetype6         2.6.3-3+b1
ii  libgcc1              1:6.1.1-10
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0         2.49.4-1
ii  libgnome-keyring0    3.12.0-1+b1
ii  libgtk-3-0           3.21.4-1
ii  libharfbuzz0b        1.2.7-1
ii  libjpeg62-turbo      1:1.5.0-1
ii  libnettle6           3.2-1
ii  libnspr4             2:4.12-2
ii  libnss3              2:3.23-2
ii  libpango-1.0-0       1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpci3              1:3.3.1-1.1
ii  libpulse0            9.0-1.1
ii  libspeechd2          0.8.4-2
ii  libstdc++6           6.1.1-10
ii  libx11-6             2:1.6.3-1
ii  libxcomposite1       1:0.4.4-1
ii  libxcursor1          1:1.1.14-1+b1
ii  libxdamage1          1:1.1.4-2+b1
ii  libxext6             2:1.3.3-1
ii  libxfixes3           1:5.0.2-1
ii  libxi6               2:1.7.6-1
ii  libxml2              2.9.4+dfsg1-1
ii  libxrandr2           2:1.5.0-1
ii  libxrender1          1:0.9.9-2
ii  libxslt1.1           1.1.28-4
ii  libxss1              1:1.2.2-1
ii  libxtst6             2:1.2.2-1+b1
ii  x11-utils            7.7+3
ii  xdg-utils            1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  2.00.1-1

Versions of packages chromium suggests:
pn  chromium-l10n  <none>

-- debconf-show failed

Message #10 received at 833342@bugs.debian.org (full text, mbox, reply):

From: Michael Gilbert <mgilbert@debian.org>

To: 833342@bugs.debian.org, 833342-submitter@bugs.debian.org

Subject: re: chromium: crashes upon the first keypress in wayland

Date: Sat, 6 Aug 2016 21:28:23 -0400

control: severity -1 minor
control: forwarded -1 http://crbug.com/615164

You should be able to work around this by using GDK_BACKEND=x11.

Best wishes,
Mike

Message #22 received at 833342@bugs.debian.org (full text, mbox, reply):

From: Andreas Henriksson <andreas@fatal.se>

To: Michael Gilbert <mgilbert@debian.org>

Cc: 833342@bugs.debian.org

Subject: Re: chromium: crashes upon the first keypress in wayland

Date: Fri, 26 Aug 2016 13:02:58 +0200

Hello Michael Gilbert.

I recently ran into this issue myself...

On Sat, Aug 06, 2016 at 09:28:23PM -0400, Michael Gilbert wrote:
> control: severity -1 minor
> control: forwarded -1 http://crbug.com/615164
> 
> You should be able to work around this by using GDK_BACKEND=x11.

Thanks for this suggestion, but maybe you could make sure chromium
always starts with the x11 backend until using the wayland backend is
considered stable enough?

As you might be aware the overwhelming majority of Debian desktop users
are using GNOME which will go switch to wayland by default for 3.22
which will soon be released and is already being prepared in
experimental. (It was already planned for 3.20 but postponed then.)
As the Debian social contract says our users are our priority I thus
think this bug report deserves a higher severity than minor as the
browser by default is more or less unusable now.

Here's a backtrace fwiw (if nothing else might make it easier for search
engines to index this and help others find this bug report easier):

Thread 1 "chromium" received signal SIGSEGV, Segmentation fault.
0x00007fffefd52200 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
(gdb) bt
#0  0x00007fffefd52200 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#1  0x00007fffefd52b54 in gdk_x11_display_error_trap_push ()
   from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#2  0x00007fffefd715b0 in gdk_x11_window_foreign_new_for_display ()
   from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#3  0x000055555978266d in libgtk2ui::X11InputMethodContextImplGtk2::GdkEventFromNativeEvent(_XEvent* const&) ()
#4  0x000055555978277b in libgtk2ui::X11InputMethodContextImplGtk2::DispatchKeyEvent(ui::KeyEvent const&) [clone .part.61] [clone .constprop.74] ()
#5  0x000055555ab1383d in ui::InputMethodAuraLinux::DispatchKeyEvent(ui::KeyEvent*) ()
#6  0x00005555594fe47f in views::DesktopWindowTreeHostX11::DispatchEvent(_XEvent* const&) ()
#7  0x0000555556ca483c in ui::PlatformEventSource::DispatchEvent(_XEvent*) ()
#8  0x0000555556ca736b in ui::X11EventSource::ExtractCookieDataDispatchEvent(_XEvent*) ()
#9  0x0000555556ca748d in ui::X11EventSource::DispatchXEvents() ()
#10 0x000055555a33decc in ui::(anonymous namespace)::XSourceDispatch(_GSource*, int (*)(void*), void*) ()
#11 0x00007ffff74b15aa in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff74b1950 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff74b19fc in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00005555564fe71a in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) ()
#15 0x00005555564ccd3a in base::RunLoop::Run() ()
#16 0x000055555626022c in ChromeBrowserMainParts::MainMessageLoopRun(int*) ()
#17 0x00005555590a648a in content::BrowserMainLoop::RunMainMessageLoopParts()
    ()
#18 0x0000555558e7354d in content::BrowserMainRunnerImpl::Run() ()
#19 0x0000555558e73431 in content::BrowserMain(content::MainFunctionParams const&) ()
#20 0x000055555646536d in content::ContentMainRunnerImpl::Run() ()
#21 0x00005555564635d1 in content::ContentMain(content::ContentMainParams const&) ()
#22 0x0000555555ff888a in ChromeMain ()
#23 0x00007fffeea74730 in __libc_start_main (main=0x555555ff6200 <main>, 
    argc=7, argv=0x7fffffffdfd8, init=<optimized out>, fini=<optimized out>, 
    rtld_fini=<optimized out>, stack_end=0x7fffffffdfc8)
    at ../csu/libc-start.c:291
#24 0x0000555555ff8739 in _start ()
(gdb) 
(gdb) 
(gdb) 


Regards,
Andreas Henriksson

Message #47 received at 833342@bugs.debian.org (full text, mbox, reply):

From: Andreas Henriksson <andreas@fatal.se>

To: 833342@bugs.debian.org

Subject: chomium 55 on wayland works

Date: Sun, 18 Dec 2016 15:18:52 +0100

Control: fixed -1 55.0.2883.75-2

Hello!

Just wanted to mention that the above version seems to work
just fine in a (GNOME) wayland environment.

This bug report can probably be closed now.

Regards,
Andreas Henriksson

Send a report that this bug log contains spam.