chatterino2 icon indicating copy to clipboard operation
chatterino2 copied to clipboard

Chatterino doesn't refresh after sleep on Plasma 6

Open aknight2015 opened this issue 11 months ago • 10 comments

Checklist

  • [x] I'm reporting a problem with Chatterino
  • [x] I've verified that I'm running the most recent nightly build or stable release
  • [x] I've looked for my problem on the wiki
  • [x] I've searched the issues and pull requests for similar looking reports

Describe your issue

OS: Debian 12 Desktop: Plasma 6 with Wayland Manager: GDM3 Whenever I put my laptop to sleep and resume Chatterino still displays the channels live, there were reported live before the sleep. After I wake it up I'll wait like 10 minutes and there's no change. I have to close it and reopen it in order for it to update.

Screenshots

I wish I could, but I can't record my computer going to sleep.

OS and Chatterino Version

Chatterino 2.5.3 (Commit 3f3a31db) build with Qt 6.7.2 on Debian 12 (Bookworm)

aknight2015 avatar May 11 '25 15:05 aknight2015

It would be great if you could capture the output of Chatterino. See Viewing Logs on how to get those. chatterino.*.debug=true should be enough I think.

Nerixyz avatar May 11 '25 16:05 Nerixyz

Sure. Do I use the CLI to launch the chatterino appimage using the above mentioned flags?

aknight2015 avatar May 14 '25 03:05 aknight2015

You'd launch Chatterino in CLI, having set the above mentioned flags before it so

export QT_LOGGING_RULES="chatterino.*.debug=true"
./Chatterino-x86_64.AppImage

pajlada avatar May 14 '25 07:05 pajlada

I've run Chatterino with those flags. Where does it put the log file?

#!/bin/bash export QT_LOGGING_RULES="chatterino.*.debug=true" ./Chatterino-x86_64.AppImage

if anyone else has trouble I made the above a script. That way in the future you can just share that with people.

aknight2015 avatar May 15 '25 01:05 aknight2015

It doesn't log to a file, it should log to your terminal. You can log it to a file for later viewing like this: 2>chatterino.log ./Chatterino-x86_64.AppImage or when you run your script 2>chatterino.log ./your-script.sh

pajlada avatar May 15 '25 06:05 pajlada

Crap. I thought it went to a file. I'll add that to the script and run it again. Good news is that the problem persisted, so it can be reproduced on my end.

aknight2015 avatar May 15 '25 19:05 aknight2015

chatterino.log

Here's the log file. Sorry it's so large.

aknight2015 avatar May 16 '25 01:05 aknight2015

Hey @aknight2015, thanks for the logs. We now see that it is indeed timeouts, but we don't really know why yet. Could you run the new script I've posted below and share the logs with us?

#!/bin/bash
export QT_LOGGING_RULES='chatterino.*.debug=true;qt.network*=true;'
export QT_MESSAGE_PATTERN='%{time yyyy/MM/dd hh:mm:ss.zzz} %{if-category}%{category}: %{endif}%{message}'
./Chatterino-x86_64.AppImage

and running it like this:

2>chatterino.log ./your-script.sh

The updated scripts also includes debug logs from Qt's own network code, and the added QT_MESSAGE_PATTERN adds timestamps to each entry

These logs will be much bigger, so you might need to gzip the logs before sending them here (you can also upload them to a file host like https://kappa.lol if github is giving you issues) gzip the logs by typing gzip chatterino.log, which will gzip them and rename them to chatterino.log.gz

Thanks in advance!

pajlada avatar May 18 '25 11:05 pajlada

chatterinoQt.log

There you go good sir. I hope this helps.

aknight2015 avatar May 19 '25 04:05 aknight2015

I'm no longer encountering this issue on nightly with Plasma 6.3.5

edit: nvm it happened again

iProdigy avatar Jun 18 '25 03:06 iProdigy