Bug 133322

Summary:	disable icq disconnection info
Product:	[Applications] kopete	Reporter:	arne anka <kde-bugs>
Component:	Notifications	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	aspotashev, lamarque
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description arne anka 2006-08-31 11:00:06 UTC

Version:           0.11.3 (using KDE 3.5.4, Debian Package 4:3.5.4-3 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.17.6

for the last few days i got (and still get) every 3 or 4 minutes that info "<youricqnumber> disconnected".
it's a bity annoying to have that thingy popup everytime -- in particular because the icq-plugin ususally reconnects automatically.
so a config-option for icq (jabber still does not autmatically reconnect, so such a message is needed) allowing to disable this notification would be nice.

Comment 1 Jan Ritzerfeld 2006-08-31 23:20:57 UTC

At least in 0.12 this information is shown as a passive popup for me: IMHO not very disturbing. Perhaps, these popups can be disabled via "Configure Notifications...". Additionally, again at least in 0.12, jabber accounts should reconnect, too---without any notification--- see your Bug 115052.

Comment 2 arne anka 2006-09-01 09:18:23 UTC

it's a passive popup in 0.11.3, too.
but personally i consider it disturbing to have such a thingy pop up while i type (that's why it is a wish :-).

i'm not sure which of the "configure notification ..."-entries matches the icq-disconnect, debian/sid still has 0.11.3 and there jabber does not reconnect on it's own, so disabling _all_ disconnect-infos is not desirable, imo.

Comment 3 arne anka 2007-04-30 09:14:54 UTC

still true for 0.12.4 -- and imho it's a plain bug.
i disabled _everything_ that looks like it would disable that annoying thingy but it does not help.
if disabling all notification does not disable this notification too, then something is broken.

Comment 4 Lamarque V. Souza 2011-03-20 03:12:59 UTC


*** This bug has been marked as a duplicate of bug 265811 ***