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 172070 - crashes when tying to test
crashes when tying to test
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
0.3.3
Other other
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-30 06:45 UTC by runemysta
Modified: 2005-04-30 01:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description runemysta 2005-03-30 06:45:29 UTC 
Distribution: Fedora Core release 3 (Heidelberg)
Package: gnome-utils
Severity: normal
Version: GNOME2.8.0 2.8.0
Gnome-Distributor: Red Hat, Inc
Synopsis: crashes when tying to test
Bugzilla-Product: gnome-utils
Bugzilla-Component: gdict
Bugzilla-Version: 2.8.0
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/gstreamer-properties'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-30 01:45 -------


Unknown version 2.8.0 in product gnome-utils.  Setting version to "unspecified".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-utils".
   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 runemysta@westnet.com.au.
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.
Comment 1 Elijah Newren 2005-03-30 15:48:50 UTC 
Thanks for the bug report. It appears that the stack trace didn't make it.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you provide us iwth one? Please see http://live.gnome.org/GettingTraces for
more information on how to do so.
Comment 2 Elijah Newren 2005-04-30 01:01:59 UTC 
No response--closing; feel free to reopen if you can provide the requested
information.