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 305112 - crash while running gnome cdplayer.
crash while running gnome cdplayer.
Status: RESOLVED INCOMPLETE
Product: totem
Classification: Core
Component: GStreamer backend
1.0.x
Other other
: High critical
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
: 305113 305151 305154 305392 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-05-22 17:00 UTC by Bill Brown
Modified: 2005-12-28 18:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bill Brown 2005-05-22 17:00:08 UTC
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: crash while running gnome cdplayer. 
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.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/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1224591552 (LWP 7512)]
[New Thread -1226273872 (LWP 7530)]
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1226273872 (LWP 7530))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-22 17:00 UTC -------


Unknown version 2.10.0 in product nautilus.  Setting version to "2.10.x".
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 wbrown@colorfulsoftware.com.

Comment 1 Martin Wehner 2005-05-22 18:33:19 UTC
Looks gstreamer related, reassigning.
Comment 2 Sebastien Bacher 2005-05-23 09:13:35 UTC
the crash seems to be due to totem-gstreamer
Comment 3 Sebastien Bacher 2005-05-23 09:18:42 UTC
*** Bug 305154 has been marked as a duplicate of this bug. ***
Comment 4 Sebastien Bacher 2005-05-23 09:18:47 UTC
*** Bug 305151 has been marked as a duplicate of this bug. ***
Comment 5 Sebastien Bacher 2005-05-23 09:19:21 UTC
the crash is due to totem-gstreamer. Does it crash while trying to get the
properties of some files? Can you get a debug backtrace
(http://live.gnome.org/GettingTraces)? 

If you use a i386 hoary installation you can find debug packages here:
http://people.ubuntu.com/~seb128/hoary_dbgdebs/totem/totem-gstreamer_1.0.1-0ubuntu1_i386.deb
http://people.ubuntu.com/~seb128/hoary_dbgdebs/gstreamer/libgstreamer0.8-0_0.8.9-1ubuntu4_i386.deb

You can install these files with "sudo dpkg -i *.deb". libglib2.0-0-dbg from the
archive is also useful to get informations on this crash.
Comment 6 Bill Brown 2005-05-23 23:27:24 UTC
Greetings:

Here is some output while running totem:

GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/totem
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224064352 (LWP 7979)]
[New Thread -1226343504 (LWP 7982)]

(totem:7979): GLib-GObject-WARNING **: gsignal.c:1716: signal `got-redirect' is
invalid for instance `0x83071f8'
[New Thread -1235801168 (LWP 7984)]
** Message: don't know how to handle video/mpeg, mpegversion=(int)1,
systemstream=(boolean)false
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1
** Message: don't know how to handle video/mpeg, mpegversion=(int)1,
systemstream=(boolean)false
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1
[Thread -1235801168 (LWP 7984) exited]

Program exited normally.
(gdb)

So far though, most of the symptoms happen when I log in.  The Xserver screen
seems to just crash out.  Are there any other traces I can send?  Thanks. 
Comment 7 Sebastien Bacher 2005-05-25 10:29:05 UTC
*** Bug 305392 has been marked as a duplicate of this bug. ***
Comment 8 Sebastien Bacher 2005-06-05 21:05:44 UTC
thanks for the comment, there is no backtrace here. When you have the "(gdb)"
line after the crash can you enter "thread apply all bt"?
Comment 9 Bastien Nocera 2005-11-23 19:21:47 UTC
This is an automated update. Your bug has been in NEEDINFO state for more than 3
months. Please reopen the bug if the problem is still current with recent
versions of Totem and that you can provide the information asked for.
If your bug has been closed wrongly, feel free to reopen it.
Comment 10 Sebastien Bacher 2005-12-28 18:46:18 UTC
*** Bug 305113 has been marked as a duplicate of this bug. ***