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.

17 February, 2017

  • How librsvg exports reference-counted objects from Rust to C

    Librsvg maintains a tree of RsvgNode objects; each of these corresponds to an SVG element. An RsvgNode is a node in an n-ary tree; for example, a node for an SVG "group" can have any number of children that represent various shapes. The toplevel element is the root of the tree, and it is the "svg" XML element at the beginning of an SVG file.

    Last December I started to sketch out the Rust code to replace the C implementation of RsvgNode. Today I was able to push a working version to the librsvg repository. This is a major milestone for myself, and this post is a description of that journey.

    Nodes in librsvg in C

    Librsvg used to have a very simple scheme for memory management and its representation of SVG objects. There was a basic RsvgNode structure:

    typedef enum {
        /* ... a bunch of other node types */
    } RsvgNodeType;
    typedef struct {
        RsvgState    *state;
        RsvgNode     *parent;
        GPtrArray    *children;
        RsvgNodeType  type;
        void (*free)     (RsvgNode *self);
        void (*draw)     (RsvgNode *self, RsvgDrawingCtx *ctx, int dominate);
        void (*set_atts) (RsvgNode *self, RsvgHandle *handle, RsvgPropertyBag *pbag);
    } RsvgNode;

    This is a no-frills base struct for SVG objects; it just has the node's parent, its children, its type, the CSS state for the node, and a virtual function table with just three methods. In typical C fashion for derived objects, each concrete object type is declared similar to the following one:

    typedef struct {
        RsvgNode super;
        RsvgLength cx, cy, r;
    } RsvgNodeCircle;

    The user-facing object in librsvg is an RsvgHandle: that is what you get out of the API when you load an SVG file. Internally, the RsvgHandle has a tree of RsvgNode objects — actually, a tree of concrete implementations like the RsvgNodeCircle above or others like RsvgNodeGroup (for groups of objects) or RsvgNodePath (for Bézier paths).

    Also, the RsvgHandle has an all_nodes array, which is a big list of all the RsvgNode objects that it is handling, regardless of their position in the tree. It also has a hash table that maps string IDs to nodes, for when the XML elements in the SVG have an "id" attribute to name them. At various times, the RsvgHandle or the drawing-time machinery may have extra references to nodes within the tree.

    Memory management is simple. Nodes get allocated at loading time, and they never get freed or moved around until the RsvgHandle is destroyed. To free the nodes, the RsvgHandle code just goes through its all_nodes array and calls the node->free() method on each of them. Any references to the nodes that remain in other places will dangle, but since everything is being freed anyway, things are fine. Before the RsvgHandle is freed, the code can copy pointers around with impunity, as it knows that the all_nodes array basically stores the "master" pointers that will need to be freed in the end.

    But Rust doesn't work that way

    Not so, indeed! C lets you copy pointers


A openSUSE Conference 2017, o grande evento da comunidade openSUSE europeia foi agendado para a cidade alemã de Nuremberg, um cidade com uma vasta experiência na realização de encontros livres além de ser o quartel general da SUSE.

O evento ocorrerá de 26 a 28 de maio no Nuremberg Docker Meetup com a promessa de ser um grande evento para todos os apoiadores e usuários da distribuição do Camaleão em particular e do Software Livre.

A chamada para a publicação de trabalhos vai até o dia 31 de março. Então você sabe, se você quiser participar ativamente, não hesite em enviar sua palestra. 

Em suma, um dos principais eventos europeus de uma das principais distribuições sempre foi ligado ao KDE mundo.
Maiores informações acesse a página do evento no link abaixo:


Mantenha-se atualizado e você sabe: Divirta-se!

Michael Meeks: 2017-02-17 Friday.

21:00 UTCmember

  • Up; worked through the morning on the mail and task backlog. Out for a walk to see some ponies with the babes at Thorpness.
  • Back for lunch, and then to tackle the plumbing problems. Attacked an amazing amount of congealed fat in the sink plumbing - simply extraordinary; eventually had to cut the pipe-work out in sections and replace it with H's help.
  • Relaxed in the evening with some fine food. Couldn't sleep, hacked on socket code instead.

Como instalar a versão mais recente do cliente FTP FileZilla no Ubuntu 16.04

Já mostrei aqui como instalar o FileZilla no Ubuntu. Agora você verá como instalar o FileZilla no Linux, ou pelo menos, na maioria das distribuições.

Leia o restante do texto "Como instalar o FileZilla no Linux manualmente"


Dear Tumbleweed users and hackers,

