Welcome to Planet openSUSE

This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.

To have your blog added to this aggregator, please read the instructions.


Thursday
10 April, 2014


face

Drazí KDE uživatelé
Možná už jste se dozvěděli o tom všem na openSUSE mailing listu, na blogu nebo přes naší openSUSE Google plus, ale KDE repositáře jsou změněny teprve od minulého úterka.
Níže najdete ty věci, které byly změněny

Proč tyto změny byly potřeba
Na základě malých diskuzí na openSUSE-KDE mailing listu a feedbacku z našeho průzkumu usoudili jsme (většinovým hlasováním), že vytvoříme jediný repositář, kde budeme sledovat
současné KDE vydání.

Kde jsou mé staré KDE repositáře
Jméno pro tento repositář bude KDE:Current a bude nejprve pro oS 12.3 a oS 13.1.
Po vydání KDE:Current repo repositáře KDE:Release:XY byly vyčištěny a odstraněny.
Ze začátku KDE:Current přijde s 4.12.4 a KDE 4.13 je neplánováno na polovinu dubna.
Také repositář KDE: Extra a KDE:Unstable se změní, pro (KDE: Release:XY ) bude nahrazen KDE:Current.

Kde bych mohl najít nové KDE repositáře
Stránka byla updatována, aby reflekovala změny, které proběhly.
Mnoho pozdravů Raymond
http://news.opensuse.org
What’s up on KDE repositories
od:Ricardo Chung
4 Duben 2014


face
Do you love writing elegant and well-understandable code in Ruby? Do you want to do something new that really matters to thousands of people? Do you want to create open-source as your daily job and make openSUSE better? Join us and become a full-time Yast developer!

Yast team is looking for a new "Yastie". Job description can be found here at SUSE Careers page.

face

(screenshot výše : Bodega na mém pracovním stroji.)
Bodega, app story a Open Build Service

Bodega je projekt, který dělá Open Build Service použitelnějším. Vedle toho existuje mnoho spojení mezi Bodegou a týmem openSUSE – a je na čase zjistit víc.
Mluvili jsme s Aaronem Seigem, prodiskutovali jsme Bodegu, Appstream, zypper, ymp a krásu svobodného software.

Co je Bodega
Nejdříve pojďme zjistit o čem celá Bodega je. Aaron vysvětluje:
„Bodega je obchod na digitální věcičky “ vytváří katalog metadat, který reprezentuje digitální přínosy.
Nejdůležitější věc je samozřejmě název „Digitální přínos“ což může být cokoliv. Například aplikace. Aplikace můžou být samo obsažné. Přemýšlejte jak android vytváří své APK soubory.
Pochopitelně v linuxu je to často komplikovanější.
Například Apache není zrovna ten příklad samoobsažné aplikace.
Obecně jsou tu manuály, knihy, muzika i obrázky.
Konkurenci tu také zmiňme třeba Apple nebo Google.

A co Linux
Linux nemá svůj obchod, kde byste mohli sehnat širokou škálu různých věcí. Můžete použít Appstream Apper nebo GNOME software centre.
Všechny disponují svými náhledy na aplikace, škoda jen, že jsou použitelné jen pro desktopy.
Ovládáte věci takovým způsobem, který není vyšší než levely Angry birds.
Pokud si přejete python mudol, jako vývojáři tyto zajímavé nástroje vám stejně nepomůžou.
Stejně tak nejsou použitelné pro servery.
Ti co spoléhají na nástroje v příkazové řádce, nebo vše dělají ručně. Je to vše uplně odlišné u různých distribucí.
Jdeme dále, kde můžete sehnat dokumentaci? Pro openSUSE je tu Activedoc, forum nebo naše databáze podpory na wiki support database on the wiki
Muziku seženete z Magnatune atd.
Nebylo by, ale hezké mít jedno místo, kde bych sehnal knihy, hry i aplikace? Tak to je právě Bodega.

V čem je Bodega jiná?
Bodega nabízí digitální obchod, který zvládá širší škálu věcí než naše současné řešení.
Ale co dělá Bodegu jinou a co jí odlišuje od proprietních technologií jako je Playstore nebo Conical Store?
Aaron:
většina Linuxových řešení jako Appstream předpokládá, že jejich uživatelé jsou uživatelé co hrají Angry Birds a používají tabulkové procesory. Dobře to je pochopitelné. Bodega má, ale jiný přístup a je mnohem ambicioznější.
Bodega má všechna meta data na jednom místě a dabízí obchody.
To znamená, že můžete mít například seznam jazyků a jejich addonů odděleně.
A oddělené UI pro angry-birds-a-tabulky.
Podívejme se na Appstream, Bodega samozřejmě benefituje z metadat nasbíraných pro Appstream.
A


face

This week I attended #pipelineconf, a new one-day continuous delivery conference in London.

I did a talk with Alex on how we do continuous delivery at Unruly, which seemed well received. The slides are online here

There were great discussions in the open space sessions, and ad-hoc in the hallways. Here’s a few points that came up in discussion that I thought were particularly interesting.

De-segregate different categories of tests

There are frameworks for writing automated acceptance tests, tools for automated security testing, frameworks and tools for performance testing, and tools for monitoring production systems.

We don’t really want to test these things in isolation. If there is a feature requested by a customer that we’re implementing, it probably has some non-functional requirements that also apply to it. We really want to test those along with the feature acceptance test.

i.e. for each acceptance test we could define speed and capacity requirements. We could also run http traffic from each test through tools such as ZAP that try common attack vectors.

Testing and monitoring shouldn’t be so distinct

We often think separately about what things we need to monitor in our production environment and what things we want to test as part of our delivery pipeline before releasing to production.

This often leads us to greatly under-monitor things in production. Therefore, we’re over-reliant on the checks in our pipeline preventing broken things reaching production. We also often fail to spot behaviour degradation in production completely.

Monitoring tools for production systems often focus on servers/nodes first, and services second.

We’d really like to just run our acceptance tests for both functional and non-functional requirements in production against our production systems in the same way that we do as part of our deployment.

This isn’t even particularly hard. An automated test from your application test suite can probably succeed, fail, or generate an unknown failure. These are exactly the states that tools like Nagios expect. You can simply get Nagios to execute your tests.

Monitoring your application behaviour in production also gives you the opportunity to remove tests from your deployment pipeline if it’s acceptable to the business for a feature to be broken/degraded in production for a certain amount of time. This can be a useful trade-off for tests that are inherently slow and not critically important.

Non-functional requirements aren’t

People often call requirements about resilience/robustness/security/performance “non-functional requirements” because they’re requirements that are not for features per se. However, they are still things our customers will want, and they are still things that a our stakeholders can prioritise against features – as long as we have done a good enough job of explaining the cost and risk of doing or not doing the work.

Technical people typically help with coming up with these requirements, but they should be prioritised along with our features.

There’s no point building the fastest, most secure system if no-one ever


Wednesday
09 April, 2014


face

Ça y est, une image d’openSUSE avec le bureau Plasma Next est dispo pour tester, merci à ierusalim.

Vous pouvez donc télécharger l’ISO ici grâce à SUSE Studio : https://susestudio.com/a/VU5ypu/kde-frameworks-5

Ensuite il vous suffit de la lancer sur un logiciel de virtualisation comme Virtualbox ( cf http://syvolc.briolet.fr/2010/11/15/virtualbox-jonglez-avec-vos-systemes-dexploitation/ )
ou bien de le lancer sur votre ordinateur à partir d’une clé USB, mais vu que c’est une version alpha très loin d’être stable je ne le conseille pas.

Voici quelques images :

Grub

KF5-capture01

Le menu de lancement des applications

KF5-capture02

L’élément graphique du calendrier et la configuration des effets graphiques

KF5-capture06

La configuration du fond d’écran

KF5-capture07

L’écran de connexion

KF5-capture08


face

I finally got around to update VDR to version 2.0.x
I’m using this version since some time and it is working fine for me. However, I’m quite sure that there are some kinks to be ironed out.
I’m not sure if updating from an old openSUSE VDR installation is a good idea or if it would be better to start from scratch. Personally, I’d do the latter and only keep my channels.conf.

The recommended way for starting VDR from systemd is now the runvdr-extreme-systemd package, the old runvdr init script is still available from the vdr-runvdr package, but is completely untested.

Configuration now happens in /etc/runvdr.conf, the old /etc/sysconfig/vdr is no longer read at all.

Normally, only the used plugins need to be added to runvdr.conf like

AddPlugin streamdev-server
AddPlugin epgsearch --logfile=/var/log/epgsearch/log --verbose=3
AddPlugin xineliboutput --local=none --remote=37890

This should be the equivalent of old sysconfig values

VDR_PLUGINS="streamdev-server epgsearch xineliboutput"
VDR_PLUGIN_ARGS_streamdev_server=""
VDR_PLUGIN_ARGS_epgsearch="--logfile=/var/log/epgsearch/log --verbose=3"
VDR_PLUGIN_ARGS_xineliboutput="--local=none --remote=37890"

The settings in runvdr.conf are commented, so the config file should be easy to understand.

If you are using vdradmin-am and are importing the old vdradmin.conf (I’d actually advise to start from scratch there, too) then you need to change the SVDR port setting to the new default of 6419 (or change the SVDRPORT variable for VDR to the old value).

The “supported” plugins are maintained in the “vdr” repository of the openSUSE Buildservice. I’m collection “unsupported” additional plugins in “vdr:plugins”. The definition of “supported” right now is “the stuff that I use”, simply because I cannot really test stuff that I don’t use on a daily basis. Of course if someone wants to help maintain these things, I’m more than willing to move things into the main “vdr” repository.
Stuff that is in the supported repository will most likely end up in Factory and thus in openSUSE 13.2.

Bugreports via bugzilla or the opensuse-factory mailinlist, please ;-)


Tuesday
08 April, 2014


face

Do you happen to find yourself in the situation that you have a program crash every now and then, but whenever this happens to you, you did not start the app in gdb?

Then I know that feeling; this guide will help you configure your test system to create a coredump whenever an app crashes, so if needed, you can use those at any later time to still create a backtrace. There are obviously some limitations, like stepping through and anything else funny you could do while debugging a running app. But it still does give you a good entry point.

NOTE: I do not advise to set this up on shared machines or critical machines. A coredump can contain sensitive data (memory extracts), which you would not want to be shared around.

With that cleared, it’s as simple as a few configuration steps:

Create any directory where you want to keep your coredumps. I use /cores
mkdir -m 777 /cores
This creates a world readable and writable directory

Configure your system to know WHERE to store the coredumps and how to name them. Create a file /etc/sysctl.d/99-coredump.conf, with the following content:
# I want to have core dumps in a world writable directory

kernel.core_pattern = /cores/%e-%t-%u.core
The pattern results in a filename /cores/NameOfBinary-TimeStamp-UserID.core; this helps yourself to identify the more recent crashes.

