gmplayer fails to start because of skin trouble

Bug #386507 reported by José Alburquerque
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mplayer-skins (Ubuntu)
Fix Released
Undecided
Reinhard Tartler

Bug Description

Binary package hint: mplayer

Running gmplayer from the command line (without any media file) fails for me with the following:

[06:29][jose@sweety: ~]$ gmplayer
Warning unknown option vo_dxr3_device at line 6
MPlayer UNKNOWN-4.4.0 (C) 2000-2009 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
[skin] file ( /usr/share/mplayer/skins/default/skin ) not found.
Skin not found (default).
[06:29][jose@sweety: ~]$

The blue skin package is installed. The mplayer-skins package is not.

If I install the mplayer-skins package it starts but there should be an mplayer-skins dependency if gmplayer requires the default skin to run.

ProblemType: Bug
Architecture: amd64
Date: Fri Jun 12 16:37:33 2009
DistroRelease: Ubuntu 9.10
Package: mplayer 2:1.0~rc3+svn20090426-1ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
SourcePackage: mplayer
Uname: Linux 2.6.30-8-generic x86_64

Revision history for this message
José Alburquerque (jaalburquerque) wrote :
Revision history for this message
José Alburquerque (jaalburquerque) wrote :

The attached error window also comes up on start-up.

Revision history for this message
Benjamin Drung (bdrung) wrote :

I can confirm this bug. Starting gmplayer with -fontconfig is a work around.

Changed in mplayer (Ubuntu):
status: New → Confirmed
Revision history for this message
Reinhard Tartler (siretart) wrote :

is that really an error? I notice that gmplayer works fine after acknowledging that warning.

Revision history for this message
Reinhard Tartler (siretart) wrote :

okay, again 2 issues here. The "Error window" is because fontconfig support was not enabled. fontconfig enables mplayer to detect the "default system font" automatically. It is not enabled by default, users need to enable it with the commandline switch -fontconfig. We can fix the desktop file to call mplayer with -fontconfig by default. This should be tracked seperately.

the original report mentioned in the bug description is a problem in the interaction between the mplayer-skins and the mplayer-skin-blue package. The mplayer-skin-blue manages the //usr/share/mplayer/skins/default symlink via update-alternatives, while mplayer-skins does fiddle with the symlink manually. This is plain wrong of course.

I'd suggest to just merge the mplayer-skins package with the mplayer-skin-blue one.

affects: mplayer (Ubuntu) → mplayer-skins (Ubuntu)
Changed in mplayer-skins (Ubuntu):
assignee: nobody → Reinhard Tartler (siretart)
status: Confirmed → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mplayer-skins - 3

---------------
mplayer-skins (3) karmic; urgency=low

  * merge the mplayer-skin-blue package LP: #386507, #386510
  * provide transitional package mplayer-skin-blue
  * cleanup the replaces list
  * make this a debian native package
  * bump debhelper compat level to 5

 -- Reinhard Tartler <email address hidden> Fri, 16 Oct 2009 18:08:01 +0200

Changed in mplayer-skins (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.