This week we ‘only’ delivered 5 snapshots. But at least it was big ones, so that makes up for it. The review covers the snapshots {0211..0215}.

What did you receive

  • apparmor 2.11.0
  • KDE Plasma 5.9.1
  • KDE Applications 16.12.2
  • Linux Kernel 4.9.9
  • grep 2.28, with performance improvements
  • PackageKit-Qt: no more support for Qt4

In the staging ares, some work has been happening, but the usual suspects are still awaiting some love:

  • rpm 4.13.0 – the easy ones seem fixed; some obscure errors are left; mainly rpmlint seems to have trouble now
  • KDE Plasma 5.9.2
  • Mesa 17.0.0 (jumping up from 13.0)
  • Linux Kernel 4.9.10
  • glibc 2.25: still some failures left to tackle
  • util-linux will no longer pull in insserv for you. If your package makes use of it, you are now responsible for it
  • Libreoffice 5.3 – still fails the test suite on ppc64le
  • Python 3.6 – almost ready. The final piece is apparmor, where a fix is in the works / almost ready

As many will have noticed, the legal-auto bot is currently ‘much more reluctant’ to accept submissions. This is due to a total rewrite/restructuring of the legal process. See Stephan Kulow’s mail for more information.

Como instalar a última versão do driver Nvidia no Linux

Foi lançada mais uma atualização do Nvidia Driver para Linux. Se você utiliza um hardware suportado por esse pacote, veja aqui como instalar a última versão do driver Nvidia no Linux, ou melhor, em qualquer distribuição Linux suportada por ele.

Leia o restante do texto "Como instalar a última versão do driver Nvidia no Linux"

Como instalar o navegador Qupzilla no Linux manualmente

Já mostrei como instalar o Qupzilla no Ubuntu, agora, veja como instalar o navegador Qupzilla no Linux manualmente, ou seja, em qualquer distro.

Leia o restante do texto "Como instalar o navegador Qupzilla no Linux manualmente"

16 February, 2017

Michael Meeks: 2017-02-16 Thursday.

21:00 UTCmember

  • Poked at socket code a lot in the morning; drove to Aldeburgh with the family - listened to the Green Ring Conspiracy in the car. Chat with Philippe, ESC call. More hackery.


¿Qué es un proceso?

Un proceso es, a grosso modo, un programa que está en ejecución, como por ejemplo Firefox, VLC, Libre Office, etc

Los procesos se identifican mediante un PID (Process ID). El PID es un número entero positivo que identifica al proceso.


¿Qué tipos de procesos existen?

Además de los procesos “normales”, existen varios tipos de procesos, los mas importantes son:
– Proceso hijo: Proceso creado por otro proceso
– Proceso zombie: Proceso hijo que ha terminado de ejecutarse, pero permanece a la espera de instrucciones por parte del proceso padre.
– Huérfano: Cuando un proceso hijo sigue en funcionamiento pero el proceso padre ha sido matado. Los procesos huérfanos no se conviertes en zombies, sino que son adoptados por el init
– Daemon: Procesos que se ejecutan en 2º plano, generalmente relacionados con el SO.


¿Cómo puedo ver los procesos?

La opción mas sencilla es usar el “Monitor de sistema”, que ya viene instalado en la mayoría de distros con GNOME o Mate.

Monitor del sistema

Desde el terminal de comandos puedes ver los procesos usando una de las siguientes herramientas:

  • top
  • ps
  • htop

Yo recomiendo instalar y utilizar htop
, que permite ordenar procesos por % de uso de CPU, uso de memoria, buscar procesos, matar procesos y mucho más.


Como instalar o editor de vídeo Cinelerra no Linux

Já ouviu falar do editor de vídeo Cinelerra? Conheça e veja aqui como instalar o programa a partir do binário de 64 bits para Linux, disponibilizado pela sua produtora.

Leia o restante do texto "Como instalar o editor de vídeo Cinelerra no Linux"


Today: update the update process!

Yesterday a colleague asked me if it would be possible to apply a driver update (DUD) to the rescue system. He wanted to use a new btrfsprogs package.

My immediate reaction was: no, you can’t do it. But then, there’s no technical reason why it shouldn’t be possible – it actually nearly works. The updates are downloaded as usual – just not applied to the rescue system.

So I thought: “Why not make a driver update so driver updates work also for the rescue system?”

Here’s how I did it.

First, let’s find out how driver updates are usually applied. The code is here:


We need just these three lines:

for i in /update/[0-9]*/inst-sys ; do
  [ -d "$i" ] && adddir "$i" /

