Bug 770144 - [abrt] roxterm-1.18.5-1.fc14: __libc_message: Process /usr/bin/roxterm was killed by signal 6 (SIGABRT)
[abrt] roxterm-1.18.5-1.fc14: __libc_message: Process /usr/bin/roxterm was ki...
Product: Fedora
Classification: Fedora
Component: roxterm (Show other bugs)
i686 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dan Horák
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-12-23 10:58 EST by S P Arif Sahari Wibowo
Modified: 2011-12-23 12:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-12-23 12:07:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (18.38 KB, text/plain)
2011-12-23 10:58 EST, S P Arif Sahari Wibowo
no flags Details

  None (edit)
Description S P Arif Sahari Wibowo 2011-12-23 10:58:31 EST
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 18816 bytes
cmdline: roxterm
component: roxterm
Attached file: coredump, 15998976 bytes
crash_function: __libc_message
executable: /usr/bin/roxterm
package: roxterm-1.18.5-1.fc14
rating: 4
reason: Process /usr/bin/roxterm was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. like before, few hours after being left under screensaver.
time: 1324517776
uid: 501
Comment 1 S P Arif Sahari Wibowo 2011-12-23 10:58:34 EST
Created attachment 549367 [details]
File: backtrace
Comment 2 Christoph Wickert 2011-12-23 12:07:11 EST
As of 09 December 2011, Fedora 14 has reached its end of life for
updates and support. No further updates, including security updates and bug fixes,
are available.

For more info, please visit http://fedoraproject.org/wiki/Fedora_Release_Life_Cycle

Please use ABRT to submit a new bug if you still see this problem in Fedora 15 or 16, but I am confident that the problem has already been fixed in one of the newer packages in these Fedora releases.

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