About every second time I log in, Kopete pops up a ton of modal message dialog boxes (I had over 300 here!!), which flood RAM and bring the system to a halt. Turns out it does this trough Knotify4. (Perhaps because each window makes a sound when opening.) Reproducible: Sometimes Steps to Reproduce: 1. Be sure you run on KDE 4.4.1 2. Install Kopete (4.4.1) 3. Go to systemsettings, and configure a short sound for window and dialog opening. (Because you won’t see all the dialogs, and without the sound, the DOSing is harder so notice.) 4. Enable a Yahoo account. 5. Let it store the password in the digital wallet, so that that one asks for a password. 6. If everything runs, completely close Kopete, and start it again in a matter of seconds. (Just to be sure.) 7. Enter the digital wallet’s password. Actual Results: 8. A ton of dialogs about a problem with Yahoo pop up, making the configured sound in a pingpingpingpingpingpingpingpingpingpingpingpingpingping… 9. Notice memory usage going way up, flooding RAM, and slowing the system to a crawl because of swapping. (Including the ping sounds.) 10. Quickly (!!!) switch to a virtual terminal (e.g. Ctrl-Alt-F2). 11. killall kopete # make haste! 12. Notice how the flood of sounds stopped, but the RAM usage by Knotify4 is still extreme (e.g. 1.8 GB here). 13. killall knotify4 14. Notice how memory usage normalizes, and switch back to X. 15. WAIT before restarting Kopete, and prepare to eventually get the same thing again. Expected Results: 9. Kopete logs in normally, and nothing special happens. My guess is, that either this happens every time I restart Kopete, right after closing it, or it happens if you wait too long between starting Kopete, and entering the wallet’s password (and then perhaps also restart Kopete “too” quickly). It’s extremely annoying, and right now i open this bug, because it not only lost the history of what I wrote, but also crashed my PIM suite in the middle of saving, causing massive corruption, which I now have to restore via backup, losing a lengthy project plan I just had finished writing and was about to save in its final state. (The backup was this night, before I started to write the plan.)
Created attachment 225327 [details] emerge --info kopete
What message is shown in this notification?
Actually, there is no message shown, since a new dialog pops up on top of it, before its contents are rendered, and since that seems to never stop, there is never a text visible here. :/ (People with a very fast CPU might have more chance, but it’s unlikely.) The title of the windows is shown though. I can post the exact text when it happens the next time. (Right now I need my system working, so I won’t provoke it.) But for now, I can tell you that it includes the words “Kopete”, “Yahoo”, “error” and a number, like in “<302>”, where 302 is the number of dialogs open or messages, as far as I can tell, since it increases with every opening dialog.
Sorry for not being able to give more details. Is it hard to reproduce?
Please test kopete-4.4.2-r1 as there were some recent updates to the yahoo code and I just applied a patch that fixes the issue with stealth mode.
(In reply to comment #5) I just updated, and I can’t trigger the bug anymore. So unless it will happen again, I’ll mark the bug as fixed. Thx.
Ok, I’m sorry to say this, but I had the bug again, just 30 seconds ago. Is there any way I can help tracking this down?
Oh, I should note, that this time, it happened right after the start of the system. I logged is, I entered the password for the wallet as soon as it opened, and there it was. Didn’t kill knotify4 this time, because I wanted to see the dialogs, but they did go away with Kopete (obviously, since they were Kopete dialogs), and the sound for closing windows played of all of them. BUT: Memory usage didn’t go back to normal, until I killed knotify4! Seems that knotify4 doesn’t free the sound data from memory and also doesn’t re-use the same files when they already are in memory.
Please read the backtrace guide[1] and see if you can get some meaningful info. You can also open an upstream bug about this and attach there the backtrace. If you open the upstream bug, please add the link to the URL field in this bug.
Ok, I just restarted Kopete, after killing it as described. And it happened *again*. By the way, the exact text is: “Yahoo-Modul — Kopete <x>” where “x” is the number. There is no text inside the window. I also noticed something important: It doesn’t happen at login. It happens when the status of the contacts is read at the beginning. When Kopete starts, first it shows everyone who is online as online, no matter their real status. And then the little status icons of your friends in the list go from “online” to e.g. “away”, which is the real status. That’s the exact moment when it’s happening. In my exact case, the Yahoo icon for one friend of mine, who was the only one online, went to this red stop sign that is described an “busy” in the status editor dialog. Maybe that makes reproducing it easier.
(In reply to comment #9) > Please read the backtrace guide[1] and see if you can get some meaningful info. I’ll do that, as soon as I can find a way to reliably trigger the bug myself. If you can also not find anything, feel free to set the bug to NEEDINFO or something like that.
(In reply to comment #11) > If you can also not find anything, feel free to set the bug to NEEDINFO or > something like that. Unfortunately I don't have an yahoo account, so I can't test this issue. I'll leave the bug open to see if someone can help debug this.
Something I found, that turns up in .xsession-errors for each Yahoo window that opens: kwin(6245) KWin::Client::readUserTimeMapTimestamp: User timestamp, initial: 5533740 kwin(6245) KWin::Client::readUserTimeMapTimestamp: User timestamp, ASN: 5533740 kwin(6245) KWin::Client::readUserTimeMapTimestamp: User timestamp, final: 'ID: 62925071 ;WMCLASS: "kopete" : "kopete" ;Caption: "Yahoo-Modul – Kopete <81><200e>" ' : 5533740 kwin(6245) KWin::Workspace::allowClientActivation: Activation: Belongs to active application kwin(6245) KWin::Workspace::updateClientArea: screens: 2 desktops: 3 kwin(6245) KWin::Workspace::updateClientArea: Done.
Did you open an upstream bug about this issue?
(In reply to comment #14) > Did you open an upstream bug about this issue? I had planned to do it, but shortly thereafter I guess I did an update, and it did not occur anymore. I say „I guess“, because I forgot about it. Which means it did not happen anymore. Thank you for reminding me that this bug still existed. Well, right now it works for me. Which means it very likely got fixed. So let’s close it. When it really turns up again, or someone else sees it, we can still re-open it Thank you. :) >