Modify the file /etc/security/limits.conf and add the line
* soft core unlimited
instructing the system to actually write coredumps for you.

Reboot your system and go ahead, make your apps crash. you will see files appear in /cores, if all is setup right.

You can at any time later start gdb with two parameters, first one pointing to the binary to debug, 2nd parameter to the corefile. Then normal gbd usage applies (if you miss debuginfo packages, you can even still install them at this time: the coredump remains valid). The usage of gdb goes beyond the scope of this article.


Monday
07 April, 2014


Chenthill P: C to C++ tour

10:37 UTC

face

I was requested during the beginning of this year to give a crash course on C++ for the developers with C background in our company. A while back, sankar gave an introduction to go language using http://tour.golang.org/ . Fascinated by the interface of gotour, I wanted to give the C to C++ tour using a similar interface but needed it in a quick time.

I discussed it with sankar and he came up with https://github.com/psankar/kuvalai/. He masters in pulling people to learning something new ;-) So I quickly learnt a bit of Go and contributed to kuvalai. It was taking a while to get it done, so we discussed and decided to hack up the go-tour. Made it to work with c++!!

Image

Readme.txt - explains howto apply the go tour patches and get it running.

All the programs and the article is now available at https://github.com/chenthillrulz/cpp-tour :-) I wanted to put this up on webserver so that it can benefit others, esp. beginners to c++ and students. But since I don’t have any webspace at the moment, thats going to take time ;-)

It was really challenging to construct simple, connected, practical examples for demonstrating the features. I wanted this tour to go simply like a movie. I did not know that I would enjoy so much doing this stuff :-) Got some happy, encouraging feedback from my peers after the training sessions. Perhaps I should thank my manager, Pradeep for persuading me to do this stuff. And my team, some of whom are still pushing me for the final session!!

Have conducted four sessions and the last one would cover advanced concepts such as traits, functors, template specialization, c++-11 features etc. The last session is taking time as I dont have practical experience on using traits, but still want to get some practical examples :-)  Working on it!!

The descriptions in the doc. many require some polishing. It has about 42 sections at this point. And as always patches are welcome!!!

writing a blog after quite some time, refreshing :-)



face

New release, time to run gource on master -> Evolution of the Open Build Service (gource) on Vimeo.


Sunday
06 April, 2014


face

C’est effervescence du coté de KDE, les versions de développement de différents projets nous en mettent plein la vue…. voici quelques news en vrac.

Première Alpha de Plasma Next

Le futur bureau KDE est nommé plus ou moins officiellement Pasma Next, ça correspond en fait à la version 2014.6 puisqu’il est prévu pour Juin de cette année.

calendar

La première version de développement, Alpha 1, vient de sortir. C’est donc un tout premier aperçu technologique à ne pas utiliser sur votre ordinateur principal. Ces paquets ne sont pas encore disponibles dans les dépôts instables d’openSUSE.

Vous pouvez en voir une petite démo ici :

Source : http://dot.kde.org/2014/04/02/kde-releases-alpha-version-next-gen-plasma-workspace

 

Première Beta du KDE Framework 5

Pour rappel, KDE Framework 5 est la plateforme de bibliothèques de programmation utilisée pour la future version de KDE, Plasma Next est donc basé dessus. La version de développement Bêta 1 vient de paraitre.

Source : http://www.kde.org/announcements/announce-frameworks5-beta1.php

 

La release candidate de KDE SC 4.13

Pendant ce temps là, la compilation de logiciels KDE 4.13 est arrivée en version Release Candidate et arrivera en version finale le mercredi 16 avril.

Cette évolution correspond principalement à des corrections de bugs, sauf pour Okular qui arrive avec des onglets et plusieurs nouvelles fonctionnalités et pour le moteur de recherche interne qui passe de Nepomuk à Baloo… voir chapitre suivant.

Source : http://www.kde.org/announcements/announce-4.13-rc.php

 

Milou, une petite interface pour Sprinter utilisant Baloo

Oui ok, on commence à avoir des noms ridicules… je ne sais pas si pour les anglophones ça sonne comme chez nous.

Je vous avez parlé de Baloo le nouveau moteur d’indexation qui va remplacer Nepomuk dès KDE 4.13.

Milou est un élément graphique (Plasmoid) qui permet d’exécuter rapidement une recherche sur le contenu indexé tel que les fichiers ou les emails. Un aperçu de ces fichiers est également disponible, par exemple on peut afficher une visionneur pour afficher un email.milou

Sprinter est lui le nouveau moteur de recherche. C’est la partie invisible qu’exploite Milou.

Sources :  http://vhanda.in/blog/2014/03/introducing-milou/ et http://aseigo.blogspot.fr/2014/03/krunner-sprinter-and-milou-sorting-it.html

 

Retour sur Pasma Next, des propositions de design

Alors que Plasma Next est en plein développement, une équipe de graphistes s’est réuni autour du site KDE Visual Design Groupe : http://wheeldesign.blogspot.fr/

De nombreuses propositions y sont faites pour moderniser l’apparence des éléments de Plasma Next comme les éléments graphiques (Plasmoids), les icônes ou les panneaux.

Voici quelques propositions qui seront peut-être retenues pour ce nouveau thème par défaut :

Le Plasmoid de l’horloge

clock_desktop

Les icônes de la boite à miniatures

abislHi

Les icônes des dossiers présentés dans Dolphin

icons

Source : http://wheeldesign.blogspot.fr/2014/03/monday-report-7-beach-edition.html?showComment=1395093061488

Tout


face

