Hello, After upgrading to firefox 113.0.1 (113.0.1-1, 113.0.1-3 and 113.0.1-4), I started noticing significant lags when typing. This happens after a while and it doesn't matter where I'm typing, in the URL bar, in a filed on some web page, in about:config, etc.. The lag can be up to a few tens of seconds. Mouse input and keyboard shortcuts aren't affected. When the characters start to appear, I see these two messages in my system log: May 25 22:01:06 firefox.desktop[4971]: [Parent 4971, Main Thread] WARNING: Process Key Event failed: Timeout was reached.: 'glib warning', file /builddir/build/BUILD/firefox-113.0.1/toolkit/xre/nsSigHandlers.cpp:167 May 25 22:01:06 firefox[4971]: Process Key Event failed: Timeout was reached. They repeat for every delayed key press. Today I've also noticed that when the typing lag is in effect, opening magnet links is also delayed. After I select which program I want to use to open the link, for a while nothing happens. When the link is eventually opened, I get these messages: May 25 22:05:08 firefox.desktop[4971]: [Parent 4971, Main Thread] WARNING: Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.Daemon: Timeout was reached (g-io-error-quark, 24) May 25 22:05:08 firefox.desktop[4971]: : 'glib warning', file /builddir/build/BUILD/firefox-113.0.1/toolkit/xre/nsSigHandlers.cpp:167 May 25 22:05:08 firefox[4971]: Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.Daemon: Timeout was reached (g-io-error-quark, 24) Does any of that provide a hint as to what is happening or am I in for a happy debugging weekend ? :) I am running firefox on X, most of the time using Intel graphics (every time I've encountered the issue).
Can you try Mozilla upstream binnary? https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries Also can you try to downgrade to 112.0? you can download it directly from https://koji.fedoraproject.org/koji/packageinfo?packageID=37 Thanks.
Hi Martin, which of the two would you like me to try first?
I've been running firefox-112.0.2-1.fc38 for the last ~4 hours, no issue whatsoever, nothing in the logs. I'm going to try Mozilla's binary next. Should I go for the Nightly as well?
I can no longer reproduce this. Looking at the time other updates were installed and when the bug last occurred, this was fixed either by the latest ibus or mesa builds. Closing.
I had this happen again today, 10 days since the last time. I cannot figure out what's triggering it, Martin, can you think of anything I could try?
What I'm experiencing resembles a lot the problem in bug #727385. Does this (or the patch in c14) offer any clues?
I had completely forgotten about this, but after all this time, I hit the issue again, now on firefox-115.0-2: Jul 15 00:27:11 firefox.desktop[4490]: [Parent 4490, Main Thread] WARNING: Process Key Event failed: Timeout was reached.: 'glib warning', file /builddir/build/BUILD/firefox-115.0/toolkit/xre/nsSigHandlers.cpp:167 Jul 15 00:27:11 firefox[4490]: Process Key Event failed: Timeout was reached. Would running firefox in gdb produce something useful?