Opened 12 years ago

Closed 11 years ago

#2681 closed defect

Idle reporting never happens (2.1.1, Linux, AIM)

Reported by: bconway Owned by: seanegan
Milestone: Component: pidgin (gtk)
Version: 2.1.0 Keywords:
Cc:

Description

I believe this is different (slightly) from #2525 and #333. I'm running 2.1.1 compiled with XScreenSaver support and have my preferences set to report idle time based on keyboard and mouse use. For the past two releases, I've seen *no* idle time being reported (and have verified no mouse movement over that time) even after a fresh restart of X and of Pidgin. In releases prior to 2.1.0 I saw the problem listed in #333 after a disconnect/reconnect. This is compiled on a Debian Etch/4.0 system, with stock X.org 7.1 and libgtk 2.8.20, and libxss1 and libxss-dev are installed.

Debugging Information

Arguments to ./configure: '--prefix=/opt/pidgin' '--enable-cyrus-sasl' Print debugging messages: No Plugins: Enabled SSL: SSL support is present.

Library Support

Cyrus SASL: Enabled D-Bus: Disabled Evolution Addressbook: Disabled Gadu-Gadu library (libgadu): Internal GtkSpell?: Enabled GnuTLS: Enabled GStreamer: Disabled Mono: Disabled NetworkManager: Disabled Network Security Services (NSS): Enabled Perl: Enabled Startup Notification: Enabled Tcl: Disabled Tk: Disabled X Session Management: Enabled XScreenSaver: Enabled Zephyr library (libzephyr): Not External Zephyr uses Kerberos: No

Change History (14)

comment:1 Changed 12 years ago by seanegan

  • Milestone set to 2.1.2
  • Owner set to seanegan
  • Status changed from new to assigned

comment:2 Changed 12 years ago by BrianG

idle time isn't being reported with the "last message sent" option either. (2.1.0)
2.0.2 idle time worked once per session.

comment:3 Changed 12 years ago by schoen

What are your »change status when idle« settings? In versions prior 2.1.0, idle time was reported hard-coded after 10 minutes. Since 2.1.0, it is only reported if you let Pidgin change your status after a certain amount of time.

comment:4 Changed 12 years ago by BrianG

my »change status when idle« settings are off (unchecked). i don't want my status to change because i've gone idle.

comment:5 Changed 12 years ago by schoen

Try setting your »change status when idle« to set your status to »available« after e.g. five minutes. That way your account should become idle, but not away.

comment:6 Changed 12 years ago by BrianG

but what if i'm away and want to go idle without my status changing to available?

they really should be functioning separately.

comment:7 Changed 12 years ago by schoen

If you are already away, your status won’t change back to »available« again.

comment:8 Changed 12 years ago by bconway

Update: While I prefer to do all my status changing manually, I played around with schoen's suggestion and got some weird (good) behavior. Here are my steps:

1.) Check "Change status when idle." 2.) Increase minute count from 1 to 10. 3.) Change status to Available. 4.) Uncheck "Change status when idle," leave those settings underneath.

My idle time now appears and works like it did a few releases back.

comment:9 follow-up: Changed 12 years ago by BrianG

idle time works with the above work around. i noticed now when i open the message window after being idle that the message window minimizes upon the first sent message.

comment:10 in reply to: ↑ 9 Changed 12 years ago by bconway

I should add that the above work-around isn't totally reliable, after going back and forth between idle and not idle, I am now no longer able to go idle. This is without any disconnects. Thanks.

comment:11 Changed 11 years ago by dave1g

There seem to be a lot of problems with idle... some the exact opposite of each other (stuck in idle, vs never getting to idle) My problem is the stuck in idle forever one. CCing all to keep track.

#2002 #2525 #2681 #5825 #5853 #5967 #6041

comment:12 Changed 11 years ago by dave1g

My issue in #5825 seems to be fixed with 2.4.3. Everyone on this ticket should report whether 2.4.3 has fixed or not fixed the issue for them.

comment:13 Changed 11 years ago by Sim-on

  • pending changed from 0 to 1

comment:14 Changed 11 years ago by trac-robot

  • pending changed from 1 to 0
  • Status changed from assigned to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!