Plasma Media Center on openSUSE 13.1 ?>

Plasma Media Center on openSUSE 13.1

Download the installable image from here. I used kde image for installation. Once the image is installed you would be popped up for software updates ( assuming that you are connected to internet 🙂 ). For installation of packages I prefer yast. Lets start installing packages one-by-one before cloning and building plasma-mediacenter.

 

Select yast -> Software Management

1) Search for git. Attaching the screenshot below:Always do click on “Accept” to install.

2) Now install nepomuk-core-devel. See the screenshot below:

3) Install libtag-devel.

4) Installing qt-mobility is bit tricky but the screenshots and steps will help you out.

     a) Open up the web page as shown:

      

   b) Now click on “Show unstable packages”. You would land up in the following screen:

       

   c) Click on “Continue”. Below mentioned screen would be popped up.

     

  d) You can select KDE:Qt’s “1 Click Install”. Now user will be popped up in the browser( I am using firefox) as shown below:

    

   Proceed by clicking “OK” and follow up installation of adding KDE:Qt repo. And finally you end up installing qt-mobility.

     e) Install kdebase4-workspace-devel.

     

  f) Install plasma-theme-oxygen.

   

All packages are installed now its time to clone and build the plasma-mediacenter repo:

$ git clone git://anongit.kde.org/plasma-mediacenter.git

$ cd plasma-mediacenter

$ mkdir build

$ cd build

$ cmake .. -DCMAKE_INSTALL_PREFIX=`kde4-config –prefix`

$ make -j(n+1)          // n = number of cores

$ sudo make install

 

Screenshot of PMC:

 

So now you have got Plasma Media Center installed for opensuse 13.1. Try it and let the Plasma Media Center team know if you have any concerns/bugs by raising your issue here. Now don’t wait. You have your cake ready hence serve it hot!!!

 

Happy hacking.

Be Sociable, Share!

10 thoughts on “Plasma Media Center on openSUSE 13.1

  1. Maybe it would be better if the user would validate the repositories KDE:Extra and KDE:Unstable:Extra, In there he/she could find an already build version of plasma-media-center, which would pull in automatically all requirements.

    KDE:Extra has the latest stable version, while KDE:Unstable:Extra contains a very recent git snapshot.

  2. Hi, thank you for the guide. Everything worked perfectly except I get this when completing the last steps:

    VM-OS13:/home/gabe/plasma-mediacenter/build # make -j(n+1) // n = number of cores
    bash: syntax error near unexpected token `(‘

    I continued with the installation anyways, just set it to “make -j 3” and after it completed, entered the make install. I was unsure exactly where to launch, but believe this is right; however, it is not working:

    VM-OS13:/home/gabe/plasma-mediacenter/build/shells/newshell # kdesu plasma-mediacenter
    klauncher: Exiting on signal 15

    Then I tried:

    VM-OS13:/home/gabe/plasma-mediacenter/build/shells/newshell # ./plasma-mediacenter.shell
    kdeinit4: Shutting down running client.
    Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
    KDE Daemon (kded) already running.
    kbuildsycoca4 running…
    plasma-mediacenter(4922)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType “Plasma/MediaCenter/BrowsingBackend” not found
    plasma-mediacenter(4922) MediaCenter::AbstractBrowsingBackend::availableBackends: no available browsing backend

    I just have a black screen, stays that way until I kill the running command.

    I’m running 13.1 on a VMware Fusion 6 VM. This was a fresh build that followed this guide exactly. Please let me know if I am doing something wrong or if I should report this as a bug? Willing to troubleshoot this or provide any data at all to assist in this.

    Thanks.

  3. It is a very bad idea to install to $(kde4-config –prefix), as that’s managed by the package manager and doing so will corrupt the integrity of your package management and might cause horrible side-effects.

    If you really have to manually build a package outside of the package manager, install it to /usr/local or to a local directory like ~/kde-builds.

  4. @zishbu So once you have finished installation, just try “plasma-mediacenter” (excluding the double quotes). It should start up. No need to use kdesu to run plasma-mediacenter. Let me know if you face any issues. And if you face any issue please post the log, so that I can help you further. I (or PMC team ) am ready to help you 🙂

  5. I followed your steps except cloning from git.
    I installed plasma-mediacenter from KDE:Extras

    When I start it I get these errors on terminal :

    Xlib: extension “GLX” missing on display “:0”.
    libpng warning: iCCP: known incorrect sRGB profile
    (repeated around 100 times)

    and the app wasn’t starting.
    Anything I should try ?

  6. I am bit confused with what you are trying to convey.
    a) Are you trying to run as root user or with your login or so?
    If you are running as root, please don’t. And more over if you are installing plasma-mediacenter from KDE:Extras , then you don’t have to build it. So I assume you had followed only 5% or my blog. Let me know if it resolves your problem.

Leave a Reply

Your email address will not be published. Required fields are marked *

CommentLuv badge

(Spamcheck Enabled)