linuxrc downloads the driver updates and stores them in an /update directory. One (numbered) subdirectory for each update.

It obviously uses some adddir script. So we’ll need it as well. Luckily, it’s not far away:


Next, we’ll have to find the spot where the rescue system is set up. It’s done in this script:


Let’s do some copy-and-paste programming and insert the above code near the end of the script. It then might look like this

# driver update: add files to rescue system
if [ -d /mounts/initrd/update ] ; then
  cp -r /mounts/initrd/update /
  for i in /update/[0-9]*/inst-sys ; do
    [ -d "$i" ] && /mounts/initrd/scripts/adddir "$i" /

Some notes:

  • You have to know that prepare_rescue is run as the last thing before we exec to init. So everything is already in place, the left-over files from initrd are mounted at /mounts/initrd and will be removed at the end of the script.
  • This means we have to copy our updates into the new root directory, else they will be lost.
  • Also, we plan to make the adddir script available at /scripts/adddir by our driver update (see below).

Now let’s create the driver update:

mkdud --create dud_for_rescue.dud \
  --dist tw --dist leap42.1 --dist leap42.2 --dist sle12 \
  --name 'Apply DUD also to rescue system' \
  --exec 'cp adddir prepare_rescue /scripts' \
  adddir prepare_rescue

Here’s what this call does, line-by-line:

  • the fix works for all current SUSE distributions, so let’s support them
  • give the driver update some nice name
  • this command is run right after the driver update got loaded; we copy the scripts out of the driver update to their final location
  • add adddir and our modified prepare_rescue script

Here is the result: dud_for_rescue.dud.

Now, back to the original problem: how to use this to update a package in the rescue system? That’s easy:

mkdud --create new_btrfs.dud \
  --dist sle12 \
  dud_for_rescue.dud btrfsprogs.rpm

creates a driver update (for SLE12) that updates btrfsprogs also in the rescue system.


Two Linux Kernels per week in openSUSE Tumbleweed is becoming the norm as the rolling release is providing daily snapshots of new software that are closely aligned with upstream development.

Kernel 4.9.8 and 4.9.9 were released in the 20170208 and 20170212 snapshots respectively and the later brought a fix for a Btrfs system call.

Beside the 4.9.8 Kernel in the first week’s snapshot, 20170208, Mesa users will be happy to see version 13.0.4 had a specfile fix for build configuration for ARM, Power PC and s390 architectures. Gimp 2.8.20 made the color selection of the paint tool more robust and updated translations for a number of European languages. Several other packages were updated in the repositories from this snapshot and python3-kiwi 9.0.2 and vim 8.0.311 provided the most fixes.

Snapshot 20170209 brought the first major release of libosinfo (Operating System information database) in Tumbleweed with version 1.0.0, which focuses on metadata about operating systems and provides a single place to manage it in a virtualized environment.  F Virtual Window Manager (FVWM) 2.6.7 added a handful of new features and removed several other features like  GTK 1.x support.

Plasma 5.9.1 came in the 20170211 snapshot and AppArmor 2.11.0 update provided multiple improvements and fixes, one of which fixed an issue that Kernel 4.8 and above affected Apparmor policy enforcement. Libssh hackers made use of their time at FOSDEM and squashed bugs, which came in the libssh 0.7.4.

Both 20170213 and 20170214 snapshots provided updates for KDE Applications 16.12.2. GNU Compiler Collection 6.3.1 provides from architectural fixes and grub2 now has a Release Candidate 1, which came in the most recent snapshot.


A humanoid robot should be able to talk. So I looked around for some open source speech synthesis software.

