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 340308 - Crash: Splash graphic is too big for some X drivers
Crash: Splash graphic is too big for some X drivers
Status: RESOLVED DUPLICATE of bug 135045
Product: totem
Classification: Core
Component: xine-lib backend
1.4.x
Other Linux
: Normal critical
: ---
Assigned To: Maintainer alias for xine-lib component of Totem
Maintainer alias for xine-lib component of Totem
Depends on:
Blocks:
 
 
Reported: 2006-05-01 16:37 UTC by John Spray
Modified: 2006-05-01 20:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John Spray 2006-05-01 16:37:36 UTC
The sympton is that when I start totem on its own, it shows a blue window and immediately terminates with a message like "The error was 'BadAlloc (insufficient resources for operation)'.\n(Details: serial 69 error_code 11 request_code 141 minor_code 19)".  However, opening a video using totem (like "totem foo.avi") works correctly.

Totem starts correctly on its own if I do "mogrify -resize 50% /usr/share/totem/totem_logo.png".

Using the i810 x.org driver, there appears to be a limitation on the resolution available to xv programs.  The totem_logo.png file appears to be very high resolution, and exceeds this limit on my system.

I would suggest that the image is oversized at 1280x1024: shipping a lower resolution version isn't going to bother anyone.  Even if this is really a bug in xine-lib or X.org, this trivial fix should be made, since latest totem is completely broken on some very common hardware.

I have this problem on both an IBM Thinkpad R50, and on a Dell Dimension 3000.
Comment 1 Bastien Nocera 2006-05-01 20:08:55 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.


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