← Back to team overview

desktop-packages team mailing list archive

[Bug 737261] Re: Totem fails to play anything

 

Ach sorry, shmmax is the max size of one segment. 
My limits are not reached: 

ipcs -l

------ Shared Memory Limits --------
max number of segments = 4096
max seg size (kbytes) = 524288
max total shared memory (kbytes) = 8388608
min seg size (bytes) = 1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/737261

Title:
  Totem fails to play anything

Status in “totem” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: totem

  I attempted to play my entire playlist, allowing each file to load artist info, in an attempt to delete songs I often skip. The application closed without an error message, and I have not been able to play files since, although I haven't restarted yet. Totem can open, and I can go through the menus, but it can't play anything, and running it from terminal did not help locate the problem. An example output from Terminal:
  tim@Tim-Desktop-2:~$ totem
  The program 'totem' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadValue (integer parameter out of range for operation)'.
    (Details: serial 123 error_code 2 request_code 133 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.)
  tim@Tim-Desktop-2:~$ totem --sync
  The program 'totem' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadValue (integer parameter out of range for operation)'.
    (Details: serial 126 error_code 2 request_code 133 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.)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: totem 2.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic-pae 2.6.35.11
  Uname: Linux 2.6.35-27-generic-pae i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Thu Mar 17 20:45:25 2011
  ExecutablePath: /usr/bin/totem
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: totem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/737261/+subscriptions