Bug 587515 - [abrt] crash in gnome-terminal-2.28.2-1.fc12: Process /usr/bin/gnome-terminal was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnome-terminal-2.28.2-1.fc12: Process /usr/bin/gnome-terminal...
Keywords:
Status: CLOSED DUPLICATE of bug 558252
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ed64d3dd8d730dd0fb9f9359602...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-30 06:31 UTC by Richard Forster
Modified: 2010-05-25 08:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 08:34:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (8.72 KB, text/plain)
2010-04-30 06:31 UTC, Richard Forster
no flags Details

Description Richard Forster 2010-04-30 06:31:12 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gnome-terminal
comment: gnome-terminal crashes on starting the application
component: gnome-terminal
executable: /usr/bin/gnome-terminal
global_uuid: ed64d3dd8d730dd0fb9f935960235cd5f88cd732
kernel: 2.6.32.11-99.fc12.i686.PAE
package: gnome-terminal-2.28.2-1.fc12
rating: 4
reason: Process /usr/bin/gnome-terminal was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Click the gnome-terminal icon on the panel; crash report alert instantly appears.
2. Same result if I alt+F2 and type gnome-terminal into the run dialog box.
3.

Comment 1 Richard Forster 2010-04-30 06:31:14 UTC
Created attachment 410313 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 08:34:16 UTC

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

Comment 3 Karel Klíč 2010-05-25 08:34:16 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #558252.

Sorry for the inconvenience.


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