[Bug 43085] New: TIM message manager window unresponsive partly
https://bugs.winehq.org/show_bug.cgi?id=43085 Bug ID: 43085 Summary: TIM message manager window unresponsive partly Product: Wine Version: 2.8 Hardware: x86 URL: http://dldir1.qq.com/qqfile/qq/TIM1.1.0/20837/TIM1.1.0 .exe OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lilydjwg(a)gmail.com Distribution: --- Created attachment 58267 --> https://bugs.winehq.org/attachment.cgi?id=58267 The problematic window This is another window-related issue with TIM, similar to the one in bug 43009. TIM is a cleaner version of QQ, successor of QQ Lite. download and install it: http://dldir1.qq.com/qqfile/qq/TIM1.1.0/20837/TIM1.1.0.exe ecb6934f7cea33b1458308495fd965a274c6ba2a TIM1.1.0.exe winetricks riched20 so you can input your QQ number. login in, then click "消息记录" near the bottom-right corner. The window will expand to the right, showing history messages. Then click again to unexpand it. Now, the top bar and the left buddy list will become unresponsive. The top bar even doesn't update itself. A screenshot by scrot shows these unresponsive part as black. Minimizing then restoring won't help. However, cover the window with another window then it's back to normal. My window manager is Awesome 3.4. Tested with wine 2.8, wine-staging 2.8. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43085 --- Comment #1 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Does the patch4 from the bug 43009 help? If it doesn't help it would really help to have a QQ account for testing, debugging remotely and passing around huge logs makes things a little bit awkward on both ends. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43085 --- Comment #2 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Also, did you test with plain wine or wine-staging? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43085 --- Comment #3 from lilydjwg(a)gmail.com --- (In reply to Dmitry Timoshkov from comment #1)
Does the patch4 from the bug 43009 help? If it doesn't help it would really help to have a QQ account for testing, debugging remotely and passing around huge logs makes things a little bit awkward on both ends.
No, it doesn't help. I've tested with both wine and wine-staging. QQ itself is awkward too. Qi Hong once provided a testing account but it no longer works, and I can't get in touch with him now. Accounts in China now tie to the person. What's worse, I can't change passwords for my old QQ accounts unless I provide my phone number to Tencent. And I don't know what would happen when I try to tie multiple QQ accounts to the same phone number, so I can't share my account, or I may lose it permanently. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43085 --- Comment #4 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- If you are willing to do some investigation on your part, generate logs and try patches then I could try to figure out what is going on by reading the logs and try to create some patches for testing. As usually the first thing to do is to find out the properties of that unresponsive window (class name, class style, window name, window styles). Then generate the +relay,+seh,+tid,+class,+win,+msg,+event log (first run 'wine winver' in a separate xterm to reduce start up noise). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43085 --- Comment #5 from lilydjwg(a)gmail.com --- class name: TXGuiFoundation class style: 960F0000 (visible, enabled) window name: 凡人 window styles: 960F0000, extended 00080300 Here's the log https://transfer.sh/KwIJX/wine.log.xz (184M, 6G uncompressed). That part of window goes unresponsive twice, both when expending and restoring (which changes the window size). After the window losing focus, it becomes normal. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43085 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #6 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to lilydjwg from comment #5)
class name: TXGuiFoundation class style: 960F0000 (visible, enabled) window name: 凡人 window styles: 960F0000, extended 00080300
Here's the log https://transfer.sh/KwIJX/wine.log.xz (184M, 6G uncompressed).
That part of window goes unresponsive twice, both when expending and restoring (which changes the window size). After the window losing focus, it becomes normal.
Thanks for the log. There are several windows of the class "TXGuiFoundation" created in the log, some of them belong to different processes. In order to better recognize the wrongly behaving window could you please describe what you did during the log creation? Also, do you know how that window is supposed to behave under Windows? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43085 --- Comment #7 from lilydjwg(a)gmail.com --- (In reply to Dmitry Timoshkov from comment #6)
Thanks for the log. There are several windows of the class "TXGuiFoundation" created in the log, some of them belong to different processes. In order to better recognize the wrongly behaving window could you please describe what you did during the log creation? Also, do you know how that window is supposed to behave under Windows?
Can you tell the window sizes? The biggest one is the problematic one (and the main window). or if you can tell the location, the topleft corner of it was in the left top of my screen (1366x768). Not the centered one (login window), not the right top one (the popup menu from tray icon). Also not a tiny one (tooltip). The window should expand and shrink when I click "消息记录" button, updating the position of items on the top part. On the left is a sidebar of buddy list, which should respond to mouse moves and clicks. Under wine it works fine after the window loses focus. What I did (I try my best to recall): * logged in. clicked the remember passwords checkbox (though it hardly works). typed in my password and waited * the login window faded away, and the main window appeared. moved my mouse to the button "消息记录" and waited * I moved the the window a bit while waiting, but it moved back automatically * the button responded by changing appearance, and I clicked on it * waited long enough for the window to expand. then moved mouse to the left top to see if it responded or not. I might have clicked once there * defocused the window by moving mouse to another (native) window * moved mouse to the left of window again to see if it responded. it responded, the background of the item under mouse became grey * clicked "消息记录" again and the window shrank back its size * tried clicked on the left again and it didn't respond. then defocused and tried again * waited for the click to do actual things (reading information and present in the main part of window) * also tried to focus a text entry at the left top, it worked. * closed the window * right clicked the tray icon, selected "退出" (Quit) from a popup window * waited for the process to exit If you need I can record a screencast next time. It'll be quite long anyway because it is terribly slow in debug mode. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43085 --- Comment #8 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- (In reply to lilydjwg from comment #7)
Can you tell the window sizes? The biggest one is the problematic one (and the main window). or if you can tell the location, the topleft corner of it was in the left top of my screen (1366x768). Not the centered one (login window), not the right top one (the popup menu from tray icon). Also not a tiny one (tooltip).
It's hard to tell at this point of investigation the window sizes because all windows of the class "TXGuiFoundation" are being created either 0x0 or -1x-1 (which also means 0x0). In order to tell the final window size it's needed to track down the window's life time including all move/resize events, and for that one would need to inspect almost the whole log.
The window should expand and shrink when I click "消息记录" button, updating the position of items on the top part. On the left is a sidebar of buddy list, which should respond to mouse moves and clicks. Under wine it works fine after the window loses focus.
From the log it's impossible to recognize windows by their captions/text since in the log the unicode characters are represented in hex, and I could imagine that even for a chinese speaking person it's pretty hard (if not impossible) to fluently associate unicode hex character codes with their appropriate visual representation.
What I did (I try my best to recall): * logged in. clicked the remember passwords checkbox (though it hardly works). typed in my password and waited * the login window faded away, and the main window appeared. moved my mouse to the button "消息记录" and waited * I moved the the window a bit while waiting, but it moved back automatically * the button responded by changing appearance, and I clicked on it * waited long enough for the window to expand. then moved mouse to the left top to see if it responded or not. I might have clicked once there * defocused the window by moving mouse to another (native) window * moved mouse to the left of window again to see if it responded. it responded, the background of the item under mouse became grey * clicked "消息记录" again and the window shrank back its size * tried clicked on the left again and it didn't respond. then defocused and tried again * waited for the click to do actual things (reading information and present in the main part of window) * also tried to focus a text entry at the left top, it worked. * closed the window * right clicked the tray icon, selected "退出" (Quit) from a popup window * waited for the process to exit
Thanks, I'm mostly interested to know whether you clicked at the not responsive window, how much times, at which approximate coordinates, and what happened after the clicks.
If you need I can record a screencast next time. It'll be quite long anyway because it is terribly slow in debug mode.
Recording a movie during logging would be an overkill, I'll let you know if I need more information or another log. Thanks. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43085 --- Comment #9 from lilydjwg(a)gmail.com --- (In reply to Dmitry Timoshkov from comment #8)
From the log it's impossible to recognize windows by their captions/text since in the log the unicode characters are represented in hex, and I could imagine that even for a chinese speaking person it's pretty hard (if not impossible) to fluently associate unicode hex character codes with their appropriate visual representation.
If you need the hex format, it's \51e1\4eba. Later it changes to \6625\6f2b when I was finishing.
Thanks, I'm mostly interested to know whether you clicked at the not responsive window, how much times, at which approximate coordinates, and what happened after the clicks.
Once or twice. About (380, 227) (not accurate). No response, then I defocus the window. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org