Bug 628418

Summary: [abrt] gwibber-1:2.31.4-1.fc14: threading.py:473:start:error: can't start new thread
Product: [Fedora] Fedora Reporter: cleiton Lima <cleitoncfl>
Component: gwibberAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:bbe718d2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-30 13:53:01 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:
Attachments:
Description Flags
File: backtrace none

Description cleiton Lima 2010-08-30 01:02:33 UTC 
abrt version: 1.1.13
architecture: i686
cmdline: /usr/bin/python /usr/bin/gwibber-service
component: gwibber
executable: /usr/bin/gwibber-service
kernel: 2.6.35.4-12.fc14.i686
package: gwibber-1:2.31.4-1.fc14
reason: threading.py:473:start:error: can't start new thread
release: Fedora release 14 (Laughlin)
time: 1283129874
uid: 500

backtrace
-----
threading.py:473:start:error: can't start new thread

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/gwibber/microblog/dispatcher.py", line 530, in refresh
    MapAsync(perform_operation, operations, self.loading_complete, self.loading_failed)
  File "/usr/lib/python2.7/site-packages/gwibber/microblog/dispatcher.py", line 214, in __init__
    self.start()
  File "/usr/lib/python2.7/threading.py", line 473, in start
    _start_new_thread(self.__bootstrap, ())
error: can't start new thread

Local variables in innermost frame:
self: <MapAsync(Thread-515, initial daemon)>
Comment 1 cleiton Lima 2010-08-30 01:02:36 UTC 
Created an attachment (id=441866)
File: backtrace
Comment 2 Tom "spot" Callaway 2010-08-30 13:53:01 UTC 

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