You are not logged in.
i think it was started after i updated to gnome 49.
by Del key i mean this key:
https://imgur.com/a/tr9woFb
on the other hand, the Delete key (near End and Insert keys) is working without a problem (on google chrome and on everything else).
in firefox or in emacs or in Telegram Desktop or in any other text program i tried, the Del key is working without a problem.
Last edited by andav (2025-09-30 18:12:47)
Offline
https://en.wikipedia.org/wiki/Keypad
The other keypad keys work fine?
Is chromium an Xwayland client?
https://wiki.archlinux.org/title/Waylan … plications
=> https://wiki.archlinux.org/title/Chromi … er_Wayland (ignore the symptoms)
Offline
https://en.wikipedia.org/wiki/Keypad
The other keypad keys work fine?
yes.
i opened gemini in google chrome and in the prompt i entered a *lot* of text and i can confirm that the Home, Pg Up, Pg Dn End / * + - and NumLock, and the arrows are working in this text prompt.
the `Ins` key doesnt work (but i dont give a... :-)).
Is chromium an Xwayland client?
https://wiki.archlinux.org/title/Waylan … plications
=> https://wiki.archlinux.org/title/Chromi … er_Wayland (ignore the symptoms)
yes.
if i understand you well.
i installed xorg-xeyes, opened it on top of google chrome and the eyes are moving when my mouse move near them.
about this bug:
https://wiki.archlinux.org/title/Chromi … er_Wayland
i opened chrome from terminal and i don't get this text:
[333310:333425:0919/121130.103852:ERROR:gpu_channel.cc(502)] Buffer Handle is null.
[333341:18:0919/121130.104000:ERROR:shared_image_interface_proxy.cc(134)] Buffer handle is null. Not creating a mailbox from it.
[333310:333425:0919/121130.137149:ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
chrome is opened *without* any text output to the terminal
Offline
gnore the symptoms
The point was to highlight the condition and explain how to get a native wayland cilent.
The test the key there.
Offline
i dont understand your second line.
also, do i need to add this:
--disable-gpu-memory-buffer-video-frames
to the file:
~/.config/chromium-flags.conf
[EDIT]
i added the line to that file, log out and login again but problem still exist.
Last edited by andav (2025-09-30 19:23:56)
Offline
must be started with the explicit command line flag --ozone-platform=wayland
Offline
The linked wiki paragraph wrote:must be started with the explicit command line flag --ozone-platform=wayland
output from terminal:
google-chrome-stable --ozone-platform=wayland
Created TensorFlow Lite XNNPACK delegate for CPU.
[50094:50121:0930/223414.475320:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
Fontconfig error: Cannot load default config file: No such file: (null)
[50094:50121:0930/223443.437214:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
(and Del key still doesn't work)
Offline
Do xeyes still track the window?
(nb. that chromium won't start a new instance but just open a new window or tab if there's a running one)
Also do you get the same behavior w/ chromium (instead of google chrome)?
Offline
Do xeyes still track the window?
Sorry for that i forgot to check.
i did:
pkill -9 chrome (it closed chrome immediatelly)
then in terminal i did:
google-chrome-stable --ozone-platform=wayland
the xeyes still working on top of chrome.
i also installed chromium and the problem exist also there.
even if i open it in terminal like this:
chromium --ozone-platform=wayland
problem still exist.
Offline
But chromium turns into a native wayland window?
For a cross-test you could also run xterm and see how the key behaves there (ie. is this an xwayland or an electron problem) resp. "xev -event keyboard" will also tell you what key xwayland registers there (apparently not a dot or comma?)
Offline
But chromium turns into a native wayland window?
no, if i understand well.
i opened xorg-xeyes on top of chromium, and the eyes are moving.
For a cross-test you could also run xterm and see how the key behaves there (ie. is this an xwayland or an electron problem) resp
in xterm the Del key is working
after:
`xev -event keyboard` and pressing Del, i get:
KeyRelease event, serial 28, synthetic NO, window 0xa00001,
root 0x402, subw 0x0, time 1025611, (-11,47), root:(860,575),
state 0x0, keycode 91 (keysym 0xff9f, KP_Delete), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Last edited by andav (2025-09-30 20:11:22)
Offline
1. apparently not Xwayland then
2. are you sure this is gnome? 49?
loginctl session-status
3. When enabling the numlock, does the KP_Separator work? Does the key work in the url bar (ie. is the problem limited to the input field)
Offline
1. apparently not Xwayland then
2. are you sure this is gnome? 49?loginctl session-status
3. When enabling the numlock, does the KP_Separator work? Does the key work in the url bar (ie. is the problem limited to the input field)
2. yes i'm on gnome
loginctl session-status
3 - parosh (1000)
Since: Tue 2025-09-30 22:48:25 IDT; 27min ago
State: active
Leader: 1384 (gdm-session-wor)
Seat: seat0; vc2
TTY: tty2
Remote: no
Service: gdm-password
Type: wayland
Class: user
Idle: no
Unit: session-3.scope
├─1384 "gdm-session-worker [pam/gdm-password]"
├─1476 /usr/lib/gdm-wayland-session /usr/bin/gnome-session
└─1482 /usr/lib/gnome-session-init-worker gnome
ספט 30 22:48:25 Mamadoosh systemd[1]: Started Session 3 of User parosh.
ספט 30 22:48:25 Mamadoosh gnome-session-i[1482]: Starting GNOME session target: gnome-session-w
ayland@gnome.target
and also from gnome settings:
https://imgur.com/a/kBVw4UE
3. if the NumLock is on, i get period (.) when i press the Del key.
and yes, i get period (.) also in the address bar, in google chrome.
(and i get period (.) also in the text box, where i write this message :-))
Last edited by andav (2025-09-30 20:26:15)
Offline
and yes, i get period (.) also in the address bar, in google chrome.
Ok, but does kp_delete work in the URL bar?
https://wiki.archlinux.org/title/Chromi … nd_support
chromium --ozone-platform=wayland --gtk-version=4 --disable-gtk-ime
It's pretty wild that chromium would not run as native wayland client, does xwininfo detect it?
Offline
and yes, i get period (.) also in the address bar, in google chrome.
Ok, but does kp_delete work in the URL bar?
no.
nothing has changed.
Del key doesn't work (also) in the address bar, when num lock is off (in chrome or chromium).
https://wiki.archlinux.org/title/Chromi … nd_support
chromium --ozone-platform=wayland --gtk-version=4 --disable-gtk-ime
if i open chromium like that, problem still exist.
also the eyes are moving when i put them ot top of chromium.
It's pretty wild that chromium would not run as native wayland client, does xwininfo detect it?
xwininfo doesnt do a thing:
there is no output in terminal, no matter what app i press with my mouse.
Offline
So it's actually a wayland client.
You could try to reverse this w/ "--ozone-platform=x11" but that's hardly what you want - what brings us to: gnomes fault or electrons fault?
(or "wayland's fault" - because the IME handling is a mess)
Can you try the behavior on a different wayland compositor like weston, sway or hyprland?
You could also try some X11 session (esp. if the key doesn't work on Xwayland!)
Final check: you're not using some custom keymap, are you?
Offline
So it's actually a wayland client.
You could try to reverse this w/ "--ozone-platform=x11" but that's hardly what you want....
if i open chrome like that, the problem is fixed :-)
Can you try the behavior on a different wayland compositor like weston, sway or hyprland?
it's learning a new thing that is a little bit complex to me right now
You could also try some X11 session (esp. if the key doesn't work on Xwayland!)
you mean to make gnome 49 enable x11?
if yes, how do i do that?
if thats not what you meant, can you explain?
Final check: you're not using some custom keymap, are you?
by custom keymap you mean custom keybindings?
if yes, i have some key bindings to open some apps but non of those key bindings using the Del key.
if you mean something strange in the keybaord itself than no.
i'm using input languages: english us and hebrew.
just regular settings i added from inside gnome.
i didn't do anything other than that.
Last edited by andav (2025-10-02 17:18:48)
Offline
if i open chrome like that, the problem is fixed :-)
but that's hardly what you want....
you mean to make gnome 49 enable x11?
if yes, how do i do that?
if thats not what you meant, can you explain?
Gnome 49 is built w/o X11 support - you'd have to compile it yourself - I rather meant sth. like openbox but b/c of the xwayland situation, that's probably moot anyway (we assume the problem doesn't exist w/ X11) and the only remaining test would be
it's learning a new thing that is a little bit complex to me right now
to figure whether it's a gnome problem or an electron problem.
Install weston, you should be able to launch it from GDM.
i'm using input languages: english us and hebrew.
AHA!
Do you get the same problem w/ a single layout (preferably english) - I'm pretty sure I've seen multiple threads involving gnome, multiple keyboard layouts and "doesn't work", "forget", "weird behavior"
But I actually meant a completely custom layout, like english w/ hebrew on shift layer 4+5 or something like that. But that's obviously not the case.
Offline
sorry for the late response.
after installing weston and opening chrome from within weston, problem still exist.
i'm using input languages: english us and hebrew.
AHA!
Do you get the same problem w/ a single layout (preferably english) - I'm pretty sure I've seen multiple threads involving gnome, multiple keyboard layouts and "doesn't work", "forget", "weird behavior"
after removing the hebrew input language so i have only english input (and rebooting), problem still exist.
Offline
So it's not gnome (or the multilayout) but chromium's wayland implementation.
And lo and behold: https://issues.chromium.org/issues/429730008
Offline
So it's not gnome (or the multilayout) but chromium's wayland implementation.
And lo and behold: https://issues.chromium.org/issues/429730008
glad to see it's not just my specific chrome in my specific pc.
thank you very much for all the help!
Offline