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 107158 - crash when invoking from 'Open Recent'
crash when invoking from 'Open Recent'
Status: RESOLVED DUPLICATE of bug 101678
Product: gnome-media
Classification: Deprecated
Component: Gnome-Sound-Recorder
unspecified
Other other
: Normal critical
: ---
Assigned To: Iain
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2003-02-24 05:40 UTC by gnomebugs
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description gnomebugs 2003-02-27 00:18:30 UTC 
Package: gnome-media
Severity: critical
Version: 2.2.1.1
Synopsis: crash when invoking from 'Open Recent'
Bugzilla-Product: gnome-media
Bugzilla-Component: Gnome-Sound-Recorder
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
recorder crashes on invocation when called from 'Open Recent' gnome
panel menu.

Steps to reproduce the problem:
1. gnome-sound-recorder -p antything.wav

Actual Results:
Crash dialog comes up.

Expected Results:
No crash.

How often does this happen?
Always.

Additional Information:
Using Red Hat beta at the moment.
gnome-media-2.2.1.1-4



Debugging Information:

Backtrace was generated from '/usr/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)...[New
Thread 1086634784 (LWP 1000)]
0xffffe002 in ??
    ()

+ Trace 34335

Thread 1 (Thread 1086634784 (LWP 1000))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 abort
    from /lib/tls/libc.so.6
  • #5 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib/libglib-2.0.so.0
  • #7 gst_init
    from /usr/lib/libgstreamer-0.6.so.0
  • #8 main
  • #9 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-26 19:18 -------

The original reporter (gnomebugs@cerberus.anchor.net.au) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, bugs@prettypeople.org.
Comment 1 Elijah Newren 2003-03-02 02:48:13 UTC 
Thanks for the bug report. Unfortunately, that stack trace looks like
it has been mangled/truncated.  Can you get us a more complete one? 
(http://bugzilla.gnome.org/getting-traces.cgi has instructions on how
to obtain one).
Comment 2 Elijah Newren 2003-04-23 04:20:34 UTC 
No response--closing.
Comment 3 John Davis 2003-05-01 23:48:39 UTC 
appears duplicate to 112018
Comment 4 Gregory Leblanc 2003-05-02 20:52:24 UTC 
Good catch, marking a bunch of duplicates now!

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