We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Is this symptom still reproducible in 8.10?
** Changed in: mplayer (Ubuntu)
Status: New = Incomplete
--
mplayer rc2 (gutsy-backposrts) does not go down -vo list properly
https://bugs.launchpad.net/bugs/163928
You received this bug notification because you are a member of Ubuntu
Bugs,
No, you're not being ignored, we're just all busy too :).
When applying the Ubuntu configure flags, just take out the ones
relative to pulse audio and gnome screensaver for now. It's not likely
that they are the cause here.
--
mplayer rc2 (gutsy-backposrts) does not go down -vo list properly
Ah, I'm being ignored now ?
I'm sorry, I'm not a developer or anything close to that.
I'm just trying to do my part, opening bugs when I see them, trying to
go further when it is in my power/ability.
I'm sorry I cannot help more right now, and it is not laziness, but
please do not ignore the
On Wed, 2007-11-21 at 17:19 +, John Dong wrote:
If you look in debian/rules, you should be able to find
the ./configure
flags used by the build system.
OK, which debian/rules?
there is one in mplayer_1.0~rc2.orig.tar.gz, but that must be the same
as in my release tarball.
There are
On Wed, 2007-11-21 at 17:19 +, John Dong wrote:
If you look in debian/rules, you should be able to find
the ./configure
flags used by the build system. Try that against your manual build.
hold on, there is only one configure, in the root of the tarball.
Should I change it and change the
With great pleasure.
But could I get help with the process to follow?
Is it just a matter of patching the original tarball's configure file
with the diff from the Ubuntu package? (but there is polyp/pulse stuff
there that may break, at least)
I know how to do a few things, but I'm certainly not
If you look in debian/rules, you should be able to find the ./configure
flags used by the build system. Try that against your manual build.
If that's elminiated, then we can go the complicated route of backing
out patches one by one until it works again :)
--
mplayer rc2 (gutsy-backposrts) does
Here is the output in the logs:
codeMPlayer 1.0rc2-4.1.3 (C) 2000-2007 MPlayer Team
CPU: Genuine Intel(R) CPU @ 2.66GHz (Family: 6, Model: 15, Step
ping: 4)
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
Can't open joystick device
With my own package, from the release rc2, using the same command line
and config file:
MPlayer 1.0rc2-4.1.3 (C) 2000-2007 MPlayer Team
CPU: Genuine Intel(R) CPU @ 2.66GHz (Family: 6, Model: 15, Step
ping: 4)
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled
Can you try applying Ubuntu's ./configure flags on a stock mplayer and
seeing if you can reproduce?
--
mplayer rc2 (gutsy-backposrts) does not go down -vo list properly
https://bugs.launchpad.net/bugs/163928
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
11 matches
Mail list logo
