Opened 11 years ago

Last modified 7 years ago

#3564 new defect

Auto-login as invisible ...

Reported by: andrixnet Owned by: seanegan
Milestone: Component: libpurple
Version: 2.10.0 Keywords:
Cc:

Description

Am I missing something? I am really confused.

Scenario 1 :

  • assume in prefs there is NO setting for a preset status at startup, also, not checked for "use last status".
  • assume my account(s) are set to autologin
  • assume a fast PC, fast connection, thus there is potentially very little time to see and use the pidgin UI while connecting is in progress in order to stop it.
  • assume the last status was "avail" with a message.
  • start pidgin
  • it will autologin and set status to avail with message.
  • in prefs, change "status to apply at startup" from an empty value (installation default i think) to let's say "away".
  • stop pidgin
  • start pidgin

!!! pidgin starts with avail and message (the one used last time, setting in pref had no effect).

  • go to prefs, the setting marked bold above is now empty.

Scenario 2 :

  • assume in prefs there is NO setting for a preset status at startup, also, not checked for "use last status".
  • assume my account(s) are set to autologin
  • assume a fast PC, fast connection, thus there is potentially very little time to see and use the pidgin UI while connecting is in progress in order to stop it.
  • assume the last status was "avail" with a message.

I want the next time I start pidgin, to login as invisible. How do I do this? First idea that comes to mind is a command line switch.

  • open a command prompt, in pidgin installation dir.
  • type pidgin --help
  • since the default on this win32 box is for console applications to close automatically when the application exits and the fact that pidgin opens a different console window to show some text, as that window dissapears quickly, I can't read it.

REQUEST : on win32, pidgin --help and also any other instances when pidgin might open a console window, it should keep it open until user interraction (such as "Press ENTER")

So, on to the next. Go to .purple dir and look into accounts.xml I see a setting "auto-login" with value 1.

  • open the file in a text editor, change the value to 0.
  • start pidgin

Pidgin starts, doesn't auto-login, so now I can edit the account (from UI), and also access preferences for Pidgin. However, due to the problem with "status to apply on startup" described above, this option isn't of much use. Also, in the account settings (yahoo at least) there is no checkbox (like in the official yahoo client) that says "sign in as invisible".

On to the next idea... In accounts.xml I see the statuses, listed. There there is my last used status, which was an avail with a message. It has a property "active" set to true, while all others are set to false.

  • edit accounts.xml
  • set property active=false where it is set to true
  • set property active=true for the status I want to start with (my case, invisible)
  • start pidgin

nothing changes, the status I last used, the one avail with message is set again ...


So, in the end, I still remain with the question : if pidgin autologins (with my last status, whatever that was), how can I make it to log in as invisible?


I know this is a complex description with several variants and possible issues. If you think I should split it into several tickets, please let me know.

Attachments (1)

prefs1.xml (22.2 KB) - added by andrixnet 11 years ago.
prefs.xml, as requested

Download all attachments as: .zip

Change History (8)

comment:1 Changed 11 years ago by lschiere

  • Component changed from unclassified to libpurple
  • Owner changed from lschiere to seanegan

with the apply status option selected, it should not be using the last state. Please attach your prefs.xml after setting that.

comment:2 Changed 11 years ago by andrixnet

Testcase :

  • start pidgin
  • in prefs, currently nothing is set at "status to apply at startup"
  • use status from last exit is NOT checked.
  • my current status is invisible.
  • set "status to apply at startup" to let's say "away".
  • close pidgin.
  • saved prefs.xml as prefs1.xml

=========================================

  • start pidgin again
  • account(s) autologin
  • status is "invisible" (status last used)
  • prefs "status to apply at startup" is empty
  • close pidgin

Compare the current prefs.xml with the one saved previously. The only difference is the value of

pref name='idleaway'

Changed 11 years ago by andrixnet

prefs.xml, as requested

comment:3 Changed 10 years ago by bernmeister

Are you seeing this behaviour in Pidgin 2.5.8?

comment:4 Changed 10 years ago by maddin

I am using Pidgin 2.5.8.

Starting pidgin with "status from last exit" checked results in the following problem:

Pidgin is showing the state from the last exit of pidgin (as expected) but other people see me with the last state I had using official ICQ client with Windows.

I am going to give a example:

  1. Log in using official client, set state A, log off
  2. Log in using pidgin, set state B with "status from last exit" checked, log off
  3. Log in using the same pidgin as before, it shows state B to you but other users see you in state A

I think the problem is that pidgin shows the correct state to the user but doesn't update the state on the server.

comment:5 Changed 10 years ago by deryni

  • Status changed from new to pending

This sounds like #9626 which should be fixed in 2.6.0.

comment:6 Changed 10 years ago by andrixnet

  • Status changed from pending to new

Tested on 2.6.1 :

Current status : Available.
Go to prefs, unset "use status from last exit".
Set "status to apply at startup : Away".
Close Pidgin.
Start Pidgin.

Pidgin logs in as "available".
Go to prefs, "status to apply at startup" shows empty (no text).

comment:7 Changed 7 years ago by andrixnet

  • Version changed from 2.2.1 to 2.10.0
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!