Open verbal007 opened 3 years ago
OS: Manjaro Linux 20.2 Kernel: 5.8.18-1
I'm having a similar issue with a white rectangular box appearing directly in the middle of my chat window. In the Options screen, it shows up more toward the right side of the window (see screenshots). If I quit Wire and reopen it, the white box goes away for a period of time. I'm uncertain how long, but it could be over an hour before it shows up again. If I turn off the Dark Theme, it's less noticeable but I can still tell that the box is there because it's not exactly the same color as the default background.
I have uninstalled and reinstalled the same package version, but this did not solve the issue.
This started with update 3.21.2936 on Linux.
Attached are screenshots of the Wire chat window and options screen.
As the original poster stated, this problem occurs after the monitor is awakened from the Screen Saver Blanking feature within DPMS.
https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling
$ xset q
...
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 1800 cycle: 600
...
Instead of waiting for the automatic timeout to occur, I can force the issue to occur by turning off the monitor with the following command:
$ xset dpms force off
Once the monitor is awakened, I can sign back into my desktop, and if Wire is still running I will see the white box appear again. Closing Wire and re-opening it is the only way I know of to make it go away.
Wire version: 3.21.2936 Operating system: Manjaro (Linux) 20.2
What steps will reproduce the problem?
What is the expected result? Expecting no artefacts.
What is the actual result? Wire looks like attached image w/ blank window or white box appearing in chat.
Please provide any additional information below. Attach a screenshot if possible. This issue started about 2 weeks ago and is quite distracting. Typically a restart of Wire resolves the issue. The attached animated screencapture shows the black/blank screen and white box that appears. I have been experiencing similar issues with Chromium browser for a few months, which I may have solved with the following information.