Bug 206928 - AIM keeps disconnecting frequently when DHCP lease is set short (60 minutes)
Summary: AIM keeps disconnecting frequently when DHCP lease is set short (60 minutes)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kopete
Classification: Unmaintained
Component: ICQ and AIM Plugins (other bugs)
Version First Reported In: 0.70.90
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-10 04:27 UTC by David Trebacz
Modified: 2018-11-08 14:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Trebacz 2009-09-10 04:27:11 UTC
Version:           0.70.90 (using KDE 4.3.1)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Not sure this is a bug with Kopete, but that is where in manifested itself after a recent update of KDE via the PPA backports repositories for Kubuntu 64 bit OS. After an update Kopete kept dropping my AIM connection periodically. It would automatically try and reconnect, but eventually AIM would ban reconnection for progressively longer times. It essentially became unusable for AIM, but the simultaneous connection to MSN chat never skipped a beat.

I looked for people having similar issues, but didn't see anything recent. I have used Kopete successfully day in and day put for at least a couple years with my current configuration. I even tried a purge and reinstall, in case the update caused some weird incompatibility.

Ultimately nothing changed. Cleaning up a couple other issues on my install I noticed that there were frequent DHCP requests made to my Smoothwall router/firewall. Realizing I had set the DHCP lease on my Smoothwall to 60 minutes (don't remember why). I changed it to a more relevant number 10080 minutes (a week) for a small home network. Lo and behold Kopete stayed connected to AIM without any issues. I have no idea what DHCP lease would have to do with Kopete's ability to stay connected to AIM, but offer this up in hopes it may shed light on the deeper issue.
Comment 1 David Trebacz 2009-09-19 18:43:02 UTC
Oddly enough after a reboot of KDE the problem has returned. As I suspected it has nothing to do with DHCP lease. Not sure why a reboot has brought back the problem though. Any suggestions for additional troubleshooting would be appreciated.
Comment 2 David Trebacz 2009-09-19 20:27:56 UTC
In a terminal window I get the following output after launching Kopete:

X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)                                 
  Resource id:  0x300c87d                                          
QObject::connect: Cannot connect (null)::onlineStatusChanged(Kopete::Contact *, const Kopete::OnlineStatus &, const Kopete::OnlineStatus &) to Kopete::Identity::updateOnlineStatus()                                                                                                             
QPainter::begin: Widget painting can only begin as a result of a paintEvent                                                                      
QPainter::translate: Painter not active                                                                                                          
QPainter::setClipRect: Painter not active                                                                                                        
QPainter::hasClipping: Painter not active                                                                                                        
QPainter::setPen: Painter not active                                                                                                             
QPainter::setBrush: Painter not active                                                                                                           
QPainter::hasClipping: Painter not active                                                                                                        
QPainter::setPen: Painter not active                                                                                                             
QPainter::setBrush: Painter not active                                                                                                           
QPainter::hasClipping: Painter not active                                                                                                        
QPainter::setPen: Painter not active                                                                                                             
QPainter::setBrush: Painter not active                                                                                                           
QPainter::hasClipping: Painter not active                                                                                                        
QPainter::setPen: Painter not active                                                                                                             
QPainter::setBrush: Painter not active                                                                                                           
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active
QPainter::font: Painter not active
QPainter::setFont: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active
QPainter::font: Painter not active
QPainter::setFont: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active
QPainter::setPen: Painter not active
QPainter::worldTransform: Painter not active
Comment 3 David Trebacz 2009-09-20 20:13:46 UTC
After further evaluation of the problem (trial and error), I think the issue with Kopete stems from a recent updated to my local firewall (SmoothWall 3.0 update 5), which runs an IM proxy (IMSpector).

The September 2nd update of Smoothwall included an update of IMSpector (20090728 version). As soon as I turned off the IM proxy -Kopete stayed connected to AIM (never had any trouble with MSN.

I have since renabled the proxy to see if the connectivity issue comes back. So far it's working fine. Go figure.
Comment 4 David Trebacz 2009-10-16 04:28:35 UTC
I still have this problem with Kopete 0.80.2 and KDE 4.3.2 (from Kubuntu PPA backports). Whenever Kopete is used through my proxy AIM disconnects frequently (MSN is fine). AIM on the same machine through Pidgin is fine also. Don't think it had anything to do with DHCP lease time (thought that was odd) or IMSpector.
Comment 5 Andrew Crouthamel 2018-11-02 23:02:32 UTC
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!
Comment 6 Andrew Crouthamel 2018-11-08 14:32:31 UTC
Hi, sorry for the bad news, but AIM was discontinued last year, so I will be closing this bug.

Thank you for helping us make KDE software even better for everyone!