Wie Marco Martin und Nuno Pinheiro heute Früh berichteten, ist das Standard Plasma Theme für KDE 4.3, Air, jetzt im SVN.

Plasma Theme Air: Kubuntu 9.04 Jaunty + KDE 4.2 Beta 2 + Air

Ich habe KDE 4.3 in der Beta 2 installiert und konnte natürlich nicht bis zum RC warten und habe mir Air nachinstalliert. Dabei habe ich mich für die Installation innerhalb meines persönlichen Ordners entschieden.

Wer Air ebenfalls Installieren möchte, muß lediglich folgende 2 Befehle ausführen:

• cd ~/.kde/share/apps/desktoptheme/
• svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase/runtime/desktoptheme/air

Jetzt nur unter "Arbeitsflächen Einstellungen" auf "Air" umstellen.

Viel Spaß

Has been a time since I wrote the last update for PHP / webdevelopment related work in KDevelop4…

XDebug

First of all, Niko (nsams) is working diligently on the general debugger framework for KDevelop4. Of course gdb is still the main focus so far yet he always has his XDebug plugin (which is currently unusable) in mind. So expect some great debugging features once he’s done with the framework.

Remote Projects

Another thing I’ve not yet written about is a bunch of commits I did just after the Hackaton: Remote Projects! Yes, finally you can work directly on the server with KDevelop. I still have to make sure that the user does not try to open a remote cmake project (or similar), because that is of course not supported. Only the Generic Project Manager (basically a list of files in a dir) works. There’s for sure some things to polish, yet I’d like to see user feedback for that use-case at least.

Note: There is still some functionality missing in other areas, like creating a new remote project from a template etc.

Out-of-class declarations of member variables

The PHP plugin itself got support for some more code, like declarations of members variables outside the class context which was reported by one of our early adopters (hint hint - do the same! we need more wishes and bug reports!).

Improved DeclarationBuilder

Additionally I changed the logic of our DeclarationBuilder so it does not create a new variable declaration for each assigment expression. I think this makes refactoring, use-highlighting etc. in a PHP environment much better for many cases. Sadly it is not yet perfect since we still need to redeclare variables when their type changes. Fixing that would require potentially big changes to the DUChain and I’m not sure when it will happen.

Error Reporting

Furthermore I’ve added some more inline error reportings, namely for redeclaration of $this in a class context. This is also an area where you might help us a lot: Send us PHP snippets which fail when executed but are not yet highlighted in the editor. I’ll try to add them then. Just use the bugtracker on http://bugs.kde.org.

Performance

Also David (dnolden / zwabel) of Cpp-KDev4 fame made some changes which resulted in a good performance win. Thanks!

Ok, just a quick update on what we are doing / have done the last two days except drinking beer and eating quite a lot of food (though it never seems to be enough somehow….)

• Apol was polishing CMake support, speeding up KDevelop startup time when you enabled the QtHelp plugin, making sure that Kross plugins get loaded properly and some other things
• Adymo started some refactoring of Sublime in an experimental branch (actually they had quite a long discussion right now about things in the UI which should be changed/fixed). Besides that he also fixed some little bugs in the includepath resolver for CMake
• Nsams is fixing PHP support and adding new features here and there. Esp. completion inside a foreach over a Iterator class works now!
• and as always ZWabel did fix quite a lot of bugs, most of them which only were discoverable in a few corner cases, very nice indeed.
• shaforo who sadly already left us again to attend university fixed the sorting in the Project view among other things
• With Apols help I managed to get started with a documentation plugin which (currently) integrates PHP.net. I plan to make it possible to use the downloadable PHP.net documentation as well to speed things up. Actually setting up a documentation plugin is very easy! Maybe I’ll take a look at writing a documentation plugin for Zend, Symfony, etc. pp. as well - should be fairly easy. Maybe I can come up with a generic documentation plugin which makes it possible to include any kind of .html documentation with some configurable mapping… lets see! Or maybe I should take a look at writing Kross plugins (Apol could help me here as well) for that purpose.

