Your message dated Tue, 07 Mar 2023 15:09:47 -0500
with message-id <[email protected]>
and subject line Re: chromium: keymap changes with xmodmap after chromium
launches cause problems
has caused the Debian Bug report #989377,
regarding chromium: keymap changes with xmodmap after chromium launches cause
problems
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 [email protected]
immediately.)
--
989377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989377
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 90.0.4430.212-1
Severity: normal
Dear Maintainer,
Thanks for all your work on packaging chromium, I imagine that this
is a big job!
My keyboard lacks an AltGr key, so I use xmodmap to turn my useless
Menu key into an AltGr like so:
setxkbmap dvorak
xmodmap -e 'keycode 135 = Mode_switch' \
-e 'remove mod5 = Mode_switch'
xmodmap -e 'add mod3 = Mode_switch'
I have a script containing the above lines, though sometimes it's
"us" instead of "dvorak".
This worked well for about 5 years.
I'm not sure if it's the setxkbmap or the xmodmap, but when I run
that script _after_ chromium starts, then chromium starts ignoring
my keybinding for the menu key, and I can no longer type accented
characters, because I get a weird menu instead.
If I close chromium and open it up again, it's fixed (I can again
use that key as Mode_switch) until next time I switch to qwerty and
back (and run those xmodmap commands.)
When chromium is bugging, other programs are functioning correctly,
eg I can still type my accented characters with my menu key
remapped to alt-gr in other programs (I tested lowriter, st, atril,
and filezilla).
Thanks!
- Jason
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 90.0.4430.212-1
ii libasound2 1.2.4-1.1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libatomic1 10.2.1-6
ii libatspi2.0-0 2.38.0-4
ii libavcodec58 7:4.3.2-0+deb11u1
ii libavformat58 7:4.3.2-0+deb11u1
ii libavutil56 7:4.3.2-0+deb11u1
ii libc6 2.31-12
ii libcairo2 1.16.0-5
ii libcups2 2.3.3op2-3+deb11u1
ii libdbus-1-3 1.12.20-2
ii libdrm2 2.4.104-1
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.2.10-2
ii libflac8 1.3.3-2
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgbm1 20.3.5-1
ii libgcc-s1 10.2.1-6
ii libglib2.0-0 2.66.8-1
ii libgtk-3-0 3.24.24-4
ii libharfbuzz0b 2.7.4-1
ii libicu67 67.1-6
ii libjpeg62-turbo 1:2.0.6-4
ii libjsoncpp24 1.9.4-4
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.29-1
ii libnss3 2:3.63-1
ii libopenjp2-7 2.4.0-3
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.46.2-3
ii libpng16-16 1.6.37-3
ii libpulse0 14.2-2
ii libre2-9 20210201+dfsg-1
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.2.1-6
ii libvpx6 1.9.0-1
ii libwebp6 0.6.1-2+b1
ii libwebpdemux2 0.6.1-2+b1
ii libwebpmux3 0.6.1-2+b1
ii libx11-6 2:1.7.1-1
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxml2 2.9.10+dfsg-6.7
ii libxrandr2 2:1.5.1-1
ii libxshmfence1 1.3-1
ii libxslt1.1 1.1.34-4
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium recommends:
ii chromium-sandbox 90.0.4430.212-1
Versions of packages chromium suggests:
pn chromium-driver <none>
pn chromium-l10n <none>
pn chromium-shell <none>
Versions of packages chromium-common depends on:
ii libc6 2.31-12
ii libstdc++6 10.2.1-6
ii libx11-6 2:1.7.1-1
ii libxext6 2:1.3.3-1.1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium-common recommends:
ii chromium-sandbox 90.0.4430.212-1
ii dunst [notification-daemon] 1.5.0-1
ii fonts-liberation 1:1.07.4-11
ii libgl1-mesa-dri 20.3.5-1
pn libu2f-udev <none>
ii system-config-printer 1.5.14-1
ii upower 0.99.11-2
Versions of packages chromium-sandbox depends on:
ii libc6 2.31-12
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 15 Feb 2022 18:39:22 -0500 Andres Salomon <[email protected]>
wrote:
> On Wed, 2 Jun 2021 03:17:50 -0400 Jason Woofenden wrote:
> > Package: chromium
> > Version: 90.0.4430.212-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > Thanks for all your work on packaging chromium, I imagine that
this
> > is a big job!
> >
> > My keyboard lacks an AltGr key, so I use xmodmap to turn my
useless
> > Menu key into an AltGr like so:
> >
> > setxkbmap dvorak
> > xmodmap -e 'keycode 135 = Mode_switch' \
> > -e 'remove mod5 = Mode_switch'
> > xmodmap -e 'add mod3 = Mode_switch'
> >
> > I have a script containing the above lines, though sometimes it's
> > "us" instead of "dvorak".
> >
> > This worked well for about 5 years.
> >
> > I'm not sure if it's the setxkbmap or the xmodmap, but when I run
> > that script _after_ chromium starts, then chromium starts ignoring
> > my keybinding for the menu key, and I can no longer type accented
> > characters, because I get a weird menu instead.
> >
> > If I close chromium and open it up again, it's fixed (I can again
> > use that key as Mode_switch) until next time I switch to qwerty
and
> > back (and run those xmodmap commands.)
> >
> > When chromium is bugging, other programs are functioning
correctly,
> > eg I can still type my accented characters with my menu key
> > remapped to alt-gr in other programs (I tested lowriter, st,
atril,
> > and filezilla).
>
>
>
> Hi,
>
> Is this still happening with chromium 98? We've changed a bunch of
> things around the way we build chromium since v90.
>
> Thanks,
>
> Andres
>
I didn't hear back, and we've had a bunch of chromium releases since
then, so I'm going to go ahead and close this. If the bug is still
occurring, please let me know and I'll reopen it.
--- End Message ---
