totem no longer plays movies after resolution has been changed

valeri@valeri-laptop:~$ totem &
[1] 3169
valeri@valeri-laptop:~$ /var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
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 130 error_code 11 request_code 132 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.)

[1]+ Exit 1 totem
valeri@valeri-laptop:~$ totem --sync &
[1] 3691
valeri@valeri-laptop:~$ /var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
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 82 error_code 11 request_code 132 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.)

___________________________________________________________________________________________

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.

Hi ,

This is what I mananged to get as an additional info:

valeri@valeri-laptop:~$ totem &
[1] 3169
valeri@valeri-laptop:~$ /var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
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 130 error_code 11 request_code 132 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.)

[1]+  Exit 1                  totem
valeri@valeri-laptop:~$ totem --sync &
[1] 3691
valeri@valeri-laptop:~$ /var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
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 82 error_code 11 request_code 132 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.)

Best Regards
Valeri

________________________________
From: Pedro Villavicencio <email address hidden>
To: <email address hidden>
Sent: Wednesday, 8 April, 2009 22:21:43
Subject: [Bug 357824] Re: totem no longer plays movies after resolution has been changed

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.

** Changed in: totem (Ubuntu)
  Importance: Undecided => Medium

** Changed in: totem (Ubuntu)
      Status: New => Incomplete

** Changed in: totem (Ubuntu)
    Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)

--
totem no longer plays movies after resolution has been changed
https://bugs.launchpad.net/bugs/357824
You received this bug notification because you are a direct subscriber
of the bug.

Status in “totem” source package in Ubuntu: Incomplete

Bug description:
Binary package hint: totem

Hi all,
I have installed UBUNTU 9.04 yesterday and tried out totem (mplayer).. It worked OK when it was on the  LCD display(1280x800) of my laptop. After that I switched to an external monitor with resolution (1680x1050). After that totem stopped working  - tries to resize the window, but apparenly fails and then sometimes I'm asked to relogin or when Automatic resize is turned off it silently exits. I tried to set back the resolution to the previous value to see if this would help somehow, but it does not...

Okay I don't know if this helps anyone but I found a way around it that worked for me. I'm on a Toshiba Satellite A135-S4427 Store bought config. I upgraded today and had the same problem... I went to System => Preferences => Multimedia System Selector and changed the video output to something other than auto detect and everything worked again. Don't know if this helps anyone but it worked for me. Thanks for everthing

I meet the same problem.

I find a temporarily solution for this: change your video card driver to "vesa" , then totem works.

------
My video card is Intel 865G, and I hear Intel video card driver does not work well in 9.04. So I guess this may be the cause. So I boot my system in my friend's computer (a Nvidia video card in his computer), totem work well. This support my conjecture. Then I add "driver "vesa"" to "device" section in xorg.conf, restart X, totem works.

-----

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.