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 145735 - After double cliking on wave file a fatal error occurs
After double cliking on wave file a fatal error occurs
Status: RESOLVED DUPLICATE of bug 101678
Product: gnome-control-center
Classification: Core
Component: Sound
unspecified
Other other
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-13 10:55 UTC by Carlos L. Diaz
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description Carlos L. Diaz 2004-07-08 18:24:04 UTC
Package: control-center
Severity: normal
Version: GNOME2.2.0 2.2.1.1
os_details: Gnome.Org
Synopsis: After double cliking on wave file a fatal error occurs
Bugzilla-Product: control-center
Bugzilla-Component: sound
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:

After double cliking on wave file a fatal error occurs
Steps to reproduce the problem:
1. double click on .wav file on my windows drive
2. 
3. 

Actual Results:
Fatal Crash	

Expected Results:
Music being played.


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/opt/gnome2/bin/gnome-sound-recorder'

(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)...[New
Thread 16384 (LWP 2666)]

(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)...
0x40a05cf7 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 2666))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /opt/gnome2/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 kill
    from /lib/libc.so.6
  • #5 pthread_kill
    from /lib/libpthread.so.0
  • #6 raise
    from /lib/libpthread.so.0
  • #7 raise
    from /lib/libc.so.6
  • #8 abort
    from /lib/libc.so.6
  • #9 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/lib/libglib-2.0.so.0
  • #11 gst_init
    from /opt/gnome2/lib/libgstreamer-0.6.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/libc.so.6
  • #0 waitpid
    from /lib/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 14:24 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "control-center".
   Setting to default milestone for this product, '---'
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 2004-11-08 19:42:43 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

Matches the stack trace in bug 122273, which has been marked as a duplicate of
101678.

*** This bug has been marked as a duplicate of 101678 ***