Except these changes we also discussed how to support dynamically typed languages like PHP, Ruby, Python and JavaScript better. One result of it that we now plan to fully support the dedicated map types of each language, with autocompletion and such. Of course that won’t be possible for 100% of the use-cases, but we hope to support at least the most common ones (i.e. 90%). You can take a look at http://www.kdevelop.org/mediawiki/index.php/SupportForDynamicMaps for more information.

Additionally Nsams, Apol and Zwabel took a look at the GDB plugin and started working on it a bit. It’s still a work in progress though.

My biggest change is that color highlighting support for dark color schemes now is in trunk. It automatically adapts to changes in the global KDE color scheme, yet you still have to manually change the Kate color scheme. Actually I intend to add an interface to Kate so we can use it’s color schemes instead of the global KDE one - makes much more sense and would fix some bugs (i.e. fix from dark color scheme to a light one). Here’s a screenshot of it (with the PHP.net documentation showing):

dark color scheme and syntax highlighting in KDevelop 4

If you followed the planet kde you might have seen some blog posts about color reception and color generation by Ariya Hidayat. I will take a look at it and implement it in KDevelop. Or I simply pick a given set of colors and use them - for 10 colors or so we need it doesn’t make that much sense to let them be generated. Yet the article he linked to about adaptive coloring for syntax highlighting will be helpful I think! Thanks!

Yet it currently works quite well I’ll first try to fix the colors in the Declaration tooltip, quickopen and codecompletion lists.

So stay tuned for more KDevelop goodness throughout the next days.

Facts

