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.

Saturday
28 January, 2012

Baltasar Ortega: Cómo instalar KDE 4.8 en Fedora 16

@ 15:43 UTCmember

Sigo con la serie de cómo instalar KDE 4.8 en diversas distribuciones. En esta ocasión toca otra de las conocidas: Fedora.

Para ello tenemos la explicación de Fedorigen, la cual copio y pego

Para poder tener esta versión tendremos que agregar los repositorios kde-redhat a nuestro equipo lo haremos de la siguiente forma:

yum -y install wget && wget http://apt.kde-redhat.org/apt/kde-redhat/fedora/kde.repo -O /etc/yum.repos.d/kde.repo

ahora procedemos a editar nuestro archivo para activar los repositorios inestable

nano /etc/yum.repos.d/kde.repo

donde dice enable=0 lo cambiamos por enable=1

con esto procedemos a actualizar el sistema

yum update

Como no soy especialista de esta distribución, si teéis dudas os remito a dos blogs donde también han publicado esta mini guía e incluso han puesto sus propios comentarios y explicaciones: Gabuntu y Espacio Linux.

Bien seguro os pueden ayudar.

Stefan Seyfried: Using IRMP with Arduino

@ 12:10 UTCmember

I needed to implement an infrared remote control decoder, so certainly I took out my Arduino and hooked up an IR sensor chip to pin 2. Then the interesting thing started. Looking around, I found ladyada’s tutorial on IR sensors. However, the method used there is pretty limited (you basically record a sample of each key signal and then compare the received signal to your samples) and unreliable for many protocols.
Then I found IRMP (german only link, sorry) which is a very versatile IR decoder for many protocols. However, IRMP is made to be used with plain avr-gcc, not from within Arduino’s IDE.
But fixing that was really not very hard.
The results are available on gitorious, project arduino-addons/irmp-arduino, including a simple example sketch to test the decoder.

Note that I’ll probably rebase the git tree whenever something happens in the IRMP SVN repository, so be aware of that in case you make local changes to the code and want to update from my tree.

Have fun!

Masim Vavai Sugianto: Amanda: Program Backup untuk Linux, Windows, Unix dan OS X (3)

@ 07:33 UTCmember

Melanjutkan tulisan saya tentang Amanda di episode 1 dan episode 2, kayak film aja , kali ini saya tuliskan episode penutup dari keseluruhan cerita tentang siapa sebetulnya Amanda. Wah jadi trilogy nih
Namun jangan khawatir, tulisan lain tentang Amanda masih akan menghiasi tulisan-tulisan saya.

Apa kebutuhan sistem buat Amanda?
Amanda membutuhkan sebuah komputer yang dapat mengakses disk (local, NAS, atau SAN) atau tape drive atau library dengan kapasitas besar.
Mendukung semua format tape modern seperti LTO,EXABITE, DAT, atau DLT. Komputer ini nantinya akan menjadi “backup server host”. Semua komputer yang akan anda backup dinamakan “backup client host”. Server tadi juga bisa menjadi client host.

Amanda bisa berjalan lancar dengan satu atau lebih partisi besar “holding disk” di server host yang digunakan untuk buffering data-data dump sebelum ditulis ke tape. Hoding disk memudahkan Amanda menjalankan backup secara paralel ke disk, dan akan ditulis ke tape jika backup sudah selesai.
Catatan: holding disk tidak begitu dibutuhkan, tanpanya Amanda akan tetap menjalankan backup secara berurutan ke tape drive, namun menjalankan Amanda tanpa holding disk tidak akan mendapatkan performa yang optimal tetapi masih bisa mendapatkan keuntungan dari fitur-fitur Amanda yang lain.

Gampangnya begini, untuk performance terbaik holding disk harus lebih besar kapasitasnya dibanding hasil dump data-data dari partisi yang mau dibackup. Contohnya, jika anda ingin membackup partisi dengan ukuran 1 terabyte yang hasilnya dikompresi sampai 500 GB, berarti anda memerlukan sedikitnya 500 GB di holding disk. Dengan kata lain jika partisi terbesar di komputer yang akan dibackup adalah 50GB dan akan dikompresi sampai 25GB, berarti anda membutuhkan 25GB di holding disk. Namun Amanda akan bekerja lebih baik dengan holding disk yang lebih besar.

Sejatinya, proses backup akan tetap jalan jika data-data dump tersebut melebihi kapasitas holding disk, Amanda akan mengirim data dump tsb langsung ke tape drive. Jika anda punya banyak data dump yang melebihi holding disk-nya maka akan menurunkan kecepatan dari mesin yang memproses backup tsb.

Sistem apa saja yang cocok untuk Amanda?
Amanda bisa jalan di sistem Unix modern yang mensupport dump atau GNUtar, punya sockets dan inetd (atau penggantinya seperti xinetd), dan mempunyai salah satu fitur ini, system V shared memory atau mengimplementasikan BSD mmap.

Secara khusus, Amanda telah di-kompile dan ditest di sisi client di sistem-sistem berikut:

AIX 3.2 and 4.1
BSDI BSD/OS 2.1 and 3.1
DEC OSF/1 3.2 and 4.0
FreeBSD 6, 7 and 8
GNU/Linux 2.6 on x86, m68k, alpha, sparc, arm and powerpc
HP-UX 9.x and 10.x (x >= 01)
IRIX 6.5.2 and up
NetBSD 1.0
Nextstep 3 (*)
OpenBSD 2.5 x86, sparc, etc (ports available)
Solaris 10
Ultrix 4.2
Mac OS X 10
Windows: XP Pro (Server pack 2), 2003 server, Vista, 2008 server R2, Windows 7 (*)

(*) Amanda server dapat berjalan di semua mesin-mesin tsb kecuali yang ditandai bintang.

Operasi backup menggunakan CPU dan memori secara intensif (misal untuk operasi enkripsi dan kompresi). Sangat disarankan anda menggunakan CPU sekelas server pada server backup.

Dimana bisa mendapatkan Amanda?
Amanda, termasuk source code-nya …

Sebastian Siebert: openSUSE – Adobe Flash Player 11.2 Beta 4 installieren

@ 20:00 UTCmember

Am 19.01.2012 hat Adobe im Adobe-Labs die 4. Beta-Version (11.2.202.183) des Flash Players für 32-bit wie auch 64-bit Systeme veröffentlicht.

Laut der Release Notes sind folgende Feature enthalten:

Throttling event (new ThrottleEvent)
Einige Bugfixes (laut dem Bugtracker von Adobe)

Wer noch einen Fehler oder Ungereimtheiten in der aktuellen Beta des Flash Player gefunden hat, so möchte ich den Bugtracker von Adobe empfehlen.

Die Installation des neuesten Flash Player auf openSUSE:

Hinweis: Die Installation wird in der Konsole mit root-Rechten durchgeführt. Hierzu wird der Flash Player und das zugehörige Packaging Skript heruntergeladen. Daraus wird ein RPM-Paket gebaut und auf Wunsch installiert.

Downloads:

Das Skript makerpm-flash-11.2-beta4.sh wie auch die Prüfsummendatei herunterladen:

wget http://www.sebastian-siebert.de/downloads/makerpm-flash-11.2-beta4.sh

wget http://www.sebastian-siebert.de/downloads/makerpm-flash-11.2-beta4.sh.sha1

Die Prüfsumme vom heruntergeladenen Skript prüfen:
```
sha1sum -c makerpm-flash-11.2-beta4.sh.sha1
```
Idealerweise sollte folgende Ausgabe erscheinen, andernfalls ist das Skript defekt und sollte ersetzt werden:
```
makerpm-flash-11.2-beta4.sh: OK
```
Das Skript ausführbar machen:
```
chmod 755 makerpm-flash-11.2-beta4.sh
```
Nun gibt es 3 Möglichkeiten die Pakete zu erstellen und zu installieren:
1. Auf einem reinen KDE-System:
```
./makerpm-flash-11.2-beta4.sh -i kde
```
2. Auf einem reinen GNOME- bzw. GTK-System:
```
./makerpm-flash-11.2-beta4.sh -i gnome
```
3. Sowohl auf einem KDE-System wie auch auf einem GNOME-System:
```
./makerpm-flash-11.2-beta4.sh -i all
```
  oder einfach nur
```
./makerpm-flash-11.2-beta4.sh -i
```
Dann entspannt zurück lehnen und warten bis die Installation abgeschlossen ist. Das Skript ist wie gewohnt gesprächig und die jeweilige Aktion kann verfolgt werden.
Rechner neustarten und Flash Player 11.2 Beta 4 testen.

Feedbacks sind immer willkommen.

Have a lot of fun!

Bruno Friedmann: ATI/AMD fglrx 8.930 Catalyst 12.1 rpm available for openSUSE 11.3, 11.4, 12.1

@ 16:35 UTCmember

AMD/ATI Catalyst 12.1 / fglrx 8.930 rpm are available

Sorry I missed in December the annoucement release for the 8.920, but from what I’ve seen. zypper up do the job for you

Quick Résumé about 12.1

AMD rename their installer, So Sebastian did the same for his script.

I will just copy/google translate/paste here the comment made by Sebastian Siebert on his blog :

With this version AMD Catalyst Gnome 3.2 issues (flickering and screen cracks) are finally resolved.
According to AMD, the notebook with the PowerXpress technology (Intel-/AMD-Grafikkarte – discrete GPU) should work again.
I would be grateful if someone could test this functionality for me and give me feedback. Thank you.

See more at Sebastian’s blog. Don’t be shy, you can leave there the result of test in english too
See below what to do in case of troubles.

The rpms version 8.930 are available from Friday January 27th

My advise is to firstly remove any existing version with zypper rm, then just zypper in the new version, even if 8.930 are the first version I’ve seen making its upgrade correctly.

As usual, I let the last 2 previous versions in the repository, just in case you need it.

Catalyst 8.930 fglrx 12.1 in action

Tested on a fresh 12.1 + updates with a stock kde 4.7.2

Factory rpms are not available actually, I’ve not be able to build a new building machine for it.
Anyways, factory and 12.2 should keep their effort on debuging and testing widely the free radeon driver.

One-click-installer

As nobody killed me about the one click installer available, I upgrade its status to RC (feedback welcome)
For 32bits system :

For 64bits system :

(*) To know which kind of system you have, open a console, then run uname -a, and look the output if you see x86_64 on the line you are running a 64bits, otherwise a 32bits.

Installation, Caution, Troubles

