So far it happened when I was reading the backlog. I scrolled up to the top, and started reading, scrolling from time to time. Then suddenly scrolling stopped working and clicking anywhere didn't do anything either. Reproducible: Sometimes Steps to Reproduce: 1. start konversation and connect to the server 2. let a backlog build up/receive a backlog from a bouncer 3. scroll up and start reading the backlog Actual Results: konversation freezes after some time Expected Results: konversation should not freeze About the only thing related to konversation in journalctl is this: ----------- No language dictionaries for the language: "en" ----------- This gets spammed a few times. I'm running plasma 5.3.1 and kf5.1.0 Never happened before 1.6/the kf5 switch. Scrollback is set to 1000 lines, but most backlog I receive from the bouncer is max 500 lines.
I think I figured it out. When you have konversation configured to open links to files in the program they're associated with, the kioexec process doesn't seem to return with some programs. In my case it's photoqt. So Konversation sits there and waits for kioexec to exit, but for some reason it does not after photoqt is closed.
Created attachment 93061 [details] Related: random popup of kioexec The weird thing is, that if I configure Gwenview to open the images by default, things work, but I then get random popups as shown in attachment long after I've opened any image files.
Scratch the part about gwenview working - it just froze on me after I opened a link with it. Had to manually kill the kioexec process.
I just had the same type of freeze with another application, so it seems it's not a bug in konversation, but kioexec instead...
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!