[Bug 15900] New: totem doesn't want to start

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=15900
Ubuntu | totem-xine

           Summary: totem doesn't want to start
           Product: Ubuntu
           Version: unspecified
          Platform: Other
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: totem-xine
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: capitanterrex at yahoo.es
         QAContact: desktop-bugs at lists.ubuntu.com


(in daily-updated breezy)
I know why but two or three days ago totem is broken. If I start it from GNOME
menu, all of window borders of all applications disappear and appear again
(metacity?); and totem is not shown (neither the ps command show the totem
process). I've removed ~/.totem*, ~/gconf/apps/totem and
~/gnome/apps/gnome-settings/totem with the same results. Starting it from
console dump this output:

$ totem

(totem:20287): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion
`gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

(totem:20287): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion
`gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
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 1164 error_code 11 request_code 53 minor_code 0)
  (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.)

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.