Immediate crash after Start of Totem

[Tiefflieger]

Binary package hint: totem

Appeared on up-to-date Intrepid 64bit
When I try to open any Video, e.g. the one in the Attachment, Totem crashes. Running from the console, I get the following:

///////////////////////////////////////////////
me@me-desktop:~$ totem
** (totem:7911): DEBUG: Init of Python module
** (totem:7911): DEBUG: Registering Python plugin instance: BBCViewer+TotemPythonPlugin
** (totem:7911): DEBUG: Creating object of type BBCViewer+TotemPythonPlugin
** (totem:7911): DEBUG: Creating Python plugin instance
** (totem:7911): DEBUG: Init of Python module
** (totem:7911): DEBUG: Registering Python plugin instance: YouTube+TotemPythonPlugin
** (totem:7911): DEBUG: Creating object of type YouTube+TotemPythonPlugin
** (totem:7911): DEBUG: Creating Python plugin instance
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 73 error_code 11 request_code 141 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.)

////////////////////////////////////////////////

The problem occurs with any video, the video in the attachment was taken with a Canon Ixus 65, encoded with OggConvert with default settings. It is about a second long.

[goto (gotolaunchpad)]

I tried to reproduce it and here it works (64 bit Intrepid). What graphical driver do you use?

[Tiefflieger (tiefflieger)]

Nvidia v177, installed via ubuntu's hardware-manager

After a restart, it works again - but I was having this problem several times before, so I guess it's because of something I do before I start totem.
I will try to reproduce the error and give any informations that may be helpfull for this report.

[Tiefflieger (tiefflieger)]

Totem crashes again in the session I'm currently on. All I did was logon, start evolution, firefox3 and google-earth.
I don't know if its of any matter, but sometimes (just like right now) my google-earth is far too slow to use it (aproximatly 1 frame per 3 seconds). So maybe its really related to my video driver?
(I'm using nvidia v177.82 installed via hardware-drivers on 64 bit Ubuntu)
the only errors in /var/log/Xorg.0.log are the following lines:

(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)

everything else seems to work just fine, I appreciate any help on how I could track down the source of my problem :-)

[Tiefflieger (tiefflieger)]

I added 3 log-files. From /var/log/gdm the two most recent files and the complete /var/log/Xorg.0.log, maybe thats of any help... :-/

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Tiefflieger (tiefflieger)]

There you are :-)
But I don't think they are really of great help :-/
the first one where created like described at https://wiki.ubuntu.com/Backtrace#Generation , the program said I should run it with --sync as parameter, so I did that and created a second trace.
First time I've done this, maybe I've done something wrong?

[Tiefflieger (tiefflieger)]

I don't know what a valgrind is, but made one according to https://wiki.ubuntu.com/Valgrind ;-)

[Pedro Villavicencio (pedro)]

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.