Bug 675423 - [abrt] task-1.9.3-1.fc14: fseek: Process /usr/bin/task was killed by signal 11 (SIGSEGV)
Summary: [abrt] task-1.9.3-1.fc14: fseek: Process /usr/bin/task was killed by signal 1...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: task
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Federico Hernandez
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2ac379ff371fa164e8d34b3c430...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-05 15:09 UTC by Patrick R McDonald
Modified: 2011-02-05 16:49 UTC (History)
2 users (show)

Fixed In Version: 1.9.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-05 16:49:57 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (15.58 KB, text/plain)
2011-02-05 15:09 UTC, Patrick R McDonald 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Patrick R McDonald 2011-02-05 15:09:30 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: task shell
comment: Repeated command outside task shell and received the same results.
component: task
crash_function: fseek
executable: /usr/bin/task
kernel: 2.6.35.10-74.fc14.x86_64
package: task-1.9.3-1.fc14
rating: 4
reason: Process /usr/bin/task was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296918455
uid: 500

How to reproduce
-----
1. Run the following command in task shell, "log project:network Transfer cable line downstairs"
2.
3.
Comment 1 Patrick R McDonald 2011-02-05 15:09:33 UTC 
Created attachment 477207 [details]
File: backtrace
Comment 2 Federico Hernandez 2011-02-05 16:49:57 UTC 
THX Patrick for taking your time and reporting this bug with all the detailed information. It is not that often that this happens. Appreciated. This is worth an attribution in the AUTHORS file.

Good news: this bug has already been fixed in the upcoming version 1.9.4 which is currently under development. We expect it to be released around March.
Note You need to log in before you can comment on or make changes to this bug.