Your message dated Sat, 10 Feb 2018 23:09:49 -0500
with message-id
<CANTw=mohhu6gdupzf+ggqthizkuhvmg0cqca+j0p7bwt92b...@mail.gmail.com>
and subject line Re: Bug#833102: chromium: Chromium 52 (gtk+3 issue) does not
honor gtk-key-theme
has caused the Debian Bug report #833102,
regarding chromium: Chromium 52 (gtk+3 issue) does not honor gtk-key-theme
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.)
--
833102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 52.0.2743.82-4
Severity: important
Since 52.0.2743.82-3 chromium uses gtk+3 backend. But now it doesn't honor gtk-
key-theme as the previous gtk+2 backend (or any other gtk+ program).
How to reproduce:
* set gtk-key-theme to Emacs.
* open a new tab and go to a search engine.
* write some text on the address bar or the search text box.
* Press CTRL+W.
What it does:
* Close the page.
What it should to:
* Delete the word on the left of the cursor.
Severity important because for me, and probably other people too, some combos
like, for example, CTRL+W and CTRL+U are build into muscle memory and closing
the tab every time we edit a text box inside a page or the address bar is
frustrating and renders the browser unusable.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (800, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-rc4-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to it_IT.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-2
ii libcairo2 1.14.6-1+b1
ii libcups2 2.1.4-4
ii libdbus-1-3 1.10.8-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-9
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-0 2.48.1-2
ii libgnome-keyring0 3.12.0-1+b1
ii libgtk-3-0 3.20.6-2
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-9
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 1.07.4-1
Versions of packages chromium suggests:
ii chromium-l10n 52.0.2743.82-4
--- End Message ---
--- Begin Message ---
Chromium for stretch was released with the gtk2 backend, so it was not
a problem there. The unstable build is back to gtk3, but this should
no longer be a problem since upstream shares a lot more code between
backends now. Please reopen if that is not the case.
Best wishes,
Mike
--- End Message ---
