Re: repos and kickstarts for pa4

2013-05-23 Thread Paul S
On Wed, May 22, 2013 at 12:49 PM, Thomas Pfeiffer colo...@autistici.orgwrote:

 I'd just like to initiate a shift in mindsets: From PA on Mer does not
 work correctly on my device!, which we hear from pretty much everyone who
 tries to use it on a device where nobody used it before, to I see that a
 lot of work still has to be put into making it work on this device. How do
 we get that work started?

 Of course the problem is: How do users distinguish bugs related to
 hardware integration from actual PA- or Mer-Bugs? This is a problem I have
 no solution for yet. One indicator might be that it's a fairly obvious and
 critical bug which has not yet been reported on bugs.kde.org. In this
 case, it's unlikely that it happens on the devices we use as well without
 having been reported yet.


I think there's big potential for the x86 users like my lenovo s10-3t to
use pa4. However, there's a an xorg bug holding back x86 users since
January 2012. But, the bug is close to being fixed.
https://bugs.freedesktop.org/show_bug.cgi?id=56578 for you info. Perhaps it
will be done for the fall distro updates.

Right now the best x86 touchscreen experience is androidx86, but it has the
same problems that mer does, for example, you can't even print and the eth0
does not work on android.

Now that I understand mer better, let me ask the question, would it be
possible for the xorg server used on mer to be ported to another distro?
For example, if kubuntu-active ran like mer, I think it would attract a
huge touchscreen user base.
___
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


Re: repos and kickstarts for pa4

2013-05-22 Thread Paul S
On Wed, May 22, 2013 at 7:51 AM, Thomas Pfeiffer colo...@autistici.orgwrote:

 It seems like you are confusing MeeGo and Mer. Mer is a community
 continuation of MeeGo. Our images do not use MeeGo, it's just Mer, with
 Plasma Active on top and the Nemo Mobile integration parts (e.g. the
 kernel) below.


Yes I was, thanks for correcting my ignorance.

Complaining is the one thing that won't help you.

I apologize if it sounds like just complaining. I was trying to provide
useful feedback of an early image. Perhaps my words aren't as good as they
should be. I hope no hard feelings.
___
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


Re: repos and kickstarts for pa4

2013-05-21 Thread Paul S
On Tue, May 21, 2013 at 6:10 PM, Michael Bohlender 
michael.bohlen...@kdemail.net wrote:


 I'm trying this as a live disk on my lenovo s10-3t and notice that the
 about screen says it's version 3 still, instead of version 4.


I didn't realize how crippled meego is for something like my netbook. Even
though I loaded my wireless module bcrmsmac and got no errors in dmesg, I
can't find a way to create the wlan0 device. So no wifi here. Also, I
notice it takes 8 to 9 minutes to get it to wake up from sleep. I've done
this 3 times, so it's not a fluke .. Also, I tried installing firfox from
mozilla.org, and can't get it to run. Why would anyone with X86 hardware
want to run this crippled meego? I think you should stop producing it.

On the other hand, I tried kububu-active sausy iso from yesterday and it
won't give me a usable screen. It boots to a screen that's divided into 3
or 6 of the same image in each third or 6th of the screen.

It's too bad you can't use the mer from your meego distro with kubuntu.

The mer part seems pretty useful and stable. I didn't have any crashes yet
and the touchscreen is working fine. These are the parts that never work on
kubuntu.
___
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


Re: need help starting kde plasma-mobile

2013-05-02 Thread Paul S
On Thu, May 2, 2013 at 6:06 AM, Aaron J. Seigo ase...@kde.org wrote:

 **

 On Wednesday, May 1, 2013 15:06:00 you wrote:
 Yes, because there is a plasma-desktop.desktop file installed to
 `kde4-config --prefix`/share/autostart and ksmserver starts things in there.



 As long as the contents of that autostart dir in the $KDEDIRS when plasma
 active starts, plasma desktop will also be started.

 In my case, it's /usr/local/share/autostart and this is the contents:

kaddressbookmigrator.desktop
konqy_preload.desktop
nepomukcontroller.desktop
plasma-desktop.desktop
kalarm.autostart.desktop
korgac.desktop
nepomukserver.desktop
contour.desktop
klipper.desktop
krunner.desktop
plasma.desktop

Should I remove all of these or just plasma-desktop and
plasma-desktop.desktop?
___
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


Re: need help starting kde plasma-mobile