Installation

Please refer to my previous article where all the installation procedure are explained.

For a first installation, if you don’t remove radeon from the initrd, you will get in trouble. Don’t thanks who removed that from the wiki.

Caution

Wrong (to my point of view) create an xorg.conf file which is unneeded if you work with /etc/xorg.conf.d/50-device.conf and have driver “fglrx” inside
AMD CCLE didn’t get correctly upgraded if xorg is running during the upgrade. My advise, let’s go to console and as root do the following :
```
init 3
rcatievenstd stop
zypper ref
zypper up
init 6
```
Let the package rebuild the kernel driver. And for me I always remove the newly xorg.conf file created.
reboot is mandatory!

Debuging troubles

I recommend in case of trouble the use of his script which can collect the whole informations needed to help you. then you just have to issue a simple commande in console to …

@ 15:10 UTCmember

El tema principal de hoy son la ley SOPA, ACTA y el sonado caso de Megaupload. Además de los problemas con aplicaciones Android Legitimas, y el caso de los SMS espías.

Securnoia, tu dosis seguridad y paranoia.

Baltasar Ortega: Cómo instalar KDE 4.8 en KUbuntu

@ 14:54 UTCmember

Ayer hablé de openSUSE y sus repositorios para KDE 4.8, hoy de KUbuntu que también disponde de los suyos. Como se ve, las grandes distribuciones no se duermen.
Los chicos/as de KUbuntu apenas tardaron un par de horas tras el lanazmiento de KDE 4.8 para tener todos los paquetes listos para tener al día la versión de KDE.
Para ello debes añadir el repositorio (si aún no lo tienes):

ppa:kubuntu-ppa/backports

Luego ejecutar en Konsole:

sudo apt-get dist-upgrade

Esto actualizará los paquetes obsoletos: kdepim-groupware, kdepim-wizards y kdepim-kresources.

Vía: Espacio KDE

Alexandre Marcolino: Baixe já a sua Linux Magazine Community Edition 86!

@ 12:11 UTC

Baixe já sua Linux Magazine 86 Community Edition! Já está no ar a Linux Magazine 86 Community Edition.Confira nesta edição os principais assuntos da Linux Magazine de janeiro (Ciberguerra) e leia um artigo completo sobre o Lazarus, ambiente de desenvolvimento para o Free Pascal compatívelcom diversas plataformas, e que permite aos desenvolvedores criar interfacesgráficas com [...]

Baltasar Ortega: Primeras impresiones con KDE 4.8 (I)

@ 08:53 UTCmember

Ya estoy probando KDE 4.8 en un portátil con openSUSE, se instala tal y como explico en esta entrada, y estoy viviendo en primera persona sus mejoras. Así que iré escribiendo aquellas cositas que hace que a KDE 4.8 el mejor escritorio de todos los tiempos:

A nivel general, el portátil va mucho más fluido, el escritorio se desliza con extraordinaria suavidad.

A la hora de añadir nuevos plasmoides, por fin el foco del cursor está en el cuadro de búsquedas.

Añadidas opciones para configurar la transición entre ventanas.

Además, éstas funcionan mejor. Por ejemplo, en el modo presentación, la ventana seleccionada aumenta de tamaño con un suave zoom.

La gestión de energía ha mejorado sustancialmente. El portátil con KDE aguanta mucho más tiempo.

Han desaparecido los problemas de bloqueo cuando el portátil entraba en modo de hibernación.

Seguramente habrá muchos más detalles, pero todavía no he investigado a fondo esta nueva versión. Así que atentos, supongo que habrán muchos más artículos como éste.

Masim Vavai Sugianto: Membuat Live USB dari berbagai macam distro Linux di LinuxMint/Ubuntu

@ 08:32 UTCmember

Mungkin anda sudah pernah pakai Startup Disk Creator, dan juga sudah membaca dan mempraktekkan ulasan saya tentang USB Installer Windows. Kali ini tool yang kurang lebih sama dengan dua tool tadi namun tool ini hanya untuk install distro linux ke flashdisk anda, yaitu LiveUSB Install akan saya ulas di artikel ini.

LiveUSB Install adalah tool untuk membuat Live Linux USB di Linux dan Windows. Sangat mudah digunakan untuk menginstal bermacam distro Linux di flashdisk anda dari file image ISO atau dari CD/DVD, bahkan bisa langsung download dan install file ISO nya dari internet.

LiveUSB Install support bermacam distro Linux seperti Android, Debian, Centos, Fedora, Kubuntu, LinuxMint, OpenSuse, Ubuntu, Xubuntu dan banyak lagi. Anda bisa melihat daftar lengkapnya disini.

Untuk menginstal program ini di LinuxMint, jalankan perintah berikut melalui terminal:

sudo add-apt-repository “deb http://download.learnfree.eu/repository/skss / #SKSS”

wget http://download.learnfree.eu/repository/skss/repo.pub.asc -q -O- | sudo apt-key add -

sudo apt-get update

sudo apt-get install live-usb-install

Setelah terinstal dan dijalankan, jangan lupa colokkan flashdisk biar terdeteksi flashdisknya oleh program ini. Kemudian pilih Mode instalasi yang diinginkan pilihannya yaitu Distribution, Custom syslinux config, WinGrub ISO Chainloader, IMG Write and (Re)Install Syslinux.
Selanjutnya pilih sumber instalasinya, pilihannya ada 3 yaitu dari CD/DVD, ISO Image, dan Internet.