(The above video does feature a talking robot (and a multilingual dolphin) but that's where similarities with the following content end.)


Hello world:

espeak 'Hello, world!'

Standard input works too:

espeak <<EOS
A robot may not injure a human being or, through inaction,
allow a human being to come to harm.

I need the robot to speak Czech too:

espeak -v cs 'Dobrý den!'

Chinese also seems to work, at least to my beginner ear:

espeak -v zh '认识你很高兴'
# The same in pinyin
espeak -v zh 'ren4shi ni3 hen3 gao1xing4'

To put the words to the robot's mouth we first need to save the sound to a file:

espeak -w dobry-den.wav -v cs 'Dobrý den!'    # 16 bit, mono 22050 Hz

Now a thing that is not so useful for the robot, but a cool diversion. This tells eSpeak to be quiet, and transcribe the text in International Phonetic Alphabet.

espeak -q --ipa 'All human beings are born free and equal
in dignity and rights. They are endowed with reason and conscience
and should act towards one another in a spirit of brotherhood.'

ˈɔːl hjˈuːmən bˈiːɪŋz ɑː bˈɔːn fɹˈiː and ˈiːkwəl ɪn dˈɪɡnɪti and ɹˈaɪts

ðeɪ ɑːɹ ɛndˈaʊd wɪð ɹˈiːzən and kˈɒnʃəns and ʃˌʊd ˈakt tʊwˈɔːdz wˈɒn ɐnˈʌðəɹ ɪn ɐ spˈɪɹɪt ɒv bɹˈʌðəhˌʊd

And it also works for Czech:

espeak -q -v cs --ipa 'Všichni lidé rodí se svobodní a sobě rovní
co do důstojnosti a práv. Jsou nadáni rozumem a svědomím
a mají spolu jednat v duchu bratrství.'

fʃˈixɲi lˈideː rˈoɟiː se svˈobodɲiː a sˈobje rˈovɲiː tsˈo do dˈuːstojnˌosci a prˈaːv

jsoʊ nˈadaːɲi rˈozumem a svjˈedomiːm a mˌajiː spˈolu jˈednat v dˈuxu brˈatr̩stviː


The problem with eSpeak is that it sounds quite robotic. I remembered that for Czech, the epos system was much better, also for its availability of better quality downloadable voices.

I installed epos (here as an openSUSE RPM) and downloaded the high quality voices epos-tdp.tgz, then unpacked them to the right place:

cd /usr/share/epos/inv
sudo tar xvf .../epos-tdp.tgz

At first I got no sound but strace showed me a problem with /dev/dsp and a bit of searching turned out that I must run eposd with a dsp wrapper:

padsp eposd $OPTIONS
# eg.
padsp eposd --voice machac
padsp eposd --voice violka

Another quirk is that epos wants the input in ISO Latin 2, so I used iconv:

while read S; do say-epos $(echo "$S" | iconv -f utf8 -t l2); done

For saving the sound to a file, use -w to use a fixed


Exactly on the schedule, Weblate 2.11 is out today. This release brings extended stats available to users and various other improvements and bug fixes.

Full list of changes:

  • Include language detailed information on language page.
  • Mercurial backend improvements.
  • Added option to specify translation component priority.
  • More consistent usage of Group ACL even with less used permissions.
  • Added WL_BRANCH variable to hook scripts.
  • Improved developer documentation.
  • Better compatibility with various Git versions in Git exporter addon.
  • Included per project and component stats.
  • Added language code mapping for better support of Microsoft Translate API.
  • Moved fulltext cleanup to background job to make translation removal faster.
  • Fixed displaying of plural source for languages with single plural form.
  • Improved error handling in import_project.
  • Various performance improvements.

If you are upgrading from older version, please follow our upgrading instructions.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Aptoide, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Filed under: Debian English phpMyAdmin SUSE Weblate | 0 comments

My efforts to spread the good news of Linux continues with this somewhat basic but capable Gateway laptop. The name is a little odd and not very memorable: This is the NE56R41u… sounds awesome… It seems that not everyone can have naming creativity.

Admittedly, in my hasty search on the web for other individual Linux install experiences, I didn’t see much positive. I expected there to be some fiddling around with the machine in order to install openSUSE Linux on the Gateway computer.

This is the second laptop I have converted for this particular family. The first one went so well for them, they asked if I could fix up their other broken PC. It is rather encouraging to know that they really liked it and wanted yet another machine with this “Linux Stuff.”

Preparing the Installation

Having previously used the SUSE Imagewriter to “burn” the openSUSE Leap 42.2 to a USB Flash drive. I wanted to start out by just plugging the USB drive in and seeing what happens on a cold boot. Of course, nothing happened as it booted to a broken Windows install.

I had to get into the BIOS but the designers of this machine felt it best not to let you know on screen how to get into the system firmware. A little research online gave me a few hints as to how to get into it and what ended up working was to press and hold F2 immediately after you power on the machine.

Within the BIOS configuration utility, I moved over to the Boot options and set the USB HDD as first on the boot order and attempt installation. The result was, the system would not boot from USB stick but rather just sat on the Gateway Logo splash screen. It appears that I cannot boot from USB with UEFI active. Thankfully, there is a toggle to switch to Legacy BIOS boot mode so that I can actually get the thing to boot from USB.

One little quirk that I don’t understand is, when you put the BIOS in legacy mode, you can’t change the boot order. Set the boot order in UEFI and switch to Legacy Mode. Not a big deal, just seemed a bit annoying.

Installation Process

The installation was extremely uneventful and not much to discuss. You can basically follow the step by step from there. I did setup the network so that it would pull the latest packages upon install. I didn’t care for the default partitioning scheme set up by the installer so I did make a slight customization:
- Increased Swap Space to 4 Gb instead of the default 2 Gb.
- Increased The / (root) partition from 10Gb to 30Gb. I do not like running out of space on the root partition.

I am a fan of using SSH for remote access and file transfers, so prior to committing the install, I opened the SSH port and activated the service so that I could

15 February, 2017

Michael Meeks: 2017-02-15 Wednesday.

21:00 UTCmember

  • Awoke again to the dulcet tones of the neighbours extension being drilled / compacted / etc. Hey ho - they get to enjoy our early morning piano practice I suppose.
  • Built ESC stats. Most encouraged to see that the German comment count has dropped by ~10% in the first two weeks of February - ~320 lines fewer (of 3600) thanks to: Johnny M, Michael Stahl (RedHat), Katarina Behrens (CIB), and Lukas Röllin - wonderful.
  • Sync. with Ash; interview in the evening.


You create docker containers and many tools are missing. As a example: tcpdump

So I was looking for a solution for sniffing the traffic from outside of the container. It is recommended to setup an additional (tcpdump) container and to use it with following network connection:

docker pull adamoss/docker-tcpdump

docker run -ti –net=container:${id} adamoss/tcpdump port https or port http


You can specify different ports and save the data in a file. The id is the name of the container and the „–net=container:“ is saying that you want to have input/output traffic of the docker container like the command would be executed on the same system.


Veamos cómo hacer funcionar una Raspberry Pi 3 con openSUSE. Empezando desde el comienzo…

Antes que nada aclarar que no tengo una Raspberry Pi. Este artículo simplemente es una traducción de un artículo en inglés sobre cómo instalar openSUSE en una Raspberry Pi 3.

El artículo es una traducción de uno escrito por Dmitri Popov en los blogs de suse.com

Por tanto si lo intentáis y no lo conseguís siguiendo los pasos, no podré ayudaros, ya que no tengo los conocimientos, ni la experiencia en dicho equipo. Dicho esto empezamos a hacer funcionar nuestro openSUSE en una Raspberry Pi 3.


Imagen: Yan Arief

Hacer funcionar openSUSE en Raspberry Pi 3 no es complicado, pero hay algunos pequeños pasos que hay que dar para que todo funciona bien.

Lo primero de todo, tienes varias opciones entre las que escoger. Si tienes pensado utilizar la Raspberry Pi 3 como un equipo normal de trabajo, entonces openSUSE con un entorno gráfico es la mejor opción.

Puedes escoger entre varias opciones de entornos gráficos que consumen pocos recursos: X11, Enlightenment, Xfce, o LXQT. Y también  tienes la opción de poder escoger entre la versión de lanzamientos estables o de actualización contínua o “rolling release” que son las opciones de Leap o Tumbleweed respectivamente.

Lo primero de todo, por supuesto es descargar la imagen de openSUSE desde este enlace:

Una vez descargado el archivo raw.xz , hay que crear una tarjeta microSD autoarrancable desde la que arrancar el sistema. Puedes utilizar las herramientas del sistema para “quemar” la imagen en la tarjeta microSD.

O puedes utilizar Etcher lo que hace el proceso más seguro. Simplemente tienes descargarte el programa de código abierto desde el sitio oficial, extraer el fichero .zip y hacer ejecutable el archivo .AppImage con este comando:

chmod +x Etcher-x.x.x-linux-x64.AppImage

Hecho eso conecta la tarjeta microSD en tu equipo, ejecuta Etcher y selecciona el archivo raw.xz que has descargado de openSUSE e inicia el proceso con Flash!

Terminado el proceso de grabar la microSD con openSUSE, enchúfala a la Raspberry Pi y arranca la máquina. Durante el primer inicio, openSUSE automáticamente instalará el sistema y hará uso de todo el espacio libre de la tarjeta.

Durante el proceso verás el siguiente mensaje:

GPT data structures destroyed! You may now partition the disk using 
fdisk or other utilities

No te preocupes ni sufras, todavía. Espera un minuto o dos y openSUSE continuará arrancando normalmente. Cuando acabe el proceso inicia la sesión como root y contraseña linux.

Ya que openSUSE viene ya configurado con el protocolo SSH, puedes arrancar en tu Raspberry Pi sin necesidad de tener un monitor. En ese caso tendrás que conectar tu Raspberry a la red mediante Ethernet.

Dale tiempo al sistema a que

Como instalar o Carnê Leão no Linux manualmente

Se você está com dificuldade para instalar o Carnê Leão no Linux, veja como fazer isso de um jeito simples, prático e que funciona em qualquer distribuição Linux.

Leia o restante do texto "Como instalar o Carnê Leão no Linux manualmente"

14 February, 2017


Uma nova revisão do que aconteceu esta semana em openSUSE Tumbleweed a versão “rolling release” de atualização contínua da distribuição de GNU/Linux openSUSE.

O anúncio original você pode ler no blog de Dominique Leuenberger, no link abaixo:

Esta semana, conseguimos obter 7 snapshots - vou rever os snapshots {0203 até o 0209}.

Então, vamos ver o que esses snapshots trouxeram:

  • GStreamer 1.10.3 / GStreamer 0.10 é definitivamente removido
  • Network Manager 1.6.0
  • Linux Kernel 4.9.8
  • GCC 6.3.1

E como de costume, há um monte de itens sendo preparados para você, como por exemplo:
  • KDE Plasma 5.9.1 (snapshot 0210+)
  • Aplicações do KDE 16.12.2
  • RPM 4.13.0 - ainda alguns pacotes precisam de amor
  • Glibc 2.25 - também precisa da sua ajuda
  • Libreoffice 5.3: falha o conjunto de teste interno em ppc64le
  • Linux Kernel 4.9.9

Se você quiser descobrir onde você pode ajudar nas várias áreas de preparação, você pode sempre olhar para as falhas listadas no painel que você pode encontrar em:

As ISO’s são instáveis, porém se você já utiliza openSUSE Tumbleweed em seu equipamento, simplesmente deverá atualizá-lo mediante o comando “zypper up” assim seu sistema receberá as atualizações.Para realizar o download acesse o link abaixo:


Mantenha-se atualizado e você sabe: Divirta-se!

Michael Meeks: 2017-02-14 Tuesday.

21:00 UTCmember

  • Nice set of Valentines Day cards for the whole family; dug away at drear contract review much of the day.
  • Watched and fast-forwarded some James Bond for H. and N. in the evening. Hacked until late on improved non-blocking socket code.

Como instalar a última versão do Blender no Linux

Se você já trabalha com 3d ou quer apenas experimentar o programa, veja aqui instalar a última versão do Blender no Linux.

Leia o restante do texto "Como instalar a última versão do Blender no Linux"


Boletín de noticias relacionadas con el software libre publicado por la Free Software Foundation.

La Fundación para el Software Libre o Free Software Foundation (FSF) es una organización creada en Octubre de 1985 por Richard Stallman y otros entusiastas del software libre con el propósito de difundir este movimiento.

La Fundación para el software libre (FSF) se dedica a eliminar las restricciones sobre la copia, redistribución, entendimiento, y modificación de programas de computadoras. Con este objeto, promociona el desarrollo y uso del software libre en todas las áreas de la computación, pero muy particularmente, ayudando a desarrollar el sistema operativo GNU.

Además de tratar de difundir la filosofía del software libre, y de crear licencias que permitan la difusión de obras y conservando los derechos de autorías, también llevan a cabo diversas campañas de concienciación y para proteger derechos de los usuarios frentes a aquellos que quieren poner restricciones abusivas en cuestiones tecnológicas.

Mensualmente publican un boletín (supporter) con noticias relacionadas con sus campañas, o eventos. Una forma de difundir sus proyectos, para que la gente conozca los hechos, se haga su propia opinión, y tomen partido si creen que la reivindicación es justa!!

Puedes ver todos los números publicados en este enlace: http://www.fsf.org/free-software-supporter/free-software-supporter

Un pequeño equipo de entusiastas traducimos mensualmente este boletín para que esté disponible en castellano. Tratamos de hacerlo lo mejor que podemos pero no estamos exentos de cometer errores.

¿Te gustaría aportar tu ayuda y ayudarnos en la traducción? Lee el siguiente enlace:

Aquí te traigo un extracto de algunas de las noticias que ha destacado la FSF este mes de febrero de 2017, pero puedes leer el boletín completo en español en este enlace:

.- La computación está cambiando, también la Lista de Proyectos de Altas Prioridades de la FSF

Del 17 de enero

Como respuesta al panorama cambiante de la computación, y con una amplia ayuda de la comunidad de software libre, la Free Software Foundation ha actualizado su Lista de Proyectos de Software Libre de Alta Prioridad con seis nuevas áreas de proyectos que necesitan de tu ayuda.

.- El discurso de Sumana Harihareswara cerrará la LibrePlanet 2017

Del 27 de enero

Sumana Harihareswara será la oradora principal en LibrePlanet, la conferencia anual de software libre, el domingo 26 de marzo de 2017. Harihareswara es una oradora veterana, que ha dado charlas en el Open Source Bridge, code4lib y Wiki Conference USA.

Ha dado numerosas conferencias sobre gran variedad de temas, incluyendo PyCon y LibrePlanet, donde, en 2016, habló sobre la rareza no-esencial del software libre. Sus monologos cómicos se


Le samedi 25 Février 2017, nous organisons notre Journée Mensuelle du Logiciel Libre à la Maison St Sever à Rouen (Centre Commercial St Sever, 10-12 rue Saint-Julien 76100 Rouen) de 14h00 à 18h00. Rouen, Normandie. On fera connaissance avec la toute dernière version de openSUSE, la openSUSE Leap 42.2, Gnome 3.16.2, LibreOffice et beaucoup d’autres distributions […]

13 February, 2017

Michael Meeks: 2017-02-13 Monday.

21:00 UTCmember

  • Up lateish; babes on half term holiday - team meetings; E-mail, code review with Ash. E-mail deluge, board call, chase Cyber Essentials certification; dinner, more paperwork.


openSUSE Tumbleweed es una distribución “Rolling Release” en desarrollo continuo. Aquí puedes estar al tanto de las últimas novedades.

Empieza una nueva semana, pero antes echemos un vistazo a lo sucedido la semana anterios en openSUSE Tumbleweed la versión “rolling release” o de actualización continua de la distribución de GNU/Linux openSUSE.

El anuncio original lo puedes leer en el blog de Dominique Leuenberger, en este enlace:

Las ISO’s son instalables, pero si ya estás disfrutando de openSUSE Tumbleweed en tu equipo, simplemente deberás actualizarlo mediante “zypper up” o este otro comando que recomiendan en las listas de correo, para disfrutar de esas actualizaciones.

Esta semana ha habido 7 nuevas “snapshots” publicadas desde la 0203 hasta la 0209 con interesantes actualizaciones entre las que destaco por su importancia las siguientes:

  • GStreamer 1.10.3 / GStreamer 0.10 ha sido definitivamente eliminado.
  • Network Manager 1.6.0
  • Linux Kernel 4.9.8
  • GCC 6.3.1

Y como es normal, también hay muchas cosas interesantes que estarán disponibles próximamente. Por ejemplo:

  • KDE Plasma 5.9.1 (diponible en “snapshot” 0210+)
  • KDE Applications 16.12.2
  • RPM 4.13.0
  • glibc 2.25
  • Libreoffice 5.3
  • Linux Kernel 4.9.9

Si quieres estar a la última con software actualizado y probado utiliza openSUSE Tumbleweed la opción rolling release de la distribución de GNU/Linux openSUSE.

Mantente actualizado y ya sabes: Have a lot of fun!!

Enlaces de interés



O site principal do KDE, o www.kde.org, ganhou um novo e bonito projeto desenvolvido por Ken Vermette.

No dia 11 de fevereiro Jonathan Riddell anunciou um novo design para o site KDE Org. O membro do Visual Design Group, Ken Vermette, trabalhou silenciosamente com as principais partes interessadas para criar um novo projeto e também para atualizar o conteúdo. 

O novo site usa HTML5 e é responsivo ao trabalho em celulares e tablets. Ele inclui uma introdução aos produtos, a comunidade e como as pessoas podem se envolver.

O escopo dos projetos do KDE continua a crescer à medida que evoluímos do ambiente de desktop original para se tornar uma organização de guarda-chuva que hospeda projetos tão diversos como a colaboração de livros didáticos acadêmicos do WikiToLearn ou o site de distribuição de conteúdo do KDE Store. O novo site reflete essa mudança de direção, enquanto ainda se concentra em nosso desktop Plasma.

Este novo design foi aplicado  apenas para as primeiras páginas, outras páginas no kde.org ainda utilizam o tema antigo, mas estas serão transicionadas nas próximas semanas. Muitos outros sites sob o kde.org são esperados e encorajados a adotar o novo tema.

Maiores informações no anuncio original:

Mantenha-se atualizado e você sabe: Divirta-se!


Soon it will be a decade since we started the RadeonHD driver, where we pushed ATI to a point of no return, got a proper C coded graphics driver and freely accessible documentation out. We all know just what happened to this in the end, and i will make a rather complete write-up spanning multiple blog entries over the following months. But while i was digging out backed up home directories for information, i came across this...

It is a copy of the content of an email i sent to an executive manager at SuSE/Novell, a textfile called bridgmans_games.txt. This was written in July 2008, after the RadeonHD project gained what was called "Executive oversight". After the executive had first hand seen several of John Bridgmans games, he asked me to provide him with a timeline of some of the games he played with us. The below explanation covers only things that i knew that this executive was not aware of, and it covers a year of RadeonHD development^Wstruggle, from July 2007 until april 2007. It took me quite a while to compile this, and it was a pretty tough task mentally, as it finally showed, unequivocally, just how we had been played all along. After this email was read by this executive, he and my department lead took me to lunch and told me to let this die out slowly, and to not make a fuss. Apparently, I should've counted myself lucky to see these sort of games being played this early on in my career.

This is the raw copy, and only the names of some people, who are not in the public eye have been redacted out (you know who you are), some other names were clarified. All changes are marked with [].

These are:
SuSE Executive manager: [EXEC]
SuSE technical project manager: [TPM]
AMD manager (from a different department than ATI): [AMDMAN]
AMD liaison: [SANTA] (as he was the one who handed me and Egbert Eich a 1 cubic meter box full of graphics cards ;))

