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.

30 August, 2016


Go 1.7 was released earlier this month, and the thing I’m most excited about is the incorporation of the context package into the Go standard library. Previously it lived in the golang.org/x/net/context package.

With the move, other packages within the standard library can now use it. The net package’s Dialer and os/exec package’s Command can now utilize contexts for easy cancelation. More on this can be found in the Go 1.7 release notes.

Go 1.7 also brings contexts to the net/http package’s Request type for both HTTP clients and servers. Last year I wrote a post about using context.Context with http.Handler when it lived outside the standard library, but Go 1.7 makes things much simpler and thankfully renders all of the approaches from that post obsolete.

A quick recap

I suggest reading my original post for more background, but one of the main uses of context.Context is to pass around request-scoped data. Things like request IDs, authenticated user information, and other data useful for handlers and middleware to examine in the scope of a single HTTP request.

In that post I examined three different approaches for incorporating context into requests. Since contexts are now attached to http.Request values, this is no longer necessary. As long as you’re willing to require at least Go 1.7, it’s now possible to use the standard http.Handler interface and common middleware patterns with context.Context!

The new approach

Recall that the http.Handler interface is defined as:

type Handler interface {
        ServeHTTP(ResponseWriter, *Request)

Go 1.7 adds new context-related methods on the *http.Request type.

func (r *Request) Context() context.Context
func (r *Request) WithContext(ctx context.Context) *Request

The Context method returns the current context associated with the request. The WithContext method creates a new Request value with the provided context.

Suppose we want each request to have an associated ID, pulling it from the X-Request-ID HTTP header if present, and generating it if not. We might implement the context functions like this:

type key int
const requestIDKey key = 0

func newContextWithRequestID(ctx context.Context, req *http.Request) context.Context {
    reqID := req.Header.Get("X-Request-ID")
    if reqID == "" {
        reqID = generateRandomID()

    return context.WithValue(ctx, requestIDKey, reqID)

func requestIDFromContext(ctx context.Context) string {
    return ctx.Value(requestIDKey).(string)

We can implement middleware that derives a new context with a request ID, create a new Request value from it, and pass it onto the next handler in the chain.

func middleware(next http.Handler) http.Handler {
    return http.HandlerFunc(func(rw http.ResponseWriter, req *http.Request) {
        ctx := newContextWithRequestID(req.Context(), req)
        next.ServeHTTP(rw, req.WithContext(ctx))

The final handler and any middleware lower in the chain have access to all the previously request-scoped data set in middleware above it.

func handler(rw http.ResponseWriter, req *http.Request) {
    reqID := requestIDFromContext(req.Context())
    fmt.Fprintf(rw, "Hello request ID %v\n", reqID)

And that’s it


The approaches in this post are now obsolete thanks to Go 1.7, which adds the context package to the standard library and uses it in the net/http *http.Request type. The background info here may still be helpful, but I wrote a follow-up post that revisits things for Go 1.7 and beyond.

A summary of this post is available in Japanese thanks to @craftgear. こちら@craftgearによる日本語の要約があります。

The golang.org/x/net/context package (hereafter referred as net/context although it’s not yet in the standard library) is a wonderful tool for the Go programmer’s toolkit. The blog post that introduced it shows how useful it is when dealing with external services and the need to cancel requests, set deadlines, and send along request-scoped key/value data.

The request-scoped key/value data also makes it very appealing as a means of passing data around through middleware and handlers in Go web servers. Most Go web frameworks have their own concept of context, although none yet use net/context directly.

Questions about using net/context for this kind of server-side context keep popping up on the /r/golang subreddit and the Gopher’s Slack community. Having recently ported a fairly large API surface from Martini to http.ServeMux and net/context, I hope this post can answer those questions.

About http.Handler

The basic unit in Go’s HTTP server is its http.Handler interface, which is defined as:

type Handler interface {
        ServeHTTP(ResponseWriter, *Request)

http.ResponseWriter is another simple interface and http.Request is a struct that contains data corresponding to the HTTP request, things like URL, headers, body if any, etc.

Notably, there’s no way to pass anything like a context.Context here.

About context.Context

Much more detail about contexts can be found in the introductory blog post, but the main aspect I want to call attention to in this post is that contexts are derived from other contexts. Context values become arranged as a tree, and you only have access to values set on your context or one of its ancestor nodes.

For example, let’s take context.Background() as the root of the tree, and derive a new context by attaching the content of the X-Request-ID HTTP header.

type key int
const requestIDKey key = 0

func newContextWithRequestID(ctx context.Context, req *http.Request) context.Context {
    return context.WithValue(ctx, requestIDKey, req.Header.Get("X-Request-ID"))

func requestIDFromContext(ctx context.Context) string {
    return ctx.Value(requestIDKey).(string)

ctx := context.Background()
ctx = newContextWithRequestID(ctx, req)

This derived context is the one we would then pass to the next layer of the system. Perhaps that would create its own contexts with values, deadlines, or timeouts, or it could extract values we previously stored.


These approaches are now obsolete as of Go 1.7. Read my follow-up post that revisits this topic for Go 1.7 and beyond.

So, without direct support for net/context in the standard library, we have to find another way to

29 August, 2016


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


Una nueva revisión de lo que ha acontecido estas semanas 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” para disfrutar de esas actualizaciones.

Como siempre, echemos un vistazo a las novedades de las ISOs 0818, 0820 y 0822 publicadas esta semana pasada, entre las que podremos encontrar:

  • GNOME Maps
  • Un montón de mejoras y actualizaciones en YaST. La herramienta por excelencia de openSUSE.
  • Kernel Firmware 20160804
  • Skanlite 2.0 – ya portado a KDE Framework 5
  • Linux Kernel 4.7.1
  • GCC 6.2 RC1

Actualización del kernel, actualización del compilador, y muchas más cosas. También se está tratando de que en el GRUB muestre el contenido de /etc/os-release para que quede más integrado.

Como siempre, echemos un vistazo a lo que ya se está preparando y que pronto podremos disfritar.:

  • GCC 6.2
  • ModemManager 1.6.0
  • Linux Kernel 4.7.2 – Las actualizaciones del kernel no se detienen
  • KDE Applications 16.08.0
  • KDE Framework 5.25.0
  • Plasma 5.7.4

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

Enlaces de interés



Now that Nextcloud 9 is out, many users are already interested in migration so I'd like to address the why and how in this blog post.

Edit: Nextcloud 10 is out with loads of unique features. We now also have a client! You can find out about client account migration here.

Why migrate

Let's start with the why. First, you don't have to migrate yet. This release as well as at least the upcoming releases of own- and Nextcloud will be compatible so you'll be able to migrate between them in the future. We don't want to break compatibility if we can avoid it!

Of course, right now Nextcloud 9 has some extra features and fixes and future releases will introduce other capabilities. With regards to security, we have Lukas Reschke working for us. However, we promise that for the foreseeable future we will continue to report all security issues we find to upstream in advance of any release we do. That means well ahead of our usual public disclosure policy, so security doesn't have to be a reason for people to move.

EditNextcloud 10 comes with far more features on top of this. For Nextcloud 11 we have a ambitious road map already but we'll still enable migration from ownCloud 9.1 to Nextcloud 11 so you can migrate at your leisure!

Migration overview

If you've decided to migrate there are a number of steps to go through:
  • Make sure you have everything set up properly and do a backup
  • Move the old ownCloud install, preserving data and config
  • Extract Nextcloud, correct permissions and put back data and config
  • Switch data and config
  • Trigger the update via command line or the web UI
Note that we don't offer packages. This has been just too problematic in the past and while we might offer some for enterprise distributions, we hope to work together with distributions to create packages for Nextcloud 9 and newer releases. Once that is done we will of course link to those on our installation page.

There are other great resources besides this blog, especially this awesome post on our forums which gives a great and even more detailed overview of a migration with an Ubuntu/NGINX/PHP7/MariaDB setup.

Edit: With regard to packages, there are now packages for CentOS and Fedora and other distributions will likely follow soon. See our packages repository if you want to help!


First, let's check if you're set up properly. Make sure:
  • You are on ownCloud 8.2.3 or later
  • Make sure you have all dependencies
  • Your favorite apps are compatible (with ownCloud 9), you can check this by visiting the app store at apps.owncloud.com
  • You made a backup
Once that's all done, time to move to the next step: cleaning out the old files.

Removing old files

In this step, we'll move the existing installation preserving the data and configuration.
  • Put


As the Silk Road case winds down, Ars Technica posted a great article (seriously, read it) summarizing one of the most interesting aspects of the entire case.

It is the story of how two corrupt officers in the DEA and Secret Service attempted to use the Silk Road investigations to illegally profit from and abuse the authority entrusted to them. After reading the article above I became interested in the case and decided to read the criminal complaint filing. Within it there were lots of interesting explanations of how the investigators were tipped off on the possibility of the corrupt activity as well as how they were able to produce the necessary evidence for the case.



The two corrupt officers referenced in the filing were a Carl Force and Shaun Bridges. The two were not cooperating with each other during the relevant time. When interviewed Bridges also stated that he did not know Force well and that they only worked together on the Silk Road case.

Force was a 15 year veteran of the Drug Enforcement Agency (DEA), during the timeframe of the investigation, Force was the only member of his family who was receiving income as his wife was a homemaker. This fact proves to be important during the investigation when tracing Force’s income.

Bridges was a computer forensics expert working for the Secret Service. He became a suspect after the Feds gained full access to Silk Road through the capture of C.G. (Curtis Green), a Silk Road admin, a very large theft took place on Silk Road.


Bitcoin is a digital currency that records all transactions on distributed public ledger called the block chain. The block chain is updated six times an hour with every transaction and balance for each Bitcoin address. While Bitcoin is used to move money anonymously, it is possible (demonstrated later on) to trace financial transactions on the block chain.

Carl Force, A Man Of 3 Faces

Force was employed by the DEA to investigate and determine the identity of DPR. Force regularly interacted with DPR using the identity of ‘Nob’. He and DPR would communicate using PGP to encrypt their messages. Force was expected to provide all decrypted versions of the messages in his reports of the investigation. However since PGP requires the use of a private key to decrypt messages, Force never provided the key in his reports. The criminal complaint states that Force was repeatedly told the importance of providing all communications by the prosecutor. This seems to suggest that Force knowingly did not want to let the DEA see all the messages he exchanged with DPR and is proven when messages that Force never reported were discovered.


Force noted that while acting under the Nob identity, he advised DPR that his ‘friend Kevin’ wanted a ‘donation’ of bitcoins for insider information of the Silk Road investigation. He claims that he provided DPR with a Bitcoin address but made a note that no payment was

27 August, 2016

Sebastian Kügler: facelift

23:47 UTC


I’ve done a facelift to my website. The new version is more mobile-friendly, modern-looking and quite a departure visually from its original look. I’ve chosen for a newpaper-like, typography-based responsive layout. My site finally also supports SSL, thanks to let’s encrypt.

Going to Akademy
Next week, I’ll be going to Akademy, which is co-hosted with QtCon. As usual, my focus will be around Plasma-related topics. I’ll also hold a presentation about a KDE software store.


KDE Connect es la aplicación “mágica” que hacen que tu teléfono inteligente y tu escritorio Plasma se comuniquen e interactuen.


Ayer 26 de agosto de 2016 se publicó oficialmente la primera versión estable de KDE Connect. Esta versión es la más sólida y estable de todas las publicadas.

No en vano ha estado en desarrollo durante 1 año, y tiene detrás un gran trabajo no sólo de Albert Vaka, que es su desarrollador, también de una gran comunidad como KDE y de muchos aportes de desarrolladores que han hecho de esta aplicación una verdadera joya imprescindible.

Puedes leer el anuncio oficial en inglés en la página oficial del desarrollador del programa Albert Vaka:

Además de mejoras, y estabilidad esta primera versión tiene disponibles un gran número de nuevas funcionalidades que lo hacen todavía más apetitoso, entre estas novedades encontramos:

  • Comandos ya preconfigurados, al estilo de “lanzadores” o accesos directos que lo hacen más productivo y rápido a la hora de realizar las tareas más comunes.
  • Puedes responder directamente a SMS desde tu escritorio. Una de las características más esperadas, ya que cuando recibes una notificación de un mensaje de texto en tu escritorio, un botón de “Responder” te permitirá responder al mensaje sin necesidad de utilizar tu teléfono. ¿Mágia? ¡No, simplemente software libre! Por cierto, para disfrutar de esto necesitarás la versión 1.4 de la aplicación Android, ya disponible.
  • Recibe en tu teléfono las notificaciones de tu escritorio. Esta funcionalidad está deshabilitada por defecto, ya que puede llegar a incomodar un poco. Deberás habilitarla tanto en la aplicación de Android como en los Ajustes del Sistema, y podrás escoger qué notificaciones notificar al teléfono y cuales no.
  • KDE Connect gana en un cifrado más robusto, cambiando del método RSA a TLS. Esto además de proteger la comunicación entre ambos dispositivos también mejora la rapidez y consumo de batería que es menor.

Todo esto y mucho más está ya disponible. Pronto las distintas distribuciones que ofrezcan KDE Connect deberían tener disponible entre los repositorios esta nueva versión. Y también puedes compilartela tu mismo desde los archivos fuentes disponibles en download.kde.org.

Aunque la versión nueva para Android es compatible con las versiones anteriores de KDE Connect, la versión de escritorio necesita la versión 1.0 de la aplicación de Android.

Para descargar esta aplicación para tu teléfono con Android lo puedes hacer desde F-Droid o Play Store.

Sin duda este gran programa hace que tu escritorio Plasma y tu teléfono Android se comuniquen y se integren como ninguna otra aplicación y sistema lo hace. Este gran software es una delicia de la que espero poder probar pronto


Dear Tumbleweed users and hackers,

Time seems to be flying, it feels like I only just wrote review of week 33 and now week 34 is already over again. A perfect moment to look back what the three snapshots (0818, 0820 and 0822) offered us.

  • GNOME Maps – New Map provider
  • A lot of YaST updates
  • Kernel Firmware 20160804
  • Skanlite 2.0 – ported to KDE Framework 5
  • Linux Kernel 4.7.1
  • GCC 6.2 RC1

Quite the list, updated kernel, updated compiler. One snapshot had been discarded this week: we are trying to align the usage of /etc/os-release which resulted in Tumbleweeds snapshot version to be shown in GRUB.

What will be coming your way soon:

  • GCC 6.2
  • ModemManager 1.6.0 – I know some of you are waiting for it
  • Linux Kernel 4.7.2 – Upstream is fast, so are we
  • Pattern changes: The ‘Minimal Server Selection’ was removed from the installer. It was basically identical to the ‘Server (Text Mode)’ entry
  • KDE Applications 16.08.0
  • KDE Framework 5.25.0
  • Plasma 5.7.4

Have a great time!

26 August, 2016


La próxima openSUSE Leap 42.2 incluirá el escritorio Plasma 5.8.1 que será de soporte extendido o LTS.


openSUSE Leap 42.2 retrasará un par de semanas la publicación de su versión final para poder incluir Plasma 5.8.1 como entorno de escritorio.

Como habréis leido hace tiempo en KDE Blog, Plasma 5.8 será LTS es decir, tendrá soporte extendido. Por lo que los desarrolladores de KDE corregirán y solucionarán problemas de esta versión durante más tiempo. Y hace unos días la gente de KDE ha anunciado que adelantará la publicación de Plasma 5.8 un par de semanas. 

Esta nueva fecha de lanzamiento de Plasma 5.8 viene como anillo al dedo para openSUSE Leap 42.2 que podrá incluir esta versión LTS del escritorio en su próximo lanzamiento de la versión estable prevista en noviembre.

Ayer se anunció en las listas de correo, que la publicación final de openSUSE Leap 42.2 se retrasará un par de semanas para poder incluir no la 5.8.0, si no la 5.8.1 que estará más pulida y se habrán corregido ya muchos errores de la versión anterior. Puedes leer el anuncio en este enlace:

Para adaptarse a este nuevo movimiento tanto de KDE como de openSUSE el calendario de lanzamientos de la versión Leap 42.2 de este último, sufre modificaciones y se realizarán los siguientes cambios de fecha:

  • La “Release Candidate” 1 o RC1 pasará a llamarse Beta 3 y se publicará el 6 de octubre.
  • La nueva RC1 se publicará el 10 de octubre
  • La RC2 se publicará el 2 de noviembre
  • La “Golden Master” o GM se publicará el 10 de noviembre
  • Y la versión final se publicará el 16 de noviembre

En este nuevo movimiento de fechas (y creo que en la petición de crear una versión LTS de Plasma) ha tenido mucho que ver SUSE, lo que le favorece a la hora de ofrecer este escritorio en su sistemas operativos, y de paso también favorece a los que somos usuarios de openSUSE y de este entorno de escritorio.



25 August, 2016


El 25 de agosto de 1991 era anunciado timidamente al mundo un proyecto personal de un estudiante llamado Linus Torvalds, ese proyecto era el kernel Linux.


Si hace unos años celebré en el blog el 30 aniversario del sistema GNU, hoy no quería dejar pasar la fecha, y aunque seguro que lo has leido hasta la saciedad, hoy también quería unirme a la celebración de los 25 años del kernel Linux. La combinación de ambos hacen que podamos disfrutar de nuestras distribuciones de GNU/Linux.

Y quería hacerlo compartiendo una infografía que la gente de SUSE ha creado con motivo del evento. En esta infografía se comparan los datos de Linux en estos 25 años de diferencia. Y entre esos datos curiosos leemos:

  • Hace 25 años el código de Linux ocupaba 14 disquetes (alguien los recuerda). Hoy ocuparían 556
  • Hace 25 Linux lo usaba 1 persona, hoy son 86 millones.
  • En 1994 el código tenía 150.000 líneas de código, hoy llegan a los 19.5 millones de líneas de código.
  • Hace 25 años sólo estaba disponible para una aruqitectura de equipos concreta, hoy soporta más de 25 tipos de arquitectura.
  • El costo del desarrollo de Linux hace 25 años fue un PC 386 y un par de hamburguesas, hoy costaría más de 3 billones de dólares.
  • En 1998 sólo había 1 supercomputador que usara Linux, hoy es el 95% de las supercomputadoras las que lo usan.
  • En 2002 había 96 distribuciones de GNU/Linux hoy son más de 278

Puedes consultar la infografía realizada por SUSE en este enlace:

¿Te consideras un genio de GNU/Linux? Pues demuéstralo en este concurso que han creado la gente de SUSE:

Si quieres conocer a la gente que está detrás del código te invito a que leas estas 30 entrevistas a 30 desarrolladores y desarrolladoras de Linux que traduje hace unos años en el blog:

Y ahora toca cantar…



Cliquez sur l'image pour l'afficher en taille normale

Nom : 500px-KDE_logo.svg.png 
Affichages : 687 
Taille : 166.8 Ko 
ID : 3471

Une nouvelle qui pourra en intéresser plus d'un : il se pourrait bien qu'openSUSE Leap 42.2, la nouvelle version d'openSUSE


Vídeos do YouTube: como instalar o Minitube no Linux

Foi lançada mais uma versão do cliente YouTube Minitube. Se você quiser experimentar essa versão e assistir vídeos do YouTube, veja abaixo como instalar ela no Ubuntu, OpenSUSE, Arch Linux, Manjaro e sistemas derivados.

Leia o restante do texto "Vídeos do YouTube: como instalar o Minitube no Linux"

Este texto saiu primeiro em Vídeos do YouTube: como instalar o Minitube no Linux

With the EU (in this case France and Germany) gearing up for another attack on privacy I'm quite happy and proud to have been part of the release of Nextcloud 10!


It is the usual story: we should disallow companies from using perfect end to end encryption and force them to insert backdoors against terrorists.

Not that it would help - that's been discussed extensively already but in short:
  • If you have nothing to hide, you'll use a backdoored app and you're vulnerable to foreign (and your own) governments, terrorists (!), criminals and others who can abuse your data in more ways than you can imagine.
  • If you have something to hide, you can use 1000 different tools to do so and there is nothing government can do about that so you won't use a backdoored app.
  • And note that government has failed to even use fully unencrypted information to stop terrorist attacks so perhaps we should first see if they can actually get their act together there.
Now yes, backdooring all commonly used encryption apps will help a BIT, essentially only with the low level, common crime. So you might catch the dude who broke into your house and bragged about it to his friends over Whatsapp. You won't catch the terrorists plotting with Al Qaida (or whatever the terrorist organization du-jour) to blow up a train because they can simply get one of the many solutions out there to protect themselves.

Nor will you catch corrupt politicians or big companies doing nasty stuff, though I am quite certain the laws will be written in such a way that you can use them to go after people who actually try to expose such politicians or companies.

And I'm also quite certain companies will use this as an excuse to not implement proper protection in their products so you can continue to stop pacemakers remotely or disable the brakes in cars over the internet.

Generally, laws targeting encryption and terrorism do more to harm whistleblowing than terrorism and are thus promoting corruption and bad, unsecure products.

These laws will literally cost lives. Not save any.

And it is exactly why Frank started ownCloud and why we continue to develop that vision at Nextcloud. And keep developing new features, like the File Access Control app which can provide an extra protective layer around your data. I for one certainly can use that app and exactly in the way described in that blog! So much for 'enterprise only features'.

Get it and migrate today. You and your data deserve it!

24 August, 2016


Plasma 5.8 will be our first long-term supported release in the Plasma 5 series. We want to make this a release as polished and stable as possible. One area we weren’t quite happy with was our multi-screen user experience. While it works quite well for most of our users, there were a number of problems which made our multi-screen support sub-par.
Let’s take a step back to define what we’re talking about.

Multi-screen support means that connecting more than one screen to your computer. The following use cases give good examples of the scope:

  • Static workstation A desktop computer with more than one display connected, the desktop typically spans both screens to give more screen real estate.
  • Docking station A laptop computer that is hooked up to a docking station with additional displays connected. This is a more interesting case, since different configurations may be picked depending on whether the laptop’s lid is closed or not, and how the user switches between displays.
  • Projector The computer is connected to a projector or TV.

The idea is that the user plugs in or starts up with that configuration, if the user has already configured this hardware combination, this setup is restored. Otherwise, a reasonable guess is done to put the user to a good starting point to fine-tune the setup.

This is the job of KScreen. At a technical level, kscreen consists of three parts:

  • system settings module This can be reached through system settings
  • kscreen daemon Run in a background process, this component saves, restores and creates initial screen configurations.
  • libkscreen This is the library providing the screen setup reading and writing API. It has backends for X11, Wayland, and others that allow to talk to the exact same programming interface, independent of the display server in use.

At an architectural level, this is a sound design: the roles are clearly separated, the low-level bits are suitably abstracted to allow re-use of code, the API presents what matters to the user, implementation details are hidden. Most importantly, aside from a few bugs, it works as expected, and in principle, there’s no reason why it shouldn’t.

So much for the theory. In reality, we’re dealing with a huge amount of complexity. There are hardware events such as suspending, waking up with different configurations, the laptop’s lid may be closed or opened (and when that’s done, we don’t even get an event that it closed, displays come and go, depending on their connection, the same piece of hardware might support completely different resolutions, hardware comes with broken EDID information, display connectors come and go, so do display controllers (crtcs); and on top of all that: the only way we get to know what actually works in reality for the user is the “throw stuff against the wall and observe what sticks” tactic.

This is the fabric of nightmares. Since I prefer to not sleep, but hack at night, I seemed to


openSUSE Tumbleweed had another abundant week of snapshots.

Four Tumbleweed snapshots were released since the last article and the snapshot of the week, 20160816, brought users a new version of gtk3 (3.20.8). Updated in the repositories for this snapshot was an updated version of yast2-auth-client (3.3.10). Cairo graphics fixed several bugs and Apache2 removed the omc xml config because the change log states it is “useless nowdays.”

Snapshot 20160817 has several updates for the scalable storage platform ceph, which added an ability to reduce the constraints on resources required to build ceph and ceph-test packages. Git updated to version 2.9.3 and glib2 had several subpackages updated as did gnome-desktop. This snapshot caused quite a bit of chatter on the openSUSE Factory mailing list and serves as a reminder for people using openSUSE Tumbleweed to subscribed to the mailing list so they are aware of the updates.

The most appealing update in snapshot 20160818 was the added subpackages to libreoffice. Other noteworthy updates in the repositories for this snapshot were grub2, libstorage and kernel-firmware version 20160804. Updates in the repositories specific to openSUSE in this snapshot were made to snapper, wicked and yast2.

The Linux Kernel was updated to version 4.7.1 in the 20160820 snapshot along with F Virtual Window Manager2.

KDE applications 16.08.0 and glibc 2.24 are expected to come in a snapshot soon.

Kernel 4.7.2 recently entered a staged testing phase and will hopefully make it into a snapshot by next week. Hopefully it will come sooner, but since it just reached the testing phase, at this point, it is hard to tell how quickly it will arrive in a snapshot.


The submission deadline for Beta 1 for openSUSE Leap 42.2 is tomorrow. Tasks associated with the release of Leap were recently added to https://progress.opensuse.org and an e-mail will soon be sent to people who have expressed their desire help with the release of the distribution.

Anyone who wants to help translate the release of openSUSE Leap 42.2 can email opensuse-translation(at)opensuse.org or sign up for an account and begin translating at https://l10n.opensuse.org.

Anyone who want to help with the release team should contact opensuse-factory(at)opensuse.org and community members are always encouraged to help with the newest release.


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


Una nueva revisión de lo que ha acontecido estas semanas 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” para disfrutar de esas actualizaciones.

Este artículo de revisión de las novedades en openSUSE Tumbleweed suelo publicarlo el lunes de la semana siguiente, pero en este caso llega con un poco de retraso. En todo caso echemos un vistazo a las novedades de la semana pasada.

De nuevo se publicaron 5 “snapshots” 0812, 0813, 0815, 0816 y 0817 y como de costumbre estas trajeron pequeños cambias y grandes actualizaciones. Entre las más importantes destacaré:

  • Mozilla Firefox 48.0
  • KDE Plasma 5.7.3
  • Mozilla NSS 5.24
  • Linux Kernel – con algunas mejorar en cuanto a seguridad
  • PAM Config 0.91

Y entre lo que ya se está preparando y que en esta semanas se irá publicando será:

  • Linux kernel 4.7.1
  • KDE Applications 16.08.0
  • glibc 2.24

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

Enlaces de interés



22 August, 2016


Veamos una manera de consultar el tiempo actual en tu localidad accediendo a los datos que ofrecen aficionados a la meteorología en la web meteoclimatic.

Pincha sobre la imagen para ampliar

El conocer y consultar el tiempo climatológico es una de esas inquietudes que todos tenemos. Saber cómo va a hacer o qué temperatura y demás datos de humedad, presión, precipitaciones, etc hay ahora mismo en tal o cual localidad.

Veamos un pequeño tutorial para añadir en nuestro escritorio Plasma una opción para consultar los datos de nuestra localidad (o de cualquier otro sitio de España) que nos ofrecen aficionados a la meteorología con sus estaciones climatológicas y que los datos que recopilan los ofrecen en la web meteoclimatic.net

Lo primero que debemos hacer es ir a la web en cuestión, donde aficionados a la meteorología con sus estaciones ofrecen los datos que estas recopilan y las ponen a disposición de todos para consultarlos.

Accedemos a la web y buscamos en el mapa o por los menús si existe una estación meteorológica en nuestra ciudad o pueblo, o alguna cercana que queramos consultar.

Yo para el ejemplo busqué una en Madrid, por ejemplo la del barrio de Vallecas (que creo que ya no está disponible… mira tú que puntería). Una vez que accedes a la estación que quieres pinchas sobre el icono de RSS o feeds (el clásico icono naranja) en la parte superior izquierda.

Copias esa dirección. Y después en nuestro escritorio Plasma instalamos (si no lo tenemos ya instalado) el “widget” Simple RSS reader y lo añadimos a nuestro escritorio.

Abrimos los ajustes del “widget” y pegamos en URL la dirección que antes habíamos copiado y que nos había suministrado la web meteoclimatic de la estación que habíamos escogido.

Yo lo tengo para que se actualice cada 900 segundos, pero ya las diferentes opciones serán las que tu prefieras, le buscas una ubicación al “widget” dentro de tu escritorio, y ya tenemos una información precisa de cómo hace en la localidad que hemos escogido.

Claro que muchos podréis decir que abriendo la ventana también puedes ver el tiempo que hace… pero ¿con tanta exactitud?🙂

Meteoclimatic sólo ofrece datos de estaciones meteorológicas de España, por tanto en otros países deberéis investigar si hay webs similares.



20 August, 2016


Diversos amigos reclamaram (principalmente usuários do Sony Xperia) por não conseguirem instalar aplicativos por falta de espaço. A solução é colocar o celular no modo desenvolvedor (varios link na internet de como fazer isto) e executar o comando set-install-location como veremos a seguir:

$ adb shell pm set-install-location 2

Pronto, agora vá em Configurações -> Aplicativos e mova os maiores APP para o SDCard. E a partir deste momento seu aparelho instalará por padrão o novos aplicativos no SDCARD.



Como instalar a versão mais recente do Opera no Linux

Foi lançada mais uma versão do Opera estável e de desenvolvimento para Linux. Se você quiser instalar o Opera no Linux Ubuntu, Debian, Fedora e sistemas derivados, veja aqui como fazer.

Leia o restante do texto "Como instalar a versão mais recente do Opera no Linux"

Este texto saiu primeiro em Como instalar a versão mais recente do Opera no Linux

19 August, 2016


Bonjour à tous,

Afin de préparer au mieux l’arrivée de Leap 42.2 – actuellement en alpha 3, bientôt en beta – mais aussi afin d’enrichir les articles et les news sur Alionet sur le long terme, je recherche deux nouveaux rédacteurs.

Nom : i_want_you_green.png
Affichages : 829
Taille : 102.1 KoCette activité demande à mon sens :

  • de


Dear Tumbleweed users and hackers,

Week 33 brought us again 5 snapshots (0812, 0813, 0815, 0816 and 0817). There were some smaller and bigger updates, as usual.

The noteworthy updates were

  • Mozilla Firefox 48.0
  • KDE Plasma 5.7.3
  • Mozilla NSS 5.24 – Most SSLv2 code disappeared
  • Linux Kernel – some security fixes
  • PAM Config 0.91 – this time without the regression of ‘last time’

And a couple more things are being prepared in staging areads

  • Linux kernel 4.7.1
  • KDE Applications 16.08.0
  • glibc 2.24 – one more package needs to be fixed (openmpi)

Most of those things are likely to reach you during next week.

18 August, 2016


Como instalar o driver Nvidia 370.23 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 o driver Nvidia 370.23 no Linux, ou melhor, em qualquer distribuição Linux suportada por ele.

Leia o restante do texto "Como instalar o driver Nvidia 370.23 no Linux"

Este texto saiu primeiro em Como instalar o driver Nvidia 370.23 no Linux


Tor no Linux: veja como instalar manualmente

Se você precisa de um navegador seguro e com suporte a navegação realmente anônima, veja aqui como instalar manualmente o navegador Tor no Linux.

Leia o restante do texto "Tor no Linux: veja como instalar manualmente"

Este texto saiu primeiro em Tor no Linux: veja como instalar manualmente


As already mentioned in our previous blog post, with Leap 42.2 in Alpha phase and SLE12-SP2 in Beta phase, the YaST Team is concentrating the firepower in fixing bugs in the installer. We fixed more than 40 bugs in three weeks! The dark side is that most bug fixes are not juicy enough for writing a blog post… but there is always some interesting stuff to report.

Integration of installer self-update with SCC and SMT

The installer self-update feature integrates now with SUSE Customer Center (SCC) and Subscription Management Tool (SMT) servers. Until now, there were three different mechanisms to get the URL of the installer updates repository:

  • User defined (using the `SelfUpdate` boot option).
  • Using an AutoYaST profile.
  • The default one, specified in the `control.xml` which is shipped in the media.

Now YaST2 is able to ask for the repository URL to SCC/SMT servers. The details of how the URL is determined are documented in the repository.

Fixes and enhanced usability in dialogs with timeout

As you may know, it’s possible to install (open)SUSE in an automatic, even completely unattended, basis using AutoYaST. AutoYaST can be configured to display custom configuration dialogs to the user and wait for the reply a certain amount of time before automatically selecting the default options. Until now, the only way for the user to stop that countdown was to start editing some of the fields in the dialog.

We got a bug report because that functionality was not working exactly as expected in some cases so, in addition to fixing the problem, we decided to revamp the user interface a little bit to improve usability. Now there are more user interactions that are taken into account to stop the counter, specially we added a new “stop” button displaying the remaining seconds. You can see an example of the result below.

New layout for dialogs with timeout

Following, as usual, the Boy Scout Rule we also took the opportunity to add automated tests to make that part of YaST more robust for the future.

Automatically integrating add-on repositories during installation

Sometimes you want to extend the regular installation media by adding just a few extra packages or provide a number of fixed packages along with the media.

For this purpose, the installer can automatically register an add-on repository. All you have to do is to put the repository on the installation medium and to add a file /add_on_products.xml that points to this repository.

The file looks like this:

<?xml version="1.0"?>
<add_on_products xmlns="http://www.suse.com/1.0/yast2ns"
    <product_items config:type="list">
            <name>My Add-on</name>
            <priority config:type="integer">70</priority>
            <ask_user config:type="boolean">false</ask_user>
            <selected config:type="boolean">true</selected>
            <check_name config:type="boolean">false</check_name>

You can define the following elements:

  • <name> is the name of your repository
  • <url> points the the repository location; you’ll likely

17 August, 2016

This Saturday I'll talk at FrOSConabout the future of private clouds and how Nextcloud is pushing that.

Frank won't make it, sadly, as he's in Denmark speaking at another event. Or somewhere else, his travel is a bit crazy lately ;-)

Future of private clouds

Frank blogged last week about a vision for Nextcloud and we've been thinking and discussing this at our hackweek with about 30 community members as well. It was quite amazing to bring so many people together and discuss these things!

Afterwards we've brought most of the topics to our forums or github, including our ambitious Nextcloud 11 roadmap. I'll certainly talk about some of those things this weekend at FrOSCon:
  • Communication integration
  • New app store
  • New updater
  • Federation
And more. Today or tomorrow we'll release a RC of Nextcloud 10 and I'll discuss what we've done there as well, what is new and improved, small and big.

If you like to get involved in the 'future', join us at our conference!


Como instalar a versão mais recente do VirtualBox no Linux

Se você usa o virtualizador desktop da Oracle e quer estar sempre com as últimas funcionalidades a sua disposição, veja nesse tutorial como instalar a versão mais recente do VirtualBox no Linux.

Leia o restante do texto "Como instalar a versão mais recente do VirtualBox no Linux"

Este texto saiu primeiro em Como instalar a versão mais recente do VirtualBox no Linux


Screen Shot 2015-09-10 at 15.46.06 copySnapshot 20160808 brought openSUSE Tumbleweed users Plasma 5.72 shortly after last week’s article was published, but it didn’t last long.

This week Tumbleweed appears to have a strong wind making it roll remarkably fast as openSUSE’s popular rolling release had six snapshots since the last update was published.

The latest snapshot, 20160815, was fairly small updating gstreamer-plugins-bad, libgusb and opus codecs.

Snapshot 20160813 updated repositories for systemd and kernel-source were updated to enable missing BayTrail and LynxPoint drivers. Yast2-firstboot was updated in this snapshot as well as a snapshot the day before. The multipath-tools package had the most fixes and cleanup in the 20160813 snapshot.

Some users might already be using the latest version of Mozilla Firefox after the 20160812 snapshot, which updated Firefox to version 48. Plasma 5.72 had a very short life in Tumbleweed as version 5.7.3 rolled over the previous version that arrived just four days earlier. Other notable updates in the snapshot were qemu, NetworkManager-openvpn and gfxboot.

Snapshot 20160811 had only two packages update in Tumbleweed, but there were a significant amount of patches and cleanup for grub2.

Updates for gnome-photos to 3.20.3, wine to 1.9.16, and xen to 4.7.0_10 were just a few of the many updates that made it into snapshot 20160810. Libnfs and libvirt  were updated in the snapshot. Python3-setuptools updated to 25.1.6 and a few updates for YaST virtual machine and network were also in the snapshot.


New packages in openSUSE Factory will automatically be submitted for the next release of Leap until Beta 2. Beta 2 is the freeze to get packages into the release of openSUSE Leap 42.2.

For those who want to get packages in the Beta 1, the submission deadline is August 25. The Release of Leap’s Beta 1 is expected to be released for testing on August 31. Testers are encouraged to test the latest development versions of Leap, which can be found at software.opensuse.org.

16 August, 2016

I was searching for a language to write the phone GUI with... python3+gtk3 is way too slow; 9 seconds for trivial application is a bit too much (on N900). python2+gtk2 is a lot better at 2 seconds. Lua should be even faster.

But while searching for good language, Vala caught my mind. Designed to be integrated with gtk/dbus, compiled language. I was woried about error messages and errors from vala->c->binary compilation, but seems good so far.

Oh and it seems that emacs org mode is right thing to use for calendar. It looks like a bit too complex at first, but it seems the complexity is well justified... and I was doing similar things manually. Still have to search for a component to notify using popup / audio when an event is upcoming.

Older blog entries ->