Corel released CorelDraw x7 on 27 March 2014. We had some time to look at the changes in file-format and we adapted libcdr to be able to open it. The changes landed this week in LibreOffice code, in master and libreoffice-4-2 branch. That means that support will be available in the next 4.2.x release.

It is good to note that while introspecting the files we discovered a flaw in CorelDraw x7 that makes files using the Pantone palette number 30 pretty unusable for CorelDraw users. We worked it around and the files are opening just fine in LibreOffice. Take this as a first contribution by the new Document Liberation Project.


face

Seit einiger Zeit bin ich ebenfalls, wie schon etliche vor mir, stolzer Besitzer einer Synology DiskStation. Bei mir werkelt ein eher kleineres Teil aus dieser Reihe, nämlich das DS 213j. Aber meine Begeisterung für diese, vereinfacht ausgedrückt Netzwerkfestplatte, kennt keine Grenzen.Ich will mich hier jetzt aber gar nicht zu Einzelheiten dieser DiskStation auslassen. Dafür gibt es etliche spezialisierte Seiten, Blogs und Foren, die das viel besser können.

Aber diese Netzwerk DiskStation hat auch einiges zu bieten, was gerade auch für Linuxer interessant ist. Da wären zum Beispiel, das man die ownCloud darauf betreiben kann und das man den Speicherplatz der Station per NFS und auch per WebDAVs in Linux einbinden kann. Und gerade letzteres finde ich sehr hilfreich, weil man so ( einige Voraussetzungen auf Synology DiskStation müssen erfüllt sein) mit einer verschlüsselte Verbindung übers Internet auf seinen heimatlichen Netzwerkspeicher zugreifen kann, wie auf einem lokalen Laufwerk. Und das ein mal eingerichtet und jederzeit verfügbar.

Was auf der Synology DiskStation für eine Verbindung per WebDAVs ( WebDAVs ist die verschlüsselte Variante von WebDAV ;-) ) konfiguriert sein muss werde ich hier auch nicht im einzelnen erläutern. Das ist recht einfach und die Benutzeroberfläche der DiskStation erklärt das sehr schön selbst und hilft durch alle Schritte die nötig sind, damit die Synology DiskStation auch von außen, vom Internet, erreichbar ist. Einschließlich Tipps für die Konfiguration des Routers.

Ich möchte hier nur den Part auf openSUSE Seite erklären, wie man den Speicherplatz der DiskStation per WebDAVs in KDE einbindet und so z.Bsp. über den Dateimanager Dolphin auf die Daten zugreifen kann.

Startet den KDE Dateimanager Dolphin und klickt links unter

Startet den KDE Dateimanager Dolphin und klickt links unter “Orte” auf “Netzwerk” und dann im rechten Fensterteil auf “Netzwerkordner hinzufügen”.

Daraufhin startet der Assistent für Netzwerkordner.

Daraufhin startet der Assistent für Netzwerkordner. WebDAV ist schon ausgewählt und das lassen wir auch so. Einfach auf “weiter” klicken.

Hier kommen die notwendigen Informationen rein, um eine Verbindung zum Server und zum persönlichen Account aufzubauen.

Hier kommen die notwendigen Informationen rein, um eine Verbindung zum Server und zum persönlichen Account aufzubauen.

webdav _002

Der “Name” der Verbindung ist frei wählbar. Spielt keine Rolle was da steht. ;-) Der “Benutzer” muss identisch mit einem existierenden Benutzer auf der Synology DiskStation sein. Auch die Schreibweise muss exakt übereinstimmen.

Um eine verschlüsselte Verbindung zu der DiskStation aufzubauen musste man bei den Vorbereitungen auf der Station ein eigenes SSL Zertifikat erstellen. Wenn man dieses Zertifikat nicht beglaubigen lässt ( ich glaube so heißt das ;-[ ) und im oberen Fenster letztendlich auf “Speichern & Verbinden” klickt, wird eben dieses Zertifikat vom System erst mal als unbekannt angemeckert. Die zwei Nachfragen, ob man dem Zertifikat trotzdem vertrauen will und dieses nur ein mal oder dauerhaft akzeptieren will kann man bei einem selbst erstellten Zertifikat ruhig tun. Danach wird die Verbindung zur DiskStation übers Internet erst hergestellt und es erfolgt die Passwortabfrage für den jeweiligen Benutzer.

Hier wird erst jetzt das Passwort für den Benutzer der Synology DiskStation abgefragt, dessen Speicherplatz hier ins System eingebunden werden soll.

Hier wird erst jetzt das Passwort für den Benutzer der Synology DiskStation abgefragt, dessen Speicherplatz hier ins System eingebunden werden soll


face

Hi there!

As you are reading this, I guess you have an interest in openSUSE and GNOME; and you are already fully aware of GNOME 3.12 being released. Also, you do not want to wait for the next version of openSUSE 13.2 to be made available (will anyway only be in November, presumably with GNOME 3.14).

So, how can YOU get GNOME 3.12 NOW on your openSUSE 13.1 system?
The answer is simple: there IS already a repository available, but it is ABSOLUTELY not meant for the one that could not potentially recover from a bad repository state.

The repository in question is called ‘home:dimstar:broken’
zypper ar obs://home:dimstar:broken/openSUSE_13.1 GNOME-3.12
zypper dup –from GNOME-3.12

BUT, as the name indicates, it CAN be broken. A group of people did test this repository already and we concluded it ‘working on our machines’; but then, we only have a handful of machines.

So, if you ARE interested in helping, testing and you are NOT afraid of having to revert from a potentially broken state, please feel free to add the repository, ‘DUP’ to it and enjoy.

Any breakage notices? Please tell us in #opensuse-gnome on irc.freenode.net; best to hant around there with us and engage; we might have a bunch of question which you would be the only one to answer.

So? What are you waiting for? GO GET IT!

If you’re not as brave to add a repository that has ‘broken’ in the name (the name is intentional, for exactly that reason), then please stay tuned; depending on the feedbacks we receive, the repository will be fixed up and once considered stable be moved into the GNOME:STABLE namespace; at which time you can safely get it as well.

Cheers! Happy testing.


Friday
04 April, 2014


face
If your running openSUSE 13.1 and you use Webex on a regular basis for home/work/other you have probably noticed that it does not execute properly and you can't get some of the features to work on it. Well look no further. Thanks to my colleague dvosburg you can run the below command on your openSUSE 13.1 and it will install the necessary packages and its dependencies that are required for a good Webex experience.

zypper in libpango-1_0-0-32bit \
libpangomm-1_4-1-32bit \
libpangox-1_0-0-32bit \
libgtk-2_0-0-32bit \
libgtk-3-0-32bit \
libglib-2_0-0-32bit \
libXau6-32bit \
libXmu6-32bit \
libxcb1-32bit_64 \
libXext6-32bit 


Enjoy!

face

If your running VMware Workstation 9 and above and you use both existing and new VMs you can possibly get a return of "Unable to change virtual machine power state: Cannot find a valid peer process to connect to" error.

This does not happen with everyone, but the problem seems to come from the Nvidia drivers. At least as far as I can tell thus far. I have not been able to debug further because this problem is not happening to me. If you have this problem and your running the Nvidia 331.20 drivers then you will want to do the following.


1) Download the Nvidia 325.15 driver from here http://www.nvidia.com/object/linux-display-amd64-325.15-driver.html


