After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 345852 - Totem crashes during initialization
Totem crashes during initialization
Status: RESOLVED DUPLICATE of bug 135045
Product: totem
Classification: Core
Component: Movie player
1.4.x
Other All
: Normal critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-06-25 05:49 UTC by kelvin
Modified: 2006-07-17 15:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description kelvin 2006-06-25 05:49:48 UTC
Steps to reproduce:
1.clicking icon on desktop
2.clicking icon in sound and video menu
3.running sudo totem from command line


Stack trace:
** (totem:5582): WARNING **: Failed to connect to the session bus: No reply within specified time
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 72 error_code 11 request_code 140 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.)


Other information:
When firefox uses totem to open videos there is no way to stop or replay video from within firefox. You can only use the refresh button to view video again. This is annoying and really needs to be addressed.
Comment 1 Bastien Nocera 2006-07-17 15:17:47 UTC
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.

See http://bugzilla.gnome.org/show_bug.cgi?id=135045#c16 as well

*** This bug has been marked as a duplicate of 135045 ***