Adium

Ticket #2479 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

Adium causes delay when system wakes from sleep

Reported by: Jeroen (jeroen at je dash ju dot net) Owned by: nobody
Milestone: Component: None
Version: Severity: normal
Keywords: Cc:
Patch Status:

Description

For a while now I had been stumped because I had intermittent issues with waking my powerbook from sleep. It would take about half a minute to a minute for it to wake from sleep. I tried running spincontrol, but that doesn't work when you're not logged in. Log messages were not really clear and mostly had to do with configd and lookupd.

But tonight I dug a little deeper and through Google's digging through Adium's changesets, I have tracked down the issue to Adium. The following log entries never appear when Adium is not running (and there is almost no delay) and always occur when Adium is running and causes a huge delay:

Dec 20 20:46:50 Doc lookupd[14561]: NetInfo connection failed for server 127.0.0.1/local
Dec 20 20:46:58 Doc configd[35]: SecKeychainFindGenericPassword err= -25308 ( =0xffff9d24, secErrStr=User interaction is not allowed. ) (current= je-ju.net)
Dec 20 20:47:00 Doc /Applications/Utilities/NetInfo Manager.app/Contents/MacOS/NetInfo Manager: NetInfo connection failed for server 127.0.0.1/local

This is a serious issue. It is not easy to see that Adium is to blame here. Delays when waking from sleep are very annoying and can drive users to question their hardware.

Change History

Changed 4 years ago by evands

I've never seen this behavior, and I wake my laptop with Adium running multiple times per day.

What service(s) are you using / having connected at the time that the system goes to sleep with Adium running?

Changed 4 years ago by Jeroen

Upon further research, this may indeed not be Adium's fault. It now also happens when Adium is not running. For some odd reason, last night when I checked (multiple times!) every time Adium was not running it didn't happen and when it did, it happened.

Seems I'll have to try to look into this some more :(

Changed 4 years ago by boredzo

  • priority changed from high to normal
  • status changed from new to closed
  • resolution set to invalid
  • severity changed from major to normal

not an Adium issue -> invalid.

also, when you file a ticket, please tell us the version of Adium that you're using, and please don't set priority.

Note: See TracTickets for help on using tickets.