Bug 632608 - [abrt] lxterminal-0.1.7-2.fc13: terminal_window_title_changed_event: Process /usr/bin/lxterminal was killed by signal 11 (SIGSEGV)
Summary: [abrt] lxterminal-0.1.7-2.fc13: terminal_window_title_changed_event: Process ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: lxterminal
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL: https://sourceforge.net/tracker/?func...
Whiteboard: abrt_hash:8bf70fbc6ceb2d0c1a0425eb717...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-10 14:50 UTC by Mark Chappell
Modified: 2010-10-30 23:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-30 23:26:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (13.23 KB, text/plain)
2010-09-10 14:50 UTC, Mark Chappell
no flags Details

Description Mark Chappell 2010-09-10 14:50:38 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: lxterminal
comment: I'd swear a terminal tab had just closed on me too...
component: lxterminal
crash_function: terminal_window_title_changed_event
executable: /usr/bin/lxterminal
kernel: 2.6.33.8-149.fc13.i686
package: lxterminal-0.1.7-2.fc13
rating: 4
reason: Process /usr/bin/lxterminal was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce: 1. Unknown had just run ssh (probably unrelated) 
time: 1284129772
uid: 500

Comment 1 Mark Chappell 2010-09-10 14:50:43 UTC
Created an attachment (id=446526)
File: backtrace

Comment 2 Mark Chappell 2010-09-10 19:16:31 UTC
Package: lxterminal-0.1.7-2.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
 


Comment
-----
Tabs did something odd just before it crashd out, the wrong tab closed. and the one that remained "hung" with "exit" at the bottom.

Comment 3 Christoph Wickert 2010-10-30 23:26:18 UTC
Thanks for reporting this crash. I have forwarded your report to the upstream
developer at
https://sourceforge.net/tracker/?func=detail&aid=3099378&group_id=180858&atid=894869
Feel free to subscribe to that bug report in order to be notified about any
updates. I will get back to you if I need more information and notify you once
the issue is resolved.

Further investigation should take place in the upstream bug report, therefor
I'm now closing this one now.


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