Hi,
another thing I noticed since F28 upgrade is what I would best describe as "hickups".
Sometimes the mouse pointer hangs for a fraction of a second - just enough to notice it.
Sometimes the keyboard repeats the last stroke for 3 to 5 times, which sometimes is quite anoying - eg. when Ctrl-W a browser tab and finding 5 tabs closed instead.
Did anyone else see this?
Funny! It just happened again! This is journald:
Mai 08 14:51:07 4delsthubner02 org.gnome.Shell.desktop[2058]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mai 08 14:51:07 4delsthubner02 org.gnome.Shell.desktop[2058]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mai 08 14:51:07 4delsthubner02 org.gnome.Shell.desktop[2058]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mai 08 14:51:09 4delsthubner02 gnome-shell[2058]: Object Shell.GenericContainer (0x56008a74b5a0), has been already finalized. Impossible to get any property from it. Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: == Stack trace for context 0x5600882e01f0 == Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #0 0x7ffddbedf7a0 I resource:///org/gnome/shell/ui/tweener.js:73 (0x7fa043ec7cd0 @ 9) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #1 0x7ffddbedf840 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7fa043ec7f78 @ 36) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #2 0x7ffddbedf8e0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7fa043ec7de0 @ 52) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #3 0x7ffddbee0850 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fa043ed2918 @ 54) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #4 0x7ffddbee09a0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fa043ed29a0 @ 1626) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #5 0x7ffddbee0a50 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fa043ed2a28 @ 100) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #6 0x7ffddbee0ae0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fa043ed2ab0 @ 10) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #7 0x7ffddbee0b60 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7fa043ecff78 @ 386) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #8 0x7ffddbee0c10 b resource:///org/gnome/shell/ui/tweener.js:207 (0x7fa043ecf5e8 @ 159) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #9 0x7ffddbee0c80 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa043eb5de0 @ 71) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #10 0x7ffddbee0c80 I resource:///org/gnome/shell/ui/tweener.js:182 (0x7fa043ecf560 @ 15) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: == Stack trace for context 0x5600882e01f0 == Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #0 0x7ffddbedf7a0 I resource:///org/gnome/shell/ui/tweener.js:80 (0x7fa043ec7cd0 @ 82) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #1 0x7ffddbedf840 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7fa043ec7f78 @ 36) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #2 0x7ffddbedf8e0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7fa043ec7de0 @ 52) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #3 0x7ffddbee0850 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fa043ed2918 @ 54) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #4 0x7ffddbee09a0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fa043ed29a0 @ 1626) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #5 0x7ffddbee0a50 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fa043ed2a28 @ 100) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #6 0x7ffddbee0ae0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fa043ed2ab0 @ 10) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #7 0x7ffddbee0b60 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7fa043ecff78 @ 386) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #8 0x7ffddbee0c10 b resource:///org/gnome/shell/ui/tweener.js:207 (0x7fa043ecf5e8 @ 159) Mai 08 14:51:09 4delsthubner02 gnome-shell[2058]: Object Shell.GenericContainer (0x56008a74b5a0), has been already finalized. Impossible to set any property to it. Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #9 0x7ffddbee0c80 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa043eb5de0 @ 71) Mai 08 14:51:09 4delsthubner02 org.gnome.Shell.desktop[2058]: #10 0x7ffddbee0c80 I resource:///org/gnome/shell/ui/tweener.js:182 (0x7fa043ecf560 @ 15)
Thanks, Stefan
Data Tue, 8 May 2018 14:55:16 +0200 Stefan Hübner via users users@lists.fedoraproject.org napisał(a):
Hi,
another thing I noticed since F28 upgrade is what I would best describe as "hickups".
Sometimes the mouse pointer hangs for a fraction of a second - just enough to notice it.
Sometimes the keyboard repeats the last stroke for 3 to 5 times, which sometimes is quite anoying - eg. when Ctrl-W a browser tab and finding 5 tabs closed instead.
Did anyone else see this?
I do. I have a laptop with 2 core amd cpu (really slow for 2018 standards) and sometimes key stroke is registering twice or more. It is especially inconvenient while typing password when unlocking the desktop. I start to type, monitor wakes up, password screen rolls up and my second letter is getting registered 4 times by the time animation is over.
I also have to release T very quickly when opening new terminal tabs with ctrl+shift+T shortcut. Otherwise I have 10 of them.
Mouse pointer also hangs, or registers only vertical movement, when CPU is busy.
I have had similar experience which was resolved in the Mouse/Keyboard setup for the system to turn down the sensitivity. The upgrade will sometimes reset to very sensitive settings for some reason and a quick adjustment cleared up the issue. May be worth a look if you have not already checked.
-- Fred
Data Fri, 11 May 2018 00:01:44 -0700 fred roller fredroller66@gmail.com napisał(a):
I have had similar experience which was resolved in the Mouse/Keyboard setup for the system to turn down the sensitivity. The upgrade will sometimes reset to very sensitive settings for some reason and a quick adjustment cleared up the issue. May be worth a look if you have not already checked.
Thanks. I have mouse sensitivity at middle, but I indeed changed keyboard repeat rate in dconf. Default setting is way too slow for me.
Allegedly, on or about 11 May 2018, Łukasz Posadowski sent:
I have mouse sensitivity at middle, but I indeed changed keyboard repeat rate in dconf. Default setting is way too slow for me.
Just out of curiosity, what do people use keyboard repeat for?
I can't see any point in being able to repeatedly type a string of letters, but it's useful in cursoring around. Maybe it's time that keyboard repeating was made more intelligent, and only repeats some (user) selected keys. Games that make use of key repeat for sustained fire, for instance, could reconfigure those particular keys during the game, or do a raw key read (which seems more practical).
On Fri, May 11, 2018 at 11:11 PM, Tim via users < users@lists.fedoraproject.org> wrote:
Allegedly, on or about 11 May 2018, Łukasz Posadowski sent:
I have mouse sensitivity at middle, but I indeed changed keyboard repeat rate in dconf. Default setting is way too slow for me.
Just out of curiosity, what do people use keyboard repeat for?
I can't see any point in being able to repeatedly type a string of letters, but it's useful in cursoring around. Maybe it's time that keyboard repeating was made more intelligent, and only repeats some (user) selected keys. Games that make use of key repeat for sustained fire, for instance, could reconfigure those particular keys during the game, or do a raw key read (which seems more practical).
mostly backspace and delete and other non-char functions. Prob dates back to easier to set any key pulse as a whole than being able to distinguish specific key strokes and combination strokes. Pretty sure there is a whole discussion on the pros and cons for changing the status quo on the issue.
Tim:
Just out of curiosity, what do people use keyboard repeat for?
I can't see any point in being able to repeatedly type a string of letters, but it's useful in cursoring around. Maybe it's time that keyboard repeating was made more intelligent, and only repeats some (user) selected keys.
fred roller:
mostly backspace and delete and other non-char functions. Prob dates back to easier to set any key pulse as a whole than being able to distinguish specific key strokes and combination strokes. Pretty sure there is a whole discussion on the pros and cons for changing the status quo on the issue.
It's a shame keyboards weren't built like the old IBM Selectrix typewriters. Some keys repeated, if you pressed them in harder, such as underline, space, etc. But every key only fired once if you normally pressed them once. Keys that had no point in being repeatable, such as most of the alphabet, couldn't repeat.
Data Sat, 12 May 2018 15:41:14 +0930 Tim via users users@lists.fedoraproject.org napisał(a):
Allegedly, on or about 11 May 2018, Łukasz Posadowski sent:
I have mouse sensitivity at middle, but I indeed changed keyboard repeat rate in dconf. Default setting is way too slow for me.
Just out of curiosity, what do people use keyboard repeat for?
To play Nethack twice as fast. :)
-
fred roller -
Stefan Hübner -
Tim -
Łukasz Posadowski