*** This bug is a duplicate of bug 386507 ***
https://bugs.launchpad.net/bugs/386507
** Branch linked: lp:ubuntu/mplayer
--
gmplayer does not find the default skin and no controls are visible after
installing mplayer-skins or mplayer-skin-blue
https://bugs.launchpad.net/bugs/390398
You
*** This bug is a duplicate of bug 386507 ***
https://bugs.launchpad.net/bugs/386507
** This bug has been marked a duplicate of bug 386507
gmplayer fails to start because of skin trouble
--
gmplayer does not find the default skin and no controls are visible after
installing
This bug was fixed in the package mplayer -
2:1.0~rc3+svn20090426-1ubuntu10
---
mplayer (2:1.0~rc3+svn20090426-1ubuntu10) karmic; urgency=low
* make sure that patches are applied for non-i386 builds as well.
Fixes: LP: #390398, #448603, #448595, #441566, #440346
-- Reinhard
this situation is indeed very wicked. We have two skin packages that
don't play very well with each other. I think we should either
a) merge both packages
b) decide on one skin and make it replace the other one
if we go with a), which skin should be the default? And how does the
user switch
clearplayer should be the default, because it was the default in jaunty.
--
gmplayer does not find the default skin and no controls are visible after
installing mplayer-skins or mplayer-skin-blue
https://bugs.launchpad.net/bugs/390398
You received this bug notification because you are a member
clearplayer *IS* the default (see my comment - #3)
It's just that clearplayer skin is part of mplayer-skins is not installed
when one installs mplayer, because it is not listed as dependency, while
mplayer-skin-blue gets installed to provide dependancy for mplayer-skin.
Notice mplayer-skins vs.
** Summary changed:
- gmplayer does not find the default skin
+ gmplayer does not find the default skin and no controls are visible after
installing mplayer-skins or mplayer-skin-blue
--
gmplayer does not find the default skin and no controls are visible after
installing mplayer-skins or
