Bug 747540 - No automatic login after network is established
Summary: No automatic login after network is established
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-20 08:32 UTC by Robert Smol
Modified: 2013-02-13 09:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 09:09:32 UTC
Type: ---


Attachments (Terms of Use)

Description Robert Smol 2011-10-20 08:32:56 UTC
Description of problem:
Even when there is a connection network established, the status is as Unavailable, I need to manually connect to IM networks.

Version-Release number of selected component (if applicable):
empathy-3.2.1-1.fc16.x86_64

How reproducible:
Have an gmail account setup and connect to network.

Steps to Reproduce:
1. Create Gmail account in empathy.
2. Connect to network
3. Manually click "Available" in the MeMenu
  
Actual results:
Not online

Expected results:
Connects automatically to all IM accounts when network is available.

Additional info:

NetworkManager-vpnc-0.9.0-1.fc16.x86_64
NetworkManager-gtk-0.9.1.90-3.git20110927.fc16.x86_64
NetworkManager-openvpn-0.9.0-1.fc16.x86_64
NetworkManager-0.9.1.90-3.git20110927.fc16.x86_64
NetworkManager-gnome-0.9.1.90-3.git20110927.fc16.x86_64
NetworkManager-openconnect-0.9.0-1.fc16.x86_64
NetworkManager-glib-0.9.1.90-3.git20110927.fc16.x86_64
NetworkManager-pptp-0.9.0-1.fc16.x86_64

Comment 1 Alan Schmidt 2012-11-14 16:09:15 UTC
This is still outstanding.

It happens on a wired network, so it's not actually a thing with wireless not being ready.

In my environment, I have it as a startup item in KDE.

I haven't tried this with anything but GTalk, so I don't know if it's protocol- or even service-specific.

I'm using a fully-patched Fedora 17 environment.

Comment 2 Alan Schmidt 2012-11-14 16:24:28 UTC
There is at least one upstream bug report at either

https://bugzilla.gnome.org/show_bug.cgi?id=685835

or

https://bugzilla.gnome.org/show_bug.cgi?id=685836

These may be duplicates of one another. They are "new" after a whole month, so I'm guessing the issue is not straightforward to duplicate.

Comment 3 Fedora End Of Life 2013-01-16 10:25:24 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-13 09:09:42 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.