Bug 638984

Summary: pino-0.2.11-1 doesn't update after adding accounts
Product: [Fedora] Fedora Reporter: Destinatus <elfyn>
Component: pinoAssignee: Filipe Rosset <rosset.filipe>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: metherid, rosset.filipe, supercyper1
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-01 19:03:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Destinatus 2010-09-30 14:49:10 UTC 
Description of problem:

After adding two accounts (for Twitter and identi.ca) pino just sits there doing nothing with "updating..." in the status bar. the UI is responsive so it hasn't hung, but beyond that it's not at all useful.

Version-Release number of selected component (if applicable):

Name        : pino
Arch        : x86_64
Version     : 0.2.11
Release     : 1.fc14
Size        : 715 k
Repo        : installed
From repo   : anaconda-InstallationRepo-201009210339.x86_64

How reproducible:

Easily reproducible on a number of different systems (i686, x86_64). This has happened every time I've installed F14 Alpha through Beta, so that's at least six seperate installations. In this last instance, pino has been spinning for roughly 30 minutes - still nothing.

Steps to Reproduce:
1. Install and execute /usr/bin/pino
2. Add an account.
  
Actual results:

pino never makes it past the "updating..." phase.

Expected results:

Streams fetched, displayed etc.

Additional info:

I've tried running pino in a terminal to see if there's any output on stdout/stderr, but it seemingly does a "fork()" followed by a "setsid()", so there is no output for me to look for.
Comment 1 Destinatus 2010-10-01 19:03:03 UTC 

*** This bug has been marked as a duplicate of bug 629192 ***