Open GoogleCodeExporter opened 8 years ago
Here is command line I used to start video playing:
ierton@pokemon ~/proj/gnu/gnome-mplayer-read-only $ ./src/gnome-mplayer -v
~/downloads/For\ the\ Birds\ \ \(2001\).avi > log 2>&1
Original comment by ier...@gmail.com
on 5 Nov 2010 at 5:45
Might try another vo like xv? When did this last work? And what else have you
changed on your system? I am currently unable to duplicate your issue.
Original comment by kdeko...@gmail.com
on 5 Nov 2010 at 5:48
might try running 'make distclean' or 'make clean' and rerunning configure and
make and see if that solves the problem. This could be caused by some other
component being upgraded.
Original comment by kdeko...@gmail.com
on 5 Nov 2010 at 5:52
I've tried different settings (all video outputs except vpadu). Same results.
I've also tried 0.9.9.2 installed as package before svn.
No, it is not an upgrade issue - I made svn checkout for the first time.
Here is my mplayer version:
ierton@pokemon ~ $ equery list mplayer
[ Searching for package 'mplayer' in all categories among: ]
* installed packages
[I--] [ ] media-video/mplayer-1.0_rc4_p20091026-r1 (0)
For me it looks like something is wrong with mplayer's argument for window id
to draw on.
Original comment by ier...@gmail.com
on 5 Nov 2010 at 8:18
For example, smplayer works fine. Here is it's log. Notice -wid 18874712
argument. gnome-mplayer doesn't use this. Is it all right?
Original comment by ier...@gmail.com
on 5 Nov 2010 at 8:21
Attachments:
Ah, sorry, I am wrong. gnome-mplayer uses -wid <id>. Is there a tool which I
can use to check this id? Maybe it actually points to invalid window.
Original comment by ier...@gmail.com
on 5 Nov 2010 at 8:28
Mm, just a guess. smplayer uses decimal numbers while gnome-mplayer - hex. Can
it be a clue?
Original comment by ier...@gmail.com
on 5 Nov 2010 at 8:41
Decimal or hex should be fine. I've been using hex numbers for years. you can
try decimal numbers by altering thread.c
I think what is bothering me is the assertions you have in the log. Seems like
something in gtk just isn't working right.
I have two machines, one with gtk 2.20 and another with gtk 2.22 and they both
work fine as is.
Original comment by kdeko...@gmail.com
on 5 Nov 2010 at 8:47
Hm. Yes, hex is ok. I have x11-libs/gtk+-2.20.1-r1 on my machine. Works quite
fine.
Maybe it's a gnome-related problem? I am not using it. My environment is just
AwesomeWM. And here is new info: When I'm launching nautilus, it replaces my
wallpaper with the desktop (~/Desktop/* and Trash icons). If I launch
gnome-mplayer after that, following can happens (not always but quite
frequently):
ierton@pokemon ~/proj/gnu/gnome-mplayer-read-only $ ./src/gnome-mplayer
~/downloads/For\ the\ Birds\ \ \(2001\).avi
The program 'gnome-mplayer' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1143 error_code 3 request_code 40 minor_code 0)
(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.)
If I kill nautilus, those crashes will gone.
Can it be some missing gnome resource?
Original comment by ier...@gmail.com
on 5 Nov 2010 at 9:42
I'm unsure what could be causing that as I don't run the awesome window
manager. I actaully run nautilus with --no-desktop so I don't have the Desktop
icons. It might be possible that awesome is interfering with the window
embedding process that gnome-mplayer uses.
Original comment by kdeko...@gmail.com
on 5 Nov 2010 at 9:52
No, I've checked it without WM (using pure xterm session). Same behaviour as
before, no crashes.
Original comment by ier...@gmail.com
on 5 Nov 2010 at 10:02
Can you test using metacity as the window manager and see if that helps?
Original comment by kdeko...@gmail.com
on 5 Nov 2010 at 10:12
Done. Pure metacity. 2 logs are in attach, one good and one bad (bad case is
more frequent on given video file). Also there were situations when all looked
fine at the beginning of playback but then "invalid Pixmap or Window parameter"
errors appeared suddenly and screen became blank.
Original comment by ier...@gmail.com
on 5 Nov 2010 at 11:03
Attachments:
Here is new log. Initially good, but then I pressed pause/unpause several times
and errors appeared.
Original comment by ier...@gmail.com
on 5 Nov 2010 at 11:14
Attachments:
Please post your configure log and you might try upgrading mplayer to something
newer.
Original comment by kdeko...@gmail.com
on 5 Nov 2010 at 11:17
Ok. Config.log attached.
Original comment by ier...@gmail.com
on 5 Nov 2010 at 11:23
Attachments:
Can you retest SVN, improvements have be made to this area of the code.
Original comment by kdeko...@gmail.com
on 11 May 2011 at 8:20
Original issue reported on code.google.com by
ier...@gmail.com
on 5 Nov 2010 at 5:39Attachments: