FS#7026 - gxine crashing on startup

Attached to Project: Arch Linux
Opened by Rob Page (robrob) - Sunday, 29 April 2007, 11:55 GMT
Last edited by Aaron Griffin (phrakture) - Monday, 04 June 2007, 21:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture All
Severity Medium
Priority Normal
Reported Version 0.8 Voodoo
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Running gxine-0.5.11-1, trying to start it, the splash screen appears then disappears gxine does not start. Running from console I get:

[rob@rob-v2 ~]$ gxine
The program 'gxine' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 288 error_code 8 request_code 139 minor_code 14)
(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.)
[rob@rob-v2 ~]$

If I try starting with the -V opengl option then it starts ok, and seems to work as normal. However, I cannot find any way to set this to the default option.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Monday, 04 June 2007, 21:54 GMT
Reason for closing:  Deferred
Additional comments about closing:  Closing this is it's more-or-less an upstream bug with gxine's handling of Xv output - please report to the gxine people
Comment by Jan de Groot (JGC) - Sunday, 29 April 2007, 12:34 GMT
You don't have enough videomemory available for XV. If you have an integrated videochipset with shared memory, allocate some more with the "VideoRAM" option in xorg.conf and XV should work fine again.
Comment by Rob Page (robrob) - Sunday, 29 April 2007, 13:27 GMT
Hi Jan,

Thanks for the comment. I'm not sure whether my graphics card uses shared memory, I can't find anything to adjust it in the BIOS though. I've uncommented the VideoRAM line in my xorg.conf, to say:
VideoRam 131072

In my xorg log i now have:
(II) fglrx(0): Video RAM override, using 131072 kB instead of 131072 kB

Also output of proc/meminfo:

[rob@rob-v2 ~]$ cat /proc/meminfo
MemTotal: 1034516 kB
MemFree: 741704 kB
Buffers: 7548 kB
Cached: 127268 kB
SwapCached: 0 kB
Active: 187988 kB
Inactive: 63600 kB
HighTotal: 129868 kB
HighFree: 260 kB
LowTotal: 904648 kB
LowFree: 741444 kB
SwapTotal: 771080 kB
SwapFree: 771080 kB
Dirty: 124 kB
Writeback: 0 kB
AnonPages: 116856 kB
Mapped: 43272 kB
Slab: 12696 kB
SReclaimable: 5644 kB
SUnreclaim: 7052 kB
PageTables: 1184 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 1288336 kB
Committed_AS: 397784 kB
VmallocTotal: 114680 kB
VmallocUsed: 10084 kB
VmallocChunk: 104296 kB
[rob@rob-v2 ~]$
Comment by Jan de Groot (JGC) - Sunday, 29 April 2007, 14:11 GMT
Ah, fglrx... That driver only has one XV port, so if something else uses it at the same time, you can't start a 2nd application using XV. This happens when you have two movies running at the same time, or you have two mediaplayers opened, etc. Even the hidden totem browser plugin window that doesn't get stopped in all cases will trigger this.
Comment by Rob Page (robrob) - Sunday, 29 April 2007, 14:33 GMT
ok. I've tried running plain xine (from xine-ui) and that starts without a problem, even forcing the video output to xv works, but gxine still crashes.

For now, i've added in video.driver:opengl to .gxine/config so it defaults to the opengl driver and starts happily for now.
Comment by Aaron Griffin (phrakture) - Thursday, 17 May 2007, 05:46 GMT
Follow up - is this still an issue?
Comment by Rob Page (robrob) - Saturday, 02 June 2007, 10:26 GMT
Hi Aaron,

Sorry for the really slow response. Work and life seem to get in the way of stuff.

This isn't an issue anymore as i've changed my config file to use the opengl driver instead of xv, and it seems to work with that, however switching it back still causes the same problem.

Thanks for the response.
Rob.

Loading...