• Kubuntu (needs to) import KDE's translations (+po templates, +desktop file translations, +desktop file po templates) into Launchpad's translations system Rosetta
• Those translations then can be changed and/or enhanced
• Changed translations don't automagically get overriden by a new upstream import but have to be reviewed by the translation team
• Changed translations have to be manually upstreamed by the translator or the translation team (thus implying that one should either have direct access to upstream's po files or file loads of bug reports)
• Rosetta makes new contributors contribute to out-of-date translations
• Rosetta failed to properly support KDE 3's po format for years
• Rosetta's interface is difficult to use
• Rosetta has no clue when a package gets removed from the archives or superseded with a new major version that does not ship the once available translation template
• Kubuntu's localization breaks at least once every release cycle, always as close to release as possible
• Kubuntu string changes/additions don't get translated at times
• Kubuntu needs to maintain patches to keep that whole construct of import-breakage-export working

Rants

Import

Having to import all main applications' l10n related data to a distribution specific tool for enhancement and bug fixing is a completely sane thing to do. Of course, if the whole process would not be bound to the build process (i.e. if it could be supervised outside the build process) it would be a lot easier to notice/track/find issues, and god knows there are loads of those (at least for KDE imports). It probably would also help if rosetta wouldn't need ages to process the data for import. But hey, what can you do, it's a bottlenecked design.

So, assuming that the data ended up properly in Rosetta (which is not always the case, though it arrived there ... I guess you can imagine what I'm talking about), now a nice community member can start fixing bugs or enhance the translation (to pick up on the bottleneck: if the template is imported but the po is not, there will be loads of untranslated strings ... again I'm quite confident that you see the implication here).

Leon is Kubuntu user. He is speaking German and wants to help translate KDE. Being a user who actually knows about the need of translation he knows that the translations are being handled over at Launchpad. So he commands to konquer launchpad.net. Right at the top there is a link to Translations. Leon clicks.

On the translations main page he finds a link to the translations for Ubuntu 9.04. Again he follows that link.

Oh dear, what a load of red!!!!

Anyway, he scrolls down and eventually finds german.

So far so good, now Leon just needs to find some KDE application.

Hum... Leon reads kdesktop and kicker, having used KDE for quite some time he knows that this stuff was replaced in KDE 4 and is not even available in the archives anymore, so he avoids them, luckily they are fully translated anyway.

On the very same page he finds konqueror with one untranslated string. He thinks that one untranslated string would be a perfect starting point so he wants to give it a shot.

Our character filters for untranslated items having no clue what the guide filter means as there is only none or german.

The suggested translation "Textmarken" from openoffice's translations sounds about right so he applies that. For those who don't know, the KDE default translation for bookmark in german is "Lesezeichen", Leon doesn't know that, and neither does Rosetta. JohnTooray suggested "Lesezeichen" but that was almost 2 months ago, so one must assume it was not very much liked, so for the scenario's sake we will just ignore that there is already a suggestion.

Leon submits his suggestion "Textmarke" and goes on walking through >20 pages of templates trying to find more KDE stuff to translate.

[timelaps]

---

I hope you see the flaws I tired to highlight, in that very simple example use. Those are mostly non-technical problems, I have talked about the technical ones so often on IRC and in various meetings that I am simply tired of repeating myself all the time.

Export

Communication

Latest example: "lets go rape our packages of their desktop file translations" which was done less than one month before release of 9.04 without any warning.

Cause: The Kubuntu patch for grabing desktop file translations from .mo files was not working + the translations were not imorted + the templates were not imported + no-one ever warned us

This isn't news at all. A flickr image set is watching the progress of Kubuntu since 8.04 (though it is, with exception of 8.10, mostly tracking in-development progress, then again how much localization QA can you expect when it is horribly broken half the time).

Also if you speak german you might want to check out the latest KDE-de thread about Kubuntu's state of translation, they also had a similar one for 8.10, where they considered various crude but understandable actions in how to handle this issue. After all the KDE l10n teams probably get most of the complaints, because the user is lead to believe that it's a problem there.

Conclusion

So, finally just let me get my position straight.

1. Rosetta is the best example why rolling release does not work in every case
2. I raised my concerns about the constant issues and lack of quality coming out of Rosetta... for I think the last year or so
3. Most people do not speak English, and if they do as second language I find it doubtable that they do well enough to use an operating system in English
4. Ubuntu touts itself as believing it's important for everyone to have a computer that works in their own language, yet the project as whole (Kubuntu being part of that larger Ubuntu) fails to meet that very claim most of the time
5. I pity all those that have to use Rosetta in order to make their desktop not speak 2 languages at the same time, as well as those that have to live with constant complaints coming from Kubuntu users
6. I am deeply sorry that I can't help either of them, due to the very nature of Rosetta still not being open source
7. Should this crap continue I am going to leave the Project and join Debian or Fedora, I am not going to waste my time on a system that is constantly breaking due to external (meaning not caused by the Kubuntu crew) screwups
8. Comments on how to improve the situtation (i.e. what Kubuntu should do in order to get out of all this) are greatly, because I'd rather not leave a project I have spent most of my spare time on for the last couple of years

Ok, a short blog about the first day of our KDevelop Hack Sprint at Mykolayiv (see my first blog post). First up, being in the Ukraine is a very interesting experience since it’s totally different from any place I have ever been to. And thanks to the great hospitality of Alexander (adymo) we already had a city tour of Odessa and Mykolayiv.

Tomorrow will be the first real day of our hack sprint: Today we only hacked at our flat for a few hours. Before that we had the city tour through Mykolayiv. And tomorrow David Nolden (zwabel) and Nick Shaforostoff will arrive which will make the list complete.

Today I personally worked on making KDevelop support dark color schemes better which is still a work in progress (nothing comitted so far). Actually for a real good experience I’ll have to extend KTextEditor to make it’s color configuration available for the parent application (i.e. KDevelop). Let’s see when I get to that. Though I plan to push my patches to KDevplatform beforehand for an intermediate solution.

Random other notes about Ukraine: - I love the Vodka (esp. with its prices) here! - breakfast at a cafe is pretty much a no-go here it seems - street lights are luxury - very many old building all across the city, looks pretty good. Though would look even better if all of them would be in a good shape… Yet I still prefer it that way - I hate what was done to Berlin after the war, i.e. that they teared most of the old buildings apart instead of repairing them…

So, lets see what tomorrow brings, now I’m back to some more hacking :)

