Bug 628418 - [abrt] gwibber-1:2.31.4-1.fc14: threading.py:473:start:error: can't start new thread
Summary: [abrt] gwibber-1:2.31.4-1.fc14: threading.py:473:start:error: can't start new...
Keywords:
Status: CLOSED DUPLICATE of bug 627686
Alias: None
Product: Fedora
Classification: Fedora
Component: gwibber
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bbe718d2
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-30 01:02 UTC by cleiton Lima
Modified: 2010-08-30 13:53 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-08-30 13:53:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (604 bytes, text/plain)
2010-08-30 01:02 UTC, cleiton Lima
no flags Details

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 ***


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