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 552510 - crash in Movie Player: Moviendo un video hacia ...
crash in Movie Player: Moviendo un video hacia ...
Status: RESOLVED DUPLICATE of bug 527572
Product: totem
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-09-16 15:40 UTC by diegopalomo
Modified: 2008-09-16 17:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description diegopalomo 2008-09-16 15:40:42 UTC 
Version: 2.22.2

What were you doing when the application crashed?
Moviendo un video hacia delante


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

System: Linux 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 174268416 vsize: 174268416 resident: 60047360 share: 26370048 rss: 60047360 rss_rlim: 4294967295
CPU usage: start_time: 1221579579 rtime: 271 utime: 237 stime: 34 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb67e3720 (LWP 15249)]
[New Thread 0xafa30b90 (LWP 15267)]
[New Thread 0xb155ab90 (LWP 15266)]
[New Thread 0xb2814b90 (LWP 15265)]
[New Thread 0xb307db90 (LWP 15261)]
[New Thread 0xb39ffb90 (LWP 15260)]
[New Thread 0xb54eeb90 (LWP 15257)]
[New Thread 0xb6192b90 (LWP 15253)]
0xb7f12424 in __kernel_vsyscall ()

+ Trace 206847

Thread 4 (Thread 0xb2814b90 (LWP 15265))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 ??
  • #8 volume_transform_ip
    at gstvolume.c line 709
  • #9 gst_base_transform_handle_buffer
    at gstbasetransform.c line 1446
  • #10 gst_base_transform_chain
    at gstbasetransform.c line 1590
  • #11 gst_pad_chain_unchecked
    at gstpad.c line 3523
  • #12 gst_pad_push
    at gstpad.c line 3691
  • #13 gst_base_transform_chain
    at gstbasetransform.c line 1610
  • #14 gst_pad_chain_unchecked
    at gstpad.c line 3523
  • #15 gst_pad_push
    at gstpad.c line 3691
  • #16 gst_base_transform_chain
    at gstbasetransform.c line 1610
  • #17 gst_pad_chain_unchecked
    at gstpad.c line 3523
  • #18 gst_pad_push
    at gstpad.c line 3691
  • #19 gst_proxy_pad_do_chain
    at gstghostpad.c line 193
  • #20 gst_pad_chain_unchecked
    at gstpad.c line 3523
  • #21 gst_pad_push
    at gstpad.c line 3691
  • #22 gst_queue_loop
    at gstqueue.c line 1021
  • #23 gst_task_func
    at gsttask.c line 192
  • #24 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.16.5/glib/gthreadpool.c line 265
  • #25 g_thread_create_proxy
    at /tmp/buildd/glib2.0-2.16.5/glib/gthread.c line 635
  • #26 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #27 clone
    from /lib/i686/cmov/libc.so.6 




----------- .xsession-errors ---------------------
  <interface>
    <addr>192.168.2.1</addr>
    <bcast>192.168.2.255</bcast>
    <dev>eth0</dev>
    <enabled>1</enabled>
    <hwaddr>00:15:f2:16:ba:79</hwaddr>
    <mask>255.255.255.0</mask>
    <type>ethernet</type>
  </interface>
</network-ifaces>
<!-- GST: end of request -->
Cannot access memory at address 0x80
Cannot access memory at address 0x80
--------------------------------------------------
Comment 1 Philip Withnall 2008-09-16 17:00:53 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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