** Changed in: medibuntu
Status: New => Invalid
--
Please Upgrade Mplayer
https://bugs.launchpad.net/bugs/243453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
This bug was fixed in the package mplayer -
2:1.0~rc3+svn20090426-1ubuntu1
---
mplayer (2:1.0~rc3+svn20090426-1ubuntu1) karmic; urgency=low
* Switch to debian packaging for the mplayer package
* New upstream release, LP: #336697, #260918, #246675, #243453, #74282
* Fixes securit
For anyone who hasn't already discovered this there are packages of more
recent MPlayer snapshots as well as SMPlayer and dependancy libraries in
PPAs described here...
http://smplayer.berlios.de/forums/viewtopic.php?id=1139
--
Please Upgrade Mplayer
https://bugs.launchpad.net/bugs/243453
You re
SMPlayer now complains about a too old MPlayer in Jaunty. Please
downgrade SMPlayer or upgrade MPlayer.
--
Please Upgrade Mplayer
https://bugs.launchpad.net/bugs/243453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Also affects: medibuntu
Importance: Undecided
Status: New
--
Please Upgrade Mplayer
https://bugs.launchpad.net/bugs/243453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
What's the reasoning behind not updating mplayer?
MPlayer 1.0rc2 may be the most recent actual release but the following page
states that is isn't supported because it's outdated...
http://www.mplayerhq.hu/design7/dload.html
Surely ubuntu should be using supported versions of the software in the r
Currently my mplayer gives the same error as described in this bug:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/318445
But since ffmpeg in jaunty is new, ffmpeg is actually fixed. But I still
can't play the file in mplayer, because it's old and isn't linked
against the new ffmpeg.
I rea
Reinhard, if the ffmpeg svn is allowed in the main repo, then mplayer
svn should be allowed too.
--
Please Upgrade Mplayer
https://bugs.launchpad.net/bugs/243453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Kevin DeKorte <[EMAIL PROTECTED]> writes:
> As stated above the mplayer team does not do releases and recommends
> using SVN. I know this causes more work for you as a packager, but even
> doing a monthly or quarterly release even with a package name of
> 'mplayer-svn' would be helpful. That way t
William,
As the developer of gnome-mplayer I get several bugs with regards to
subtitles and other weirdness. Most of those issues are solved by
getting a newer version of mplayer. By not upgrading this package to
something more recent you are actually creating more problems for users
and developer
** Changed in: mplayer (Ubuntu)
Importance: Undecided => Wishlist
--
Please Upgrade Mplayer
https://bugs.launchpad.net/bugs/243453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
William Grant:
This report should be either Confirmed or Invalid, because it definitely
fulfills the criteria for Confirmed. As detailed in the Ubuntu wiki:
https://wiki.ubuntu.com/Bugs/Responses#Triage Successful
"Thanks for reporting this bug and any supporting documentation. Since this bug
ha
It's especially odd given that Ubuntu has, several times in the past,
shipped with an item in main which hadn't officially been 'released' -
and certainly wasn't stable. See NM back in... either breezy or dapper?
Firefox in Hardy...
I'm unsure, given the development model of mplayer / ffmpeg and g
William Grant:
If you are the maintainer, that is fair enough.
However, if this report has, in your view, no merit whatsoever, please
don't keep the uninformed users hanging by reverting this to "New",
giving any false hopes about mplayer in Ubuntu.
In other words, if you are not going to upgrad
Sorry, but thats complete nonsense William and I'm flawed that you
honestly consider that to be the case.
The development model of ffmpeg is that they do not "do" releases. What
ffmpeg does is to continually update the code and refer any bug reports
to "use the latest svn and see if it's still a p
Not confirmed. I don't have any good reason to do this.
** Changed in: mplayer (Ubuntu)
Status: Confirmed => New
--
Please Upgrade Mplayer
https://bugs.launchpad.net/bugs/243453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: mplayer (Ubuntu)
Status: New => Confirmed
--
Please Upgrade Mplayer
https://bugs.launchpad.net/bugs/243453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
I patched all of those in all releases months ago.
** This bug is no longer flagged as a security issue
--
Please Upgrade Mplayer
https://bugs.launchpad.net/bugs/243453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Also there is atleast four unpatched security vulnerabilities resolved
since rc2 was released back in 07/10/2007. Some details are found on
http://www.mplayerhq.hu/design7/news.html but I suspect there is other
security issues resolved in SVN.
** This bug has been flagged as a security issue
--
I notice on the Intrepid repo atleast, that dependencies are wrong with
mplayer and gnome-mplayer. For some reason libx264-57 2007-12-74 is auto
installed instead of the better later version which is named
libx264-5920080408. I think it would be better to use one libx264
package so that when it is
20 matches
Mail list logo