[EXEC], i made a rather extensive write-up about the goings-on throughout 
the whole project. I hope this will not intrude too much on your time, 
please have a quick read through it, mark what you think is significant and 
where you need actual facts (like emails that were sent around...) Of 
course, this is all very subjective, but for most of this emails can be 
provided to back things up (some things were said on the weekly technical 
call only).

First some things that happened beforehand...

Before we came around with the radeonhd driver, there were two projects 

One was Dave Airlie who claimed he had a working driver for ATI Radeon R500
hardware. This was something he wrote during 2006, from information under 
NDA, and this nda didn't allow publication. He spent a lot of time bashing 
ATI for it, but the code was never seen, even when the NDA was partially 
lifted later 


Small Messaging Service, or SMS, is a very common and popular way to communicate today. It is a convenient way to transmit a short message. It has seemingly evolved into a way to carry on conversations throughout the day… but it is so 2007... 

I don't actually have a problem with the Small Message Service in itself. I think it is a fine service but I do have some issues with it: 

One, I don't have a great way of using my computer to utilize SMS from my phone. There are some 3rd party services, some are free, some are not. MySMS.com is a service I do use but it often lags as of late. I can use a remote desktop service like TeamViewer to control my phone and have the full keyboard. KDE Connect is close to being able to do it but is just not quite there. 