Di bagian Select Linux Distribution, anda bisa memilih nama distro dan versi Linux yang akan anda buat menjadi Live USB.

Anda juga bisa mencentang opsi Autodetect distribution di bagian Install from, supaya program bisa mendeteksi secara otomatis distro apa yang anda masukkan jika anda mengambil sumber dari CD/DVD atau dari ISO Image, jika sumbernya dari Internet maka anda tetap harus memilih nama dan versi distro Linuxnya.

Setelah instalasi distro linux yang anda inginkan selesai dimasukkan ke flashdisk, selanjutnya anda bisa gunakan flashdisk anda untuk menjalankan live session linux yang anda pilih tadi atau menginstalnya ke komputer target.

Sumber: Learnfree

Thursday
26 January, 2012

Sebastian Siebert: openSUSE – proprietären Grafik-Treiber AMD Catalyst 12.1 als RPM installieren

@ 20:01 UTCmember

AMD Catalyst 12.1 (fglrx 8.930) wurde veröffentlicht. Das Skript makerpm-amd-12.1.sh steht ab sofort zum Download zur Verfügung und unterstützt openSUSE 11.3, 11.4 und 12.1. Hinweis: AMD hat den Installer von ati-driver-installer… in amd-driver-installer… umbenannt. Im Zuge dessen habe ich ebenfalls das Skript von makerpm-ati… in makerpm-amd… umbenannt.

Nach einem Test dieser AMD Catalyst Version ist die GNOME 3.2-Problematik (Flackern und Bildschirmrisse) endlich behoben worden. Laut AMD sollten die Notebooks mit der PowerXpress-Technologie (Intel-/AMD-Grafikkarte – discrete GPU) wieder funktionieren. Ich wäre sehr verbunden, wenn jemand diese Funktionalität für mich testen könnte und bitte um entsprechende Rückmeldung. Vielen Dank.

Zudem habe ich die Generierung des Systemreport vom Skript überarbeitet, um weitere Systeminformationen abzufragen. Ein aktualisiertes Packaging Skript habe ich beigefügt und wird separat heruntergeladen. Ab sofort können die User von Balsam Professional (ein Ableger von openSUSE) das Skript verwenden. Das makerpm-Skript hat nun die Version 5.0 erreicht und bin ziemlich stolz darauf, dass die makerpm-Skript-Reihe sich seit 2 Jahren erfolgreich bewährt hat. Vielen Dank für eure Unterstützung und mit eurer Hilfe (Feedbacks und eingereichte Systemreports) habe ich mich für euch mit AMD auseinander gesetzt, um die Fehler im Treiber beheben zu lassen. Ich bitte euch nicht aufzuhören, sondern fleißig weiterhin Fehler zu melden. Vielen Dank.

Downloads:

Skript: makerpm-amd-12.1.sh
SHA1: makerpm-amd-12.1.sh.sha1

Installationsanleitung:
http://de.opensuse.org/SDB:AMD/ATI-Grafiktreiber#Installation_via_makerpm-ati-Skript

Über das makerpm-amd-Skript

Das Skript makerpm-amd-12.1.sh ist sehr mächtig, robust und läuft vollautomatisch. Der AMD-Installer wird automatisch heruntergeladen, falls er nicht schon im Verzeichnis liegt. Zudem wird geprüft, ob die Grafikkarte vom Treiber unterstützt wird. Auf Wunsch wird nach dem Bau des RPM-Packages der fglrx-Treiber installiert.

Folgende Argumente können dem Skript übergeben werden:

-b	Nur das RPM-Package bauen (Standard)
-c <type>	Nur X-Server konfigurieren. Monitor-Typ: single = 1 Monitor, dual = 2 Monitore (Wichtig: Nur ausführen, wenn es Probleme mit der Standardkonfiguration des X-Servers auftreten)
-d	Nur den ATI-Installer downloaden
-i	Das RPM-Package bauen und installieren bzw. updaten
-kms <yes\|no>	Kernel-Mode-Setting (KMS) aktivieren oder deaktivieren
-nohw	Hardware-Erkennung explizit ausschalten. (z.B. beim Bau in einer VM)
-old2ddriver <yes\|no>	den alten 2D-Treiber aktivieren oder deaktivieren
-r\|–report	erstellt ein Report und speichert diese in eine Datei namens ati-report.txt
-u\|–uninstall	entfernt AMD Catalyst restlos vom System. Zuerst wird das fglrx-Package (falls vorhanden) vom System deinstalliert. Danach werden vorhandene ATI-Dateien und -Verzeichnisse entfernt. Hinweis: Falls das Rebuild-Skript installiert wurde, wird es ebenfalls entfernt und das Initskript /etc/init.d/xdm wiederhergestellt.
-ur\|–uploadreport	wie Option –report nur zusätzlich wird der Report auf einem NoPaste-Service sprunge.us hochgeladen und gibt bei Erfolg den Link zurück.
-h	Die Hilfe anzeigen lassen
-V	Version des Skript anzeigen

Hilfe, es funktioniert nicht!

Bitte haltet folgende Regel ein:

Bei der Eingabe der Befehle auf mögliche Tippfehler überprüfen.
Möglicherweise ist die Lösung für das Problem …

@ 19:49 UTC

Sascha Manns: Skype with Plasma Active

@ 19:25 UTCmember

You have an Touchpaddevice and you're looking for an free and open source operatingsystem, touchfriendly and with a KDE UI?

Then you maybe have heard about Plasma Active. Plasma Active is a new UI specially developed for touch-devices. You can download it there from open-slx. That image is prepared to install Plasma Active on the Top of Balsam Professional.

In this Article you can see how to prepare the stick. After booting and installing you have a Plasma Active on your device. You also can use Plasma Active inside a Dual or Multiboot Installation.

But we want to use Skype for this device.

First of all you have to surft to: http://www.skype.com/intl/de/get-skype/on-your-computer/linux/downloading.suse . After accessing the site it will be prepare the download. Just save it any place.

Change now to that directory which contains the saved package. Type in your console:

sudo zypper in skype-2.2.0.35-suse.i586.rpm

After the installation you will see the Skype Icon in the Applicationlauncher.

Tap now on that icon. Now opens the graphical client as you maybe know from the desktop. Tap on Username and type there your Username with the virtual keyboard. Sadly the virtual keyboard doesn't see the Password field. That means that you have to use an external USB Keyboard for this field.

After the Login you can use it through tapping on it. If you tap on the Text field you can use the virtual keyboard. If you like to call anyone just tap on the phone icon.

The integrated WeTab Webcam is supported directly without any changes.

You can plug in a Headphone into the WeTab. A seperate port for a microphone isn't placed there. But the WeTab has a integrated microphone which pacify in most cases.

wetab-skype

Updated 27.1.12: Changed the packageinstall from rpm to zypper.

Uwe Dittmann: openSUSE: KDE SC 4.8.0 – freigegeben und installiert!

@ 17:20 UTCmember

Pünktlich nach Plan, wurde am gestrigen 25.Januar 2012 mit KDE SC 4.8.0 die neueste Ausgabe des KDE Projektes veröffentlicht. Neben dem beseitigen von etlichen Bugs, wurde auch wieder viele Neuerungen eingebaut. So hat das KDE Team gleich an vielen verschiedenen … Weiterlesen →

Alexandre Marcolino: Instalando SUN Java sob openSuSE 12.1

@ 17:18 UTC

Eu juntei informações de várias fontes aqui neste artigo, então comecemos dando crédito a quem merece! http://www.freetechie.com/blog/installing-oracle-sun-java-1-7u1-opensuse-12-1/ https://sites.google.com/site/easylinuxtipsproject/java-for-opensuse Meu sistemas Linux é um Notebook SAMSUNG RV411 com openSuSE 12.1 64bits. Agora, vamos ao artigo. A Sun descontinuou a sua licença que permitia as distribuições Linux distribuir versões empacotadas de sua JVM junto com suas [...]

Miguel Angel Barajas: Episodio 3 de Android Apps Reviews por GnuOwned En esta ocasión...

@ 15:35 UTC

Episodio 3 de Android Apps Reviews por GnuOwned

En esta ocasión platicamos de Foursquare y Untappd

Baltasar Ortega: Cómo instalar KDE 4.8 en openSUSE

@ 15:00 UTCmember

Al parecer las diferentes distribuciones Linux se han puesto las pilas y no tenemos que esperar unos días para instalarnos KDE 4.8 en nuestros PC.
De hecho estoy escribiendo estas líneas en un portátil con openSUSE 12.1 con KDE 4.8, cuya instalación realicé ayer sobre las 12 de la noche.
Bien, pasemos a las explicaciones, comencemos con cómo instalar KDE 4.8 en openSUSE

Basta con añadir los siguientes repositorios y actualizar el equipo. Si utilizamos 11.4, basta cambiar el número en la línea de rspositorios.

http://download.opensuse.org/repositories/KDE:/Release:/48/openSUSE_12.1/

http://download.opensuse.org/repositories/KDE:/Extra/KDE_Release_48_openSUSE_12.1/

Esto lo podemos hacer mediante la línea de comandos
Más información: My KDE week | openSUSE

Notas importantes:

Asegurarse que no se añade ningún repositior Qt ya que todos los paquetes ya están integrados en los anteriores.

Desactivar el repositorio UpdatedApps

Si no se inicia el escritorio Plasma y se queda en negro el fondo de escritorio pero funciona KRunner y el resto de aplicaciones, bastará eliminar la carpeta oculta /.kde4 que está en el directorio raiz del usuario. Esto depende de la configuración del escritorio anterior. Eso si, perderemos las configuraciones básicas de nuestro anterior KDE.

Fridrich Strba: FOSDEM 2012 - How to make the best of it and become LibreOffice developer

@ 14:49 UTC

FOSDEM 2012 is just round the corner and, as you might know, LibreOffice will have a DevRoom this year too. And, as it was already publicized, your servant and Eilidh McAdam of libvisio fame will attend too. The goal of this event will be to help you to become a LibreOffice developer, by helping you to get your first contact with the code from inside.

How to prepare for the event?

In order to give as many community members the possibility to speak, the presentations will not take more then 15 minutes each. But we will be there for one-to-one contacts and hacking goodness. If you are interested in contributing to our new Visio import filter, or the upcomming Corel Draw and MS Publisher filters, here is what you can do:

Find a bug that is bothering you in the current Visio import filter, or some simple feature that the importer currently does not support
Check out the following libraries:
- master branch of libwpd (git clone git://libwpd.git.sourceforge.net/gitroot/libwpd/libwpd)
- STABLE-0-2-0 branch of libwpg (git clone -b STABLE-0-2-0 git://libwpg.git.sourceforge.net/gitroot/libwpg/libwpg)
- master branch of libwps (git clone git://libwps.git.sourceforge.net/gitroot/libwps/libwps)
- master branch of libvisio (git clone git://anongit.freedesktop.org/libreoffice/contrib/libvisio), and
- master branch of libcdr (git clone git://anongit.freedesktop.org/libreoffice/libcdr)
Build them as system libraries and install them in the same order.
Then build LibreOffice according to these instructions. The important thing is to use those system libraries that you just built. To do so, be sure you added to the configure flags
- --with-system-liwpd
- --with-system-libwpg
- --with-system-libwps
- --with-system-libvisio
- --with-system-libcdr

With this kind of build, you will be ready to make the most from your Brussels weekend. Nevetheless, you can drop around at our IRC channel #libreoffice-dev channel at irc.freenode.net for more information and ideas.

Starting to do it instead of planning to do it ...

... is the best way to enter the FOSS development. That is why your servant and Eilidh will be around to hold your hand with debugging and finding way to implement your favourite features. We will answer your questions about the library design. We will point you to the place in the code where your bug might linger. And for more complicated stuff, we will debug it with you.

Don't expect us to give you a fish, but we will certainly teach you how to catch it by yourself. And in the same token, you will become a contributor inside a community of smart people that is fun to hang and hack with.

See you in Brussels the 4^th and 5^th of February 2012.

Ray Chen: Hime 輸入法 for openSUSE

@ 13:51 UTCmember

Hime 首頁：https://github.com/caleb-/hime/
Hime 是由 gcin 輸入法分支出來開發的，
http://tetralet.luna.com.tw/index.php?op=ViewArticle&articleId=234&blogId=1
兩方面仍維持合作的關係，
不過可能開發的重心會不一樣，
也就是說，隨著時間流逝，兩者的差別將越來越大
如果您想要嘗試一下 hime
可以由 home:swyear 套件庫安裝
以 openSUSE 12.1 為例：

# zypper ar obs://home:swyear/openSUSE_12.1 swyear
(若已經加過 home:swyear 套件庫，上面步驟不必再做)
# zypper in hime

重新登入後會自動改用 hime
(這裡的優先順序並不代表任何的偏好，
只是希望新安裝一個輸入法後能順利的切換)

若要改回用其他輸入法可以
1. 移除 hime，回到您的原本設定
2. 要同時保有 hime
在 ~/.profile 加上

export INPUT_METHOD=gcin

全域設定在 /etc/sysconfig/language
設定

INPUT_METHOD=gcin

或其他您想要的輸入法

Lucian Oprea: [Actualizat] Program de lansare openSUSE 12.2

@ 13:09 UTCmember

Indiferent că versiunea 12.1 a fost un succes sau nu, Echipa Boosters a terminat de conceput calendarul pentru construcţia şi lansarea openSUSE 12.2. Conform calendarului creat de Coolo, openSUSE 12.2 va fi disponibil publicului pe data de 15 iulie 2012.

Calendarul detaliat cu etapetele de construcţie este următorul:
openSUSE 12.2 Milestone 1, 9 Februarie 2012
openSUSE 12.2 Milestone 2, 3 Martie 2012
openSUSE 12.2 Milestone 3, 5 Aprilie 2012
openSUSE 12.2 Milestone 4, 26 Aprilie 2012
openSUSE 12.2 Beta 1, 24 Mai 2012
openSUSE 12.2 RC1, 14 Iunie 2012
openSUSE 12.2 RC2, 28 Iunie 2012
openSUSE 12.2 Gold Master, 6 Iulie 2012
openSUSE 12.2 lansarea oficială Duminică, 11 Iulie 2012

PS: calendar actualizat conform informaţiilor din acest articol.

Lucian Oprea: [Actualizat] Cinnamon disponibil şi pentru openSUSE

@ 13:08 UTCmember

Încă de la prima sa apariţie Gnome 3 a creat valuri… pe internet. Unii utilizatori au aplaudat şi în acelaşi timp indrăgit noul aspect al acestui mediu de lucru în timp ce alţii l-au comparat cu Unity al celor de la Ubuntu, considerând versiunea 3 drept o dezamăgire. Personal îndrăznesc să cred că şi pe meleagurile noastre treaba stă cam la fel.
În toiul acestei dispute se naşte Cinnamon, un fork al Gnome 3, creat de fondatorul distribuţiei Linux Mint Clement Lefebvre. Cinnamon este considerat de utilizatori râspunsul la schimbările majore aduse de Gnome 3, fiind o îmbinare între aspectul clasic şi funcţionalitatea avansată oferită de actuala versiune. Spre bucuria utilizatorilor de openSUSE, Cinnamon este disponibil pentru versiunea 12.1 prin metoda 1 click install. Adiţional, acest mediu de lucru este disponibil şi pentru cei care folosesc versiunea Factory a openSUSE precum şi pentru Tumbleweed. Utilizare plăcută !

Actualizarea articolul constă în următoarele două elemente:
1. Mediul de lucru Cinnamon a fost mutat în cadrul surselor de pachete Gnome
2. Ajustarea adreselor pentru instalarea Cinnamon prin metoda “1 click install”

Duncan Mac-Vicar: On Java, Maven, JPP and rpm

@ 10:06 UTCmember

Java on Linux has been always a “special” topic. They don’t mix well.

The mindset of Linux distributions is very different to the Java world when it comes to build software. This is understandable as they have different requirements.

In the Java world, there is the concept of artifacts. You build org.foo.bar:bar-moo:1.1 once and it stays there forever, archived for anyone to use it. Tools like maven and ivy allow developers to specify in their source tree the specific dependencies of their components and those are grabbed from the network, the software built and then publish the output as a new artifact that others can grab.

Linux distributions on the other hand, bootstrap the complete stack from source. They don’t take the binary artifact from upstream but build it, and then use the binary they built to build the next. This seems to work pretty well for C, C++, and for Ruby, Python, let’s say it “works”.

When it comes to package Java software, Linux distributors find themselves in the following situation:

If a buildable source tarball is provided then you are lucky.
If the buildable tarball is provided, it will either include a directory full of binary jars (the build dependencies) or it will have a very automatic build system grabbing them from the network.

This clashes with Linux in various edges:

Linux distributions have normally one version of each component. The Java method works well if you bundle your dependencies inside your application, but not if everything is a reusable component. I have mixed feelings here. I think bundling your dependencies in the application for everything that is not part of the “base” system is the right approach. Updating them can break the application and trying to control this via QA only moves QA from the application developers to the distribution itself. When I ship apache-commons-collection as part of my Foobar Java application as a Java package, I am inviting everyone to use it, forcing myself to give support for it out of the context of the application.
Distributions needs to build from source. Even if you get rid of the above requirement and you bundle all your dependencies, distributions want to build everything from source. This has technical and legal reasons. SUSE build system does very complex checks on every package that it builds. Those checks are part of the quality we sell to our customers. Other reasons are legal: I am still trying, for example, to build the Play! framework. Even if it is BSD, it includes some .jars inside of unknown origin. What would happen if one of these jars results to be proprietary?. Michael Vyskocil had a similar issue with openproj and its bundled dependencies.

Another reason to build from source is support. Enterprise distributions sell support and if a customer has a problem, we will fix it on our own and not wait for upstream to release a new version. Having a standardized way to …

@ 08:56 UTC

If you were waiting for Studio to support the latest version of openSUSE on Amazon's EC2, listen up: Your wait is over. The same goes if you tried to upload an older version of openSUSE to EC2's latest region, Sao Paulo. Studio finally offers full functionality for all openSUSE versions on all EC2 regions. Of course, SLE still offers a wide range of advantages over openSUSE. Just think about long term support, stability or getting updates for your system. However, if you chose to create your appliance based on openSUSE, you are now finally able to use Studio to take your first steps into the cloud. Have a lot of fun!

Mariusz Fik: Priorytety fontów a fontconfig

@ 00:22 UTCmember

Fontconfig jest biblioteką służącą do konfiguracji dostępu do fontów. Cała konfiguracja jest przechowywana w plikach xml, dzięki czemu są one czytelne i łatwe w modyfikacji. Wyczerpujące informacje można znaleźć w podręczniku man fonts-conf bądź bezpośrednio na stronie.

Domyślna konfiguracja jest wystarczająca dla przeciętnego użytkownika jednak ma pewien mankament. Otóż rodzina fontów MS ma większy priorytet niż fonty domyślne. Dla przykładu, mając ustawione fonty z rodziny DejaVu Sans jako domyślne instalujemy font Consolas (dostępny np. w PowerPointViewer – wypakować za pomocą cabextract). Okazuje się, że po instalacji staje się on domyślnym fontem monospace. Czy aby tego chcieliśmy?

Jeśli nie chcemy aby zainstalowane fonty MS stały się domyślnymi, wystarczy zmienić konfigurację fontconfig. Tworzymy kopię zapasową i edytujemy plik:

su
cp /etc/fonts/suse-post-user.conf /etc/fonts/suse-post-user.conf.backup
vim /etc/fonts/suse-post-user.conf

Odszukujemy odpowiednie fonty które wg. nas nie powinny panoszyć się w systemie (np. Consolas, Verdana, etc.) i przenosimy je o kilka linii w dół. Po zapisaniu pliku pozostaje nam odświeżenie pamięci podręcznej fontconfig:

su
rm /var/cache/fontconfig/*
fc-cache

Od teraz, fonty którym obniżyliśmy priorytet nie będą ‘ustawiać’ się jako domyślne choć nadal można będzie z nich korzystać.

Przykładowy plik konfiguracyjny z obniżonym priorytetem fontów MS: suse-post-user.conf

Wednesday
25 January, 2012

Timothée Briolet: KDE SC 4.8 est là

@ 22:40 UTC

KDE SC 4.8 vient de sortir aujourd’hui.

KDE SC 4.8

Des améliorations majeures de fonctionnalités, de stabilité et de performances ont été réalisées sur le bureau Plasma et les applications KDE.

L’annonce officielle [en] : http://www.kde.org/announcements/4.8/

Kwin est plus performant et moins gourmand en ressources. Le « gestionnaire d’énergie » a été réécrit avec une intégration des activités. Les premiers Plasmoids basés sur QTQuick ont été intégrés.

Plus d’infos dans l’annonce officielle des améliorations de Plasma [en] : Plasma Workspaces Announcement.

Les applications KDE ont été mises à jour avec nottement Dolphin pourvu d’un nouveau moteur d’affichage. Kate arrive avec plusieurs nouvelles fonctionnalités pour les développeurs, Gwenview maintenant doté d’effets visuels et d’autres améliorations. KDE Telepathy sort aujourd’hui en version 0.3 Bêta. Marble s’améliore avec entre autres l’intégration dans Krunner.

Plus d’infos dans l’annonce officielle de la mise à jour des applications [en] : KDE Applications Announcement.

La plateforme KDE fourni les fondations pour tous les logiciels KDE qui sont maintenant plus stables que jamais. Elle arrive avec un nouveau système d’enregistrement des mots de passe (compatibilité avec les applications GNOME).

Plus d’infos dans l’annonce officielle de la nouvelle plateforme [en] : KDE Platform 4.8 release announcement.

Pour réaliser la mise à jour sous openSUSE, effectuez les commandes suivantes :

sudo zypper ar http://download.opensuse.org/repositories/KDE:/Release:/48/openSUSE_12.1/ KR48
sudo zypper mr -r KR48
sudo zypper ref
sudo zypper dup --from KR48

Je vous laisse découvrir tout ça !

Pour plus d’infos allez voir la news sur Linuxfr très complète : http://linuxfr.org/news/kde-sc-4-8-est-disponible

La news sur Alionet : http://www.alionet.org/content.php?189-kde-SC-4.8
–

Syvolc

Nelson Marques: ‘tirpitz’ – you sunk my battleship…

@ 22:10 UTC

I’ve forked Linux Mint Welcome Screen into ‘tirpitz’… and though I’ve used a lower case name so it wouldn’t be associated with Admiral Tirpitz, some people really like to make a big deal out of everything… so this ‘tirpitz’ actually never got to fire his main guns…

Since I really believe that this application can help openSUSE (at least I want to bundle it in a Cinnamon spin), it can be a great marketing tool for new users and it’s not really intrusive… I’ve decided to take suggestions for potential names for this fork…

I’ve spoken today with Clement and though we’re moving different ways, we’ve decided to work together whenever possible and look for features together and share our work… He seems to be a pretty accessible guy and it’s a great and fun opportunity to improve and learn a bit more on python.

Any suggestions for a name are welcome and if some are left in comments, I’m sure I will pick one of them…

Sebastian Siebert: openSUSE 12.2 – Roadmap wurde bekannt gegeben

@ 21:51 UTCmember

Die Entwicklung an openSUSE 12.2 hat bereits begonnen. Die jeweiligen Meilensteine wurden festgelegt und sieht wie folgt aus.

09.02.2012 – Milestone 1
03.03.2012 – Milestone 2
05.04.2012 – Milestone 3
26.04.2012 – Milestone 4
24.05.2012 – Beta 1
14.06.2012 – Release Candidate 1
28.06.2012 – Release Candidate 2
06.07.2012 – Gold Master
11.07.2012 – openSUSE 12.2 Final Release

Quelle: http://en.opensuse.org/openSUSE:Roadmap

Die openSUSE 12.2 Entwicklungs-CD und -DVD werden erst ab dem jeweiligen Meilenstein gebaut und veröffentlicht.
Download ab dem 09.02.2012: http://software.opensuse.org/developer/

Hilfe zum Projekt ist immer willkommen. Egal ob man in der Wiki mitarbeitet, sich am openFATE beteiligt, Pakete in unserem OBS für openSUSE bauen, in der Mailing Liste; im hauseigenen Forum oder auch im IRC Hilfestellung gibt, Fehler in openSUSE via Bugreport melden, u.v.m. Über Mitstreiter an meiner Seite würde ich mich freuen. Ein paar Voraussetzungen, wie sie in jedem Projekt gibt: ein wenig Freizeit entbehren, am Ball bleiben, sich gegenzeitig motivieren/helfen.

Eine weitere wichtige Meldung ist, dass der Support für openSUSE 11.3 am 20.01.2012 eingestellt wurde. Um weiterhin mit Updates versorgt zu werden, ist es empfohlen in nächster Zeit auf openSUSE 11.4 oder 12.1 umzusteigen.

Quelle: http://lists.opensuse.org/opensuse-announce/2012-01/msg00001.html

Michael Meeks: 2012-01-25: Wednesday

@ 21:00 UTCmember

Chewed mail, quick call with Vojtech, then Charles. Finally got around to submitting a LinuxTag paper or two. Lunch. More mail, patch pieces.
J. out for Rosemary's leaving pizza party. Up extremely late poking android's wedging on ANativeWindow_lock - sadly the debugger gives no trace: an thread un-attached to the VM ?

Older blog entries ->

This site is not an official openSUSE website, and is not in any way affiliated with or endorsed by SUSE Linux GmbH or Novell.

openSUSE and SUSE are trademarks of Novell, Inc. in the United States and other countries.

Overview