[helix-maintainers] helix-player test report

[Zack Cerza]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,=20

I decided to test your helix packages on my Sid box, under KDE. I found som=
e=20
issues, which may or may not be your concern as packagers.

I used aptitude to install helix-player 1.0beta-3 from your repository. The=
re=20
were no errors during installation.

The first thing I noticed was that there was no KDE menu entry for Helix. T=
he=20
second thing I noticed was that there was no 'helix' or 'helix-player' bina=
ry=20
in /usr/bin/. I only found 'hxplay' by using 'dpkg -L helix-player' and=20
knowing what to look for. You should probably symlink /usr/bin/hxplay to=20
something more similar to the actual package name.

On switching to fullscreen mode, bad things can happen. But not the same ba=
d=20
things every time. Sometimes the video stops while the audio moves along=20
normally. Sometimes the screen turns all black while the audio continues.=20
Sometimes the video continues while the audio stops. I can usually just=20
return to windowed mode when any of these errors occur. But sometimes the=20
screen turns all black and the audio "stops" - except for an occasional=20
crackling sound not unlike what old records on a turntable produce - and al=
l=20
I can do is run xkill from a run dialog and click on the broken video windo=
w.=20
When that happens, I get errors like this in the terminal I ran it from:

The program 'hxplay.bin' received an X WindowSystem error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 4336 error_code 9 request_code 142 minor_code 19)
<snipped part telling me to try --sync>

And again with --sync:
<snipped what was the same>
  (Details: serial 10570 error_code 9 request_code 142 minor_code 19)

I don't know how to "break on the gdk_x_error() function" or I would provid=
e a=20
backtrace.

Oddly, I have much better luck reproducing these problems when using kwin a=
s a=20
window manager as opposed to openbox. These are the setups I've tested:
KDE 3.3b1 (using kwin 3.3b1)
openbox 3.2 inside Xnest inside KDE 3.3b1
kwin 3.3b1 inside Xnest inside KDE 3.3b1
The two kwin setups perform pretty much the same.

Here are a couple more issues:
On the first run of hxplay, I see this:=20
http://greenfs.mine.nu/files/screenshots/helix-01-relnotes.png - something=
=20
seems missing.
These next two issues only occur with the first setup (vanilla KDE session).
When I run 'hxplay foo.ogg' where foo.ogg is a vorbis/theora file, I see th=
is:=20
http://greenfs.mine.nu/files/screenshots/helix-02-openfile.png - definitely=
=20
not right.
When I run 'hxplay --sync foo.ogg' I see this:=20
http://greenfs.mine.nu/files/screenshots/helix-03-openfile.png - not right=
=20
either. But different. Go figure.

In the end, Helix has enough problems to keep me from using it at the momen=
t.=20
Some of this is upstream, and some is packaging. I'll stay up to date on yo=
ur=20
packages, though. I wrote this up in a completely unorganized fashion, so=20
It's probably out of order and missing information in spots. If you need me=
=20
to be more clear about anything, let me know.

I'm not subscribed so please keep me in the CC field.

Thanks for packaging Helix,
=2D --=20
Zack Cerza   <http://greenfs.mine.nu>
GPG Key:     CE48 481B AC70 9C06 740E  E196 A64C 0952 9A8B E23F
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBBBgipkwJUpqL4j8RAtn7AJ9RVX2r3OVwRg78Iqa17iBxfbbjVACdGwtJ
McjTVmhK+cob9Y3LZ1Hj+Jc=3D
=3DheBu
=2D----END PGP SIGNATURE-----