Two, I would prefer to have some way of messaging seamlessly from the computer or the mobile device without relying on the phone itself. Utilizing any of aforementioned services, you don't have access to the full message history. With MySMS, if I send a message from that web interface from the computer, I can't see what I sent on the phone. The SMS service will not function unless the phone has an active internet and cell service connection. Internet alone will not work. I have been in many situations were I have an active Internet connection but have no cell service available. 

Three, SMS is, well, small, you can't send larger files to include pictures or audio clips. It is VERY limited and I have yet to have one of those, “Attachement not received, tap to download” or something like that actually work.

Lastly, I have chosen to use Ting for my mobile service provider, a pay-per-use type of service, I am charged per SMS, albeit a very small amount and there is no way I am going to spend more there than what I had been paying with a contract-type-of-service but my goal would be to use less of that service and instead use all the unlimited WiFi that I have access to throughout the day at work or at home. Squeeze that dollar as much as possible.

Google HangoutsOne solution I have been using has been the Google Hangouts messaging service, it works very well, and I do like it. I mostly like the Google ecosystem but I am starting to lose confidence in Google. Another solution for messaging has been Facebook Messager but I don't use that one voluntarily anymore. I REALLY don’t trust Facebook at all. I know that neither Google or Facebook are not shy about mining my data for advertising purposes. As much as I like Google and their services or tolerate Facebook, I don't necessarily want either publicly traded company to have all aspects of my communication. 

Why I am using Telegram

Besides my primary reason

12 February, 2017

Michael Meeks: 2017-02-12 Sunday.

21:00 UTCmember

  • Overslept vigorously, to the stable for NCC; Claire explained Ephesians 1 well - helpful; back foor lunch. Off to pick up littlies but too late for the service. Lots of stories. Played with them in the afternoon; stories, bed.

<- Current blog entries