#818071 mcabber: Weird bug/freeze when using PgUp/PgDwn

Package:
mcabber
Source:
mcabber
Description:
small Jabber (XMPP) console client
Submitter:
eingousef
Date:
2022-03-31 06:18:03 UTC
Severity:
important
Tags:
#818071#5
Date:
2016-03-13 10:56:38 UTC
From:
To:
Dear Maintainer,

When pressing PageUp/PageDown quickly to navigate in the roster window,
mcabber seems to freeze, doesn't seem to take any input, I have to kill it
from an other terminal. After it's killed all the characters sent to mcabber
while it was hanging appear on the shell (like ~~~~~~~~~/help/quit). If I
press the PgUp/PgDown buttons slowly I can navigate in the roster without any
problem.

This didn't happen previously, it must be due to a very recent upgrade.

I'm using zsh in a tilda terminal.
#818071#10
Date:
2016-03-14 11:49:43 UTC
From:
To:
Dear Maintainer,

I can't reproduce the bug anymore so I guess it was a binary I forgot to
reload after an upgrade, or something like that. Sorry for the inconvenience.
#818071#15
Date:
2016-09-15 11:52:51 UTC
From:
To:
I can't reproduce it all the time, but it seems that after pressing
PgUp/PgDwn several times (no matter how fast), mcabber freezes and the
input characters are sent to the console in the background. This
happens with different terminals (tilda and sakura), and with
different shells (bash and zsh), so it's probably an mcabber bug.
#818071#20
Date:
2016-09-15 12:25:39 UTC
From:
To:
Actually it's the roster up/roster down command that is
bugged. Binding those commands to different keycodes doesn't solve the
problem.
#818071#25
Date:
2018-02-19 10:31:11 UTC
From:
To:
Dear eingousef, could you please check whether the problems with
PageUp/PageDown are still present in version 1.1.0-1 and comment
here on this bug report? Many thanks!
#818071#28
Date:
2018-02-19 10:31:11 UTC
From:
To:
Dear eingousef, could you please check whether the problems with
PageUp/PageDown are still present in version 1.1.0-1 and comment
here on this bug report? Many thanks!
#818071#33
Date:
2022-03-31 06:15:11 UTC
From:
To:
I can't reproduce this bug. Working for me in version 1.1.2-1.