Create a custom patched Nvidia driver.


2) Download the patch below for the latest kernel in openSUSE 13.1 which is 3.11+

http://cvs.rpmfusion.org/viewvc/*checkout*/rpms/nvidia-kmod/devel/kernel_v3.11.patch?revision=1.1&root=nonfree

save as kernel_v3.11.patch


3) Execute the following to create the custom patched Nvidia installer.

# sh NVIDIA-Linux-x86_64-325.15.run --apply-patch kernel_v3.11.patch
4) You will get a file output NVIDIA-Linux-x86_64-325.15-custom.run
5) You can now install this custom Nvidia driver which should fix your VMware Workstation problem.

Enjoy!

face

Download this patch

Then follow these steps from a terminal as root user

# cd /usr/lib/vmware/modules/source/
# cp vmnet.tar vmnet.tar.original
# tar xvf vmnet.tar vmnet-only/filter.c
# patch vmnet-only/filter.c < /location_of_filter.c.diff/kernel-3.14-vmware-filter.c.diff
# tar -uvf vmnet.tar vmnet-only/filter.c
# rm -rf vmnet-only/
# vmware-modconfig --console --install-all 
 Enjoy!

face

Run the following.

Download this kernel patch

Download the NVIDIA driver version NVIDIA-Linux-x86_64-331.49.bin

from root execute:
   # sh NVIDIA-Linux-x86_64-331.49.bin --apply-patch kernel-3.14-nvidia.patch

Now install the custom NVIDIA Driver.
Enjoy!


face

So if your struggling to get the full functionality out of Blackboard Collaborate. Usually your unable to get the Application Sharing to work properly, but there might be other reasons. Here are a few scripts that I have created that will allow Blackboard to run properly either with Oracle Sun Java 1.7 or with openJDK Java.

For openJDK Java 64bit:

1) Download this script
2) Copy the script prepare-openjdk-blackboard.sh to your system anywhere you prefer locally
3) Login as root
4) execute from your locally preferred location.
     # ./prepare-openjdk-blackboard.sh
5) Open Firefox and launch Blackboard Collaborate from the Guest or Chair Link and Select the webstart that shows up automatically. Enjoy Blackboard Collaborate on openJDK 64bit Java.

For Oracle SUN Java 64bit (Supported):

1) Download this script
2) Copy the script prepare-oracle-java-blackboard.sh to your system anywhere you prefer locally
3) Login as root
4) execute from your locally preferred location.
     # ./prepare-oracle-java-blackboard.sh
5) Open Firefox, and select Preferences. Applications. In the search box, type 'jnlp' In the drop down under Action, choose 'Use Other', and browse to /opt/java/64/jre1.7.0_51/bin/javaws
6) Launch Blackboard Collaborate from the Guest or Chair Link. Enjoy Blackboard Collaborate on 64bit Oracle SUN Java.

Enjoy!


face

Ingredients:

  1. one Linux box with multiple Ethernet interfaces
  2. at least two networks with segments assigned
  3. a desire to make the Linux box route packets between the networks

Read more »

face

Joining the OpenStack blogosphere. I will soon have some posts around SUSE Cloud. Stay tuned.
-C


face

Dear KDE Users,

Maybe you have heard already about it from another openSUSE mailing list, a blog post or through our openSUSE community page on Google+, but the KDE repositories have been changed since last Tuesday. Below you will find the changes that were done based on the release of KDE 4.12.4.

Why was this changes needed

Based on a small discussion in the opensuse-kde mailinglist and feedback on our survey, we concluded that the majority is in favor of creating a single repository where we track the current KDE release.

Where are my old KDE repositories

The name for this repository will be KDE:Current and will initially be build for oS 12.3 and oS 13.1.

After the release of the KDE:Current repo, the repositories KDE:Release:XY have been cleaned and removed. Initially KDE:Current will be delivered with 4.12.4 as that the KDE 4.13 release is scheduled for mid April.

Also the repository KDE:Extra and KDE:Unstable:Extra will change as that some of the building targets (KDE:Release:XY) are disappearing and be replaced with KDE:Current.

Where should I find the new KDE repositories

The KDE Repository page KDE repositories has been updated to reflect the changes. We would like to ask those that have been working on the localization of this page in other languages, to
update their pages as well.

Regards,

Raymond


face

Bad news for the bugs: the new version of openQA is ready for prime time. Everybody following the blog of the openSUSE Team @ SUSE or the Factory mailing list during the last months, should be aware of the ongoing work to improve openQA and to promote it into a key component of the openSUSE integration process. Finally the new openQA is ready for public production environments, so thanks to the collaboration between the openSUSE Team and the original developers of openQA -Bernhard M. Wiedemann and Dominik Heidler- it’s finally deployed and accessible at openqa.opensuse.org

This new version brings a lot of changes at many levels, but probably the most relevant difference is the approach for tests execution: instead of running every step sequentially and comparing the needles at the end, the new version evaluates the status several times per test, deciding what to do next based on that status or aborting the whole tests as soon as a critical error is found. This approach enables both a better usage of the resources and more precise results.

This enhanced control of the execution and the results, alongside other improvements, makes possible to extend the scope of openQA. Tests of Factory isos are still there and running. But apart from them, you can see test results for the so called "staging projects", used to merge potentially dangerous packages. Generally speaking, you can just browse the test results and see what state is Factory in and how dramatic changes are about to happen.

Fuzzy matching in action: ignoring the floppy icon

Another main new feature is the use of fuzzy area matching for interpreting test results. That means much less false positives. Tests do not break that often and that easily. There is also a nice interface to figure out what failed. Try going to some failed test, selecting a needle and dragging the vertical yellow line. Pretty neat, isn’t it? You can also check how the test is written and what is it looking for. Feel free to play with it, enhance the current tests and needles and submit them via GitHub ;-)

There are even more changes, not directed towards users, but improvements in the interface that service operators use to set things up, including users management, job control or a new REST-like API. These will not affect most of you directly, just indirectly by making operators job easier.

So go ahead, play with it and if you want to help, sources are on github and we even have some easy hacks in progress.o.o to ease you into the development ;-)


Thursday
03 April, 2014


face

MariaDB logoI was browsing around the Internet (don’t remember what for) and I accidentally found one cool aspect of MariaDB. There is a feedback plugin and this short post is meant to encourage you to use it!

Ok, so what it does and why should you opt-in to be spied on :-) It takes some information about your MariaDB server including it’s usage and it will send it to the MariaDB folks. It doesn’t send private data from your database. It sends stuff like what OS are you running, what version of various plugins, how did you tweaked the default settings and also how big and how busy is your server. Now a short list of why I turned this on:

  • Why not? Doesn’t cost me anything, nothing from the data I send is secret.
  • When I develop an application, I’m always happy when somebody uses it. This is an easy way how to tell developers, that they have here one happy user :-)
  • Easy way to contribute. It’s really simple to turn it on, it will help MariaDB folks make better database and doesn’t require much effort from my side.
  • Selfish reason – if they see that plenty of people use MariaDB the same way I do, they will focus more on my use case :-)

But all these data are not only available to them, they are also making some nice graphs out of it. That way, I can find out that there is at least another 27 guys running latest 10.0.10. Also I found out that there is not many reports from openSUSE folks. And that is one of the reasons to write this blog. If you are running MariaDB on openSUSE, please turn feedback plugin on to show that we have plenty of people using MariaDB :-)

How can you turn it on? Simple, login to your database and activate the plugin using following command:

INSTALL PLUGIN feedback SONAME 'feedback';

Now just wait till your reports will show up in statistics. If I got you interested, you can read more about the plugin on MariDB website (it can report to any url, not only MariaDB one, you can use it for monitoring). While waiting, browsing already collected statistics is also interesting ;-)


face

Welcome to the Bodega store!

Bodega is a project making use of the Open Build Service. Aside from that, there are many other connections between the Bodega team and openSUSE – time to find out more! We spoke with Aaron Seigo, and discussed Bodega, Appstream, zypper, ymp and the beauty of Free Software.

What is Bodega?

First off, let’s find out what Bodega is all about. Aaron explains:

Bodega is a store for digital stuff. In fancy words: it creates a catalog of metadata which represents digital assets.

The most important thing is of course the ‘digital asset’ term. That can be anything. For example, applications. Applications can be self contained – think how android does its APK files. Of course, things on Linux are often more complicated. Apache isn’t exactly a self-contained thing. And look further – perl, php, ruby, they all have their own addons like gems that need managing. Generalizing further, there are manuals. And books in general. Music, movies, pictures, you can go on.


Setting up a Bodega account

Of course, the competition has these too – look at Apple or Google.

And how about Linux…

Linux does not have a store where you can get such a wide variety of things. For a game, you can use Appstream, get it from Apper or GNOME’s software center. They all give a view on applications. Unfortunately, that is only useful for desktops and can handle things barely above the level of Angry Birds. If you want a python module as developers – these fancy tools won’t help you. Nor are they useful on servers. For those you have to rely on command line tools or even do things completely by hand. And it is all different between distributions.

Going further, where do you get documentation? For openSUSE, that’s activedoc or the forums or our support database on the wiki. Not from zypper. Music – you can get that from Magnatune and so on.

