After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 152645 - VI Crashed gnome-terminal while gnopernicus running
VI Crashed gnome-terminal while gnopernicus running
Status: VERIFIED INCOMPLETE
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other Linux
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
AP1
Depends on:
Blocks:
 
 
Reported: 2004-09-14 18:26 UTC by tvuong
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tvuong 2004-09-14 18:26:41 UTC
While gnopernicus running with speech enabled, bring up gnome-terminal, "vi" a 
file (i.e. vi log.txt), gnome-term crashed with Error below :

Error occured in Dialog Box:
The Application "gnome-terminal" has quit unexpectedly.
You can inform the developers of what happened to help them fix it.
Or you can restart the application right now.
<Restart Application> <Close> <Inform Developers>

Steps:
1. Bring up gnopernicus
2. enable speech
3. Listen for speech
4. bring up gnome-terminal
5. vi a file (i.e. vi log.txt)

Once should see the crash by now ... 

If gnopernicus is not running, "vi" works fine with gnome-terminal.

Setups:
Fedora Core 2
gnopernicus   : 0.9.10
gnome desktop : 2.7.9
Comment 1 Dana Ormenisan 2004-09-15 08:42:33 UTC
I am not able to reproduce this crash. "vi" works fine with gnome-terminal and
gnopernicus outputs the current line content. 
Since this is a gnome-terminal crash and not a gnopernicus one, I will send this
bug to gnome-terminal for further investigations.
Comment 2 padraig.obriain 2004-09-15 14:24:15 UTC
Do you have a stack trace from the crashing process?
Comment 3 tvuong 2004-09-15 15:50:41 UTC
Dana - "vi" works fine WHEN gnopernicus (with enabled speech) IS NOT Running ...
But While gnopernicus is up and running, "vi" crashed. So this has something to 
do with gnopernicus being on and off ?

Padraig - I will try to get you a trace cuz when it crashed it closed existing 
gnome-terminal and all other gnome-terminal applications within 1 to 2 secs. 
That leaves no time to copy and paste anything. Unless you have a clever way of 
capture this trace, please let me know. Please be specific with your steps.

Comment 4 padraig.obriain 2004-09-16 07:13:13 UTC
If the crashing program drops a core file you can get the stack trace from the
core file. Otherwise run gnome-terminal in gdb from a xterm.
Comment 5 tvuong 2004-09-16 19:58:44 UTC
Here is another trace ...



Comment 6 padraig.obriain 2004-09-27 12:50:41 UTC
Without knowing what function is being called from poll it is difficult to help.
Comment 7 tvuong 2004-10-12 20:31:42 UTC
This problem is still occurred in :

gnopernicus : 0.9.12
Gnome Desktop : 2.8

Steps to reproduce 
1. Bring up gnopernicus
2. enable speech
3. Listen for speech
4. bring up gnome-terminal
5. vi a file (i.e. vi log.txt)
6. try to type something inside the file

At this point crash should exist for gnome-terminal ...
Without running gnopernicus, vi works fine. 



Comment 8 Calum Benson 2004-10-21 15:31:14 UTC
Marking as AP1 to reflect accessibility impact.
Comment 9 Calum Benson 2004-10-21 16:42:22 UTC
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.
Comment 10 padraig.obriain 2004-10-27 09:41:55 UTC
Does the patch in bug #153405 help?
Comment 11 tvuong 2004-10-28 21:30:11 UTC
This problem is still occurred in :

gnopernicus : 0.9.16
Comment 12 padraig.obriain 2004-11-10 10:28:23 UTC
I am closing this as I do not see the crash and a meaningful stack trace has not
been provided.