It is unacceptable to have Battlestar Galactica on DVD and be unable to watch it on Kubuntu. However, out of the box, Dragon Player does not know how to play standard DVDs which makes the unacceptable perfectly horrendous.
This fix is an easy one: the Dragon Player doesn’t work without certain drivers that are legally encumbered (that’s code for proprietary with the risk of strongly worded legal letters arriving uninvited at your home) so you have to go get the drivers yourself so as to keep various people, most notably Canonical, from declaring bankruptcy or being embarrassed in court when they kick the RIAA‘s butt (did I say that out loud?).
If you have 64-bit Kubuntu running on a Core 2 Duo and the Dragon Player does not work when you try to play a DVD movie run the following lines from a terminal window (if you want to run them all together put a semi-colon after each command):
sudo wget http://www.medibuntu.org/sources.list.d/intrepid.list --output-document=/etc/apt/sources.list.d/medibuntu.list
sudo apt-get update
sudo apt-get install medibuntu-keyring
sudo apt-get update
sudo apt-get install w64codecs libdvdcss2
I found this information a few months ago at http://www.ubuntugeek.com/install-mplayer-and-multimedia-codecs-libdvdcss2w32codecsw64codecs-in-ubuntu-810-intrepid-ibex.html. It just made it possible for me to watch my legally purchased copy of BSG.
The cat was alive again.
I just (well, a few weeks ago) installed an instance of Kubuntu on a Dell Studio 17 (the host OS is Vista Home Premium 64-bit) and the volume went from low, after the initial installation, to non-existent after rebooting. Was it possible that the volume on Amarok was down? Nope, it was at 100%. Was the volume setting located in the task bar set to mute? No again. Was the Mixer at fault? No.
After trolling the web and finding many possible reasons for the sudden onset of muteness (bad drivers, conflicting installations of software) I found a simple check that proved to be the most telling: I ran the command line alsamixer and made sure the volume is up!
This is what I saw after I opened a Konsole terminal window and typed
Notice the lack of color on the third bar; the one labelled PCM. After moving the cursor to the PCM column and pressing the up arrow a few dozen times the bar was nicely multi-colored. This is what the
alsamixer levels looked like (notice the PCM is up) after my tinkering:
I pressed Esc to exit
alsamixer and ran the following to save the settings:
sudo alsactl store
The cat was alive.
- Writing an Eclipse Plug-in (Part 2): Creating a custom project in Eclipse - Adding to the New Project Wizard
- Writing an Eclipse Plug-in (Part 1)- What I'm going to do
- Writing an Eclipse Plug-in (Part 7): Creating a Custom Navigator
- Writing an Eclipse Plug-in (Part 4): Create a Custom Project in Eclipse - New Project Wizard: the Behavior
- Writing an Eclipse Plug-in (Part 11): Common Navigator: Displaying Custom Resources or Refresh Or Die or The Magic of navigatorContent
- January 2012 (1)
- February 2011 (1)
- January 2011 (1)
- August 2010 (2)
- June 2010 (1)
- May 2010 (2)
- April 2010 (1)
- March 2010 (1)
- February 2010 (4)
- January 2010 (2)
- December 2009 (5)
- November 2009 (2)
- October 2009 (6)
- September 2009 (6)
- August 2009 (4)
- July 2009 (6)
- April 2009 (2)
- February 2009 (2)
- December 2008 (1)
- October 2008 (2)
- September 2008 (2)
- August 2008 (1)
- 435,604 hits