gnome-terminal crashed with signal 5

Bug #1289855 reported by xxvirusxx
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)
New
Undecided
Unassigned

Bug Description

1.

Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

2. installed with ubuntu

3. Testing how fast crash Ubuntu. To not crash when open multiple terminal

4. Closed opening Terminals and crash

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-terminal 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME
Date: Sat Mar 8 21:27:32 2014
ExecutablePath: /usr/bin/gnome-terminal
InstallationDate: Installed on 2014-03-07 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140228)
ProcCmdline: gnome-terminal
Signal: 5
SourcePackage: gnome-terminal
Stacktrace: No symbol table is loaded. Use the "file" command.
StacktraceTop:

Title: gnome-terminal crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
xxvirusxx (condor20-05) wrote :
information type: Private → Public Security
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0xb6d2540a in ?? ()
 #1 0xb6d66f4e in ?? ()
 #2 0x00000006 in ?? ()
 #3 0xae500fb8 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 5 (LWP 4766):
 #0 0xb7729424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x6

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Public Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.