totem-gstreamer crashes when Compiz-fusion is activated (fglrx)

[joaq]

Binary package hint: totem

Ubuntu 8.10 beta amd64
ati radeon x1600
athlon64 X2 1Gb RAM

Both vlc and totem crash when opening any video or music file with compiz fusion activated
If I deactivate Compiz (Preferences -> Appearance -> Visual Effects -> Normal) both work fine

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/totem-gstreamer
Package: totem-gstreamer 2.24.2-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: totem file:///home/username/Desktop/Isabel%20coca%20Sarli%20-%20El%20trueno%20entre%20las%20hojas.avi
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/libavcodec.so.51
 ff_mpeg4_decode_mb () from /usr/lib/libavcodec.so.51
 ?? () from /usr/lib/libavcodec.so.51
 ff_h263_decode_frame ()
 avcodec_decode_video ()
Title: totem-gstreamer crashed with SIGSEGV in ff_mpeg4_decode_mb()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

The crash seems to be a ffmpeg one there, do you get it on any video? could you attach an example to the bug?

[joaq (joacococo)]

I'm not a developer and this is my first bug report i dont know if a am doing well

I opened totem with GDB and then File -> Open -> almost any supported file and then exits suddenly

This is the backtrace with GDB:

GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(gdb) run
Starting program: /usr/bin/totem
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffc1e084790 (LWP 6604)]
[New Thread 0x41485950 (LWP 6608)]
[New Thread 0x42036950 (LWP 6609)]
[New Thread 0x42837950 (LWP 6610)]
[Thread 0x42837950 (LWP 6610) exited]
[New Thread 0x42837950 (LWP 6611)]
[New Thread 0x43038950 (LWP 6612)]
[New Thread 0x43839950 (LWP 6613)]
[New Thread 0x4403a950 (LWP 6614)]
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 46 error_code 11 request_code 140 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[New Thread 0x4483b950 (LWP 6615)]
[New Thread 0x4503c950 (LWP 6616)]
[New Thread 0x4583d950 (LWP 6617)]

Program exited with code 01.

[Reinhard Tartler (siretart)]

joaq <email address hidden> writes:

> I'm not a developer and this is my first bug report i dont know if a am
> doing well

The approach is OK, however your crash is totally unrelated to this
bug. This bug is about a crash in ffmpeg playing an mpeg4 file. You are
most probably seeing a bug or limitation in your video driver. Please
file a seperate bug about that.

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

[Reinhard Tartler (siretart)]

You have reported a crash that actually happened in the libavcodec or libavformat library. In order to be able to actually fix this bug, we must be able to:

1. Reproduce it;
2. Check if it happens with the latest version; and
3. Understand where it actually crashes.

You can help with the first point by attaching an example file to this bug report. Please note that a proper attachment is preferred over a link to some remote site. Remote sites that are password protected or otherwise restricted (services like rapidshare.com) are absolutely not acceptable. If your file is too large, try to reproduce with the first few MB only. See http://ffmpeg.org/bugreports.html section "Submitting Sample Media" for guidelines.

[xteejx (xteejx)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!