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 446069 - crash in Movie Player: Opened an .rm file while...
crash in Movie Player: Opened an .rm file while...
Status: RESOLVED DUPLICATE of bug 423668
Product: totem
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-06-10 16:12 UTC by Øystein
Modified: 2007-06-10 19:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Øystein 2007-06-10 16:12:11 UTC
Version: 2.18.1

What were you doing when the application crashed?
Opened an .rm file while listening to an .mp3 file


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 184770560 vsize: 184770560 resident: 32346112 share: 13926400 rss: 32346112 rss_rlim: 4294967295
CPU usage: start_time: 1181491681 rtime: 2503 utime: 2457 stime: 46 cutime:13 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208849808 (LWP 2910)]
[New Thread -1340507248 (LWP 2951)]
[New Thread -1330017392 (LWP 2950)]
[New Thread -1319527536 (LWP 2949)]
[New Thread -1301660784 (LWP 2948)]
[New Thread -1290798192 (LWP 2947)]
[New Thread -1247786096 (LWP 2946)]
[New Thread -1221350512 (LWP 2945)]
[New Thread -1268765808 (LWP 2943)]
[New Thread -1279255664 (LWP 2941)]
[New Thread -1231840368 (LWP 2913)]
(no debugging symbols found)
0x00fca402 in __kernel_vsyscall ()

Thread 10 (Thread -1279255664 (LWP 2941))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gst_adapter_flush
    from /usr/lib/libgstbase-0.10.so.0
  • #5 ??
    from /usr/lib/gstreamer-0.10/libgstrmdemux.so
  • #6 ??
    from /usr/lib/gstreamer-0.10/libgstrmdemux.so
  • #7 ??
    from /usr/lib/libgstreamer-0.10.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6


----------- .xsession-errors (6 sec old) ---------------------
** (totem:2910): WARNING **: Add decoder gsm (86037) please
** (totem:2910): WARNING **: Add decoder gsm_ms (86049) please
** (totem:2910): WARNING **: Add decoder mpc sv7 (86047) please
** (totem:2910): WARNING **: Add decoder smackaud (86042) please
** (totem:2910): WARNING **: Add decoder wavpack (86044) please
** (totem:2910): WARNING **: Add decoder adpcm_thp (69650) please
** Message: don't know how to handle audio/x-sipro, flavor=(int)1, rate=(int)8000, channels=(int)1, width=(int)16, leaf_size=(int)0, packet_size=(int)304, height=(int)6
** Message: don't know how to handle audio/x-sipro, flavor=(int)0, rate=(int)8000, channels=(int)1, width=(int)16, leaf_size=(int)0, packet_size=(int)232, height=(int)6
** Message: don't know how to handle audio/x-sipro, flavor=(int)0, rate=(int)8000, channels=(int)1, width=(int)16, leaf_size=(int)0, packet_size=(int)232, height=(int)6
--------------------------------------------------
Comment 1 Philip Withnall 2007-06-10 19:38:00 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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