Bug 713760 - [abrt] hamster-applet-2.32.0-3.fc14: PyObject_SetAttrString: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] hamster-applet-2.32.0-3.fc14: PyObject_SetAttrString: Process /usr/bin...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: hamster-applet
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mads Villadsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f0283f9335bd617b73b288a5a0b...
: 700332 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-16 13:57 UTC by Juan Carlos Watts
Modified: 2012-08-16 14:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:14:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (78.50 KB, text/plain)
2011-06-16 13:57 UTC, Juan Carlos Watts
no flags Details
File: backtrace (162.62 KB, text/plain)
2012-02-21 11:48 UTC, Steve Dowe
no flags Details

Description Juan Carlos Watts 2011-06-16 13:57:21 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 80385 bytes
cmdline: python /usr/bin/hamster-time-tracker
component: hamster-applet
Attached file: coredump, 29577216 bytes
crash_function: PyObject_SetAttrString
executable: /usr/bin/python
kernel: 2.6.35.13-91.fc14.i686.PAE
package: hamster-applet-2.32.0-3.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1308232189
uid: 500

How to reproduce
-----
1.Try to sync gtg with time tracker usin hammtel
2.
3.

Comment 1 Juan Carlos Watts 2011-06-16 13:57:23 UTC
Created attachment 505051 [details]
File: backtrace

Comment 2 Steve Dowe 2012-02-21 11:48:38 UTC
Tried to edit (clicking on the edit button of) a previously recorded time entry.

backtrace_rating: 4
Package: hamster-applet-2.32.1-1.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment 3 Steve Dowe 2012-02-21 11:48:42 UTC
Created attachment 564660 [details]
File: backtrace

Comment 4 abrt-bot 2012-03-20 16:54:22 UTC
Backtrace analysis found this bug to be similar to some already closed bugs from other components. You might want to check those bugs for additional information.

Bugs which were found to be similar to this bug: 
  abrt: bug #542135, bug #659179
  blueman: bug #587960, bug #642462
  dbus-python: bug #562109, bug #585725

This comment is automatically generated.

Comment 5 abrt-bot 2012-03-30 15:30:39 UTC
*** Bug 700332 has been marked as a duplicate of this bug. ***

Comment 6 Fedora End Of Life 2012-08-16 14:14:59 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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


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