Bug 805523 - Sugar collaboration connections are started in GNOME, hidden from view
Sugar collaboration connections are started in GNOME, hidden from view
Product: Fedora
Classification: Fedora
Component: sugar (Show other bugs)
All Linux
unspecified Severity medium
: ---
: ---
Assigned To: Simon Schampijer
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-21 10:08 EDT by Samuel Greenfeld
Modified: 2013-08-01 06:54 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 06:54:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Samuel Greenfeld 2012-03-21 10:08:00 EDT
Description of problem:
The Sugar collaboration connections are started while in GNOME 3, but not shown from GNOME 3's control panel.

This results in error messages occasionally popping up stating these connections cannot be started (due to network issues) and the occasional person randomly trying to chat with you from the {default} Sugarlabs Jabber collaboration server.

Running "empathy-accounts" will show the connections; 

How reproducible: Seems close to always.

Steps to Reproduce:
1. Install both Sugar and GNOME 3 environments on a F17 or F16 machine.
2. Use both Sugar & Sugar-emulator for a bit.
3. Switch back to GNOME.
Actual results: Sugar collaboration connections are often active in GNOME.

Expected results: Sugar collaboration connections should not be active in GNOME.
Comment 1 Fedora End Of Life 2013-07-03 23:24:37 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.
Comment 2 Fedora End Of Life 2013-08-01 06:54:19 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.