What if you can have one place where you can get a book, game, applications, isn’t that nice? That is what Bodega is.


The main screen of the store

How is Bodega different?

So, Bodega offers a digital store which can handle a wider variety of things than our current solutions. But what sets it apart from proprietary technologies like the Playstore and of course Canonical’s store solution? Aaron:

Most Linux solutions like Appstream assume their audience are users who play Angry Birds and use spreadsheets. Fair enough. Bodega takes a different approach and is far more ambitious.

Bodega has all the meta data in one place and offers ‘stores’ which are views on that data. That means you can have a software developer store, for example listing all languages and their addons separate; and a server section etc. And a separate UI for the angry-bird-and-spreadsheet crowd. All from the same bodega system, filtered by tags (not static categories!).

Talking about Appstream, Bodega can of course benefit from the metadata gathered for Appstream


Wednesday
02 April, 2014


face

Y bien, tenemos a las puertas uno de los eventos más maravillosos y singulares que podemos observar desde la superficie de la Tierra. Me refiero a un eclipse total de Luna.Este evento dará inicio (para Nicaragua y Centroamérica) en la noche del 14 de Abril y concluirá en la madrugada del 15 de Abril. En […]


face

Since last time I had kernel source code repository and initramfs used in stock kernel and I thought that the way to boot will be easy. Unfortunatelly there are several facts I needed to accept and tasks I needed to do. This will give you idea what have I done in the meantime:

  • to be able to flash or boot kernel I needed to unlock bootloader - Sony is respectable that it offers way to unlock your bootloader (with loosing or reducing warranty though)
    • if you want to be able to re-lock your bootloader, you need to backup your TA partition, before unlocking (you'll need root for that)
    • unlocking doesn't work well before latest Sony update (you'll loose some functionality when unlocking on 4.1)
      • updating to lastest Sony firmware will remove your root access

At the end of this saga, I was running Sony's Android 4.3 with root access and I could start playing with fastboot's boot command. After plethora of unsuccessful attempts I get to know that it is crippled in Sony's bootloader and won't work - that was dead end for me. Flashing kernel using fastboot protocol worked but my experimental kernel didn't boot. Furthermore experimenting with kernel builds and flashing each of them would kill my flash memory very soon.

I left Sony's stock firmware and installed Cyanogenmod 10.2 which works quite nice. I was able to build identical kernel by myself and could play further. I tried to enable kexec() support in kernel but as you probably expect, it didn't started the kernel correctly so this was also dead end for now.

People from FreeXperia community gave a lot of useful information about almost everything (i.e. proper location of boot kernel and meaning of other partition) and told me also about Little Kernel bootloader. Lilstevie even made port to Xperia Tablet Z already.

I need to have device initialized during boot before loading kernel and that is the job for Sony's bootloader. In LK bootloader scenario Sony's bootloader loads Little Kernel instead of Linux Kernel so Little Kernel doesn't have to care about HW initialization and can only load and run kernel. FreeXperia community used this method to have two separated images with kernels and initial ramdisk instead of one kernel+initrd which can behave both as normal boot or recovery. In this setup you don't have to worry about flashing wrong kernel anymore as it will be fixable even without computer access.

LK was already prepared so I could only grab binaries and flash it, with some minor differences - I used actual version of TeamWin recovery project, and Cyangenmod's boot.img. It worked nicely but only after applying this kernel patch I could use `adb reboot recovery' to get to recovery. Besides Little Kernel usefulness it has also one nice feature - it supports fastboot protocol as well and


Tomáš Čech: Xperia, FOTA format

00:11 UTCmember

face

Long time no see. I got new Sony Xperia Z Tablet (WiFi, not LTE one) to play with and I thought that it would be nice device to run our openSUSE with my Enlightenment on that to combine cool hardware and cool software.

It seems that there is not much project targeted on running full blown Linux distribution on Android devices. You can meet Replicant (which is great anyway), you can meet Ubuntu Touch but that is almost all. So I decided to revive my old blog and write here my notes.

I played in past with HTC Desire Z with the same desire, but as I had very little time in the end, I didn't progressed significantly beyond interesting Hackweek project. I hope that this time it will do better and at least it is not my only mobile I'd wreck :)

I started with rooting the device, which was very simple thanks to the article on unlockr and the work of DooMLoRD. I prepared then openSUSE chroot on microSD card, automated chrooting process and installed some basic tools (gcc, git, mosh + ssh) and E17. To see I have working installation I used Android's native XWindow implementation.

To boot openSUSE I'd need to boot kernel with something like

root=/dev/block/mmcblk1p4
(where my openSUSE partition is) or even provide my initramfs which will take care of mounting and other needed stuff. To be able to boot without bricking I need to find way how to provide kernel to bootloader without changing contents of flash.
fastboot
should do the job (at least it did with my HTC Desire Z attempts).

It seems that I can't influence kernel parameters for now so let's build own kernel with root device settings hardcoded. Sony provides repository with kernel source on github. Kernel configuration was not present so I took the one from Cyanogenmod project.

Let's have a look on internal flash to find some more information:


# fdisk -l /dev/block/mmcblk0
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.

Disk /dev/block/mmcblk0: 15.8 GB, 15758000128 bytes, 30777344 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt


