On 25/10/2018 19:01, Till Hofmann wrote:
On 10/25/18 4:47 PM, mcatanz...@gnome.org wrote:
On Thu, Oct 25, 2018 at 6:50 AM, Nicolas Mailhot
wrote:
I get the same thing without any special load. System would work fine
for hours and then input would start bugging.
It translates into floods of
On 10/25/18 4:47 PM, mcatanz...@gnome.org wrote:
> On Thu, Oct 25, 2018 at 6:50 AM, Nicolas Mailhot
> wrote:
>> I get the same thing without any special load. System would work fine
>> for hours and then input would start bugging.
>>
>> It translates into floods of keystrokes, or eaten keystroke
Le jeudi 25 octobre 2018 à 18:52 +0200, Alexander Larsson a écrit :
>
> So, the question is what happens to you. Does the compositor hang for
> a bit, and then you get a string of duplicated letters, or is the
> compositor working, and you keep getting new letters displayed over
> time (until you
> basically there's no way for the compositor to
> tell the difference between "the key is being pressed for a long time"
> and "the computer is under such heavy load that the keypress end event
> hasn't arrived from the client yet". Of course it's a bit more
event should have a timestamp when the
libinput ticket
https://bugzilla.redhat.com/show_bug.cgi?id=1643144
tracker miner ticket
https://bugzilla.redhat.com/show_bug.cgi?id=1643186
On Thu, Oct 25, 2018 at 6:05 PM Muayyad AlSadi wrote:
> > This is a very poor bug report because it does not list the hardware
> details of the machine.
On 10/25/2018 06:27 AM, Muayyad AlSadi wrote:
I've a lot of data in my ~/Downloads (many projects, git repos, ...etc.)
That may be a bad idea because Downloads is normally excluded from
backups. Easy to change, but you have to remember to do it.
___
On Thu, Oct 25, 2018 at 6:42 AM Nicolas Mailhot
wrote:
> I get the same thing without any special load. System would work fine
> for hours and then input would start bugging.
>
> It translates into floods of keystrokes, or eaten keystrokes, or
> keystrokes being fed to apps out of order. Requires
On Thu, Oct 25, 2018 at 6:50 AM, Nicolas Mailhot
wrote:
I get the same thing without any special load. System would work fine
for hours and then input would start bugging.
It translates into floods of keystrokes, or eaten keystrokes, or
keystrokes being fed to apps out of order. Requires a sy
> This is a very poor bug report because it does not list the hardware
details of the machine.
yes, it's a discussion. When I get to know more details I'll file a bug
report. For example is it really "libinput"?
> What is the output from "uname -a"?
[alsadi@laptop ~]$ uname -r
4.18.10-200.fc28.x
> I use Logitech wireless keyboards and mice with the bluetooth usb dongle.
Don't know if that's your case too.
I'm using my laptop keyboard (thinkpad t440p), no external gadgets.
> (priorization, ordering, and press/release detection).
it seems that too frequent "fake" press/release cycles are
On 10/25/18 11:27 UTC, Muayyad AlSadi wrote:
There are some things that makes my machine to freeze [[snip]]
This is a very poor bug report because it does not list the hardware details
of the machine.
What is the output from "uname -a"? What is one section of "cat /proc/cpuinfo"?
How much R
Le 2018-10-25 12:27, Muayyad AlSadi a écrit :
Hi,
There are some things that makes my machine to freeze
1. I've noticed that if I have some heavy CPU usage (ex. running many
VMs or tensorflow training or having tracker-miner-fs working in
background)
while typing somewhere (firefox, geany, ...
Hi,
There are some things that makes my machine to freeze
1. I've noticed that if I have some heavy CPU usage (ex. running many VMs
or tensorflow training or having tracker-miner-fs working in background)
while typing somewhere (firefox, geany, ...etc) a flood of keystrokes is
send to the applica
13 matches
Mail list logo
