New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mouse scrolling is broken #17254
Comments
Works like a charm. Looks like these steps aren't right. |
Hmm.. restarting Telegram fixed the problem. I could still type messages. Is there some kind of crash report or logging file I could refer to? EDIT: I found |
The log file (log.txt) gets overridden.. Maybe you should store at least the current log AND ALSO the previous log file. |
Nothing regarding scrolling is logging, it's something handled at toolkit level, not at app level |
happened here with me too. what I noticed is that the problem is intermittent, when the scroll does not work, I noticed that the mouse icon is different when it is over the application, and when the mouse icon is not different (from other apps) the scroll works in desktop telegram I'm using the binary version available here on github in release v3.2.4 |
Without a reliable way to reproduce, it's unlikely to be fixed |
yes, i'll keep an eye out here and if i can find a way to reproduce it, i'll share it here 😉 |
@ilya-fedin yes, you could also think along how to debug this issue better. |
@Danger89 I don't imagine how this could happen and how to debug this, tdesktop just reacts to mouse events sent by Qt. I have a feel this is a Qt bug. |
I have the same problem running 3.2.2 and 3.2.5 versions. version 3.2.5 works for while after start, but some moment later wheel scroll becomes broken. |
It should happened in 3.1.8 version also if it was a Qt bag. But 3.1.8 scrolls nicely. |
Qt was updated in 3.2.0 |
How to reproduce:
Ubuntu 20.04.3 LTS |
tdesktop doesn't use your system Qt, it has Qt 6.2 embedded in the binary |
Can you be more specific - you mean suspend or hibernation? I don't have any action assigned to the lid. |
suspend. No hibernation. |
Sorry, but I can't reproduce :( |
This could be why.. Maybe build a debug app (if possible, so we can catch any eerros)? Or did you see anything strange in the telegram desktop log.txt? |
Sorry indeed. |
I don't imagine how a debug build would help, this is not a crash, so debug symbols won't help. log.txt won't help either since, as I said previously, nothing regarding scrolling is logged.
I don't know :(. If this is a Qt bug, only Qt developers know how to debug this... |
yea I could find some debugging techniques within the Qt docs: Just maybe |
All QT_DEBUG_PLUGINS=1 does is outputs debug info about plugins loading |
maybe |
It solidly happens if notebook was suspended for about 1 hour - the way from home to office. |
It produces a lot of output. Hope my SSD is enough to accommodate all of them until scroll freezes... |
Pls take a look in the log - https://dev.kopeyko.ru/tmp/telegram-v3.2.5.debug20211119.output I started telegram as
All day it work great, but finally wheel scrolling got frozen - after note spend about 45 minutes in suspend mode (the way from office to home) :-( Hope it'll help you to investigate the problem. |
I see input device re-detection at line 87810 and no scroll wheel events logged since then. I don't know when it happened though since the log has no timestamps. |
How I can enable timestamps? |
looks like |
Given that Qt's X11 support degrades and it seems they have no people with enough knowledge to fix bugs like this one or #10348 on X11, we're trying to remove GNOME from blacklist for operating with Wayland backend again (it's the only blacklisted environment). Last time we tried that, there were a lot of reports about regressions as migrating from X11 backend to Wayland backend with Qt is basically exchanging one bugs with the others as both backends have various user-noticable bugs. So, this time we're trying to make Wayland the default only for new installations, so these bugs appear as result of manual intervention (like installing the application on new system installation, switching from X11 session to Wayland or clearing application data) rather than a regression after automatic update. So, if you're using any Wayland-capable environment (like Ubuntu 22.04 with non-NVIDIA hardware) and you aren't afraid of exchanging the current bugs with some other ones, you can update to beta version 4.0.3 and clear application data or remove |
telegram desktop |
Ok, apparently the thread should be locked again to avoid noise |
Everyone who want the fix right now: feel free to switch to Wayland and follow what is described in #17254 (comment) |
Good news, looks like Qt is going to have a fix for this in the release 6.5.0 version (currently the static binary is using 6.5.0-beta3). |
@ilya-fedin : Don't you mean 6.6.0? That's what it says on the Qt bug page. A fix has just been checked into the trunk there. |
The cherry-picks aren't merged yet, but the 6.5.0 one already failed, so it may be that it will be only in 6.5.1 (unless they will re-stage it tomorrow) |
I can add that the trigger on my computer is disconnecting and reconnecting the mouse several times. Scrolling does work on other applications correctly, however - not for Telegram. |
fixed on 4.8.0 |
@Aokromes @ilya-fedin petition to reopen this issue? I think I found a lead. The broken scrolling is reproducible using the Snap / sandboxed build, v4.8.1 (Ubuntu Desktop). No issue when installing "directly"
|
@nogurenn this issue is not about closing when scrolling, it's about scrolling just not working. I.e. you scroll and nothing happens. |
Steps to reproduce
Expected behaviour
Scrolling within the message window.
Actual behaviour
Telegram desktop doesn't respond to any scroll wheel action.
Operating system
Linux Mint 20.2 (Ubuntu based)
Version of Telegram Desktop
3.2.4
Installation source
Static binary from official website
Logs
No response
The text was updated successfully, but these errors were encountered: