gnome terminal crashed unexpectedly
Submitted by trq..@..il.com
Link to original bug (#301296)
Description
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-terminal Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: gnome terminal crashed unexpectedly Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: gnome terminal crashed unexpectedly
Steps to reproduce the crash:
- i'd started the yum update from the gnome terminal
- after it finished the update the gnome terminal closed itself
How often does this happen? this is the first time it happenned
Debugging Information:
Backtrace was generated from '/usr/bin/gnome-panel'
(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xf6fe97a2 in PKCS12_key_gen_uni () from /lib/libcrypto.so.4
`#0` 0xf6fe97a2 in PKCS12_key_gen_uni () from /lib/libcrypto.so.4
`#1` 0xf68dd3d3 in ?? ()
`#2` 0xf6efea94 in ?? ()
`#3` 0xf6ec4f50 in ?? ()
`#4` 0x00006857 in ?? ()
`#5` 0xfee18580 in ?? ()
`#6` 0x00000000 in ?? ()
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-20 05:17 -------
Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-terminal". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was trqy@hotmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED INCOMPLETE