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 554906 - Crash in gst_dvd_read_src_goto_title
Crash in gst_dvd_read_src_goto_title
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
0.10.x
Other All
: High critical
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-03 18:42 UTC by gamingtechnology
Modified: 2011-04-13 04:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description gamingtechnology 2008-10-03 18:42:34 UTC
Version: 2.22.2

What were you doing when the application crashed?
I opened Totem Movie Player and chose to Play my Disc from the menu and then it opened Bug Buddy on its own after crashing.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-amd64 #1 SMP Wed Sep 10 15:31:12 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: SphereCrystal

Memory status: size: 406405120 vsize: 406405120 resident: 28336128 share: 15949824 rss: 28336128 rss_rlim: 18446744073709551615
CPU usage: start_time: 1223059266 rtime: 42 utime: 30 stime: 12 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f84e9a8e790 (LWP 6717)]
[New Thread 0x42467950 (LWP 6732)]
[New Thread 0x41c66950 (LWP 6719)]
0x00007f84e5801d29 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0

Thread 2 (Thread 0x42467950 (LWP 6732))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.5/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.5/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
    from /usr/lib/libdvdread.so.3
  • #7 ifoOpen
    from /usr/lib/libdvdread.so.3
  • #8 gst_dvd_read_src_goto_title
    at dvdreadsrc.c line 462
  • #9 gst_dvd_read_src_create
    at dvdreadsrc.c line 895
  • #10 gst_base_src_get_range
    at gstbasesrc.c line 1776
  • #11 gst_base_src_loop
    at gstbasesrc.c line 2018
  • #12 gst_task_func
    at gsttask.c line 192
  • #13 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.16.5/glib/gthreadpool.c line 265
  • #14 g_thread_create_proxy
    at /build/buildd/glib2.0-2.16.5/glib/gthread.c line 635
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6
  • #17 ??




----------- .xsession-errors ---------------------
*** libdvdread: CHECK_VALUE failed in ifo_read.c:1575 ***
*** for c_adt->cell_adr_table[i].start_sector < c_adt->cell_adr_table[i].last_sector ***
*** libdvdread: CHECK_VALUE failed in ifo_read.c:1575 ***
*** for c_adt->cell_adr_table[i].start_sector < c_adt->cell_adr_table[i].last_sector ***
*** libdvdread: CHECK_VALUE failed in ifo_read.c:1575 ***
*** for c_adt->cell_adr_table[i].start_sector < c_adt->cell_adr_table[i].last_sector ***
*** libdvdread: CHECK_VALUE failed in ifo_read.c:1575 ***
*** for c_adt->cell_adr_table[i].start_sector < c_adt->cell_adr_table[i].last_sector ***
--------------------------------------------------
Comment 1 Philip Withnall 2008-10-06 22:09:47 UTC
Looks like a GStreamer problem.
Comment 2 Stefan Sauer (gstreamer, gtkdoc dev) 2011-03-02 11:13:03 UTC
I think this is from libdvdread.so.3. Can we please get a backtrace with libdvdread debug symbols? Is it happening with a particualt DVD only or several (name one where it happens). Finally which is the libdvdread version?
Comment 3 Akhil Laddha 2011-04-13 04:58:41 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!