Bug 695099 - [abrt] gnome-pilot-2.32.1-1.fc14: vasprintf: Process /usr/bin/gpilotd-control-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-pilot-2.32.1-1.fc14: vasprintf: Process /usr/bin/gpilotd-control...
Keywords:
Status: CLOSED DUPLICATE of bug 701139
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-pilot
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:21f45815c30704e48c0cec8f19f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-10 14:40 UTC by Chris
Modified: 2012-03-30 11:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 11:59:14 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (206.92 KB, text/plain)
2011-04-10 14:40 UTC, Chris
no flags Details

Description Chris 2011-04-10 14:40:32 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 211889 bytes
cmdline: gpilotd-control-applet --druid
component: gnome-pilot
Attached file: coredump, 974848 bytes
crash_function: vasprintf
executable: /usr/bin/gpilotd-control-applet
kernel: 2.6.35.11-83.fc14.i686
package: gnome-pilot-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/gpilotd-control-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302398513
uid: 500

How to reproduce
-----
1.Not sure it comes up when i start the program.
2.
3.

Comment 1 Chris 2011-04-10 14:40:34 UTC
Created attachment 491079 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-30 11:59:14 UTC
Backtrace analysis found this bug to be similar to bug #701139, closing as duplicate.

Bugs which were found to be similar to this bug: 
  gnome-pilot: bug #654510, bug #664674, bug #701139
  menu-cache: bug #556296, bug #558303
  rygel: bug #667231

This comment is automatically generated.

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


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