# Start End Size Type Name
1 256 4351 2M unknown TA
2 4352 4607 128K unknown sbl1
3 4608 5119 256K unknown sbl2
4 5120 5631 256K unknown s1sbl2
5 5632 6655 512K unknown sbl3
6 6656 7679 512K unknown aboot
7 7680 8703 512K unknown tz
8 8704 8959 128K unknown alt_sbl1
9 8960 9471 256K unknown alt_sbl2
10 9472 9983 256K unknown alt_s1sbl2
11 9984 11007 512K unknown alt_sbl3
12 11008 12031 512K unknown alt_aboot
13 12032 13055 512K unknown alt_tz
14 13056 14079 512K unknown rpm
15 14080 15103 512K unknown alt_rpm
16 16384 49151 16M Linux filesyste LTALabel
17 49152 90111 20M unknown boot


Tuesday
01 April, 2014


face

I’m pleased to announce a new 1.22.0 package of calibre for openSUSE. Whats happend in this version?

New features

  • A new tool to compare ebook files, showing the differences in their underlying text, styles and images side by side
  • Edit book: Add a tool to view the list of checkpoints and compare the current state of the book to the state at the specified checkpoint. To use it click View->Checkpoints
  • Edit book: Add a tool to compare the book being currently edited with another file. To use it go to File->Compare to other book
  • Allow comparing the ORIGINAL_EPUB version of a book to the EPUB version by right clicking on the ORIGINAL_EPUB format in the book details panel. And the same for ORIGINAL_AZW3 and AZW3 formats.
  • Edit Book: Add a button to show the changes after various automated tools are run such as: remove unused CSS, subset embedded fonts, smarten punctuation, etc.
  • Edit Book: Add check for spine items with incorrect media-type specified in the manifest
  • Edit Book: Enable editing of page map XML files
  • DOCX Input: Improve handling of text boxes. Text boxes are still not supported, but they no longer cause errors or duplicate content when embedded inside paragraphs.
  • Edit Book: Add check for links that point to directories in the book instead of files.
  • Edit Book: Show the filename of the currently edited file in the title bar.

Bug fixes

  • Edit Book: Fix unused CSS removal tool inserting namespace declaration at the top of the stylesheet
  • Edit book: Fix cover not being updated from the current cover in the calibre library when using Edit Book. Note that you can turn off metadata updating via Preferences->calibre Integration in the Edit Book Preferences.

Downloading

You can find the latest version in the Documentation:Tools Repository. As example for openSUSE 13.1: http://download.opensuse.org/repositories/Documentation:/Tools/openSUSE_13.1/ .

Bugreports

You can send Bugreports for the calibre package to the Novell Bugzilla

Donations

Donations for the packager are everytime welcome. Just click on: Donate


face

I’m pleased to announce a new 1.21.0 package of calibre for openSUSE. Whats happend in this version?

New features

  • Edit book: Add a tool to automatically remove all unused CSS rules. Useful for books created from templates that can have large numbers of CSS rules that dont match any actual content. Available via Tools->Remove unused CSS.
  • Edit book: Add a tool to split HTML files at multiple locations automatically. To use it, right click in the file and choose ‘Split at multiple locations’. Useful if you want to split at all heading tags or all tags having a certain class and so on.
  • Book polishing: Add an option to automatically remove all unused CSS rules, works the same as the tool for Edit book, above.
  • Driver for ImCoSys imcoV6L
  • Edit book: Allow editing of .plist files as XML

Bug fixes

  • Metadata download: Fix downloading of metadata from Edelweiss not working because of website changes
  • Ebook viewer: Do not override the background color specified in the book if the user has not set a background color in the viewer preferences
  • Edit book: Handle EPUB files that erroneously list the OPF itself in the OPF manifest with an incorrect mime type
  • Edit book: Prevent arrange into folders tool from moving files inside the META-INF folder

Downloading

You can find the latest version in the Documentation:Tools Repository. As example for openSUSE 13.1: http://download.opensuse.org/repositories/Documentation:/Tools/openSUSE_13.1/ .

Bugreports

You can send Bugreports for the calibre package to the Novell Bugzilla

Donations

Donations for the packager are everytime welcome. Just click on: Donate


face

I’m pleased to announce a new 1.20.0 package of calibre for openSUSE. Whats happend in this version?

New features

  • Edit book: Add a new tool to automatically arrange all files in the book into folders based on their type. Access it via Tools->Arrange into folders.
  • Edit book: Add various validity checks for OPF files when running the Check Book tool.
  • Edit book: Add checks for duplicate ids in HTML/OPF/NCX files
  • Edit book: Add checks for filenames containing URL unsafe characters to the Check Book tool
  • Conversion: Allow getting text for entries in the Table of Contents from tag attributes.

Bug fixes

  • AZW3 Output: When converting EPUB files that include an HTML titlepage and no external cover is specified, ensure that the Go to cover action on the Kindle goes to the cover image and not the HTML titlepage.
  • Prevent setting an incorrect value for compression quality in the wireless driver causing an error
  • Show a busy cursor while calibre is working on matching books on the device to books in the library, which can take a while if the user has a lot of books on the device.
  • iTunes driver: Retry automatically a few times when failing to send multiple book to iTunes.
  • HTML Input: Fix UTF-16/32 encoded files that are linked to from the parent file not being properly processed.
  • EPUB Output: Fix splitting of large HTML files removing all child tags from inside tags.
  • Edit book: Fix tab characters not being identified in the lower right corner.

Downloading

You can find the latest version in the Documentation:Tools Repository. As example for openSUSE 13.1: http://download.opensuse.org/repositories/Documentation:/Tools/openSUSE_13.1/ .

Bugreports

You can send Bugreports for the calibre package to the Novell Bugzilla

Donations

Donations for the packager are everytime welcome. Just click on: Donate

<- Current blog entries