des kritischen Journalismus in Deutschland:

4. Macht, my ass!

Es ist nicht so einfach für uns Ressourcen für andere Projekte, als die die wir momentan betreuen, frei zu machen, denn ehrlich gesagt, arbeiten wir immer am Rande unserer Kräfte und sind überlastet. Es gibt zur Zeit nicht sehr viele kubuntu-de.org Mitglieder und für mich ist es daher beeindruckend, dass mcas aka Marcus Asshauer und Tscheesy aka Marcus Kälin gemeinsam mit einem neuen Nutzer namens “denis” in so kurzer Zeit die kubuntu-docs in das Deutsche übersetzt haben und nun sogar vor der Deadline fertig sind. Daneben ist mir die Zusammenarbeit mit dem ubuntu-l10n-de Team, das auf einfachem Weg erlaubt hat die Übersetzungen beizusteuern, sehr positiv aufgefallen. Vielen Dank dafür und für die klasse Arbeit.

Besonders froh bin ich über die Teilnahme von “denis” (”hat wie eine Maschine übersetzt”). Wir haben in den letzten Monaten leider ein paar wichtige Leute im Team verloren und es ist wirklich gut auch mal wieder neue Helfer zu sehen. Ich möchte auf diesem Wege von daher auch noch einmal loswerden, dass wir jede Hilfe gebrauchen können. Vor allem die arbeitsintensive Redaktion ist immer ein Anlaufpunkt, daneben gibt es natürlich auch immer im technischen Bereich etwas zu tun.

Falls sich wer gewundert hat, warum sein Kommentar so lange in der Warteschleife hängt: Ich habe ein paar Kommentare erst heute gesehen. Drupal verschickt in der Standardinstallation keine Benachrichtungen, wenn neue Kommentare gepostet werden. Allerdings lässt sich diese Funktionalität leicht mit dem Workflow-NG Plugin nachrüsten. Wie das funktioniert erklärt dieser Screencast.

Die Freischaltung der Kommentare geht ab jetzt also schneller. ;)

Weiterlesen

Wer schon Kubuntu Jaunty einsetzt (was ich auf keinen Fall empfehlen kann), hat vielleicht das Problem, dass nur KDE Anwendungen Sound ausgeben können, während andere Anwendungen (z. B. VLC oder Flash) stumm bleiben. Ich konnte das Problem mit folgendem Kommando lösen:

asoundconf set-pulseaudio

A quick meta-blog about nothing directly KDE related, but I think those of you who can understand German should see it nonetheless. Hope you don’t mind me spreading it on the planet:

I just stumbled upon a great video about the definition of “being a nerd”. You can watch it here:

http://www.elektrischer-reporter.de/elr/video/115/ (note: it’s in German!)

I have to say that I can identify myself with the message of the video, very nicely done. Must see for anyone! I’ll spread it in my circle of friends so they understand me better when I talk (proudly) about being a geek.

Deutsche Version

Hey Leute,

ich habe nun playwolf-0.7.1 für Kubntu 9.04 gepackt.

Playwolf ist ein echt cooles Now-playing-plasmoid Amarok2. Es kommt Kirocker sehr ähnlich und wird laut Entwickler auch diesem immer ähnlicher werden.

Pakete können direkt aus dem Anhang heruntergeladen werden oder ihr installiert es über adept, indem ihr meine Paketquelle einbindet.

deb http://ppa.launchpad.net/kopf-alexander/ppa/ubuntu jaunty main

Genauere infos zu meiner Paketquelle auf Launchpad

Weiterlesen

