Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#12028 closed defect

Status at Startup Corrupted

Reported by: LanceHaverkamp Owned by: rekkanoryo
Milestone: Component: unclassified
Version: 2.6.6 Keywords: Status at Startup
Cc:

Description (last modified by LanceHaverkamp)

My 'Status at Startup' has been corrupted for months--used to work fine. I thought an upgrade might fix it but never has:

Use status from last... is not checked. Every boot I have to go into manage accounts & manually disable then enable each separate account to login to each chat server. Complete uninstall & reinstall does not help. Deleting .purple folder and rebuilding from scratch does not help.

The more I work on this, the more I think it's a problem with accounts being disabled. The enable box is checked, but the icons are all grayed-out until I uncheck, then recheck them.

Currently running 2.6.6 (same problem for many months with earlier versions), on Mepis (Debian) Linux on a KDE 3.5.10 Desktop.

Change History (12)

comment:1 Changed 9 years ago by LanceHaverkamp

  • Description modified (diff)
  • Version changed from 2.7.0 to 2.6.6

comment:2 Changed 9 years ago by datallah

  • Status changed from new to pending

Please follow the instructions to get a debug log and attach it to this ticket.

comment:3 Changed 9 years ago by QuLogic

Does the status selector show Online as you would expect? Does it also say "Waiting for connection..."?

comment:4 Changed 9 years ago by LanceHaverkamp

  • Status changed from pending to new

Yes, it does behave normally & display "Waiting for connection..."

After I manually disable then re-enable each account it works perfectly fine until Pidgin closes. Once I re-launch the program, I again have to manually disable then re-enable each account. That's why I'm increasingly suspecting that this is not truly a status issue, but rather that all accounts are being disabled when the program closes but not enabled at launch.

Any ideas? I'm stumped!

comment:5 Changed 9 years ago by QuLogic

  • Status changed from new to pending

You need to configure NetworkManager to recognize your connection, or uninstall it.

comment:6 Changed 9 years ago by LanceHaverkamp

  • Status changed from pending to new

I have no idea what NetworkManager is (and therefore certainly didn't change anything in NetworkManager to make Pidgin stop working). What are you talking about & why do you suspect it is the culprit?

Thanks!

comment:7 Changed 9 years ago by deryni

  • Status changed from new to pending

NetworkManager is a service that handles network activity notifications, pidgin uses it to detect when your network connection doesn't exist, goes away, comes back, etc. The "waiting for network connection" message means pidgin has been told by NM that your network connection does not exist and so pidgin does not attempt to make any connections as it believes they will of necessity fail.

When you disable and re-enable your accounts you are bypassing the connectivity status check and forcing pidgin to connect the accounts, which is why it works.

Your problem is that you have NM running and pidgin can talk to it but NM is not configured to know anything about your network connection and so will never report that it exists to pidgin, hence either configure NM or disable it.

comment:8 Changed 9 years ago by trac-robot

  • Status changed from pending 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.

comment:9 follow-up: Changed 8 years ago by kc9bcy

Why has this problem not been addressed?

comment:10 in reply to: ↑ 9 Changed 8 years ago by QuLogic

Replying to kc9bcy:

Why has this problem not been addressed?

There's nothing to address. It is a configuration problem on the reporter's computer.

comment:11 Changed 8 years ago by kc9bcy

there's still no solution here, wtf?

i don't appreciate emails that state there's nothing to resolve. Link the shit.

comment:12 Changed 8 years ago by QuLogic

Read the ticket. NetworkManager has nothing to do with Pidgin. We can't help you fix it.

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!