Bug 150435

Summary: Kopete per-protocol error dialogs are annoying AND dangerous
Product: [Unmaintained] kopete Reporter: Stephan Sokolow <kde_bugzilla_2>
Component: Main ApplicationAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Stephan Sokolow 2007-10-03 10:04:09 UTC 
Version:           0.12.5 (using KDE KDE 3.5.7)
Installed from:    Compiled From Sources
Compiler:          gcc (GCC) 4.1.2 20070214 (  (gdc 0.23, using dmd 1.007)) (Gentoo 4.1.2 p1.0.1) 
OS:                Linux

Not only are the procotol-specific errors focus-stealing, modal, and too common (eg. the ones which basically say "I don't know what the server is complaining about. I'm going to hope for the best"), they can actually be dangerous.

I just woke up to a frozen X session which, according to the <#> component of the title bar, was trying to deal with 452 of them. (Opened in less than 8 hours while I slept)

I had to SSH in and repeatedly SIGKILL kopete... and wait for several minutes while the X server picked itself up off the floor. This is not acceptable.

How about some kind of error log window instead? Each message could begin with the name of the procol which sent it and whether it appears and/or is raised above the other windows could be a user-configurable setting.
Comment 1 Jan Binder 2008-06-23 09:48:26 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 2 Justin Zobel 2021-03-09 22:40:51 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 3 Stephan Sokolow 2021-03-11 19:48:09 UTC 
I don't use Kopete anymore (I switched to Pidgin as a less problem-ridden choice) and, since I don't know how to generate multiple Kopete error dialogs on demand, I don't know a practical way to quickly test if this is still a problem.

Can someone else who uses Kopete please weigh in?
Comment 4 Christoph Cullmann 2024-09-18 18:27:47 UTC 
Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.