Bug 746143 - [abrt] gnotime-2.3.0-7.fc14: IA__gtk_widget_hide: Process /usr/bin/gnotime was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnotime-2.3.0-7.fc14: IA__gtk_widget_hide: Process /usr/bin/gnotime wa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnotime
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2fa6269a6c22a6d40cac937b232...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-14 04:04 UTC by Alfred Reaud
Modified: 2012-02-02 14:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-02 14:44:41 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (18.52 KB, text/plain)
2011-10-14 04:04 UTC, Alfred Reaud 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Alfred Reaud 2011-10-14 04:04:05 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 18964 bytes
cmdline: gnotime
comment: Part two above occurred more than once in this instance. Closing activity report and reopening it resloved the entry issue. Intermittent problem. Has occurred previously without crashing gnotime.
component: gnotime
Attached file: coredump, 23601152 bytes
crash_function: IA__gtk_widget_hide
executable: /usr/bin/gnotime
kernel: 2.6.35.14-97.fc14.i686
package: gnotime-2.3.0-7.fc14
rating: 4
reason: Process /usr/bin/gnotime was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1318564512
uid: 500

How to reproduce
-----
1. Inserting time entries into activity report 1 dairy entry before top entry.
2. Clicking apply had no effect on dairy entry.
3. Attempting to close activity report crashed gnotime.
Comment 1 Alfred Reaud 2011-10-14 04:04:07 UTC 
Created attachment 528149 [details]
File: backtrace
Comment 2 Gwyn Ciesla 2012-02-02 14:44:41 UTC 
Fedora 14 is End-of-Life, please reopen against a current release if this bug is still occurring.  Thank you!
Note You need to log in before you can comment on or make changes to this bug.