Nach über fünf monatiger Entwicklungszeit haben die Kubuntu Devs gestern die erste Beta Version von Kubuntu 9.04 “Jaunty Jackalope” freigegeben. Mutige Nutzer sind natürlich wie immer aufgerufen die neue Version zu testen und es wäre klasse, wenn dann auch gleich unsere deutschsprachige Anleitung zur Aktualisierung überprüft würde.

In Anbetracht des unfertigen Zustandes von Adept3 haben wir uns entschlossen eine Anleitung für die Kommandozeile zu schreiben und zu veröffentlichen. Der Vorgang ist allerdings nicht schwer und hoffentlich so genau beschrieben ist, dass auch Anfänger damit gut zurecht kommen.

Hinweise zur Verbesserung bitte auf der Diskussionsseite, gleich im Text oder natürlich als Kommentar hier im Blog. Vielen Dank.

Eigentlich wollte ich ja nicht mehr über persönliche Dinge bloggen, aber ich glaube, dass es sich hierbei um eine typische FOSS Situation handelt. Irgendwie bin ich wohl in einer dieser berühmten Burnout Situationen, da ich immer weniger mit den Ergebnissen und vor allem den Reaktionen auf meine Arbeit zufrieden bin. Es hängen dann doch so einige Dinge von mir ab und ich bringe es einfach nicht über mich sie einfach aufzugeben. Oft handelt es sich um Dinge, die ich selbst initiiert habe oder solche an denen ich mit vollem Herzen hänge, ich habe sie alle wirklich immer gerne betreut, obwohl ich eigentlich überhaupt keine Zeit dafür habe und ich mich wirklich um andere Dinge kümmern sollte. Mein Examen rückt immer näher und ich stelle fest, dass ich manchmal, sicher unangebracht allergisch, auf Kiritik, besonders, wenn sie in meinen Augen nicht angebracht ist, reagiere. Ich bin kein Entwickler und dazu habe ich auch eher wenige Dinge zu Kubuntu beigesteuert; manchmal bin ich sicher dazu auch noch ein echt mieser Supporter, sieht so aus, als wäre meine Arbeit ziemlich unbedeutend. Kubuntu-de.org existiert nun schon einige Jahre und wir haben natürlich nie unsere Ziele erreicht, was aber für mich ziemlich normal ist, denn man möge mir ein Projekt zeigen, das genug Personal hat oder ausreichend positives Feedback bekommt. Viele der Teammitglieder sind für mich im Laufe der Jahre zu guten Freunden geworden und viele davon haben das Projekt auch frustriert verlassen, alle haben dabei aber fantastische Arbeit geleistet und ich mag sie wirklich alle. Ich möchte keinen enttäuschen.

Mich würde interessieren, wie ihr mit solchen “Burnout” Situationen umgeht und bin sicher, dass viele von euch schon mal eine solche Phase durchgemacht haben. Ich freue mich auf eure Antworten?

Unit tests are in my eyes a very important part of programming. KDE uses them, KDevelop does - the PHP plugin I help writing does as well. cmake comes with a ctest program which does quite well to give you a quick glance on which test suite you just broke with your new fance feature :)

But I am very dissatisfied with it. Right now I usually do the following

# lets assume I'm in the source directory
cb && ctest
# look for failed test suites
cd $failed_test_suite_path
./$failed_test_suite.shell | less
# search for FAIL
cs
cd $to_whereever_I_was_before

That’s pretty much for just running a test. Especially all that cding and lessing became very tedious. Tedious is good, because I eventually fix it:

introducing kdetest

I wrote a bash function (with autocompletion!!!) called kdetest. Calling it without any parameter will run all test suites and gives a nice report of failed functions at the end. Here’s an example (run via cs php && kdetest).

kdetest
# ... lots of test output
 
 --- ALL PASSED TESTS ---
...
PASS   : Php::TestCompletion::implementMethods()
PASS   : Php::TestCompletion::inArray()
PASS   : Php::TestCompletion::cleanupTestCase()
 
143 passed tests in total
 
 --- ALL FAILED TESTS ---
