Bug 755036 - [abrt] roxterm-1.18.5-1.fc14: g_type_check_instance_cast: Process /usr/bin/roxterm was killed by signal 11 (SIGSEGV)
Summary: [abrt] roxterm-1.18.5-1.fc14: g_type_check_instance_cast: Process /usr/bin/ro...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: roxterm
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ec5ee90dc45b8eabf1ea0607a2a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-18 16:05 UTC by S P Arif Sahari Wibowo
Modified: 2012-08-16 12:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 12:55:21 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (15.89 KB, text/plain)
2011-11-18 16:05 UTC, S P Arif Sahari Wibowo
no flags Details

Description S P Arif Sahari Wibowo 2011-11-18 16:05:26 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 16273 bytes
cmdline: roxterm
component: roxterm
Attached file: coredump, 16277504 bytes
crash_function: g_type_check_instance_cast
executable: /usr/bin/roxterm
kernel: 2.6.35.14-103.fc14.i686
package: roxterm-1.18.5-1.fc14
rating: 4
reason: Process /usr/bin/roxterm was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1321585125
uid: 501

How to reproduce
-----
1. I had several roxterm windows with several tabs each
2. I left my computer with those roxterm windows on (behind locked screensaver) overnight.
3. The crash happened few hours after I left them.

Comment 1 S P Arif Sahari Wibowo 2011-11-18 16:05:28 UTC
Created attachment 534412 [details]
File: backtrace

Comment 2 S P Arif Sahari Wibowo 2011-11-24 16:05:34 UTC
Package: roxterm-1.18.5-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I have a couple of roxterm windows, each with multiple tabs
2. I left those roxterm windows up under screensaver
3. Roxterm crashed about 1 hour 10 minutes after being left

Comment 3 S P Arif Sahari Wibowo 2011-11-28 16:27:29 UTC
Package: roxterm-1.18.5-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I have a couple of roxterm windows, each with multiple tabs
2. I left those roxterm windows up under screensaver
3. Roxterm crashed about 1 hour 45 minutes after being left

Comment 4 S P Arif Sahari Wibowo 2011-12-01 16:54:30 UTC
Package: roxterm-1.18.5-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I woke up my computer, the Roxterm was still up from last night
2. I started to work on Roxterm, on a tab with alpine up
3. Roxterm suddenly crashed

Comment 5 S P Arif Sahari Wibowo 2011-12-06 15:40:39 UTC
Package: roxterm-1.18.5-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Couple of windows, several tabs each
2. Left overnight under screensaver.
3. Crashed several hours after being left.

Comment 6 S P Arif Sahari Wibowo 2011-12-09 15:42:42 UTC
Package: roxterm-1.18.5-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. 2 windows multiple tab each.
2. Left behind screensaver.
3. Crashed several hours after.

Comment 7 S P Arif Sahari Wibowo 2011-12-13 15:53:37 UTC
Package: roxterm-1.18.5-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. 2 roxterm windows, multiple tabs each
2. left overnight behind screensaver
3. crashed many hours later (14 hours+)

Comment 8 S P Arif Sahari Wibowo 2011-12-15 17:57:33 UTC
Package: roxterm-1.18.5-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. 2 roxterm windows, multiple tabs
2. left overnight under screensaver
3. crashed just when I relogin 17+ hours after being left

Comment 9 Fedora End Of Life 2012-08-16 12:55:27 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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