#include <hallo.h>
* Darren Salt [Wed, Mar 29 2006, 05:32:47PM]:
> retitle 359815 gxine occupies all virtual desktops
> thanks
> 
> I demand that Richard Thrippleton may or may not have written...

> > annoying). I suspect it's a cross-wm issue, as there's a standard window
> > property for 'occupy all virtual desktops',  but if it helps I'm running
> > icewm.

It is not reproducible for me with default icewm settings (you can tune
it to identify gxine and change the settings, of course). I just
installed gxine, started, no such problems. I will attach my xprop
output if you wish to compare.

> This is repeatable here. However, gxine is definitely calling
> gtk_window_unstick() for the window (the same window is used for both display
> modes).

Ooookay... more details please. Icewm version, custom configuration, etc.




Btw, the first time I started it and began to play an AVI (freely
available AVI trailer of Star Wreck, if you want to reproduce it).

lirc: Kann nicht initialisieren - Fernbedienung deaktiviert
lirc: Evtl. läuft lircd nicht oder der Socket kann nicht verbunden werden?
  sysname: Linux
  release: 2.6.16-rc6-686
  machine: i686
X-Video Extension version 2.2
video_out_xv: Xv image format: 0x32595559 (YUY2) packed
video_out_xv: this adaptor supports the yuy2 format.
video_out_xv: Xv image format: 0x32315659 (YV12) planar
video_out_xv: this adaptor supports the yv12 format.
video_out_xv: Xv image format: 0x59565955 (UYVY) packed
video_out_xv: Xv image format: 0x30323449 (I420) planar
ioctl(): Eingabe-/Ausgabefehler
ERROR: error reading Info sector (150)
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 3092 error_code 8 request_code 138 minor_code 6)
  (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.)

Eduard.

Reply via email to