2013-05-02 Thread Paul S
On Thu, May 2, 2013 at 7:26 AM, Aaron J. Seigo ase...@kde.org wrote:

 **

 On Thursday, May 2, 2013 06:32:32 you wrote:

  On Thu, May 2, 2013 at 6:06 AM, Aaron J. Seigo ase...@kde.org wrote:

 if you want to run plasma desktop on the same machine, you'll need to move
 them to another root and adjust the KDEDIRS based on whether you are
 starting plasma desktop or plasma active.



 e.g. plasma desktop might have /usr/local/plasma/desktop/ (with
 share/autostart under it) in its KDEDIRS



 plasma active would have /usr/local/plasma/active/ in its with the
 contents of plasma-mobile-config in there.

 OK, thanks.

If I wanted to build just a plasma-mobile ptoject using kdesrc-build, what
could I exclude from my ~/.kdesrc-buildrc file, following:

# Autogenerated by kdesrc-build-setup. You may modify this file if desired.
global
use-stable-kde true
qtdir ~/qt
#remove-after-install
# KDE install directory
kdedir ~/kde4
# Directory for downloaded source code
source-dir ~/kdesrc
# Directory to build KDE into before installing
build-dir build
# Use multiple cores for building. Other options to GNU make may also be
# set.
make-options -j2
end global

module qt
configure-flags -fast -debug -system-zlib -system-libpng
-system-libjpeg \
-plugin-sql-mysql -no-phonon \
-dbus -webkit -nomake examples -nomake demos
# KDE's unmodified copy of Qt is used by default since git.kde.orgsupports
# cloning the module more reliably than gitorious. To use standard Qt as
# provided by Nokia, comment the following line and uncomment the next
# repository line.
repository kde:qt
# Nokia's Qt. Note that gitorious has had known issues checking out
large
# git modules such as Qt. If there are failures try using KDE's qt (see
# above).
# repository git://gitorious.org/qt/qt.git
branch 4.8
end module

module shared-desktop-ontologies
repository git://
oscaf.git.sourceforge.net/gitroot/oscaf/shared-desktop-ontologies
branch master
end module

# These encompass modules that are not directly a part of KDE proper but are
# required or highly recommended for the KDE framework and are developed in
# the KDE source repository.
module-set baselibs-support
repository kde-projects
branch master
use-modules automoc cagibi attica soprano polkit-qt-1
end module-set

# Phonon provides the KDE multimedia layer. It requires an appropriate
backend
# to be installed to actually implement multimedia.
module-set framework-phonon
repository kde-projects
branch master
use-modules phonon/phonon phonon-gstreamer phonon-vlc
end module-set

# Strigi provides file analysis tools for extracting information from files
# (e.g. music length, picture size, etc.) It is split into several
submodules
# so do not alter the order in the use-modules below.
module-set strigi
repository kde-projects
branch master
use-modules strigi/libstreams strigi/libstreamanalyzer
strigi/strigiutils \
strigi/strigidaemon strigi/strigiclient
end module-set

# libdbusmenu is needed to support new-style Plasma system tray icons and
# support in the Unity shell. Installing a recent development package from
your
# distribution should be sufficient, but if you want to have the latest then
# make sure you have the Bazaar program installed and uncomment the
# following:
#module libdbusmenu-qt
# The lp: prefix refers to Canonical's Launchpad repository
#repository bzr://lp:libdbusmenu-qt
#end module

module taglib
repository git://github.com/taglib/taglib.git
# Note: -DWITH_ASF=TRUE and -DWITH_MP4=TRUE (for taglib) is required to
# allow Amarok (defined below, near the end of this file) to build.
cmake-options -DWITH_ASF=TRUE -DWITH_MP4=TRUE
end module

# Base/essential KDE libraries and the required runtime programs.
# Split into two module-sets to setup the right branch for kdelibs.
module-set baselibs-kdelibs
repository kde-projects
use-modules kdelibs
end module-set

module-set baselibs-other
repository kde-projects
use-modules kactivities kde-runtime nepomuk-core
end module-set

module-set baselibs-pimlibs
repository kde-projects
use-modules akonadi kdepimlibs
end module-set

module-set workspace
repository kde-projects
use-modules kde-workspace kdeplasma-addons
end module-set

module-set base
repository kde-projects
# kde-baseapps requires kate to be built first.
use-modules kate kde-baseapps konsole
end module-set

# icons and such:
module kdesupport
end module

module-set pim
repository kde-projects
use-modules nepomuk-widgets kdepim-runtime kdepim
end module-set

module-set user-modules
repository kde-projects
use-modules plasma-mobile calligra-active bangarang kontact okular
marble startactive plasma-mobile-config
end module-set
___
Active mailing list