FAIL!  : Php::TestCompletion::newExtends() Compared values are not the same
FAIL!  : Php::TestCompletion::updateExtends() '! forbiddenIdentifiers.contains(item->declaration()->identifier().toString())' returned FALSE. ()
FAIL!  : Php::TestCompletion::updateExtends() '! forbiddenIdentifiers.contains(item->declaration()->identifier().toString())' returned FALSE. ()
FAIL!  : Php::TestCompletion::updateExtends() Compared values are not the same
FAIL!  : Php::TestCompletion::newImplements() Compared values are not the same
FAIL!  : Php::TestCompletion::updateImplements() Compared values are not the same
 
6 failed tests in total

usage

• kdetest, i.e. without any arguments runs all tests in this directory and below
• kdetest path/to/test.shell ... runs that test suite only, ... can by any argument the test suite accepts.

autocompletion

kdetest comes with full support for autocompletion of tests and functions, for example:

milian@odin:~/projects/kde4/php$ kdetest TABTAB
completion/tests/completiontest.shell     duchain/tests/expressionparsertest.shell  parser/test/lexertest.shell
duchain/tests/duchaintest.shell           duchain/tests/usestest.shell
milian@odin:~/projects/kde4/php$ kdetest duchain/tests/usestest.shell TABTAB
classAndConstWithSameName          classSelf                          interfaceExtendsMultiple           staticMemberFunctionCall
classAndFunctionWithSameName       constAndVariableWithSameName       memberFunctionCall                 staticMemberVariable
classConstant                      constant                           memberFunctionInString             variable
classExtends                       constantInClassMember              memberVariable                     variableTwoDeclarations
classImplements                    functionAndClassWithSameName       memberVarInString                  variableTwoDeclarationsInFunction
classImplementsMultiple            functionCall                       newObject                          varInString
classParent                        interfaceExtends                   objectWithClassName

the code

You can find the code below, or you can obtain the most up-to-date version on github. Just head over to my shell-helpers repo and peek into the bash_setup_kde4_programming file.

# run a given unit-test or all via ctest
function kdetest
{
  local tests test args old_pwd tmpfile;
 
  old_pwd=$(pwd)
  cb
 
  tests=$(LANG=en_US.UTF-8 ctest -N -V | grep "Test command:" | cut -c $(echo "Test command: $(pwd)/" | wc -c)-)
 
  if [[ "$tests" == "" ]]; then
    echo "this directory does not contain any unit tests!"
    echo
    cd "$old_pwd"
    return 1
  fi
 
  tmpfile=/tmp/testoutput_$$
 
  if [[ "$1" != "" ]]; then
    test=$1
    shift 1
    args=$@
 
    if [ ! -f "$test" ] || ! in_array "$test" $tests ; then
      echo "could not find unittest '$test'. available are:"
      echo $tests
      echo
      cd "$old_pwd"
      return 1
    fi
 
    ./$test -maxwarnings 0 $args | tee -a "$tmpfile"
    echo
  else
    # run all tests
    for test in $tests; do
      ./$test -maxwarnings 0 | tee -a "$tmpfile"
    done
  fi
 
  echo
  echo " --- ALL PASSED TESTS --- "
  grep --color=never "^PASS " "$tmpfile"
  echo 
  echo $(grep -c "^PASS " "$tmpfile")" passed tests in total"
 
  echo
  echo " --- ALL FAILED TESTS --- "
  grep --color=never "^FAIL!" "$tmpfile"
  echo
  echo $(grep -c "^FAIL!" "$tmpfile")" failed tests in total"
 
  rm "$tmpfile"
 
  cd "$old_pwd"
}
 
