Difference between revisions of "Plasma/Active/Installation"

< Plasma‎ | Active
Jump to: navigation, search
(Balsam Professional)
m (openSUSE)
 
(106 intermediate revisions by 21 users not shown)
Line 1: Line 1:
= Install Plasma Active on ARM Systems =
+
= Plasma Active Images =
  
== External MultiMediaCard (MMC) Images ==
+
The Plasma Active team provides official Images based on Mer for some devices.
  
=== Mer Plasma Active ===
+
== Supported ==
The [http://merproject.com Mer] project creates a Plasma Active [http://bug10738.openaos.org/images/tegra2/ MMC Image] which is build for the armv7hl target devices like the ARM Tegra 2 tablet. For more details please see the related [http://wiki.merproject.com/wiki/Community_Workspace Mer Wiki].
 
  
You can also download the kernel boot image, the external MMC image and some additional helper scripts from basysKom download location [http://share.basyskom.com/contour/Deployment/latest-basyskom-plasma-active-tegra2-mer.html here].
+
=== WeTab / ExoPC ===
  
== Deploying a Plasma Active (MMC) raw Image to a MultiMediaCard ==
+
The hardware is a little outdated but you will get the most polished Plasma Active experience on this device.  
A Installation description for MultiMediaCards could be found in the [http://wiki.meego.com/ARM/N900/Install/MMC MeeGo ARM Wiki].
 
  
 +
* [https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/basyskom-plasma-active-four-wetab-exopc-tablet-mer-release.iso Download ISO]
 +
* [https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/basyskom-plasma-active-four-wetab-exopc-tablet-mer-release-iso.sha1 Checksum] (sha1: 51bd1ac2aea097d8e17503a92ce2781a6532491d)
 +
* [https://share.basyskom.com/plasma-active/deployment/wetab-exopc/tablet/mer/stable/ Download Archive]
  
= Install Plasma Active on x86 Systems =
+
Take a look at the installation instructions [http://community.kde.org/Plasma/Active/WeTab here].
  
== Live Images==
+
== Preview ==
These can be used as testing base and to track progress.
 
  
=== Balsam Professional ===
+
=== Nexus 7 ===
[http://open-slx.de open-slx] creates regularly updated packages of Balsam Professional for Plasma Active. You can try the Live ISO from a USB stick. Download the Balsam Professional live image [http://download.open-slx.com/iso/12.1/plasma-active-2.iso download.open-slx.com/iso] ([http://download.open-slx.com/iso/12.1/md5sums.txt checksum)].
 
  
The image plasma-active-2.iso is always the newest one and a link to the plasma-active-<xxx>.iso in the download repo. Please check the changelog and README. The images are also booting WeTabs without flashed BIOS.
+
Even though very much already works reasonably well, there are still some glitches. So, please don’t expect a 100% working system. For detailed installation instructions, see the article on the [https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_installation Mer Wiki]
  
The image comes with a live-installer. This is currently availible via Konsole. This works:
+
=== Archos G9 ===
  
- Download the image and put it on a stick
+
Take a look at [http://ruedigergad.com/2013/02/24/plasma-active-archos-g9-armv7hl-rootfs-tarballs/ Ruedigers Blog] for more information.
  
- connect a usb-keyboard to the system
+
=== Nokia N950 ===
  
- Boot the stick and wait until Plasma Active is running
+
Take a look at [http://www.osnews.com/story/25307/Nokia_N950_Running_Plasma_Active_on_Mer this OSnews article] for more information.
  
- Open a konsole and change to root via typing: su -
+
=== VirtualBox ===
  
- Enter yast2 live-installer
+
When running Plasma Active in a virtual machine, consider that performance will not be as good as when it runs naively on the devices it has been designed for. For testing, we strongly recommend running Plasma Active on a device. The following limitations need consideration when using a virtual machine instead of a real device:
 
 
- Follow the instructions. You can configure dualboot, user and partioning the natvie system
 
 
 
=== MeeGo Plasma Active ===
 
[http://basyskom.com basysKom] creates regularly updated packages of Plasma Active based on MeeGo.
 
 
 
This image is an adaption of the public '''meego-tablet-ia32-pinetrail''' variant and it is bootable on x86 based devices like '''WeTab''', '''ExoPC''' or the '''Idea Pad'''. Login Data: User meego passwd meego; User root passwd meego
 
 
 
You can try the installable Live ISO from a USB stick. Download the [http://share.basyskom.com/contour/Deployment/latest-meego-plasma-active-stable.html latest demo and stable release live image] ([http://share.basyskom.com/contour/Deployment/latest-meego-plasma-active-stable-checksum.html sha1]).
 
 
 
If you want to try new but not yet released versions you can find here the [http://share.basyskom.com/contour/Deployment/latest-meego-plasma-active-testing.html latest testing live image] ([http://share.basyskom.com/contour/Deployment/latest-meego-plasma-active-testing-checksum.html sha1]).
 
 
 
The scope of Plasma Active Contour UX development is for usage on tablet devices. If you want to activate the mouse cursor eg on a netbook, follow [http://community.kde.org/Plasma/Active/Info/FAQ#How_do_I_get_a_Mouse_Cursor.3F these instructions].
 
 
 
== Deploying a Plasma Active ISO Image to a Flashdrive ==
 
After you have downloaded the ISO image it's a good idea to validate the image against transmission errors.
 
A checksum file should be available for every image.
 
 
 
<!--
 
=== Validate and Deploy on Microsoft Windows ===
 
On Windows you can compare the hash on equality between image and related checksum file by the [http://support.microsoft.com/kb/841290 fciv.exe] tool. You will find all needed information about
 
usage on this site.
 
 
 
With the [https://launchpad.net/win32-image-writer win32-image-writer] tool you can easily deploy a plasma active image to a USB Flashdrive. For a detailed description how to work with this tool please see the MeeGo [https://meego.com/devices/netbook/installing-meego-netbook/windows-instructions Windows instructions]. -->
 
 
 
=== Validate and Deploy on Linux ===
 
On Linux you can compare the hash between the image and related checksum file using the following command (with both the image and the checksum file in the same directory):
 
 
 
    user@host# '''sha1sum -c ''<checksum file>'''''
 
 
 
    user@host# '''md5sum -c ''<checksum file>'''''
 
 
 
If the command returns "<image name>: FAILED", please download the image one more time and check again.
 
 
 
 
 
After validation feel free to deploy the image to a '''not mounted''' USB flashdrive. In the following example we use the
 
tool 'dd' for this:
 
 
 
    root@host# '''dd if=''<image file>'' of=/dev/''<USB flashdrive>'' bs=1M'''
 
 
 
'''Please note, the usage of this tool is potentially dangerous! In case of a mistaken output device, all data on it will be irrecoverably lost'''.
 
 
 
'''To get the correct output device for this tool, please follow the steps below:'''
 
 
 
;1. Remove all mobile flashdrives from your host system.
 
;2. Enter the command below and note the output.
 
    user@host# '''cat /proc/partitions'''
 
 
 
    major minor  #blocks  name
 
      8    0    3000000  sda
 
      8    1    2999998  sda1
 
 
 
;3. Plug the Flashdrive for deploying into the host system.
 
;4. Enter the following command and note the output again.
 
    user@host# '''cat /proc/partitions'''
 
 
 
    major minor  #blocks  name
 
      8    0    30000000 sda
 
      8    1    29999998 sda1
 
      8    16    3872256 '''sdb'''
 
      8    17    594944 sdb1
 
;5. In this example the correct dd parameter is '''sdb''' in the position of '''<USB flashdrive>'''.
 
 
 
== Running Plasma Active in a Virtual Machine ==
 
 
 
When running Plasma Active in a virtual machine, consider that performance will not be as good as when it runs natively on the devices it has been designed for. For testing, we strongly recommend running Plasma Active on a device. The following limitations need consideration when using a virtual machine instead of a real device:
 
 
* Performance, especially graphics, boot and application startup might be reduced
 
* Performance, especially graphics, boot and application startup might be reduced
 
* Advanced visual effects might not be available or work correctly in the virtual machine. This can lead to degradation of certain features, performance, visual effects and possibly stability
 
* Advanced visual effects might not be available or work correctly in the virtual machine. This can lead to degradation of certain features, performance, visual effects and possibly stability
 
* User interfaces designed for touch-screens often work less efficiently for mouse and keyboard based input methods, or feel less natural.
 
* User interfaces designed for touch-screens often work less efficiently for mouse and keyboard based input methods, or feel less natural.
  
We have found VirtualBox to basically work, albeit in some cases the above problems have been noted. Read on for instructions on how to have a first look at Plasma Active, even without suitable hardware.
 
 
=== Virtual Box ===
 
 
Before you can start the image via '''VirtualBox''', please configure the virtual device
 
as below.
 
 
VirtualBox OSE Manager
 
  Settings
 
  ├── General
 
  │  └── Basic
 
  │      ├── Name --> e.g. Plasma-contour
 
  │      ├── Operating System --> Linux
 
  │      └── Version --> Linux 2.6
 
  ├── System
 
  │  ├── Motherboard
 
  │  │  ├── Boot Order
 
  │  │  │  ├── CD/DVD-ROM
 
  │  │  │  └── Hard Disk
 
  │  │  └── Base Memory --> 1024MB
 
  │  └── Processor
 
  │      └── Enable PAE/NX
 
  ├── Display
 
  │  └── Video
 
  │      ├── Video Memory --> 128 MB
 
  │      └── Enable 3D Acceleration
 
  └── Storage
 
      ├── IDE Controller
 
      │  └── IDE Secondary Master
 
      │      └── Set up the virtual CD/DVD drive
 
      │          └── <ISO image>
 
      └── SATA Controller
 
          └── Hard Disk
 
              └── Set up the virtual hard disk
 
                  ├── Dynamically expanding storage
 
                  └── Virtual Size --> 8.00 GB
 
 
'''Please note, only live images since ''2011-07-20-10-50-meego-plasma-contour-in-progress-USB-live.iso''
 
''' are runnable via VirtualBox'''.
 
 
Please note, if you'd like to install our live image to an VirtualBox hard drive,
 
you have to remove the live image from the virtual CD/DVD-ROM after installation.
 
This will be done after '''Power off the machine''' via VirtualBox OSE Manager.
 
 
  Settings
 
  └── System
 
      └── Motherboard
 
          └── Boot Order
 
              ├── CD/DVD-ROM --> disable
 
              └── Hard Disk
 
 
Once MeeGo/Plasma Active is installed, you may want to [[Plasma/Active/Info/FAQ#How_do_I_get_a_Mouse_Cursor.3F | '''enable the mouse cursor''']].
 
 
== Booting the Live Image on a WeTab/ExoPC ==
 
 
1. Plug the flashdrive into the WeTab/ExoPC (WeTab only works with flashed BIOS from ExoPC).
 
 
2. Get the WeTab/ExoPC running.
 
 
3. Press the power (top left underside) + softtouch (top left upperside) buttons until it reboots.
 
 
4. When it reboots, press "BBS" to display a boot menu.
 
 
5. Choose the flash drive in the boot menu (press the softtouch button briefly to move to the next selection; press the softtouch button longer to emulate Enter).
 
 
6. Choose in the boot menu using the softtouch button
 
 
== Installation on Balsam Professional or openSUSE ==
 
 
In order to install the latest development snapshots on Balsam Professional or openSUSE 11.4, you have to add two repositories to your system. These update kdelibs and kde-runtime to a patched 4.7 which contains additions in QML bindings and improvements needed to run the development version for Plasma Active. If you would like to try it in a virtual machine, we recommend Virtualbox, which provides accelerated graphics capable of "desktop effects" (see above).
 
 
Important: this procedure '''will upgrade your KDE installation''' to a patched version of 4.7, replacing any KDE packages you have installed.  Some versions of these packages, for example kdepim4 and kdepim4-runtime, are built for a mobile target and the desktop versions of their apps '''will not run properly'''.  Running a newer version of KDE may update users' configuration files in a way that is '''not backward-compatible with previous versions''' of the applications, so it is advised to use a development installation or backup your KDE configuration.  If you don't know how to do this, '''stay with the Live image'''.
 
 
=== Installation Recipe ===
 
==== Preparation ====
 
For initial installation, a mouse is helpful and an external keyboard is essential.
 
 
Install openSUSE 12.1 Live KDE via USB stick from [http://software.opensuse.org/121/en the openSUSE download page]. [http://download.opensuse.org/distribution/12.1/iso/openSUSE-12.1-KDE-LiveCD-i686.iso Direct download link].
 
 
When the Live Image has loaded completely, pull the top bar down to expose App Launch. In the search box, type "install" (you may need to touch in the search box to expose a keyboard). Select Live Installer to launch the installation process. Several user interactions are required to complete the process. There is [http://opensuse-guide.org/installation.php more detailed information] (section 4.3) available on the 4.3 Live CD/USB installation.
 
 
As you are going to install packages from a different source, or so-called "vendor", you can make your life easier by telling zypper to automatically resolve packages across vendors. In /etc/zypp/zypp.conf, change the following line
 
 
solver.allowVendorChange = false
 
 
to
 
 
solver.allowVendorChange = true
 
 
(You don't need to perform the step above if you follow the YaST-based alternatives offered below.)
 
 
Due to a bug in the DVD installation, you may be using static network configuration using YaST instead of NetworkManager. To change it to use NetworkManager, launch YAST, select "Network Settings" and under "Global Options" change the setting to "User Controlled with NetworkManager". You can then enable wireless and configure it as normal. (Note: this seems to be fixed with the OpenSUSE 12.1 iso, at least the 64-bit version.)
 
 
==== Repository Setup ====
 
Register KDE:Active repositories:
 
<nowiki>
 
zypper addrepo --refresh \
 
    http://download.open-slx.com/balsam/professional/distribution/plasma-active/12.1/ plasma-active
 
</nowiki>
 
 
Increase KDE:Active packages' priority, we want the KDE:Active versions that are built with Active-specific options (higher prio than openSUSE which is 99 by default):
 
<nowiki>
 
zypper modifyrepo --priority 90 plasma-active
 
</nowiki>
 
 
(Alternative: Use YaST's Software Repositories feature to add the repository http://download.open-slx.com/balsam/professional/distribution/plasma-active/12.1/, and set its priority to 90.)
 
 
==== Upgrading from Plasma Active One ====
 
Upgrading is easy, you'll need to remove one repo, add one back and then do a system upgrade.
 
 
''If you are still running OpenSUSE 11.4 you will need to upgrade to 12.1 before proceeding.
 
 
First, point zypper to the new repo, delete the old one:
 
<nowiki>
 
zypper rr plasma-active
 
 
zypper addrepo --refresh \
 
    http://download.open-slx.com/balsam/professional/distribution/plasma-active/12.1/ plasma-active
 
zypper mr --priority 90 plasma-active
 
</nowiki>
 
 
Then do a full system ugprade, possibly accepting all "vendor changes" (this means that you are changing the repo for some packages):
 
<nowiki>
 
zypper refresh
 
zypper dup
 
</nowiki>
 
 
After that, Log out and in again, restart X or reboot. You might want to remove the config files in your homedirectory under (~/.kde4/share/config), look into /etc/kde4/share/config/ for default config files, as you might not get all updates to your settings if you have configured things differently already.
 
 
==== Package Installation ====
 
Update all packages to the latest versions, trust the keys for the repos.  NOTE: if you have other additional repositories than these registered in your system, YOU are responsible for making sure they are compatible.
 
<nowiki>
 
zypper dist-upgrade
 
</nowiki>
 
 
For some reason GRUB isn't always updated to make the new kernel the default when installing this new kernel, so check in YAST, System, Boot Loader
 
 
(Alternative: use YaST's Online Update feature to perform system updates.)
 
 
Finally, install the Plasma Active specific packages:
 
<nowiki>
 
zypper install plasma-contour-config qt-mobility </nowiki>
 
 
This will install and setup the Plasma Active shell, which is contained in the plasma-mobile package (plasma-mobile has different sets of QML user interfaces per UI profile). zypper will ask you to accept the key. It will also suggests vendor changes for some packages. Accept these options.
 
 
(Alternative: use YaST's Software Management feature to search for and select the plasma-contour-config and qt-mobility packages for installation, install them, selecting the first choice for resolving package conflicts.)
 
 
=== Running Plasma Active ===
 
If you have installed the plasma-tablet-config package, your system will automatically start into Plasma Active. Just make sure you have autologin enabled in Yast and restart your system.
 
 
From a full Plasma Desktop (or Netbook) user experience, you can also switch at runtime to Plasma Active as follows (as user logged into the the X11 session):
 
<nowiki>
 
# Quit your plasma session
 
kquitapp plasma-desktop
 
or
 
kquitapp plasma-netbook
 
 
# Start Plasma Active
 
plasma-device
 
 
# It is also possible to run Plasma Active in a window,
 
# this is useful for testing purposes:
 
plasma-device --nodesktop
 
</nowiki>
 
 
=== Installation of Plasma Active from sources ===
 
 
While the recommended way to test Plasma Active is with the above recipe using the binary packages, it is possible to build Plasma Active from the source repository, who wants to try the bleeding edge repository can build plasma-mobile from sources.
 
The recommended way is to follow the usual kde from sources [http://techbase.kde.org/Getting_Started build instructions]. It is also possible to use the binary kde packages as a base.
 
 
It is necessary to install some packages (and their dependencies) to have a working development environment:
 
<nowiki>
 
sudo zypper install gcc gcc-c++ git cmake, kdelibs-devel
 
</nowiki>
 
 
Now clone the plasma mobile source repository and build:
 
<nowiki>
 
git clone git://anongit.kde.org/plasma-mobile
 
 
cd plasma-mobile
 
 
mkdir build
 
 
cd build
 
 
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
 
 
make
 
 
sudo make install
 
</nowiki>
 
 
=== Installing Additional Software ===
 
 
There are a few KDE projects that have created touch friendly versions of their applications already. These versions are included in the plasma-active repository. Currently, these are:
 
 
* Calligra Active - Install package calligra-active
 
* Kontact Touch - Install package kontact
 
* Bangarang - Install package bangarang
 
 
In addition, some applications already work quite well together with active. The following is a list of applications that work ok on a touchscreen:
 
 
* Okular - For viewing documents.
 
* Marble - Virtual globe, includes routing support.
 
* Bangarang - Media player, uses Nepomuk for listing media.
 
* Dolphin - File manager.
 
 
== MeeGo ==
 
 
=== Installation ===
 
 
A repository of most of KDE components, including Plasma Active for MeeGo is at
 
https://build.pub.meego.com/project/show?project=Project%3AKDE%3ATrunk%3ATesting and is available for both i586 and ARM, which is added by running the following command if you are using MeeGo trunk
 
 
<nowiki>
 
zypper ar http://repo.pub.meego.com/Project:/KDE:/Trunk:/Testing/Trunk/Project:KDE:Trunk:Testing.repo
 
</nowiki>
 
 
or for MeeGo 1.2 users:
 
 
<nowiki>
 
zypper ar http://repo.pub.meego.com/Project:/KDE:/Trunk:/Testing/MeeGo_1.2_oss/Project:KDE:Trunk:Testing.repo
 
</nowiki>
 
 
To install the software run the following command:
 
  
<nowiki>
+
For detailed installation instructions, see this [http://community.kde.org/Plasma/Active/VirtualBox installation manual].
zypper install plasma-contour-config
 
</nowiki>
 
  
=== UX Launch ===
+
= Downstream Plasma Active  =
  
uxlaunch is the MeeGo component that actually launches the shell. There are two ways of switching the default MeeGo Tablet UX shell to Plasma.
+
Some distributions provide Images with Plasma Active for x86 Systems.
  
==== Changing UX permanently ====
+
== Kubuntu Active ==
  
Edit /etc/sysconfig/uxlaunch and change the session key to "/usr/bin/startkde" (Plasma Active One) or "/usr/bin/startactive" (Plasma Active Two).
+
Current stable release of a Kubuntu remix with Plasma Active is available at
  
==== Dynamic UX selection at boot ====
+
http://cdimage.ubuntu.com/kubuntu-active/releases/13.04/release/
  
Finally, to switch to using the plasma tablet UX in MeeGo, use the uxselector project, following the instructions found here: http://wiki.meego.com/MeeGo_Desktop/Changing_Desktops#UXSelect_Switcher_Tool_.28alpha.29 - edit the /etc/xdg/aard/uxselect.conf file to include the following section:
+
Daily unstable images of a Kubuntu Active are at
  
<nowiki>
+
http://cdimage.ubuntu.com/kubuntu-active/daily-live/
[plasma]
 
  
name=Plasma Active
+
You can burn image to CD (e.g. with k3b) or USB (e.g. with usb-creator-kde)
  
description=The Plasma Active Tablet UX
+
https://help.ubuntu.com/community/BurningIsoHowto#Kubuntu
  
# Use this in Plasma Active One
+
It includes an installer '''ubiquity'''.
#path=/usr/bin/startkde
 
  
# Use this in Plasma Active Two
+
== openSUSE ==
path=/usr/bin/startactive
 
</nowiki>
 
  
and add the text plasma text to the uxlist property in the General section.
+
PlasmaActive has been packaged for opensuse in the KDE:Active OBS Repository.
 +
Mind that it is ALPHA Quality. The apps that come with a Mer-based image might not be available and there may be bugs. Feel free to report (and fix) them or improve the packaging process. Help will be welcome!
  
==== Known Issues ====
+
It can be installed as follows:
  
The Meego tablet UX installs a number of files in /etc/xdg/autostart that are also executed when running Plasma Active, resulting in elements of the Meego tablet UX showing up nevertheless. Workaround is to rename/remove that folder.
+
zypper ar http://download.opensuse.org/repositories/KDE:/Active/openSUSE_Factory PA
  
=== Installing Additional Software ===
+
zypper ref && zypper install plasma-mobile declarative-plasmoids  bodega-client
  
There are a few KDE projects that have created touch friendly versions of their applications already. These versions are included in the MeeGo repository. Currently, these are:
+
If the Maliit onscreen keyboard is wanted, additionally install maliit-framework maliit-plugins maliit-inputcontext-qt4
  
* Calligra Active - Install package calligra-active
+
Only i586 has been tested. To run PA4 the preferred method is to create a .xinitrc file in the home directory and add a line saying 'startactive'. Then a call to 'startx' will bring it up.
* Kontact Touch - Install package kontact-touch
 
  
In addition, some applications already work quite well together with Active. The following is a list of applications that work ok on a touchscreen:
+
There currently is an issue with plasma-desktop beeing started automatically so the file '/usr/share/autostart/plasma-desktop.desktop' needs to be (re)moved before running PlasmaActive.
  
* Okular - For viewing documents.
+
There is also a LiveCD available at http://susestudio.com/a/GzMWEV/activesuse
* Marble - Virtual globe, includes routing support.
 
* Konsole - Support for virtual keyboard
 
  
=== MeeGo system image===
+
= Get started after install =
For a complete ready to go image of Plasma Active see [[Plasma/Active/Installation#Live_Images|Live Images]].
 
  
== Other Systems ==
+
[http://community.kde.org/Plasma/Active/Info Suggestions, FAQ, additional information]
If you have installed Plasma Active on a system not yet listed here, please add detailed installation instructions in a new section.
 

Latest revision as of 19:53, 16 June 2015

Plasma Active Images

The Plasma Active team provides official Images based on Mer for some devices.

Supported

WeTab / ExoPC

The hardware is a little outdated but you will get the most polished Plasma Active experience on this device.

Take a look at the installation instructions here.

Preview

Nexus 7

Even though very much already works reasonably well, there are still some glitches. So, please don’t expect a 100% working system. For detailed installation instructions, see the article on the Mer Wiki

Archos G9

Take a look at Ruedigers Blog for more information.

Nokia N950

Take a look at this OSnews article for more information.

VirtualBox

When running Plasma Active in a virtual machine, consider that performance will not be as good as when it runs naively on the devices it has been designed for. For testing, we strongly recommend running Plasma Active on a device. The following limitations need consideration when using a virtual machine instead of a real device:

  • Performance, especially graphics, boot and application startup might be reduced
  • Advanced visual effects might not be available or work correctly in the virtual machine. This can lead to degradation of certain features, performance, visual effects and possibly stability
  • User interfaces designed for touch-screens often work less efficiently for mouse and keyboard based input methods, or feel less natural.


For detailed installation instructions, see this installation manual.

Downstream Plasma Active

Some distributions provide Images with Plasma Active for x86 Systems.

Kubuntu Active

Current stable release of a Kubuntu remix with Plasma Active is available at

http://cdimage.ubuntu.com/kubuntu-active/releases/13.04/release/

Daily unstable images of a Kubuntu Active are at

http://cdimage.ubuntu.com/kubuntu-active/daily-live/

You can burn image to CD (e.g. with k3b) or USB (e.g. with usb-creator-kde)

https://help.ubuntu.com/community/BurningIsoHowto#Kubuntu

It includes an installer ubiquity.

openSUSE

PlasmaActive has been packaged for opensuse in the KDE:Active OBS Repository. Mind that it is ALPHA Quality. The apps that come with a Mer-based image might not be available and there may be bugs. Feel free to report (and fix) them or improve the packaging process. Help will be welcome!

It can be installed as follows:

zypper ar http://download.opensuse.org/repositories/KDE:/Active/openSUSE_Factory PA

zypper ref && zypper install plasma-mobile declarative-plasmoids bodega-client

If the Maliit onscreen keyboard is wanted, additionally install maliit-framework maliit-plugins maliit-inputcontext-qt4

Only i586 has been tested. To run PA4 the preferred method is to create a .xinitrc file in the home directory and add a line saying 'startactive'. Then a call to 'startx' will bring it up.

There currently is an issue with plasma-desktop beeing started automatically so the file '/usr/share/autostart/plasma-desktop.desktop' needs to be (re)moved before running PlasmaActive.

There is also a LiveCD available at http://susestudio.com/a/GzMWEV/activesuse

Get started after install

Suggestions, FAQ, additional information


This page was last edited on 16 June 2015, at 19:53. Content is available under Creative Commons License SA 4.0 unless otherwise noted.