pedrotuga
May 12th, 2009, 07:47 PM
After the upgrade to jaunty, miro shuts down each time I try to play a file.
I google a bit and a couple of people apparently fixed the problem by removing some old repository. I believe that is not my case since I don't have any third party repository besides skype.
Here's my sources.list if necessary:
http://pastebin.ca/raw/1420767
Here's the error message I get when I run miro from the console.
The program 'miro.real' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 134 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.)
Any tips?
EDIT:
Ok, turns out that is not only miro. I've tryed to open a file with VLC and got this error message:
[????????] x11 video output error: X11 request 132.19 failed with error code 11:
BadAlloc (insufficient resources for operation)
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 132 (XVideo)
Minor opcode of failed request: 19 ()
Serial number of failed request: 81
Current serial number in output stream: 82
I google a bit and a couple of people apparently fixed the problem by removing some old repository. I believe that is not my case since I don't have any third party repository besides skype.
Here's my sources.list if necessary:
http://pastebin.ca/raw/1420767
Here's the error message I get when I run miro from the console.
The program 'miro.real' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 134 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.)
Any tips?
EDIT:
Ok, turns out that is not only miro. I've tryed to open a file with VLC and got this error message:
[????????] x11 video output error: X11 request 132.19 failed with error code 11:
BadAlloc (insufficient resources for operation)
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 132 (XVideo)
Minor opcode of failed request: 19 ()
Serial number of failed request: 81
Current serial number in output stream: 82