# completion for kdetest
function _kdetest
{
  local tests;
 
  old_pwd=$(pwd)
 
  cb
  tests=$(LANG=en_US.UTF-8 ctest -N -V | grep "Test command:" | cut -c $(echo "Test command: $(pwd)/" | wc -c)-)
 
  COMPREPLY=()
  cur="${COMP_WORDS[COMP_CWORD]}"
  prev="${COMP_WORDS[COMP_CWORD-1]}"
 
  if [[ "$prev" == "kdetest" ]]; then
    # completion of tests
    COMPREPLY=( $(compgen -W "${tests}" -- ${cur}) )
  elif in_array "$prev" $tests; then
    # completion of available functions
    COMPREPLY=( $(compgen -W "$(./$prev -functions 2>/dev/null | cut -f 1 -d \( )" -- ${cur}) )
  fi
 
  cd "$old_pwd"
}
 
complete -F _kdetest kdetest
 
# see http://ftp.hu.freebsd.org/pub/linux/distributions/frugalware/frugalware-testing/t/functions.sh
function in_array
{
  local i
  needle=$1
  shift 1
  # array() undefined
  [ -z "$1" ] && return 1
  for i in $*
  do
    [ "$i" == "$needle" ] && return 0
  done
  return 1
}

Die Jugend von heute liebt den Luxus, hat schlechte Manieren und verachtet die Autorität. Sie widersprechen ihren Eltern, legen die Beine übereinander und tyrannisieren ihre Lehrer.

(Sokrates, griechischer Philosoph, 469 - 399 v. Chr.)

Schlimm diese Jazz-Musik Comics Rock'nRoll-Musik Hippies Punks Killerspiele.

Weiterlesen

Bevor ich zu indenti.ca gewechselt bin habe ich Twibble genutzt, um meinen Status zu aktualisieren. Leider konnte ich bisher keinen identi.ca Client für mein N95 finden, so dass ich unterwegs auf Microblogging verzichten musste. Vorhin bin ich über Mobiidentica gestolpert und nun kann ich wieder ohne Probleme meine “Dents” posten. Das Programm ist sehr einfach, aber dafür funktional gehalten und einen Versuch wert.

I read about choqoK 0.5 to be released at 21st of March because it is spring time then. So it is testing time again and there are new svn packages in my ppa. ChoqoK 0.5 has a shiny new interface and a couple of long waited features are added. Please report bugs via mail to the author or send a dent with “!choqok”.

You can use my ppa by adding


deb http://ppa.launchpad.net/neversfelde/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/neversfelde/ppa/ubuntu jaunty main


or for Intrepid:


deb http://ppa.launchpad.net/neversfelde/ppa/ubuntu intrepid main
deb-src http://ppa.launchpad.net/neversfelde/ppa/ubuntu intrepid main


to your /etc/apt/sources.list. Import this key to get rid of key error warnings and do a

sudo apt-get update && sudo apt-get install choqok

After that you should delete or comment out the ppa to avoid problems with untested packages.

Im Modul “Persönliche Informationen” kann man einen Benutzeravatar festlegen, der zum Beispiel im Kickoff Menü angezeigt wird. In Jaunty bietet auch das Standardthema von KDM Raum für ein solches Icon, allerdings wird es nicht automatisch hinzugefügt. Um es auch hier einzufügen muss man in den Systemeinstellungen >> Erweitert >> Anmeldungsmanager >> Benutzer >> Benutzerbilder im Dropdown Menü den gewünschten Spitznamen auswählen und natürlich ein Bild festlegen. Nach dem nächsten Start sollte dann auch für den Anmeldebildschirm ein Avatar angezeigt werden. Man sollte beachten, dass man hierfür das Administratorpasswort braucht, denn um KDM zu verändern braucht man Root Rechte.

Dieser Artikel kann im Wiki erweitert und verändert werden.

You can specifiy a user image, which is for example shown in the kickoff menue by providing personal information in systemsettings. In Jaunty’s standard kdm theme there is also room for such an avatar, but it is not automatically added. You have to go to systemsettings >> advanced >> login manager >> user and provide your password, because changing kdm needs root privileges. After that you can change kdm’s user image by selecting your nick in the dropdown menue “User images” and of course changing the picture. Next time kdm should show an avatar, too.