Tyvm, this patch indeed seems to solve the problem on top of mutter-45.5
#888 (closed) seems indeed to be OG issue on this, and 46 is likely to have it fixed. Not sure about backports yet.
Can this MR also help 45, and maybe earlier? People are still living with I think the same issue daily as evidenced by #2750 (closed) deemed fixed, but it really wasn't (or regressed later) #2750 (comment 2029430)
My MX Ergo has a "Precision" scroll mode button on the top. After accidentally hitting it sometimes, I've found myself with very similar thoughts to issue opener. Are you sure your MX mouse is not in Precision mode?
https://www.logitech.com/en-us/products/mice/mx-ergo-wireless-trackball-mouse.htm
OK good to know I'm not alone. It's quite a work-disruptive bug, as you expect to start writing code into IntelliJ, but instead previously active browser window (and keyboard-ready web-apps these days) is now receiving a bunch of unintended keyboard commands
I think I'm still seeing this on mutter-45.2, with IntelliJ PhpStorm.
Focus seems to intermittently fail to follow mouse to IntelliJ window, unless I specifically click in native Wayland window beforehand.
Intermittently means in some unclear circumstances clickless focus transition does work correctly, but most of the time it doesn't.
I've managed to reproduce this both on dual monitors and single (large) monitor.
Seems to work fine on Gentoo 45.2
Landed here from salty beaches of https://medium.com/@fulalas/gnome-mess-is-not-an-accident-4e301032670c great salty entertainment!
This supposedly helps legitimize email https://support.google.com/a/answer/10911320?sjid=16937205389643650192-EU
When you see a blue checkmark next to emails in Gmail, it means that the sender has verified that they own the email address and brand logo.
Whoop, super exciting.
I've found my outgoing filter strategy only works partially, as in
I will test a 3.49.1+ build asap!
Yeah, looking for this functionality on every shell crash or system reboot for Slack and Mattermost (single-window apps).
Subscribed to dependencies, thanks for opening the discussion here.
Ah glad to see this already fixed. Also crashed 44 today when accidentally dragging a Firefox tab into a new window.
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 meta_wayland_compositor_get_context (compositor=0x0) at ../mutter-44.0/src/wayland/meta-wayland.c:863
863 ../mutter-44.0/src/wayland/meta-wayland.c: No such file or directory.
[Current thread is 1 (Thread 0x7fedae46b540 (LWP 1936))]
warning: Missing auto-load script at offset 0 in section .debug_gdb_scripts
of file /usr/lib64/libmozjs-102.so.0.
Use `info auto-load python-scripts [REGEXP]' to list them.
@(gdb) bt
#0 meta_wayland_compositor_get_context (compositor=0x0) at ../mutter-44.0/src/wayland/meta-wayland.c:863
#1 0x00007fedb1f4330a in display_from_offer (offer=0x55baa888ba70) at ../mutter-44.0/src/wayland/meta-wayland-data-offer.c:47
#2 destroy_data_offer (resource=<optimized out>) at ../mutter-44.0/src/wayland/meta-wayland-data-offer.c:240
#3 0x00007fedb025bed7 in () at /usr/lib64/libwayland-server.so.0
#4 0x00007fedb025c5ae in wl_resource_destroy () at /usr/lib64/libwayland-server.so.0
#5 0x00007fedb139abbd in () at /usr/lib64/libffi.so.7
#6 0x00007fedb139a129 in () at /usr/lib64/libffi.so.7
#7 0x00007fedb0261696 in () at /usr/lib64/libwayland-server.so.0
#8 0x00007fedb025cba7 in () at /usr/lib64/libwayland-server.so.0
#9 0x00007fedb025f802 in wl_event_loop_dispatch () at /usr/lib64/libwayland-server.so.0
#10 0x00007fedb1f3f227 in wayland_event_source_dispatch (base=<optimized out>, callback=<optimized out>, data=<optimized out>) at ../mutter-44.0/src/wayland/meta-wayland.c:114
#11 0x00007fedb232a5b9 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#12 0x00007fedb232aaf8 in () at /usr/lib64/libglib-2.0.so.0
#13 0x00007fedb232adaf in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#14 0x00007fedb1ed3a25 in meta_context_run_main_loop (context=context@entry=0x55baa0f863d0, error=error@entry=0x7fffc6b82ea0) at ../mutter-44.0/src/core/meta-context.c:482
#15 0x000055ba9fc8f98f in main (argc=<optimized out>, argv=<optimized out>) at ../gnome-shell-44.0/src/main.c:663
@(gdb)
Thanks for looking into it further
Curiously, I merged 3.5.0 release on Gentoo, and still ran into an infinite loop of something that has this issue title fingerprint.
Even more surprising, tracker went to index a git worktree
directory that has a .git
entry in it. Is it only checking for .git
directory? Because in a linked worktree, .git
is a file containing a path to the main worktree, and this could be a separate Tracker bug.
apr 10 17:06:48 papaya tracker-extract[11750]: Failed to update ignored file 'file:///home/leho/Documents/packages.git/hbd-institute-theme/images/layouts/1c.png': Subject file:///home/leho/Documents/packages.git/hbd-institute-theme/images/layouts/1c.png is not is not a nfo:FileDataObject, cannot have property `tracker:extractorHash'
Fortunately, Carlos' SPARQL query seems to have eliminated the problem
Is there any configuration available to trigger menu bar display only for Alt+mnemonic combo?
Alternatively, is there a way to delay Alt-only reaction?
Menu bar shifting layout for Alt+c (search field) is starting to feel aggravating.
I'll have to start a new build to check that. Itmw
I've seen this before through the years, but just ran into it again on Gnome 44, Intel iris
driver. It seemed to trigger with a short freeze describe above, when I tried to open Pano clipboard manager with Super+Shift+V.
I can confirm Gnome Tweaks > Fonts helps: any change of either Hinting, or Antialiasing, they both help revive glyph display. Whatever mode was selected, let's say "Hinting: Medium", seems to stay broken.
Will explore Mesa build issues next, but good to know there's a workaround.
[leho:~] $ qlist -IU mesa
media-libs/mesa X abi_x86_64 cpu_flags_x86_sse2 gles2 proprietary-codecs video_cards_intel wayland zstd
https://www.reddit.com/r/gnome/comments/z91lzs/my_terminal_is_not_switching_to_dark_mode_when_i/iyerv7l?utm_medium=android_app&utm_source=share&context=3 describes a workaround
You can also install this extension to sync the color scheme with unsupporting GTK3 apps: https://extensions.gnome.org/extension/4998/legacy-gtk3-theme-scheme-auto-switcher/
Curious, why was this issue closed with no visible alternatives listed? Did the initiative die?
Ah I see. So this could be a duplicate of #7870 (closed), until we find a way to shortcut this in gtk3.
Gnome has a global Dark Style menu item since version 42.
Gnome Console aka kgx
already implements this preference, so a perfectly working example exists.
Unfortunately it has its own demons with idle CPU churn, so here I am, looking to get Terminal upgraded as well.